Wikipedia:Village pump (policy)

"WP:VPP" redirects here. For proposals, see Wikipedia:Village pump (proposals).

 Policy Technical Proposals Idea lab WMF Miscellaneous 

• Table of contents
• First discussion
• End of page
• New post

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, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195

Straw poll on the current view of WP:NOT#NEWS

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.

---

Recently I proposed a change at WT:NOT which related to WP:NOT#NEWS (Wikipedia is not a newspaper) which was taken through an RFC that closed recently here (permalink to that) It closed as no consensus, but I would recommended reading the !votes and discussion of that, as it highlights a currently growing issue on en.wiki, how are we supposed to handle current events/news.

A key factor is the current fate of Wikinews. It is, as mentioned several times in the discussion above, effectively a dead project, stuck in a catch-22 problem to get people to use it. There is clearly both editor desire and readership interest to see current news provided in a wiki-style, and en.wiki has generally done well before in covering current events. But events over the last few years (particularly over the last 2 years) have created a lot of editor tension and behavioral problems related to current event coverage (given what passes by AN/ANI/ARBCOM and various policy noticeboards), and highlights the differences between what an encyclopedia is and what a newspaper is. Their goals aren't fully mutually exclusive but there are several conflicting goals. WP:RECENTISM highlights many of these issues.

So I figure that to try to resolve this is to at least start with a straw poll, not designed to establish any immediate change in policy or guideline, but only to see where the current perception is of how en.wiki should be handling NOT#NEWS. Testing the wind, to speak. To that, there's principle three options to consider to get an idea where an editor/reader's interest in this may be as to determine the preferred method to go forward, if needed.

1. The current situation for NOT#NEWS is fine or only needs some small adjustments. This might include defining a guideline to help with writing current events articles (akin to WP:Writing about fiction), but likely no change to policy.
2. NOT#NEWS should be more strongly enforced, and limiting our current event coverage. This might include stronger enforcement of WP:NEVENTS, additional policies relating to NOT#NEWS, encouraging/putting more current news articles to draft space, pushing more content/editors to Wikinews, and the like.
3. NOT#NEWS should be less strong enforced, and expanding our current event coverage. This might include outright removal of NOT#NEWS, adjusting how NOT#NEWS and NEVENTS are written and handled to allow more news, effectively merge Wikinews in en.wiki, and the like.

As this is not an attempt to find a solution right now; I would fully expect that any proposed idea that comes out of that would be under a full Wiki RFC to consider before implementation. So a straw poll is best here. I would request you simply !vote in the appropriate section below, keeping threaded discussion to the provided discussion section. --MASEM (t) 16:23, 25 September 2017 (UTC)

Option 1: WP:NOT#NEWS is working as is

Or: The coverage of current events on en.wiki is about right or only needs fine adjustment

1. What should happen is the creation of a taskforce who routinely checks on news items that don't have longterm impacts. We should be posting items our readers are interested in, without our readers, this is all pointless, but I agree that some things which are instantly recorded as "news" may not have such a long-term impact as to be considered encyclopedic for a long-term view. This is a natural conflict between (say) an "in the news" section and a paper encyclopedia which records genuinely uber-notable events. We should not divest our readers of the things they want to see just because of some snobbish and contrived criterion. The Rambling Man (talk) 20:24, 25 September 2017 (UTC)
2. First choice. Each time I've tried to get articles deleted for violating NOTNEWS (such as Richard Matt) the AfD has gone nowhere - and on each occasion, in hindsight, the judgment of the community has proven correct. There are a good number of editors who like to write about current events and overall I think they do a good job and provide useful articles that bring readers to the project and enhance Wikipedia's reputation. In the discussion at the NOTNEWS talk page there was a great deal of "it's terrible" comments but little in the way of specific examples of a need for change. Coretheapple (talk) 21:25, 25 September 2017 (UTC)
3. I'm not seeing the need for stricter enforcement, and I doubt the practicality of trying to stamp out current events articles. Wikipedia will be what Wikipedians want it to be, and this is what they want it to be. If that doesn't jibe with NOTNEWS, then jettison NOTNEWS. Beyond My Ken (talk) 21:32, 25 September 2017 (UTC)
4. stricter enforcement will not be useful/effective. —TheDJ (talk • contribs) 21:35, 25 September 2017 (UTC)
5. First choice. --Jayron32 14:04, 26 September 2017 (UTC)
6. The folks who are busy AfDing current events article are generally not busy AfDing old-current-events articles from 10+ years ago. Why is that? Because human nature enjoys working with current events, be it inclusionist or deletionist. It's just a manifestation of what people want to work on and how. For those AfDing the old articles, they will need more justification than citing the NOTNEWS alone, like if there has been longer term impacts, consequences of the event. -- GreenC 14:18, 26 September 2017 (UTC)
7. First choice. -- E.M.Gregory (talk) 21:03, 26 September 2017 (UTC)
8. First choice. NOTNEWS, properly applied, strikes a fair balance between keeping encyclopedic material and avoiding the truly mundane topics that also get news coverage. The problem is that there is not much guidance, and too many people think that NOTNEWS is carte-blanche to delete any articles about current events. Wikinews is dead and its writing style is anathema to Wikipedia's. Whether we like it or not, Wikipedia's article on a breaking news event is often the most complete, up-to-date, and unbiased coverage available, which is why so many readers come to us. We should be helping those readers, not hindering them. ---- Patar knight - ^chat/_{contributions} 20:49, 26 September 2017 (UTC)
9. First choice. petrarchan47คุก 18:08, 28 September 2017 (UTC)
10. It is working as it is. The "news articles" are relevant for Wikipedia. So the question here is: should we wait a year or two or longer with writing an article on the topic (since that would be the amount of time needed until the entire investigation and law system is done) or should we write an article on the event and update it. And as we clearly can see: there is a) an interest from Wikipedia users and editors at keeping it the way it is and b) there are enough editors editing it, so the information is from reliable sources and updated very quickly. The "current event" at the head of the article is pointing out, that information can quickly change. The product is actually quite good. Of course we could wait - but that would make Wikipedia less useful (who cares about the event in 5 years from now!?) and the articles would get worse, because less users would edit them.--Albin Schmitt (talk) 14:58, 2 October 2017 (UTC)
11. First choice, lets work on the fine things first before going into major changes. - Knowledgekid87 (talk) 14:59, 2 October 2017 (UTC)
12. First choice. We're never going to get this perfect, when an event is fresh knowing whether it will get persistent coverage over time, etc., is a matter of judgment. On the whole, I think we do okay, I see as many things that appear errors of inclusion as errors of exclusion. --joe decker^talk 15:08, 2 October 2017 (UTC)
13. You're clearly forum shopping, looking for a result that will justify your predetermined solution. No evidence that the policy is a problem other than a few disgruntled editors who won't WP:DROPTHESTICK. Wikinews is dead, editors and readers come here for encyclopedic looks at current topics. They have already spoken loud and clear and have been doing so for years. Gamaliel (talk) 15:17, 2 October 2017 (UTC)
14. I've been working around current events on Wikipedia for 10+ years. During that entire time there have always been people who think we spend too much time covering the news, and there have also been people who think we should do more to cover the news. Personally, I think we get the balance about right most of the time. If I had to choose in the moment, I would probably err on the side of more news articles rather than less. We can always go back and clean-up / delete the less significant news stories later. However, in general, producing a lasting encyclopedic summary out of major breaking news is one of the things we are actually quite good at. This should be encouraged, and for the most part I think it has been. Dragons flight (talk) 15:19, 2 October 2017 (UTC)
15. Disagree with the way this poll has been presented and hope it will not be used as any form of consensus. I don't think a problem has been properly framed – to base it on Wikinews being a "key factor" seems completely out of step with what most Wikipedians do with current events. Wikinews is irrelevant, hasn't been a factor and shouldn't be a factor. As User:Gamaliel alluded to, I cannot avoid thinking that this being the third massive discussion about this (one, two, and this) in as many months is counterproductive and asking the same question over and over again in hopes of getting a different answer. Instead, I'll assume good faith. But I must say this is quite taxing while not really moving the conversation forward. -- Fuzheado | Talk 18:45, 2 October 2017 (UTC)
16. I agree that this appears to be forum-shopping, with essentially the same issues raised with slightly altered language. Even before this is over an effort is being made to generate "observations" i.e., consensus on specific points. Figureofnine (talk • contribs) 18:54, 2 October 2017 (UTC)
17. Seems fine; what should happen is not the creation of new rules, but rather than enforcement of our current ones. And I agree with other editors who say that this "straw poll" was not properly presented. Neutrality^talk 12:28, 3 October 2017 (UTC)
18. I don't see any problem with the current balance; some people are quick to create articles, other people are quick to nominate them for deletion, and there is senseless and futile knee-jerk reaction on both sides, which tends to settle over time into more reasonable results. We'd also need a demonstrated consensus to change anything anyway; we can't just legislate from on high to target the articles we want deleted at AFD. postdlf (talk) 15:10, 3 October 2017 (UTC)
19. First choice Gandydancer (talk) 15:25, 3 October 2017 (UTC)
20. Seems to be working about right the way it is. Some people abuse the guideline to try to get rid of stuff they don't like, but regardless of what happens everything sorts itself out in the end through discussion and becomes obvious with (or without) WP:SUSTAINED coverage. Truly notable subjects will continue to get coverage, and those that are only covered for a short time will get deleted eventually. People on both sides need to realize that there is WP:NORUSH. — Insertcleverphrasehere ^{(or here)} 13:14, 4 October 2017 (UTC)
21. Sure, support aswell. Doc James (talk · contribs · email) 02:27, 14 October 2017 (UTC)
22. Theb alance seems to be working well--as judged by the trend decisions at AfD, there is general agreement on the boundaries, tho sometimes sharp disagreement in specific cases. No change in rules will eliminate that sort of disagreement. DGG ( talk ) 16:49, 14 October 2017 (UTC)
23. Our status quo agreement per RS is the way to go. No need to restrict any further. --QEDK (愛 • 海) 19:30, 14 October 2017 (UTC)
24. Second choice. --Shrike (talk) 10:29, 24 October 2017 (UTC)
25. First Choice The current consensus is adequate with borderline cases being decided at AFD, there is no need for instruction creep Atlantic306 (talk) 20:24, 24 October 2017 (UTC)
26. First Choice - Looks good to me, borderline cases are taken to AfD. The process works, imperfectly, but it works as it is today. XavierItzm (talk) 11:25, 30 October 2017 (UTC)
27. Working fine as is, except in the case of those who interpret it strictly and act like we have no news on Wikipedia or should have no news on Wikipedia. Flyer22 Reborn (talk) 19:51, 12 November 2017 (UTC)
28. I object to this being proposed as a trichotomy, since the question is really "Not The News should be more strongly enforced, Yes or No?" Adding a third option serves as a spoiler, guaranteeing a plurality for the enforce stronger vote, when it does not have consensus. This proposal simply reminds me of IDON'TLIKEIT and those editors who file ANI's and other reports "out of concern for the community" at the drop of a hat or as a modus vivendi. The community is doing just fine, this is an invalidly ill-formed distraction. μηδείς (talk) 20:45, 25 November 2017 (UTC)

Option 2: WP:NOT#NEWS should be more strongly enforced

Or: En.wiki should have significantly less coverage of current events

1. We definitely need to be stricter. Blueboar (talk) 20:11, 25 September 2017 (UTC)
2. Per the fact that WP:TRUMPSCANDALAFD is pretty much standard these days and it can go any way you want. A lot of the keep or no consensus AfDs eventually end up deleted the second go round or merged. Creating clearer standards than the GNG for current events is important, and NOTNEWS is the obvious first place to start with clarifying what is and isn't acceptable to include in Wikipedia immediately. Also, per my comments below, the biggest issue with not enforcing NOTNEWS is that we spend an inordinate amount of time having to deal with enforcing BLP policy amidst shouting and screaming that because something is so notable it must not be covered by BLP policy. This could be avoided both for the good of the encyclopedia and for the subjects of the articles if we encforced NOTNEWS more strongly. TonyBallioni (talk) 20:17, 25 September 2017 (UTC)
3. and this should include daily and weekly updates of sports tallies, film takings and so on. Here we are just acting as a mirror site riding on the websites that specialize in those types of information. Concurrently the main page "in the news" section should be scrapped, it's like a pile of last week's newspapers: Noyster (talk), 23:00, 25 September 2017 (UTC)
4. I think we could strengthen and clarify these guidelines a bit. Kaldari (talk) 00:09, 26 September 2017 (UTC)
5. NOTNEWS needs to be stricter. I don't like inclusionists claiming that a piece of Trumpcruft deserves to be included because it has a couple reliable sources. KMF (talk) 00:50, 26 September 2017 (UTC)
6. I would support allowing for an inter-wiki redirect for these topics, to aid in enforcement. Hurricane Harvey was obviously notable as it was happening, but even there it would be better to have people do live updates of that page on Wikinews. With SUL there's no editor burden to editing on a different Wiki domain. power~enwiki (π, ν) 01:07, 26 September 2017 (UTC)

   Wikinews is largely a failed project that doesn't really report on any of the major news events that we are discussing here. Just pointing that out as an example of why the interwiki links wouldn't likely work. TonyBallioni (talk) 01:51, 26 September 2017 (UTC)

   I'm not familiar with the details of why it failed, but I'm aware that it's mostly dead. Pointing editors from en.wikipedia to it (for certain topics) would need to be part of a plan to revive it. power~enwiki (π, ν) 02:46, 26 September 2017 (UTC)

   From my experiences on WikiNews, there were not enough reviewers and a very short deadline (3 day) to have a review. With no review or updated/additional info, the potential article is deleted. This would even occur when the article would indicate a future event when additional information or action would be taken and was noted by said editor (me). This would frustrate writers as most of their work would be deleted. Spshu (talk) 16:55, 15 November 2017 (UTC)

7. Above points taken on Wikinews and the inanity of repeated "current event" AfDs. I don't know what good additional "rules" will do here, but I do think it would be smart to funnel/interwiki our less encyclopedic topics into Wikinews articles, or at least reach out to the English Wikinews editors to see how the content may be transferred fruitfully. (Has anyone reached out?) On the other end of the predicament, I think better enforcement of summary style for new topics makes for better encyclopedic coverage. Standalone topics tend to collect all kinds of overly specific detail and tone unfit for a general audience. czar 03:05, 26 September 2017 (UTC)
8. As per Tony. While I agree with the Option 1 comments that stronger enforcement of WP:NOTNEWS as a whole in the moment isn't realistic and at times can be counterproductive, there are certain aspects of it (for example WP:BLP as Tony says) which are IMO incredibly important. And although more bureaucracy is really not the best way to deal with anything, I think that it could be useful to have some sort of review of current events articles a certain amount of time after creation to determine if it meets the notability criteria that can't be determined while it's still in the normal news cycle (WP:SUSTAINED, for example). The ideal solution would be for people to wait before creating articles instead of having them nominated for deletion immediately and then having those discussions closed with a "wait and see" type result, but that really isn't going to happen. ansh666 08:57, 26 September 2017 (UTC)
9. For reasons of notability and BLP. Fram (talk) 12:06, 26 September 2017 (UTC)
10. And this can be enforced as soon as admins discount the "wait and see" tactics inclusionists employ at AfD. This has become the most popular rationale to keep an article when it fails the actual substance of WP:EVENTCRIT. Or discredit the "easily passes GNG" votes which is not the case on a news event. Another thing we need consensus for is converting WP:RAPID to an essay; it contradicts itself and has no basis on notability yet inclusionists use it as a safeguard for deletion.TheGracefulSlick (talk) 16:56, 26 September 2017 (UTC)
11. My idea for stronger enforcement would perhaps involve changes to policy for a, presumed, "immediate" forced merger to existing articles of breaking news, say to last for at least a week or two - perhaps with a breaking news merger noticeboard and project, and a simultaneous allowing of a "draft" article that is indexed. -- Alanscottwalker (talk) 20:50, 26 September 2017 (UTC)
12. Wikipedia has stupidly encouraged the hoi polloi to reflexively come here to post their own truth, aided and abetted by the overenthusiastic among us who seek to write about every current event. Not only do many of these creations fail notability criteria, we give their subjects short shrift by parroting the contemporaneous screed from mere journalists. Chris Troutman (talk) 00:58, 27 September 2017 (UTC)
13. News coverage of current events is and should be treated as primary sources. Wikipedia is an encyclopedia. While we err on the side of more coverage by allowing some articles to rely mostly on primary sources, events that are entirely and solely sourceable to news media should not be covered by Wikipedia. This is why we made Wikinews. —/Mendaliv/^2¢/_Δ's/ 02:00, 27 September 2017 (UTC)
14. Per Mendaliv and other above. Whether Wikinews is functioning or not, it doesn't change the fact that we're an encyclopedia, not a news outlet. Ealdgyth - Talk 14:12, 27 September 2017 (UTC)
15. Too many people think if it was in the papers it must be notable. Many things are in the papers becasue they are interesting and satify people's thirst for something to engage their interest - which sells papers - but they are not notable in the scheme of things. The internet has made all this information so much more readily available but run-of-the-mill events have been happening for millenia. One only needs compare the ratio of recent events recorded here to the similar events that happened 30, 50 or 100 years ago. This encyclopedia is fast becoming the Readers Digest version of online newspapers. ClubOranje^T 19:40, 28 September 2017 (UTC)
16. I am not sure we can actually enforce NOTNEWS anymore, as people have become used to Wikipedia being pretty good (and a lot better than Wikinews) at covering current events. However, I think we should at least try. As a first step, maybe we can replace the "In the news" section of the Main Page by a link to Wikinews? —Kusma (t·c) 21:26, 28 September 2017 (UTC)

    @Kusma: For what it's worth, that has been proposed before and shot down because of inactivity at en.wn. ―Justin (koavf)❤T☮C☺M☯ 22:22, 28 September 2017 (UTC)

    @Koavf: I think our ITN section is one of the things that cause inactivity at Wikinews. —Kusma (t·c) 08:56, 29 September 2017 (UTC)

17. We should be stricter with this, especially given the recent influx of political articles being created preemptively. Jdcomix (talk) 17:16, 29 September 2017 (UTC)
18. I think the basic problem here is that Wikipedia operates on an idiosyncratic definition of secondary sources that includes news reports. Everybody outside Wikipedia regards news reports as primary sources, so we should do the same, and follow our basic principle of basing articles on genuine secondary sources, which can include some content published in newspapers, such as profiles and background articles that look at events over a long term, but not contemporaneous news reports. 86.17.222.157 (talk) 19:48, 29 September 2017 (UTC)
    1. I agree with 86.17 on the "secondary source problem": WP:Secondary does not mean independent. However, I think it's a bit more complicated than that. WP:PRIMARYNEWS covers some of the differences between a primary news source (e.g., eyewitness news reports) and a secondary source that is published in a newspaper (e.g., news analysis). WhatamIdoing (talk) 19:16, 17 October 2017 (UTC)
19. Per User:Noyster (great reasoning)....but trying to enforce that would be daunting....endless editwars and RfC's. --Moxy (talk) 19:58, 29 September 2017 (UTC)
20. I agree with several of the points in the comments above, ultimately boiling down to "I support the existence of WP:NOTNEWS for the reasons we have it in the first place." In the interest of thinking about enforcement strategies, I'll say again that this seems like a perfect use of the draftspace. See, although Wikinews hasn't done so well, Wikipedia does sometimes cover news well (that doesn't mean we should be doing so, of course -- I'll bet we could do lots of the things from WP:NOT well). Because many of the subjects do turn out to be notable, I see no reason why we shouldn't use the draft space to capitalize on short-term interest for the benefit of the long-term article. — Rhododendrites ^talk \\ 02:02, 30 September 2017 (UTC)

    That's an interesting observation about draft space. My experience of it has been that it is used as an excuse to delete articles about topics that don't qualify for deletion under policy and that should be developed in main space where they are visible to potential editors, as has always been a central part of the wiki process, but this seems like a valid use of that space. 86.17.222.157 (talk) 09:52, 30 September 2017 (UTC)

21. To abandon or weaken NOTNEWS is a counsel of despair IMO. I hope to have time to leave a longer post over the next few days, but believe we should clarify (to ourselves at least), that we are notnews for good reasons. These include that we undertake a longer-term responsibility to the subject, to give the more complete and rounded picture than that revealed in yesterday's headlines. I agree that it would be nearly impossible to put a 'full embarge' on news articles, and many of the 'big event' ones are well-written and accurate surprisingly quickly. However, IMO, it is a simple mathematical inevitability that the more we become simply a 'news archive', the less we will have any encyc. character or purpose. Pincrete (talk) 11:22, 1 October 2017 (UTC) … … ps I endorse the "is fast becoming the Readers Digest version of online newspapers" comment above, I wish I'd thought of the analogy! Pincrete (talk) 11:28, 1 October 2017 (UTC)
22. Stricter. I agree with Pincrete. BLP is a major issue, as are the seismic changes (hm, is that hyperbole) in not just American but other countries' resulting in a large number of new articles, as mentioned above, and new editors with no knowledge of our guidelines and often SPAs. Doug Weller talk 14:02, 1 October 2017 (UTC)
23. Same fix I've proposed before, which is a policy WP:Criteria for Speedy Incubation which is like WP:CSD.  A new criteria allows a breaking news article to be moved to draftspace, with the mainspace title being salted for 7 to 14 days.  An AfD in progress gets procedurally closed WP:NPASR.  The problem I'm seeing is that AfDs are spinning their wheels analyzing notability with a moving target.  As I posted yesterday at DRV, the problem pushes forward to other forums when decisions are made based on moving-target notability.  Unscintillating (talk) 20:24, 1 October 2017 (UTC)
24. Stricter. I'm glad to see this straw poll because I've often wondered about WP:NOTNEWS myself. While Wikpedia is fast becoming a gutter press, some of the more serious news items also belong on Wikinews. I don't know how we can achieve this. Kudpung กุดผึ้ง (talk) 00:32, 2 October 2017 (UTC)
25. Stricter. There is far too much insertion of trivial news events, commentary about our subjects and lengthy quotations. It gets in the way of knowledge. I am developing a solution. Join me. - Shiftchange (talk) 00:55, 2 October 2017 (UTC)
26. Stricter. Too many articles are being created which have a splash in the news with no lasting notability. - Knowledgekid87 (talk) 14:57, 2 October 2017 (UTC)
27. Agreed. Creating lasting enyclopedic articles with proven information backed by references in solid reliable sources is something the wiki system does (perhaps suprisingly) very well. Mimicking the National Inquirer and TMZ, not so much. Andrew Lenahan - Starblind 17:13, 2 October 2017 (UTC)
    • And the WSJ, NYT, Washington Post, NPR aren't solid reliable sources? Using them to cover fairly recent events would be an issue because we'd be like TMZ? I'm not quite getting your point here. Hobit (talk) 11:24, 23 October 2017 (UTC)
28. Definitely. And in particular the insistence on lasting interest in a subject is widely disregarded. Mangoe (talk) 22:04, 2 October 2017 (UTC)
29. There is definitely a problem of people with WP:RECENTISM forgetting that we want encyclopedic knowledge, not blow-by-blows of unfolding events simply because they are sourced. That can range in the short term of a few hours or events happening over a day or two. Sometimes, an event is going to take a longer time to determine whether it's truly a significant event or not. Lawsuits are a good example of the latter where they came take time, sometimes years, but you get people pushing to things like ambulance chasing suits to articles because a newspaper reported that someone got sued (as opposed to the court decision that establishes the encyclopedic value). I'm not sure how we can stress that Wikipedia takes the long view even more though. Kingofaces43 (talk) 22:25, 2 October 2017 (UTC)
30. I am mostly in sympathy with this view. Many articles about recent events are simply summarized news reports, often contemporaneous to the event, with little or no long-term view. It's basically a news feed. On the other hand, at the beginning stages, a summary of the various news reports is the only thing known about the topic, and many people come to Wikipedia to get a decent overview. It's something Wikipedia does passably well, though there are many distortions involved. My instinct is that Wikipedia should not be summarizing news; that's not its job, and BLP issues also frequently arise. Kingsindian ♝ ♚ 02:12, 3 October 2017 (UTC)
31. Example: Every time someone who works for Big Company A tweets a stupid thing and gets fired, people run screaming to Big Company A's article to tack it on or to create a "Controversies" section. Wp:NotNews needs to be beefed up to be a bulwark against the headline-of-the-moment news cycle. TheValeyard (talk) 04:08, 3 October 2017 (UTC)
32. Stricter. As I often try to parse bias, as opposed to going into edit wars, the "value" of perceived editors over recent events ends up in clear bias and conflated news items, with loooooong talk pages of arguing what is notable or noteworthy, when in reality, if they waited an hour, they'd get confirmation or an RS. I just supported an AfD for "reactions" for the Vegas shooting, because it was full of "my prayers and sympathies"... from Mariah Carey, for example. Just as I support removing conjecture on weapons used, etc., if Wiki is to read like an Encyclopedia, then something that has hard fact that will be released in the coming days or even hours, including wild speculation from people not on the scene is actually the currently supported way to do it on the 2017 Las Vegas Strip shooting. In fact, the name of the page itself is a bit wonky, because it wasn't on the strip and didn't target the strip. (And actually was performed within confines known as the South Strip, which makes a bit of a difference geographically.) As an encyclopedic entry, it would be named something like Jason Aldean Concert Shooting or Route 91 Harvest Music Festival Shooting. Alas, someone had to rush it to Wiki and rush to slam in a bunch of conjecture and unrelated facts. Trying to bring sanity to edit wars when that happens is nigh impossible. Avoiding the mess in the first place would be ideal. Seola (talk) 05:36, 3 October 2017 (UTC)

    I should also add, like others mention, when an event may or may not be notable waxes and wanes. There are a great many stub pages of events that no one can remember and no one looks for. I come across them and try to clean them or if I can't, I nom for AfD. And invariably, some random editor comes by and insists that nothing on Wiki should ever be removed because it was justified "at the time". There is just too many of these junk articles as it is. Putting up stricter guidelines would avoid errant words, phrases or sentences that also often happen when edit wars are going on, especially when vandalism is missed, because so many edits are happening at once.Seola (talk) 05:40, 3 October 2017 (UTC)

33. Wikipedia's structure makes it far too easy for any user to create an article about the latest minor controversy, meme, or viral incident without meeting criteria or consensus that the page should exist, while far too hard to remove an article that shouldn't be here. The proliferation of news sites that piggyback on each other's work without independently providing notability undermines the GNG and in turn the project as ephemeral topics all have their own low-quality articles. We should also encourage more summarizing into main or related articles, rather than permitting subarticles to be made for so many little things. (See also: also the awful "International reaction to..." quotefarm articles). Reywas92^Talk 06:22, 3 October 2017 (UTC)
34. Realised I hadn't actually !voted. Per my comments elsewhere and below regarding current news coverage. Only in death does duty end (talk) 10:12, 4 October 2017 (UTC)
35. It should be more strongly enforced, but in an even-handed manner that treats similar situations similarly, rather than in an ad hoc or partisan manner. I’d suggest that we more strongly discourage material about recent news that relies on primary sources, including newspaper opinion pieces and blog posts that have not been deemed worthy of mention in reliable secondary sources. We could also discourage material about recent news that names people who are expected to remain non-public figures. If we carve out particular areas like this for special treatment, then we can make good progress toward enforcing NotNews in a way that isn’t apt to change e.g. when the political shoe is on the other foot. Anythingyouwant (talk) 23:35, 5 October 2017 (UTC)
36. An encyclopedia does not need any of the transiently popular "stories". Rentier (talk) 23:58, 5 October 2017 (UTC)
37. As as been said, we want to report the controversy, not to be art of it. One of the main issues are probably a nees to clarify notability (say a election result is immediatelly notable, some fact about the latest shooting may be or not - and we should play on the safe side). That WikiNews is not active (or not) is not a reason to have news(ish) articles here. If we have no "news" here, probably WikiNews would work better - better connection / linking to and from may benefit all: editors and readers of both tendencies. "Sell" it as "the wikipedia of recent events", link to it for day-to-day timelines, and so on. - Nabla (talk) 18:27, 7 October 2017 (UTC)
38. Only choice. This also works to counter systemic bias in favour of northern hemisphere, western news. Stifle (talk) 15:56, 9 October 2017 (UTC)
39. Absolutely. Recent news articles are too often irreparable messes created with the presumption that an AP/Reuters report parroted by half a dozen news portals constitutes eternal notability, and hijacked by editors with a chip on their shoulder who edit war until the subject (doomed to "no consensus" on AfD) falls into oblivion a few months later. I think Wikipedia would do better without the product of such labour. Daß Wölf 18:25, 14 October 2017 (UTC)
40. Both as to inclusion of "passing stuff" and misuse of WP as a "live feed", e.g. of questionable and basically OR sports scores, casualty tolls, etc. which we don't know are confirmed until some time has passed. As just one example, a snooker ranking tournament article was recently updated over 300 times in the space of a day or two, to provide live coverage of game results. This is not what WP is for, and there are snooker news sites that are for this. We need not have any results tables at all until the event is over and RS confirm the results. "I was there" isn't a source, and "I saw the win on a televised match" isn't a reliable one. I'm not picking on snooker coverage in particular, I just saw it yesterday. The problem is likely much worse for things like football/soccer.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  01:13, 21 October 2017 (UTC)

    The problem isn't usually so bad with sports, because the running commentary is usually factual. but, more seriously, we get similar running news added to Wikipedia about news events that may or may not be terrorism based on primary news reports. We had an article created recently that was edited by loads of people about a road traffic accident in Exhibition Road, London, because the initial reports speculated that it might be terrorist-related, although it turned out pretty quickly that it was not. Why can't we just do our job as an encyclopedia and wait for secondary sources to appear before rushing to create an article based on editors' own interpretation of primary sources? 86.17.222.157 (talk) 16:32, 22 October 2017 (UTC)

    Um, that's exactly what I'm suggesting.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  15:07, 6 November 2017 (UTC)

41. The problem with such intensive coverage of the news of the day is that you end up with lots of abandoned articles about stories that are forgotten fifteen minutes after they occur. What Wikinews is or is not doing isn't really relevant to a discussion about what is happening here on Wikipedia though. Lankiveil ^{(speak to me)} 00:27, 24 October 2017 (UTC).
42. For several reasons. (1) Articles in news sources are typically primary sources, because they are part of the context in which an event occurs, and just as we follow medicine's definition of primary sourcing when writing about medical topics (WP:MEDRS), we need to follow history's definition of primary sourcing when writing about history, which includes events. Exceptions occur, as a news story may mix primary and secondary coverage of different events, e.g. it talks about an ongoing event and discusses the context in which the event started 100 years ago, or a news source may provide purely secondary coverage, e.g. it only discusses the context in which that event started. Let's ensure that only secondary sources are used, except in the less common situations in which WP:PRIMARY permits primary-source usage. (2) How often is a news editor or a reporter a topic specialist? He's a specialist in good writing or so we wish..., in selecting what subscribers and newsstand-purchasers will want to buy, and in condensing the story down to what will fit on the page, but in nearly all cases, your news editor and your reporter have average knowledge about the topics in which they're writing. See WP:RSBREAKING, which {{Recent news}} links — we're admitting that news coverage is often wrong, so why do we permit it? (3) Finally, an encyclopedia reports what's covered in secondary sources. In most cases, you can't predict that something showing up in a newspaper will be covered in secondary sources that won't be published until months or years in the future. Yes, there are exceptions, e.g. a news report saying that this candidate won 1,234,567 votes, while his competitor won 1,000,481 votes, but unless you can show that exactly this kind of thing has been covered in the past, you're making a statement that secondary sources will cover a topic, and no reliable, published sources exist to support this allegation, to paraphrase the intro to WP:OR. This is particularly a problem with political stuff — how can you be certain that future political historians will care about the latest mini-scandal? Nyttend backup (talk) 21:09, 25 October 2017 (UTC)
43. Trying to keep current events and news is a waste of valuable time, there is always something to do on en.wiki. Kanarya08 (talk) 08:50, 1 November 2017 (UTC)
44. Absolutely - much of today's published news combines publisher/journalist POV, propaganda, and a splattering of facts buried under allegations in order to create the level of sensationalism needed in the highly competitive bait/click news environment. While printed news has pretty much become obsolete, publishers still need to "sell papers". Look at it from the POV of a hungry journalist and publishing execs who need to generate revenue in a highly competitive market. On the other hand, WP's growth has been the result of adherence to our 5 pillars not the bait/click sensationalism used by news sources to attract readers. The importance of maintaining NPOV and factual accuracy cannot be overemphasized. ^{Atsme📞📧} 12:26, 2 November 2017 (UTC)
45. Yes, I think there is way too much rushing to see who can be first to sloppily report something that could be covered better with the passage of time. On the other hand, I don't see a way that we could really enforce this, because so much will depend upon local consensus for each case. --Tryptofish (talk) 21:47, 3 November 2017 (UTC)
46. Trying to police news-like articles will be impossible should wikipedia embrace news-like articles. A trip to WP:AFC shows that POV-Pushing is a massive problem as-is. If Wikinews is dead, revive it. RfCs have previously operated on a principle of "Wikinews is dead", so why not change that? If there's truly interest of news in a Wiki-like environment, then go to wikinews, for god's sake, instead of opening the door for POV-pushers. ProgrammingGeek ^talktome 15:43, 8 November 2017 (UTC)
47. Of the options here, I suppose this comes closest to my own view — but what I mean, in part, is that we should have clearer guidelines and not merely tighter ones. It's undeniably true that some breaking news events do turn into good articles about important events of enduring notability through the collaborative editing process — but it's also undeniably true that some people seem to think every individual bit of flotsam or covfefe that turns up in any media at all always merits its own standalone article. For instance, there is currently 2017 Ottawa Storm, a wholly unremarkable thunderstorm with entirely run of the mill effects whose coverage didn't even extend into the next day, let alone the next year — thankfully it's up for deletion, and I see no prospect of it surviving that, but I'd still prefer that nobody had ever thought it would warrant an article in the first place. There are obviously certain news stories that are almost always going to be valid and enduring article topics that pass the ten-year test (remember, 9/11 was once a "breaking news" story), and certain news stories that are virtually never going to be valid or enduring article topics that pass the ten-year test (we do not need an article about every house fire or every murder or every thunderstorm that happens anywhere at all). But perhaps we could stand to be a little clearer about how to apply some actual discernment to which side of that line any given news story falls on, because it's particularly easy to make the wrong call on a news story in the initial rush of "this just happened" coverage. Bearcat (talk) 19:38, 12 November 2017 (UTC)
48. I support stricter, especially in cases where scholarly sources and news sources conflict, and the scholarly sources are considerably more detailed in their analysis. There are also numerous criticisms of news sources relying on unnamed, anonymous sources. Further, there is a tendency to selectively cherry pick quotes from articles, and when used this way they are basically WP:PRIMARY in support of WP:OR. These issues are all already implicitly addressed by our policies, but stating it more explicitly may help. Seraphim System ^(talk) 20:00, 12 November 2017 (UTC)
49. Second choice, given that each is met:
    • Generally, WP:NOTNEWS-violating articles should always be taken to AFD instead of CSD; as a controversial issue this should be beyond debate.
    • GNG should be assumed until the fact that the article indeed consists of primary sources is proven.
    • Lastly, the quorum is expanded dramatically to allow further opinions.

    ToThAc (talk) 18:29, 13 November 2017 (UTC)

50. As, I once indicate on Meta as to deal with link rot/citation issues by using [1]. With WikiNews articles could be used as sources (as they have to be reviewed/verified) and enforcing NOTNEWS here with a way to move articles to WikiNews should cause an upsurge in writers (and hopefully reviewers) at WikiNews and as WP's rotlink solution. Spshu (talk) 16:55, 15 November 2017 (UTC)
51. Wikipedia is not breaking news. Especially on political topics. PackMecEng (talk) 16:05, 20 November 2017 (UTC)
52. Stricter. Current news is not necessarily notable, even if it's, like, totally on CNN for a week straight. SpartaN (talk) 04:30, 6 December 2017 (UTC)

Option 3: WP:NOT#NEWS should be less strongly enforced

Or: En.wiki should have more expanded coverage of current events

1. Weak support here - I dislike the current push against current events, but I don't think that we should fully become like a newspaper (i.e. we should take into account the lower reliability of reporting on current events and require more sources than usual to pass notability for current events). RileyBugz^会話_投稿記録 18:24, 25 September 2017 (UTC)
2. It'll be what it's going to be, and if that doesn't align with NOTNEWS, get rid of it. Beyond My Ken (talk) 21:34, 25 September 2017 (UTC)
3. Support. The problem with "NOT#News" is that a) it is a badly written policy, like all of WP:NOT, because it is all written as part of a list of negative things rather than as a direct statement of policy, and b) none of its "enforcement" (i.e. taking out articles about things because you dislike them politically, which is what that means in practice) has anything to do with what it says. Conversely, when you see a blindingly obvious violation of the text as written -- like the list of current watches and warnings in Hurricane Maria, temporary content that is being taken out the moment it expires, complete with a special disclaimer at the top of the article -- nobody seems to give a damn. I say if you have a dog that can't hunt and can't point and can't fetch but it can sink its teeth into every car tire, neighbor and postman that goes past, it's time to think about getting rid of the dog. Wnt (talk) 11:54, 26 September 2017 (UTC)
4. Second choice. The problem with WP:NOTNEWS is that it is over-used by people who think it means "If it is reported by newspapers somewhere, it is AUTOMATICALLY not appropriate for Wikipedia." which is fantastic over-reach. News coverage does not disqualify or invalidate Wikipedia content, and yet I would (unscientifically estimate) that WP:NOTNEWS is envoked more than half of the time as a deletion rationale rather than as style guidance. --Jayron32 14:06, 26 September 2017 (UTC)
5. I guess this is my second choice too, thank you Jayron32 for reminding me of that option. I agree with Jayron32 that NOTNEWS is overused, and if any changes are necessary they should be in that direction. Coretheapple (talk) 14:35, 26 September 2017 (UTC)
6. Second choice per Jayron32 and Coretheapple. NOTNEWS should work as it is, but it often doesn't. ---- Patar knight - ^chat/_{contributions} 20:58, 26 September 2017 (UTC)
7. Second choice. The problem with WP:NOTNEWS is that it is over-used by people who think it means "If it is reported by newspapers somewhere, it is AUTOMATICALLY not appropriate for Wikipedia." To this I want to add that our readers expect certain kinds of news stories to appear on Wikipedia, and that is no bad thing, not least because it has long seemed to me that the urge to add a bit of information to a breaking news story - or even to start an article on a news event, seems ot sometimes be an entry point for new editors. Of course, more editors would be the best solution to this and many problems and the nasty aggression on exhibit seems to drive editors away. I think one solution is for editors to hold off bringing articles to AfD on NOTNEWS rationals for about 3 months, a waiting period would reduce the Sturm und Drang factor.E.M.Gregory (talk) 21:02, 26 September 2017 (UTC)
8. Support—Current events are a way to capture editing energy and to rapidly compare developing information. It's one of Wikipedia's unique contributions to global knowledge, based on the fact that it's the only near-real-time encyclopedia. There should be strong enforcement of standards (BLP, V) on current events stories, but patient evaluation of notability for borderline cases. The quick but byzantine disputes over notability during a highly charged time pose emotionally charged questions that new editors are not ready for: are these atrocity victims significant? will that protest affect the course of the state? We're better served having editors focus on sourcing and information gathering than on debating these questions. And we're better off having started articles of borderline permanent notability (e.g., this article on Egyptian protests by midnight of 25 January 2011) Then, after a short-term time window (7 or 14 days, perhaps), evaluate notability and keep, delete (if of poor quality), or export to Wikinews (if not notable).--Carwil (talk) 18:52, 28 September 2017 (UTC)
9. Weak support. The problem with WP:NOTNEWS enforcement right now is that it often causes highly-trafficked articles to be nominated at AfD, with editors spending their efforts arguing for or against deletion instead of trying to improve content viewed by many people. This reflects badly on Wikipedia, and visitors may also perceive Wikipedia to be heartless when they see a large rectangle on top of an article about a significant news event that may or may not be notable. It can be argued that this may be a good opportunity to introduce casual visitors to the world of Wikipedia, but emotionally charged discussions about whether a news topic is WP:N notable or not, often before there is enough time for long-term coverage to be developed, is not an image we want to present to prospective editors. Whether that means NOTNEWS needs to be changed is debatable, but it is best to benefit the most readers efficiently, and ugly AfD discussions right in the face of readers aren't going to accomplish that. feminist 14:51, 29 September 2017 (UTC)
10. Support, with Option 1 as a close second choice. (I notice that the introduction includes "This might include outright removal of NOT#NEWS" as part of option 3 – I would strongly oppose that; what I'm agreeing with is "expanding our current event coverage".) Anything which receives significant coverage should be included in Wikipedia. Readers are not everything, but I think the deletion of reliably sourced content receiving high traffic is a shame when it occurs. Obviously volunteers are allowed to direct their energy anywhere they want, but I think it is suboptimal when we waste time on long AfD discussions instead of improving the article, or large efforts deleting things rather than creating them (in the specific case of well-sourced articles on recent news stories). Per the eloquent arguments of RileyBugz, Carwil, Coretheapple and feminist. — Bilorv_(talk)^(c)(e) 20:14, 29 September 2017 (UTC)
11. Support per Bilorv; similarly, Option 1 is fine as well, but there's no need to outright remove NOT#NEWS. I think a good metric for news stories - as hinted at by The Rambling Man - is "will this be interesting in 10 years time, or even 100 years time." But... actually quite a bit of seemingly transient news IS relevant, and will still matter 100 years later. There've been plenty of AfDs on content that, if it had happened in 1927, would still be a fascinating slice of life of the times - maybe even just that this was considered relevant, even if it blew over eventually. (Like... if 1927 KLM Fokker F.VIII crash was as well-built up and sourced as 2006 New York City plane crash (which was AfD'd on NOTNEWS grounds), that'd be great! SnowFire (talk) 09:26, 30 September 2017 (UTC)
12. Support WP:NOTNEWS should be removed per WP:CREEP and WP:NOTLAW. It is obviously our policy and practice to cover items in the news, including breaking news. The way in which we do this is best covered by other, existing guidelines such as WP:UNDUE, WP:N, WP:OR, WP:SUMMARY which address the issues more clearly. Andrew D. (talk) 12:56, 1 October 2017 (UTC)
13. Support per Andrew Davidson. Current events is a significant aspect of Wikipedia's mission, as recognized by the "in the news" section of the main page. Those who wish to turn this into the Britannica are blind to the realities of the way the project works. Figureofnine (talk • contribs) 15:19, 1 October 2017 (UTC)
14. Full Support.--Albin Schmitt (talk) 14:59, 2 October 2017 (UTC)
15. Support IMO Wikipedia provides an enormous public service by covering news, even (or especially) hot breaking news like Las Vegas Strip shooting. We have not historically had a problem with people putting unconfirmed or incorrect information in such articles; they are usually carefully monitored and vetted by experienced editors. My own experience is that a Wikipedia article about a current event is usually more accurate than any single news report. I'm not saying to abolish NOTNEWS - we don't and shouldn't cover everything as soon as it hits the press - but we should recognize that sometimes it is our duty to our readers to cover this kind of information in a timely fashion. --MelanieN (talk) 23:02, 2 October 2017 (UTC)
16. Support WP:NOTNEWS is generally employed to give teeth to WP:IDONTLIKEIT. The best time to find reliable sources is before link rot sets in. I have found that many articles nominated for deletion under WP:NOTNEWS still have appreciable traffic ten years later. Leaning towards supporting Andrew D.'s suggestion of abolishing WP:NOTNEWS entirely; but it certainly should be added to WP:AADP Hawkeye7 (discuss) 20:17, 3 October 2017 (UTC)
17. Support Agree with MelanieN that breaking news articles are closely monitored and poor-quality content is quickly removed. Our community does a remarkable job of sorting out verifiable facts as they become available and quickly building a high-quality article. We're not running out of space, so I don't see a reason to delete articles simply because they are old news. –dlthewave ☎ 23:00, 3 October 2017 (UTC)
18. Support If it is reliably sourced, there is no reason why we should not have an article. Verifiability concerns I can respect, some news stories are covered in a way that are guaranteed to give a distorted picture of the subject and thus leave an article that can never be accurate (e.g. BLP1E type), but for many events this is not the case. As to 'will this be important in 10 years?', who cares? If you don't want to write articles on things of no lasting importance, you don't have to --but if I want to, let me. Antrocent (♫♬) 04:24, 4 October 2017 (UTC)
19. Support as first choice – Verifiability is the reason we have notability standards. It is very easy to verify information on news items, as there is heaps of news articles about them. I do agree though, that articles made extremely quickly after a news break, articles every time Trump says something, and news reports should still be permitted as part of WP:NOTNEWS. J947^{( c ) (m)} 21:59, 7 October 2017 (UTC)
20. Support NOTNEWS is redundant with WP:N. Smooth alligator (talk) 19:57, 11 October 2017 (UTC)
21. Support Used as an excuse not to cover current events. People expect us to cover current events and we do a generally okay job at that. Of course we do not break stories but that does not mean we should not summarize notable stories. Doc James (talk · contribs · email) 02:26, 14 October 2017 (UTC)
22. Support NOTNEWS as currently implemented is detrimental to Wikipedia's mission. It is fine as written, but people act like it should overrule GNG when it comes to covering events. The best use of NOTNEWS is to balance against article notability for routine coverage of local events and against the recentism of giving undue coverage to minor events in news cycles as well as regulating Wikipedia's tone. I largely agree with Hawkeye7, and would like to add that its invocation is often about proving a point rather than supporting free knowledge. Winner 42 Talk to me! 15:29, 14 October 2017 (UTC)
23. Kind of I think we mostly hit the right place, but there are too many people making arguments that newspapers are primary sources or NOTNEWS means we shouldn't cover much of anything recent. I've seen more and more of that recently. So mostly "we are in a good place" but also "I'm worried we are pushing towards too strong of a NOTNEWS world". Hobit (talk) 04:26, 21 October 2017 (UTC)

    Can you identify any source outside Wikipedia that does not regard news reports as primary sources? Any introductory book about history aimed at high school or undergraduate students explains that they are pretty much the definition of primary sources. 86.17.222.157 (talk) 16:38, 22 October 2017 (UTC)

    Secondary sources describe, discuss, interpret, comment upon, analyze, evaluate, summarize, and process primary sources. Secondary source materials can be articles in newspapers or popular magazines, book or movie reviews, or articles found in scholarly journals that discuss or evaluate someone else's original research. An interview is a great example of a primary source. An article that summarizes a number of interviews and court documents is a clear secondary source. Hobit (talk) 22:26, 22 October 2017 (UTC)

24. First choice In my opinion events that discussed widely in world media is worthy to include in Encyclopedia. --Shrike (talk) 08:12, 23 October 2017 (UTC)
25. Second choice provided there is coverage in multiple secondary sources such as newspaper analysis rather tnan basic primary reporting Atlantic306 (talk) 20:27, 24 October 2017 (UTC)
26. First choice as there are already remedies in place for dealing with these kinds of articles, and bringing up issues about POV-pushing likely comes in violation of WP:SUSCEPTIBLE. Also, I never thought Wikinews was a good concept after briefly looking at it, and never will. ToThAc (talk) 19:50, 9 November 2017 (UTC)
27. Should be less strictly enforced or rewritten to be even clearer since we have so many editors who misuse the policy. Makes no sense to try to act like Wikipedia shouldn't cover news. Wikipedia is not a traditional encyclopedia and never will be. I mean, good luck trying to keep articles like 2017 Las Vegas Strip shooting and Harvey Weinstein sexual abuse allegations off Wikipedia. Flyer22 Reborn (talk) 19:57, 12 November 2017 (UTC)
28. Weak support. I think we should allow for creation of more current events, but clean them up a few months after the event has lapsed and we can assess lasting notability better.Icewhiz (talk) 00:10, 14 November 2017 (UTC)
29. The current approach to "newsworthiness" is broken. We get into too many pointless arguments over at WP:ITN/C for example, over what should be included, and it ends up based on editor's personal preferences, with a cite to WP:NOT#NEWS, rather than a reasoned argument based on reliable sources. Whereas in fact readers should come first. If Donald Trump is being inaugurated on a particular day, and all the newspapers worldwide are covering that with full page splashes, then it should be in our ITN section. That shouldn't even be a debate. We're not a news ticker, but we're also not the judges of the world's values.  — Amakuru (talk) 17:26, 14 November 2017 (UTC)
30. If a current event is clearly notable, getting a "first draft" done while people are actually interested is important. OF COURSE, articles should pass WP:N. But in many cases, they clearly do and NOTNEWS is used to shut down articles that people don't like, not as a as an actual concern. We should WANT Wikipedia to be up to date and current.Casprings (talk) 21:15, 18 November 2017 (UTC)
31. Abolish. This is used solely to push POVs. The whole idea of NOTNEWS was ludicrous (if not malicious) to begin with, and it contradicts GNG. It is used to delete articles solely because they may be new, controversial (WP:SUSC), and/or most of its sources are news outlets. It was never clear, and I do not think that it was ever intended to be. I'm opposed to keeping NOTNEWS in any form whatsoever. Furthermore, we must retroactively restore any articles deleted under this 'policy'.  — Mr. Guye (talk) (contribs)  04:52, 7 December 2017 (UTC)
32. Strong support in many cases Wikipedia's ability to bring facts together from multiple sources and present them in a neurtral way makes it a valuable way to consume information about new events. ChristianKl (talk) 13:30, 8 December 2017 (UTC)

Threaded discussion on NOT#NEWS

On NOTNEWS, I think that the main issue that people have with it is the notability of recent events. I think that we all agree that Wikipedia should not be written in a news style. But, we don't agree whether recent events should ever have a chance of being notable (until a week or so after) or whether we should just increase the number of sources needed for notability. RileyBugz^会話_投稿記録 18:32, 25 September 2017 (UTC)

No, notability is not the main issue. The main issue is that current events are magnets for BLP violations: even if they are notable they are also normally UNDUE and all sorts of other BLP issues, plus a massive suck on the community's time in making sure that BLP is enforced on a highly visible page and figuring out what to do with the content. TonyBallioni (talk) 20:20, 25 September 2017 (UTC)

I wouldn't necessarily eliminate notability from this. Inappropriate assessment of notability based on volume of news sources can lead to a too-narrowly defined article on a news topic that does happen to be the subject of much recent news, but where the potential for BLP violations (among other issues) may and has arisen in the past. (eg Dismissal of James Comey to me is indicative of what's been happening here). --MASEM (t) 20:28, 25 September 2017 (UTC)

Oh, I agree notability is one factor here. It is not the primary danger in my mind, though. The encyclopedia is not harmed by keeping a non-notable event around for a few months before it gets sent to AfD again and merged or deleted. The encyclopedia and real people are harmed when we can't make up our mind on BLP issues and problematic statements under BLP policy keep getting inserted or we have articles created like the first Pissgate article (which was deleted. I'm also not sure if we should even have that redirect, but thats another matter). I think we need to acknowledge that there are several factors in play here, notability being one of them, but it is not the factor that has the potential to do the most damage. TonyBallioni (talk) 20:33, 25 September 2017 (UTC)

Agreed on all points. --MASEM (t) 20:40, 25 September 2017 (UTC)

I see two problems: first, we act as if we were in competition with other sources, so there is something of a "scoop" mentality about getting the story in quickly even if it is wrong. That isn't historically how encyclopedias functioned, and I would almost suggest that we should specifically forbid writing about things so soon after the event. But second, too many people simply do not understand why news stories are published. We have to spend way too much time prying out slow-news-day and click-bait fluff, even when the article in question is years old any there's abundant evidence that nobody ever cared after that. Mangoe (talk) 22:10, 2 October 2017 (UTC)

• EEng, I know you had a list of people who had asked to be notified if there was going to be a discussion about enforcing NOTNEWS. I'm notifying you since you probably know where the conversation is. TonyBallioni (talk) 18:46, 25 September 2017 (UTC)

The ping-me list is at User_talk:EEng#Shaping_a_proposal. I'm not sure I can commit to this discussion at this time. I will say I liked someone's suggestion that if there's going to be an embargo of some kind on breaking news, the right form for it might be that a breaking-news topic shouldn't get its own standalone article for X days or weeks i.e. breaking-news content should, at first, be new content in some appropriate existing article, and only after X days/weeks should it be considered for its own article. The beauty of this is that there will typically be many eyes on the existing article, who will help keep UNDUE, BLP, and similar problems under control.Any after the X waiting period, notability for a standalone article will be much clearer. EEng 23:33, 25 September 2017 (UTC)

• I've not listed the discussion in Template:CENT yet; I wonder how the discussion would normally proceed without listing it in CENT or notifying others about this discussion. BTW, before voting, let's look at Wikipedia:WikiProject Deletion sorting/Events/archive and Wikipedia:WikiProject Deletion sorting/Sports/archive. Shall we? Most listed articles are deleted for plainly violating either notability guidelines and/or the "Wikipedia is not a newspaper" policy. Ooh... the Trump orb article is deleted... um, re-created as a redirect, actually. So are other articles. --George Ho (talk) 20:27, 25 September 2017 (UTC)
• Question - Didn't we just go through this shit? Beyond My Ken (talk) 21:29, 25 September 2017 (UTC)

• Yes we did. Coretheapple (talk) 21:39, 25 September 2017 (UTC)

• No we didn't. It is a very different question, about exactly how should NOT#NEWS be taken, not a new principle for NOT#NEWS. As the closure of the discussion put it, there is a question of exactly what NOT#NEWS means nowadays. --MASEM (t) 22:00, 25 September 2017 (UTC)

• OK, let's see how different this one becomes. Coretheapple (talk) 22:06, 25 September 2017 (UTC)

• Sort of. This conversation about our encyclopaedic treatment of breaking events was simmering below and at the surface of the RfC and surrounding discussions. Masem identified the issue three weeks ago, during the proposal of this straw poll: Whether [the RfC] closes as failed or no consensus… the disconnect related to the core NOT#NEWS policy is still evident and should be addressed…. I would characterise Masem as passionate about NOTNEWS, and in implementing performing the RfC closure I felt certain this proposed poll would go forward; perhaps that expectation affected my framing of the close. Apologies to community members sick of this topic. It's... historically contentious. Snuge purveyor (talk) 08:30, 26 September 2017 (UTC)

• One commonality with the recently concluded discussion is that the wording is problematic. Option 2 is that NOTNEWS "should be more strongly enforced" or that "En.wiki should have significantly less coverage of current events." To do that would seem to require not enforcement of the existing rules but change in the policy. So that option would appear to incorporate two separate outcomes. One could argue that NOTNEWS is already strictly enforced. Coretheapple (talk) 12:55, 26 September 2017 (UTC)

• Which is the whole point of this straw poll. the RFC even before it was closed (though the close re-affirmed what I saw) gave no clear indicator how the majority of editors felt about NOT#NEWS, with both directions having been presented. This is meant to simply determine if and by how much of a change in policy is needed, but makes no attempt to say what that could be because its impossible to know what has a likely chance of gaining consensus. --MASEM (t) 13:29, 26 September 2017 (UTC)

• But that's precisely my point. Sure some folks are going to be explicit. But when people stop by and says "yeah I'm for option 2" without saying what they want to happen, how is that to be interpreted? Option 2 provides two dramatically different outcomes - enforcement of the existing rules or changing them. If people are silent on these alternate outcomes, how do you read their minds? Coretheapple (talk) 14:13, 26 September 2017 (UTC)

• You can't, but the whole point of a straw poll is to get a quick idea of an opinion, and determine how strong the various opinions to see what type of action might be appropriate to suggest. If one option "wins" by a landfall, then there's clearly a means to consider new policy or the like towards that. If instead it just "wins" by a few percentage, I would say a massive policy change is out of the question. I do point out in the intro that results could range from adjusting existing P&G to creating new policy to eliminating some policies. --MASEM (t) 14:18, 26 September 2017 (UTC)

@Power~enwiki: The problem with Wikinews is a catch-22. It requires editors to use to fill it with news stories, and then there needs to be awareness that it exists so that people coming to WMF projects for news coverage use that instead. If no one knows about it, it's hard to draw editors to use it. If editors don't use it, it gets no visibility and people don't know about it. It's not dead-dead, articles are still created for it, but its very clear that editors and readers presently believe en.wiki is the place to find news articles, and Wikinews is basically a ghost town. --MASEM (t) 13:34, 26 September 2017 (UTC)

Oftentimes I see an AfD on a recently created article on a recent event (say, a terrorist attack) with people saying things to the effect "keep, meets GNG" and "delete, NOTNEWS". Typically these end up as "keep", I am not sure if there is a general feeling on how such cases should be treated. Jo-Jo Eumerus (talk, contributions) 14:41, 27 September 2017 (UTC)

Jo-Jo Eumerus, Masem - is there a way to know how much time a reader spends at an article or do our stats provide only clicks? There's also no way to know why page views increase or what information our readers are hoping to find. I'm of the mind that a news story breaks, and readers come to WP for validation based on NPOV. If all we're doing is reporting allegations cited to the NYTimes, WaPo, etc. then we're turning our project into another bait/click news source. ^{Atsme📞📧} 12:43, 2 November 2017 (UTC)

@Atsme: One rough way to count how interesting people find an article is to compare the amount of hits other pages linked from said article get. That works only if the article is getting a lot of attention - if it's uninteresting people won't click on its links and then the other pages don't see many more clicks, if it is interesting the other pages will receive a lot more. Jo-Jo Eumerus (talk, contributions) 16:06, 2 November 2017 (UTC)

Excuse my lack of knowledge in this area but other than manually pulling up page stats for each article in What links here (via the tool in the sidebar menu), is there an auto-calculation somewhere? I looked at Page information, then Page view statistics - does Wikilink checker contribute anything? ^{Atsme📞📧} 19:21, 2 November 2017 (UTC)

2017 Las Vegas Strip shooting and List of terrorist incidents in October 2017(and its kindred) are examples of the problems we have with editors seeing something in the media and adding it immediately. Every rumour gets added as soon as it hits the web, no matter how dodgy the source. Doug Weller talk 15:45, 2 October 2017 (UTC)

Are RS and BLP insufficient to deal with this problem? If they are not being sufficiently enforced, the problem won't be solved by adding another policy that won't be enforced. Gamaliel (talk) 17:23, 2 October 2017 (UTC)

Technically between the existing NOT#NEWS, RS, and BLP, these should be kept in check (that's the whole point of WP:RECENTISM, but as sometimes breaking news articles get swayed on being "popularity contests" in the number of voices supporting something outweigh those arguing for established policy, to which part of that is something I'd attributed to a lax treatment of NOT#NEWS by long-time editors, and admins. There are a lot of other factors though that contribute to this too, it's not just a NOT#NEWS issue, but better adherence to NOT#NEWS would help alot. --MASEM (t) 17:44, 2 October 2017 (UTC)

It's also the speed at which these articles are edited. I haven't looked but I know that the right wing media had a different, innocent (but liberal) subject named as the shooter and his name was the main name on Google for a few hours. I hope it didn't get into any of our articles. These articles also attract a lot of new editors who don't have a clue and are quite happy to argue. Doug Weller talk 17:50, 2 October 2017 (UTC)

@MelanieN: for a while yesterday Facebook and Google were presenting a conspiracy theory naming someone uninvolved as the shooter. I haven't checked to see if this poor guy's name ever go into our article (but I will), but such instant responses to breaking stories, particularly when often done by new editors who don't know about reliable sources or care at times, can be damaging. Doug Weller talk 08:00, 3 October 2017 (UTC)

@Doug Weller: Please do check; I'd like to know. I will be very surprised if our systems failed that badly. In the time I have been involved with the article, we have been concerned with whether and how to report that false news incident as false news; it seems finally to have found a home under "Social media". My hunch is that if anyone had inserted that story at the time, it would have been removed almost instantly as poorly sourced. --MelanieN (talk) 14:29, 3 October 2017 (UTC)

@MelanieN: I used Wikiblame and went back through 1500 edits, but it looks as though it wasn't added. If it had been added, I wouldn't be surprised if a copy of that version showed up somewhere else. Doug Weller talk 14:34, 3 October 2017 (UTC)

Thanks for checking. I have actually been very impressed with what a good job we do on breaking news stories like this. To me it proves again the saying, "the trouble with Wikipedia is that it only works in practice. In theory, it can never work." --MelanieN (talk) 14:45, 3 October 2017 (UTC)

P.S. I looked all through the talk page archives and can't find that anyone ever even proposed adding that false report. There were a few other wild conspiracy theories proposed at the talk page, but they were quickly shut down and never got into the article. The only false thing that went into the article is that some people, before the article was protected, inserted "Muslim" or something similar to describe the shooter. Removed almost instantly. We have strong systems. --MelanieN (talk) 14:54, 3 October 2017 (UTC)

User:Doug Weller, the first item in the list you cite is the Marseille stabbing. In fact Fr police are at present very equivocal as to whether this incident is terrorist or not French interior minister Gérard Collomb said: “It might be a terrorist act, but at this point we can’t say so with certainty”. Of course no such uncertainty is mentioned in 'our' list, and the likelihood of it being even reported widely if the story has an anti-climatic end (if, for example it was simply a conventional murder), so any update probably won't be incorporated in our article or list unless it is 'dramatic'. I believe this identifies the real danger of 'news' articles, which are the 'peripheral stories' and list entries with too few watchers, rather than the big events like 'Las Vegas'. A particularly silly example is recorded here, where WP on two seperate lists recorded a terrorist plot that simply never existed. Failing to 'update' is the norm, rather than the exception in this topic area, with dozens of articles that I know of ending "police arrested X suspects", (but how many were ever convicted of anything?) . I don't know what we do about it however. Pincrete (talk) 13:06, 8 October 2017 (UTC)

Hell, that was User:Gianluigi02 that I recently blocked for 72 hours for similar edits. Doug Weller talk 13:31, 8 October 2017 (UTC)

Another editor put it into another list, where it stayed even longer (20-ish months) and many other editors cheerfully reinstated (and sometimes embellished) it on the first list, claiming it to be "well-sourced". The list article was so full of SYNTH and over-statement that even I did not notice it for a long time. It was a NOTNEWS argument that finally killed it. Pincrete (talk) 14:43, 8 October 2017 (UTC)

Some points to reply to in regards to @Gamaliel and @Fuzheado in their !votes about forum shopping and Wikinews. First, as forum shopping, this is not the question that was asked at WT:NOT about NOT#NEWS. That was a very specific proposal about how much commentary should be in news articles, which during the course of it, it became clear the bigger "issue" is how NOT#NEWS is to be treated, period. That was a point made in the closure of that previous discussion , so it is not forum shopping because this is asking a very different, and much larger question about our relationship to breaking news, in the first place. Second, the Wikinews issue, I fully agree that Wikinews is dead, the problem is, there was nothing in place that designed en.wiki as the defacto place that news would go with Wikinews being dead. There's nothing that says WMF needs a sister site that handles news. Maybe it might seem to be practice to have news on WP, but that's a change from NOT#NEWS that never appeared to have been processed through by consensus. The point here is thus to establish if that practice does have any type of consensus, and update policies and guidelines as needed. If the practice is fine, then that needs to be written into policies and guidelines; if not, then we need to fix how it is being practiced. --MASEM (t) 19:57, 2 October 2017 (UTC)

@Masem and Gamaliel: - Regarding this: "there was nothing in place that designed en.wiki as the defacto place that news would go with Wikinews being dead." Er, you don't need a formal pact, agreement or interface on where one starts and one begins. In fact, Wikipedia existed for years before Wikinews ever came to the scene, and there was never anything formal about Wikinews does X to the exclusion of Y on Wikipedia, nor should there be. Regarding what you said, "that's a change from NOT#NEWS that never appeared to have been processed through by consensus." The practice is the consensus! It has been this way for years and years, and only now are you surfacing this as some sort of illegitimate mode of operation that needs an overhaul when there is no real desire to do so. Frankly, it's puzzling and borderline patronizing when we as a community have done very well with creating articles as news breaks and serve the public interest. Forget the old notions of "this bin is news" and "this bin in history" and never the two shall be comingled. The great thing about Wikipedia is that it blends these two seamlessly in a way we've never done before, so why make that harsh and artificial distinction? Nobody puts Wikipedia in a corner! -- Fuzheado | Talk 20:52, 2 October 2017 (UTC)

Just because it's practice doesn't make it a community consensus, particularly if the change is slow and not immediately obvious. I agree that we probably have been running current event articles for several years that would seem to go against the rub of NOT#NEWS, but this wasn't an issue until events of the last couple of years, principally driven by the US election, which has created a unique political and ideological battleground in the world as a whole that never had been present prior to this, and eventually filters down into en.wiki. The "practice" of rapidly pushing current news, while seemingly okay before, has created an endless stream of behavioral problems, much less issues with how news intersects with key content policies, because of what current news typically ends up being. That's not sustainable, unless we either establish the practice as having consensus, or adjusting our policies and guideline to reflect which way the community would want to see this. There is no question that some news today can eventually become an encyclopedic topic tomorrow, and thus it makes no sense to wholly chase off news coverage on WP. But to what level we cover breaking news and migrate that into an encyclopedic topic is a question that really needs to be answered in this current political and ideological environment. --MASEM (t) 21:59, 2 October 2017 (UTC)

• I think the most useful thing would be a straw poll or survey trying to identify what -- if any - kinds of content should be excluded under NOTNEWS. I think a lot of people will say "nothing -- if there is an RS it comes into WP". I am curious if we can get consensus around anything. If we can, then NOTNEWS should be narrowed to that. If we cannot find anything then NOTNEWS should be removed from NOT. But the first step is to try to get people to identify what they think NOTNEWS does exclude. Nobody replied at my query at NOT; how do you feel about trying that here Masem? Jytdog (talk) 05:28, 3 October 2017 (UTC)

  @Jytdog: We can get specific consensus for certain limitations; this particular change simply hasn't been made to WP:NOTNEWS. --Izno (talk) 12:39, 3 October 2017 (UTC)

You have more confidence than I do that we will find anything left of this policy in what editors actually do. There is a very strong strain of "it is in a source so we include it" out there. Jytdog (talk) 12:42, 3 October 2017 (UTC)

I totally agree with that statement, and now wondering if the changes need to occur in Notability first. POV or possibly even agendas/advocacy gets in the way of independent critical thinking that is compliant with NPOV. Encyclopedic value (EV) is easily measured by WP:FP but how do we determine an article's EV for inclusion? The simple answer is the number of times RS write about it. Therein a big part of the problem lies. ^{Atsme📞📧} 12:50, 2 November 2017 (UTC)

Neither Wikipedia nor Wikinews are set up to work well with current events and breaking news stories. Here's why:

1. Immediacy. I used to contribute at WikiNews but found it immensely frustrating, because the whole thing is so very slow. You can write a couple of unreferenced sentences on Wikipedia, tag it as a stub, and publish it immediately. Straight away it's visible to readers, and you can continue working on it - making it longer, adding sources and images etc, as can other editors. This is the way other news outlets work - they publish a "breaking news" article that's usually just a sentence or two, then add content as more information becomes available. But not Wikinews. On Wikinews there's no concept of breaking news, of the importance of publishing first and editing later. Every single Wikinews article has to be reviewed by somebody else before it's published. With so few users on that project, it can be several days before your "breaking" news article is even looked at. News by definition has to be "new". It's crazy that we can publish something to Wikipedia with immediate effect but not to our newspaper sister project.
2. Original research is allowed and very much encouraged on Wikinews, but obviously not on Wikipedia (and rightly so). To work as a news source, original research is important. The eyewitness report, the first-hand account, the reporter on the ground, the direct interview - these often make for the best news articles but they have no place in an encyclopaedia. This is something Wikinews gets right and that Wikipedia would fail at if the decision was made to replace Wikinews with Wikipedia's current events section.
3. Editorials and opinion pieces don't stand a chance with the NPOV policies that exist on both sites. NPOV is vital for every encyclopaedia article and is rightly one of the central pillars of Wikipedia policy. We want Wikimedia sites to be neutral and welcoming to all, so we don't want our newspaper project to have a strong overall political leaning as many regular newspapers do. But opinion pieces and reporter blogs are now an important feature of just about every news source out there, and the key is to allow points of view to be represented in them provided they are balanced (i.e. one piece "for", another "against", resulting in overall balance) and clearly marked as an opinion piece and not a news article.
4. Edit conflicts. The Wikimedia platform is great for collaboration over a long time, but bearing in mind the importance of immediacy mentioned above, big breaking news stories really need to allow multiple editors to work on the article in real time, in the same way as a shared Google Drive document/spreadsheet. That's a massive technical hurdle to overcome, and currently some way off. (See mw:Parser_2011/Real-time_collaboration and mw:Extension:TogetherJS)

For me, the biggest barrier by far is that first one. WikiNews needs to change the way it works dramatically and fundamentally if it is to succeed. But if Wikinews does the job it's meant to do, we can then look at strengthening the NOT:NEWS policy here on Wikipedia. Meanwhile we have a mess on our hands and I don't think any of the proposals in this RfC will remedy that. WaggersTALK 14:13, 4 October 2017 (UTC)

• My 2¢ Based on my admittedly anecdotal experiences at AfD and elsewhere I'd say that NOTNEWS is so widely ignored that it is about a half step away from being WP:HISTORICAL. I don't like it. Point in fact I am appalled by it. But it is what it is. Maybe it's time to just admit that it's on life support and talk about pulling the plug. -Ad Orientem (talk) 21:59, 11 October 2017 (UTC)
  • That's part of why I opted for this straw poll to see if that was a viable option. The current stances suggest otherwise (edging to make NOT#NEWS enforcement stronger presently), meaning we should be looking to find ways to fix issues with how AFD handles new news articles without being bitey to newcomers, among other things. A lot of AFDs I see on news events comes down to editors thinking "lots of immediate coverage" == "notable topic", despite both NOT#NEWS and WP:N saying otherwise, and AFDs are unfortunately easy to swing by sheer numbers of !votes. --MASEM (t) 22:20, 11 October 2017 (UTC)
    • The !votes so far are as close to a lack of consensus as I have ever seen. The far more lopsided sentiments in the NOT discussion were termed "no consensus" long before the close, so I find your "edging" characterization interesting in light of that. Coretheapple (talk) 23:06, 11 October 2017 (UTC)
      • Might have missed some, but taking out duplicates and second choices it appears to be a dead heat, 38 in favor of strengthening, 38 keeping same or weakening, at the present time. Figureofnine (talk • contribs) 17:41, 14 October 2017 (UTC)

Idea

• Comment. Its pretty obvious that the issue is not with NOTNEWS, but with the total failure of the Wikinews project to attract a sustainable editor base. Rather than whatever you hope to achieve here in this RfC, you should consider the bigger picture. For example a simple change to the Wikimedia software to add a namespace called News: could deal with the problem and revitalise Wikinews at once, some news items worthy of long term inclusion in the enclyopedia would be simply moved to mainspace via a method similar to AfC, news items would exist on wikipedia as a kind of draft, but still be indexable and accessible. Simultaneously dealing with the NOTNEWS and Wikinews issues in one action. To avoid issues with removing Wikinews, all news articles would be editable via Wikinews (which would still exist as a portal) and on Wikipedia, where we would no longer have to fret over which news stories will be relevant later on. This whole system is more in line with Wikipedias 'lagging behind' verifiability policy, and avoids splitting editors into unsustainable over-localised communities. Α Guy into Books™ § (Message) -  21:30, 25 September 2017 (UTC)

Aguyintobooks, the article creation has become a total mess as is. Right now, we have 1500+ articles pending review via AfC. A bunch of articles, including some articles about current events, get deleted from Wikipedia because they fail to meet encyclopedic standards. Currently, we have WP:ACTRIAL running for six months. Merging Wikinews into Wikipedia would make matters worse. We would expect more articles created and then deleted for failing to meet the standards. Also, what about 20+ other Wikinews language sites? This year, Dutch Wikinews is reopened. --George Ho (talk) 00:59, 26 September 2017 (UTC)

No. Replicating the AfC model is not the way forward. The future of how we handle new content in in limbo pending ACTRIAL/the followup RfC, and the current policy fights over the draft space are popping up all over my watchlist, and I never seek out doing anything with the draft space. Making current events AfC/Drafts 2.0 is a battleground waiting to happen. TonyBallioni (talk) 01:10, 26 September 2017 (UTC)

I also thought of this as a possible solution, but yeah there are too many problems with similar processes currently for it to be feasible. Maybe if we ever get AfC and drafts and all that stuff figured out, this could be a good idea. ansh666 09:00, 26 September 2017 (UTC)

@Aguyintobooks: The problem here and at Wikinews is the same problem: there seem to be a lot of people who want to wave around policies to try to interfere with free-licensed work about news. If you do work on Wikinews, it is very likely to be thrown away - that's why no one does. Even if successful, it will be a locked snapshot, not a comprehensive review of a phenomenon. Now I don't know the motivation of any specific person, but I think on average we should look at the myriad legal embattlements and legislative setbacks of news aggregators to see that the ever-shrinking media industry might be exerting some push-back against its competitors. I mean, if the encyclopedias had done the same back in 2001, Britannica would be making as much money as Microsoft! But on Wikipedia there is a never-ending stream of editors from other topics who just wade in and start editing without regard that we're not supposed to be able to put current events in context. This raw ignorance is our foremost strength. Wnt (talk) 18:47, 27 September 2017 (UTC)

• The statement "the total failure of the Wikinews project to attract a sustainable editor base..." is entirely true. The reason for that is that the entrenched editor base is mostly lazy and opposed to helping new users integrate their contributions in a useful manner; rather they see it as their duty to eradicate all new user contribitions that don't meet the extremely strict standards that have taken years of experience to develop. It's the expectation that all brand new Wikipedia users are born fully formed like Athena from the head of Zeus, and that any new contribution which is not already FA-quality is to be deleted within seconds of its creation with little to no explanation of the problem, and absolutely no attempt to improve such substandard contributions. What kills new user retention is primarily a culture that treats them all as enemies until they have proven themselves not to be. --Jayron32 14:11, 26 September 2017 (UTC)

  Mea culpa. Misunderstood the OP's original point. My response makes no sense. Carry on. --Jayron32 15:09, 26 September 2017 (UTC)

Your point is perfectly valid though, having ~2250 pages of policy is one thing, expecting new users to understand it all is another.  --- Α Guy Into Books™ § (Message) -  21:27, 26 September 2017 (UTC)

• Truer words were never spoken. I have been here for 3 years, and I feel as though I have just begun to get a grip on the morass of policy in the handful of areas where I most commonly edit. To me, editing feels like a deadly video game were partisan gangs try to kill you as you wander through an uncharted swamp without a compass trying to avoid the arcane booby-traps that editors set to get you banned.E.M.Gregory (talk) 21:38, 26 September 2017 (UTC)

  Large systems always grow in procedure as the numbers grow. At some point communication breaks down and a policy is made to hold the signal. Jo-Jo Eumerus (talk, contributions) 21:58, 26 September 2017 (UTC)

• I think E.M.Gregory's point in his !vote about current events articles being an entry point for new editors is a good one. People have an interest in current events, readers like them, and they add value. A win-win all around. Coretheapple (talk) 22:30, 26 September 2017 (UTC)
  • We definitely do not want to be too restrictive on new editors, and we want to encourage them to participate, but at the same time, current event articles can be touchy, and already a large subset of them fall under the post-1923 US politics Arbcom DS, where it's not the best for a novice to be making unsure edits compared to other pages. There's definitely a balance needed. --MASEM (t) 23:13, 26 September 2017 (UTC)
    • You mean, post-1932, right? George Ho (talk) 23:14, 26 September 2017 (UTC)

Realistically all events were current at some point, and there are going to be more people interested in an event at the time it happens than some years afterwards, but a balance has to be struck somewhere, especially for events where the available information changes rapidly.  --- Α Guy Into Books™ § (Message) -  23:17, 26 September 2017 (UTC)

Everything was current at one point or another but the online media quickly shares stories saying essentially the same thing; you never had that in 1932. Editors need to understand that journalists report one thing, and we, who are not journalists (some like to believe they are, however), have a different criteria for our content. If we were more patient, most current events would reveal their importance in a few weeks and speculation would be replaced by verified facts. Perhaps we can move current events to a draft space for a week or two and then access if it established a historic or societal importance after that time has passed.TheGracefulSlick (talk) 00:32, 27 September 2017 (UTC)

"most current events would reveal their importance in a few weeks" A few weeks? I think you mean a few years. Secondary source analysis (see WP:ANALYSIS) has to take place well-removed from the event. We shouldn't be writing about any presidential administration until they're a dozen years out of office. I could argue we shouldn't have any entries about living people, at all. It's still too early to write about the Gulf War, let alone the Invasion of Iraq in 2003. But of course, Wikipedia exists as a playground for wannabe writers to shout out their narrative. Wikipedia's crass inclusive approach to keep the donations coming in results in shoddy entries written by fanboys and cranks. Had we emphasized article quality over article quantity we might have built our gamification around writing responsible entries rather than the vomiting of words into multiple overlapping pages. Chris Troutman (talk) 01:09, 27 September 2017 (UTC)

Chris troutman I actually agree with you more than you probably realize. In fact, I really need your perspective for some of the articles I nominate for deletion! I was trying to bring about some sort of middle ground: no consensus will exist, instructing us to wait years for notability. Many editors like putting their "I'm a journalist" caps on and writing an often inaccurate load of drivel we are forced to call an "encyclopedic article". Unless more editors like you participate at AfD, I doubt we can initiate a serious movement to rid Wikipedia of news.TheGracefulSlick (talk) 02:15, 27 September 2017 (UTC)

@TheGracefulSlick: I'm your huckleberry, but I've hurt my AfD record by tilting at these windmills to prevent Wikipedia from being a free-for-all. I recognize Wikipedia isn't a serious endeavor, despite my desire for it to be that. Chris Troutman (talk) 02:26, 27 September 2017 (UTC)

Whether or not our articles are "inaccurate loads of drivel" (I think not), at least we still have copy editors and can spell, which is more than can be said for most of the professional media outlets that people have to resort to for far less comprehensive, partisan, and hard-to-find reviews of news events if they can't find them on Wikipedia. Wnt (talk) 10:44, 29 September 2017 (UTC)

Realistically whether our news articles are relevant depends greatly on the quality of our editor base, there is the inherent problem that news is closer to original research and harder to verify than an encyclopedic topic, and the issues presented by the accepted facts changing is always an issue. and the obvious issue that wikinews is always behind everyone else (as it is based on other news, which for news is really a disadvantage. Not a disadvantage faced by wikipedia. The strongest core concept of wikinews is that is a neutral aggregate of content, A wikinews article should always be more complete than any other single piece of coverage. A den jentyl ettien avel dysklyver 11:32, 29 September 2017 (UTC)

• I want to emphasize the points made above by User:Carwil and User:Feminist. Feminist is correct to flag the negative impact on the project viscous attacks on new editors get socked with at AfDs on big news stories. And Carwil is surely correct that energy is better put into improving articles at the moment when they are drawing attention, to which I want to add that I, personally, go to WP as an efficient way to get up to speed on a breaking political or culture wars firestorm. I expect the article to exist. And it often leads me to go take a moment to expand one of our many old, sad, neglected articles on a neighborhood, institution, think tank, publication, or individual involved in the breaking news event.E.M.Gregory (talk) 18:24, 29 September 2017 (UTC)
  • Excellent points. postdlf (talk) 22:39, 5 October 2017 (UTC)

Some observations

I'm going to note a few common themes that I'm seeing in the !votes here as they come - I'm not suggesting they are immediately actionable, that they have consensus, or the like, but they open up some reason and points of discussion why we're at this impasse on NOT#NEWS and how to proceed on that. --MASEM (t) 15:02, 29 September 2017 (UTC)

1. Handling of current events articles at AFD is an issue - both from those there !voting "Keep per GNG" (asking larger questions about news reports, bursts of news, and notability per NEVENT/GNG) and those !voting "Delete per NOT#NEWS" (more reflecting of how strong NOT#NEWS should be enforced). There should be a middle ground recognizing that DEADLINE is also a factor in addition to NOT#NEWS. --MASEM (t) 15:02, 29 September 2017 (UTC)

I see no such common theme at present. Coretheapple (talk) 18:46, 29 September 2017 (UTC)

Concur with Coretheapple; no consensus has appeared. Moreover, the problem with WP:DEADLINE is the reality that creating articles when a significant event is breaking news is among the few proven techniques to overcome our endemic shortage of editors, because when an EVENT is notable enough to support an article, many editors show up and usually create pretty solid articles before the news cycle ends. There is all the time in the world to delete, but the existence of fingers willing to build the article evaporates rapidly.E.M.Gregory (talk) 19:40, 29 September 2017 (UTC)

I question whether 'breaking news' articles actually recruit new editors. Certainly they attract IP's and a few 'newbies' (some of both are quick learners and great to have around, and some are huge liabilities) to edit on that particular article, but is there any reason to believe that news articles actually recruit long term editors? This has not been my experience. Pincrete (talk) 11:01, 1 October 2017 (UTC)

Agreed, but just to elaborate a little, the comments here should speak for themselves and editors should not be providing an ongoing play-by-play that purports to summarize the positions of multiple editors at any given point in time. Even if so far there was an actual consensus or overwhelming view on a particular subject,, that would have to be viewed in conjunction with whatever else is said. Let's not fragment and tilt the discussion, please. Coretheapple (talk) 20:24, 29 September 2017 (UTC)

My only point here is that regardless of the straw poll, there is a valid concern of problems of how NOT#NEWS is handled (for or against) at AFD on recent news articles. I can't tell you how that has to be fixed, yet, but the AFD angle (whether we are talking retention of an article or deletion) is an issue of concern. --MASEM (t) 18:01, 2 October 2017 (UTC)

News articles on current events are primary sources, and primary sources have little weight in a notability (AFD) discussion. If the only reason to keep the article is 'its been in the news recently' then it lacks notability and so should be deleted. Only in death does duty end (talk) 12:06, 3 October 2017 (UTC)

I think that there is a certain consensus for a stricter application of NOTNEWS as it applies to BLP violations. RileyBugz^会話_投稿記録 19:07, 30 September 2017 (UTC)

Seems more logical to apply BLP to BLP violations. Figureofnine (talk • contribs) 16:04, 2 October 2017 (UTC)

There are frequently times where good RSes do publish things that we would normally consider BLP violations, like the rush to name suspects. What happens far too often is editors will see that name in good RSes, and believe it is appropriate to add right away to the articles, as they don't see it as a BLP violation (because RSes back the naming). But for us, that generally is the case until some time has passed to know how much importance the suspect's name is to the situation, as per BLP. BLP is not 100% consistent which is where situations like this come up. --MASEM (t) 18:01, 2 October 2017 (UTC)

Yes, it's terrible how the media refers to [name redacted] as the shooter in the Las Vegas massacre. Figureofnine (talk • contribs) 23:39, 2 October 2017 (UTC)

That's not where the problem arises. I distinctly remember during Sandy Hook Elementary School shooting that in the first few hours, the name of the brother of the actual shooter was named as the shooter in several RSes, only because his ID was on the shooter's body. Obviously it all got sorted out in the end, but if we had included his name at the time, that would have been a major BLP problem. That's an example of a situation with BLP is at odds with massive coverage by RS. Even with the LV shooting, I know several of the early articles this morning named a possible accomplice to the shootings, but that was quickly ruled out by police. Properly, our article does not mention this person at all despite that RSes still mentioning the name. Furthermore, and this is more a sign of the times, but there were tons of false stories that floated around on major RSes, some intentionally false. (I could also point out the situation with Tom Petty today as yet another example of this). BLP is supposed to prevent issues with that, and in the long-term it does, but in the short term there has to be more awareness of why we have NOT#NEWS towards this end to help protect BLP from misinformation. --MASEM (t) 23:57, 2 October 2017 (UTC)

I just don't see the need for yet another layer of rules, based upon the supposition that RSs may not "get it right" now but may "get it right" down the road. That would put articles in a straitjacket, and would be subject to all kinds of abuse and conflict. Our BLP rules are already strict and more than sufficient. What you describe as a "problem" is simply a fact of life, not just for current events articles but all articles, even articles on ancient subjects, as the RS sources shift and change in their perspective. All we do is reflect the RS sources. That does not create a BLP issue a all, but rather is a mirror to the reality of the sourcing. Figureofnine (talk • contribs) 00:32, 3 October 2017 (UTC)

It's not a "fact of life" that we needed (or for that matter still need) 240 posts so far in the Tom Petty article. It's only a fact of WP, apparently, that people cannot be trusted to get caught up in the what will prove to be a passing and unimportant episode of misinformation. Mangoe (talk) 02:01, 3 October 2017 (UTC)

Another datapoint showing that BLP is not sufficient to deal with NOT#NEWS violations: Harvey Weinstein sexual misconduct allegations - an article based only on that allegations were made and some of those aftereffects on Weinstein, but going into far too much detail for what is yet to be even a legal charge against him. --MASEM (t) 13:43, 15 October 2017 (UTC)

Yet another datapoint is how swiftly your AfD of the article was closed as a speedy keep, without a single supporting !vote. You seem to have a narrow view of NOTNEWS that is extreme and out of step with the community. Figureofnine (talk • contribs) 16:22, 15 October 2017 (UTC)

I feel the need for written clarification of BLP as it applies to current events. Many unproductive discussions and edit wars could be avoided if we had something that explicitly stated "we do not refer to something as a murder/homicide/assault/attack until there is a conviction." This may already be covered by the existing policy, but it should be written in a way that can't easily be misinterpreted or misrepresented. –dlthewave ☎ 22:53, 2 October 2017 (UTC)

• Unfortunately, none of this is new. for a non-recent example of an article where NOTNEWS was totally ignored... see University of Florida Taser incident (of "Don't tase me, bro" fame.) Worth reading the discussions that took place about why that article should be kept. 17:54, 2 October 2017 (UTC)

• There is a lot of inappropriate assumption that media are necessarily reliable as a class, when the reality is that in the extreme short-term, they really aren't that reliable. It is typical of breaking news stories that initial reports aren't reliable: they're usually somewhat right, but they are often revised more or less drastically in light of later reports. I see no reason why something calling itself an encyclopedia should be chasing this. Reliability of accounts is something that is achieved over the long term, when the matter has been sifted through. Quick response media really cannot be taken to be that reliable until others judge them so, and that takes retrospection and therefore time. Mangoe (talk) 20:40, 3 October 2017 (UTC)

• I'd suggest that a more important need, one that no one has addressed, is to update "news" articles after the initial hubub has died down and the pageviews and editor interest has ebbed. That is an issue not just for articles on recent events but for all kinds of articles. "Orphaned" and neglected articles, sometimes bearing maintenance tags for years, are a serious problem in the project. Coretheapple (talk) 14:05, 6 October 2017 (UTC)
  • It is a serious issue, which is why a possible solution is to create a space that is on en.wiki and comes up in search results so that current news is there, and excepted to follow all content policies, but serves as a means to incubate news content such that if it doesn't turn out notable once the initial coverage has died down, it can be deleted, merged, or otherwise placed in context of something else. (Obviously notable stories can be brought into mainspace without question). It's like a Draft: space, but it needs to be more integrated with mainspace, and should have more formal processes to remove content that hasn't yet been transitioned to mainspace so they don't linger. Whether this has to be an explicit "News:" space, or management of article tags, I don't know, but it would meet both sides of the matter. (And there's a lot of cavaets, this by no means a formal proposal for this). --MASEM (t) 14:24, 6 October 2017 (UTC)
    • No, that would be like trying to light a campfire with napalm. A simple problem requiring a simple solution: greater energy expended after an article has lost its high visibility status. Not just news articles but, for instance, articles on corporations that have undergone scandal. BP comes to mind. Coretheapple (talk) 16:38, 6 October 2017 (UTC)
      • No. Better to head off the crap to begin with - and it is crap always filled with the personal predilictions of the Wikipedia editors because there are no sources who have reflected and weighed - just the personal prejudices of Wikipedians - and it is absolutely no public service to be a news aggregator. Alanscottwalker (talk) 18:36, 6 October 2017 (UTC)
        • I'm not seeing crap, I'm seeing articles in need of updating. BP isn't crap. 2014 East Harlem gas explosion isn't crap, and neither is filled with personal predilictions. Coretheapple (talk) 21:50, 6 October 2017 (UTC)
      • Not really. Once an article has lost its high visibility status in the news, we should be reviewing it per NEVENT/GNG for notability and appropriateness. Some will clearly stay, some should be merged, and few should be deleted. That achieves the same thing of then being able to tag those that are key to gain more eyes to improve, resummarize, and work in later sources after the initial burst of news, rather than let them stagnate. New developments on existing articles are less a problem, save for far far too much proseline in many cases, since we're not questioning the basic notability of the original topic. --MASEM (t) 22:28, 6 October 2017 (UTC)
        • @Masem: Can you cite any examples of current event articles which were deleted after they were no longer current events? Coretheapple (talk) 13:30, 19 October 2017 (UTC)
          • Wikipedia:Articles for deletion/2009 Fox News – White House controversy Wikipedia:Articles for deletion/2014 Romania helicopter crash Wikipedia:Articles for deletion/2014 Norfolk helicopter crash Wikipedia:Articles for deletion/2011 India–Pakistan border incident Wikipedia:Articles for deletion/Kosovo–Serbia January 2017 train incident (merged but effectively same for the question at hand) - This is just scanning the first few pages of hits in the AFD archives. Obviously there's also some keeps and some retained by no consensus, but there are definitely deletions. --MASEM (t) 13:43, 19 October 2017 (UTC)
            • @Masem: I'm referring to articles on current events that were deleted when they were no longer current. All except the India-Pakistan one were deleted shortly after they were created, and the India-Pakistan one appears to have reappeared as 2011 India–Pakistan border skirmish. Coretheapple (talk) 14:58, 19 October 2017 (UTC)
              • Wikipedia:Articles for deletion/Power Shortage in Japan 2012, Wikipedia:Articles for deletion/2017 collapse of Route 4 bridge in Israel, Wikipedia:Articles for deletion/2014 SOCATA TBM crash (2nd nomination), Wikipedia:Articles for deletion/Nicolas Estemar stabbing spree. And that's just a portion of a list I'm scanning through.
              • I will say that it is reasonable to allow articles on current events to be created and given some time to demonstrate notability per both NEVENT and GNG (with obvious hoaxes or BLP violations speedily removed), but we should still have some checkpoint a few weeks after creation of such that these articles are either approved with presumed notability (if not sooner if it is obvious) or sent to AFD to be deleted. --MASEM (t) 15:20, 19 October 2017 (UTC)
                • I'd say overall we have a pretty good record at creating articles that last and deleting ones that don't seem very significant in retrospect. And when dubious articles are created that aren't deleted... so what? I wanted Richard Matt deleted. The community emphatically disagreed. The article remains, and I fail to see excessive harm from that, except to my ego. And no, I'm not going to nom it for deletion again, for the simple reason that in fact he has gotten so much notoriety since his demise he probably does warrant an article. Coretheapple (talk) 17:02, 19 October 2017 (UTC)
                  • The problem is that when you start reviewing some of the other AFDs on events, (and I don't have any in front of me, this is from recollection earlier today) is that there is a strong pattern of numerous !votes going "Keep, lots of international coverage" and the closer clearly following that majority despite opposing !votes that point out that bot NOT#NEWS, WP:N, and WP:NEVENT point out that a burst of coverage is not sufficient to keep a news event. In other words, its a compound problem of editors not understanding existing policy/guidelines and admins not properly evaluating !votes under NOT#NEWS concerns. And then further, when this articles are kept, and the AFD is a mere memory, no one spends the time to convert these from newspaper, on-the-spot reporting to something that is more appropriate for permanence. (The whole problem with reaction sections is one part of this). Compare Watergate scandal or Lewinsky scandal (pre-WP days) to United States diplomatic cables leak (written as the events went along). Even something like Boston Marathon bombing is still showing the training wheels it needed to build out when the event was happening, and that's an article with a lot of editing activity still. And these are the high profile news articles; it's the smaller ones that have less of an impact that are typically even worse and are frequently overlooked. There is definitely a place for allowing editors to start current events articles, but we need to have a better process to make sure that these are going to end up being quality articles at some point. There's no one solution to this, but based only on the poll, there probably needs to be something changed, though not drastically. --MASEM (t) 00:42, 20 October 2017 (UTC)
                    • "Based only on the poll." We're back to that again? It is indeed funny how the lopsided !vote in the NOTNEWS page you interpreted as "no consensus" whereas this even-steven one you claim to be a mandate for something . There is no consensus here to do anything, with half the !voters wanting less or the same enforcement of Notnews and half wanting stronger. As for all those articles that need improvement, sofixem. Coretheapple (talk) 12:55, 20 October 2017 (UTC)

Not News and Reliable Sources conflict. The strictest definition of "not news" will mean that even if there are reliable sources, inclusion should be banned because Wikipedia is not news.

I believe the solution that reliable sources is a higher priority than not news. This is because if there is something truly historic but it doesn't have reliable sources, it cannot be put into Wikipedia. However, something that has reliable sources, even if we think it is news, is more worthy.

The biggest problem is that there is no editorial board and professionally trained editor in chief to make decisions. That is the wikipedia way. AGrandeFan (talk) 20:42, 11 October 2017 (UTC)

Why is it important to have articles on breaking news?

This is, to me, the undiscussed question. From my perspective, I can see three reasons not to have such articles:

1. They create notability issues because of the implication that anything that has been published about at all is notable, which our principles have said isn't true. Getting rid of them is laborious.
2. They present accuracy issues because the real sources are unstable (and often enough unreliable) and because the tendency is for the article to freeze at the point where someone lost interest. One has to hope that someone comes back after things quiet down and potential sources have had a chance to take a longer view and sort out all the various reports (which, BTW, could on some level be taken as primary sources, when it comes to that), but often enough it doesn't happen. It's pretty common that, in the long run, The World decides the event was unimportant and doesn't get around to sorting it out beyond ignoring it.
3. They present readers with a choice: who should your read for breaking news: the news, or us? Shouldn't the answer be, "well, not us, for now"?

I see some sentiment of "well, it gets sorted out in the end." I don't think that's true, but even to the degree that it does, aren't we performing a disservice until it does? Mangoe (talk) 16:46, 12 October 2017 (UTC)

A few reasons I'd offer:

• We are instinctively drawn to "citizen journalism", which is enabled by the MediaWiki platform, the WMF, and the general polices we have. It also fits well within WP due to inter-linking and a cadre of templates and tools to help build these articles. The "citizen journalism" is more in effect in the last several years due to several factors (read: Trump) that has drawn more eyes and more potential breaking news topics.
• We have had several successful breaking news articles developed on WP without much fuss and with high quality from the start, and WMF has praised that approach in the past, validating it. However, these examples all tend to be examples of major disasters (earthquakes, international terrorist attacks, etc.) where most of the reporting is objective so editors aren't fighting or pushing specific content. However, applying this same model to other stories (eg anything dealing with the Russia interference in the US elections) tends to cause more problems. There is a place for certain types of breaking news stories, but not every breaking news story needs to be in WP the moment. Most breaking should wait until we know we're into the long-tail of the story, and thus can have a more holistic view of the event to write for WP to know if it is appropriately notable, and how to structure the article and views and opinions associated with it, as to avoid OR and POV with trying to cover from the instant start.
• Where citizen journalism was to be established by the WMF, Wikinews, has failed, but the drive to write and read breaking news articles persists. It has migrated to en.wiki based on the previous models where breaking news has worked well, but when all breaking news is reported on en.wiki, it seems to cause no end to problems. We could admit we are now WikiNews and adopt policies to reflect that, but from the current state of this straw poll, that's not a likely solution. --MASEM (t) 17:06, 12 October 2017 (UTC)

• Regarding #1: I think that the objection here is poorly framed, in that the implication that is not merely that anything published is notable, it is that anything which is published in sufficient depth in the proper sources is suitable for inclusion in Wikipedia in some manner. Requirements of sourcing are universal, and don't "go away" merely because sufficient time has not passed since the event. The fact that something happened yesterday or last year or 1,000 years ago does not change the existence or non-existence of sufficient source text. If the source text is sufficient, what more is needed?
• Regarding #2: This is an issue which is true for all sources, and for all text across Wikipedia. It isn't unique to new news. Accuracy at Wikipedia is only as good as interest, and we have thousands of articles on old subjects which are based on outdated, inaccurate, or outright false information right now. That is not restricted to new stories. It's not a good thing, mind you, but it's also not a problem unique to recent events, which means setting some artificial time limit on when a topic becomes "eligible" for Wikipedia wouldn't fix the problem.

--Jayron32 17:00, 13 October 2017 (UTC)

Then there's Stonehenge, old and forgotten, but continually in the news since the dawn of the Internet. Authorities now believe the perpetrators "ate food from Scotland". Wikipedia neither confirms nor denies these latest allegations. InedibleHulk (talk) 02:49, October 23, 2017 (UTC)

When we do it well, we do it really well. Sources of breaking news are not merely cited, they are in-line attributed "The town sheriff was reported on CNN as saying it was almost certainly the work of werewolves." Meanwhile we often find news outlets are quoting each other and rumour as fact.

All the best: Rich Farmbrough, 22:36, 16 October 2017 (UTC).

• It's hugely important to have articles on breaking news because WP is neutral, comprehensive, and not a source of clickbait. Much breaking news in the MSM is simply cut-and-paste press release come-ons with red banners and articles that say nothing. When I see a headline at a media giant's website or an aggregator site, I may click there first or not, but I will definitely go to wikipedia if the topic is anything more than gossip. Since material can always be deleted, there's no harm done when a policy-compliant article's created. μηδείς (talk) 20:35, 25 November 2017 (UTC)

Food for thought

It seems to me the point of NOTNEWS is to weed out overly detailed summaries of events. Some events can only be described by such, and the litmus test appears to be that if that's what it takes to elevate an event to Wikipedia-style coverage, it's not worthy of inclusion here. To be frank, the policy seems fine to me, but then, what do I know? I won't add it above because I feel like there's something missing here, something I don't quite have the time to wade through the discussion to see. I think NOTNEWS also transcends merely creating new articles for things, as it also dictates what we add to articles we already have. Such articles' subjects have already been vetted to be describable on a more notable, more general level where it's more about impact than merely, "This happened." What we must think of when we add something to Wikipedia, especially concerning the tense sociopolitical climate of the last few years, is whether anyone outside of our sphere would care. Would someone in Uganda care about Trump's latest gaffe? After awhile, are a certain person's gaffes even worthy of tracking, or are they simply the noise that person makes as they walk by? Especially with the rise of social media and, sigh, Twitter, meme-ifying things has reached critical mass to the point that we must ask what even makes a meme anymore. Things that trend don't always deserve to trend, and wouldn't trend again once the event in question was over. If the world has largely moved on, if the world doesn't care about the specifics, then we should move on too, and we shouldn't care either. And if we choose to cover newsworthy-but-questionably-Wikipedia-worthy things, we have to tie it into a greater whole. Understandably, anytime a President goofs, it reflects on his character, so one could make the argument that whatever seemingly boneheaded thing Trump just did deserves to be covered, even mocked, by Wikipedia. But we must also ask whether such a mistake, if it were even one to start with, reflects on his Presidential qualities. Would he be any better at his job if he were never prone to such a thing? That's difficult to answer, but now I'm rambling, so my point there is that smaller, less-notable things have to truly, and of course verifiably, be tied into a greater whole that adds to the depth of our coverage of a subject. Article length or the cumulative data of coverage by a particular WikiProject are not enough to assert such depth. Therefore, my understanding is that this policy is intended to help us trim the fat off topics, or fight harder to prove why we should care and how the fat is actually a valuable part of the cut of meat, so to speak. Zeke, the Mad Horrorist ^{(Speak quickly)} _{(Follow my trail)} 03:51, 13 October 2017 (UTC)

The litmus test is "are there independent and actually secondary sources that indicate this is notable and accurate?" The sourcing is key. The assumption "newspapers/news site are secondary" is false when it comes to breaking-news reportage, which is just regurgitation of speculation, hearsay, and unverified witness claims – it is primary sourcing.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  16:10, 6 November 2017 (UTC)

That's disagreeable on some accords, as news sources are usually written in a second-person perspective, even if the news is breaking. One if the problems with WP:NOTNEWS is that users often forget that articles about events covered mainly by news sources are usually required to be written encyclopedically anyways; there are too many remedies in place at this moment to fix most, if not all, of the problems presented with articles about current events. ToThAc (talk) 19:40, 9 November 2017 (UTC)

That comment just demonstrates the basic problem here, which is that the vast majority of Wikipedia editors seem not to understand the distinction between primary and secondary sources, which has no connection to whether a source is written in a second-person perspective. We should simply stick to the core principal that this is an encyclopedia based on secondary sources, which do not, by any definition in any introductory history text book, include breaking news reports. The problem would then solve itself. 86.17.222.157 (talk) 16:51, 24 November 2017 (UTC)

Narrowing down the poll

It seems that there might be a consensus to increase how BLP applies to recent events. Therefore, I propose a poll to see whether people would be ok with having BLP modified so that the suspects in incidents in which people were killed would not be put in to article until 3 or 4 days after the incident. If you would support this, but with some other time limit, please say so and please say what time limit. RileyBugz^会話_投稿記録 20:19, 5 October 2017 (UTC)

• Oppose. Moratoriums like this are arbitrary and impossible to enforce, and of little to no relation to the confidence we have in the validity of what reliable sources report. With some events, the facts are immediately clear and never in dispute, with others years may go by without official consensus on who did what. We should follow the sources in either case and discuss our concerns in relation to each topic. postdlf (talk) 20:31, 5 October 2017 (UTC)
• Huh? There is no consensus to do anything at this point except continue this pointless exercise. Coretheapple (talk) 21:29, 5 October 2017 (UTC)*
• Oppose. I agree that BLP should be modified but it would be best to tie it to an event such as an arrest or criminal conviction. I've seen countless discussions over whether or not we can identify a suspect who has been charged but not yet convicted. We should answer that question and apply it consistently everywhere instead of discussing it repeatedly on Talk pages. –dlthewave ☎ 22:12, 5 October 2017 (UTC)
• Huh? I second User:Coretheapple in seeing no consensus here.E.M.Gregory (talk) 23:18, 23 October 2017 (UTC)
• Yeah, there is no consensus here. Hobit (talk) 23:53, 25 October 2017 (UTC)
• Nope. Agreed with all of the above comments, including dlthewave's clarification.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  16:11, 6 November 2017 (UTC)
• Oppose Beyond My Ken (talk) 01:12, 9 November 2017 (UTC)

Summary of NOT#NEWS straw poll

With the current state of this poll at the time of this writing, there's clearly no mandate to alter policy or guidelines for the handling of recent event articles. NOT#NEWS does remain a valid policy, but it has to be metered appropriately - we shouldn't be using NOT#NEWS to bite newbies or those attempting to write on breaking news stories, but at the same time, it has strength that should be used to review such articles after time has past to frame the event and content better to be more encyclopedic, and in some cases, deleting those events that turned out to be non-events.

That said, combined with the previous RFC at WT:NOT that led to this, I think the next most immediate and appropriate step is to develop a guideline that is the equivalent of Writing about Fiction, but tailored towards writing news stories. Some of the facets of this guiieline would be:

• How to interpret the nature of sources (primary, secondary; enduring coverage versus a burst of coverage, etc.) in relationship to the GNG and NEVENT, as to determine if an event article should be created or how to handle that in deletion discussions.
• That articles on breaking events may be more proseline-ish and documenting details as the event starts, but are expected to transition to more holistic/overarching coverage of the event once the event has settled down. We do want to encourage editors to create articles on current events but also encourage those same editors to shape the article over time rather than just move on to the next current event.
• That editors should keep in mind WP:RECENTISM when determining what facts and views to include in a breaking-event article to avoid the short-term bias that can arise in the current news cycle, and that sometimes it is better to wait for dust to settle to try to figure out the opinions of the event per UNDUE/WEIGHT.

There's likely other factors that can be included in this too. None of these points would introduce new ideas or conflict with the existing P&G as written, only to provide more clarity and a type of MOS for news articles, so that newer editors that are drawn to writing about current events have some type of guide to work from. It at least addresses many points raised by those !voting options #2 and #1 above without ignoring the concerns many of the option #3 !voters raised.

There could be other steps - again, revival of Wikinews still seems to be an option on the table, but that's going to take a lot more discussion and thought. It would be best to see if providing more comprehensive guidance on writing about current events would help address concerns raised before moving onto other steps. --MASEM (t) 17:18, 15 November 2017 (UTC)

"...we shouldn't be using NOT#NEWS to bite newbies or those attempting to write on breaking news stories, but at the same time, it has strength that should be used to review such articles after time has past to frame the event and content better to be more encyclopedic, and in some cases, deleting those events that turned out to be non-events." Well said. postdlf (talk) 18:09, 15 November 2017 (UTC)

• Sorry but there is absolutely no consensus for any kind of guideline, and to be frank an effort by one of the activists in this area to write a guideline is going to be still more useless drama and time suck. Why not just drop it? Coretheapple (talk) 03:14, 22 November 2017 (UTC)

• Agree with Core. The community has come to no consensus on the application of this section of the policy, which is essential to the creation of a guideline. Figureofnine (talk • contribs) 15:34, 24 November 2017 (UTC)
  • As there is no change to the current policy of NOT#NEWS, we still at at odds. There is zero issue with creating a guideline in similar style to WP:WAF that is based on all existing policy and guidelines and without introducing anything otherwise enforcable to help new editors (a key point of this poll) to write better articles on news. The lack of such guidance (in a centralized manner) is a key issue from this poll and such a guideline (meant to mirror existing p&g) does no harm nor meant to impact this poll result. --MASEM (t) 16:17, 24 November 2017 (UTC)
    • Nobody said anything about the lack of a guideline. That's something you just dreamed up yourself to keep the pot boiling. Time drop the WP:STICK. Figureofnine (talk • contribs) 15:08, 25 November 2017 (UTC)

Here we go again

The article linked above is typical of the way Wikipedia is treated as a breaking news site rather than an encyclopedia. At 16:38 today a possible terrorist incident was reported to the police, and at 17:30 a Wikipedia article was created about it. At 17:43 the Metropolitan Police tweeted, "To date police have not located any trace of any suspects, evidence of shots fired or casualties" and at 18:08, "Our response on #OxfordStreet has now been stood down." Is this the sort of thing we should be encouraging in an encyclopedia? 86.17.222.157 (talk) 18:28, 24 November 2017 (UTC)

I see that the Wikipedia article was speedily deleted just after I posted here. For reference it was about this. 86.17.222.157 (talk) 18:42, 24 November 2017 (UTC)

If this discussion is going to continue, can an admin please move this discussion onto a sub-page, or archive some of the earlier failed proposals? power~enwiki (π, ν) 20:48, 25 November 2017 (UTC)

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.

Should Wikipedians be allowed to use community granted tools in exchange for money?

Recently we had an OTRS "volunteer" lose their access to the tool here. User:KDS4444 is a well known long term paid editor.

This raises the question:

• Should OTRS volunteers be allowed to request money from people sending in question to OTRS?
• Should editors at AfC be able to request money for passing / accepting an article at AfC?
• Should admins be allowed to bill for undeleting an article / use of admin tools?
• Etc

Or should we have policies clearly disallowing this. Doc James (talk · contribs · email) 16:18, 1 November 2017 (UTC)

• Seems like WP:INVOLVED and WP:COI capture most of the spirit of this, and would be the places to amend if clarification is needed. — xaosflux ^Talk 16:40, 1 November 2017 (UTC)
  • That we have had OTRS agents using the system to make money proves that when it comes to paid editing "spirit" is often not enough. We need it to be black and white. Doc James (talk · contribs · email) 17:46, 1 November 2017 (UTC)
• Obviously not, that's corruption. If our existing policies do not effectively forbid it then we should have news ones that do - perhaps amendments to WP:INVOLVED and WP:COI, as xaosflux says. Boing! said Zebedee (talk) 16:58, 1 November 2017 (UTC)
• I think that an explicit prohibition of such would be a good idea. In government and business that is considered to be bribery or a kickback scheme. And since Wikipedia conflates tools with related powers/positions, we should note that it's not just mis-use of tools, it's mis-use of powers/position. North8000 (talk) 17:10, 1 November 2017 (UTC)
• The admin aspect was already discussed and rejected as a standalone item. Jo-Jo Eumerus (talk, contributions) 17:11, 1 November 2017 (UTC)
  • One difference is that the proposal there was "No administrator may accept payment to edit articles or to perform any administrative function on Wikipedia" (my emphasis). This suggestion is only about prohibiting paid use of tools. Boing! said Zebedee (talk) 17:17, 1 November 2017 (UTC)
  • And after reading a bit through it, the discussion is essentially about whether admins should be prohibited from paid editing. Boing! said Zebedee (talk) 17:32, 1 November 2017 (UTC)
• Making rules that are impossible to enforce is...problematic. Honest people lose, liars win. As someone who has never gotten a dime for editing Wikipedia, I can only suggest (mostly facetiously) that all editors be required to give WMF regular copies of all bank statements. Or quarantine all editors on a desert island with internet access. What a nightmare this all is. If I had to guess, I’d say that at least 10% of political edits at Wikipedia are financed by somebody. Anythingyouwant (talk) 17:51, 1 November 2017 (UTC)
  • Locking your door does not prevent 100% of break-in, that does not make it useless. Wikipedia improves when good faith editors overall have a greater ability to contribute that bad faith ones. Rules help achieve a positive balance. Google Knol failed as it filled full of advertising. Doc James (talk · contribs · email) 18:06, 1 November 2017 (UTC)
• Obviously the answer is 'No!' It's odd that the questions even have to be raised, but the goal therein is to make it absolutely clear, because paid editors - some of whom are notorious for their Wikilawyering - will use any 'omission' in the policies to practice their art. Kudpung กุดผึ้ง (talk) 18:01, 1 November 2017 (UTC)
• Okay so with respect to wording, what do people thing about adding at WP:COI:

"No one may use admin tools or accepting articles at WP:AfC in exchange for a financial reward. Additionally the WP:OTRS system may no be used for recruiting clients or payment."

Doc James (talk · contribs · email) 17:55, 1 November 2017 (UTC)

• In order to shine a light on this, if we read current policies as prohibiting administrators, editors or OTRS volunteers, from taking actions while at risk of being thought to be paid for those actions, then no funded academic, employee, Wikimedian in residence, should ever take any action using their editing/sysop/access rights which could in any way benefit their employer or funder, even the scenario often used in the past by certain employees that though they are employed, they were editing in their volunteer time... It might actually be better to highlight case studies where administrators that were in a paid contract or had a grant, did legitimately use the tools as they were the best person at that time to do so, while correctly handling their declaration of interest in a transparent way. There may be cases where conflicts of loyalty have nothing to do with money, and those may also make for useful case studies. --Fæ (talk) 17:55, 1 November 2017 (UTC)
  • If you were a WiR at say the NIH and you protected all NIH related article without explicit consensus to do so, that would still be a problem. Doc James (talk · contribs · email) 18:08, 1 November 2017 (UTC)
  • (edit conflict) Some good points there, which were raised in that other discussion (I've just finished reading it). While we should certainly want to prohibit 'corrupt' use of tools, it's hard to word policy so it does not adversely affect honest use as in examples like those. Boing! said Zebedee (talk) 18:11, 1 November 2017 (UTC)
• I fully support this. Nick (talk) 18:08, 1 November 2017 (UTC)
• Anything other than "regular" editing (as can be done by an auto-confirmed user; a name-space restriction has too many edge cases to be reasonable) in exchange for payment should be strictly prohibited. The corner cases (what if a professor who is an admin does admin work on university time) can be figured out by lawyers, the spirit should be clear. power~enwiki (π, ν) 18:10, 1 November 2017 (UTC)
• I also support making policy clear against potential corruption. I don't have a problem with Doc James formulation; it's of course always possible to improve it in the future for precision, i.e. WMF legal suggestions welcome... —PaleoNeonate – 19:36, 1 November 2017 (UTC)
• My view: No editor should be allowed to use permissions given through community input or tools that allow editors to work in an "official" capacity (OTRS, etc.) to edit for pay. As long as a draft meets all normal AfC requirements, I'm ok with editors being paid for their work. Admins can be paid for their work as long as they don't use their admin toolbox in the process. Of course, all paid contributions should be declared. — Gestrid (talk) 08:24, 2 November 2017 (UTC)
• OTRS is outside of our domain, and it seems the question has already been answered. However, I'm not aware of any instance of an admin using tools for pay - I'd be hard pressed to think of a situation where that would occur. Do we need to prohibit a practice that doesn't happen? As to AfC, that is a common job request, so it does represent something that happens. My knowledge of AfC is limited, though - do you need special tools in order to approve an article from AfC? I didn't think that was the case, but maybe I'm mistaken. - Bilby (talk) 08:49, 2 November 2017 (UTC)

Bilby, Of course you're not aware of any instance of an admin using tools for pay. I'm not. Nobody is. They are not exactly going to yell it from the rooftops if they are. It's a very plausible concern and I can think of several situations where it might occur. Kudpung กุดผึ้ง (talk) 11:23, 2 November 2017 (UTC)

Hard pressed to think of a situation where an admin using tools for pay would occur? How about undeleting an article that had been deleted, unblocking a blocked paid editor, protecting an article at a favoured revision? It took me about 30 seconds to think of those three. Boing! said Zebedee (talk) 11:37, 2 November 2017 (UTC)

No, I'm hard pressed to think of a situation where an admin is accepting money to undelete an article. The advantages are clear, but I haven't seen an admin use the tools for pay, and I'm hard pressed to picture that situation arising. - Bilby (talk) 11:41, 2 November 2017 (UTC)

Several years ago, a Russian Wikipedia admin was desysopped for using admin tools to promote paid editing.--Ymblanter (talk) 17:24, 2 November 2017 (UTC)

One instance, several years ago, on a different language Wikipedia. Ok. But has this ever happened here? I agree with the principal - no admin should use the tools in return for pay - and if the community wants that to be clearly stated I'm a bit concerned re WP:BUREAU, but it doesn't bother me overly much. I do worry about "the sky is falling" policy changes, though, and pushing through changes without evidence of there being a need for them. - Bilby (talk)

Did you ever hear, (until now), that somebody was actively using OTRS to recruit clients and solicit payments?Winged Blades of Godric^{On leave} 10:21, 4 November 2017 (UTC)

I can testify for my own part, that this case was particularly egregious and lost me a bit of sleep thinking about it. I realize it may not look that way from our end, but from the perspective of our readers, OTRS is in few ways a higher position of trust than being an admin on wiki. From the perspective of readers, they're getting an email from Wikipedia, and not a message from some anonymous user on Wikipedia. I think per discussion below, I'm personally leaning toward favoring something along the lines of No one may misuse a position of community trust... and perhaps specify that this can include user rights, various coordinator positions, and off wiki access like OTRS and ACC. GMG^talk 10:29, 4 November 2017 (UTC)

The problem with OTRS was a serious one, but that should be handled through OTRS. As I said, I'm not opposed to this on principal. My concern is that I'm seeing a lot of rhetoric and exaggerated claims about paid editing which are leading us to take more extreme steps, but not a lot of data to back up the specific claims. Given that I can't imagine any current admin accepting money to use the admin tools, the change in policy is moot, and I'll support a well worded proposal. It doesn't prevent anyone from doing anything that they were going to do. But I do want to be cautious of inventing problems that don't exist. - Bilby (talk) 11:10, 4 November 2017 (UTC)

Well, at least to my mind, the admin bit isn't really special here. It's just one of many rights or positions, of which there are many requiring both more and less community trust, and more or less oversight. And this isn't an expectation of admins; it's an expectation of everyone, and admins are an everyone. The key common factor there is the trust, not the number of buttons. For example, autopatrolled users are trusted by the community to make acceptable quality articles that don't require community review.

Also pretty much just to my own mind, there are really two distinct types of policy formation. There's policy that attempts to create new process to deal with outstanding problems, and there's policy that simply documents widespread community practice that's already in place, but hasn't been explicitly written down anywhere. I believe this is the latter. It's already a de facto policy. When we have, and if we do find someone abusing positions of trust, we will remove them from that position. That's a fact. But we currently don't appear to have explicit, unequivocal wording that says You knew this was going to happen when you made the decision to abuse your position or access. GMG^talk 11:26, 4 November 2017 (UTC)

I understand where you are coming from - I am fully in agreement that admins should not use tools for pay, with the various normal exceptions for WiR and whatever. My caution comes from seeing what can only be described as a war between paid editors and anti-paid editors, and in that war we're giving up progressively more. Thus I need to ask, every time a new policy change is put forward, the basic three questions - is it needed, will it work, what will it cost? This one costs nothing, in that it is such a specific case that it won't have a wider impact. But it isn't needed, because we have no evidence of this ever happening on en.Wiki. Will it work? I can't see how anything can "stop" something that doesn't occur, but I think we'll find that this is going to be very hard to prove to the level where we can desysop someone if it ever does arise, and that from a practical sense we'll end up using a different justification.

In regard to other tools, though, the approach doesn't seem to be the best solution. With AFC, I think we need a clear statement that says "you cannot approve any draft in return for financial remuneration" - it isn't about the use of tools, but the act of approving a draft. Focusing on the tools is the wrong part of the equation - someone just needs to take the longer process of approving it without any special permissions to meet the policy. Similarly, if we remain worried about auto-patrolled users, we need to say that all paid articles must be created through AfC is we want a real fix. It isn't the auto-patrolled status that is the core problem, but paid articles being created in mainspace and not being independently verified - although there will be more of a cost if we make that change. - Bilby (talk) 11:49, 4 November 2017 (UTC)

Not to beat the horse into a pulp, but to focus narrowly on existing community practice and reasonable expectation of future practice:

• When we have found users abusing AfC for paid editing, we have removed their access;
• When we have found users abusing OTRS for solicitation, we have removed their access;
• If we did find someone abusing autopatrolled to avoid scrutiny of paid articles, we would remove it;
• If we did find an FA coordinator, a member of the ArbCom electoral commission, etc. abusing their position, we would remove them from it;
• If we did find a sysop doing this (as other projects have), they'd have their mop snatched so fast it would cause whiplash;

So that raises the question to me, of why we haven't taken the time to write this down, when we seem to all agree to some extent that it is the way things work, and the way they can be expected to work for the foreseeable future. GMG^talk 12:05, 4 November 2017 (UTC)

I don't understand enough about OTRS - my assumption is that it was a meta issue, not a en.WP issue, but if I'm wrong it is something to address here.

In the case of ArbCom, FA coordinators and admins, you are correct - we'd act if we found them. In general I don't really care if we wish to formalize those issues, except to note that we're formalizing something that we've never done, never had to do, and which would happen irrespective of any decision here. I'm wary of the principal of creating unnecessary changes. (I'd also note that, if policy reflects practice, in these cases we're reflecting what we believe would be practice, not what actually is, simply because it has never arisen).

With autopatrolled, yes, we would (and have) removed it. Let's put that in Wikipedia:Autopatrolled as the relevant place to discuss this and make the change. This one is far more important to me, and reflects something that we do, should do, and should formally note.

AfC is the other big issue to me - I would like to see that hole filled, as there are a lot of jobs hiring people to pass articles at AfC. But it isn't the tools that are the issue, so much as the approval. I'd like to see a more important change stating that articles cannot be approved from AfC in return for pay, as that would address the actual problem. Focusing on the tools rather than the approval is an error.

Just to be clear, my disagreement isn't with the spirit of the proposal, but with the two basic issues - I don't like creating policy changes that are not needed, and I don't care for skirting around the real issues (permissions) when we should be addressing the actual problems (approving articles for pay; creating paid articles in mainspace). - Bilby (talk) 13:03, 4 November 2017 (UTC)

Well... it seems the main difference in approaches is that you would like to wait until each individual right or position is abused, and then add a specific policy on that specific topic. (Also, BTW, OTRS is stand alone project and AFAIK the only one running media wiki that doesn't accept SULs.) To my mind, it just seems simpler to put a blanket statement on a central place, like PAID. GMG^talk 13:11, 4 November 2017 (UTC)

Not quite. I have two main differences. a) I'd like to address the real problem at AfC of approving articles for pay, rather than tackling the secondary (and mostly irrelevant) issue of use of permissions. b) I don't think we would need to change in policy even in the unlikely chance that the problems with FAC coordinators, admins or ArbCom members arose, because we would solve it without a change in policy. In that situation, I don't like creating policy changes to address remote issues that have never arisen and wouldn't need a policy change if they ever did arise.

I'm sure we'll end up with a blanket statement at paid. And WP won't end as a result. But I wish this energy went into changes that would have an impact or would address the real problems. - Bilby (talk) 13:22, 4 November 2017 (UTC)

That's part of my concern though, that if we have a blanket statement, we have one arguably time wasting discussion. If we do it piece meal, we end up with separate recurring discussions for each individual piece. GMG^talk 13:49, 4 November 2017 (UTC)

I'm sorry, I think I've been explaining things badly. If we have this discussion and agree to make this change to WP:PAID - which it is likely we will if we can get the wording right - it won't make any difference to how we respond to the main cases you raise: admins, FaC coordinators and ArbCom members. It may not do any harm, but it won't change the response, make it more or less likely that the problem will arise, or make things any easier if the situation ever appears.

In regard to this change and AfC, based on what I was told below, all the paid editor needs to do is not use any advanced permissions to pass something through. They can either argue that use of the helper script is not an advanced user right, or they simply don't use the script and do it the long way. That's because the AfC problem is not about permissions, but about actions. So if we make this change, we will still need to have another discussion to address the real problem.

In the situation of auto-patrolled users, the change I'd most like to see isn't a ruling that paid editors can't create pages in mainspace if auto-patrolled, but a rule that says that paid editors cannot create pages in mainspace. That second one seems more valuable to me, and will also involve a separate discussion.

Anyway, this is not of much value, because we're having the discussion however I may feel about it. :) Which is fine. But I've been arguing against paid editors for many years now, and what I'd most like to see is discussion around actions which will address the core issues without harming the project. This discussion has the advantage of not harming WP, but it retains the disadvantage of not addressing the problems that matter. - Bilby (talk) 14:19, 4 November 2017 (UTC)

Well, part of my concern is once the issue of the paid OTRS agent was raised, it took several days for access to be removed. Even after the evidence was damning, it didn't seem like anyone wanted to unilaterally pull the trigger. Yes, it's technically a separate jurisdiction, but for English agents, it's pretty much the same cops on the beat. (I don't know of specific instances where autopatrolled has been removed for paid editing, but I'd be interested to.) This is the kind of thing that is to be expected where sysops, ideally cautious by nature, are in fairly uncharted territory as far as the letter of the law.

As to AfC, that and the issue of non-user right positions (coordinators, etc), are the reasons for my focus on emphasizing "positions of trust" and not just user rights. From a lower level implementation standpoint, if there is a project wide policy in place to that effect, project or right specific policies can probably for the most part be boldly added, and simply point to the main. Something along the lines of:

No user may use positions of community trust in order to solicit or accept payment for activities which have a direct and foreseeable impact on Wikipedia. This includes advanced user rights for which individual vetting and permission granting is required, positions of authority elected or appointed by the community, and system access on or off wiki not normally available to all users.

I think something like that would fairly well cover everything, including OTRS and AfC. GMG^talk 15:57, 4 November 2017 (UTC)

GreenMeansGo: to your question, the same OTRS agent Doc James mentioned above voluntarily relinquished their autopatrolled flag after I suggested it to them when the issue was first raised. We have no policy as to when to revoke user permissions in cases like this, and as a recent ArbCom case pointed out, the removal of user permissions is one of the most controversial things an admin can do.

Re: your proposed wording, I think I like it. I might also add something such as ...impact on Wikipedia; or use such a position to take actions on behalf of a client. for clarity. TonyBallioni (talk) 16:05, 4 November 2017 (UTC)

My issue with raising OTRS here is not that it hasn't proven to be an issue, but that my understanding is that OTRS policy is managed at meta, so I assumed that a change in that policy in regard to paid editors has to be presented and discussed there. If this is not the case I have no problems with agreeing to the policy change here, but I had always assumed that OTRS policy is outside of our immediate control.

I still need to return to my issue with the AfC problem. I do not see permissions or "positions of trust" as the primary concern, based on what I've been told. What I think we need is not the change being discussed here, but a clear and unambiguous change to Wikipedia:WikiProject Articles for creation that states that you are not permitted to approve an article where you have a COI, and in particular you are not permitted to approve an article in return for remuneration. It isn't about positions of trust or advanced permissions, but simply who can and cannot approve an article. - Bilby (talk) 16:28, 4 November 2017 (UTC)

Well, my thought was that AfC would be covered under system access on or off wiki not normally available to all users. It's true that en.wiki can't actually enforce anything at OTRS. But I think we can probably still say that someone abusing OTRS to make changes to en.wiki is exactly half in en.wiki jurisdiction, and we can still say that we don't approve of it.

Also, I'm fine with Tony's suggested addition. And I think the absence of policy on when to remove these rights is part of the problem, and part of why sysops are rightfully hesitant to do so. GMG^talk 17:00, 4 November 2017 (UTC)

---

• • Yeah, AFC Reviewers need access to a helper-script, designed for the purpose, that heavily eases the process/workflow.It may be noted though, that all auto-confirmed editors have the right to move articles from draft space into mainspace or that any body could choose to follow a tedious manual reviewing process, that existed before the development of the script.Winged Blades of Godric^{On leave} 09:08, 2 November 2017 (UTC)
    • In that case, there are no special permissions needed for AfC? Just optional access to a helper script that is open to any autoconfirmed editor? - Bilby (talk) 10:08, 2 November 2017 (UTC)
      • Manually reviewing articles is sufficiently tedious so as to be prohibitive for most users. It is a de facto user right. GMG^talk 10:27, 2 November 2017 (UTC)
      • Echo Timothy.In a very strict sense, AFC is not a right.But, in my wiki-life, I have neither seen someone evading the script-access-barrier by manually reviewing the submissions nor someone who is moving other author's AfC draft(s) to mainspace without using the script.Winged Blades of Godric^{On leave} 10:45, 2 November 2017 (UTC)
        • I guess what I'm wondering is if you need special community-granted permission to use the tool. Is this the case? Or an anyone use the tool? - Bilby (talk) 11:41, 2 November 2017 (UTC)
          • AfC works similarly to rights granted at PERM, but at a different venue. All you need is to convince one sysop that you're competent. The major differences are 1) it doesn't automatically come with the admin kit, although theoretically any admin could grant it to themselves, similar maybe to the way some things work with stewards (unless I'm mistaken), 2) it's not technically required for reviewing, but it's a bit like saying you don't technically need access to the elevator to get to the top of the Eiffel Tower. GMG^talk 11:49, 2 November 2017 (UTC)
• There was "consensus for some language on this issue" last time and it is still a good idea, so support. Alanscottwalker (talk) 10:57, 2 November 2017 (UTC)
• Regarding Doc J's wording, if it is to be used, it may be simpler and more effective to say No one may use advanced user rights.... I have a hard time imagining a scenario where any right couldn't potentially be abused, which is why they're restricted. In fact, with ACTRIAL in effect, it could be easily argued that creating a paid article outright, instead of going through AfC is itself a type of abuse of auto-confirmed.

For rights with a greater potential for damage (e.g., sysop, AfC, page mover, AWB), and especially for those which have a comparatively limited amount of public oversight (e.g., OTRS, CU, OS)... Well... until very recently I should have thought that this actually didn't need to be spelled out at all, and that anyone with enough sense to use them would have had enough sense to assume this as a matter of course. But since the laundry list of rights and the myriad ways they could be abused is so lengthy, probably best to spell out the principle, and let the community decide the specifics, For example, is it an abuse of auto-patrolled if an editor doesn't unreview their own paid article creation? I don't know that we've ever needed to answer that question, but we might at some point. GMG^talk 10:59, 2 November 2017 (UTC)

Actually, after thinking my way through a hot shower:

1. It may be better to say No one may use abuse advanced user rights...
2. I realize most autopatrolled users probably can't unreview their own article in the first place, because they probably don't have NPP. Which adds another layer of hypothetical problems.
3. It's not entirely clear that pieces of the admin kit that non-admins may also have should be on the one hand, specially covered for sysops, or on the other, specially exempted for non-sysops. GMG^talk 11:10, 2 November 2017 (UTC)

• No to allow use of "community granted tools in exchange for money" - for all the obvious reasons. Yes to policies that disallow it.^{Atsme📞📧} 11:56, 2 November 2017 (UTC)
• An even more perverse variant of this problem crops up periodically at AFC. An author/submitter of a declined (or deleted) draft is contacted off-wiki by someone who claims they will approve (or undelete) the page for payment. This practice of holding a page (draft or mainspace article) to ransom has been condemned as a form of extortion. There is a standing request that all such incidents be reported to WMF Legal. Roger (Dodger67) (talk) 12:07, 2 November 2017 (UTC)
• NO - No one should be paid this way. This smacks of bribery. ←Baseball Bugs ^{What's up, Doc?} carrots→ 12:15, 2 November 2017 (UTC)
• No- this is a horrible idea. Reyk _YO! 12:21, 2 November 2017 (UTC)
• I'd like to be clear that the question here is quite different from "Can an editor simultaneously be a paid editor and have access to certain user rights, so long as they do not overlap those roles?" ~ Rob₁₃^Talk 14:12, 2 November 2017 (UTC)
  • I'd planned on commenting on this today and it was closed before I could. Rob makes a good point, and I think it is worth clarifying if there are circumstances when being paid is incompatible with a role: the only thing I feel somewhat strongly about in this regard as an absolute no is the autopatrolled flag since it's impossible to turn off for only paid articles. Other areas I do think need clearer guidelines as well, and I think this is a first step in the direction of setting up those guidelines. Obviously this is a nuanced topic where there are strong opinions on both sides by the community, and I think further discussion (if not on this question then on other questions) is needed. TonyBallioni (talk) 14:24, 2 November 2017 (UTC)
  • (+1) to Rob's queries.But, primarily this discussion has in itself stemmed from an overlap.I have requested CPower678 to vacate their close.Winged Blades of Godric^{On leave} 14:40, 2 November 2017 (UTC)
    • The close is fine, mostly because the question as posed was wrong. The question is "should volunteers in roles of trust be allowed to use their tools for money?" The answer is a snow no, which is obvious. There is quite a separate question of whether volunteers can both hold roles of trust and separately be paid. For instance, should Wikipedians-in-residence be able to be admins? That is a very nuanced issue that would need a very different discussion. We can't have that discussion when it starts with such a flawed question. ~ Rob₁₃^Talk 14:59, 2 November 2017 (UTC)

At least to my mind, one of the more intuitive ways to go with this is that if you have an account with basically any userrights other than extended confirmed or autopatrolled, and you want to do disclosed paid editing, then you need to register a separate account for the sake of propriety. GMG^talk 15:11, 2 November 2017 (UTC)

As to off wiki access like OTRS, that's a blanket no from me. It can't be separated technically, since access is granted to a person, and not to an account, and it has comparatively little oversight. Probably similarly with CU since they have access to private information, possibly also ACC, and being part of ArbCom is right out. (Jesus this list gets long fast.) GMG^talk 15:14, 2 November 2017 (UTC)

(edit conflict) The WiR issue in particular is complex because while generally a wonderful program it has caused issues in the past (I think I'm thinking of one WiR who copied compatibly licensed advocacy pieces into en.wiki about 6 months back). That being said, having worked with Doc James on PAID issues several times, he typically is not referring to individuals employed by orgs that share the WMF's mission and values (the WiR program or similar), but to those who are paid to edit commercially.

This could be spelled out better, I agree, but I don't think the question is fundamentally flawed: establishing a principle that people agree on has value, even if it is only a very basic one. That gives a starting point for agreement for any future conversations on the issue, which as Rob rightly point out will be nuanced out of necessity. TonyBallioni (talk) 15:17, 2 November 2017 (UTC)

The UNESCO fellow? GMG^talk 15:20, 2 November 2017 (UTC)

That's the one I was thinking of. TonyBallioni (talk) 15:25, 2 November 2017 (UTC)

Rob, the question, flawed or not, concluded with "or should we have policies clearly disallowing this.". The close failed to address that adequately, or explain why it was overlooking it. I agree with your other sentiments, and a close thus explained would have been fine. -- Begoon 15:28, 2 November 2017 (UTC)

• No since this is open again, the answer to the question asked is clearly no. I also disagree with Rob that this is a flawed question, and think we can set out some general best practices here for the less complex cases that will make the more complex cases easier to deal with when the time comes to have conversations on those issues (call it the baby-steps approach if you want). These are the policy things I think are fairly easy to deal with:

1. No one should use a position of community trust to solicit payment for services rendered on Wikipedia.
2. No one should use any user rights or positions of trust to advocate for their clients or to make technical changes that would not otherwise be possible if they did not have the rights (i.e. an admin undeleting a page or a page mover skipping the RM process for a controversial move over a redirect, etc.)
3. Technical permissions, use of tools requiring a checklist, and positions of trust that involve new content cannot be used to evade our normal scrutiny system for new content and COI content.

I think these three principles are things most people can get behind, and can help be the policy basis for any guidelines on how to apply the principles that Doc James is asking about. There are obviously others that might be able to be agreed upon as well and questions that can be raised regarding these points, but I think they would provide a basis for future discussions on the more nuanced and complex cases. TonyBallioni (talk) 15:42, 2 November 2017 (UTC)

• Comment I've seen questions raised about whether buying access to admin capabilities is really a big deal. Yes, it is. Look at the number of admins whose talk pages are filled with begging from conflicted editors whose articles were deleted. Won't spell this out due to BEANS but the possibility for a rent-seeking admin with access to deleted revisions are obvious. Also, very few people know about this, but I've communicated privately my evidence-based concern about at least one other CU confirmed socking account that was trying to gain access in 2015 to OTRS. There are good reasons to believe the socking was undisclosed paid/advocacy editing-related as is often the case. This is a big deal since OTRS handles all kinds of private, confidential information that could lead to WP:OUTING at the very least.

If you can't tell I'm leaning very hard towards "no" on the question, but want to see some refinement of the terms before making a commitment. Behavior that even smells of rent-seeking and bureaucratic malfeasance, aka bribery, could be another piece in the puzzle that results in the end of this worthwhile project. ☆ Bri (talk) 17:35, 2 November 2017 (UTC)

• Yes? I think Anythingyouwant sort of addresses my viewpoint. There's an unmet need in the economy for moving drafts through AfC and getting images approved at OTRS. I would never want to turn either of those processes into pay-for-play and perhaps that's what the opposition is scared of. The fact is, volunteers do a poor job of meeting our various backlogs. Wikipedians edit where they find satisfaction and avoid the drudgery that's needed to keep our maintenance effort going. So long as editors divulge their payments per ToU, I don't see the problem. I don't think money is universally corrupting. I'd like to see our hard-working Wikipedians get paid for their work, and I'd love if some of our most-talented Wikipedians could make a living off of editing just as we're happy to see our favorite YouTubers be able to focus full time on their content work. Disclosure is the sunshine treatment that prevents corrupt activity. If the WMF would stop spending money on un-asked for coding projects and started on-going investigations for business promotion (among other problems) I think introducing a pay mechanism would help us refine product. I know I've enjoyed getting paid to edit; sadly there aren't many reasonable opportunities anymore. Chris Troutman (talk) 21:42, 4 November 2017 (UTC)
• Hell no and props to Doc James for raising this issue. Support a common-sense prohibition. Coretheapple (talk) 17:14, 5 November 2017 (UTC)
• NO in the strongest possible terms - This does not conform to the spirit of the encyclopedia. - Knowledgekid87 (talk) 16:19, 6 November 2017 (UTC)
• Once again, we have a proposal that would, whether intentionally or not, stop or hinder Wikimedians in Residence in their valuable work. "Should Wikipedians be allowed to use community granted tools in exchange for money?" What, like when I use my account creator status to set up accounts for attendees at an editathon I'm running, as a paid WiR, even thought it was given to me for that purpose? I mustn't move an article that one of my trainees creates? I mustn't use AWB, or rollback, or mark an edit as patrolled, in my WiR role? "No one should use a position of community trust to solicit payment for services rendered on Wikipedia." So, when I apply for a paid WiR role, I mustn't mention my experience as a Wikimedian? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:28, 24 November 2017 (UTC)

Usage of ACC right for editathons etc. and WIR does not fall under the purview of this discussion. Winged Blades ^Godric 15:05, 24 November 2017 (UTC)

• No - it seems I inadvertently said this twice; see my comments below under Kudpung's proposal. Ivanvector (^Talk/_Edits) 15:51, 4 December 2017 (UTC)

We just need acceptable wording and a place to put it

I agreed with the now retracted close. This is a "snow no" to allowing people to use positions of trust and tools for personal enrichment. There are many cases covered here, mainly at AfC, OTRS, and admins, so we need to refine the wording and place it in the right policies. I say policies in the plural because paid editors routinely ignore guidelines and because OTRS is regulated on enWiki by Wikipedia:Global rights policy, admins are regulated at WP:Admins (specifically at WP:Involved}, whereas AfC reviewing is not regulated by any policy that I know of, only by Wikipedia:WikiProject Articles for creation.

I suggest similar wording for all the above, based on User:TonyBallioni's wording just above. Once we get the wording to almost everybody's liking, then place it for an RfC at WP:GRP and WP:Admin. I'll be bold and start the discussion at Wikipedia:WikiProject Articles for creation soon myself.

Basic wording:

No editor may use a position of trust or any user rights to:

• solicit payment for services to be rendered on Wikipedia, or
• accept payment for the use of such a position or rights
  • for the benefit a client
  • for advocating for a client, or
  • to evade our normal scrutiny system for new content and COI content.

Payments and grants made by the Wikimedia Foundation or its affiliates (e.g. chapters) are excepted.

• Support as proposer. Smallbones_(smalltalk) 18:00, 2 November 2017 (UTC)

Please see AfC and the related talk page. Smallbones_(smalltalk) 18:38, 2 November 2017 (UTC)

• Support since it is based on my wording above, see my reasoning there. I would also extend this to NPP/the NPR flag as well as AfC because that is what gives a user the ability to mark a page for indexing by Google. This wording should cover that, but I did want to mention it explicitly in my support. TonyBallioni (talk) 18:40, 2 November 2017 (UTC)
• Support as initial wording, without prejudice to editing or improving as with any policy. This seems concise, reasonable, and easy to understand. Everything a policy needs to be. --Jayron32 19:04, 2 November 2017 (UTC)
• Comment How would this apply to Wikipedians in residence (i.e. people who edit on behalf of universities, libraries, and museums). I personally know someone who was paid by a museum to help write articles on 100 notable New Zealand craft artists as part of a GLAM project. It seems like the wording used here could be made to apply to that project as well. "any user rights" seems ambiguous. I am extendedconfirmed, does that count as a 'user right' in this context? Does that mean that autoconfirmed users are not allowed to use the perks of that 'user right' (i.e. creating articles) to create articles for pay? Or is this meant to only apply to user rights that are community granted (i.e. page mover, rollback). — Insertcleverphrasehere ^{(or here)} 19:53, 2 November 2017 (UTC)
  • It'd be pretty simple to deal with WiR's would create distinct accounts, which they do anyway normally, and in most cases, I would expect the accounts wouldn't have additional flags. Autoconfirmed isn't a flag but an implicit group that is determined every time a user action is attempted. Extended confirmed is a flag, but it is automatically granted, so I'd assume we'd use common sense and treat it the same as autoconfirmed. TonyBallioni (talk) 20:23, 2 November 2017 (UTC)
• Comment I agree with ICPH any paid editor (disclosed or otherwise), any wikipedian in residence that uses an autoconfirmed user right to create a page or even just to edit is in breech of this text; Wikipedia:User right is redirected to WP:User access levels and ALL user groups have right attached to them. Domdeparis (talk) 20:08, 2 November 2017 (UTC)

• Those creating articles for pay are to go through AfC. Doc James (talk · contribs · email) 20:18, 2 November 2017 (UTC)
• As I mentioned above, autoconfirmed is not a user right. It is a test that the software does automatically when any action is attempted. TonyBallioni (talk) 20:23, 2 November 2017 (UTC)

You might be right about autoconfirmed. — Insertcleverphrasehere ^{(or here)} 21:36, 2 November 2017 (UTC)

Insertcleverphrasehere: yes, this is made clearer in Special:UserRights. See yours here. It lists autoconfirmed as an implicit membership rather than a membership. Its just a software check. From the admin side of it, we can't revoke autoconfirmed status once it has been achieved (there is no tick box for it, and removing the confirmed tick box on the rare occasions that flag is granted does nothing once someone meets the software requirements). TonyBallioni (talk) 21:44, 2 November 2017 (UTC)

• Support Doc James (talk · contribs · email) 20:18, 2 November 2017 (UTC)
• I definitely support a prohibition such as this. I would suggest that the way to distinguish someone like a Wikipedian in residence etc. from what we want to prohibit, is that the prohibited conduct occurs when there is a quid pro quo in exchange for something that would not be approved if it were out in the open. --Tryptofish (talk) 20:21, 2 November 2017 (UTC)
  • Tryptofish, WiRs who have distinct accounts for their work as a WiR would be in compliance with the user permissions part of this since that role account would not have additional permissions. We do want to prohibit a WiR who is also an OTRS agent (or hell, hypothetical future arbcom member) from using that position to somehow advance the cause of the org they are being paid by just as much as we'd want to prevent those paid for commercial purposes. The WiR program is good but we also need to recognize that some of them do have a COI on advocacy issues, and that the same principles apply to them as well. I think the overwhelming majority would not abuse it, but I don't want to exempt them completely. TonyBallioni (talk) 20:29, 2 November 2017 (UTC)
    • I agree with what you say. I didn't mean to make it sound like I was saying that there should be anything special about WiR, but I see now that it sounded that way. What I meant was distinguishing acceptable from unacceptable conduct. And I think that what defines unacceptable is (i) a quid pro quo and (ii) a result that would have been opposed by the community if it had happened out in the open. --Tryptofish (talk) 20:34, 2 November 2017 (UTC)
• Comment - I don't know if this is exactly the right wording, someone can probably improve upon it, but I would suggest going with something more like No editor may use advanced user rights requiring community trust.... Auto confirmed and Extended confirmed are both user rights, but they're not really an expression of community trust, and they're not really a user right in any meaningful sense that we are talking about now. As for the rest of it, if we did have a user with advanced rights go out for WiR, I think it would be totally appropriate for them to either request their rights be temporarily removed, or register a disclosed second account, especially as it concerns auto-patrolled and sysop. I don't really see a reason why a WiR would need to be active at places like NPP or AfC anyway. GMG^talk 20:24, 2 November 2017 (UTC)

I'd support this proposed change in the wording (which I believe was the original and understood intent of the version proposed above). I propose that we amend the proposal to this new wording, and then continue the voting. — Insertcleverphrasehere ^{(or here)} 22:11, 2 November 2017 (UTC)

If we are going to change it lets just come out and add normal editing by autoconfirmed or extended confirmed users is not considered use of permissions for these purposes or something like so we don't get into quibbling as to what an advanced permission is or which ones require community trust. TonyBallioni (talk) 22:19, 2 November 2017 (UTC)

Umm... I think I actually disagree on one point. I think the purpose is kindof to be intentionally vague to some extent, and let the community decide the specifics in an actual situation. GMG^talk 22:30, 2 November 2017 (UTC)

Not all forms of advanced editing privileges requiring community trust are backed by user rights. I wouldn't want FAC coordinators accepting money to get commissioned articles on the Main Page, for instance. MER-C 12:57, 3 November 2017 (UTC)

Ah ha! Now this is actually a very good point indeed! There are actually quite a bit of coordinator type positions that have nothing to do with a user right in the software but could be just a easily used improperly and in many cases with greater effect. This should probably be covered here somehow. GMG^talk 14:12, 3 November 2017 (UTC)

• Oppose for now. I'm 100% in support of the sentiment here, but I still think the wording is a little vague. For instance, last year I spent some time in a paid WIR position. I registered a separate account, and made it clear that I would not be using any of my admin/functionary access for anything related to my work as a WIR. I kept the separation going to the point of CSD tagging old userspace drafts rather than deleting them myself. I did not make a secret of the fact that I was an administrator before taking the job, and I suppose that an overzealous individual could say that by making this clear I was trading my 'authority' as an admin and trusted user in exchange for a job? I am also not sure what problem this instruction creep is going to solve, as in the KDS4444 situation the user was quickly evicted from OTRS once their conduct was discovered without the need for a policy change. This does have the smell of security theatre about it. Lankiveil ^{(speak to me)} 02:17, 3 November 2017 (UTC).
  • Wikipedians are not the only audience for this policy. This creates a policy we can point to when reporting spammers to freelance job sites and/or in OTRS tickets regarding commissioned articles. MER-C 12:52, 3 November 2017 (UTC)
• No editor may use a position of trust... may be overly broad. If you were going to legitimately hire someone to make non-promotional edits, you'd want to engage someone who was trusted by the community. Conversely, if an editor is going to provide copy-writing services, the community should prefer someone who is trusted to follow policies, guidelines, and best practices, versus someone who has failed to be proven trustworthy. isaacl (talk) 03:05, 3 November 2017 (UTC)
• Support in principle. Wording wise, I suggest something like "Editors with advanced editing privileges requiring community trust must not solicit or accept payments for using said privileges to advocate for or on behalf of a client or circumvent normal editorial processes regarding new and COI content". As for placement, why not put it in WP:PAID as well? MER-C 12:52, 3 November 2017 (UTC)
• Comment Personally I would go even further and require that any advanced user right cannot be *held or granted* if you are engaged in or offering any commercial or otherwise paid service related to Wikipedia. The inherent conflict of interest that receiving money for services engages means that its too much of a risk. Only in death does duty end (talk) 17:14, 3 November 2017 (UTC)
• Support, with wording to be refined, particularly regarding acceptable exceptions. And yes, per Only in death, no advanced right or permission should be granted or allowed to paid editors. Justlettersandnumbers (talk) 20:24, 3 November 2017 (UTC)

  I don't see that working generically for practical reasons. The GLAMwikitoolset right has been given to GLAM and Wikimedia Chapter employees for their "official" user accounts in order to manage donations of image archives to Wikimedia Commons and in some cases to run bot-generated reports (with granted bot flag) to support reuse on Wikipedias. They were being paid to do the work, and there is no reason to waste valuable unpaid volunteer time when projects like these are run transparently. --Fæ (talk) 22:56, 3 November 2017 (UTC)

  @Fæ: minor questions. a) Is this being run to make edits on enWiki? b) is this right covered at WP:GRP? c) does my proposed wording below make your objection mute? Smallbones_(smalltalk) 16:30, 4 November 2017 (UTC)

Fæ, what I said in my first short sentence above ("wording to be refined, particularly regarding acceptable exceptions") should be taken as applying also to what I said in the second sentence. Also, what happens on Commons happens on Commons; my opinion expressed here on Wikipedia relates specifically to this project. Justlettersandnumbers (talk) 18:43, 5 November 2017 (UTC)

• Oppose. I'm ok with the principal, but what is meant by "any user rights"? That seems overly broad. The wording makes it sound as if anything you can do as a user - create new articles, edit, revert, etc - would fall under this. The wording needs to better reflect what rights are at issue. - Bilby (talk) 08:14, 4 November 2017 (UTC)
• Oppose. The suggestion is that "payment for service" is automatically harming the encyclopedia, that is just suspicion, it's possible to be paid for doing good work, it's also possible for an admin to put their responsibilities to the community last or first, paid is not proof of a problem, it's only proof that we don't trust them. The heart of the issue isn't WHY the editor, or admin might be acting against the community, only that there is a problem with what they actually did. So lets be focused on behavior not mistrust. Dougmcdonell (talk) 19:17, 4 November 2017 (UTC)

Prohibition statements etc. in policies/guidelines oalmost always reflect upon the behaviour of common folks, not that of the outliers.Though, if you had choosen to oppose, because you think, that there's no problem in any editor soliciting payment(s) from potential customers through OTRS channels (as long as the worth the article he/she later churns out is satisfactory) or somebody self-patrolling his own paid creations, despite the elements of obvious cognitive bias or some sysop restoring articles, declining CSDs, closing AfDs in lieu of payments, it's another case.Winged Blades of Godric^{On leave} 14:05, 5 November 2017 (UTC)

• Oppose I think Wikipedians should always be able to solicit "payment for services to be rendered on Wikipedia". Chris Troutman (talk) 21:46, 4 November 2017 (UTC)
• Support long overdue. Coretheapple (talk) 17:16, 5 November 2017 (UTC)
• Support in principle and most specifics; I prefer the slight modification in the next subsection. It's concise, non-bureaucratic, and consistent with the general community take on these matters. We know there'll be some paid/COI editing, and consensus implemented policy about it. This just closes a loophole.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  00:23, 11 November 2017 (UTC)

With very few exceptions there are no opposes here based on principle. We're just arguing about wording (and where to put that wording). Within the limits of my available time, I'll keep coming back to this. There are several places to put this, and I think several are needed since advanced rights are covered in several places. Progress so far:

• I've placed a simple one line prohibition at WP:WikiProject_Articles_for_creation#How_to_get_involved and opened a discussion at Wikipedia_talk:WikiProject_Articles_for_creation#No_payments_for_reviews. So far - no opposes, 1 support.
• A few days ago User:Godric on Leave added ""you should not accept any such affected article(s) at articles for creation process." to WP:COI and then reverted it as premature. I've put it back and reopened the discussion at Wikipedia_talk:Conflict_of_interest#Using_tools_in_exchange_for_pay. I expect that will stick (based upon further discussion here, and is likely to be made stronger.

Other discussions, with possible wording changes, will have to be held at WP:GRP (for ORTS) and WP:Admin. I don't expect any opposition at WP:GRP, and will start that discussion on Monday. My suggestion for wording follow. I'm just adding a line on Wikipedians in residence, but please note that the "who" in the 1st line will change based on where the policy is proposed. Once everything is done, we can then summarize the changes at WP:Paid.

• I don't get it. As far as I can tell, using any bit in exchange for money is already disallowed so outlining rules for it just makes it easier to game. Anyone misusing any bit is subject to having that bit removed. Doing it for pay is clearly misusing it. There really is no question about it. Any admin unblocking for cash would be dragged to Arb and bit stripped, for instance. No one would oppose that. A new rule is superfluous. Dennis Brown - 2¢ 20:14, 18 November 2017 (UTC)

• @Dennis Brown, the TOU—even in the brave new world of the WMF crackdown—aren't as clear-cut as you think, and there are still quite a few loopholes. Show me where in policy it's forbidden for an admin to profit from their access to deleted revisions, for instance—and that's something that does have commercial potential, there are ad-funded websites that literally do nothing but host deleted Wikipedia articles (Deletionpedia is the best-known). ‑ Iridescent 20:23, 18 November 2017 (UTC)

• As long as policy is based on consensus and consensus is overwhelmingly against selling use of the bits, then it seems obvious to me. If I find any admin using any bit for gain, I won't hesitate to block them, for example. I don't need a specific policy statement, WP:COMMONSENSE covers it well, as bits are based on trust that they will be used only to benefit Wikipedia. Any use of the bit to gain advantage, be it financial, in an edit war, or otherwise, is grounds to lose the bit. Any bit. The community has already said this by providing a vetting system for all the bits, and policies on use of each of the bits. Anyone that doesn't understand that shouldn't have advanced bits, as the reason we have them is to benefit the encyclopedia, not ourselves. I'm afraid once you start setting specific rules, you start creating loopholes. As it is now, ANY misuse of any kind, even those we can't think of ahead of time, is grounds to lose the bit. I truly feel we codify too much that is already covered by common sense, and that is part of the problem with the contradictory maze of policies we have. Dennis Brown - 2¢ 01:35, 19 November 2017 (UTC)

• Without a policy to back it up, the odds of a desysop from arbcom are negligible. Sure we could go the community ban route that we went with within the last few days for an OTRS agent, but that would also lead to the inevitable arbcom case. TonyBallioni (talk) 01:45, 19 November 2017 (UTC)

• I have a bit of a counter-proposal to this, which is that rather than setting out prohibitions for paid editing activities, we should merely set out a very tightly limited list of what paid editors can do, and specify that any action not on that list is prohibited. The list would be something like, following disclosure of having been paid, adding reliably sourced information to a draft, or proposing on an article talk page that content be added or changed. If that is the complete list, then obviously things like unearthing deleted edit histories would be outside the scope. bd2412 T 20:28, 18 November 2017 (UTC)
  • As the United States discovered when it tried to ban alcohol, it is very difficult to regulate that which you prohibit, and I think your proposal comes so close to prohibition that the same principle will apply. If you make the rules too onerous, then at some point paid editors will just not disclose their paid status. I'm sure this already happens, and probably quite a bit, but it will get worse. WP:OUTING is written so strongly (too strongly IMO, but that's a separate discussion) that enforcement will be very difficult. --Trovatore (talk) 21:14, 18 November 2017 (UTC)
• Support this or a similar version. Gandydancer (talk) 04:33, 24 November 2017 (UTC)

break

New basic wording:

No editor may use a position of trust or advanced user rights to:

• solicit payment for services to be rendered on Wikipedia, or
• accept payment for the use of such a position or rights
  • for the benefit a client
  • for advocating for a client, or
  • to evade our normal scrutiny system for new content and COI content.

Payments and grants made by the Wikimedia Foundation or its affiliates (e.g. chapters) are excepted. Wikipedians-in-Residence should declare their paid status and their paid use of advanced rights, but are otherwise exempt.

Smallbones_(smalltalk) 16:30, 4 November 2017 (UTC)

This is an improvement, but I'm still a little uncomfortable with the word "solicit", which I think could potentially cover a wider range of scenarios than what is intended. Am I correct in assuming the intended effect of that clause is to stop people using OTRS and other WMF-sponsored tools for finding work? Lankiveil ^{(speak to me)} 02:30, 5 November 2017 (UTC).

Examples where "solicit" may come into play: Orangemoody-type advertising via email, i.e. Pay me to write your article and I'll make sure it sticks because I'm an admin, b) ads on Fiverr "You can pay me to write your article, and I'm an admin". One place that it wouldn't come into play is with Wikipedians-in-Residence because they "are otherwise exempt." I have no problem with a potential WiR saying to a respectable GLAM "BTW I also volunteer at OTRS" because GLAMs are aligned with our aims, and because I think GLAM folks (on- and off-Wiki) would police the activity themselves. I trust librarians!. Smallbones_(smalltalk) 04:20, 5 November 2017 (UTC)

Can the scope of "position of trust" be narrowed? What roles that do not require advanced user rights are being targeted? For example, is a co-ordinator of WikiProject Military history, an elected position, considered a position of trust for the purpose of this proposed guidance? How about the Today's featured article co-ordinators? Teahouse hosts? isaacl (talk) 18:26, 5 November 2017 (UTC)

Sorry for my absence here, real-world obligations catch up sometimes. The answer to @Isaacl:'s question is most that there are many places where the rules for different positions and user rights are set out. I believe that each place needs input from the folks that hang out there and that the exact wording for each position can be worked out, In short, it'll be narrowed by doing one position at a time, and by the people involved. That's not to say that folks here can't be involved at those pages as well. So far:

• small change already made at WP:AFC, with no opposition
• small change at WP:COI reflecting the AfC change
• an interesting discussion at WT:Good articles
• I'll start a discussion very soon at WT:GRP (which covers OTRS and other rights)

Smallbones_(smalltalk) 16:47, 8 November 2017 (UTC)

Can you list some examples of roles that would be covered which do not have associated advanced user rights? This would help me consider what type of wording may be appropriate. Personally, I do not think just being trusted by the community should be in itself a disqualifying factor, even though trusted editors inherently have a greater influence on discussions than those who aren't trusted. isaacl (talk) 17:00, 8 November 2017 (UTC)

My main concern is with holders of advanced rights who use their status, rather than the rights per se for paid editing, e.g. OTRS "volunteers" who might come on to enWiki (their rights, if we call them that are used elsewhere) and post something on a talk page, e.g. "From an OTRS ticket, I'm removing .... until a better source can be found." Or say an admin !voting at ANI. That's not exactly using their tools - it's a use of their position or status.

As far as "trusted positions" without tools - the only ones that concern me at all are AfC reviewer (this seems to have been taken care of) and Good Article reviewer (which is still being discussed). Others may be concerned about different positions - but let them make the proposals. As far as the elected director of WP:Military history - I just don't know enough about it - but I doubt that he'd win an election if he declared that he was willing to sell his services as the director. Smallbones_(smalltalk) 17:49, 8 November 2017 (UTC)

FA coordinator and the ArbCom election commission have been mentioned above. GMG^talk 17:56, 8 November 2017 (UTC)

Perhaps it would be better to cast the restriction (for editors without advanced user rights) in terms of the type of services offered: the commonality seems to be decisions that are entrusted to one or a small number of persons, or the evaluation of the community's consensus view. So maybe something like this:

• No editor with advanced user rights may solicit or accept payment for any service related to Wikipedia. Examples of services include advocating for a client, or evading scrutiny for any edits benefiting a client.
• No editor may solicit or accept payment for any service related to evaluating the Wikipedia community's consensus view, or to deciding on an outcome either as an individual or within a committee, as opposed to part of a community discussion. Examples of outcomes include decisions made by the feature article co-ordinators, and rulings made by the Arbitration Committee election commission.

Further examples of course can be listed. isaacl (talk) 18:35, 8 November 2017 (UTC)

• Prefer this version to the one in the above section, since it deals with the "coordinators" matter. I do think the admin, CU, etc. policies need to be updated with explicit rules again using such special power/tools/authority on behalf of off-site interests. It really doesn't have anything to do with money changing hands but with PoV, COI, and NOT#ADVOCACY policy.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  00:24, 11 November 2017 (UTC); revised: 12:34, 29 November 2017 (UTC)
• I've made the relevant additions to New Page Patrol: [2][3]. MER-C 09:33, 22 November 2017 (UTC)

(radical?) counterproposal

Instead of running away and pretending we can stop editing (hint - I've only seen reports and instances of paid editing increase since the change in the ToS from my OTRS work), why don't we almost create a "trusted editor" system - editors that are trusted by the community are added to a page, can be contacted by external editors, and if the subject is indeed notable, the page can be created by them for either a charge or a donation to the WMF? (something a bit like WP:JOB but better publicised) Paid editing is clearly not going to go away - as I see it, we can have a choice where both us (with better paid-for articles, so less NPP needed), and the subjects (article less likely to get deleted, less likely to be scammed). I'm aware this does present a potential COI flag over the foundation, but as it is independent editors carrying out the editing, I don't see this as an issue.

Note: I'm not involved in paid editing, I just regularly dealt with the fall out from it. The current approach clearly isn't working IMO - maybe a shift in our approach may well get better results. Mdann52 (talk) 22:50, 3 November 2017 (UTC)

Those hiring paid editors are often looking for promotional rather than neutral content. The problem is growing as we become more well known and respected and the businesses that do this work increase in number. The rise of sites like Elance and Fivver also contribute. Doc James (talk · contribs · email) 07:18, 4 November 2017 (UTC)

@Doc James: True - however, I think if we are going to keep our head into the sands that this issue can be solved with our current approach, promotional content is going to become more widely available. I think that trialing different approaches to see what impact they make would be at least vaguely worthwhile. Mdann52 (talk) 17:01, 5 November 2017 (UTC)

Our current approach appears to be 1) some pretending the problem does not exist or if it does it does not matter 2) a small group trying very hard to keep our rules against paid editing from being applied and try to do everything possible to prevent any new rules from being created to regulate the practice or enforce our TOU.

So it is not surprising we are here. We do need to try things, but I would like to suggest we try enforcing our current rules or ban paid promotional editing directly in article space completely. Doc James (talk · contribs · email) 04:41, 6 November 2017 (UTC)

• See certain portions in this thread.Winged Blades of Godric^{On leave} 09:53, 4 November 2017 (UTC)

• @Godric on Leave: I can see the parallels there, but that seemed to be far more about money from the WMF rather than subjects. I'm under no illusion this proposal is not going to get any real levels of support - sometimes, I think it's best to throw radical proposals out there to get people thinking, as in my time on Wikipedia, towing the same line has only seen the problem get worse... Mdann52 (talk) 17:05, 5 November 2017 (UTC)

• Hi all! My opinion is simply disallowing those types of paied contributions because especially OTRs members as will as admins should be of the most confident users and represent the idea of volunteering for wikipedia and if we allow them to be paied for their contributions then wikipedia will become like any paid website and will lost its main principle of free knowledge. Those paied users are more prone to bias than those who are freely volunteering and sacrificing there efforts and time!. Regards--مصعب (talk) 11:18, 4 November 2017 (UTC)

This isn't going to happen.

• @مصعب: There are a few editors involved with Wikipedia who are paid for their work and tend to produce high-quality articles - I'm of the opinion that paid editors != bad editors as a general rule - hence why I'd rather it was members of the community being paid for writing articles outside their comfort areas, rather than unknown people writing paid promotional content. Mdann52 (talk) 17:01, 5 November 2017 (UTC)

• Just no TonyBallioni (talk) 13:13, 4 November 2017 (UTC)
• Hell no! - it would be reputational suicide. --Orange Mike | Talk 20:58, 4 November 2017 (UTC)
• Heck no! - some people get carried away! Smallbones_(smalltalk) 21:44, 4 November 2017 (UTC)
• Absolutely no . This is even worse than the error that was made in the first place by allowing paid editing under the condition of disclosure. No form of paid editing is compatible with the volunteer philosophy of Wikipedia.Kudpung กุดผึ้ง (talk) 03:36, 6 November 2017 (UTC)
• Hahaha Worth imagining just so that in my mind I can see the look on the WMF's face if we tried to turn the platform into a donation machine through community consensus... In all seriousness though: not gonna happen. — Insertcleverphrasehere ^{(or here)} 12:31, 6 November 2017 (UTC)

• @Insertcleverphrasehere: Evidently, you've never been on Wikipedia around December while logged out for the annual fundraising drive... :P Mdann52 (talk) 22:12, 6 November 2017 (UTC)

• Presses nuke button - Seriously though, it is a good idea but per above wishful thinking. - Knowledgekid87 (talk) 16:24, 6 November 2017 (UTC)
• No. Such a web site would be possible, and might be no worse than the commercial world already is, but whoever wants to run it, can and must do so entirely independently from WP or the WMF, and I do not think anyone could ethically participate in both. The problem is that our copyright permits anyone to use our material, and then add commercialism onto it, but we always knew that's inherent in the license. Personally I sometimes think we should have chosen -NC, but we didn't. DGG ( talk ) 19:14, 20 November 2017 (UTC)

History - people with privileges who edited for pay

Several folks have asked if this has ever happened. I've been spending a bit of time looking at that...

• Nichalp (talk · contribs · deleted contribs · logs · filter log · block user · block log)

apparent sock (listed at SPI): Homechap (talk · contribs · deleted contribs · logs · filter log · block user · block log)

apparent sock (listed in Arbcom decision June 2009): Zithan (talk · contribs · deleted contribs · logs · filter log · block user · block log)

crat, oversighter, admin, OTRS.

per edit count first edit in 2004.

status, Zithan blocked; other accounts not blocked, Nichalp retired; last edit on en-WP was Jan 2009 (left enigmatic note here 31 Jan 2009).

Made a 'crat here in September 2005 ; stripped by arbcom here June 2009.

joined OTRS here October 2007; removed from list here July 2009 with edit note No longer active(!)

June 2009 SPI filed and was put on hold for Arbcom, Arbcom finding is here

btw this from July 2008 looks a lot like trying to figure out how to cover their socking tracks after a goof, using the tools.

The arbcom decision spawned a long discussion at the related talk page here.

Led to a slew of AfDs eg linked from Wikipedia:Articles for deletion/Brad Sugars

Led to a mammoth RfC that ran June-July 2009 Wikipedia:Requests_for_comment/Paid_editing

• Seicer (talk · contribs · deleted contribs · logs · filter log · block user · block log)

admin

Status. not blocked. Still an admin. not too active per edit count, last edit was Feb 2017

per edit count, created in 2006

diff, June 2009 acknowledged editing for pay; explained here on 11 June that they work for a university and I only add content or modify content with information that is sourced directly from our publications and web-sites, or from accompanying articles.. That diff says that they gave up the bit and they did but they asked for it back in Nov 2009 log)

• Wifione (talk · contribs · deleted contribs · logs · filter log · block user · block log)

admin

sock of account formerly called Mrinal Pandey, renamed to Empengent (talk · contribs · deleted contribs · logs · filter log · block user · block log)

See SPI Wikipedia:Sockpuppet_investigations/Mrinal_Pandey/Archive (I had never looked at that before. Wow)

arbcom case Feb 2015; desysopped and banned for socking and editing for pay on behalf of a university, Indian Institute of Planning and Management

Master account (edit count) created Dec 2006

Wifione account (per edit count) created April 2009.

user rights log, made admin Sept 2010.

• KDS4444 (talk · contribs · deleted contribs · logs · filter log · block user · block log)

OTRS, autopatrol

status, indeffed Nov 2017)

OTRS (removed Oct 2017)

--(That is what I found so far. Jytdog (talk) 18:31, 18 November 2017 (UTC))

• Salvidrim! (talk · contribs · deleted contribs · logs · filter log · block user · block log) via Salvidrim! (paid) (talk · contribs · deleted contribs · logs · filter log · block user · block log)

admin

Currently editing for pay through "Mister Wiki"

— (added by JJMC89 (T·C) 18:56, 19 November 2017 (UTC))

• Malunrenta (talk · contribs · deleted contribs · logs · filter log · block user · block log)

New Page Patroller

Systematically marked as patrolled new pages created by one of the big UPE sockfarms.

-- added by Rentier (talk) 19:27, 19 November 2017 (UTC))

• Soetermans (talk · contribs · deleted contribs · logs · filter log · block user · block log)

AFC reviewer

Does work for "Mister Wiki".

- (added by Jytdog (talk) 22:54, 19 November 2017 (UTC))

Other history

Had never seen this list before. Back in 2009 already somebody was tracking ads for paid editing on Elance. See User:Brumski/paid_editing_adverts. Jytdog (talk) 18:31, 18 November 2017 (UTC)

Rather than putting this list on the village pump page, how about including it somewhere under Wikipedia:WikiProject Integrity, such as a subpage of Wikipedia:WikiProject Integrity/Editor Registry, so it can more easily located again in future and kept up-to-date? isaacl (talk) 20:07, 19 November 2017 (UTC)

As I noted at the top, people in the RfC discussion asked about other people with advanced privileges (PWAPs ??) who edited for pay and I wanted to make it easy for folks participating to see. But yes it should be copied to the Integrity page. Jytdog (talk) 21:17, 19 November 2017 (UTC)

You guys should probably take care to separate your own sigs from the list of editors in the section above. ☆ Bri (talk) 00:31, 21 November 2017 (UTC)

thx, added notations and smallified. :) Jytdog (talk) 02:40, 28 November 2017 (UTC)

Current developments

In view of the current case (which is going to be accepted) at Wikipedia:Arbitration/Requests/Case#Mister_Wiki concerning an admin, the entire proposal should be reworded as:

The holding of advanced rights is incompatible with paid editing

Even if a user with advanced rights creates creates another identity for his/her paid editing (such as user:Salvidrim!), it just creates yet another perceived degree of tolerance for paid editing - and its still the same person. No one can claim to successfully manage a voluntary split personality. Kudpung กุดผึ้ง (talk) 01:01, 26 November 2017 (UTC)

• I didn't realize this discussion was happening here, I had been commenting on the case request. I'll just basically expand on what I said there: I think that it would be a very good idea if we made users choose between holding advanced permissions or being paid to edit. To my mind it's pretty simple: if you want to accept payment for doing something on Wikipedia, you first go to WP:BN and say "I've been hired to do a thing, please remove all of my userrights" (yes, rollback and everything, right down to autoconfirmed). Maybe we should require that you describe the work you're being paid to do, or post a link to the request on Fiverr or wherever, that seems like a good idea for transparency. Then you go do your paid gig, making proper disclosures along the way, and once you're done you go back to BN and say "my paid gig is done, please give me back my userrights". Then, obviously, you don't touch that topic again. It's all done from one account so you're accountable for it, and nobody is prevented from doing paid editing if that's a thing they want to do. And if you're being paid to "manage" content on an ongoing basis, you shouldn't be entitled to any advanced permissions.

As for Pigsonthewing's concern about Wikipedians in Residence, I think it stands to reason that being paid to promote Wikipedia and facilitate outreach events is somewhat different from being paid to edit Wikipedia on behalf of a third party. The WiR program is already pretty transparent, and clearly valuable. Ivanvector (^Talk/_Edits) 15:43, 29 November 2017 (UTC)

• I think this would be a very bad idea. There are far too many grey areas and corner cases and times where this would harm the encyclopaedia (making it much harder for someone to revert vandalism they happen across) - not to mention that it would encourage people with rights greater than autoconfirmed to lie about any paid editing making the problem worse rather than better. We will either lose many good editors and admins because of technical violations or the rules will be inconsistently enforced making much more of a mess than we currently have. Thryduulf (talk) 17:15, 11 December 2017 (UTC)

Support the principle that The holding of advanced rights is incompatible with paid editing. I'm not sure that lesser rights than admin really need to be covered, but it does no great harm and keeps it simple. Anything in excess of auto-confirmed rights should be covered.

And this seems to me to be consistent with the direction ARBCOM has taken. When I became an admin, the principle seemed to be that I'd be under greater scrutiny when exercising "the mop", but that's now been extended to every edit an admin makes. We should be consistent, and apply this principle to all advanced rights and positions.

But please note I'm not advocating enforcement as a solution. The spirit of wp:5P5 as I see it is, whenever we need to enforce the rules, they have in a sense already failed. The goal should be to write the rules, and build consensus supporting them, so that enforcement is rarely necessary, and so that the cases where sanctions are needed stick out like sore thumbs, because users that are here try to follow the rules whether they agree with them or not. Andrewa (talk) 22:01, 20 December 2017 (UTC)

Support Kudpung's proposal that "The holding of advanced rights is incompatible with paid editing". Once money enters the scene the motivation for every action is questionable. In Salvidrim's case, granting rights to the alternate account is (imho) indistinguishable from sockpuppetry. Regardless of the outcome at Arbcom Salvidrim's credibility and impartiality is shot. How can an admin, who accepts payment under another hat, give fair judgement on other paid editors?

A bright-line rule as proposed by Kudpung would leave no room for ambiguity or doubt, and leave no grey area for anybody to stumble into. The restriction needs to be applicable not only to Admins but to Page Movers (for suppressredirect) and Template Editors (for the ability to duck the title blacklist) at the very least. Cabayi (talk) 18:31, 23 December 2017 (UTC)

Not in this form. With the way the question is being framed so far, the proposed solution is missing the aim. The problem underlying all the situations that have been discussed so far is not the fact itself that payments have been made, it is the introduction of a conflict of interest subsequent to these payments. It is the conflicts of interest that we should strive to find ways of tackling, regardless of their form (and there are myriads ways for this to happen: personally, I think the existence of visible edit counts acts as a much stronger disincentive to keep wikipedia's purpose in mind than all the harmful money you could pump into the project). Directly or indirectly receiving payment for any forms of editing (with or without the exercising of advanced rights) can happen in a variety of situations that do not involve such conflicts of interest. How about wikipedians in residence, WMF staff or WikiEdu coordinators, should they be banned from using any advanced tools? Is it wrong for the organisers of a big student editathon to hire a wikipedian to clean up the resultant mess? Is it wrong for a user to start a crowdfunding campaign among her friends so that she can dedicate a month of her time to helping clear the AfC backlog? – Uanfala (talk) 19:27, 24 December 2017 (UTC)

Consensus and copyright law

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

---

This removal by Sandstein apparently need to be discussed. Admins that are closing FFD discussions need to have a grasp on the relevant copyright law(s) in order to make a sound decision. This is one of the few areas were community consensus can actually have a detrimental effect on the project as a whole as consensus, or lack thereof, could result in a violating image being kept on the project when it really shouldn't be.

The question is as follows: Should admins be able to use their knowledge of copyright law to ensure that images uploaded to the English Wikipedia follow said law. Regardless of the actual consensus of a FFD discussion? --Majora (talk) 20:42, 4 November 2017 (UTC)

CaCL:Support

• Support allowing admins to use their discretion to ensure files follow the law. --Majora (talk) 20:42, 4 November 2017 (UTC)
• Support but I assumed this was already covered by WP:F9. A copyright violation cannot be allowed on Wikipedia. TonyBallioni (talk) 00:25, 5 November 2017 (UTC)

• @TonyBallioni: I noticed that F9 isn't listed at Wikipedia:Criteria_for_speedy_deletion#Pages_that_have_survived_deletion_discussions. Do you reckon it should be? G12 is, so I don't see why F9 shouldn't be. F8 is also listed, so "pages" does cover files. Adam9007 (talk) 01:16, 6 November 2017 (UTC)

• Adam9007, yes. I think it should be, though I agree that G12 covers this as well. Administrators already have a basis in policy to delete copyright violations regardless of the outcome of discussion. I firmly support the four-eyes principle on speedy deletion even for copyright, but once an editor has pointed out a copyright violation, the CSD allows for an admin to delete the page. Wikipedia almost always sides with taking the most conservative option when it comes to copyright, and that means deletion when there is a reasonable basis to assume that the content is copyrighted and without proof of the content in question being free. Majora, could you explain a bit more why you don't think this is already under the CSD policy? TonyBallioni (talk) 01:46, 6 November 2017 (UTC)

• (edit conflict) Because having things written down in black and white make it far less likely for someone to find a way around it. I tried to explain the fact that the image that caused all of this was copyrighted but Sandstein claimed that deleting it would constitute a supervote. When I tried to explain to them that it would not be a supervote because of the admin instructions they removed those instructions. If it can happen once it can happen again. So having it in black and white can only avoid such instances in the future. --Majora (talk) 01:54, 6 November 2017 (UTC)

• Thanks. I'd also suggest opening up a conversation at WT:CSD about the point Adam raised above. Copyright is one area where the CSD policy always trumps XfDs, and getting it is writing there will also be helpful. TonyBallioni (talk) 02:00, 6 November 2017 (UTC)

• @TonyBallioni: I'd also suggest opening up a conversation at WT:CSD about the point Adam raised above I was going to suggest the same thing. Adam9007 (talk) 02:03, 6 November 2017 (UTC)

• Support this has always been the case, copyright policing has always trumped consensus because of the legal implications to both us (the Wikimedia Foundation sites) and to our downstream content re-users. We cannot permit copyright violations to remain visible here just because consensus in one deletion discussion is in favour of keeping a file. I would also remind users that we're here to create a 'free encyclopedia' - that is to say, one that is as unencumbered by copyright limitations and restrictions as far as is possible'. We are not here to create an 'online illustrated encyclopedia', one which includes as many images as possible from anywhere and everywhere'. I'm shocked but far from surprised we're having this discussion, and disappointed my colleagues are closing copyright discussions when they do not understand about copyright, nor do they seem to care that they don't understand copyright. Nick (talk) 13:01, 5 November 2017 (UTC)
• Support the RfC question, sort of, but considering it to be separate from the specific text added/removed that led to this RfC. It may help to reframe it, though. Yes, it's about making a determination about a legal matter using knowledge of copyright, but it's more likely to get support if we just say that the closing admin must base the close on the strength of arguments -- and that we afford admins more leeway in FfD closes to go against the majority or even "supervote" when the majority get it wrong. Notability is more open to interpretation and the consequence of getting it wrong by siding with the majority is far less than it is in matters of IP. — Rhododendrites ^talk \\ 17:34, 5 November 2017 (UTC)
• When a closer has not concluded there is copyright infringement, as in this case, the paragraph-at-issue is irrelevant. You can't use it to badger an unconvinced-admin into deleting. If you're convinced a non-consensus should be delete, then either re-nominate or take it to DRV. (It was unnecessary for the admin to delete the paragraph to reject the unpersuasive demand.) On the other hand when a closer is convinced that sufficient evidence of infringement has been established then SUPPORT. There is abundant basis to go against a majority based on strength of argument and the various valid reasons for discounting poor arguments.[4] This is especially true in the case of copyright: Wikipedia policy, which requires that articles and information be verifiable, avoid being original research, not violate copyright, and be written from a neutral point of view is not negotiable, and cannot be superseded by any other guidelines or by editors' consensus.[5] Copyright violation is probably the strongest justification for discounting a faulty majority. If you object to the deletion then take it to DRV. Alsee (talk) 17:22, 6 November 2017 (UTC)
• Support Consensus cannot overwrite copyright law, so images clearly uploaded that violate copyright can be removed by a knowledgable admin even if consensus thinks it should be kept. That said, we need to differentiate these from problems with NFC rationales, which start with the assume that there's a fair-use claim and all core copyright issues are not a problem. Those need to be taken in consideration with strength of FFD arguments to keep or delete. --MASEM (t) 23:12, 6 November 2017 (UTC)
• Support copyright is one of a very small number of areas where, because of the potential for serious harm to result, we need to err on the side of caution. As a result if an FFD discussion comes to a conclusion about copyright which the closing admin knows is incorrect then they should be able to place greater weight on the global policy and less on the local consensus. No, we don't select admins for detailed copyright knowledge, but we do expect that admins who don't have the knowledge required to work in some area stay away from it. Hut 8.5 18:11, 7 November 2017 (UTC)
• Support: I agree with pretty much what everyone has posted above. I also think discussions involving copyrighted content (files or text) need to err on the side of caution. While I can understand how a "no consensus = keep" might be acceptable for AfD discussions, I don't believe such an approach works very well with discussions about files. I've seen some FFD discussions (involving both non-free content and free content) closed as such over the past few months and the logic for doing so seems questionable at best to me. It's seems to me that the licensing of a file should be clearly verifiable; otherwise Wikipedia should not accept it. In cases where a file's licensing is challenged, the burden should be for those arguing for the file to kept to clearly show that the licensing complies with WP:COPY; if they are unable to do so to the satisfaction of the community, Wikipedia should delete the file along the lines of c:COM:PCP. I don't think this proposal is asking for closing admins to offer legal opinions or cast supervotes; I just think it more clearly spells out that file copyright discussions can sometimes be complex and the automatic default in cases where there still exists some significant doubt should not be to keep. -- Marchjuly (talk) 00:56, 8 November 2017 (UTC)
• Support. Copyright law should trump consensus, and admin discretion to delete to follow copyright law in spite of consensus is perfectly fine. I would also support shifting the default outcome for a no-consensus FFD to be delete to err on the side of caution. ---- Patar knight - ^chat/_{contributions} 04:10, 8 November 2017 (UTC)
• Support per above. I'm also concerned that so few editors understand/respect copyright that we actually have to discuss this. For example, if someone uploads a copy of File:TheAvengers2012Poster.jpg under {{PD-self}} and consensus says keep as is, then rest assured I'll be there to delete it. -FASTILY 20:26, 10 November 2017 (UTC)
• Support Copyright law closures should only adhere to what actual law says, and not care about consensus. The discussion should bring in examples why or why not it is a violation of the law, but the closure should have sufficient copyright law knowledge to close such a discussion. Being an admin is not an end-all reason to be able to close all kinds of discussions, sometimes knowledge in an area, such as copyright is required. / Commons admin (t) Josve05a (c) 13:33, 11 November 2017 (UTC)
• Support. Law (and indeed WMF fair use policy) supersedes a local consensus. Stifle (talk) 10:31, 14 November 2017 (UTC)
• Only partial support Of course consensus cannot overule copyright law, but the effective copyright law depends upon many layers of interpretation, both the interpretation done in the legal system(s), the interpretations(s)we do here, and there necessary adjustments we have made to accommodate in some manner incompatible legal systems. It's very easy in a discussion to say "copyright law " but the actual meaning is very often "my interpretation of copyright law " or actually "my interpretation of our practices on how we interpret what we think to be copyright law" DGG ( talk ) 02:30, 20 November 2017 (UTC)
• Support, if a file violates NFC or copyright law, it must be removed regardless of consensus. Those policies are not subject to override by consensus. Admins are entirely capable of having good enough understanding of both NFCC and copyright law to understand when that needs to happen. (That also means it will happen regardless of consensus or lack thereof here, those policies are not subject to consensus at all.) Seraphimblade ^{Talk to me} 05:22, 27 November 2017 (UTC)
• Support. If an admin is confident that there are legal considerations that require file deletion, then the admin should delete the file (generally with a clear explanation) even if the FFD consensus was otherwise. We cannot and should not tell admins to do something that they believe is contrary to law simply because some editors want to do it. But that is not the same thing as saying that admins must make a determination of law, or that any deletion decision cannot be subject to review. --Tryptofish (talk) 00:41, 28 November 2017 (UTC)

CaCL:Oppose

• Oppose As remover of the text, I obviously disagree with it. We do not select our admins for a knowledge of or training in copyright law, and therefore a random admin's understanding of the law (which varies substantially depending on jurisdiction) is only marginally likely to be better than that of other editors. Ultimately, consensus determines which files are kept or deleted and therefore what Wikipedia's collective understanding of copyright law is. Obviously, admins should take strength of argument into account in closing, and therefore give less weight to opinions based on a clearly mistaken view of the law (e.g., "information wants to be free, you can't copyright art!"). But that's not the same as saying that an admin's personal interpretation of the law should override everybody else's views.  Sandstein  20:52, 4 November 2017 (UTC)

  If your knowledge of copyright law is only marginally better than the general editor's perhaps you shouldn't be closing FFD discussions that are partly or entirely based on copyright law? Perhaps leave those to admins that know what they are doing? --Majora (talk) 20:54, 4 November 2017 (UTC)

  I'm talking about administrators generally, because what you propose is a rule that is supposed to apply to all closing administrators, including those who may know nothing at all about copyright law. If you disagree with a closure that did not end in deletion, just renominate the file or go to WP:DRV.  Sandstein  21:02, 4 November 2017 (UTC)

  It isn't about this one file. It is about the actions of an admin who admits to closing a discussion when they didn't know all the facts based on a lack of consensus that violates copyright law. I tried to get you to understand but you refused. I would certainly hope that most admins would have the knowledge of their own personal abilities to know what areas of the project they are best suited for. Those that know nothing about copyright law should not be setting foot into FFD to close discussions based on copyright law. Just as those that know nothing about username violations shouldn't be stepping foot in UAA without at the very least learning about it first. We hold our admins to such high standards for a reason. We trust they won't go bouncing around the project willy nilly without knowing what they are doing first. --Majora (talk) 21:09, 4 November 2017 (UTC)

• Oppose Suppose there was a discussion where everyone !voted delete based on copyright violation but the closer, based on his superior knowledge of the law that copyright was not being infringed, closed as keep. Would that do? Of course not. The role of the closer is to assess consensus, not to assert any supposed superior knowledge. Thincat (talk) 21:27, 4 November 2017 (UTC)

  I'm trying not to bludgeon the process by responding to every person but that seems much more unlikely to ever occur. First of all, obvious copyright violations are speedy deleted and never get to FFD to begin with. Second, I would assume this hypothetical admin would actually attempt to provide proof to the other respondents? I certainly hope so. If they are closing FFD discussions they are ultimately responsible for proving that the image follows copyright. We trust random people with OTRS access to access copyright based on their "superior knowledge". We should trust admins closing FFD discussions to do so as well. And to provide proof of their actions. --Majora (talk) 21:37, 4 November 2017 (UTC)

  Thincat, Wikipedia:Closing discussions#Policy says it ain't quite that simple. ―Mandruss ☎ 21:39, 4 November 2017 (UTC)

  But Majora has raised breach of the law which is narrower than breach of policy. Copyright infringement, generally being a tort, requires damage to be actually caused to the injured party for tort to be proved. And that seems very unlikely to be realistic in this case. (That shows how little I know about the law!) Of course consensus should be policy-based. Take the matter to WP:DRV. Thincat (talk) 21:59, 4 November 2017 (UTC)

  The preservation of the project's safe harbor status under the DMCA requires us to deal with copyright violations immediately, as soon as they are noticed. Actual damage to the party in question is beyond the scope of that carve out in the law. Commons puts this pretty succinctly in their precautionary principle. "We can get away with it" isn't a valid reason primarily because of safe harbor. So an admin using consensus, or lack thereof, to keep a violating image is a serious concern. Hence this RfC, to reestablish that point in the FFD admin instructions. --Majora (talk) 22:08, 4 November 2017 (UTC)

  Thincat, I definitely understand looking at the mirror-situation. However I see a strong asymmetry here. If a closer is convinced that sufficient evidence has been presented to establish copyright infringement, that supersedes a majority-consensus to the contrary. In the opposite case a closer believes it is not copyright infringement, they consider it a poor deletion. However that is not strong cause to disregard a (presumably) reasonable consensus of responsible editors. They should either accept that consensus, or better yet they should simply !vote KEEP and explain why. A good closer needs to be able to do two very important things: (1) Close against a majority when there is solid cause to do so. (2) Close against their own view. This mirror-case neatly packages up those two critical criteria for a closer. Alsee (talk) 17:52, 6 November 2017 (UTC)

  Thank you for your remarks, which are helpful. Because, in my view, the hosting of File:Bob Hasegawa Official Portrait.jpg does not infringe US copyright, I think the arguments that there is a legal tort (or even a crime!) are mistaken. Perhaps when some people are claiming there is a copyright violation what they really mean is that WMF or WP policy is being broken. That position is far more firmly based – WMF do not allow "no harm" as justification even though it is allowed in law and no fair use rationale has been provided (none is required by law). So, to me some of the claims here of impropriety and impending legal calamity seem extravagant. However, I agree that closers should not close against policy (except when you ignore it!) and maybe that happened here. Thincat (talk) 23:03, 6 November 2017 (UTC)

What... exactly leads you do believe that this is in the public domain? GMG^talk 23:13, 6 November 2017 (UTC)

I'm not supposing that for one moment (and I don't know if there is a "free" licence). I am suggesting that no copyright violation (in law) has occurred. Thincat (talk) 23:20, 6 November 2017 (UTC)

• Oppose Per WP:NOLEGAL, "Nothing on Wikipedia.org or of any project of Wikimedia Foundation, Inc., should be construed as an attempt to offer or render a legal opinion or otherwise engage in the practice of law." Andrew D. (talk) 12:16, 5 November 2017 (UTC)
• Oppose - A few points here... First, discussions on copyright are ultimately simply not purely consensus based. They may seem that way, but they're really not for one very important reason: if you have 100 inane !votes to keep, and one !vote to delete that is based on a solid sourced rationale for why the content violates copyright, the admin probably shouldn't close the discussion at all, and should instead take that one well reasoned delete !vote to legal, for actual lawyers to weigh in on the actual law. They should post whatever response they get on the deletion discussion for public review, and at the end of the day that actual legal opinion is much more important than all the inane !votes in the world.

Second, we do not empower any Wikipedia editors to make legal decisions. There are very good reasons why our donations help keep legal counsel at arm's reach.

Third, this probably didn't even need to escalate to that level, and the discussion was fairly evidently one weakly reasoned !vote with nothing to back it up, and one vote that was pretty clearly the exact opposite. Inane !votes don't count toward consensus because they're "inane !votes" and not "inane votes".

Finally, if I haven't made it abundantly clear, This was probably a bad close. But they're bound to happen occasionally, and we have a process in place to deal with that. I don't see a reason that this should be outside of the ability of that process to handle. GMG^talk 12:55, 5 November 2017 (UTC)

Striking all but the final portion after some convincing arguments on IRC. I appear to be generalizing from a particular case in a way that isn't correct. I still oppose the overall proposal. I don't think every bad close requires a change in policy. I don't see any evidence to suggest that this is a persistent and pervasive problem that DRV or renominating isn't able to handle. GMG^talk 13:27, 5 November 2017 (UTC)

• Oppose. Not only do I strongly second Sandstein's point about copyright-law knowledge not being a criterion for getting the mop, I would from personal experience not trust any close made on that basis by an admin, even if I agreed with it, because there is a lot of misunderstanding out there about how copyright law works, even where only U.S. copyright law is at issue, and our admin corps is certainly not immune. I saw one admin once argue for the removal of a book cover from an article, a book cover that was itself ineligible for copyright in the U.S. as it consisted only of the work's name and some geometric shapes, on the grounds the book cover was covered by the copyright on the book itself. But even in countries where the cover art might have been eligible for copyright, its copyright is still an entirely separate one from the book's text.

  We also have the issue of too many people thinking copyright law and our copyright policy are identical—in fact, the latter is more restrictive than the former, by design, due to values the community has decided it wishes to express through that policy.

  Only one actor within the Wikimedia community has the clear authority to rule on an FFD closure on copyright-law grounds: the Foundation counsel's office. They get paid to know these things, and make such decisions on that basis (which they rarely do; they prefer to leave most of those decisions to the community, and when they do have to get involved in deleting images it will be for reasons that supersede those the community can consider such as a DMCA takedown notice, in which case they will not bother to involve themselves in an FFD since it is moot under those circumstances).

  If an editor feels that a closing admin has applied our image and copyright policies in a manner inconsistent with the relevant copyright laws, there is, as has been noted, a process available to them: deletion review. Daniel Case (talk) 00:24, 6 November 2017 (UTC)

• Oppose. I'd also like to add that Wikipedia's administrators should also refrain from giving mandatory medical advice, or anything else that would expose the community to liability. NFC is handled by community discussion, subject to the oversight of WP:OA (as I understand it), not by administrators' knowledge of copyright law, or lack thereof. Sławomir Biały (talk) 00:45, 6 November 2017 (UTC)
  • The exact opposite is actually true: an administrator closing an FfD and keeping a file they know could reasonably be under copyright would be the one assuming liability as would be the admin restoring a copyrighted file. An admin deleting a copyrighted file would have next to no liability legally: no one has a legal right to store any image on Wikipedia, even if they are the legitimate copyright holder, so deletion of a file exposes the deleting admin to no legal jeopardy. Being the admin who decides to keep a copyrighted file because of consensus, however, arguably does because individual contributors are legally responsible for their actions, and the liability comes to the contributor, not to the WMF. We would never dream of allowing anything like this for text copyright, I don't see why so many users think we should allow it for files. TonyBallioni (talk) 07:40, 6 November 2017 (UTC)
    • No. There has to be a take-down request by someone with standing. Alanscottwalker (talk) 12:31, 6 November 2017 (UTC)
      • And depending on the circumstances the individual admin could still be liable for not acting. Additionally, it is undisputable that deleting a copyrighted file does not expose an admin to legal jeopardy if it was done incorrectly: no one has a right to host any file here. TonyBallioni (talk) 14:34, 6 November 2017 (UTC)
        • • No, but requiring administrators to learn copyright law and police the site might open the foundation or individual administrators to liability. (Notice I said "community", not specifically "foundation" in my vote.) What if it were found that some administrators were negligent in their (apparently new) responsibility? Sławomir Biały (talk) 18:30, 8 November 2017 (UTC)
            • Individual adminsitrators are already liable for every action and edit they take on Wikipedia, whether it is in regards to copyright or not. The same is true of every editor: there is no community liability for anything, all users are legally responsible for their own actions. Deleting content poses zero legal jeopardy to administrators: no one has any right to use WMF servers as a webhost. Taking an administrative action that chooses to actively retain content where the copyright status is legally questionable has significantly more legal risk, though as anyone who is discussing copyright and Wikipedia should point out: its a very complex situation and it would need to be sorted out in the courts. TonyBallioni (talk) 20:32, 8 November 2017 (UTC)
              • You still misunderstand. An administrator is not liable for copyright infringement if he or she simply summarizes community consensus (as keep, say). Currently, closing a discussion one way or another does not carry with it any implicit assumption that the administrator will have evaluated the copyright status him or herself. Administrators are expected only to assess the consensus of discussions based on the strengths, not, in their administrative capacities, to verify the copyright status personally. However, if we require administrators to assess the copyright status of content, then they could conceivably become liable for an incorrect assessment of that status: closing a discussion as "keep" would amount to an administrator personally testifying that he or she has verified that the image is compatible with all relevant copyright laws. We don't want to open administrators up to this additional liability by implying that this is in any way their responsibility. But in any case, I'm not a copyright lawyer. Are you? Sławomir Biały (talk) 20:29, 20 November 2017 (UTC)
        • No. Not doing something is not an act of infringement, not deleting is not an act of infringement, saying "consensus is to keep" is not an act of infringement -- it's just an opinion about consensus that is protected free speech. Alanscottwalker (talk) 14:38, 6 November 2017 (UTC)
          • Knowing that something is a copyright infringement and deciding to use a position of community trust to keep it rather than delete it when one has the option arguably makes one a party to the infringement. This has nothing to do with free speech. TonyBallioni (talk) 15:06, 6 November 2017 (UTC)
            • No. It does not, and if one does not know what free speech is, how can one presume to claim to know copyright infringement. Alanscottwalker (talk) 16:40, 6 November 2017 (UTC)
              • As a point of order, this has nothing to do with free speech. Carry on. GMG^talk 16:51, 6 November 2017 (UTC)
                • That is not a point of order, that is just not paying attention. It remains, whether you like it or not, 'saying "consensus is to keep" is not an act of infringement -- it's just an opinion about consensus that is protected free speech.' Alanscottwalker (talk) 18:44, 6 November 2017 (UTC)
                  • People often think that the First Amendment prevents anyone or anything from punishing them for their speech. This is not the case. The First Amendment prohibits the government — not private actors — from punishing you for your speech. A private company can censor artistic expression or a private employer often can discipline its employees for speech without violating the First Amendment.[6] GMG^talk 18:49, 6 November 2017 (UTC)
                    • That's not of any meaning, here. It certainly does not change the case that, 'saying "consensus is to keep" is not an act of infringement -- it's just an opinion about consensus that is protected free speech.' (It's those who are trying to imbue it with legal meaning -- in copyright-law -- that are not only wrong, but dangerously so).Alanscottwalker (talk) 19:05, 6 November 2017 (UTC)
                      • The government is not trying to interfere with editors closing XfD discussions. It therefore has nothing to do with free speech, because... that's what freedom of speech means. Freedom of speech has to do with the government. It does not have to do with the not-government. I'm not... totally sure how much more clearly that can be put. GMG^talk 19:56, 6 November 2017 (UTC)
                        • You can pay attention to what is actually being described, an opinion, which falls in the realm of free speech is not copyright infringement. Alanscottwalker (talk) 21:17, 6 November 2017 (UTC)
                          • I... umm... Sure thing. GMG^talk 21:19, 6 November 2017 (UTC)
    • No. The administrator would most definitely not be liable. Then again, hey, what do I know about copyright law? For that matter, what do administrators know? Take it up with the WMF legal team. Sławomir Biały (talk) 18:26, 8 November 2017 (UTC)
• Oppose. In a no consensus situation it may make sense to allow it, but not in a case of a clear consensus. עוד מישהו Od Mishehu 07:30, 6 November 2017 (UTC)
• Oppose On the internet nobody knows you're a dog. Only in death does duty end (talk) 12:19, 6 November 2017 (UTC)
  • Which is a great argument to ignore the consensus at FfDs when the possibility of copyvio exists. TonyBallioni (talk) 14:34, 6 November 2017 (UTC)
• Oppose absolutely nothing we do or adopt should even begin to suggest an admin is rendering their own legal opinion in taking an admin action. -- Alanscottwalker (talk) 18:59, 6 November 2017 (UTC)

• Oppose, with obvious usual provisos. This is either unneeded WP:CREEP or an invitation for supervotes. Admins should close based on the consensus of the discussion, which already can potentially include weighting certain !votes lightly if they display an obvious failure to engage with the relevant policies. If an admin feels that a discussion has a consensus which is profoundly against their own personal view of copyright, they are free to not close the discussion and instead cast a normal vote, and perhaps the eventual closing admin will be influenced if the original admin's argument really is persuasive. And finally, if the community truly bollocks up a discussion, there is as always WP:OFFICE action to correct it if the actual copyright holder complains and the Foundation's lawyers think the complaint has merit. SnowFire (talk) 06:36, 9 November 2017 (UTC)
• Oppose on the grounds that if we follow it through to it's logical conclusion, it would likely have the opposite intended effect since users would quickly determine which admins are partial to their own copyright/fair-use/nonfree views, thereby actually giving users greater opportunity to exploit the protections already put in place. Also I oppose, to a lesser extent, (since this view has already been expressed), because copyright law, like any other law, is widely open to interpretation, and single individuals should rightfully be excluded. Even the U.S. justice system espouses a (kind of) consensus interpretation with the 12-member jury. No cop, lawyer, or judge gets to decide if you broke the law. The jury does. Most people think copyright/killing is against the law. Maybe. Maybe, not. What if you killed in self defense? What about justfiable homicide? Accidental manslaughter? Premeditated murder? Who get's to decide? A jury of your peers, that's who. Huggums537 (talk) 14:47, 9 November 2017 (UTC)
• Oppose copyright law, like all law,needs to be interpreted. Obvious violations are removed by speedy, but anything that reached FFD is somethign where the interpretation is not obvious. The only way for deciding interpretation is consensus. DGG ( talk ) 17:48, 10 November 2017 (UTC)
• Oppose per Alanscottwalker and Andrew Davidson. --Tom (LT) (talk) 22:40, 10 November 2017 (UTC)
• Oppose. If it's not a blatant situation, you (and I) must obey consensus achieved at FFD. We can already disregard nonsensical arguments at any XFD nomination, after all; when Randy shows up and says that an image is PD-animal because it was created by sword-wielding skeletons, we can just ignore his opinion when determining consensus the first time around or when evaluating a DRV. Nyttend (talk) 05:00, 13 November 2017 (UTC)
• Oppose. Let admins be admins and lawyers be lawyers. Conflating the two undermines both. WaggersTALK 13:17, 23 November 2017 (UTC)

*Oppose, consensus doesn't much matter in that case. If the content is a copyvio or in violation of NFC (as an extension of the WMF exception doctrine policy), it must be removed even if consensus is in favor of it. Consensus is totally irrelevant at that point. Seraphimblade ^{Talk to me} 04:16, 27 November 2017 (UTC) Oops, seems I misread! Seraphimblade ^{Talk to me} 05:22, 27 November 2017 (UTC)

Umm... Seraphimblade The OP's question asks whether you favor admins using knowledge of copyright to decide on a file, despite the actual consensus. Your rationale looks as if you favor an admin using such knowledge. Shouldn't the vote be moved to "support"? George Ho (talk) 04:45, 27 November 2017 (UTC)

• Oppose - This appears to me to be the sanctioning of a few rogue ultra-deletionists (who tend to populate files policing to begin with) to do whatever the hell they want based on their own sometimes skewed and wrong personal interpretations of copyright law. Take such extremism to Commons if you want and stew on your juices there. Don't mess with what is working at en-WP, which has been successfully sued over file copyvio zero times and counting. Carrite (talk) 14:41, 28 November 2017 (UTC)
• Oppose. It's been my lengthy professional experience (working for a non-profit law firm for a decade as a policy analyst (IANAL) that people who think they understand copyright law almost always do not, and even those who really do know a lot can still frequently be wrong if they're not intellectual-property specialist attorneys who've been keeping up with caselaw and legislation closely (especially with regard to digital media). [And WMF is notoriously, excessively paranoid about copyright anyway; what we're allowed by WMF to do under fair use is only a fraction of what we actually legally allowed to do under that doctrine. While WMF does have exposure to legal liability for images that it should not be using at all (e.g. because someone uploaded something under false licensing), it has virtually none when it comes to reuse of promotional images (movie posters, publicity shots, etc.).]

  It's an admin's "job" to interpret and apply policy, not the law (and the law on this is much more about caselaw than about statutes at this point). When a legal question arises, the entire community in a consensus discussion is more apt to identify correctly whether there's a potential copyright problem that a lone-wolf admin who is not an attorney, or an attorney who's not an int-prop specialist. If WMF itself is concerned about this stuff, it can appoint staff counsel to review keep decisions at FfD and selectively override them by WP:OFFICE action. Or it can create a special class of admin with verified legal credentials in the relevant jurisdiction. Or come up with some other plan. But the notion that "I was trusted to become an admin because I seem sane and to be not a jackass" magically transmogrifies into "I know better than the community about copyright law just because I said so" is not viable. We have a lots of editors who are actual intellectual property attorneys, and they greatly outnumber the admins who are, and are likely a converge on FfD as an area of interest. If we have a consensus formation and assessment problem at FfD where people who really have no idea WTF they're talking about are !vote to keep images on a WP:ILIKEIT basis, a) this should be easy to detect, and b) we can provide specific "arguments to avoid in FfD discussions" at the FfD page, e.g. about arguing to keep a file, when copyright is at issue, without presenting an actually legally defensible rationale. "Admin knows best" is not the solution to this problem, if it is even a real one.
   — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  13:22, 29 November 2017 (UTC)

CaCL:Other

• If the laws of a country make any admin feel at personal risk of civil, criminal, or terrorist/paramilitary-mediated liability for upholding Wikipedia consensus, he should recuse himself and leave it to some member of the consensus (there must be many, after all) to decide what to do. Our policy should actually be to require he recuse himself in that position. (Note he would not be required to recuse himself if he honestly feels he is upholding consensus by following the law, which is far more common) Wnt (talk) 13:32, 5 November 2017 (UTC)
• This RfC is moot - copyright is one of those policies with legal considerations which isn't subject to consensus. Copyright-violating material is required to be removed immediately; any community consensus which conflicts with that is irrelevant. Ivanvector (^Talk/_Edits) 11:50, 19 November 2017 (UTC)
• The hard part is determining WHETHER the material violates copyright. Blueboar (talk) 16:17, 19 November 2017 (UTC)
• ’’’Moot’’’ per Ivanvector. As a policy with legal considerations, our policy on copyright is not subject to consensus. ~ Rob₁₃^Talk 21:37, 6 December 2017 (UTC)

CaCL:Discussion

• There has been an incident that facilitated the need for this discussion beyond Sandstein's removal of that part of the admin instructions for FFD. The no consensus close of an image that is clearly in violation of copyright. --Majora (talk) 20:42, 4 November 2017 (UTC)

  In the context of this specific example, I think the framing is somewhat wrong. An uploader (and those who support keeping files) have an affirmative burden of proof when it comes to establishing that the file meets our copyright restrictions. In such a discussion, I would suggest that a lack of consensus about whether copyright obligations have been met should generally be treated as delete result by default. In the absence of consensus, the need for a precautionary principle when it comes to copyright ought to favor deletion. Dragons flight (talk) 12:40, 5 November 2017 (UTC)

• Generally, when I see a discussion which seems to go counter to what would be disallowed (or permissive) under copyright law, I comment or skip. This is essentially a collision between copyright and Wikipedia:Consensus; Commons as a file repository is a lot more exposed to copyright issues so they give more weight to the first point. I think it's also the reason why Commons has no equivalent to WP:INVOLVED. Jo-Jo Eumerus (talk, contributions) 11:16, 5 November 2017 (UTC)
• Couple of points here. This is not about NFC. It never was and never will be. Non-free use is a completely different policy that has nothing to do with this. If you believe that this is about NFC please revisit your post.

  To those that are bringing up NOLEGAL. I don't see how that is relevant at all. Would you considering deleting things under F9 or G12 legal advice? I certainly hope not since that would cripple our ability to deal with copyright infringement. This is about the community being able to override legitimate copyright law via consensus or lack thereof (in the case of a no consensus close). Right now that is possible. This RfC is an attempt to rectify that. --Majora (talk) 01:15, 6 November 2017 (UTC)

  • Agree on the NOLEGAL point. Yes, we don't try to present legal advice to readers, but internally we have to be 100% of legal matters and implement policies like EL, BLP and NFC to comply with legal requirements, as best as we can interpret them. There are times we turn to WMF to help resolve matters, but they have charged us to keep content within legal allowances for US law. --MASEM (t) 23:15, 6 November 2017 (UTC)
• User:Marchjuly has very helpfully raised the matter at com:vpc where there has been a useful discussion. The position of "clearly in violation of copyright" does not seem to be supported. However, there seems to be sufficient doubt about the licensing of the image that Commons would not host the image because of Commons' Precautionary principle which is a matter of policy rather than law (and one I agree with). PRP is clear that what is relevant is whether there is significant doubt about whether an image is freely licensed. That is a different matter from whether its display here or on Commons is unlawful. My own view is that it is disallowed by policy but allowed by law (but I'm an internet dog). Thincat (talk) 11:53, 7 November 2017 (UTC)
• I think the "no consensus = keep" closes when it comes to file discussions is something that needs to be addressed. Such closes may be less problematic in other XfD discusssions, but when I comes to files I think they need to be seriously reconsidered. File copyright issues can be quite tricky and I am certainly no expert on them, but it does seem that in almost every case a file's licensing either clearly complies with WP:COPY or it doesn't, and in the latter case the default should not be to keep the file. Wikipedia should adopt an approach similar to c:COM:PCP in such cases and delete a file whenever significant doubts have been raised about its licensing.

In this particular case, there were a number of things that probably should have been considered before closing the discussion.

1. The actual link cited in support of the PD claim actually does no such thing:it states that most of the content found on the website is not copyrighted, but some might be copyrighted by others. This is quite common for government website, even US federal government websites, so assuming that something hosted by such a site has to be PD is often a mistake.
2. The EXIF data of the file shows that the copyright is not held by the organization given as the source of the file, but is actually credited to a different party, which means that it needs to be verified how this party licenses it content. If not clear, then clarification should be sought (perhaps at WP:MCQ).
3. Consideration also should have been given as to whether this file would be accepted by Commons. There's no reason for an official PD-licensed photo of a US state government official downloaded from one of the state's official websites to be hosted locally on Wikipedia and such files should (eventually) be moved to Commons. So, the administrator should've considered whether the file would be accepted by Commons. When there's doubt as to whether it would be appropriate to move the file per WP:MTC#Do not Transfer, then perhaps clarification should be sought at c:COM:VP/C. If a PD-licensed file of US origin is unlikely to be kept by Commons, there's no point in moving it, thus no point in keeping the file locally since the {{PD-ineligible-USonly}} cannot be used and {{Keep local}}/{{Do not move to Commons}} should not be used in a case like this.

So, unless the closing admin actually felt strong enough to cast a keep !vote, the FFD should have been (in my opinion) either relisted (with perhaps clarification sought at MCQ or COM:VP/C) to see if a stronger consensus could be established or should have been deleted without any prejudice against the file being restored at a later date via WP:DR if the PD claim is subsequently verified. I understand that this might be alot to ask for an adminstrator to do and appreciate all the admins who try to help and reduce the backlog at FFD, but I do think that perhaps that it would be better in most cases for an admin to pass on closing a discussion if they only feel confident enough in reaching a "no consensus = keep" close. -- Marchjuly (talk) 01:53, 8 November 2017 (UTC)

• TonyBallioni brought up the exact same thing to me a few days ago. It seems like a precautionary principle at FFD might be acceptable. But it would have to be specifically tailored to make sure it isn't gamed. The principle would not apply to any file being brought to FFD on fair use grounds, etc. That seems like a discussion that should be had in my opinion and would probably make this entire RfC moot. --Majora (talk) 02:09, 8 November 2017 (UTC)

@Majora and Marchjuly: the basic principle that I believe every admin who is working in any form of copyright deletions (text or file) should follow is this: if an administrator would be unwilling to take on the personal liability of restoring the content if it had already been deleted, and they are considering actively declining to delete it, they should let an admin who is more experienced with copyright issues handle the request, whether it be CSD, XfD, or revdel. This would address all the no consensus situations above when admins who are not familiar with copyright default to keep when a file would be eligible under one of the CSD criteria. TonyBallioni (talk) 02:47, 8 November 2017 (UTC)

@Majora: Nitpicky perhaps, but I think Wikipedia should try to maintain a distinction between non-free content and fair use because Wikipedia's policy is considerabally more restrictive than the US concept of fair use and different countries may treat "fair use" or refer to it differently (e.g., fair dealing than the US. It's easy for those not familiar with Wikipedia and the difference to treat them as one and the same, which is why it tends causes a fair amount of misunderstandings as expalined in WP:ITSFAIRUSE. Now having said that, I don't think non-free content use should be automatically excluded from any Wikipedia PCP because I've seen some "no consensus = keep" FFD closes for non-free files which also seem questionable. While it's true that not every FFD discussion regarding non-free content use involves immediate deletion, they do in a sense involve a discussion of Wikipedia's policies on using copyrighed content. I think it would be acceptable for deletion/removal via FFD per a Wikipedia PCP type of rationale because the burden for justifying non-free use seems to be strongly placed upon those wanting to keep/use a non-free file per WP:NFCCE. If there exists substantial disagreement as to whether a non-free use rationale which clearly shows how all ten non-free content criteria are met to the satisfaction of the community has been provided for a non-free file, the default fallback close should not automatically be "no consensus = keep/not remove". The discussion can be relisted as necessary, but if a consensus still cannot be achieved, then maybe the use should be disallowed per such PCP type of rationale. I understand that opinions on non-free use can be quite subjective, but if a consensus cannot be clearly established via a FFD that the a particular non-free use is justified per relevant policy, keeping the file as a default seems (in my opinion) to be a mistake. -- Marchjuly (talk) 03:23, 8 November 2017 (UTC)

There is definitely a line between what is an outright copyright failure that must be deleted immediately (eg someone posting something like the Flag Raising at Iwo Jima and claiming they are the owner of the copyright), and NFC problems which require a bit more care and human handling to make sure it is not small issues or consensus-based decisions to be made. Admins should be able to delete images on a precautionary measure if they are reasonable certain there is a copyright problem (eg clearly wrong license, clear lack of ownership to claim licenses, etc.). If they do have doubt (as would be commonly the case with works published overseas in the mid-20th century, which become embroiled in a mess of legalese), that should be discussed at MCQ or some other place to figure out the legal issue. Once that legal issue is dealt with, the rest of such images then become subject to NFC and image use policies, which means that's where consensus should be engaged. Admins can tag such images for removal, but this does require a 7-day period for editors to respond to and a second human review to delete. --MASEM (t) 16:59, 8 November 2017 (UTC)

@Masem, Majora, and TonyBallioni: I understand what you're all saying, but let me use Wikipedia:Files for discussion/2017 July 17#File:Robert Goldston01.jpg as an example of where I think some kind of c:COM:PCP-type of policy/guideline could also be helpful regarding an FFD discussions about non-free images. The file in question is of a individual who is presumed to be dead, but for whom no reliable sources can be found to establish that he is truly dead. So, per WP:BDP, such individuals are assumed to be living until the age of 115. The file was originally tagged for speedy deletion per WP:F7, but it was sent to FFD because being born in 1927 apparently means that an individual in unlikely to still be living. The file was nominated at FFD and the only response in favor of keeping the file was that BDP is unjustifiably long based upon a Wikipedia article about average life expectency,, which might be the case but which is not a justification for non-free use. FFD does not always attract lots of attention from the community at large and the FFD was relisted twice by two admins before by closed by a third admin as "no consensus = keep" with the comment "There aren't enough people interested in the issue to establish a consensus." After the FFD was closed, the application of BDP in this particular case was discussed at Wikipedia:Biographies of living persons/Noticeboard/Archive257#Robert Conroy Goldston and the consensus of one other admin and two very experienced editors (one who is now also an admin) was that it did apply and the use of the image should not be allowed per WP:NFCC#1. When the closing admin was asked to clarify the close, they seemed to give as a reason that a non-free file of the author in his prime would be better than a freely equivalent photo of the author at his current age, which is something that has really nothing to do with NFCC#1 and which is essentially a !vote which the admin should've been made in the FFD itself. Having to re-nominate this at FFD might have been avoided if there had been some PCP-type of guidance for admins that "no consensus = keep" should not be the default FFD close even for a non-free file whenever there are significant doubts raised about the file's use/license, and that either relisting or seeking further clarification at WT:NFCC or WP:MCQ (or even in this case at WP:BLPN) is preferred. If clarification had been sought, then perhaps the one of the three FFD admins would have learned that there is actually a pretty strong consensus which has been stable for many years that non-free images are, in principle, simply not allowed for identification purposes in articles about still living individuals, even long retired not publically active individuals, except in certain cases such as when the individual's Wikipedia notability is primarily based upon their physical appearance. FWIW, I am not trying to re-FFD this file here (the file can be nominated at FFD again), but just using it as an example how a default "no consensus = keep" close, even for non-free files, does not seem to work as well as it might in other XfD discussions and giving administrators a little more leeway/guidance might actually be a good thing. -- Marchjuly (talk) 14:34, 9 November 2017 (UTC)

See, that's a reasonable fair NFCC discussion, and the type of thing that an admin shouldn't step over "consensus" (of which there was no feedback for all purposes on that FFD). If the guy was alive or not is a fair question that we can't prove either way, but we can at least make reasonable guesses that both what their apparent age would be (115, unlikely) and the forum post that says he's likely dead, and thus we keep under NFCC allowances. We have to make some judgements like that, but none of that is a outright copyright violation problem that an admin should overstep. --MASEM (t) 14:39, 9 November 2017 (UTC)

• Do we have any indication of whether a discussion closer who allows a copyright violation to stand would be legally liable if they were wrong? And I am asking legally. Jo-Jo Eumerus (talk, contributions) 11:12, 11 November 2017 (UTC)

Well, it wouldn't be the first time that someone tried to bring legal action against an individual editor (e.g., [7][, [8], [9], [10]). Would they have enough knowledge of our deletion process to pin it on a particular closer? Would they succeed if they tried? That's probably speculation all the way down. I think the more interesting question that comes to mind, is if WMF were hit with a subpoena to reveal the identity of an editor who was identified to the foundation, would they have to comply with it? GMG^talk 12:16, 11 November 2017 (UTC)

comment: I would just like to point out that every single !vote supporting the nomination so far doesn't seem to recognize we already have a system of checks and balances in place for blatant copyright violations to be removed without question by any single user no matter what the consensus is. I see no point in granting "special privileges" to admins when they (and everyone else) already possess such a privilege. If the admin/s or editor/s in question did not know how to exercise such privilege in the case/s provided by the nominator, then I will suggest to you that this would be another example of why we should oppose special privileges. Admins are just as susceptible to misuse as anyone else. And, as I pointed out in my !vote, it would likely fail by having the opposite intended effect. It didn't work out for the Galactic Republic when they awarded Senator Palpatine special powers, and it will be bad for us too... :) Huggums537 (talk) 23:51, 23 November 2017 (UTC)

What are you talking about? Last I checked editors can't "remove" files. That would require their deletion which unless I slept through a seismic shift in Wiki-policy can only be done by admins. Are you thinking about text copyright? Text copyright can be removed by anyone by simply rewriting the content. Although that still requires an admin to intervene to actually rev'del it from the history. Sure you could remove any violating images from articles but that doesn't solve the problem. It still exists. --Majora (talk) 03:15, 24 November 2017 (UTC)

Sure, some things still require admin intervention. I stand corrected on that. However, those things which require admin intervention can easily be achieved by admins who already have the special powers to do so. That was my whole point. In any case, every editor does in fact possess the power to correct any one of these problems by way of proxy. They need only to enlist the assistance of any single admin to do so. This is all possible because the special powers already exist. One only needs to know how to access these powers to make use of them accordingly. Now that we have properly dispensed with my technical error, perhaps we could address something else in my statements other than just the minor mistake I made? (Please don't say you want to address my Star Wars references!) Huggums537 (talk) 06:54, 27 November 2017 (UTC)

I think you have missed the entire point of this discussion entirely. Could I have just asked another admin to delete the image? Sure. I probably could have gotten it done in two seconds if I really wanted to. I know plenty of admins that would have done it. That is really not the point at all. Me "accessing those powers" is completely irrelevant. The point is that the closing admin didn't want to "go against a lack of consensus" even though they were told by multiple people that the image couldn't be hosted here. Even though there was plenty of evidence that the image was not public domain and was actually F9'able. --Majora (talk) 02:45, 28 November 2017 (UTC)

I understand THE point just fine. Frankly, it's the only point that concerns me, and that point is simply if we should or shouldn't allow admins to have a special power. However, It is not really needed by your own admission, "I probably could have gotten it done in two seconds if I really wanted to. I know plenty of admins that would have done it." Furthermore, giving said powers introduces new problems, which have already been raised earlier in discussion. "I came across a stubborn admin who stood his ground, so give me special power" [paraphrased] is simply not reason enough for me to do so. I understand that may seem like an oversimplification to you since you have all these complex copyright/policy rationalizations to justify YOUR point, but this is how I sometimes like to reduce things to their simplest form in order to make the decision easier for myself. Thanks. Huggums537 (talk) 10:39, 28 November 2017 (UTC)

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 for changing the production section guidelines. 2

Please comment on the RFC here Thanks. --Deathawk (talk) 06:08, 6 November 2017 (UTC)

Remove "exception" to DEFAULTSORT guideline inserted on the basis of a 6-person, one-subject discussion

Someone's put the following into Wikipedia:Categorization of people:

Some people are known primarily by their first name only. When it is not possible to set the first name alone as the article title, as with many articles in Category:Brazilian footballers, you should sort with the first name first to make the article easier to find in the categories. For example, Leonardo Araújo is commonly known as Leonardo, and should be sorted as {{DEFAULTSORT:Leonardo Araujo}}.

It is proposed to replace this much clearer, narrower wording that does not have the WP:CONLEVEL policy problem of carving out a strange exemption for a single wikiproject:

Some people are known primarily by their first name (or a stage name) only. If an article's title is at that single name – alone, as in the case of Pelé, or disambiguated, as in the case of Pink (singer) – then do not use DEFAULTSORT at all; the article will automatically sort by the article title. If the article is at a full name (at least one given name and family name), sort normally in familyname, given name order. (Be aware that some cultures use family name first in natural language, so do not blindly assume that the last part of a subject's name is the family name); examples: {{DEFAULTSORT:Araujo, Leonardo}} Leonardo Araujo (often called simply Leonardo), and {{DEFAULTSORT:Utada, Hikaru}} for Utada Hikaru (often known as Utada).

The parenthetical about family name order could be put into a footnote.

[Clarified: 09:50, 12 November 2017 (UTC)]

Background and rationale

The current wording is obviously narrow-PoV instruction creep, and is completely pointless: If there's a genuine desire to have them appear in the categories under their first names for people familiar with them that way, this is done with categorized redirects, the same way we do this with any other subject, e.g. with a Leonardo (footballer b. 1969) redir to Leonardo Araujo. For any case where the full name is not actually the WP:COMMONNAME, then the page should be moved and disambiguated; we don't just "fake it" for category purposes by monkeying around with the DEFAULTSORT.

The justification for the current "rule" (in a footnote in the above-quoted material) is nothing but a single discussion at a sport wikiproject page, with a total of 6 participants, not all of them in agreement, dating to 2011.

This has led to disputes and "principle of least astonishment" bewilderment (here, most recently), plus the obvious category-sorting problem: People quite normally credited by a full name and at that name on WP, but also fairly often called by just their first name in a subset of (usually national/regional) news, are being sorted in firstname lastname order. Many of these subjects were not even alone in their sometimes-mononym, in the same context in the same place (e.g., multiple Brazilian footballers have popularly been called "Leonardo" in their heydays in the football/soccer press in Brazil).

Worse yet, Category:Brazilian footballers has become a complete trainwreck, with around 85% of the entries in it sorted by given name, due to people mistaking the original idea – an uncommon exception – for a standard to apply to any Brazilian footballer. I don't have the heart to check whether it's spreading to other footballer categories or other Brazilian sport categories (or even further) but I'd bet money on it.

Contrary to the current wording, this obviously does the exact opposite of make the articles easier to find in the category, since the entire world expects them in family-name-first order, and only people already very familiar with the subject, and probably from the same place where the subject is called by given name, would expect otherwise (if even then). Those few would also be less likely to be manually digging through a category for that subject, especially a massive one like Category:Brazilian footballers.

There's no evidence the current "rule" has consensus, just the support of less than half a dozen people with a shared micro-topical interest in popular football players in one country.
 — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  21:57, 10 November 2017 (UTC)

Comments on DEFAULTSORT revision

• Support: if someone is most commonly known by their forename only, then that should be the article title, with disambiguation such as "(Brazilian footballer born 1960)" as necessary; a redirect (or dab page entry or hatnote) should be made from their full name if given in the article. The DEFAULTSORT will be that single name.

If the article title is "Forename Surname", then the DEFAULTSORT should follow the normal rules for names of that nationality, usually "Surname, Forename". If the article states that they are also known by the single name, then there should be a dab page entry, hatnote or conceivably a redirect (if unique name) from that single name. End of story.

Not everyone who Wikignomishly edits an article on a Brazilian footballer will be a specialist in Brazilian football, and there is no convincing reason why this narrow exception should exist. PamD 22:34, 10 November 2017 (UTC)

• Comment: The text "then sort the article by the article title" should be "then do not use DEFAULTSORT at all". All articles, by default, sort according to the exact title, except where there's a DEFAULTSORT to make it something else. In other words, DEFAULTSORT is only ever required where it is desired the article be sorted by some key other than the exact title. This is why I've long thought the name "DEFAULTSORT" is an utter misnomer. It is only used when the default sorting (i.e. what you get when you do nothing) is exactly what is NOT required. -- Jack of Oz ^{[pleasantries]} 22:47, 10 November 2017 (UTC)

  Oh! Right. Duh. I'll fix that.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  03:41, 11 November 2017 (UTC)

• Comment: "sort normally by the conventions for the culture in question". Then the Brazilian ones are all incorrect. I'm Brazilian and we rarely talk to/compliment other people by using their surname, we only use forenames (one or two) - this is an American/European culture, not ours. Although I can't agree with @PamD's comments either, because if we use WP:COMMONNAME for all "Leonardo", all "Gabriel" that are or were Brazilian footballers and are or were known by their first names only, can you imagine the confusion of "(Brazilian footballer, born month year)"? MYS77 ^✉ 18:23, 11 November 2017 (UTC)

• Hmm, I wonder whether that's the case for scientists, lawyers, politicians, etc: would a list of Brazilian medical doctors be sorted into A-Z by forename, or by surname? That's what "Defaultsort" is about. .... Hmm, interesting: have found a couple of university pages where staff are listed in A-Z order of first names here and here. If this is really the norm for Brazilian lists of Brazilian people (rather than just lazy programming) then there needs to be an exception on the same basis as for Icelandic lists of Icelandic people. I suggest that WP:WikiProject Brazil needs to be consulted on this. PamD 19:18, 11 November 2017 (UTC)

Comment - Icelandic names are not Western-style names. They are patronymic and do not use inherited surnames. It is my understanding that Brazilian names in general are Portuguese-style, which is a modified form of Western style with a matronymic. Brazilian athletes typically use mononyms, which are a different special case. Is the real issue the mononyms used by Brazilian athletes, or the Portuguese-style nomenclature, which is modified Western, or something else? Robert McClenon (talk) 02:21, 12 November 2017 (UTC)

@Robert McClenon: You are correct, but Brazilian athletes use their surnames because they are appearing in an European/American-based competition, which has English as its main language and the sorting of surname, forename as its standard. A good example is Isaquias Queiroz: sorted by Queiroz, Isaquias in the Olympics/other competitions, he is known as just Isaquias in Brazil, per here, here, here and here. MYS77 ^✉ 14:11, 13 November 2017 (UTC)

• @PamD: That's what I've been trying to explain to @SMcCandlish and @GrahamHardy, sorting is not equal when it comes to Brazilian people (especially footballers)... Sorting Brazilian names by surname, forename is a rare exception. Even doctors here are listed by their forename. MYS77 ^✉ 21:44, 11 November 2017 (UTC)

• This list is a clear example of how sorting can be difficult when related to Brazilian people. The majority of these politicians are sorted by his forename, but there are some exceptions where they are sorted by surname. MYS77 ^✉ 21:46, 11 November 2017 (UTC)

@MYS77: The list of doctors you quote shows us nothing, as the people are listed there by job title not name. From the same website another list might have been useful but seems to be in random order within each of the two groups which I'd have expected to see sorted (A=Z by surname if British). The list of politicians is just mind-boggling. What would a printed telephone directory look like, I wonder? PamD 23:12, 11 November 2017 (UTC)

• PamD. This has nothing whatsoever to do with how people use spoken English (much less spoken Brazilian Portugese), only about what the family name is. WP (like 99% of the rest of publishers) sorts alphabetically by family name. The issue here is, thus, that Mao Zedong should be sorted as "Mao, Zedong", not "Zedong, Mao". I.e., people have to be aware which is the family name and not assume blindly that the last one shown in the name is it.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  09:44, 12 November 2017 (UTC)
  I've clarified the proposed wording to be much clearer.
   — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  09:50, 12 November 2017 (UTC)

RfC on naming of Chinese railway line articles

See also: § RfC: Russian railway line article titles

How should the titles of railway line articles for Mainland China and the high-speed railway in Hong Kong be named? Jc86035 (talk) 09:29, 11 November 2017 (UTC)

Background (naming of Chinese railway line articles)

Most article titles for Chinese railway lines follow the structure "Place 1–Place 2 Railway" or similar, though they have been inconsistently named and the naming guideline is probably a reflection of the state of articles rather than a fully consensus-based system. However, Dicklyon has recently renamed or made RMs for a number of railway lines to decapitalize them. (According to this PetScan query, out of about 270 railway lines and former railway companies, 174 are named with "Railway" and 86 are named with "railway". Dicklyon renamed all 86 of the latter this week.) Their naming should be based on reliable sources per MOS. A mix of non-capitalized and capitalized is used by sources for the more well-known high-speed railways, but more than 90% of sources use the capitalized form for the Guangzhou–Shenzhen–Hong Kong Express Rail Link (but a mix when the line is referred to as just the "Express Rail Link" or "express rail link"), and most news articles for the Beijing–Tianjin Intercity Railway use the capitalized form unless they refer to it without the phrase "intercity railway" e.g. "Beijing-Tianjin intercity route". There are very few English-language sources about the slow railways; 3 news sources use "Beijing–Kowloon Railway" and one source uses "Beijing–Kowloon railway", while others use "Beijing–Jiujiang–Kowloon [Rr]ailway". (Almost all passenger and freight lines in China are operated by China Railway and its subsidiaries, so it would probably be odd to capitalize them differently entirely based on the inconsistent capitalization of sources.) Further investigation is probably needed.

In addition, some articles are named in their abbreviated form, using only one Chinese character from each place name (e.g. Guangshen Railway instead of Guangzhou–Shenzhen Railway). Sources about high-speed lines usually use the long form. Most news articles about the Guangzhou–Shenzhen [Rr]ailway are actually about the subsidiary of China Railway which operates it, which is named with the abbreviated form. (The railway itself seems to never be in the news.) Most Google results for "Jingjiu railway" [Beijing–Kowloon] are Wikipedia articles; sources generally use the long forms. There is some old discussion in the archives of Wikipedia talk:Naming conventions (Chinese) which indicates that the long form should be used for clarity, although the highways also addressed by the naming convention have always been named using the short form (e.g. Guangshen Expressway).

Some articles are also named "Passenger Railway" instead of "High-Speed Railway". This is a result of the official Chinese names being literally translated; most English-language sources avoid "passenger railway" probably for clarity, although it's also possible that they used Wikipedia's article titles.

Note that my observation is probably incomplete and more web searches will be needed.

		A	B	C
Should the railway line articles be named with a capitalized "Railway"?	1	capitalized	not	case-by-case (i.e. based entirely on sources)
Should the railway line articles be named with the short or long form?	2	short	long	case-by-case
Should the railway line articles be named high-speed railway or passenger railway?	3	high-speed	passenger	case-by-case
Should the railway line articles be named intercity railway or passenger railway?	4	intercity	passenger	case-by-case
Should closed/historical/heritage/narrow-gauge railway line articles (e.g. Gebishi Railway, Jiayang Coal Railway) be named the same way as open railway lines operated by China Railway?	5	yes	no	case-by-case
Should the current and former railway company articles be renamed to match the line articles?	6	yes	no	case-by-case
How should railway lines with termini in Tibet and Xinjiang etc. be named?	7	Mandarin-derived name	local name	case-by-case

Survey (naming of Chinese railway line articles)

• 1B, 2B, 3A, 4A, 5C, 6B and 7C. (I am the RfC initiator.) Jc86035 (talk) 09:38, 11 November 2017 (UTC)

  See WP:JUSTAVOTE; why do you support those options?  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  13:31, 11 November 2017 (UTC)

  @SMcCandlish:

  • I am the initiator so my reasoning for 1B and 2B is largely outlined in the section above.
  • This needs to be double-checked, but 3A and 4A are sorted this way because the Chinese government seems to officially name high-speed lines "客运专线" (literally, "passenger dedicated line"). Some Chinese Wikipedia articles are named that way; others use "高速铁路" ("high-speed railway"). I don't know why. I have corrected "passenger line" to "passenger railway" since it is probably an editor's translation of the same phrase.
  • I !voted 5C since heritage railways may or may not be state-owned and thus may be named using a different system. Similarly, the name may be translated differently.
  • I !voted 6B since the company name does not need to be the same as and has little to do with the railway name; it would be a little like renaming c2c because the railway it operates on isn't called the c2c railway. The only operator for which this applies is Guangshen Railway (company), and the company is publicly listed internationally so it has an official English name which we don't need to change. The other operator [with an article] is Daqin Railway (company), which operates over multiple lines which are mostly not named the Daqin Railway. To be honest, this doesn't actually have much to do with the rest of the RfC, so maybe it could be removed.
  • I !voted 7B since the Chinese government apparently has an tendency to pretend that ethnic groups in the autonomous regions don't exist and only installs English-language signage based on the Mandarin Chinese transliteration rather than signage based on the Tibetan or Uyghur names. I've changed my preference to 7C.

  Jc86035 (talk) 15:30, 11 November 2017 (UTC)

• Remove WP:NC-CHINA#Transport as a bunch of no-consensus WP:CREEP – do not expand it further with this stuff. Not only does it directly conflict with site-wide guidelines like MOS:CAPS and WP:NCCAPS, it is not actually addressing anything unique to China and is thus off-topic – just one wikiproject PoV-pushing a bunch of trivial nit-picks without consensus. I checked – there was no discussion at WT:NC-CHINA about adding any of that material, and it's just someone's opinion, i.e. a mis-placed WP:PROJPAGE essay. It's also unnecessary (as I demonstrate below), because we already have title and sourcing policies, basic naming conventions, and style guides that result in usable article names simply by following them. I'm a huge fan of consistency within reason, but this RfC is just ridiculous. In case this nonsense is kept, I've answered the RfC questions below, with actual rationales, based on site-wide rules and advice.

Details, by number:

1B, 2C (2B by default), 3C (3A by default), 4C (4A by default), 5C (5A by default), 6C (6A by default), 7C (7A by default). Reasons: 1A is not actually an option (per MOS:CAPS, WP:NCCAPS, WP:NOR). 2C (2B by default) because these are usually descriptive names, in translation, so should be descriptive, but in the case that one is a proper name, use that. 3C per follow the sources; the choice doesn't even make sense, since "high-speed" and "passenger" are not synonyms and there are passenger lines that are not high-speed; if the railway is high-speed, use that by default as more descriptive. 4C (4A by default) per follow the souces; the choice the nom offers is another false equivalence, as there are passenger lines that are not intercity; for an intercity case, that word is more descriptive; but use whatever a proper name actually translates as. 5C (5A by default) per WP:CONSISTENCY policy, with allowance for a [translation or transliteration of a] proper name that doesn't fit the format. 6C (6A by default) per WP:CONSISTENCY and because not doing it (absent unusual proper name exceptions) invalidates the whole point of the RfC to settle on a consistent naming convention. It's utterly baffling that the nominator would pick 6B. 7C (7A by default) per COMMONNAME and follow the sources. Important note: "I saw it on a sign" does not equate to "proper name"; signs are primary sources self-published by the agency in question, and are written in an intentionally compressed fashion; they are not natural English. And the agency's own publication cannot be used to "style-war" for overcapitalization or other quirks, since WP doesn't follow external house style of random other organizations, and these names aren't in English anyway.

This kind of instruction creep is problematic, because if even a few topical-interest wikiprojects did something like this, MoS page by MoS page as WP:TRAINS has been trying to do, then a page like MOS:CHINA would be so long no one would read or follow anything in it. We should have no MoS rules other than those that address points of style and usage that editors have repeatedly had raucous conflicts about (or which address internal, usually technical, requirements) and which are not adquately addressed by existing WP:P&G pages. MoS/AT material is not a style guide for the public but an internal problem-solving tool. Every new rule added that isn't actually needed is just a reduction in editorial leeway and pisses people off.
 — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  13:31, 11 November 2017 (UTC)

@SMcCandlish: The last discussion about railways at Wikipedia talk:Naming conventions (Chinese) was more than six years ago. There probably aren't enough active editors to form a consensus, other than through the RM process (which probably isn't as widely trafficked as this page). I agree that some of these didn't really need to be in the RfC, but it made sense to ask them all at the same time to have a sort of more solid precedent than a RM from 2009 which ended in no consensus. It's a bit of a stretch to say that building consensus on these things is "instruction creep" and "ridiculous", since these are all (well, 1 to 5, anyway) points of inconsistency between article titles which no discussion has managed to sort out in the last decade.

I am also proposing this independent of the guideline and do not really care whether or not the guideline is changed to reflect it; I should have clarified this. I am fine with removing the guideline's section, since it only serves to reflect the status quo and has its own problems like introducing infobox title inconsistencies. Jc86035 (talk) 15:30, 11 November 2017 (UTC)

It's actually worse than that; it's a WP:POLICYFORK that contradicts the main guidelines on capitalization, among other problems.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  15:36, 11 November 2017 (UTC)

@SMcCandlish: Would it be acceptable to notify the Chinese Wikipedia of this RfC, or would that be canvassing? Jc86035 (talk) 04:28, 13 November 2017 (UTC)

I wouldn't. This doesn't have anything to do with what's done in Chinese, and zh.WP doesn't share our style guide.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  05:10, 13 November 2017 (UTC)

• Mixing style guidelines with naming conventions – 1B usually, since we have site-wide consensus represented in WP:NCCAPS and MOS:CAPS to reserve caps for proper names, typically as determined by consistent capitalization in sources, and these are pretty mixed in sources as nom notes. No new guideline or instruction is neeeded; see my RFC a few sections up where nobody disagrees with following these central guidelines. For the rest, these are more like project naming conventions; I agree there are some consistency improvements that would be useful. In terms of the current state, I started with downcasing "XXX High-Speed Railway", and then "XXX Intercity Railway" after studying sources about those. I would plan to look next at "XXX Passenger Railway" and plain "XXX Railway". In many parts of the world, the latter form is typically referring to a company, and is capped, while the railway infrastructure is called a "line". So I need to look at what's going on here. Any help you care to offer will be appreciated. Dicklyon (talk) 17:02, 11 November 2017 (UTC)

Comment It is a proper name in Chinese and just lost in translation in English and by grammar it should be capitalised (the Chinese government had a system to name it, does not mean it is not a proper name, such as the First Bridge of "Long River", the Frist Road of People, or People East/West/North/South Road. Or Shenzhen Airport. Beijing International Airport. Matthew_hk tc 03:24, 13 November 2017 (UTC)

@Matthew hk: I don't think this is necessarily the case, as English grammar norms are a little different from those of Chinese. For example, the zhwiki article for Shenzhen is called 深圳市 (Shenzhen City), but our article is titled simply Shenzhen because we don't consider "City" to be part of the proper name and it's not necessary for disambiguation. Jc86035 (talk) 04:28, 13 November 2017 (UTC)

Yep.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  05:10, 13 November 2017 (UTC)

What I saw is wikipedia screw with no sense that Australia use English language and capitalize Fremantle Line [11] in their webpage and the wiki lower cap them. Matthew_hk tc 06:06, 13 November 2017 (UTC)

Yes, we "screw with" some of their styling, since they're not even consistent (see [12]) and since we go by secondary sources. Dicklyon (talk) 06:35, 13 November 2017 (UTC)

And more citation on Chinese railway: Hsü, Immanuel C.Y. The Rise of Modern China. Oxford University Press., a history book written in English (by a guy with Chinese surname publish by a reputable university press) use Wade–Giles, uses Peking-Hankow Railway, Canton-Hankow Railway Matthew_hk tc 06:46, 13 November 2017 (UTC)

He also has "Fengtien-Peking and Tientsin-Pukow railways", which would seem unlikely if their proper names were Fengtien-Peking Railway and Tientsin-Pukow Railway. Things like "Southern Manchurian Railway track" that he has make more sense, as referring probably to the company South Manchuria Railway Company as opposed to the line. Anyway, he has a style, but it's not WP style. Dicklyon (talk) 03:16, 6 December 2017 (UTC)

Here I will comment that there is no such thing as a "South Manchuria railway" as a single line. The South Manchuria Railway operated a number of lines, of which none were called the "South Manchuria Line". For the record, they were called the Lianjing Line (Dalian–Xinjing/Changchun), the Anfeng Line (Andong/Dandong–Fengtian/Shenyang), and the Jincheng Line (Jinzhou–Chengzitong).2Q (talk) 03:35, 19 December 2017 (UTC)

Comment: If we in proper English capitalise "Hollywood Boulevard" or "Fifth Avenue" or "Crescent City" or "Brooklyn Bridge", then these cases of railways wherein 'Line' is part of the proper name need to be capitalised too. Though I'm thinking more specifically of Korea and Japan, but applicable elsewhere too, including China. Secondly, there are/were numerous railway lines in Hamgyeong Province, or in the Tohoku region ... saying "Hamgyeong line" (or "Tohoku line" etc) is not specifically referring to any of said lines, whereas "Hamgyeong Line" ("Tohoku Line" etc) is specifically referring to the one line that is commonly known by that name.

I know in China railway lines are called 鐵路 (railway) and not 線 (line), but I'd say the same thing applies. Proper names are capitalised, this is a basic and universal rule of English orthography. 2Q (talk) 02:04, 27 November 2017 (UTC)

• Avoid instruction creep. (Basically "C" in all cases above [where not in conflict with MOS:CAPS, etc.].) WP guidelines aren't for us to neatly order the lamentably inconsistent real world; they are created as a last resort to help editors focus on improving articles rather than waste time endlessly bickering about small things without resolution. Here, I don't see a long-standing ongoing conflict that needs some WP guideline to come down and make decisions for us. Especially in this RfC, where we are asked to !vote on a list of different rules for different small sub-subjects. This requires anyone commenting get detailed knowledge for each separate issue, which an RfC is the worst way to achieve. I'd close this RfC as a bad idea no matter what the outcome. (Maybe start a separate RfC for each issue where needed.) --A D Monroe III^(talk) 16:12, 30 November 2017 (UTC)

Korea exception?

Is Korea different from China? I started downcasing a few lines in Korea, but got reverted by 2Q. See discussion at User talk:Dicklyon#Undid page moves. The argument seems to be that since Korean and maybe other Asian languages have no analog of capitalization, and even though there's not consistent capping in English-language sources, we must nevertheless treat these line names as proper names. Anyone buy that? Dicklyon (talk) 03:31, 29 November 2017 (UTC)

Not on your life; the fact that CJK scripts have no case distinction means we absolutely should use lower-case here because our translations of them are just approximations and thus cannot be their proper names. We have the same rule when it comes to translating titles of published works: the translations go in sentence case. (However, the English-language title of an English-language edition of a book, or English-dubbed/subtitled English-language-market release of a film, or traditional English name of a famous artwork, goes in title case.)  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  13:31, 29 November 2017 (UTC)

I don't see how the Korean language has any influence here. Per COMMMONNAME, The naming we follow is based on English, not uses in other languages; we don't call Germany Deutschland. If English sources cap it, then we should, especially when the native official language has no caps. I'm sure the French Wikipedia doesn't look to English sources to determine if "Basketball" is a masculine or feminine noun, a concept English doesn't have. --A D Monroe III^(talk) 15:39, 30 November 2017 (UTC)

In User_talk:Dicklyon#South_Manchuria_Railway, User:2Q makes a case for capping "Line" for Japan and Korea lines. It makes more sense than I've seen elsewhere (more than for the NYC subway lines, for instance). Comments? Dicklyon (talk) 06:06, 17 December 2017 (UTC)

US or NYC exception?

There is also some pushback on capitalization normalization of "Line" in New York, in spite of sources using lowercase a lot. See ongoing RM discussion at Talk:IRT_Lexington_Avenue_Line#Requested_move_17_November_2017. The notification of the project has brought in some local opposition based on their longstanding practice of capping "Line". Dicklyon (talk) 16:30, 29 November 2017 (UTC)

Hong Kong exception?

I've downcased the majority of Chinese XXX Railway articles, and working away on them; a few seem to be consistently capped in sources, and a few have a little pushback for other reasons (2Q also comments on some of those). But it's when I mess with things that get into Hong Kong that I find more pushback, especially on downcasing Station (e.g. see Wikipedia_talk:WikiProject_Hong_Kong#Railway_and_Station_capitalization and User_talk:Dicklyon#Why_are_you_even_allowed_admin_tools?). And I continue to get random comments from the banned/sock Russia anon for my work there, sprinkled into some of these conversations. I'm going to hold off on Japan and Korea, go slow on Hong Kong, and see how things go as I try to finish up China. Comments? Dicklyon (talk) 06:06, 17 December 2017 (UTC)

On the Hong Kong MTR stations, I've opened a mulit-RM discussion: Talk:Hung_Hom_Station#Requested_move_17_December_2017. Dicklyon (talk) 16:55, 17 December 2017 (UTC)

Strong opposition and motion for reconsideration

As the creator or editor of the vast majority of China railway articles in English Wikipedia, I am appalled and deeply dismayed that this de-capitalization exercise was undertaken with little to no input from the editors who are familiar with the content of this subject area and laid down the conventions for article in naming, as a means to help readers identify the articles they are reading and editors to help expand the subject area.

First, the naming convention which I proposed and was adopted in 2011 after significant discussion with other China railway editors, has worked. See Archive 11 (reproduced below). Until Dickylyon started de-capitalizing high-speed railway names, virtually all articles about particular railways in China had "railway" capitalized in the same way that Great Western Railway, Trans-Siberian Railway and Union Pacific Railroad have railway/railroad capitalized in their names. The capitalization signifies that the article name is referring to a particular railway, and the names of particular railways are proper nouns. Per MOS:CAPS, proper nouns are capitalized.

This section is weirdly broken and not editable, having sections inside the collapsed part. How about a link to the relevant archive instead? And did these proposals ever get adopted or documented any place, or just discussed? Dicklyon (talk) 05:16, 20 December 2017 (UTC)

And trying to edit sections after this also doesn't work so well; the edit button usually leads to the wrong section number. Dicklyon (talk) 05:53, 20 December 2017 (UTC)

The 2011 discussion and consenus

For article names of Chinese railways, replace transliterated shorthand names with hyphenated full names Under the current naming convention, Wikipedia English article names of Chinese railways (and expressways) follow the shorthand Chinese character names for these railways (and expressways) transliterated into English. For example, the Beijing-Shanghai Railway is named Jinghu Railway, after the shorthand of the Chinese name for this railway, 京沪铁路. Jing is the pinyin tranliteration for 京, the character used in Chinese as a shorthand for the city of Beijing. Hu is the pinyin transliteration for 沪, the character used in Chinese as a shorthand for the city of Shanghai. Beijing and Shanghai are the two terminal cities on the railway. For ease of reference, let’s call Jinghu Railway the “transliterated shorthand name” and the Beijing-Shanghai Railway, the “hyphenated full name”. The transliterated shorthand name, while seemingly faithful to the Chinese naming method, is not helpful or effective for most English Wikipedia readers and fails to satisfy most of the objectives under Wikipedia’s article naming convention, which are recognizability, naturalness, precision, conciseness and consistency. This naming convention should be replaced by hyphenated full names of Chinese railways, which has the two terminal location references (usually cities but also could be provinces) of each railway fully spelled out and connected by a hyphen. This hyphenated name should be followed by “Railway”, capitalized because the name of each Chinese railway is a proper noun. The transliterated shorthand name could be mentioned in the article and could have a redirect link, but should not be the primary article name – for the following reasons: Recognizability – an ideal title will confirm, to readers who are familiar with (though not necessarily expert in) the topic, that the article is indeed about that topic. The names of most railways in China, regardless of naming method, are not familiar or recognizable to most English Wikipedia readers. When this is the case, the more descriptive name will make the railway more identifiable. For example, most English readers are unfamiliar with, say, the railway between Chengdu and Chongqing, but between Chengyu Railway and the Chengdu-Chongqing Railway, they’re much more likely to identify the latter as the railway between the two cities. As of April 22, 2011, articles for only a handful of railways in China have been created and named with the transliterated shorthand name method. Most of these articles are for railways that many bilingual (Chinese and English) readers can recognize, such as the Jinghu, Jingguang, Jingjiu, Jingbao Railway, so the naming convention appears to be fine. Yet, once we expand the article coverage to railways that are less well-known, recognizability of names will diminish. Railways like the Funen, Kuybei, Qibei, Nenlin, are likely to be as obscure to the English reader as they are to the bilingual reader. As the number of articles proliferates, the article names will become progressively more difficult to recognize and tell apart. Try telling apart the following railways: Fuhuai, Fuxia and Funen. Part of the difficulty is that the transliteration method obscures differences in Chinese characters and Chinese tones that help to pick apart some of those names, such as 阜淮, 福厦, 富嫩 in the riddle above. Compared to the shorthand names, Fuxin-Huainan, Fuzhou-Xiamen, and Fuyu-Nenjiang, are more recognizable. With pinyin transliteration from Chinese to English, considerable detail and discerning information is lost. Consider more examples: Xiangyu, Xianggui, Xiangpu Railways all have different “Xiang” characters; Baolan and Baocheng Railways have different “Bao” characters; Jiaoji and Jitong Railways have different “Ji” characters; Jiaoji and Jiaoliu Railways have different “Jiao” characters Jitong and Tongpu Lines have different “Tong” characters; Lanxin and Lanyan Lines have different “Lan” characters; Qibei and Ningqi Lines have different “Qi” characters; Tongjiu, Tongpu, Jitong Railways have different “Tong” characters Xianggui and Guikun Lines have different “Gui” characters; Yiwan and Wangan Railways have different “Wan” characters; Yiwan, Yijia, and Xinyi Lines have different “Yi” characters; Yuli and Licha Railways have different “Li” characters; Many English readers may be unfamiliar with one-character abbreviations of Chinese cities and provinces that are commonly used in Chinese shorthand names for railways, Hu for Shanghai, Yu for Chongqing, Rong for Chengdu, Ning for Nanjing, Yong for Ningbo and Jiu for Kowloon. Compare Beijing-Kowloon Railway with Jingjiu Railway. Just when you thought Jing stood for Beijing, there is Jingsha Railway, between Jingmen and Shashi in Hubei Province. Part of the difficulty is that the Chinese method itself is vulnerable to confusion due to the repetition of the same characters used to describe different location. Consider Changda (长大), Xinchang (新长), and Daqin (大秦) railways. These three lines have two pairs of Chang and Da characters in common but those two characters refer to four different cities: Changchun, Changxing, Dalian and Datong. When these homographs characters are transliterated into the English, the confusion they cause is compounded by their homophone characters. Joining the Da (大) railways, e.g. Daqin (大秦) and Dazheng (大郑), are the Da (达) railways – Dacheng (达成) Dawan (达万) Railway. Joining Chang (长) railways are other Changs such as (昌), as in the Changjiu (昌九) Railway. Naturalness – refers to the names and terms that readers are most likely to look for in order to find the article (and to which editors will most naturally link from other articles). How are the names of Chinese railways referred to in English publications? A search in the English news articles for Beijing-Shanghai Railway yields hundreds of results. A search for Jinghu Railway yields few to no results. In everyday use, when an English writer wants to identify a Chinese railway in English prose to an English reading audience, he/she is much more likely to use the hyphenated full name approach than the transliterated shorthand name approach. Precision – titles are expected to use names and terms that are precise, but only as precise as is necessary to identify the topic of the article unambiguously. Not surprisingly, the hyphenated full name is more precise and less prone to confusion than the transliterated shorthand name. For example, does Xinyi Railway refer to the railway between Fuxin and Yi County (新义铁路) or the railway of Xinyi (新沂铁路), which goes to Changxing? What about the Ningwu Railway, is it one of the railways that originates from Ningwu or the Nanjing-Wuhu Railway, whose transliterated shorthand is also Ningwu? Conciseness – shorter titles are generally preferred to longer ones. This is the only consideration where the transliterated shorthand name appears to have the edge. But this objective is far outweighed by others consideration. The hyphenated full name is hardly long by Wikipedia article name standards. Furthermore, as a rule, in Wikipedia, we do not use abbreviations as article names. Why adopt Chinese abbreviations as the official English names? Consistency - titles which follow the same pattern as those of similar articles are generally preferred. As noted, news articles about railways overwhelmingly follow the hyphenated full name approach. Among China’s high-speed railways, the majority also following the hyphenated full-name approach, because this approach delivers more identifying information and is less prone to confusion. It’s time to make the English article names of Chinese railways consistent, clear and descriptive. The need for hyphenated full names for Chinese railways is more pressing than it is for Chinese highways. Whereas railway names are stable, highways in China frequently have their names changed as expressways are lengthened and numbering systems are adopted. As an encyclopedia, we want to present seemingly complex information to readers in a way that is clear and consistent and easy to understand and follow. Under the hyphenated full name approach, readers can tell right away, what the two terminal cities of any railway are, and if they can recognize one of the two cities, be able to orient the railway. They will be able to tell that the Nanjing-Xian (Ningxi), Nanjing-Wuhu (Ningwu) and Nanjing-Qidong (Ningqi) Railways do not originate from the same city as the Ningwu-Kelan (Ningke) and Ningwu-Jingle (Ningjing) Railways. For consistency and clarity, Wikipedia article names of Chinese railways should always feature the full names. In-article references can use transliterated shorthand names. The only exception may be the Longhai Line, which has become a two-character word in itself. The reason for this lengthy argument is because prior attempts to convert transliterated shorthand article names into hyphenated full names have been reversed with reference to the naming convention. ContinentalAve (talk) 15:14, 22 April 2011 (UTC) I will refuse to agree to anything regarding railways unless something is done to expressways as well. Since expressways follow about the same convention, with the only conceivable difference being the addition of the "G__" numbering system, it makes little sense to have 2 separate conventions. Also, I am pretty sure that you fell for the pitfall of not using " " (i.e. exact phrasing) when doing Google searches. HSR, since they have been built only recently, are mentioned using the Terminus 1-Terminus 2 format in most media sources. And with regards to "most English Wikipedia readers"... that's not the most important issue to be considered here, and probably should not be one. Precision far eclipses recognisability; you pointed this out. Full transliteration often creates disambiguation. --HXL's Roundtable and Record 00:15, 23 April 2011 (UTC) HXL:Appreciate your prompt response. Regarding the highway naming convention: Sure, we can certainly adopt the same full-name approach for highways. i.e. G12 Hunchun-Ulanhot Expressway instead of G12 Hunwu Expressway. Regarding the Google searches: the point here is that more English writers use the full-name approach than the transliterated shorthand approach because the former is more natural. This is true whether we are talking newly built HSRs or longstanding regular speed railways. A search for "Beijing-Shanghai Railway" (in quotes) yields 269,000 results on Google, whereas "Jinghu Railway" (in quotes) yields only 77,000. The "Baotou-Lanzhou Railway" has 16,100 results and "Baolan Railway" has only 1,010 results. Regarding most "English Wikipedia readers": I would not dismiss them so readily from our consideration of naming conventions. Wikipedia exists for their and our use. Two criteria in Wikipedia's naming convention -- recognizability and naturalness -- are based on the reader's experience. While it is true that many of the railway and expressways in China are currently unfamiliar to English readers (and therefore not recognizable to them), Wikipedia can help to change that through the creation of articles about them. This is why it is important for the names of these articles to be helpful, descriptive and memorable. Over time, many of the railways and expressways in China will become more recognizable. How we name them can have quite a lot to do with how quickly they gain acceptance. Precision versus Recognizability: If I read your last point sentence correctly -- Full transliteration often creates disambiguation. -- then you're in agreement with me that using the full-names of these railways and highways creates less ambiguity than the shorthand names, not just often, but almost always. Thank you for your attention. ContinentalAve (talk) 14:36, 23 April 2011 (UTC) To be clear, it is not that I am necessarily opposed to the proposal, but I am concerned about some of the wording of the rationale. Indeed, I will come out and say that full spelling is required in all cases where ambiguation with even one terminus is possible (i.e. Nanjing). --HXL's Roundtable and Record 14:52, 23 April 2011 (UTC) I am fairly neutral on the proposal; but, as one data point, there were 455 results when searching on "beijing-hankou railway" on Google Books; 26 and 35 results when searching on "jing-han railway" and "jinghan railway", respectively. (Among them, there must have been a few "pseudobooks", created by a parasitic publisher from Wikipedia pages; but the number was small enough as not to affect the overall results significantly. There were also a few hits with "chinghan", "beiping-hankow", etc., but again to few too affect the overall ratios). -- Vmenkov (talk) 15:50, 23 April 2011 (UTC) I broadly support this. I am far from proficient in Chinese but recognise many place names, including most cities. But the short names really make no sense to me, i.e. on encountering them I would need to look for the longer full name to understand what is being referred to. I suspect only those proficient in Chinese would recognise the short names, and such people are unlikely to be using the English Wikipedia as a reference for the Chinese railway system. It seems that broader usage agrees with this, based on the searches done. There will still be redirects for those that are searching by the short names, but the full names are more appropriate for the article titles.--JohnBlackburnewordsdeeds 16:26, 23 April 2011 (UTC) I appreciate the helpful input from everyone. HXL, I understand your reluctance to change a long-standing policy but your proposed solution of spelling out the full name only when there is ambiguity with the abbreviated name will prove to be difficult to implement. For one, many writers will not be aware of ambiguities because they haven’t considered the whole galaxy of railway and expressway names. This is why I have gone through the effort of creating a very long post with many examples to illustrate the problem. Only when you consider the Ningwu-based railways will the Nanjing-based railway names seem ambiguous. Second, as we all know, China is undergoing extensive infrastructural expansion and the number of highways and railways will proliferate and create new ambiguities. For example, Hubei and Hunan are building a railway between Jingmen and Yueyang called the Jingyue Railway. The Jingyue along with the Jingsha Railway will start to erode the distinctiveness of Jing for Beijing in English. It will be more and more difficult to tell whether the Jingyuan and Jingzhang Railways are really obscure railways linked to Beijing or somehow related to the Jingyihuo Railway in Xinjiang. If Jing can be made ambiguous, no one is safe. Third, Wikipedia is the place where old knowledge finds new life. Many historical railways in China, like the Jinghan, will have articles created for them. Their inclusion will compound the potential for ambiguity. The earlier we adopt a clear and consistent policy, the less uncertainty and difficulty there will be for article creators going forward. After all, you were the one who opposed bifurcating railways from highways! :P Set forth below, is my proposal of the revised naming convention for the transportation section: Transportation When naming articles of expressways, highways, railways, railway stations, or airports in China, use the common English name if it can be determined, e.g. Karakorum Highway. Otherwise, follow these naming rules for the article name: For roadways, highways, expressways and railways whose names in Chinese consist of two- or three-character abbreviations of the terminal cities (or other location names), do not adopt the pinyin version of the Chinese abbreviated name as the English article name. Instead, spell out the full English name of each abbreviated Chinese place name and connect them with hyphens in the article name: For the 宁芜铁路, use Nanjing-Wuhu Railway as the article name not, Ningwu Railway. The {[full English spelling of terminus 1][hyphen][full English spelling of terminus 2] [Expressway/Railway]} article naming format is intended to identify expressways/railways with precision and avoid ambiguity. E.g. In addition to the Ningwu Railway, there are Ningwu-Kelan and Ningwu-Jingle Railways. The pinyin version of the Chinese abbreviated name should be mentioned in the first sentence of the article as a secondary name of the expressway/railway, and should be made a redirect link to the article. Furthermore, the pinyin version of the Chinese abbreviated name can be freely used in the article itself and in other articles. The rule above applies only to article names. Where there is ambiguity in the pinyin version of the Chinese abbreviated name, create a disambiguation page for the ambiguous name. Nanfu Railway may refer to: Nanchuan-Fuling Railway, a railway in Chongqing under construction since 2008. Nanping-Fuzhou Railway, a railway in Fujian built in 1959. Please capitalize Expressway/Railway in the article name. Railways 京九铁路 - Beijing-Kowloon Railway not Jingjiu Railway 宝成铁路 - Baoji-Chengdu Railway not Baocheng Railway 皖赣铁路 – Anhui-Jiangxi Railway not Wan'gan Railway 精伊霍铁路 - Jinghe–Yining–Khorgas Railway not Jingyihuo Railway Where the pinyin spelling of a place name differs from the official English spelling of the place name (especially in the case of non-Chinese place names) use the official English spelling. 滨州铁路 - Harbin-Manzhouli Railway not Haerbin-Manzhouli Railway Use the same naming format for China's high-speed railways 武广高速铁路 - Wuhan–Guangzhou High-Speed Railway not Wuguang High-Speed Railway Exceptions to hyphenated full-spelling naming format: Where the Chinese name is descriptive, use a brief translation of the descriptive name: 北疆铁路 - Northern Xinjiang Railway not Beijiang Railway. Where the abbreviations in the Chinese name are no longer considered abbreviations. This usually occurs when the abbreviated name has survived changes in the underlying names. 陇海铁路 - Longhai Railway not Longxi-Haizhou Railway because Longxi is no longer used to describe eastern Gansu Province and Haizhou is now part of Lianyungang Roadways For [[13]], add the expressway number as a prefix to the hyphenated expressway name in the article. The prefix and the hyphenated expressway should be separated by a space. 京沪高速公路 - G2 Beijing-Shanghai Expressway 京承高速公路 - S102 Beijing-Chengde Expressway The pinyin version of the Chinese abbreviated name should be mentioned in the first sentence of the article as a secondary name of the expressway and should be made a redirect link to the article. For National Highways that are numbered simply follow the format {China National Highway [number]}: 国道102 - China National Highway 102 National Highways can be abbreviated with "G{no. of highway}", e.g. G105 as a redirect link for China National Highway 105. Railway Station Articles for railway stations in China should be named using the city's name (or in some cases the station's unique name— for example, 丰台火车站) followed by the English translation of the cardinal direction in the railway station name, if applicable (North, South etc.), and then [Railway Station]: 北京站 - Beijing Railway Station 北京西站 - Beijing West Railway Station 丰台火车站 - Fengtai Railway Station Abbreviated forms of the railway station name should be mentioned in the article's first sentence as secondary names and should have redirect links to the article name. Beijing West Beijing South Station Airports Airport articles should have the city's name followed by the [airport's name] if applicable, followed by [International Airport] or [Airport] as applicable: 北京首都国际机场 - Beijing Capital International Airport 上海浦东国际机场 - Shanghai Pudong International Airport 广州白云国际机场 - Guangzhou Baiyun International Airport ContinentalAve (talk) 19:01, 23 April 2011 (UTC) Revised ContinentalAve (talk) 08:05, 1 May 2011 (UTC) I am not opposed to this proposal. Sounds sensible and reasonable for the large readership who doesn't understand the abbreviation used in Chinese. The short names are usually used in mass media. As such, I assume these will be redirects to the full hypenated names. --Visik (Chinwag Podium) 02:31, 29 April 2011 (UTC) This proposal sounds eminently sensible and generally excellent. Hear hear! Jpatokal (talk) 10:01, 29 April 2011 (UTC) I agree with the proposal as well. It may be appropriate, however, to explicitly say in the policy that the "two-syllable" names of railways and highway (Jinghu Railway etc) should also be mentioned in the lede of relevant article. -- Vmenkov (talk) 15:11, 29 April 2011 (UTC) Thank you for everyone's suggestions. I have incorporated your input about the need to mention the Chinese abbreviated name in the first sentence of the article and to have redirect links created for the Chinese abbreviated name. ContinentalAve (talk) 08:05, 1 May 2011 (UTC) By the way, you probably will need to clarify the new policy a bit once certain ambiguities are found. For one, I am not entirely supportive of reducing "Terminus A–B County" to "Terminus A–B". Secondly, cases where the article title of a terminus (i.e. X City or Y County) is not at X or Y County, respectively, due to the existence of other settlements of the same name, need to be dealt with. With romanisation, the reader cannot always know which "X" or "Y County" is being referred to. To begin with, a solution is to use "X City" in the title if there are no other officially-designated cities of the same name. I don't know about the other 2 cases for now. –HXL's Roundtable and Record 04:51, 13 May 2011 (UTC) Endorse, though of course, some wording needs to be changed. My experience with disambiguating town, township, and subdistrict divisions is frustrating enough; no two counties or county-level cities in mainland China share the same name in Chinese but then when romanising, many counties and county-level cities are "repeated" across provinces when fully romanised. Applying this sentiment here, the precision point alone is enough grounds for me to support the policy change. And sorry for the delayed response; have been busy with what I alluded to above...check my contribs if you wish to know. –HXL's Roundtable and Record 04:44, 13 May 2011 (UTC) HXL49, thank you for the endorsement, thoughtful reply and questions. In general, the Terminal A-Terminal B naming method should follow the unabbreviated Chinese place names used to identify the terminals in the name of the railway itself, even if those place names are different from the actual place names currently used to name the places in which the terminal is located. What do I mean? Generally, there is no difference between the place name used to identify a terminal in the name of the railway and the place name in which the terminal is located. E.g. The Yingtan-Xiamen Railway refers to the railway between Yingtan and Xiamen. However, consider the 临策铁路 Linhe-Ceke Railway. The railway was planned when the eastern terminal city was called Linhe. Linhe has since been renamed Bayan Nur, but the underlying railway name still uses the abbreviation for Linhe 临河. Since we are naming articles of the railways, not the place names, we should adhere to the Chinese place name used in the railway name and maintain Linhe-Ceke Railway, not Bayan Nur-Ceke Railway. There are instances where the terminals of a railway are not actually located in the place identified in the terminal place name. For example, the Qiqihar-Bei'an Railway begins in the station of Angangxi, near Qiqihar but not in the city itself. Since the railway name uses Qiqihar as the terminal place name, the article name follows with Qiqihar-Bei'an Railway, not Angangxi-Bei'an Railway. In the first paragraph of the article, there should be a clarification of any differences between the location of the actual terminal and the place suggested by the terminal name referenced in the name of the railway. Consider an opposite example, 南福铁路 Nanping-Fuzhou Railway, was built in 1956 as a branch of the Yingtan-Xiamen Railway. This railway begins in the west at the 外洋 Waiyang Station on the Yingxia Line. Waiyang is located in 来舟 Laizhou, a township of Nanping. Initially, this was the only railway near Nanping and was called the Nanping-Fuzhou Railway. Later as other railways were built into Nanping itself, the line took on 外福铁路 Waiyang-Fuzhou Railway and 来福铁路 Laizhou-Fuzhou Railway as alternate names. In English Wikipedia, an article name has been created for each of the three names. Currently, Waiyang-Fuzhou and Laizhou-Fuzhou redirect to Nanping-Fuzhou because all three names are now considered to be historical names since most of the line has become part of the Hengfeng-Nanping Railway. Nanping-Fuzhou was the first name for the line and remains the most intelligible. The point here is that the article name should follow whichever Chinese place names are used in the Chinese railway name. Quite a few railway terminals are named after and located in counties. See Ningwu-Jingle Railway. If I understand you correctly, I don't think you are calling for this line to be named Ningwu County-Jingle County Railway, since there is no ambiguity with Ningwu or Jingle. I think the more tricky scenario you alluded to is when one of the terminal names when romanized into English is itself ambiguous. Consider the 新义铁路, which when translated under the general rule, becomes the Fuxin-Yi County Railway. But there are several "Yi Counties" in China, and this could lead to some confusion. I do not see a definite solution, but see several options: (a) Fuxin-Yi County Railway. Leave it as is. There may be several Yi Counties in China, but only one Fuxin-Yi County Railway. When the reader clicks through, the first sentence of the article should explain which Yi County the railway connects to. (b) Fuxin-Yi County (Liaoning) Railway. This approach completely disambiguates Yi County. (c) Fuxin-Yi County Railway (Liaoning). This approach explains that the entire railway is located in Liaoning, which should dispel any ambiguity about which Yi County is being referred to, but might give the misleading impression that there is another Fuxin-Yi County Railway in another province. I'm indifferent. What do you and others think? ContinentalAve (talk) 08:33, 15 May 2011 (UTC) Agree with comment. The titles should use En dashes instead of regular ones. Therefore titles like Beijing-Kowloon Railway should actually be Beijing–Kowloon Railway.  –Nav  talk to me or sign my guestbook 13:45, 30 June 2011 (UTC) Who approved this new change? It was not like this before. Python eggs (talk) 01:49, 3 July 2011 (UTC) That's the key idea behind "change". You can see through the history that a proposal was put into place back in April and nobody posted any oppositions for the entire two months that the discussion was open. See this section.  –Nav  talk to me or sign my guestbook 01:52, 3 July 2011 (UTC) Dear Python eggs, on April 24, 2011, shortly after making this proposal, I posted a message on your talk page informing you of this discussion and inviting you to participate. I wanted to give everyone sufficient opportunity to discuss and make inputs and build a consensus before making the agreed to changes two months hence. ContinentalAve (talk) 05:38, 3 July 2011 (UTC) Okay, I do not oppose (not support either) most names, but names like “Lanzhou–Xinjing Railway” really suck, even the Railways itself use “新建铁路兰州至乌鲁木齐第二双线” when it had to write in the long form. [Comment by User:Python eggs] Dear Python eggs, can you explain your objection to the name Lanzhou-Xinjiang Railway more clearly? It is difficult for others to tell why you don't like this name. ContinentalAve (talk) 14:57, 4 July 2011 (UTC) I would like to ask why User:Python eggs reverted some (or most) of my renamings of the articles, which were performed in order to fit with this new convention. Special:Contributions/Python_eggs and Special:Contributions/Heights. I would like to leave a message in light of this new discussion here before moving them back again because it seems some issue has arisen. Heights(Want to talk?) 20:26, 3 July 2011 (UTC) Also sorry I must point up another issue. From the official chinese names of the high-speed railway lines, most of them are in the format of XY客运专线. Now I am not sure of the exact translation of this but it seems to be "Passenger Dedicated Line" or "Passenger Railway." The problem is even the larger lines which comprises of several smaller lines are also called 客运专线, for example Beijing-Harbin客运专线 encompasses Beijing-Shenyang客运专线, Harbin-Dalian客运专线, Panjin-Yingkou客运专线 (客运专线 used because I don't know what the name is). I made the effort of moving all of the larger lines to a "XY Passenger Dedicated Line" format such as Beijing–Harbin Passenger Dedicated Line and the smaller lines that are part of it, such as the Harbin–Dalian Passenger Railway, in the XY Passenger Railway format. I know this is inconsistent because in Chinese, they are both 客运专线, however one encompasses several smaller 客运专线. User:Python eggs reverted some of these back to XY High-Speed Railway such as Harbin–Dalian High-Speed Railway which I feel is incorrect because the Chinese name is 客运专线, which does roughly translate as "passenger dedicated line." Nowhere in those 4 characters do you see any reference to high-speed, albeit it is high speed. In contrast, the Beijing–Shanghai High-Speed Railway makes sense because in Chinese, the name is 京沪高速铁路, with 高速铁路 specifically meaning "High-Speed Railway Line." This is understandable and makes sense. I understand that Wikipedia is also about recognition and High-Speed would be more recognizable, but can we also come up with a consensus on how to name larger 客运专线s, smaller 客运专线, and 高速铁路, before I start moving articles again. Thank you, Heights(Want to talk?) 20:34, 3 July 2011 (UTC) Harbin–Dalian High-Speed Railway and others Can you please explain your rationale for moving Harbin–Dalian Passenger Railway to Harbin–Dalian High-Speed Railway. I moved all of the articles to a X–Y Passenger Railway format in order to maintain consistency. In Chinese, these lines are referred to as 客运专线, which roughly translates as "passenger dedicated line" or "passenger railway" but nowhere do I see the words "High-Speed." In contrast, the Beijing to Shanghai High Speed Railway is correct because in Chinese it is actually named 高速铁路, the words 高速 clearly indicating High-Speed. Also, explain your rationale for reverting all of my moves for Qinshen Passenger Railway and such. Please take a read at Wikipedia:NC-CHINA#Transportation as the new naming convention is to name the articles with the termini stations, aka Qinhuangdao and Shenyang, not Qinshen. Please explain your rationale and/or conform to naming conventions set by WP:NC-CHINA. Thank you Heights(Want to talk?) 20:21, 3 July 2011 (UTC) No. In Chinese, it is controversy. If you search for "哈大高铁" on Google, tons of results will be returned, and many of them from official sites like xinhuanet or gov.cn. Chinese government is switching from "客运专线" to "高速铁路". Python eggs (talk) 03:01, 4 July 2011 (UTC) I think Python eggs is trying to say that in Chinese official usage, "客运专线" is giving way to "高速铁路". But see [14] using 客运专线 from yesterday's Heilongjiang Economic Daily. It's difficult to create a consensus between "客运专线" and "高速铁路" when these lines are so new and often still not yet in operation. I can't see why one is more correct than the other. Maybe in a few years' time, one description will prevail over the other. ContinentalAve (talk) 14:57, 4 July 2011 (UTC) Ok, so I am taking this as all of the 客运专线 should be High-Speed Railway? I was just slightly confused because before I moved all of them to Passenger Railway, the Qinshen or Qinhuangdao-Shenyang article was Qinshen Passenger Railway but everything else was High-Speed Railway. I also find government sources and government sanctioned news sources using 客运专线 and also it is weird that Chinese Wikipedia still has everything as 客运专线 Heights(Want to talk?) 00:59, 5 July 2011 (UTC) I suggest "XXX High-Speed Railway" for all 300+ km/h lines. Recently, all 300+ km/h lines are commonly known as "高速铁路" in China, like 郑西高铁, 武广高铁, 沪杭高铁, 广深港高铁, and etc. The exceptions are Beijing–Tianjin Intercity Railway and Shanghai–Nanjing Intercity High-Speed Railway which is formally referred as "沪宁城际高速铁路". For lines less than 300 km/h, use "XXX Passenger Railway", or simply "XXX Railway" if their no paralleled old railway. (i.e. Hening Railway, Hewu Railway, Wenfu Railway, etc.) [Python eggs] Python eggs, I think it is premature to enact such a blanket policy on the naming of high-speed railways in China until more consistent usage patterns emerge. Heights was certainly within reason to use passenger railway to describe 客运专线. The 300km/h threshold you propose creates an unclear distinction between high-speed railway and passenger railway (and passenger dedicated line)　based on speed of operation, which is not necessarily true. The Wuhan-Guangzhou High-Speed Railway is still being mentioned in some Chinese press articles as the 武广客运专线. Let's wait and see how naming conventions in Chinese evolve　before adopting a formal policy. ContinentalAve (talk) 14:39, 7 July 2011 (UTC)

Second, many if not most railways in China are not written about very much in English-language sources, so sources are often limited and trends may not be readily apparent. The authoritative sources such as the rail operator itself China Railways [15], China Railway Construction Corporation Limited, a leading builder of railways in China [16], as well as sources that study or follow Chinese railways closely such as the World Bank [17] and Asia Development Bank [18] tend to capitalize the word “railway”. They do so because this subject area requires greater precision.

Unlike virtually any other part of the world, rail transport in China is unprecedented expansion, with the number of railways, types of railways, railway stations, etc. proliferating rapidly. See High-speed rail in China The new railway assets are often located in the same places as older assets, giving rise to the need for greater precision in the naming of the new assets as well as the older ones.

For example, as of December 2017, there are two railways between Beijing and Shanghai: the Beijing-Shanghai Railway and the Beijing-Shanghai High-Speed Railway. A second Beijing-Shanghai high-speed railway will be built in the next five years. Consider this statement:

I’m traveling on the Beijing-Shanghai railway.

Can you tell that “Beijing-Shanghai railway” is a proper noun and therefore refers to conventional-speed railway between Beijing and Shanghai? Or is this term is referring to any of the railways between Beijing and Shanghai?

The problem is more acute with the names of railway stations. With the boom in railway construction, Chinese cities are adding railway stations. Apart from a handful of exceptions such as Shanghai Hongqiao, most Chinese railway stations are named after the city in which they are located, plus a cardinal direction, to distinguish the first railway station in the city from newer ones. Consider this statement:

The train arrived at the Beijing railway station.

Did the train arrive at the Beijing Railway Station? Or another railway station in Beijing such as Beijing South Railway Station (for now, the city’s principal high-speed rail hub), the Beijing West Railway Station (for now, the busiest railway station in the city), the Beijing North Railway Station (for day trips to the Great Wall), the Beijing East Railway Station (current undergoing expansion to accommodate the expected opening of the Beijing-Shenyang High-Speed Railway)? Or any of the other railway stations in Beijing, such as the Fengtai railway station (which gives rise to another question, the old Fengtai Station or the new one currently under construction)?

This train is running on the Beijing-Zhangjiakou railway heading to the Beijing railway station.

Beijing Railway Station

Beijing South Railway Station

Beijing North Railway Station

Beijing West Railway Station

But on which Beijing-Zhangjiakou railway is the train running and to which Beijing railway station it is headed?

Why create the confusion when capitalizing these proper nouns would make the message so much more clear? At the least, I would like to see the de-capitalization campaign implemented in English-language dominated areas.

I urge you to reconsider this deeply misguided decision to de-capitalize names of rail lines and rail stations in China. It will only create problems for editors and readers, stunt the growth of coverage in this subject area and ultimately be reversed due to user and editor complaints, as the ambiguity problems become more pronounced.

ContinentalAve (talk) 21:01, 17 December 2017 (UTC)

Broken section above

I can't edit the section above, since it contains sections in the collapsed part, so may this new subsection will work.

I don't agree that the lowercase railway, station, or line necessarily adds ambiguity. There's a big difference between "the Beijing–Shanghai railway" and "a Beijing–Shanghai railway". One is specific, the other is not. There's no difficulty in distinguishing the specific referents of "the Beijing–Shanghai railway" and "the Beijing–Shanghai high-speed railway" that would be any different with capital letters. Dicklyon (talk) 05:22, 20 December 2017 (UTC)

Also strongly oppose

The two users most strongly wanting to decapitalise are Dicklyon and SMcCandlish... I find no evidence of either of them having any knowledge of either the subjects or the languages in question. Yes, knowledge of the language isn't really relevant to en.wiki generally, but I think in this case, it's important, because, quoting SMcCandlish from above: "the fact that CJK scripts have no case distinction means we absolutely should use lower-case here because our translations of them are just approximations and thus cannot be their proper names." is patently false. The concept of a proper name is basically universal across languages; by that logic, we should also be transcribing 東城秀樹 as "tojohideki" instead of "Hideki Tojo", 毛澤東 as "maozedong" instead of "Mao Zedong", and 김일성 as "kimilsŏng" instead of as "Kim Il-sŏng" or "Kim Il-sung". A proper name is a proper name, and it per the rules of English, they are to be capitalised. A quick Google search tells me that this concept is taught in Grade 2 or Grade 3.

Regarding the capitalisation of "station", "line", and "railway" in the CJK context specifically, though, I'd make the following observations.

1. Station - I'm not at all adamant that the 'station' part be considered part of the proper name, w/r/t the contexts of Korea, Japan, PRC, and Taiwan; as far as HK is concerned, English is an official language there, so we should do whatever is most widely used in HK - to which I cannot speak to, because I don't know aught about HK's railways. As far as the others are concerned, though, I can agree that 'station' is not always an integral part of the proper name, even though it is often used like that in those languages. In some cases, however, it would be necessary to capitalise it, to disambiguate. For example, Pyongyang Station refers to one specific station in Pyongyang; there are numerous other stations in Pyongyang, including West Pyongyang Station, Taedonggang, Man'gyongdae, Rangrim, etc. To say only "Pyongyang station" is, as ContinentalAve pointed out above with a Chinese example, ambiguous, so it needs to be capitalised for clarity. And if that's done, then it should follow that it be done in other non-ambiguous cases, simply for the sake of consistency.

2. Line - this isn't applicable to the PRC, but is applicable to Japan, Korea, and the parts of mainland China under Japanese administration prior to 1945, where railway lines used 線 as part of their name. In these cases, it must absolutely be capitalised, because it is without question a proper name. In Japan, names of railway lines are for the most part taken from either one location on the line, from the region the line is in, from one character from each terminus of the line, or some other descriptor, such as

• Aizu Line, from the Aizu region of Fukushima Prefecture;
• ja:小松島線 Komatsushima Line, from Komatsushima, one of the termini of the line;
• Keiyō Line, which is formed from the second character of each terminus, Tokyo (東京) and Chiba (千葉) (京葉 together is read as "Keiyō"), to form a new proper name as a specific designator for the line;
• Sankō Line, whose name means "Three Rivers Line", but there is no station on the line with that name, but rather is descriptive of the area; this sort of name is also used for the Chuo Main Line aka Chuo Line (=Central Line), etc.

To take "Aizu Line" as an example, it is without question the proper name of one specific line, because there are numerous other railway lines in the Aizu region, such as the Tadami Line, the Banetsu West Line, the former Nitchū Line ja:日中線, etc., which makes saying "Aizu line" ambiguous - *which* Aizu line is being referred to? So - it's necessary to capitalise the 'line' in this case, too, and so by extension, even if we accept the (ridiculous) notion that these are not necessarily proper names, for consistency's sake all "XYZ Line" names should be capitalised.

Railway practice in Korea is derived from Japanese practice, as it was the Japanese who brought the railway to the Korean peninsula; to this day, the naming of lines follows the Japanese models described above, primarily using the first and third varieties, though the other two turn up, as well. Taking the Hambuk Line as an example, its name is taken from the region it is in - Hamgyeong Buk-do (buk = north, North Hamgyeong Province); like the Aizu Line example above, writing "Hambuk line", however, would be ambiguous, as there are numerous other lines in the province. Another example would be the Gyeongbu Line (style number 3 above), whose name is formed from one character from each terminus - Gyeongseong (today called Seoul) and Busan; these names are, like Keiyō Line above, new formations used specifically for the naming of the railway line in question.

This third way (with 線) was also commonly used in China prior to 1945 in areas under Japanese rule, such as for the South Manchuria Railway's lines like the Anfeng Line, or the Manchukuo National Railway's Chaokai Line, etc. These are, without question, proper names.

The PRC differs from the above in using not 線 but 鐵路 to name its railway lines, which complicates the question a bit, 鐵路 means 'railway' in Chinese; 線 means 'line' (in the general sense), 'thread', 'wire', 'route' etc. And, in China, there are both long and short forms of names for railway lines, e.g. the Beijing–Harbin railway which is also called the Jingha Railway along the third model shown above. In the latter case, for the same reasons as above, these are proper names (there are several railway lines between Beijing and Harbin, for example). Although I will maintain that "Beijing–Harbin Railway" - when referring to one certain, specific line - is just as much a proper name as "Jingha Railway" is, I'd suggest that as a compromise we can consider the long form as just a descriptor, with 'railway' left uncapitalised, but that the short form is a proper name without question and so should be capitalised. Long-form names like this are in my experience rarely-to-never seen in Japanese or Korean.

I'll admit I'm not too adamant about what we do for the PRC, as I don't really have more than a superficial interest in the post-1945 situation there, I'm just including it for completeness; however, for Japan, Korea, and the railway companies of China under Japanese rule - the South Manchuria Railway, the Manchukuo National Railway, the Central China Railway, the North China Transportation Company, and several smaller, privately-owned railway companies in Manchukuo, such as the East Manchuria Railway (note that in these cases the 'railway' must be capitalised, as it is part of the name of the company, just like Canadian Pacific Railway etc) - I will be extremely adamant on the capitalisation of 'line' in reference to specific lines.2Q (talk) 16:18, 19 December 2017 (UTC)

Write all such articles in German. That way we don't have to worry about any of this (since in German, all nouns are capitalized). –Deacon Vorbis (carbon • videos) 16:28, 19 December 2017 (UTC)

How is this in any way a useful comment? 2Q (talk) 16:33, 19 December 2017 (UTC)

Because sometimes, when faced with utter lunacy (like the amount of effort that's been spent arguing over such a minute detail in an area of such niche interest), a little humor is exactly what's needed to put things in perspective. –Deacon Vorbis (carbon • videos) 16:40, 19 December 2017 (UTC)

Fair enough. :) I agree, though, it is kinda a ridiculous thing to be arguing about. 2Q (talk) 18:35, 19 December 2017 (UTC)

@2Q:, I appreciate that you're an expert on these old Japanese, Korean, and Chinese railways. Great stuff. And I understand that it's possible that I made mistakes and downcased some things that are legitimately proper names. But it's not really clear, from your explanations; when you say "it is without question the proper name of one specific line", it's not clear why you say "proper" in there. Many specific line names in many countries use lowercase "descriptive" names, or proper names with "line" or "railway" appended. When a specific Chinese character implies a proper name, I'd need help understanding that before I say OK. And when a "... Railway" title is about a company, as opposed to a rail line, then certainly I agree it's a proper name, and if I downcased any articles about companies I apologize (we had a dispute a year ago on the Harz Narrow Gauge Railways, an article that was originally written to be about the rail lines, but was rewritten to be about the company to justify the caps). Anyway, as I said, I've done my pass; now, if I got some wrong, point those out for discussion, or just move them back. Then maybe we can learn something and come out ahead. Dicklyon (talk) 05:00, 20 December 2017 (UTC)

I suppose the clearest way I can explain it is that in Japan and Korea there is (or, "was", in the case of parts of China under Japanese rule) a practice of naming railway lines, the same way that there is a (I imagine universal) practice of naming streets in a city. So, much like we've got a Granville Street and a Trafalgar Street and a King George Boulevard here where I live, in Japan and Korea etc they name railway lines in the same way, with the naming schemes I described earlier, so you've got a Tadami Line and a Gyeongbu Line and a Musan Line and what have you. There isn't a universal analogy to this in the West, aside from occasional cases, such as the SkyTrain system in Greater Vancouver, which has the Canada Line, the Expo Line, the Millennium Line, and the Evergreen Line. But these are proper names (in the same sense as street names etc.).

I'll admit don't know enough about the situation in the PRC post-1949 to say with 100% conviction it's the same there, but the impression I have is that they do have the same practice in use there as in Japan and both Koreas, and formerly in Manchukuo and the other Japanese-controlled parts of China. 2Q (talk) 15:39, 20 December 2017 (UTC)

The "practice of naming streets in a city" is much older than the practice of treating the "avenue" or "boulevard" or "street" as part of the proper name. Over time the interpretation of what's a proper name evolves, and this is where sources come in. In most places I've looked, I see of lot of lowercase line and railway and such (but always capped street, avenue, and such). I admit that for Japan the capitalized Line seems more prevalent. But I'm not at all sure that I can accept and extend that to the older lines without English-language evidence or a better explanation of what kind of name should be considered a "proper name" when it appears in Japanese or Korean or Chinese. Dicklyon (talk) 16:30, 20 December 2017 (UTC)

"The "practice of naming streets in a city" is much older than the practice of treating the "avenue" or "boulevard" or "street" as part of the proper name" - how is this relevant, though? It is the case now, and has been since at least the beginning of the 20th century. Capitalised Line is pretty much universal for Japan and is the basically standard form used in Romaji/English writing of line names... I'm really not sure how else to explain it more clearly than I already have short of suggesting you learn Japanese or Korean; I don't mean to be rude (and I don't think I honestly believe this, either, but you know how feelings can go), but it almost feels like you're being obtuse for the sake of being obtuse... okay that said I think if you're asking me how I'd define what constitutes a proper name... I'd say: if it is written with 線 and follows one of the four schemes I described above, it's a proper name... as when talking about a line in general, Japanese and Korean will most usually use "路線" ('route'), and will most usually be writing out the names of the termini in full.

For the record then I don't care what yous all decide on for lines in the PRC (although the situation with names like "Shendan Railway" *is* the same as with "Line")... I don't really care enough to put further effort into that. But for Japan, Korea, and the Japanese-controlled railways in the occupied parts of China and in Manchukuo (namely the South Manchuria Railway, the Manchukuo National Railway, the East Manchuria Railway, the North China Transportation Company, the Central China Railway, and a number of small privately owned railways in Manchukuo) I'll dig in as long as it takes. If it's written with 線 and follows one of the four schemes I described above, it's a proper name and should be capitalised as "XYZ Line"; in these places, if it's writing about 鉄道/鐵道 ("railway"), it's either speaking in general, or about the name of a railway company - which context will make clear, and if necessary can be dealt with on a case by case basis. 2Q (talk) 17:51, 20 December 2017 (UTC)

What percentage support should be needed for a policy proposal on Wikipedia to pass?

Wondering if we already have consensus on this? I have seen greater than approximate 66% support frequently used (thus those who oppose change get twice the vote as those who support change). We give the closing admin some leeway in judgement based on arguments, but generally not that much. Others thoughts? There are requests for clarification around the consensus process. Doc James (talk · contribs · email) 05:48, 19 November 2017 (UTC)

Like most things, we don't vote on these so there is not a percent. — xaosflux ^Talk 06:03, 19 November 2017 (UTC)

But we sort of do. The question is how do we determine consensus, and "it is complicated" is not a very useful answer. Doc James (talk · contribs · email) 06:09, 19 November 2017 (UTC)

Generally I've seen it as a 2/3 majority, especially in big discussions where it's a lot harder to simply discount one side of the argument. I can't recall it ever being written down anywhere though, probably because we hate voting so much that every major decision is effectively made via that process. Jenks24 (talk) 06:26, 19 November 2017 (UTC)

@Doc James:--Can you link the discussion or call for clarification? Because, I feel that it would be a pointless bureaucratic exercise and will most-likely oppose any attempt at clarification.From my own experiences and observations, numerically, anything greater than 66-70% shall be enough but arguments need to be almost always weighed and it's complicated is the optimum call.Winged Blades ^Godric 13:28, 19 November 2017 (UTC)

• We intentionally don’t set a firm percentage. Broadly speaking, the more support a proposal gets, the more we can say it reflects consensus and should be adopted. However, we also pay a lot of attention to STRENGTH of arguments for and against. A few well argued opposing comments can sometimes out weigh a lot of supporting comments that essentially just say “I like it” - but contain no explanation as to WHY it is liked (and vise-versa). Determining consensus can be as much an art as it is a science. Never easy, unless the consensus is fairly overwhelming. Blueboar (talk) 16:12, 19 November 2017 (UTC)
  • Wikipedia is neither a bureaucracy nor a democracy; it would be better described as a "meritocracy", where "votes" with more merit are given more consideration than "votes" with less. Please read Wikipedia:Polling is not a substitute for discussion. עוד מישהו Od Mishehu 07:45, 20 November 2017 (UTC)
    • "Given more consideration" by the closer? If that's the reality, we should see some closes going against the numbers (assessing a consensus against the majority !vote). Can you point to two in the past year? ―Mandruss ☎ 08:01, 20 November 2017 (UTC)
  • Supports are always typically taken to mean that the participant thinks that the rationale provided by the proposer is correct. Opposes have more of a burden in every conversations since no one is writing an overarching statement with reasoning, as any good policy proposal will have. TonyBallioni (talk) 16:58, 20 November 2017 (UTC)
    • Agree. And opposes are typically given twice the vote as supporters so excellent rational should be expected. Doc James (talk · contribs · email) 17:49, 29 November 2017 (UTC)
      • You could have a rationale provided for both sides in an RFC; see Wikipedia:Requests for comment/Example formatting#Pro and con for one way to do that. WhatamIdoing (talk) 18:24, 30 November 2017 (UTC)
• I'm not aware that the rules being different here than for any other discussion. 2/3rds is an interesting marker, but by no means is it the line in the sand. Discretion is in the hands of the closer, and then if the community supports that close. Dennis Brown - 2¢ 16:41, 20 November 2017 (UTC)
• Typically 60-65% for guidelines,66-70% for policies. Also, I will put my standard bitching out there that screaming for policy based reasons and to ignore numbers on policy RfCs is circular reasoning and the last resort of the losing side of an RfC: it is literally impossible to have a policy-based reason to change policy. Policy RfCs are very different than regular discussions and are much more like a vote.
  Our information page on closing discussions also makes clear (in the lovely worded shortcut WP:not counting heads) that If the discussion shows that some people think one policy is controlling, and some another, the closer is expected to close by judging which view has the predominant number of responsible Wikipedians supporting it, not personally select which is the better policy.
  In a discussion where there can be no controlling policy, this turns the discussion much more into a poll. Obviously arguments such as I hate the proposer, so I'm opposing or Wikipedia sucks and this will help it go down in flames, I support, should be discounted, but otherwise good faith opinions should be given equal weight. TonyBallioni (talk) 16:54, 20 November 2017 (UTC)
  • If the boundaries of all policies were clearly non-overlapping, then sure, by definition a policy change would not be based on other policies. But in practice, policies have fuzzy boundaries, and often additional clarification is required. Thus a consensus agreement to determine the relative weight and tradeoffs of all applicable policies needs to be reached. isaacl (talk) 19:01, 20 November 2017 (UTC)
    • Agreed re: fuzzy and overlapping, but even when two policies are in tension, numerical consensus is how our closing guidelines say something should be evaluated. If there are two policy-based arguments opposing each other, having an RfC to determine which should be applied would not have a strong pre-existing basis, otherwise there wouldn't be confusion. On new policies or removals, there is virtually never any basis for a change in policy. I'm not arguing for a pure poll, but simply that at some point, numbers matter. TonyBallioni (talk) 19:07, 20 November 2017 (UTC)
      • In practice, nearly all English Wikipedia decisions are made via a straw poll with commenters trying to persuade others, so sure, numbers matter. As a community grows, it is increasingly unlikely that it will be strongly aligned in purpose, which is required for true consensus. Even with everyone behaving in good faith, people have different guiding principles that lead them to interpret policies differently. And because Wikipedia's guidance doesn't all move in lockstep, but incrementally as different groups of interested persons shift guidelines and policies one way or another, it is quite possible to have policy A which had been based on principle X originally, and a newer policy B based on principle Y that pulls in a different direction. Consider, for instance, how the need for citing everything has gained increasing importance over the years. Accordingly, Wikipedia guidance has been updated to reflect the change in the community's underlying views, and it is reasonable to make policy-based arguments on how to adjust older guidance to adapt. isaacl (talk) 05:09, 21 November 2017 (UTC)
  • What Tony said. For policies (and occasionally guidelines) you often cannot have arguments based on policies - because you are usually either seeking to add one, remove one, or alter one to say something different. Strength of argument does make a difference, a !vote with a credible and plausible rationale behind it carries far more weight than 'I like/don't like it'. Only in death does duty end (talk) 17:09, 20 November 2017 (UTC)
    • I agree that you "often" cannot have arguments based on policies, but I disagree with his assertion that it is impossible. For example, we can, and probably should, be changing several SNGs to explicitly repeat NOT's policy on not having any articles whatsoever (much less BLPs) for which no third-party reliable sources are not available. That's a policy-based argument, and therefore it is possible to make such arguments. WhatamIdoing (talk) 18:27, 30 November 2017 (UTC)
• It should be no firm percentage, given that the second you set a number, it becomes a firm number. If we said 66%, then if we had a discussion with 200 participants, and there were 132 supports, we would expect it to ALWAYS be closed in favor, and 131 supports would ALWAYS be closed against, because you've just told everyone that 66% is your number. The guidance on this should always be intentionally vague. --Jayron32 18:36, 20 November 2017 (UTC)
• Per some of the above, percentage support is hardly the only factor. The closing admin also needs to evaluate the degree to which participants are making informed arguments, weigh their relative experience as contributors to Wikipedia (or, where applicable, other Wikimedia projects), and weed out troll posts. The degree of participation also matters. A proposal for a major change that gets two votes in favor and one against is not in nearly as strong a position as a proposal that gets two-hundred votes in favor and one-hundred against. bd2412 T 20:44, 20 November 2017 (UTC)
• The German Wikipedia has structured votes on policies with strict numerical standards for suffrage and vote counts. We are a lot less organised, which makes us a lot more flexible (and somewhat more anarchic). Fixed percentages only make sense in much more structured environments than our usual policymaking dramahboards. —Kusma (t·c) 14:11, 21 November 2017 (UTC)

  It's also a very German way to handle it. Cultural relativity matters, even on Wikipedia, and we expect different language communities to have different cultural millieu, which is why we allow local governance. What works for the German-speaking community in the context of their culture doesn't necessarily work in the Anglophone world. --Jayron32 15:00, 28 November 2017 (UTC)

  Amen to that.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:14, 29 November 2017 (UTC)

• Can't agree with "it is literally impossible to have a policy-based reason to change policy", because WP:POLICYFORK. There have been many, many times when policy arguments have been, necessarily, used to adjust conflicts between policies and between guidelines, etc. (Infamous example: a wikiproject incrementally forked two naming conventions and an MoS subpage away from the main MoS page to push a viewpoint, it turned into several years of dispute, finally settled in a massive RfC that normalized it back to the main MoS position; details elided per WP:BEANS and the "don't pick at scabs" principle). Not all policies are created equal. E.g. WP:OFFICE policies trump community-created ones. Below the OFFICE level, WP:CCPOL ones trump a lot of other ones on many things, though this can run the other direction (e.g. the vague generalities in WP:V, WP:RM, and WP:NOR can't be used to evade the specifics of WP:MEDRS, within medical articles. Site-wide guidelines trump micro-topical ones per WP:CONLEVEL. Except that broad consensus can decided that in a particular case it does not, as it did with MEDRS. Etc., etc. Short version: "It's more complicated than that."

  At least at this stage in the en.wp organizational lifecycle, switching to a vote-based system might be fatal, and would at very least do severe damage, even if it might be recoverable. A tremendous number of editors would leave, right off the bat. I know I would. This principle problem with the idea is that there are way too many issue to resolve, with too few people to resolve them and too few people competent to resolve them. The consequence is that only those who care and know WTF they're talking about work on resolving them (aside from a few tendentious gadflies who get in the way). A voting system would require a much larger pool with much more interest in participation in such matters than we actually have. What would happen is that the tendentious loudmouths would be given near-free reign to impose their will by sheer refusal to ever STFU about whatever they refuse to let go.

  E.g. if you have five editors convinced that it's a great wrong that some policy or guideline gets in the way of their WP:OWNership of some topic, all they have to do is convince a few of their cohorts to go along, then they have a thick voting bloc to modify a policy to carve out a special pleading exception for their peccadillo; meanwhile hardly any one else is going to care or even know what they're talking about, so the motion will pass. In the present system, ten people can show up and make a stupid argument, and two editors can oppose it on solid policy and RS footing, and a sensible closer will not close in favor of the stupid thing, because it's self-evidently stupid and has no basis, while the two common-sense people who spoke up actually had the meaningful input. This doesn't always happens – too many inexperienced or nervous closers close in favor of the majority even when it's stupid, but this trend is thwarted frequently enough (much as the Senate often blocks lame-ass populist nonsense from the House of Representatives – or at least it used to) that en.wp is remarkably stable. That stability would be out the window in an instant if we switched to numeric majority, vote-based decisionmaking. Voting might actually have a made sense in 2005–2008 when WP was awash in editors, but it makes sense less and less the more the editorial pool condenses.
   — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:33, 29 November 2017 (UTC)

  • I don't think I'd argue ever for a simple majority or for a small poorly advertised discussion to change policy. I think you probably know that I'm more than willing to close local discussions against the numbers when they aren't in line with policy. At the same time those who scream NOTAVOTE every time they are on the "losing" end of the conversation seem to ignore that numbers do matter, especially in a policy RfC. If a policy RfC is widely advertised, has large participation, and over 70% support, there is virtually never any justifiable reason to have a result other than adopting the proposal. Re: policy RfCs: I was not discussing splits, but the creation of new policies and guidelines, where I stand by my statement that it is impossible to have a valid reason in policy to propose a new one. Heck, we even have a policy supplement against it. I think the point that Doc James and I are trying to make is that it is extremely arrogant in a discussion with over 100 participants for the loudest voices in a position that received less than 30% support to say "Our arguments were better, so you can't do this." Common sense dictates that numbers matter, and we shouldn't just stick our heads in the sand on that. TonyBallioni (talk) 14:45, 29 November 2017 (UTC)
    • I agree the closer should be given some leeway in votes between 60 and 70% when more than 100 people have weighted in (after bad faith and sock votes have been removed). That those who oppose something can demand 80% or 90% support is simple unreasonable. User:SMcCandlish I would argue that this currently gives "loudmouths... near-free reign to impose their will by sheer refusal" as it is fairly easy to build a block of 10 or 20% Doc James (talk · contribs · email) 18:02, 29 November 2017 (UTC)
      • We don't seem to have a case history of this, though. Can you show a proposal with 80% or even 70% support (after discounting clownage) that was not actually adopted? This looks like a solution in search a problem, and it would have a lot of fallout.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  00:54, 30 November 2017 (UTC)
        • Sure on meta right now.[19] This RfC was initially closed as not supported but Rentier reversed the close.[20] Doc James (talk · contribs · email) 18:36, 7 December 2017 (UTC)

• • • I still don't agree with "can't use policy to make policy". All of our policies inter-relate, so we always use policy to make more of it. You seem to be imagining a scenario where we have some policy proposal that has no relationship to existing policy. I was going to make up a silly example but I can't actually think of one, because every case I can come up with actually relates strongly to either one of the WP:CCPOL, a legal matter we already have a policy about, or behavioral policy. It's seeming increasingly unlikely to me that we're ever going to have any new out-of-the-blue policy that isn't deeply rooted in existing policy.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  00:59, 30 November 2017 (UTC)

We don't even need a majority, we just need a consensus as per wp:closing. But what does that mean? Well, I've been at Uniting Church in Australia meetings where consensus decision making was used and a handful of people won over the majority, and all agreed afterwards that it was a good decision. But that needs a skillful chairperson, or in our case, a good closing admin. And it needs mutual respect so that "loudmouths" (mentioned above) don't just shut other people up. That is why I'm so concerned that the current tendency to regard wp:NPA as "aspirational" to the point that even admins don't abide by it will eventually make consensus here meaningless. Andrewa (talk) 22:25, 29 November 2017 (UTC)

We need a sea-change at ArbCom, to start enforcing the civility-related policies again. This has already happened a little, incrementally. E.g. not that long ago a civility desysop case was brought, we clearly going to result in a desysop, and the admin resigned the bit under that cloud.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  00:54, 30 November 2017 (UTC)

Disagree that we need... to start enforcing the civility-related policies... Enforcement shouldn't be necessary, and isn't practical in any case unless we have a clear consensus that wp:NPA is more than "aspirational", and we don't. That consensus is what we need. More important, NPA is far more than a civility-related policy. It is a cornerstone without which meaningful consensus can't be achieved or assessed, whether in the UCA or Wikipedia or anywhere else. Civility can be in the eye of the beholder, while NPA has no such wiggle-room. Andrewa (talk) 08:16, 30 November 2017 (UTC)

RfC: Comma or parenthetic disambiguation for "small places"

There are recurrent disputes about article titles for what could be called "small places" – churches, sporting event arenas and other venues, schools and other institutions, malls, plazas, parks, outdoor statues and monuments, railway stations, and other things to which one can go but which are structures or otherwise have an architectural component, and are not villages, cities, forests, or other large areas. Just today, for example, there was move-warring between Nieuwe Kerk, Amsterdam and Nieuwe Kerk (Amsterdam), both moves performed via WP:RM/TR despite being potentially controversial. I see stuff like this all the time, and the amount of disruption (both to article locations and to editorial tempers) has gotten to the "enough is enough" point.

Should Wikipedia:Article titles#COMMADIS be applied to such "small places" consistently, or should we continue to arbitrarily apply parenthetic disambiguation to some of them? If the latter, what determines whether to use the one style versus the other?

Background: according to WP:ATDIS policy, parenthetic disambiguation is the third (that is, quite disfavored) choice in disambiguation style, with comma-based disambiguation ahead of it as number 2, and natural disambiguation preferred over all. An argument can be made that comma style in this sort of case is actually a form of natural disambiguation because it is regularly used in everyday English (i.e., comma disambiguation that isn't also natural is really more like Robert Scarlett, 2nd Baron Abinger and Robert Scarlett, 6th Baron Abinger – an awkward formalism, though still less awkward than parenthetic). The section in this policy on comma disambiguation gives both royal styles/titles and locations as examples, but not only is this not an exclusive list, it specifically says "Comma-separated disambiguation is sometimes also used in other contexts". The counter-argument appears to be that "places" was meant to be interpreted strictly as jurisdictions, is not inclusive of structures, fields/pitches, and other "micro-places", and that "sometimes also used in other contexts" doesn't apply to them.

 — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  05:51, 23 November 2017 (UTC)

Comments on COMMADIS scope

• Apply COMMADIS consistently, as more in keeping with WP:CONSISTENCY and WP:NATURAL policies (not to be confused with WP:NATURALDIS, which is dependent on it), and to put an end to pointless but heated and near-constant disputation over this disambiguation trivia, which is predicated on subjective, unclear, idiosyncratic distinctions about what is and isn't a "place".  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  05:51, 23 November 2017 (UTC)
• Support for all cases where there's no good reason to do otherwise. Tony (talk)
• No objection to adding churches, parks and stations to the list. But for example this generally does not work for paintings in art galleries (or in cities). Johnbod (talk) 13:40, 23 November 2017 (UTC)
  • Sure; this isn't mean to apply to anything no one would think of a "place", i.e. something one can neither enter nor (thinking of large monuments with no doors) climb. If it's big and outside, it should qualify. More like: stuff that our language naturally disambiguates with commas qualifies generally (per WP:ATDAB policy's order of disambiguation-style precedence); but commas don't work well for small, indoor things, or for stuff that's abstract or a person, or otherwise not something we non-awkwardly use commas with in English.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:49, 26 November 2017 (UTC)
• I do not get how this works for neighborhoods/sections of a city, where there is also a park or other geographical feature with the same name. Alanscottwalker (talk) 13:47, 23 November 2017 (UTC)
  • Same as for any other such naming clash: disambiguate further, probably parenthetically. The idea that "Foo Bar, Baz" and "Foo Bar (Baz)" with each term identical between the examples (i.e. Foo = Foo), is supposed to meaningfully disambiguate between (e.g.) a park and a neighborhood is silly and impractical. The fact that people have been trying this and that readers and even many editors have been confused by it is a part of why this RfC has been opened. The sensible approach is to use "Foo Bar, Baz" for the WP:PRIMARYTOPIC and "Foo Bar, Baz (park)" or whatever for the non-primary one(s).  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:42, 26 November 2017 (UTC)
• Comma disambiguation is a relic of the fact that this is how names of populated places tend to be addressed in the real world. I think it would be absurd to apply it to objects like statues. With respect to natural features like rivers and mountains, it typically distinguishes between those features and place names that happen to include the word "River" or "Mountain". bd2412 T 05:51, 24 November 2017 (UTC)
• — Note: An editor has expressed a concern that editors have been canvassed to this discussion. (diffs: [21], [22], [23])  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:37, 26 November 2017 (UTC)
• Consistency is not needed... What determines whether to use the one style versus the other? Discussion and local consensus. Blueboar (talk) 15:11, 26 November 2017 (UTC)

  That doesn't seem to be particularly meaningful. This is a discussion, and WP:CONLEVEL specifically exists to prevent a "local consensus" from making up its own rules that conflict with site-wide policy like WP:ATDAB.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:38, 29 November 2017 (UTC)

I’m not saying that a “rule” should be made at a local level... I’m saying that the “rule” is: “There are several acceptable forms of disambiguation”... and the determination of WHICH acceptable form of disambiguation is most appropriate to use in any given article has to be made at the article level... on a topic by topic basis. Blueboar (talk) 13:04, 3 December 2017 (UTC)

• This RfC seems a poorly framed (i.e., unclear) attempt to make policy based on edge cases. In general, I really, really do not understand why some editors have such an irrational dislike for parenthetical disambiguation. Personally, I think parenthetical disambiguation should be the default EXCEPT in those cases where there is a commonly used natural language title. Parenthetical disambiguation makes it clearer to readers what part of the title is the actual name of the subject rather than some arbitrarily appended term to disambiguate. So, I think that would place me firmly in the oppose camp. older ≠ wiser 15:25, 26 November 2017 (UTC)

  Cognitive dissonance. It seems "unclear" to you, and you "don't understand" and think there's something "irrational" going on because you've made an incorrect assumption that this has something to do with likes and preferences. In reality, it's about how to apply the WP:ATDAB policy more consistently, to avoid continual pointless dispute on the matter. By way of analogy 1: You can harbor a dislike of a particular rule in Texas hold'em poker and wish that the game were a little different, but you'll still strenuously object when one of your opponents cheats under the rules as-written. Analogy 2) Your argument is effectively indistinguishable from "Kosher and hallal are weird nonsense. I don't get why these people hate pigs and have emotional issues with dairy. It's irrational that they won't eat my pepperoni pizza." It has nothing to do with emotional preferences, but with wether the food you put in front of them complies with rule systems they take seriously.

  I personally don't mind parenthetic DAB at all. I'd be quite happy if we eliminated all other options. But we have a four-tier system of DAB, with parenthetic in next-to-last place of preference, and that's what consensus has decided we collectively want. Analogy 3: Don't show up to a football game with a basketball and complain about all this kicking and grass and lack of a hoop.
   — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:45, 29 November 2017 (UTC)

  I stand by the assertion that this is unclear (not only that it seems so). You want to read WP:ATDAB policy as being more hierarchical than it is or than how others interpret it. Sorry, I remain unconvinced. Ignoring your deprecating asides as off point and irrelevant, I continue to maintain it is more beneficial for readers to clearly mark the disambiguating terms with parentheses rather than make implicit suggesting that the comma term is a part of the name. older ≠ wiser 16:18, 30 November 2017 (UTC)

• Close per WP:FORUMSHOP. See Wikipedia talk:WikiProject Trains#RfC: UK railway station disambiguation. --Redrose64 🌹 (talk) 21:24, 26 November 2017 (UTC)
  • Nonsense. That's an only tangentially related discussion, primarily about word order, for one topic+country intersection. This is about a general principle across all topics, site-wide.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  14:36, 29 November 2017 (UTC)

So what was the objection to advising those participating in that specific discussion that a discussion of the 'general principle' had now been initiated (and would outrank the local discussion)?Rjccumbria (talk) 16:48, 30 November 2017 (UTC)

I don't know. Where is this objection of which you speak, so we can look at it?  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  10:53, 3 December 2017 (UTC)

• There is absolutely nothing wrong with comma disambiguation for these places. It should be applied as it has always been applied. Consistently according to consensus (e.g. in most Commonwealth countries, the consensus is and has long been to use commas). -- Necrothesp (talk) 14:20, 29 November 2017 (UTC)
• I have several issues:
  • I agree with Bkonrad in believing that my esteemed colleague, SMcCandlish, is mistaken in asserting that, because in WP:ATDIS policy, parenthetic disambiguation is listed third, it is a "quite disfavored" choice in disambiguation style. In fact, WP:ATDIS says, "When deciding on which disambiguation method(s) to use, all article titling criteria are weighed in," and then it lists 5 methods. There is no basis for concluding that these methods are listed in order of most-favored to least-favored.
  • The topic heading here is vague. Streets and roads are long and narrow; are they small places? For example:
    • Main Street (disambiguation) lists 10 streets named Main Street with parentheses disambiguation, one street named Main Street with comma disambiguation (Main Street, Gibraltar), and one street named Main Street with comma disambiguation that redirects to an entirely different name (Main Street, Winnipeg).
  • Schools are typically disambiguated with parentheses, see, e.g. Lincoln High School.
  • It was recently decided that rail lines should use parentheses disambiguation.
  • "X, state" implies that X is the name of a locality within a state, for example, Syracuse, New York. We should avoid using comma disambiguation when it incorrectly implies that something is a locality.
  • In conclusion, I think this proposal should be quietly forgotten, i.e.,
  • Close. —Anomalocaris (talk) 10:20, 3 December 2017 (UTC)
• Use parenthetical disambiguation for geographical objects which are not, as Wiktionary says, "inhabited areas" (place § English § Noun 1.3). While both would be correct but strange if inserted into the middle of an English sentence (and assuming we can't use "in place" as a disambiguator), using parentheses would marginally help with some consistency in naming for classes of physical objects which are disambiguated by things that are and are not place [inhabited area] names, such as railway stations. Jc86035 (talk) 15:13, 3 December 2017 (UTC)
• Prefer comma disambiguation when it would be a natural way to describe a place in a sentence. As Jc86035 says, some "would be correct but strange if inserted into the middle of an English sentence"; the comma-disambiguated ones that would be correct and not strange should be preferred that way. I would think this would apply to a lot of Main Streets and railway stations. Dicklyon (talk) 16:17, 3 December 2017 (UTC)
• Close. I cannot see how any one rule is going to fit well for all purposes, places, and regional styles; the reasonable exceptions may well outweight the "majority". "Small places" is imprecise, likely to create more EW, not less. Maybe this RfC could be broken down in a few manageable sub-cases (like the railway naming), but not one rule to ring them all. --A D Monroe III^(talk) 18:04, 3 December 2017 (UTC)

Extended discussion of COMMADIS scope

What are you raving about, McCandlish? There has only been a single move, which I performed (not by WP:RM/TR), at Nieuwe Kerk, Amsterdam, to what you admit (behind the usual smokescreen of verbiage) is the right title. You might be thinking of Oude Kerk, Amsterdam, which is where it has long been, until some well-meaning type briefly moved it to Oude Kerk (Amsterdam), to agree with the Nieuwe Kerk as it then was, and I moved it back (via a WP:RM/TR request). The vast majority of churches are disamed with a comma, and rightly so. No "move-warring", still less "pointless but heated and near-constant disputation", & nothing "potentially controversial", Johnbod (talk) 13:22, 23 November 2017 (UTC)

I decline to address uncivil characterizations like that. If I say this is about a long-term pattern of conflict, then I mean that. The fact that you don't like one example has no bearing on the RfC other than maybe some additional examples would have been in order. At this late a date, there'd be no point.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  16:48, 16 December 2017 (UTC)

Are these "small places" actually places, or are they just things which happen to have a fixed place because they're too big to move easily? For example, Forres railway station just moved. (Must update the article...) The term "Forres railway station" now applies to the new facility (even though they built new platforms rather than shifting the old one), suggesting that the article's topic is an object rather than a place. There is an argument for COMMADIS applying, but I don't think it's an obvious consequence of "small places" being a subset of "places". Certes (talk) 15:18, 26 November 2017 (UTC)

@Certes: See also wiktionary:place#noun. I think you could look at this debate as entirely based on which sub-definition of "place" is supposed to be meant. Jc86035 (talk) 15:21, 3 December 2017 (UTC)

RfC about river disambiguation conventions

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.

Despite some minor squabbles, there's an unanimous consensus to Y support Dickylon's changes to Wikipedia:WikiProject Rivers.Finer issues could be sorted out through local discussions at project-talk-pages.Thankfully,Winged Blades^Godric 13:56, 23 December 2017 (UTC)

---

Should the changes in this diff be kept? I updated Wikipedia:WikiProject Rivers#Multiple rivers with the same name to reflect what I think represents a likely consensus, but the last time we had a small discussion there it closed with "no consensus" and advice to "be flexible". So we need a bigger discussion while remaining flexible. Dicklyon (talk) 01:53, 29 November 2017 (UTC)

Background

When I found that I had taken a picture of the Rio Puerco (Rio Grande tributary), its article was at Rio Puerco (Rio Grande), which I found confusing.

• Wikipedia talk:WikiProject Rivers/Archive 4#RfC on Rivers: updating the naming/disambiguation conventions – previous RFC, closed with "no consensus" and "be flexible"
• Talk:Rio Puerco (Rio Grande tributary)#Requested move 5 April 2017 – The only RM discussion I know of on this topic; it supports this change.

Discussion

• Support keeping the change that I made on 28 Nov. Over the last several days I've moved nearly 250 of the highest-ranked ambiguous river, creek, wash, etc. articles (mostly in the US West, and nearly 100 in Minnesota alone, see my move log) to include the word "tributary" to make the disambiguator meaningful to more readers than just the river insiders, which I believe accords with the inputs I got the last few times I brought this up (see Background above). Nobody has objected (but a couple have asked for a pointer to the previous discussion). So it's probably time to convert the proposed river title conventions to a real and improved convention more consistent with how disambiguation is usually done. I remain flexible and seek alternatives and refinements to my edits there. Dicklyon (talk) 01:53, 29 November 2017 (UTC)
• Support including "tributary" for less prominent watercourses that are primarily significant due to their relationship to a better-known watercourse. bd2412 T 04:50, 29 November 2017 (UTC)
• Obvious support. The idea that "St. Joseph River (Maumee River)" is a sensibly disambiguated title is nuts. Any disambiguation system that causes at least as much confusion as it would solve is a total failure. After this, we should change it to use comma disambiguation as per other placenames with the exception to use parenthetic clarification when there's a conflict, instead of making a silly "use parenthetic in the US and [where ever]" but use comma in the UK".  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  15:02, 29 November 2017 (UTC)
• Support in cases where disambiguation is required (in case that needs to be said). I don't see a need for anyone to create Saguenay River (St. Lawrence River tributary), for example, but this is as reasonable as any other special-case disambiguation method we use for other topics. Ivanvector (^Talk/_Edits) 15:13, 29 November 2017 (UTC)

  Since this is just one option in the subsection "Multiple rivers with the same name", I think you don't need to worry. But feel free to look and clarify if needed. Dicklyon (talk) 16:32, 29 November 2017 (UTC)

• Support per Ivan. --SarekOfVulcan (talk) 15:16, 29 November 2017 (UTC)
• Support. It just sounds better. Rationally, it seems a little strange that when a river dumps into another river we need an extra word to say that it does so, but I think the explanation is that River (River) is just too ambiguous. It isn't obvious what the connection between the two rivers is, unlike seas or bays which can only be related to rivers in one way. —David Eppstein (talk) 06:28, 30 November 2017 (UTC)
• Support. It's clearer for readers. Mathglot (talk) 10:23, 1 December 2017 (UTC)
• Support. The construction "X River (Y River)" reads as if "Y River" is a variant name of "X River", so the added term is necessary for clarification. On a related but distinct topic, I'll add that the "X River (Y River)" practice has been widely applied in the past in cases where it is not strictly necessary for disambiguation -- rather, it is thought by some that this format should be a solution to the precision issues that arise when a river flows through multiple U.S. states. Rock River (Mississippi River tributary) and Big Sandy River (Ohio River tributary) are examples of this (both were recently moved to incorporate the word "tributary"). I think "Rock River (Wisconsin—Illinois)" and "Big Sandy River (Kentucky—West Virginia)" would be more helpful for most readers, and there is no disambiguation problem that is solved by their current titles (i.e., there are no other streams named "Rock River" in Wisconsin or Illinois, nor other streams named "Big Sandy River" in Kentucky or West Virginia). There was a recent discussion of this at Talk:White River (Arkansas–Missouri). I'm generally opposed to the application of the convention "X River (Y River tributary)" in cases where rivers can be sufficiently disambiguated using the names of major jurisdictions instead. Thanks-- TimK MSI (talk) 13:19, 2 December 2017 (UTC)

  That seems reasonable to me. In working through states via articles such as List of rivers of Minnesota, I've noticed a lot of variance in the naming, articles, density of redlinks, etc. (Minnesota in particular has a lot of rivers, about 100 with tributary disambiguation, and had a ton of wrongly done stubs, with disambiguators copied into lead sentence and infobox titles, so took a lot of hours to fix). I think clarifying the conventions and working on some that diverge a lot from the norm would be a good idea. But I'm pretty bushed working on tributaries, and not done yet, so I'll leave that to others. Dicklyon (talk) 16:43, 2 December 2017 (UTC)

  List of rivers in Pennsylvania is proving to be quite a challenge. I'm several hours into it and flagging. So many Mill Creeks, so much unneeded disambig, etc. Dicklyon (talk) 03:47, 3 December 2017 (UTC)

  Done with PA. Moved over 300 more today. Just need to do New England now; and the rest of the world... Dicklyon (talk) 05:32, 3 December 2017 (UTC)

• Support on using the word tributary when a river is disambiguated by the downstream body. However the rest of the guideline is vague about guidance on choosing between disambiguators. It says political/geographical is commonly used and tributary can be used as well. I would like to have it state which is preferred (if we can reach a consensus on that) or at least in which circumstances is either preferred. I am leaning towards Rock River (Mississippi River tributary) over Rock River (Wisconsin-Illinois). Both seem equally good/logical as methods of disambiguating. But considering the number of common names used for small creeks, there is a precision issue to consider. For example, see Indian Creek. Methods used here include river, state, city, and county. There isn't even consistency within Missouri. As someone who has spend a fair amount of time disambiguating creeks, it isn't always easy. The dab page says there are three Indian Creeks in Pennsylvania, but GNIS lists 10 total (all of which could have articles someday), including two in the same county. There are three in one county in Arizona. Clearly there are cases when using political disambiguation doesn't work well. I think using (Y River tributary) is a bit cleaner overall and should be the default choice. MB 03:57, 3 December 2017 (UTC)

  I agree it's a bit of a complicated mess, and different groups (states, drainage basins, neighborhoods, or whatever) are doing it differently. Probably not something to resolve here though; that's the kind of thing a small group of river experts should be good at working out. Sounds like TimK MSI is leaning the other way, so you two should talk. Dicklyon (talk) 05:32, 3 December 2017 (UTC)

• Support I am unable to perceive strong cases for the other side. If there is opposition to this proposal elsewhere I am not quickly seeing it. I feel that giving clear guidance is preferable. So far as I can see, the previous guidance was saying that any of several options works. I appreciate the flexibility but it is helpful at some point to take a position and recommend a preferred way of doing things. The decision is somewhat arbitrary but what is proposed here seems logical and understandable to me, and of the proposed naming conventions, I prefer it. I say to firm this way of doing things until and unless someone more clearly articulates problems and has a better general rule. Blue Rasberry (talk) 16:39, 4 December 2017 (UTC)

Subtleties

I moved North River (Hudson River) to North River (New York–New Jersey), which might be in opposition to a previous move, though it's hard to figure out the malformatted discussion there. This is the only one I've noticed where the river in parentheses was an alternate name, not a tributary relationship. I suppose if we fix all the tributaries we could put it back, but I think it's confusing no matter how we do it. The article is about the alternate name for the lower Hudson River. Better ideas? Dicklyon (talk) 07:34, 3 December 2017 (UTC)

Status

I've now moved over 800 river disambig titles to include "tributary", in 49 states (Hawaii didn't have any like this). If I missed any, sorry. Hopefully this will be enough to attract the attention of at least all US wikipedians who have an interest in rivers. I just got one more query at my talk page and pointed him here. Dicklyon (talk) 20:03, 3 December 2017 (UTC)

Some rivers that aren't sufficiently disambiguated by tributary relationship include a place name as well. But when I did that for Beaver Creek (White River tributary, Missouri) to distinguish from the one in Alaska (which is listed but doesn't have an article), I got reverted. We could perhaps use a better scheme for this, or clearer guidance, as there are quite a few (dozens, not hundreds) like this. Dicklyon (talk) 20:23, 3 December 2017 (UTC)

I worked over the List of rivers of Quebec; maybe we'll get some less US-centric (or less English-centric) comments from there? They have about a million rivers, but most of them are redlinks, so very few moves were needed. Dicklyon (talk) 04:37, 4 December 2017 (UTC)

Nope, no more comments or pushback there, either. Time to close, move on, finish Canada, then the world ... Dicklyon (talk) 07:44, 9 December 2017 (UTC)

I believe I've finished with Canada now, too. And I've looked at Mexico and England and didn't find any such disambiguations. Does anyone know if some other countries use that? Dicklyon (talk) 04:43, 11 December 2017 (UTC)

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.

MOS:PN to MOS:CAPS merger

FYI

 – Pointer to relevant discussion elsewhere.

General community input requested at Wikipedia talk:Manual of Style/Capital letters#Merge in MOS:PN.

Summary: We have a page (which is virtually never edited or cited) at WP:Manual of Style/Proper names that is redundant with WP:Manual of Style/Capital letters and its material on proper names/proper nouns, but the former is a bit more specific on a few things, and these should probably be retained. Ergo, it's proposed to merge the salvageable material from MOS:PN into MOS:CAPS. Some of MOS:PN would not be retained in MOS:CAPS because it is non-MoS material about article titles, redundant with various naming conventions pages such as WP:Naming conventions (people), etc.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  10:18, 3 December 2017 (UTC)

• The reason I oppose this at the discussion is that the long-time "WP:Manual of Style/Proper names" guideline includes the wording Wikipedia does not seek to judge such rival claims, but as a general rule uses the name which is likely to be most familiar to readers of English and SMcCandlish hasn't agreed that when a merge occurs that this language be included in some form. "As a general rule uses the name which is likely to be most familiar to readers of English" is wonderful encyclopedic-appropriate language, and is a common sense guideline/policy which is now in place. A merge should include this language, which has been stable. Randy Kryn (talk) 15:04, 3 December 2017 (UTC)

  No one proposed removing it, so I don't know what you're on about. The concept of "merge" here is "move content from one place to another, with a minimal changes only, to integrate it into the pre-existing material at the target page". It does not mean "delete the content and start from scratch".  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  16:54, 16 December 2017 (UTC)

RfC: Accessibility versus convenience in indentation

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.

---

Should MOS:MATH and WP:INDENT be updated to comply with the WP:MOS and MOS:ACCESS instructions on accessible indentation in 2017 Wikipedia's article content?

Tracked in Phabricator
Task T6521

Background: WP editors have long misused description list markup for indentation (we do it all the time on talk pages). MoS has also long advised to not do this in articles, and to instead use indentation templates (e.g. here). We provide various templates for doing accessible indentation that does not cause problems for screen readers (for details, see MOS:ACCESS, specifically WP:Manual of Style/Accessibility#Indentation).

WP:Manual of Style/Mathematics (MOS:MATH) has been advising (in one section) the continued use of description list markup for visual indentation in articles, for reasons that do not appear clearly articulable other than that doing it with : list markup is simply easier for editors. This appears to be a guideline PoV fork. (And a pointless one, since no one would be "punished" for doing it the crude way, we'd simply advise the better way and WP:GNOMEs would incrementally fix cases of it being done the bad way).

A decade-old essay, Wikipedia:Indentation (WP:INDENT), is also providing outdated and incorrect information on how to indent on Wikipedia; it pre-dates these templates' deployment. Editors are reverting WP:MOS- and MOS:ACCESS-compliance updates to MOS:MATH on the basis of this essay [24].

A background point from the opening paragraph of WP:MOS: "If any contradiction arises, this page has precedence over all detail pages of the guideline[e.g. MOS:MATH], style essays [e.g. WP:INDENT], and the Simplified Manual of Style." The policy basis of this is WP:CONLEVEL: no individual or group of topical editors can make up their own rules to override site-wide consensus based on their personal preferences. No WP:IAR rationale has been provided for forking MOS:MATH from the rest of MoS on this trivial point. This RfC is a procedural one, since at least two editors are edit-warring against MOS:MATH's accessibility compliance and demanding a show of consensus to comply.

 — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  13:32, 3 December 2017 (UTC)

A better summary of the RFC issue is: "Should articles be forbidden from using colons to indent displayed equations, as in mathematics, chemistry, and other fields?" Tens of thousands of articles, including featured articles such as Californium, use colons for indentation. There is no recent "fork" here, as the language at the Math MOS has been in place since at least 2005 [25]. There is also no template that is even somewhat often used instead of colons to indent equations that appear on their own line - this indentation is essentially always done with colons. The MOS should reflect this near-universal usage, where the Wikipedia style is very clear from practice. At the same time, the developers should work to make this style emit better HTML. — Carl (CBM · talk) 13:41, 3 December 2017 (UTC)

Separately, neither WP:ACCESS and WP:MOS forbids the use of colons, and I think that all of the MOS policies are currently in agreement that colons can be used. — Carl (CBM · talk) 13:50, 3 December 2017 (UTC)

Congratulations for just contradicting yourself. It isn't possible for a guideline to "forbid" anything anyway. If there's a technical necessity for some reason to use : markup for non-list indentation, anyone can cite WP:IAR and just do it. It's difficult to imagine such a scenario, but whatever. No one can be "punished" for not writing in compliance with MoS. The only issues here are PoV-forking in an MoS that has nothing to do with indentation, way from the main MoS page and the accessibility MoS page, which do have something to do with indentation; giving bad advice when better advice is available; and (in theory) interfering with editors using the better advice to produce more accessible markup after the fact. No where anywhere in this is there any suggestion that anyone will be forced to stop misusing colons for indentation in articles (and it's not like we're going to stop doing it on talk pages, a lost cause until they're replace with some kind of threaded messaging system that's also capable of rendering MediaWiki markup samples accurately).  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  03:28, 4 December 2017 (UTC)

• Indents are perfectly fine to do with colons, and I would oppose doing them with any other methods. Headbomb {t · c · p · b} 13:55, 3 December 2017 (UTC)

  Also, to all those complaining that the issue hasn't been addressed in years, Mediawiki is open sourced. If the WMF hasn't coded the solution to this rather low-priority thing, why not apply a little WP:SOFIXIT? Headbomb {t · c · p · b} 22:21, 6 December 2017 (UTC)

  What Wikitext is VE producing for indents? · · · Peter (Southwood) ^(talk): 14:02, 3 December 2017 (UTC)

  Nothing. You can use blockquotes if you want something indented in the visual editor. (In the wikitext mode, it's whatever you type, just like the older wikitext editors.) Whatamidoing (WMF) (talk) 19:47, 6 December 2017 (UTC)

• Indenting in this way makes sense in this context... and if it conflicts with MOS? Well, MOS does say that there will be exceptions. I think this is a valid exception. Blueboar (talk) 14:08, 3 December 2017 (UTC)
  • I don't think there is a conflict - the MOS has always allowed colons for indentation, as evidenced by their use in featured articles. I think the proposal here is, essentially, to change the MOS to forbid colons. Some language was added to WP:ACCESS just today [26]. — Carl (CBM · talk) 14:25, 3 December 2017 (UTC)

    Wait... there wasn’t any conflict between practice and guidance... until SMC created one with his recent edit to ACCESS? With no prior discussion for that recent edit? And then he points us to CONLEVEL? (Based on an edit that had a consensus of exactly one person... himself!) ... talk about gaming the system! I have reverted his edit. The way this is supposed to work is that we hash it out first, reach consensus, and THEN write guidance to reflect that consensus. An editor can’t slip in a change to guidance, with no discussion, and then immediately turn around and claim CONLEVEL applies. Blueboar (talk) 15:07, 3 December 2017 (UTC)

• Not yet. You haven't really come up with, or let everyone figure out, a good alternative. There have been some thoughts discussed, but this RFC is premature until there's something more solid to recommend. You also haven't addressed the technical feasibility of an automatic conversion tool, because something like "the gnomes will fix it all", is not a proper answer for that. –Deacon Vorbis (carbon • videos) 14:11, 3 December 2017 (UTC)
• No but only if it's technically possible to distinguish indentation and actual definition lists with an acceptably small increase in parsing time. Semantically, since the <dd> tag is only supposed to appear as a definition following a <dt> tag, if a ;/: MediaWiki list doesn't begin with a ; item (or doesn't contain any ; items) then all : in that list could be treated by the software as <p> with indentation. Jc86035 (talk) 14:30, 3 December 2017 (UTC)
• Oppose. If the MOS does not correctly explain that colon indentation is how Wikipedia presents displayed equations, fix the MOS instead. Or maybe go for a technical fix and stop treating ":" as a HTML "definition list" for screen readers: everywhere on Wikipedia, it is used for indentation level. A fix for this should include talk pages. —Kusma (t·c) 14:32, 3 December 2017 (UTC)

  There is no (forthcoming) technical fix. One has been asked for from the MediaWiki developers for over a decade and they've done nothing to fix it.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  03:22, 4 December 2017 (UTC)

  There might be, if m:2017 Community Wishlist Survey/Reading/Functional and beautiful math for everyone were more popular. But in general, if you're interested in technical fixes, you should start there and work backwards to the detailed discussions at the German Wikipedia about this subject (earlier this year; look for a proposal by User:Debenben). Whatamidoing (WMF) (talk) 19:47, 6 December 2017 (UTC)

• Oppose proposed change to longstanding guidelines. Firstly, this is arguably one of the most ill-formed RfCs I've ever seen, and is unlikely to lead to a new consensus because it is not even clear what the "consensus" concerns. How, exactly, should displayed math be indented? As a block quotation? Using math display="block">? Some other method using templates? The phrasing is also highly misleading and non-neutral ("WP editors have long misused..."), with evidence for the "long misuse" apparently consisting of this edit and this revert, both from today by the same editor attempting to assert that the MOSMATH guideline is in conflict with ACCESS. Concretely, what seems to be proposed is this: that the way displayed math is typeset in Wikitext is to be changed on all of our mathematics and scientific articles, including all featured mathematics articles and good articles. Implementing this proposed change would require someone trusted by the community, with toolserver access, to change possibly millions of lines of code in tens of thousands of articles. Legions of mathematics and scientific editors would need to familiarize themselves with a more complicated syntax for doing basic Wikipedia editing (and it is not even obvious what that syntax actually is as of this writing). Editing Wikipedia would become correspondingly less inviting for new editors because of the more arcane methods of indentation that are proposed (when those new arcane methods actually are properly proposed). Not only has there been no such impact assessment, but the stated reasons for the proposal are spurious, as far as I can tell. The referenced part of WP:MOS discusses the formatting of block quotations, not displayed math. The relevant content guideline, with longstanding established consensus, on how math should be typeset when displayed on its own line, is WP:MOSMATH. It has also been asserted that this longstanding guideline is in conflict with WP:ACCESS, but while WP:ACCESS notes that the use of colons is not semantically ideal for this purpose, it even provides guidance on how to use colons for exactly this purpose. I agree with others here that, if the semantics of the way the colon is translated into html do not agree with the intended semantics, the issue should be fixed at the software level, not by requiring Wikipedia's new editors to learn CSS. Finally, I do not think this is a significant issue with screen readers and displayed math. Far greater is the issue of making equation alt text understandable to the vision impaired. The semantics of indentation are by far a secondary concern. Sławomir Biały (talk) 15:10, 3 December 2017 (UTC)

  Hear, hear! I'm sick and tired of hearing about how screen readers can't understand this and that. If I can see it, the screen reader can describe it. Fix the broken screen readers. EEng 17:32, 3 December 2017 (UTC)

  You realize you're supporting a minor MoS page contradicting two major ones, including the main one, in away that violates WP:CONLEVEL policy, right?  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  03:22, 4 December 2017 (UTC)

  Among several points that I raised in my vote, was your failure to show any contradiction with existing guidelines. Sławomir Biały (talk) 11:16, 4 December 2017 (UTC)

• Oppose. WP:MOS has not section about indentation and use of colon for that. All occurrences of "indentation" is this page are about block quotations, not at all about the usage of colons in math and talk pages. MOS:ACCESS says Colons (:) at the start of a line ... is not ideal for accessibility or semantics, but is currently in wide use. Thus, there is no guideline discouraging the use of colons for indentation (except for quotations), and there is nothing to which MOS:MATH and WP:INDENT should comply. Moreover, accessibility includes ease of reading sources, and any replacement of colons must keep reading sources easy. No such replacement is proposed. D.Lazard (talk) 15:33, 3 December 2017 (UTC)
• Support The use of colons produces broken definition lists (and broken html) that are yet another unnecessary annoyance for anybody using a screen reader. Their use should be discouraged, and it should be obvious that we ought to be bringing guidelines documenting poor practice into line with guidelines recommending best practice – which is to use one of the already existing templates that produce visual indenting without causing any problems for visually impaired readers. --RexxS (talk) 18:04, 3 December 2017 (UTC)
• Comment: This is Yet Another Case of the WMF doing something stupid (putting out HTML that contains definition lists for content that isn't even close to being a list of definitions) and the community trying to work around the stupidity.

$90 million dollars in assets, but somehow they can't afford to hire someone to fix the ancient creaky wikimarkup-to-HTML conversion software. --Guy Macon (talk) 19:04, 3 December 2017 (UTC)

That is a misstatement of the case. They haven't gotten around to it because that would cause a single wikitext encoding to create two different kinds HTML. That's bad for everyone--developers, users, and editors. --Izno (talk) 21:11, 4 December 2017 (UTC)

• Tentative support per RexxS. The {{in5}} template appears to be an adequate replacement for indentation of formulas and other things. I don't see this as creating a huge burden for the community: those who wish to change colon indentation to something more suitable could do so as they please with the support of the MOS; this proposal wouldn't mandate an immediate change of every instance, as at least one "oppose" suggests. I also don't see this as being problematic for new contributors: they can continue to use colons, just as many use hyphens instead of en-dashes in numeric ranges—no one is punished, but those who notice will quietly fix it. Rebbing 19:10, 3 December 2017 (UTC)
• Oppose. This is the wrong fix to a problem that is invisible to most editors and is really an issue in the Wikimedia engine having nothing to do with math. It would make Wikipedia mathematics editing harder, pointlessly, at a time when Wikipedia still lags behind literally every other mathematics-publishing site on the web in the quality of its mathematics formatting (see m:2017 Community Wishlist Survey/Reading/Functional and beautiful math for everyone) and when we still have battling gnomes some of whom are systematically going through mathematics articles stripping out <math> formatting and replacing it with html because our <math> formatting is so bad and some others of which are doing the opposite. The correct solution is for the Wikimedia developers to realize that the users have overwhelmingly decided that : means indent, not definition list, and to change how it is translated into html to reflect that. —David Eppstein (talk) 20:07, 3 December 2017 (UTC)
• Comment If we are to do it then the <math display="block"> is the format we should use, it is a special software feature specifically designed to work with this problem. There are something of the order 35,000 articles which use math tags, I can generate a list if needed. It's not an unreasonable number of articles to use some bot or tool to process the articles. I'm not convinced there is enough need to do this and whether this is really a case of busy work. --Salix alba (talk): 20:27, 3 December 2017 (UTC)
• Oppose deprecating ":" as standard indent. The recommended alternative, such as it is, is more cumbersome for something as often-used (especially for multileveling), and is fragile (equal-signs in math equations!). The use it too widely ingrained in too many places to change without being disruptive. If the problem is that colon makes HTML with incorrect screen-reading for the visual effect it creates and everyone uses it for the visual and visual-content/semantics effect it creats, then fix the HTML generator. I think WP:DLISTs are fairly rare. And they are fragile (in general and also towards screen-readers) when written using semi-colon/colon. We have a template set for them that is less fragile. So let's:
  1. Work towards using a template to in a less-common situation and to make things less fragile.
  2. Then make colon just do intending because that's the common use anyway.

For #1, a quarry for "line beginning with a semicolon" would be useful. that would also find places that such a syntax is used as inappropriate WP:PSEUDOHEADs. DMacks (talk) 20:58, 3 December 2017 (UTC)

• Oppose. A classic case of the tail trying to wag the dog. If the problems arise because of the association of the starting colon with the HTML definition element, then the solution is obvious, you change the association instead of attempting wholesale behavioral modification of the editing population.--Bill Cherowitzo (talk) 21:03, 3 December 2017 (UTC)
• Oppose. A colon means indentation in Wikipedia and changing that is a silly idea. What should be fixed if anything for accessibility is how : is changed into html. Figure out how we should represent indents in the first place rather than having people use some other symbol which generates this other html. Dmcq (talk) 21:13, 3 December 2017 (UTC)

  This is not a change; it's a conflict between an old MoS page (focused on nothing but math and having no bearing on indentation) advising bad markup, and two better-maintained MoS pages which absolutely do have normative things to say about page formatting, one of them being the main MoS page which trumps its subpages in the event of any conflict.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  03:22, 4 December 2017 (UTC)

  No, it doesn't. As you can see, consensus supports the currently used style, and the MoS as a descriptive document should reflect that. —Kusma (t·c) 09:57, 4 December 2017 (UTC)

• Support, obviously, as the one who opened the RfC, and for reasons already given.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  03:23, 4 December 2017 (UTC)
• Support. MOS:MATH#Typesetting of mathematical formulae and MOS:DLIST contradict each other on colon indents and should be made consistent. The former leads to HTML that fails validation. That's not just of academic concern. It generates nonsense output for visually impaired users, complicates navigation for keyboard-only users, and scrambles the page structure with possible SEO consequences. Even if colon indents were valid HTML, they'd still be an HTML hack doing poorly what CSS does well. Sure, <dl><dd> displays the desired way in some configurations, but that's not true of all browsers, devices, and skins. For example, a <dl><dd> between two <p>s is noticeably off-center vertically in the Minerva skin. MOS:DLIST leads to conforming HTML, and avoids all of these problems. Maybe someone can suggest for Extension:Math to support <math class="some-class"> to make it nicer to attach CSS to the tag in lieu of colon indents. Matt Fitzpatrick (talk) 11:10, 4 December 2017 (UTC)

  Wouldn't it make more sense to bring MOS:DLIST into line with the standard usage on Wikipedia? And then fix the conversion to html? Sławomir Biały (talk) 11:18, 4 December 2017 (UTC)

  As noted above, fixing the conversion to HTML has been listed in the WMF MediaWiki bug tracker as a to-do item for over ten years. They simply do not ever get around to doing it, and apparently never will. It is thus upon us to write accessible code rather than rely on the software to fix it for us when we don't. PS: Using : for indentation is not a "standard". There is no policy requiring it, and there is no guideline demanding it, other than one disputed line in MOS:MATH (a page which has nothing to do with indentation) trying to WP:POLICYFORK from the rest of MoS, which is itself against CONLEVEL policy. Using : for indentation is a bad habit we should not continue to do in actual articles (even if we think talk pages are a lost cause), because we know it's an accessibility problem and we know there are very easy other ways to do it properly. There is nothing even faintly challenging about doing {{blockindent|Foo bar baz}} instead of :Foo bar baz. It costs us nothing but a few characters, and is actually far more robust, because the colon markup is easily bollixed. For example, if an inexperienced editor closes a linebreak, Yadda yadda.:Foo bar baz, it fails, but this is not true of the templated version. There are various other circumstance under which the colon markup fails, such as being the first line inside a newly opened block element (full bug documentation here). The way the "I don't get it and don't care" responses above are going, this bulk of this RfC is just a big "fuck you" to people who depend upon even marginal accessibility at this site. Not cool. Not viable.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  11:49, 4 December 2017 (UTC)

  Comment: As one can see by looking at the source of the preceding comment, the one who opened this RfC uses colons for indenting. There is something wrong here :-) D.Lazard (talk) 12:03, 4 December 2017 (UTC)

  But the problem with screen readers and math is not the indentation, it's the math. This is a "fix" for the wrong problem. In any case, as the Phabricator link shows, the devs are aware of this issue but apparently do not think it is a substantial accessibility concern despite knowing more about the technical side of things than probably most of us here. If there is a strong case for an ACCESS violation, then I would raise it with the devs or the foundation. Sławomir Biały (talk) 12:33, 4 December 2017 (UTC)

• Moot. This seems to have gotten lost, but I just wanted to say again that this is all pointless until someone comes up with a workable alternative, and tests it – extensively. I've seen multiple different templates suggested, but are we sure we really want to co-opt something beyond its main purpose for something this major? Should we come up with a new dedicated one? Should we add an attribute to the <math> tag? Will whatever is ultimately proposed work if it's set on a line by itself surrounded by spaces without adding extra paragraphs? Because if not, then page sources become more difficult to read and edit. I'm vaguely aware of a desire to add MathJax support (although I haven't really followed this); will a proposed solution play nicely if it's added? Again, until this sort of stuff is hashed out, any sort of policy change is premature – and yes, SMc, it is a change. –Deacon Vorbis (carbon • videos) 15:01, 4 December 2017 (UTC)
• Support in principle, per RexxS, though I would have liked to see a more concrete draft change on which to comment. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 17:52, 4 December 2017 (UTC)
• Comment: FWIW, I'm trying to start a discussion specifically on the "expand the functionality of the math element" aspect of this issue at Wikipedia talk:Manual of Style/Mathematics#Extending math element functionality (merely to consider the possibility/feasibility of providing this alternative method of indenting math in particular). Also, just to make this explicit: as indicated in a piped link above by the OP, other relevant discussion predating this RFC is at Wikipedia talk:Manual of Style/Mathematics#Indenting. - dcljr (talk) 19:00, 4 December 2017 (UTC)
• Oppose: I think I understand the issue (that the use of a colon is an abuse), but unless there is a workable solution, I cannot support the change. -- Taku (talk) 21:42, 4 December 2017 (UTC)
• Oppose in over twenty years of writing HTML, I have not once used a dd/dl style list. I would support an alternate proposal to formally redefine ":" to be an "indented list", in a way that codifies and allows for its co-mingling with ul and ol lists, yet allows it to serve as generic indentation as well. power~enwiki (π, ν) 01:51, 9 December 2017 (UTC)

Math block display

$$e^{i\pi }=0$$

^ That looks indented to me. That seems like the functional and correct alternative. --Izno (talk) 21:11, 4 December 2017 (UTC)

Yes, that produces the correct appearance, but it's much more cumbersome to type. And it's not an improvement to use the usual solution when things are too cumbersome to type, templates, because | and = are used too often within mathematics formulas and are a pain to use as characters in the arguments to templates. Apparently, though, this solution is even worse in its html semantics than using a colon for indented formulas, because it nests <div> within <p>, not allowed in html. And if that were fixed, the right solution would be for the engine to recognize :<math> and translate it into the block display as it already does (note that when math is part of an indented block, it's displayed bigger than in inline text) and to produce cleaner html for it. —David Eppstein (talk) 21:30, 4 December 2017 (UTC)

div-not-in-p: Is there an actual Phabricator task regarding that issue? (Edit: I have submitted one at T182041.)

right solution would be for the engine to recognize :<math> and translate it into the block display You and others keep saying this. I do not agree that it is a true statement, for multiple reasons (already elaborated on the Phabricator task for that "improvement" already).

cumbersome to type There are many things cumbersome to type--for example, image syntax. Yet we somehow persist. I am not entirely sure why you're going on about templates, as the above is not a template nor is it in a template. --Izno (talk) 21:55, 4 December 2017 (UTC)

Maybe the better solution would be for the system to treat <math> when it is placed on its own line always as if it were a block. That reduces the burden further on us, and I would guess that's the intent in most cases when math appears on its own line. --Izno (talk) 21:58, 4 December 2017 (UTC)

<math> already sets its content to be class=mwe-math-element, so why don't we just use CSS (as was asserted to be the "correct" solution) in our skins to indent it? DMacks (talk) 22:09, 4 December 2017 (UTC)

The reason that doesn't work is because the Math extension HTML doesn't provide the necessary classes presently, without setting the math element explicitly to display as block, to differentiate block formatting from inline formatting for targeting in the CSS file. This failure is at presently due to the task on Phabricator I just filed. If the div were not placed inside of a p, we'd be fine to sort that out that way (minus the benefits that explicitly setting block currently provides, which is slightly larger presentation I think, but we don't get that already :D). I think I'll go file my other suggestion and see who pops up. --Izno (talk) 22:25, 4 December 2017 (UTC)

"more cumbersome to type" is a pretty poor reason to break accessibility and harm the ability to access Wikipedia for people with visual disabilities. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 08:29, 5 December 2017 (UTC)

Do really screen readers allow accessibility for math articles? I am not a specialist, but I am not sure that screen readers are useful for reading math. As far as I know, people with visual disabilities prefer the latex description of formulas rather than a spatial description of their displayed form that ignore the mathematical semantic. Thus accessibility implies to leave latex source as simple as possible, and this is in favor of keeping colon for indenting math. In any case, if screen readers are unable to deal with the present use of colon in math, they are certainly unable to deal properly with displayed formulas, and, in this discussion, the argument of accessibility is a pure fallacy. D.Lazard (talk) 09:34, 5 December 2017 (UTC)

To answer your question. Yes, all math has alt tags, which can be read by the the screen reader and some modern screenreaders can handle mathml to some degree (there is a hidden mathml description). There are also some specialised extensions, which can be used to enhance that even further. Screenreaders are able to handle colons just fine btw, it's just that they might tell screenreader users that a list will follow, while there won't be a list. This adds several words/sentences to the pronunciation that might be confusing and distracting for screenreader users. —TheDJ (talk • contribs) 10:14, 5 December 2017 (UTC)

If you are talking of the option <math alt= > you are wrong: it is rarely used in math articles, and, when used, the provided text is usually confusing, and, in any case, less clear than the latex source. In any case, alt tags are the worse solution, as you will never find math-competent editors that are willing to translate latex in English. The few alt tags that I have encountered in my edits (more than 1000 math articles in my watch list) are not understandable, or at least highly confusing. D.Lazard (talk) 11:15, 5 December 2017 (UTC)

No, the math tag where it displays an image includes the LaTeX as the alt attribute automatically. --Izno (talk) 15:25, 5 December 2017 (UTC)

The behavior is also different between the two versions in terms of what gets produced depending on if there are blank lines before/after the formula, or if there are no blank lines, but newlines, or if it's all written as a single line. I don't know HTML well enough to really know what's better, worse, or wrong, but it seems like a displayed equation should be part of the same <p>...</p> block, since it's usually part of the same paragraph (often part of the same running sentence even). It's not like that currently, but regardless, <math display="block">...</math> is producing some inconsistent results. Is there a wikitext token to just say "leave this line blank"? Like a hyphen on a line by itself or something. That would at least mitigate the problem of having LaTeX code crammed together with English if there's going to be some difficulty in figuring out if blank lines should be ignored or not. –Deacon Vorbis (carbon • videos) 23:07, 4 December 2017 (UTC)

{{Block indent}} uses <div>, and it's valid markup to nest divs inside each other. There is nothing faintly "cumbersome", as wikitext goes, about {{block quote|1=Your math here}}, expecially given the arcane geekery that goes into formula markup itself. This "it's too hard, so I'm going to use : and screw all those people who use screen readers" is about as plausible as NASA engineers claiming it's just too complicated to use turn signals when they're driving to work.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  11:24, 6 December 2017 (UTC)

If you convert to templates, then you won't be able to use the equation editor in the visual editor. If you haven't tried it before, then this link should take you to a little equation in my sandbox. (Setting block formatting is one click from the quick edit mode, or under the 'Options' tab in the full editing mode, but the other features in the full mode are even cooler.) Whatamidoing (WMF) (talk) 20:07, 6 December 2017 (UTC)

@Whatamidoing (WMF): Thanks for the ping and for taking the time to try and help with the problem.

I did a little survey in the German Wikipedia a few months ago. The long term goal that got the most votes was to turn <math> into proper inline math with \textstyle as default and use something like <math display="block"> or some equivalent notation as a proper block formula. The plan that I would have suggested is the following: Resurrect the MathJax display method which already was configured such that <math> was inline. It only turned it into a block equation for new lines with a colon in front. If that is done, one could replace the colons with some other markup.

I still think this would be a good plan, but at the moment it does not seem to be possible to get enough support for it. The biggest problem in my view are not the colon indentations but all those workarounds like {{math}} etc. I might be biased because the German Wikipedia is one of the few projects not using them and in the survey they decided unanimously not to introduce them. As far as I know those are not accessible to screenreaders at all and I continue to be surprised that so many editors are happy to learn some special mix of HTML and wiki-templates to write some formulas. Other options I can think of:

• Push ahead with turning <math> into inline math even without MathJax: I do not know any website that uses server-side generated svg images for mathematical equations. I doubt that it is possible to use this technique to get a rendering that is at least as good as those HTML workarounds. If templates are used for inline math, there is no strong reason why inline should be made default for <math>. Also <math display="block"> cannot replace a lot of block formulas, because \text{} often looks ugly and for non-latin languages it might be not readable at all. Even dots at the end of a sentence look different in math tags than outside of them. Currently some editors prefer to write them outside of the math-tags of a block equation even though this might lead to them being broken into a new line. Finally one would need something that can take care of the numbering of equations and replace templates like {{NumBlk}}. Without those problems solved, such a change would just be a lot of work and might result in more workarounds.
• Bring back the "use HTML for simpe formulas" option that was abandoned in favour of MathJax: I still frequently encounter those \!\, hacks used to circumvent some bugs or because some editor wanted to ensure that all symbols and expressions have the same appearance. I am afraid that a solution like this might backfire and make everything worse.
• Change the global CSS to match that of enWP to make <math display="block"> indented everywhere: I think this does not really help. More or less everyone still uses the colons for indentations and with the problems mentioned above I do not see that this is going to change in the near future. In case this encourages people to use the new <math display="block"> option, there would be more than enough formulas still needing the colon indentation. Finally I do not know if there is a more intelligent solution than the

  .mwe-math-mathml-display math { display: inline; }
  

  abuse or if one should just leave the MathML rendering inconsistent.

Summary: At the moment I do not see a way out of this deadlock. I am kind of getting tired of all those meta-discussions and trying to convince people why something like MathJax is needed or why the WMF should care about math rendering. For now I will probably just go back to spending my time writing articles and maybe try again in a few years time.--Debenben (talk) 13:44, 9 December 2017 (UTC)

So I finally broke down and took a quick look at MathJax, and oh my god, why aren't we using this already? It really seems like the way to go. And if we're worried about accessibility via screen readers, it's apparently way better in that regard too. I'd also be fine with <math>...</math> for inline and <dmath>...</dmath> for a block as I saw suggested elsewhere (I can't remember where). I also still think that it would be good to keep these on separate lines in the editor with blank lines surrounding them to make it more readable, especially for long equations. And then it would be a lot better if there were a way to tell the parser to just "ignore this line" (no new paragraphs, and no breaking of lists, which would already be useful for separating comments on talk pages without having to worry about those same MOS:LISTGAP issues). But I have no idea how feasible that is, or how likely someone is to add it, even if it is. –Deacon Vorbis (carbon • videos) 17:27, 9 December 2017 (UTC)

MathJaX was supported at one point, but was removed in 2015. See phab:T99369 for a long discussion on the topic, and Wikipedia talk:WikiProject Mathematics/Archive/2015/Aug#Future of MathJax on wiki as well. Anomie⚔ 17:14, 10 December 2017 (UTC)

Closing

After running for seven days, this discussion has largely gotten opposition; people make strong points, including the absence of a comparable alternative (as demonstrated by colons being used by the proposer), the fact that this proposal would render numerous good and featured articles at variance with policy, and above all else, the fact that the proposer has added his preferred wording to MOS:ACCESS and then half an hour later referred to that change as a basis for this proposal. Moreover, over at WP:VPT, the proposer left the following note:

The RfC at Wikipedia:Village pump (policy)#RfC: Accessibility versus convenience in indentation was opened as a question of whether it's permissible for MOS:MATH, which has nothing to do with indentention, to demand that editors misuse definition list markup in articles for this purpose, when the main WP:MOS page and MOS:ACCESS have for years recommended a better method of indenting. This has somehow turned into a torches and pitchforks campaign to ban the use of accessible alternatives to the abuse of : markup. I've never seen anything like it in my entire 12 years here, and am skeptical that the regulars of VPTECH would agree with the rationales being offered there. There's a palpable hostility in play, toward accessibility, HTML specs, and WP:CONLEVEL policy.

Our policies outright forbid such hostile characterization of other editors, and blatant canvassing like this has the effect of tainting all further support. Editors who falsify pages for their own purposes, or commit blatant personal attacks on others, or who engage in public canvassing are typically given extended blocks as well as having their proposals closed. 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. Nyttend (talk) 21:27, 10 December 2017 (UTC)

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.

Followup

• The pile of accusations in the closer's WP:SUPERVOTE at the bottom of the RfC have all been refuted in detail. The actual canvassing to this discussion was by CBM here, in which he grossly misrepresented the nature, intent, and actual effect of the RfC's proposition, which is why the RfC had virtually no participation other than from WT:MATHS editors all making off-topic points about mathethematics, when this RfC was about WP:CONLEVEL policy and HTML specs. I don't really care, since the outcome has been slightly productive anyway; I'm just not going to let Nyttend's shipload of false WP:ASPERSIONS go unanswered.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  11:49, 12 December 2017 (UTC)
• Productive ongoing discussions since the RfC:
  • Wikipedia talk:Manual of Style/Mathematics#Extending math element functionality
  • Phabricator bug T6521 is seeing traction for the first time in over a decade as result of this RfC

 — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  11:49, 12 December 2017 (UTC)

Is Wikipedia:WikiProject Video games/Sources a guideline?

While reviewing an RFC, one of the arguments raised assumed Wikipedia:WikiProject Video games/Sources was a legit guideline. While someone did, a long time ago, incorrectly substitute the guideline template onto it (hence no tracking cat to discover it until now), there doesn't seem to be any actual discussion about it, which leads me to believe it was never raised for greater community discussion. Maybe it's fine as-is, though, since nobody's really raised it as an issue, but I thought I'd point it out here regardless. If it actually should be a guideline, the template should probably be updated to be non-subst, the page should likely should be moved out of its Wikiproject-subpage location, and its linkages (e.g., on WP:RS, WP:LGL) should reflect its official-ness status, if applicable. If not, it should probably be (un)tagged back as an essay or similar (and obviously can be otherwise left as-is). The latter is what seems safest to assume is the default in the absence of input to the contrary. --slakr^\ talk / 03:06, 5 December 2017 (UTC)

No, that's a WP:PROJPAGE (wikiproject advice essay). It's way, way too full of micro-detailed instruction creep to be a guideline.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  11:26, 6 December 2017 (UTC)

Where does it contradict policy? Benjamin (talk) 19:14, 10 December 2017 (UTC)

Its nothing to do with contradicting policy. Its a wikiproject advice page on the better (or worse) sources out there. To be elevated to an actual guideline it would need all the specific 'This is reliable, this isnt' removed - as reliability is dependant on context and information used, not solely the source. It could be turned into a guideline but what you would end up with would just be a cut-down version of WP:RS. So it would be completely redundant. Only in death does duty end (talk) 12:28, 11 December 2017 (UTC)

Yeah, no one said anything about contradicting policy. Example: I hereby declare that the word "cat" on Wikipedia shall be taken to mean felid, since the word is often used this way in English: "the tiger is the largest living cat", "many of members of the cat family are nearing extinction". Felis catus, the domesticated species, is to be referred to as the "domestic cat" or "house cat". This proposition contradicts no policies. Do you think it's a guideline?  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  17:02, 16 December 2017 (UTC)

Speaking for the VG project, we don't consider it a policy, nor an attempt to override it. But it is meant to say "in our field, these are the sources we have deemed to meet WP:RS", so that new editors know where to look for sources, and when we go to GA or FA, we can point questions about source reliability to that page. I will note that its discussion page , that's where we do determine if sources qualify or not, following the principles of WP:RS, in context of the video game industry. In any case, the top box on it was changed to be a WikiProject guideline ("essay" for all purposes). --Masem (t) 17:12, 11 December 2017 (UTC)

Right; that's a WP:PROJPAGE essay. We have many of them, and some of them are very good. They're not guidelines. It takes a tremendous amount of community buy-in to elevate one of those "topical RS" pages to guideline status, as we have done with WP:MEDRS. It doesn't happen unless the community considers it a really serious matter (e.g. people dying because they relied on bogus medical "information" in an article here).  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  17:02, 16 December 2017 (UTC)

RfC: Russian metro line article titles

See also: § RfC on naming of Chinese railway line articles

The section was named "Russian railway line article titles" when the first users started to comment. I hate to open yet another railway RfC (why is that topic area so fraught with dispute?) but move-warring has broken out and it needs to stop. How should articles on railway lines in Russia be titled?:  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  04:11, 9 December 2017 (UTC)

Topic	Option A	Option B	Option C	Option D
Description	En dash and lowercase "line"	Hyphen and uppercase "Line"	En dash, but uppercase	Hyphen but lowercase
Example line	Kalininsko–Solntsevskaya line	Kalininsko-Solntsevskaya Line	Kalininsko–Solntsevskaya Line	Kalininsko-Solntsevskaya line
Example station	Aviamotornaya (Kalininsko–Solntsevskaya line)	Aviamotornaya (Kalininsko-Solntsevskaya Line)	Aviamotornaya (Kalininsko–Solntsevskaya Line)	Aviamotornaya (Kalininsko-Solntsevskaya line)

Comments on Russian metro lines

• Use option A per WP:CONSISTENCY, MOS:DASH, MOS:CAPS, and WP:USEENGLISH. What the official name looks like in Russian bureaucratese is irrelevant on English Wikipedia, since English and Russian do not have the same punctuation and capitalization practices, nor do signage and encyclopedic writing, even in the same language. The English title of our article is a translated approximation of the name in Russian, and is subject to English orthography and to Wikipedia's title policy and its naming and style guidelines. Option B is wrong twice over, and options C and D are just pointless mishmash, listed only for completeness.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  04:11, 9 December 2017 (UTC)

Second Avenue Subway, BMT Fourth Avenue Line (more at Category:New York City Subway lines); Washington County, Sixth Avenue (more at Category:Streets in Manhattan). Who claims WP:CONSISTENCY and promotes an option that reduces consistency? Ping User:Dicklyon. 77.180.49.189 (talk) 00:18, 10 December 2017 (UTC)

Ah, you noticed some New Yorkers can be pretty stubborn, too. See Talk:IRT Lexington Avenue Line#Requested move 17 November 2017 where I failed to find a consensus in spite of the guidelines and evidence. Shit happens. As for street names, those became consistently treated as proper names (in the US at least) over 100 years ago. Counties, too. Lines, not. Dicklyon (talk) 00:26, 10 December 2017 (UTC)

Dicklyon could you compile a list and add evidence? Do you have more examples for lower case apart from lines? How is the distribution, e.g. https://www.rmt.org.uk/news/tube-chaos-on-piccadilly-line/ has "Picadilly Line", a UK website, about a UK line. 78.53.140.207 (talk) 00:50, 10 December 2017 (UTC)

Like many things, London Underground names are sometimes capped in sources. I believe the UK Trains project looked at that specifically and decided that all those would use lowercase line, hence Piccadilly line. See Wikipedia:WikiProject London/Naming conventions#Transport. And no, I'm not going to compile a list (of what?). Dicklyon (talk) 01:02, 10 December 2017 (UTC)

Dicklyon you claimed "Counties, too. Lines, not." but refuse "I'm not going to compile a list". So, what to do with a claim without proof? I gave an an example for X Line, but then you refer it to a UK WP project. Good to see double standard, WP:RUSSIA not allowed to handle things by its own. 78.53.140.207 (talk) 01:12, 10 December 2017 (UTC)

Well, it's not that simple. The London folks make their lines and stations MOS compliant a long time ago (2007?); but it was a recent big mess to convince the UK Railways project; see the archives of Wikipedia talk:WikiProject UK Railways for all the dirt on me that you want. We had a big to-do about similar problems in China recently, though it actually went easier; moved about 1600 "Xxx Railway Station" to "Xxx railway station" with the help of a bot after getting consensus that it was OK noncontroversial. Your situation should be similar, I think. Bottom line, there's a general consensus, usually, that we should follow our house style, not let wikiprojects make up conflicting styles. This still leaves them considerable latitude on titling and disambiguating conventions, as you see what's going on now in Taiwan and Iran discussions. Dicklyon (talk) 01:23, 10 December 2017 (UTC)

• I agree with SMcCandlish on this matter. Tony (talk) 05:32, 9 December 2017 (UTC)

User:Tony1: Second Avenue Subway, BMT Fourth Avenue Line more at Category:New York City Subway lines. How would changing titles of articles about Moscow Metro lines to use lower case increase WP:CONSISTENCY? 77.180.49.189 (talk) 00:20, 10 December 2017 (UTC)

• A obviously is the WP MOS way. Take a look at Kalininsko-Solntsevskaya Line which in it's Sept. 2005 state said "The Kalininskaya is a line of the Moscow Metro. Today it is the only line to be named after a figurehead instead of the areas that it connects." This makes it pretty clear that all (or nearly all?) of the Moscow metro lines are named for places they connect, like many other lines in most other cities and countries and metro systems; the en dash is clearly the right punctuation for connecting the two place or direction names, while the hyphen makes no sense. In Russian orthography, I expect things are different, and it's OK to use the hyphen in the Russian. And the capped "Line" came to this article in December 2005. Not too surprising to see overcapping this old, but that's not a reason to avoid fixing it. It's not capped in the Russian, so not clear why anyone thought that was a good idea in English; most likely it was done originally, back in the day, by someone unaware of WP:NCCAPS. There's work involved to fix all this, but it's not a big problem compared to some others we've fixed this year, so let's get started. Dicklyon (talk) 06:00, 9 December 2017 (UTC)

Comment the comment "This makes it pretty clear that all (or nearly all?) of the Moscow metro lines are named for places they connect" - makes it pretty clear that the author uses false information. Koltsevaya Line, Moscow Monorail, Moscow Central Circle, Third Interchange Contour. No, it's not like Beijing–Shanghai Railway where the two items connected by "–" mark the end points of a line. Several lines have been extended without any name change. Propsers have no clue and should leave it to WP:RUSSIA92.231.182.37 (talk) 06:26, 9 December 2017 (UTC)

Sorry, I intend the scope of my comment to be the metro lines with hyphens in their titles. I stand corrected. And no I did not suggest that the places named would necessarily be at the ends of a line, though that's common in many systems, at least ones that aren't growing. Dicklyon (talk) 06:42, 9 December 2017 (UTC)

• A ticks the most MOS boxes and IMO should be treated as a de facto standard format. Jasphetamine (talk) 10:44, 14 December 2017 (UTC)
• Oppose:

1. Procedural
   1. Should be taken to WP:RUSSIA because the editors of that project are the ones that do the actual work. Cannot find any improvement by User:SMcCandlish, User:Tony1 to the actual content. Will they do the maybe 100 000 edits that are needed to convert all occurences visible to the reader? 92.231.182.37 (talk) 06:10, 9 December 2017 (UTC)
   2. Status quo (Option B) is not presented fairly, was written by user that supports Option A. Also why would the current naming be put at "B"? That's no neutral representation.
2. Policies
   1. MOS:DASH - fine, see Guinea-Bissau, "-" is allowed. No, it's not like Beijing–Shanghai Railway where the two items connected by "–" mark the end points of a line. Several lines containing "-" in the name have been extended without any name change.
   2. WP:CONSISTENCY - WP:RUSSIA has Moscow Oblast, Shatursky District, Central Administrative Okrug, Varshavskoye Highway, Mira Avenue, Mokhovaya Street, Cosmonauts Alley, Chistoprudny Boulevard, Boulevard Ring, Nakhimovsky Prospekt, Sivtsev Vrazhek Lane, Lefortovo Tunnel, Moskvoretskaya Embankment, Moscow Ring Road, German Quarter, Vodootvodny Canal, Arbatskaya Square (Red Square too), Tsar Cannon, Chudov Monastery, State Kremlin Palace, Alexander Garden, Kremlin Arsenal, Spasskaya Tower, Bagration Bridge, Donskoye Cemetery, Bolshoi Theatre, Vnukovo International Airport, Nekrasov Library, Cosmos Hotel, Rumyantsev Museum
   3. MOS:CAPS - all fine.
   4. WP:USEENGLISH - the titles are already English.

92.231.182.37 (talk) 06:10, 9 December 2017 (UTC)

A detailed response to this has been posted in #Extended discussion of Russian railways, below.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  06:48, 9 December 2017 (UTC)

• I can support Option A per Dicklyon. It looks like it ties out to what is used for lines in other systems. Some of the stuff that got ported over to English ended up with some odd variations. There are a few that I’ve been meaning to get to myself. I can certainly help with some of the work on this if you need it. TastyPoutine ^{talk (if you dare)} 06:30, 9 December 2017 (UTC)
• Option A per WP:CONSISTENCY and WP:USEENGLISH. It would be just too unsightly and confusion to change the articles titles to something that is inconsistent with related articles. It would also fall out of line with the manual of styles linked above to change them. Boomer Vial^{Happy Holidays! • Contribs} 06:38, 9 December 2017 (UTC)
• Follow the sources. The entire discussion seems irrelevant navel-gazing. What do reliable sources use? Wikipedia's policy is to always do what reliable English-language sources do, if they exist. What do Moscow travel guides use? As reliable sources about different topics often use different conventions, Wikipedia is not internally consistent (and that is not a particularly worthwhile goal anyway). —Kusma (t·c) 11:22, 9 December 2017 (UTC)

@Kusma: this is a common misapprehension. We do not always follow the styles used in reliable English language sources, for a number of reasons: like other publications, we have our own style rules embodied in the Manual of Style; reliable sources are of different kinds, some more specialized than others, and we take into account those that are appropriate for a general encyclopedia. Peter coxhead (talk) 11:33, 9 December 2017 (UTC)

Of course, our rules are not fixed in stone and can be changed (if there is consensus to do so)... there are a lot of editors who think our MOS rule should be changed to “follow the sources”. Don’t know if it is a majority of editors who think that... but if not, it is a sizable minority. Blueboar (talk) 11:57, 9 December 2017 (UTC)

A response to this has been posted in #Extended discussion of Russian railways, below.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  12:24, 9 December 2017 (UTC)

Sourcing tends to be all over the place. Just as in some cases, there isn’t consistency in transliterating Russian, you also don’t get consistency in this matter. The Metro itself uses lowercase [27] while TASS uses an uppercase [28]. For what it’s worth, TASS also called the Koltsevaya Line the Circle Line which is probably correct since Koltsevaya in Russian is meant to be descriptive. But that’s a fight with another IP editor for another day. In any case, even the Moscow Times which is one of your best local sources isn’t particularly consistent (lowercase [29]) and (uppercase [30]) The New York Times wavers between the colloquial name with uppercase [31] and the official name with lowercase [32]. So in that case, my guess would be that the MOS is the best guide. TastyPoutine ^{talk (if you dare)} 13:35, 9 December 2017 (UTC)

Thank you TastyPoutine. To add a not particularly RS: the English translation of Metro 2033 uses both "Red Line" and "Sokolnicheskaya line". In the absence of a strong argument that points in a different direction, lowercase "line" probably works best, although if a different convention has been in place for years, I see no particularly good reason to change that. —Kusma (t·c) 19:23, 9 December 2017 (UTC)

I would put it out there that it may be worth making effort to change. Articles that got ported over from foreign languages were pretty inconsistently set up and it’s probably better to get it right than settle into inertia. Something written a decade ago likely set it but without a good MoS and did their best. And the extensiveness of the system makes it difficult to make wholesale change. But if we can, I think wwe should make the right change now and move on.TastyPoutine ^{talk (if you dare)} 20:02, 9 December 2017 (UTC)

• Comment Option B is used since 2005 [33] 92.227.230.156 (talk) 17:11, 9 December 2017 (UTC)

  I presume you are the same as the dynamic IP who made the big "Oppose" section above, which I interpret as a vote for B. It would be better to clarify there than to vote again. Dicklyon (talk) 19:18, 9 December 2017 (UTC)

  Dicklyon, statement by 92.227.230.156 says "Comment", which is not a vote. And it does not even endorse any of the options, only adds a new finding in chronological order, so all voters before might have been under-informed. 77.179.37.199 (talk) 23:49, 9 December 2017 (UTC)

  Since the anon is now pretending to be different editors, I've taken this to WP:SPI.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  06:04, 10 December 2017 (UTC)

  User:SMcCandlish claims the untrue. Where did anyone here claim to "to be different editors"? 92.231.183.209 (talk) 05:19, 13 December 2017 (UTC)

  Covered at the SPI report; VPPOL is not the place for this discussion.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  05:24, 13 December 2017 (UTC)

  User:SMcCandlish - VPPOL was the place where you made a claim regarding an activity that occurred here. Now you refuse to show the evidence. Did User:SMcCandlish lie? Where is the diff of the SPI where you cover that? 92.231.183.209 (talk) 05:42, 13 December 2017 (UTC)

  Take it to the right venue. See also WP:Tendentious editing; repeating demands after your told they're off topic doesn't make them on-topic.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  05:59, 13 December 2017 (UTC)

  Thanks for pointing out that Arbatsko-Pokrovskaya Line that's been capped since 2005. As you can see in books, sources often call it "Arbatsko-Pokrovskaya line" with lowercase line. It is not near the usual threshold of "consistently capitalized in sources" that we use to determine proper names. Dicklyon (talk) 05:25, 10 December 2017 (UTC)

Extended commentary by anon with multiple IP addresses

Comments regarding MOS:DASH

MOS:DASH lists Guinea-Bissau, so "-" is allowed. The "-" in the Moscow Metro articles are not connectors like Beijing–Shanghai Railway where the two items connected by "–" mark the end points of a line. Several lines containing "-" in the name have been extended without any name change. 77.179.78.253 (talk) 06:45, 9 December 2017 (UTC)

Comments regarding WP:CONSISTENCY

WP:RUSSIA consistently uses the type name in upper case:

• Moscow Oblast, Shatursky District, Central Administrative Okrug
• Varshavskoye Highway, Mira Avenue, Mokhovaya Street, Cosmonauts Alley, Chistoprudny Boulevard, Boulevard Ring, Nakhimovsky Prospekt, Sivtsev Vrazhek Lane, Lefortovo Tunnel, Moskvoretskaya Embankment, Moscow Ring Road, German Quarter, Vodootvodny Canal, Arbatskaya Square (Red Square too), Bagration Bridge, Northern Sea Route
• Tsar Cannon, Alexander Garden, Kremlin Arsenal, Chudov Monastery, State Kremlin Palace, Spasskaya Tower, Donskoye Cemetery, Bolshoi Theatre, Vnukovo International Airport, Nekrasov Library, Cosmos Hotel, Rumyantsev Museum
• Meshchera Lowlands, Crimean Peninsula, Kara Sea, Kara Strait

The content is consistent as it is. All Moscow Metro lines are named consistently. Hundreds of pages contain the line names. 77.179.78.253 (talk) 06:45, 9 December 2017 (UTC)

Also outside Russia many items use upper case. Even rail lines: Second Avenue Subway and all the lines in Category:New York City Subway lines. 77.179.76.40 (talk) 23:55, 9 December 2017 (UTC)

Comments regarding WP:USEENGLISH

WP:USEENGLISH - the titles are already English. They are perfect English. 77.179.78.253 (talk) 06:45, 9 December 2017 (UTC)

They are as English as possible : NYC's BMT Fourth Avenue Line, Moscow's Filyovskaya Line. 77.179.76.40 (talk) 23:57, 9 December 2017 (UTC)

Comments regarding MOS:CAPS

MOS:CAPS does not prohibit capitalization of proper names. MOS:NAMECAPS explicitly allows it. 77.179.78.253 (talk)

Extended discussion of Russian metro lines

• This discussion has been "advertised" to WT:AT, WT:NCCAPS, WT:USEENGLISH, WT:MOS, WT:MOSCAPS, WT:TRAINS, and WT:RUSSIA. The "WP:Naming conventions (Russia)" page is an old draft abandoned around 2011, so I skipped that; no one uses its talk page.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  04:36, 9 December 2017 (UTC)
• Response to the anon's long block of FUD up there: This is not a "support" or "oppose" RfC; its a four-way multiple choice. Option B is not the status quo ante; they were at totally different names until you (at a different IP address) moved them [34] just over a day ago. And, no, it will not be taken to WT:RUSSIA (which has already been notified of this RfC). The entire point of WP:Village pump is to get broad editorial input, to assess actual site-wide consensus and avoid a bloc vote by an insular wikiproject or other knot of editors apt to produce a WP:FALSECONSENSUS. This was already explained to you at RM/TR, so I have to wonder why you're pretending it was not and are recycling the same "I want this on my turf" argument when you already know that is not going to fly.

  To address your various policy mis-citations: MOS:DASH: Guinea-Bissau is a single place, it is not a construction expressive of a relationship linking two different places the way Kalininsko–Solntsevskaya line does. WP:CONSISTENCY is a site-wide policy; it does not mean "make articles on my favorite topic consistent with each other but inconsistent with those on all the other topics just for the hell of it". MOS:CAPS: if "all fine", why are you back at RM tendentiously and falsely pushing more of the same moves as "non-controversial" [35]? USEENGLISH: Yes, these titles are in English, which means they follow English-language norms, not Russian ones. That's the entire point.

  PS: Option B is written accurately, based on the exact justifications that you (at yet another IP address) offered at RM/TR [36]: because the Russians, in their language, use a hyphen and capitalize (according to you, anyway; even that has not been verified yet, but is irrelevant).
   — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  06:47, 9 December 2017 (UTC)

• Response to Blueboar and Kusma: "Follow the sources" already is the rule, just applied in a common sense manner. MoS is based on major style guides, ironing out where they conflict. Beyond that, an unusual stylization (i.e. which doesn't match what MoS says to do based on what mainstream style guides in print say to do) is permissible here if it's used consistently in a sizable majority of reliable sources. Unless I'm sorely misremembering, you brokered that codicil yourself, Blueboar, so it's weird to me to see you acting here today like it's not in place. You and Kusma and a handful of others (not a large minority, or MoS probably would no longer exist) seem to want style at every article to follow the style used in specialist material for the topic on question. That's never going to happen for various reasons, the most obvious of which are: A) Music-journalism writing about rock stars and physics-journal writing about cosmology [and so on] use styles that are not appropriate for encyclopedic writing. B) Sources reliable for specialized facts about a topic are not reliable for how to best write English (unless they're coincidentally sources specialized about how to best write English, such as reputably published style guides). C) Few topics are the exclusive subject of a single specialized field, and different fields use different styles, so a unified MoS becomes inevitable if for no other reason that to stop specialists in different fields from fighting over style. That's how and why MoS arose in the first place, less than a year after WP was started, because the squabbling was already intolerably disruptive by then. Publishers have style guides for a reason.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  12:29, 9 December 2017 (UTC)

  @SMcCandlish: Indeed consistency of style across all of Wikipedia is not an achievable or even worthy goal. (WP:ENGVAR/MOS:RETAIN is one of our traditional rules in this regard, which achieves peace without enforcing consistency between articles). With respect to article titles, following the sources appropriate for the field is what we have done for years. Mao Zedong and Go Seigen and Shiing-Shen Chern and Chiang Kai-shek and Samuel C. C. Ting are five articles about Chinese people alive during the 20th century following five different and wildly inconsistent conventions for their name order, romanisation, language use, capitalisation and hyphenation. Each of them is at the correct title per Wikipedia:Naming conventions (use English). Legislating a consistent style for foreign topics against the evidence of scholarly publications just does not work. It is to Wikipedia's detriment to force people to use conventions against those correct in the article subject: it drives experts away and makes articles inconsistent with their sources. "Consistency" isn't worth that. So again, are there any relevant publications about Russian railways in English and what style do they use? —Kusma (t·c) 19:04, 9 December 2017 (UTC)

  Note that the discussion is not even about railways (which in Russia never use "line" or "Line" anyway), but specifically about metro (mainly Moscow Metro, though it will apply as well to other four cities which have more than one metro line).--Ymblanter (talk) 19:31, 9 December 2017 (UTC)

  The wording has been fixed.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  04:44, 12 December 2017 (UTC)

  Kusma, all you're doing is demonstrating my point for me. We do in fact have standard naming conventions for Chinese people (see WP:NCCHINA#Names of people); there are variations from it precisely because in those cases the bulk of the RS consistently do something different – and the same different thing – for those specific individuals. And if you think MoS's primary purpose is not cross-article consistency, you're not thinking about it very hard. If that were true we would need not a style guide at all, and it would simply be left to every wikiproject or even every random cluster of editors at every article to decide topic-by-topic on all style matters. We tried that in WP's first year and it was a disaster.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  05:11, 10 December 2017 (UTC)

  The question is always when we should follow the sources instead of our standards. Our difference seems to be that I think in cases of doubt, we should follow the sources. You seem to say in cases of doubt, we should impose some arbitrary standard. And indeed I agree that some sort of style guide, describing Wikipedia's common practice, is useful. However, I object to your characterisation of the MoS as saving Wikipedia from a "disaster" in its first year. I have admittedly not been here for Wikipedia's first year, but in the last thirteen years, the MoS has been a source of constant bickering that has created several ArbCom cases. The date unlinking debate alone led to millions of edits and thousands of hours of editor time that were used without a measurable overall improvement to Wikipedia. Infobox and citation style debates have cost us many good editors. It may look different from your end, but I have not perceived editors enforcing "standards" through the MOS to be a positive for Wikipedia: sometimes the net result is almost neutral (because the difference between "Line" and "line" is minuscule), sometimes negative (good editors gives up). —Kusma (t·c) 10:24, 10 December 2017 (UTC)

  It's not really clear what you're thinking when you say "follow the sources" in "cases of doubt". When sources are clear, we do follow them, as MOS:CAPS advises. When they're not, we default to our style (lowercase when it's not clear that sources treat the term as a proper name). Have you looked at sources on these metro lines? I have, and there's an awful lot of lowercase line there. In particular, see books like The Rough Guide to Moscow, Lonely Planet Moscow, and most fiction works that talk about Moscow metro lines, all with lowercase line. Dicklyon (talk) 17:29, 10 December 2017 (UTC)

  Kusma's anti-MoS fingerpointing is in the wrong direction anyway, on all counts (though see below for the spirit of the matter, which Kusma seems to intuit without realizing our guidelines are the solution not the problem).

  1. WP:NCCAPS, which is really the guideline central to these rail and metro moves, isn't part of MoS, but a subsidiary guideline of WP:AT policy. (It is and should be consistent with MOS:CAPS, of course, or we'd have a WP:POLICYFORK and conflicts between article titles and body text).
  2. The date auto-linking fiasco was caused by the MediaWiki developers deploying a problematic "feature" that did not work well here; MoS didn't cause that. (And it's not unique – similar disputes have erupted about WP:Flow, WP:Visual editor, and many other WMF technical debacles, like doing visual indentation with <dd> markup). There was an ArbCom case about date delinking in 2009 because certain individuals were engaging in uncivil behavior over the matter. ArbCom does not settle content disputes or write policy; "there was an ArbCom case" just means "certain editors were accused of being jerks". The end result of the de-linking (which the community decided in a series of RfCs and polls – not ArbCom, not MoS regulars) was obviously a net positive for the project, in getting rid of a problematic mess over which people were uncivilly squabbling, while reducing the pointless "sea of blue" overlinking effect our readers were being subjected to for no encyclopedic reason.
  3. MoS is entirely neutral on infoboxes, and leaves their inclusion up to editorial discretion at each article (see WP:INFOBOXUSE). People get into emotional infobox-related fights for MoS-unrelated reasons (and arguably WP-unrelated ones, to do with personal philosophies of information architecture and Web design "elegance"). Quitting in a huff after getting too emotionally invested in fighting about infoboxes (or any other trivial dispute) is a WP:CIR matter, not a policy problem.
  4. Citation style is covered by WP:CITE, which is not part of MoS. While I agree that disputation about citation style has frequently been disruptive, it has nothing to do with MoS. (MoS, including MOS:DATE, expectations are of course applied to citation content, when doing so does not directly conflict with a specific citation style that's used consistently in an article.)
  5. The other partly-MoS-related ArbCom case, in 2012, concerned incivility at WT:AT and WT:MOS in disputes about the wording of that policy and guideline (respectively) – just another editorial behavior matter, which could as easily have been about Pokemon or fungi. When ArbCom was asked last year if it considered the issue broad enough to apply to title and style discussions more generally (e.g. RMs, and RfCs like this one) it explicitly denied that expanded scope interpretation.

  "MoS has been a source of constant bickering that has created several ArbCom cases" simply isn't true; it's like blaming "the gov'ment" for all one's problems. Kusma's central concern, once the mis-blaming of MoS is cleared away, amounts to "people shouldn't bicker over stylistic trivia", which is true and good. MoS has eliminated the vast majority of style-related bickering that used to plague the project, article by article over the same trivia again and again; the handful of ArbCom cases were triggered by a few individuals who persisted in uncivil bickering. The most common "style" squabbling that recurs is actually over AT and NC, not MoS, matters (though citation to MoS often resolves them, because its applicability is so generalized and AT is not a style policy).

  Yes, "line" versus "Line" is trivial; continual disruptive bickering about it is not a trivial problem. The very fact that people will sometimes engage in it doggedly is why we need RfCs and naming conventions and style guidelines, to settle the question consistently and move on. Otherwise the same tedious dispute will still be happening in 2020 and in 2025. See also previous RfC on this page that closed a week or so ago in favor of developing something along the line of a MOS:TRANSPORT guideline; this RfC is another step toward that prescribed goal.
   — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  06:42, 12 December 2017 (UTC)

Scope

Resolved

As some mention below, this is more about metro lines than railways. I propose that to keep the noise down we limit to titles that come from Cyrillic titles such as "Святошинсько-Броварська лінія" which is now at Sviatoshynsko-Brovarska Line which is a line in the Kiev Metro in Ukraine (that is, not limit to Russia, but limit to such place-descriptive metro lines for now). This will reduce the fear of over-generalization, and we can discuss generalizations to other things elsewhere. Dicklyon (talk) 20:24, 9 December 2017 (UTC)

Quoting Ymblanter (19:31, 9 December 2017): "Note that the discussion is not even about railways (which in Russia never use "line" or "Line" anyway), but specifically about metro (mainly Moscow Metro, though it will apply as well to other four cities which have more than one metro line)." - Spasibo Yaroslav! I agree with Dicklyon that it should be consistent with Kiev Metro. It should be consistent accross with Minsk Metro too. And also with systems outside the capitals. 78.53.140.207 (talk) 00:35, 10 December 2017 (UTC)

• Section headings updated to reflect narrower scope. The original section names are preserved with anchors, so links don't break.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  04:40, 12 December 2017 (UTC)

Status

I wouldn't quite agree with SMcCandlish that move warring has broken out, but we do need to hash this out, again, apparently. An editor changed some disambiguators (not changing the caps and dash issues, but bringing them to my attention at WP:RMTR). So I moved a few things to conform with normal style. He asked for a revert of those moves, at WP:RMTR. The admin who did (part of) what he asked unfortunately made a mistake and overwrote a line article with a station article somehow before going off for the evening. Another admin saw the requests still there, now with SMcCandlish's objections, and tried to finish up, without noticing the problem. It's still a mess. We'll get it sorted, maybe not today. So it's a good thing SMcCandlish didn't provide a link to the line article, because it would just confuse by taking you to the station article (this is since fixed). Nevermind, back to the real issue. Dicklyon (talk) 05:38, 9 December 2017 (UTC)

User:Dicklyon, and who did actual work on the articles? None of you. You both come in, move some pages around and everywhere else the year-old naming system persists. 77.179.78.253 (talk) 07:01, 9 December 2017 (UTC)

I had every intention of doing a lot more work there, but that got put on hold by your move revert request. I'll get back to it later, I expect. Dicklyon (talk) 07:18, 9 December 2017 (UTC)

User:Dicklyon, how would you ensure all occurrences visible to reader are changed? What tool is there to list all occurences to be done? 85.182.27.83 (talk) 07:40, 9 December 2017 (UTC)

That would be so awesome! We do still have widespread visible linking through wongly styled redirects, with over-capitalization, missing hyphens, hyphens for dashes, etc., throughout the en.wp, and a tool that replaces those with the preferred-styling title would be great. I've recently had some luck getting bot operators to do some large-scale moves, for downcasing railway station in China and a few other places for example, so I think there's hope for such things on specific subsets, and I'm willing to give that a try in the Moscow metro case, and then see from there. Lacking such tool support, I find that getting the titles styled right first is a big help; then getting templates updated will typically fix the majority of appearances of wrongly styled titles. So a little manual work goes a long way. Want to help? Dicklyon (talk) 19:26, 9 December 2017 (UTC)

Dicklyon, it's not about templates, that's easy. "then getting templates updated will typically fix the majority of appearances of wrongly styled titles" - no, the problem is plain text. Without tool support it will take years, just look at districts and divisions of India. Several years ago five or so users decided to use "X district" where all of Wikipedia elsewhere uses "X District". And they still don't have it done fully. Why not help and create articles for the Line 11 several red links still exist.. ? I also see no consistency, some rail lines are singled out and many other things still have the type name capitalized, Mississippi River, Sixth Avenue (Manhattan). It should be done consistently for all things, only to do it for some classes (e.g. rail lines) is creating inconsistency. 77.179.37.199 (talk) 23:45, 9 December 2017 (UTC)

• User:Dicklyon claimed "So I moved a few things to conform with normal style.". But provides no evidence for his normal style. Normal style for many other subway and transport infratructure articles is to use upper case. Second Avenue Subway (Category:New York City Subway lines), Sixth Avenue (Category:Streets in Manhattan). Maybe move war there has no chance, so Moscow / Eurasia was selected? 77.180.49.189 (talk) 00:28, 10 December 2017 (UTC)

  I've been doing a lot of style work (using WP:MOS to define "normal style") on railway related articles around the world, as I find them. Recently a lot in China, Philippines, Malaysia, Vietnam, Australia; before that the whole of the UK, which was more of a challenge; it's true I haven't had much luck with the NYC subway folks yet, and recently lost a multi-RM there, so bummer. I had no plan to take on Russia, but your moves showed up at WP:RMTR, just too late for me to contest. Dicklyon (talk) 04:58, 10 December 2017 (UTC)

  How else would you capitalize Sixth Avenue? In US usage the "road type" words in street names are always capitalized ("Center Street", "Main Avenue", "Park Lane", and so on). They are proper names. "Sixth avenue" would be as nonsensical as "Jimmy stewart". --Khajidha (talk) 17:02, 13 December 2017 (UTC)

  PS - this also applies to your point about rivers. In the US many (possibly most rivers) are named "________ River". The word "river" is not some sort of type marker or disambiguation, it is part of the proper name. --Khajidha (talk) 17:10, 13 December 2017 (UTC)

Collapsing a dispute which has been mooted.

Error in the question's premise Moot  – The Russian-language-related wording no longer appears in the RfC question or table. SMcCandlish's proposed option B, described as Hyphen and uppercase "Line" to mimic the WP:OFFICIALNAME in Russian Cyrillic is supposed to represent the status quo, and it pretty much does, but with the false premise that the Russian does it this way. In all Russian sources and Russian wikipedia, line is lowercase "ли́ния" or "линия". Furthermore, the justification for the hyphen can be found in some of the line article histories as "easier to type", when the articles were moved back from the en dash after a move "per MOS:DASH"; nothing about official, Russian, or Cyrillic in that reason. A couple of IPs (perhaps the same person) have told me that the capped "Line" is a "year-old consensus". Not clear why or where that happened. So not clear what a vote for B would mean, but I'm sure people will explain their choices. Dicklyon (talk) 05:38, 9 December 2017 (UTC) Option "B" has been framed by a person supporting Option A. Not trustworthy at all. The "mimic" stuff is nonsense. Uppercase exists due to WP:CONSISTENCY 92.231.182.37 (talk) 06:12, 9 December 2017 (UTC) As noted in my response to the anon, option B was drafted on the basis of the anon's own claims. Whether the underling premise is true I did not investigate, but it doesn't matter, since the idea that we'd write English to match Russian orthography is nonsensical to begin with.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  07:00, 9 December 2017 (UTC) User:SMcCandlish is saying the untrue. Nowhere was it suggested that uppercase is done in Russian Cyrillic for "line". 77.179.78.253 (talk) 07:04, 9 December 2017 (UTC) I agree. He misinterpreted your statement "all metro lines in Russia use upper case type name ("X Line")" as being about in Russian, but you meant in en.wp titles. Still, my point, on which I agree with SMcCandlish, is that there's no logical basis for the status quo as represented in option B. It's just how it is now, which I think is what you were saying, too. Dicklyon (talk) 07:18, 9 December 2017 (UTC) Dicklyon, you claim "there's no logical basis for the status quo". But several have been given. 1) It is all consistent, the page movers will not fix it in all articles. Or is there a tool to control that? 2) It is consistent with bridges, roads, airports, lakes, districts, towers, palaces, etc in Russia. See Wikipedia:Village_pump (policy)#Comments regarding WP:CONSISTENCY and comment there. Present your logic. 3) "-" is not used to connect end points. Comment at Wikipedia:Village pump (policy)#Comments regarding MOS:DASH. 85.182.27.83 (talk) 07:36, 9 December 2017 (UTC) This is the third time this anon has called me a liar in this discussion (here and at RM/TR). Adding that to the ANI material. I did not lie at all: Here's a direct quote of the anon's actual statement in the original RM mess: 'all metro lines in Russia use upper case type name ("X Line") and use "-" as in Russian source, these are proper names'. That's an [ungrammatical] two-part claim about Russian-language sources. If the anon meant to say "All WP articles about metro lines in Russia use upper case type name ("X Line"), for no particular reason. Our article titles also use "-" as in Russian sources.', that would be a very different statement. The anon is in fact back-pedalling from an incorrect statement; the "these are proper names" bit demonstrates that, since being proper names would be an argument for capitalization but would have nothing to do with hyphen versus en dash. So, nice try, but no.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  07:44, 9 December 2017 (UTC) User:SMcCandlish is saying the untrue once again. He was not called a liar here. It was simply stated that "User:SMcCandlish is saying the untrue." 85.182.27.83 (talk) 07:53, 9 December 2017 (UTC) Don't be so quick to say he's calling you a liar, just because he says what you're saying is untrue. Consider the Russian capitalization rule, which I just looked up myself: "In compound proper names, as a rule, only the first member is capitalized: Чёрное море – Black Sea". So the lowercase линия actually gives no indication one way or the other about whether it's part of a proper name or not. I still say it's not, and maybe he is saying what you thought about the Russian, but it's not true he's claiming that that word would be capped in Russian. Anyway, no matter, things like "Xxx line" are not usually treated as a proper name in English (and Moscow oblast is only half the time, so we should probably downcase those, too), and the various things that are treated as proper names in English, like bridges and streets, are not relevant. Dicklyon (talk) 07:56, 9 December 2017 (UTC) Dicklyon, if you want to lower case type names of territorial entities you can start with Washington County. Note that CMOS suggests upper case, and that is what English WP does - everywhere except for India. Also, if the type name is not part of the proper name, then shouldn't it go into "()"? 92.226.217.125 (talk) 08:07, 9 December 2017 (UTC) Not comparable cases, and no it wouldn't go in parentheses if natural disambiguation is available; see WP:ATDAB policy.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  08:21, 9 December 2017 (UTC) Here's the anon explicitly calling me a liar, twice: [37][38]. See also WP:ASPERSIONS and WP:SANCTIONGAMING. One can't go around accusing people of dishonesty and then claim one isn't doing that simply because one used, in two instances, a different word than "liar". Changing one's IP address isn't going to fool anyone, either.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  08:21, 9 December 2017 (UTC) User:SMcCandlish is claiming the untrue once again. "Here's the anon explicitly calling me a liar, twice" 1) [39] does not contain the word "liar". It makes a claim about what would be a lie (It's a lie if the opposer claims that "X Line" and use of "-" has been started by IP requests "only just over a day ago"."), and then, after the other party does not pull back from the false statement about "Line", it is sure that he sticks to the lie. But there is no claim that the whole person is a liar. 2) [40] the diff does not contain the word "lie" nor "liar". It says "is saying the untrue", but that does not constitute lying. ... Now, "explicitly calling me a liar, twice" is just a false claim. It's a libel. 78.55.248.119 (talk) 05:52, 10 December 2017 (UTC) See WP:SANCTIONGAMING and WP:No legal threats. Probably also First law of holes.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  06:20, 10 December 2017 (UTC)

Collapsing another dispute which has been mooted.

RfC misrepresentation Moot  – Later parties have removed the statements in question and restored the RfC to wording similar to that with which it started.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  04:50, 10 December 2017 (UTC) At least three things the anon changed in the RfC's wording are mispresentation of the intent and meaning of this RfC, of WP policies and guidelines, and of actual practice. It's pure FUD. Third Interchange Contour would not be "Third interchange contour" in option A, because it's a proper name, not a description. This RfC is not about anything other than the word "line" in descriptive titles of WP articles on railway lines. Moscow Monorail – Ditto. These bogus examples have been inserted as straw man and argument to emotion tactics to scare editors away from option A, which would not actually result in the titles the anon claims. The entire option B "reasoning" block – inserted after removal of most of the reasoning for option A by the same editor – is not a neutral statement but just one person's pleading and "evidence" presentation, a restatement of their !vote. And none of it aligns with reality; this is the anon arguing how they wished things were. A style that a handful of people made up in a wikiproject about a year ago – either without bothering to consult the titles policy and naming and style guides, or directly conflicting with them on purpose – is not "long-standing", but a recently introduced conflict of a WP:PROJPAGE essay with much longer-established WP:P&G material (see WP:POLICYFORK). "I can find some other 'Line' cases" = WP:OTHERCRAPEXISTS; it's just stuff we've not cleaned up yet.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  09:49, 9 December 2017 (UTC) User:SMcCandlish claims the untrue: "A style that a handful of people made up in a wikiproject about a year ago" ... See 2005 version of Arbatsko-Pokrovskaya Line 213.39.186.49 (talk) 17:08, 9 December 2017 (UTC) Again, he probably mis-interpreted your phrase "year-old" as meaning about a year ago. Probably you meant "years-old". I agree the over-capitalization is very old there. Dicklyon (talk) 19:10, 9 December 2017 (UTC) Just for the record: If that's the case then it again is not me misinterpreting anything, it's the anon writing one thing then later claiming a different meaning. (Anon also made the same singular-year claim here.) This sort of equivocation has been happening with that editor throughout the discussion.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  04:53, 10 December 2017 (UTC) User:SMcCandlish - you are again claiming the untrue. [41] "Hyphen and uppercase "Line" to mimic the WP:OFFICIALNAME in Russian Cyrillic" - Russian Cyrillic has no uppercase "Line". And that was never claimed to be so. Re your "A style that a handful of people made up in a wikiproject about a year ago" - it's simply not true. IP made no such claim. IP did not claim "handful" nor "about a year ago". IP didn't define the number of years. https://en.wiktionary.org/wiki/-year-old 78.55.248.119 (talk) 05:33, 10 December 2017 (UTC) Attempting to disprove equivocation with more equivocation is not a good tactic.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  06:19, 10 December 2017 (UTC) User:Dicklyon you claim, but don't prove. There is no "over-capitalization". It is only "over-capitalization" in your mind and that of some others. It's common practice to capitalize, it is a question of style: Second Avenue Subway and all the lines in Category:New York City Subway lines. Both ways are possible. 77.179.37.199 (talk) 23:33, 9 December 2017 (UTC) It's overcapitalization according to WP:NCCAPS and MOS:CAPS. This has nothing to do with your mind versus his mind or any other such projective nonsense. Either RS consistently treat these things are proper names and write them out and capitalize them the same way from source to source, or they do not. In these kinds of cases they do not, since they're descriptive phrases not names, and are not used consistently in sources at all, style questions aside. These things have no particular common names in English.  — SMcCandlish ☏ ¢ >ʌⱷ҅ᴥⱷʌ<  04:49, 10 December 2017 (UTC) Yeah, you really shouldn't aspire to consistency with the New York subway over-capitalizers. Note that the New York Times and New Yorker magazine, to name a few, don't do that; they say Second Avenue subway, (100 years ago, the old one was called Second avenue subway, but times change); similarly for Lexington Avenue line, and New York subway, which NYC wikipedians insist on capping against the advice of their MOS; yes, WP:OTHERCRAPEXISTS. But per our MOS, if the New York Times and New Yorker and other respectably edited English-language publications can get away with lowercase, then we there's no reason we should treat these as proper names. But I can't fix everything as once; when I get pushback, I slow down and work through it. Dicklyon (talk) 05:40, 10 December 2017 (UTC)

Corresponding Requested Move discussion opened

I open a multi-RM on all the lines in the 5 metros I could find: Talk:Kalininsko-Solntsevskaya_Line#Requested move 11 December 2017. This seems like an opportunity for a more focused discussion now that we've all aired our feelings and it's clearly "A" vs the status quo. Dicklyon (talk) 03:28, 11 December 2017 (UTC)

RFC on forming possessive form of singular names, MOS advice simplification

Should we simplify the advice of the WP:Manual of Style to choose between a pronunciation-based option and a uniform "add apostophe and s" option, in favor of just the uniform approach, since the pronunciation-based approach is complicated, seems to be misunderstood, and is hard to apply? Dicklyon (talk) 02:36, 12 December 2017 (UTC)

Specifically, the proposal, based on the discussion at WT:MOS#Apostronot, is that the nearly three hundred words of the existing MOS:POSS under the heading Singular nouns be replaced with this text that paraphrases the advice in University of Oxford Style Guide:

For the possessive of singular nouns, including proper names and words ending with an s (sounded as /s/ or /z/, or silent), add 's: my niece's wedding, James's house, Cortez's men, Glass's books, Illinois's largest employer, Descartes's philosophy. If a name already ends in s or z and would be difficult to pronounce if ’s were added to the end, consider rearranging the phrase to avoid the difficulty: Jesus’s teachings or the teachings of Jesus.

Note that most modern English guides recommend an approach close to this, though often with a short list or small category of exceptions. Please comment, support, or oppose. Feel free to propose alternative simplifications if neither this proposal nor the status quo seems ideal. If you prefer exceptions, what is the list or how will it be determined? Dicklyon (talk) 02:36, 12 December 2017 (UTC)

Comments on singular possessive form

• Support as much simpler and easier to understand and explain; would avoid the pronunciation arguments that the current MOS:POSS generates, and reflect common usage MapReader (talk) 06:10, 12 December 2017 (UTC)
• I've always found this rule from the University of Oxford's style guide to be very clear and useful. I'd support this change. Killiondude (talk) 07:09, 12 December 2017 (UTC)
• Support. This is the sensible "please stop fighting about this" approach, and is very clear and simple both for editors and more importantly for readers. The "sometimes just use ' alone" styles are ambiguous, inconsistent, confusing, and lead to frequent dispute, while the "consistently use 's" style is understood by everyone, and 100% clear on whether something is a singular or plural possessive. Verbal pronunciation-based ideas about how to punctuate are of no relevance on Wikipedia, which is not a broadcast medium. Such "rules" (which sharply conflict in both specifics and rationales from publisher to publisher) are found in regional style guides, but do not make any sense in an international encyclopedia, because pronunciation of things like Jones's and Texas's vary on more than one axis (both syllabification and, often, /s/ versus /z/ – varying not only by dialect but by individual word/name). Modern style guides are increasingly shifting to a simple "just use 's" rule, including The Chicago Manual of Style (with some nitpicks [some of which are not even self-consistent – even CMoS has some editing gaffes] in the 17th ed., University of Oxford Style Guide, and various others. Those that want some kind of "odd exceptions for ' only" variance are mostly either old, or are written for a fixed audience with known dominant pronunciation patterns. We have no need of the rather tortured "make a special exception for ..." stuff found very randomly and inconsistently in various off-WP style guides (when not based on regional pronunciation, they're usually based on the traditionalism of "Jesus'" and "Moses'" in the King James Version of the Bible, which is written in late Middle English, while Wikipedia obviously is not).  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  11:25, 12 December 2017 (UTC)
• Support but allow occasional exceptions if contemporary English reliable sources are (mostly) consistent in using just '. Above all don't edit war about it. Thryduulf (talk) 13:43, 12 December 2017 (UTC)

  I was assuming it went without saying that the normal approach of preserving format for citations and quotations would continue to apply. Other than that, I doubt that there are any words where an alternative format is consistently used; even Jesus's is very common nowadays MapReader (talk)

• Support This is the only sensible version. No need for a list of exceptions, just rephrase the sentence if you don't like how it sounds. --Khajidha (talk) 13:46, 12 December 2017 (UTC)
• Support. This is great.The current MOS, with two options, one unconditional and the other depending on pronunciation, with the one to be used depending on who's edited the article first, couldn't be better designed to generate editor disputes. The new proposal is so much better. — Preceding unsigned comment added by 2a00:23c5:5a4c:c400:d093:4f95:a3d0:abdb (talk • contribs)
• Support per University of Oxford style guide linked above. --SarekOfVulcan (talk) 15:42, 12 December 2017 (UTC)

  Just to be clear, this is the "University of Oxford Style Guide", not one of the "professional" guides published by Oxford University Press, which it states it is not trying to compete with, but does differ from a bit. Dicklyon (talk) 16:35, 12 December 2017 (UTC)

  Thanks, edited to clarify. --SarekOfVulcan (talk) 18:57, 14 December 2017 (UTC)

• Comment - in the example, I don't understand why it's recommended to add 's for "Glass's books" while it's recommended to rewrite "Jesus's teachings". What's the difference? Both end with a hard s sound, at least how I pronounce them. And maybe it's different in different places, but wouldn't "Jesus's teachings" and "Jesus' teachings" be pronounced the same? Ivanvector (^Talk/_Edits) 18:55, 14 December 2017 (UTC)

• Your last sentence is a good point. I suggest that multiple editors corner their respective priests/pastors at church on Sunday and ask them how they pronounce the possessive of "Jesus" in their sermons. And report back here afterwards. If "Jesus's" is good enough for Father Bob and his congregation, it should be good enough for Wikipedia. ―Mandruss ☎ 19:49, 14 December 2017 (UTC)

• Jesus's is certainly good enough for a range of reputable sources including the Daily Telegraph, the Atlantic website, Newsweek magazine, and the Guardian, as well as a whole batch of Christian sites in both the U.S. and Europe. MapReader (talk) 20:59, 14 December 2017 (UTC)

• That being the case, even if the last sentence is retained, which I will probably oppose as a cost:benefit fail, "Jesus's" is a crappy choice for an example. ―Mandruss ☎ 21:06, 14 December 2017 (UTC)

• Nevertheless the proposal delivers 90% of what you are arguing for, and the option to re-word a phrase is always there, whether flagged by the MOS or not. WP MOS proposals are littered with examples of the good failing for want of the best, and hopefully editors will recognise that a leap forward is progress even if not perfection in a single bound? MapReader (talk) 22:55, 15 December 2017 (UTC)

• I stated support for "as written" as second choice. That means that, absent a consensus for my first choice, my !vote is no different from yours. Thus, this is not a case of "better is the enemy of good". But there is no chance of that consensus if nobody is willing to be the first to !vote for it. ―Mandruss ☎ 05:12, 17 December 2017 (UTC)

• Many guides discuss exception for names already ending with two sibilants, like Jesus and Moses; quite different from Glass. And if you would pronounce Jesus' the same as Jesus's, you are evidence for the fact that this distinction is super confusing. Dicklyon (talk) 20:24, 14 December 2017 (UTC)
• No, that's the key point, the ' is silent (in those style rules, like ours, that are based upon pronunciation). Listen to the Velvet Underground song Heroin, the line containing Jesus' son. Pronounced the same as Jesus son. Indeed pretty much the only argument for the ', given the potential ambiguity it creates, is the supposed difficulty of pronouncing 's (in certain limited circumstances). Yet, as SMcC says above, WP is not a broadcast medium. MapReader (talk) 20:46, 14 December 2017 (UTC)

Is that a point of difficulty with the instructions? I've always read constructions like Jesus's and Jesus' as both sounding like "Jesuses", although it occurs to me that I would pronounce something like "Jesus' son" as you said in your example. I've also wondered why it became standard to use s' at all, figuring it's just one of those weird English things. Like how in Shakespearean-era English in a phrase like "all are punished!" the word "punished" is pronounced with three syllables (pun-ish-ed), where for it to be pronounced like we do these days it would be written "punish'd". That is, just something weird that evolved into (or out of) the language. This is probably way off-topic. The point is, if people don't agree on how to pronounce these things, then a standard based on pronunciation will fail. I don't know if this is a widespread case: it's what I'm used to, but it could still be a rare thing. Ivanvector (^Talk/_Edits) 21:37, 15 December 2017 (UTC)

The only argument for not adding the 's, which is the standard approach in written English, is the link (in some style guides) with pronunciation. As soon as you divorce pronunciation from the written form - already a common approach, English being full of irregularities - you may as well always just add 's for the written possessive. As you say, we would be better off without a style guide within WP that tries to link punctuation with pronunciation, given how much the latter varies around the world. MapReader (talk) 03:43, 19 December 2017 (UTC)

• Comment - If a name already ends in s or z and would be difficult to pronounce if ’s were added to the end, consider rearranging the phrase to avoid the difficulty: Jesus’s teachings or the teachings of Jesus. - Why does it matter whether it's difficult to pronounce (for some people)? How often do people read Wikipedia articles aloud? Are readers going to spend a significant amount of time struggling to "pronounce" "Jesus's" in their minds? ―Mandruss ☎ 19:35, 14 December 2017 (UTC)

  You're right, and the group of us that discussed it on the MOS talk page did consider going a step further and recommending simply always adding 's. The final proposal we ran with retains a small part of the existing link to pronunciation, particularly for sensitive words like Jesus - but through the option of re-ordering the phrase (which is always open to editors anyhow). MapReader (talk) 20:51, 14 December 2017 (UTC)

  To answer this would take quite awhile and involve the mechanics of how people actually perform the process of 'reading'. Short version: Internal voice can trip up reading as much as external voice. See Subvocalization. If its hard to say, it can be hard to read. Only in death does duty end (talk) 09:16, 15 December 2017 (UTC)

  That is not an argument for omitting the 's. I get "tripped up" more by Jesus' than by Jesus's—my language processing center needs the 's sound to make it a possessive.
  Regardless, even if there is some subvocalization benefit that is so minute that we need academics to tell us it exists (and that has yet to be shown, anyway), I weigh all benefit against its cost and I believe that that second sentence is a cost/benefit fail for the project. Editor time is a finite resource; there will never be enough of it to do everything, so priorities must be set and some less important things must be allowed to slide in favor of more important things. The editor time spent arguing, edit-warring, and RfCing about this (and more editor time dealing with the disputes at DRN, ANI, AN3, etc) would be editor time not spent doing things that benefit readers more. ―Mandruss ☎ 20:24, 15 December 2017 (UTC)

• Support first sentence only per my comments above. I fully support the use of guidelines to eliminate unjustifiable battlegrounds, and the second sentence does the opposite. It will not be a good use of community time to engage in debates about the degree of difficulty in pronouncing "Hughes's"—replete with academic/pedantic references to sibilants and such—especially considering that readers are not required to pronounce it. Support as written as second choice, as that would still be a marked improvement. ―Mandruss ☎ 21:46, 14 December 2017 (UTC)
• Oppose anything more: I am extremely unfamiliar with "'s" being added to possessives ending with an "s"; it looks really weird. In that regard, I am completely against anything that fully discourages the use of "s'". If—however—it is evidently becoming common (and I have missed it), by all means give editors a choice. –Sb2001 14:19, 15 December 2017 (UTC)

  Adding 's has always been the most common thing, for most names ending in s. I've never seen a style guide that said generally not to, have you? A lot of people do confuse the rules from plurals that end in s, however, which may be the case with your own familiarity. For examples, see the history of the Steve Jobs article; every now and then someone comes along and claims they were taught that Jobs's would be wrong; but by all style guides I've ever seen, it's right and preferred. Still, some of the cited sources do use Jobs', so we quote them that way. Neither of the alternatives recommended by our MOS or most guides would sanction that. Dicklyon (talk) 02:02, 17 December 2017 (UTC)

  I cannot say I have ever consulted a style guide on this—it has never been disputed. I have always written "s'", and haven't been questioned about it. Most of my grammar, etc, comes from education. The teacher who introduced me to possessives must have adopted this style. –Sb2001 01:00, 20 December 2017 (UTC)

• Oppose standardising this completely. As there are still style guides that recommend checking the pronunciation [42], we don't need to force editors to write "Mephistopheles’s" against their will. Our MoS should not recommend something and then say "if it looks weird to you, rephrase it". Instead, allow non-weird possessives. —Kusma (t·c) 21:55, 15 December 2017 (UTC)

  You are of course free to write it any way you please. The MOS does not force editors to do anything. But if someone moves it toward MOS compliance, let it go, OK? That's all we ask. Dicklyon (talk) 03:58, 16 December 2017 (UTC)

  Unfortunately, in reality, no one is free to write anything any way they please because MOS does force editors to do it the MOS way -- and it's why one editor can easily lord over another editor with [[MOS:SAYS]]. Pyxis Solitary talk 12:14, 23 December 2017 (UTC)

  I can't even imagine how I could force you or another editor to write the way the MOS recommends. Dicklyon (talk) 00:49, 24 December 2017 (UTC)

  Every time an editor swoops into an article to delete or change content with [[MOS:SAYS]] as the reason, he's using MOS to force editors to write content in a manner that complies with MOS. Sometimes it's legitimate, but sometimes MOS is used by assholes who spend their life nitpicking articles as self-appointed MOS enforcers. Pyxis Solitary talk 03:59, 26 December 2017 (UTC)

  So how do you decide which it is? Legitimate attempt to bring an article more into accord with en.w's MOS, versus just nitpicking self-appointed enforcers? And how does that force anyone else to write one way or another? Dicklyon (talk) 04:11, 26 December 2017 (UTC)

  Unless a change per MOS can be shown to harm the article, it should be left alone. If there is disagreement about whether it harms the article, that's why we have article talk pages and consensus. All of this can and should be resolved with mutual respect like any other issue. Hyperbolic and inflammatory references to swooping into articles (how does one "swoop into" an article, exactly?) and "assholes who spend their life nitpicking articles as self-appointed MOS enforcers" have no place in discussion or in one's thinking, smack of WP:PA and WP:OWN, and are themselves harmful to the project. Period. ―Mandruss ☎ 04:57, 26 December 2017 (UTC)

Uptick in MOS-related RfCs

I notice that we have had a recent surge in discussions that pit our MOS against various project level guidelines. Is there a reason for this? (Not saying who’s right or wrong in these discussions... just wondering why we are suddenly getting so many). Blueboar (talk) 05:42, 13 December 2017 (UTC)

I suspect that it's because those who like the MOS are running up against significant opposition from those who like the individual project guidelines when the former group of editors try and change articles written/named according to the project guidelines. This is certainly the case with rail transport and so I presume it's the same in other areas too. I haven't been following all the discussions by any means, but from those I have seen I wouldn't like to say the manual of style is always or even almost always the better. Thryduulf (talk) 17:53, 13 December 2017 (UTC)

But why does this seem to be happening more often right now?--Khajidha (talk) 18:06, 13 December 2017 (UTC)

Do we have examples of what you're talking about? I've seen only very few such, like the NYC subway folks liking to cap all their stuff, but that discussion goes back a few years, nothing new. Dicklyon (talk) 18:18, 13 December 2017 (UTC)

If you're thinking of the recent China and Russia caps discussions, there was really no conflict with projects there. I was unable get much input from projects on those; they don't seen to care or have any conflicting style. There's one anon on the Russia stuff, and a one or two counter opinions on the China/Hong Kong situation, but nothing resembling project-level guidelines. In Taiwan, Philippines, and some other places the projects have been actively moving toward MOS compliance. Where is this "pit against" thing you think you've noticed? Dicklyon (talk) 18:34, 13 December 2017 (UTC)

• If it is, it doesn't represent anything new. The standard tension at Wikipedia (which could perhaps be generalized to a sort of standard tension in across all human endeavors in the history of mankind) is the tension between uniformity and flexibility, or between "lumpers and splitters", or similar. Without taking sides (because taking sides isn't useful, or even necessary here, because neither is right, and both are wrong; and also simultaneously both are right, and neither is wrong), the issue is thus: On the one side, there is a benefit to having a clear unified rule set that everyone follows (if we all agree to do the same thing, its one less thing to fight over, so we can move along to something actually important). On the other side there is a benefit to allowing a diversity of rules to allow for the greatest diversity of ideas (rules that exclude valid ideas or their expression limits the usefulness of the project). This tension spills out in various places, under various manifestations randomly and without direct cause; it just happens to flare up somewhere or another. Whether its the "All articles should have infoboxes" vs. "It's OK if some don't" debates, the "The MOS should be applied to every article without question" vs. "Wikiprojects should manage their own affairs" debate, to any of a gajillion or so manifestations. If you really want to be helpful, just recognize the problem isn't going away, treat all of these discussions with nuance, and there is nothing to do about it because there is no reason to do anything. It always happens, will always happen, and doesn't need approval to happen. It just does. Accept that it will, and manage the fallout with nuance and grace when it does. --Jayron32 20:14, 13 December 2017 (UTC)

As you say, it's a natural consequence of having decisions taken at various levels, the latter being a better way of managing almost any complex enterprise than trying to centralise everything. In theory at least it might help to have some common definition of the things expected to be consistent across WP - grammar, punctuation, linking, content of the lead section, etc. - and those left to projects to sort out, which for me would include stuff like the use of infoboxes mentioned above. Whether such exists in WP I have no idea? If it doesn't it could be a difficult and tortuous thing to create (or, rather, on which to gain any sort of consensus!) MapReader (talk) 04:10, 14 December 2017 (UTC)

@Blueboar:, since I do a lot of MOS gnoming, I'm really wondering if your comment was related to some of my efforts. I haven't seen such a thing, so wondering what you're seeing. When an active project is out of sync with the MOS like at Wikipedia:WikiProject_New_York_City_Public_Transportation#Naming_conventions, there's not much that can be done. I tried an RM; it lost; that's life. Are there other projects relevant to what you're thinking, where things have happened recently? The big noise above about Russia should never have happened; it's about a globally banned block evader and a screwup in executing his technical requests; not a project; open RM to fix it is unopposed, last I looked. What else is behind your premise that we are "suddenly getting so many"? Dicklyon (talk) 21:05, 14 December 2017 (UTC)

My comment was inspired by the fact that at least 6 of the current discussions on this page relate to questions re MOS vs Progect guidance. I am used to seeing one or two such discussions a month, and it seemed unusual to have so many. Blueboar (talk) 22:05, 14 December 2017 (UTC)

Maybe I'm blind, but I don't see a conflict with project guidelines in any of those, with the exception of the NYC lines already noted. So if you see "discussions that pit our MOS against various project level guidelines", maybe it's just you seeing things oddly? Dicklyon (talk) 22:16, 14 December 2017 (UTC)

Oh, a little bit of the China transport discussion did involve an MOS conflict, too, I see now. There was essentially no project pushback when fixing hundreds of those titles though. Like in other countries where we worked on that, users with a China interest saw the advantage of consistency with WP style, I think. There's more to be done there, but I'm not sensing any resistance. Dicklyon (talk) 22:23, 14 December 2017 (UTC)

It's just a factor of: A) some overdue MoS cleanup and consolidation happening at the same time as B) a bunch of large-category WP:CONSISTENCY cleanup that happens (as titles discussions often to) to involved MoS questions; plus C) conscientiousness that VPPOL be notified of substantive, non-trivial MoS changes and proposals; and D) using VPPOL for its actual purpose as a non-topical, "editors of all interests and backgrounds" centralized discussion venue for WP:P&G matters, especially when individuals or topical blocs of editors make consensus determination difficult.

As to specifics: MOS:MATH is a site-wide guideline; the idea that MOS:MATH agreeing with WP:MOS (to which it is subordinate as a matter of policy) and with MOS:ACCESS, on an accessible markup question is somehow "pit[ting] our MOS against various project level guidelines"; WP:WikiProject Mathematics was canvassed to the RfC, but does not own or control that guideline, the WP community does, and accessibility and HTML and template markup questions that aren't maths-specific are outside of both MOS:MATH's and the wikiproject's scope. The Russian metro line RfC would not have been necessary if not for a disruptive and tendentious anon, who has now been positively identified as WP:SOCKing, banned editor Tobias Conradi. The earlier one on Chinese railways is not an wikiproject versus MoS dispute, but a wikiproject versus wikiproject one; the railway and stations wikiprojects have had multiple RfCs concluding (in agreement with MOS:CAPS) to stop over-capitalizing words like "line" and "station" when outside of proper nouns; a few editors from the China wikiprojects wanted to WP:POLICYFORK from that, as if there was something special and different about how to refer, in English, to train stuff in China. And so on. It's just coincidental timing.
 — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  00:30, 15 December 2017 (UTC)

You've been around long enough to know what is and is not canvassing. But WP:APPNOTE is very clear that notifying Wikiprojects with an interest in a decision is not canvassing, and one of the best practices described at WP:RFC is to notify relevant Wikiprojects. I'll also remind everyone that Wikiprojects consist of editors who are just as much a part of "the community" as everyone else. Just to be clear, I don't claim that Wikiprojects always have the answers, or that Wikiproject Mathematics is always right, but there seems to be an implied attitude here that if you're not closely monitoring the pump and editing policies, then you aren't a member of "the community". Well I happen to think that all editors are part of the community, whether they are actively involved in policy work or not. Since not everyone monitors the pump as closely as most of the regulars here, it is very important for them to be notified of topically relevant proceedings here. Ideally all interested parties should be notified of a request for comment. While I've quite recently been accused of acting "tribally", I see more evidence that only those editors who regularly lurk on policy pages have opinions that are worthy of consideration, whilst those of us that edit more in focused content areas and articles are viewed as second-class citizens. Thus this is cast as "the community" versus "the Wikiprojects", which is a specious distinction with the sole intent of creating an artificial division of opinion. Sławomir Biały (talk) 13:09, 15 December 2017 (UTC)

Thanks for pointing out that this is largely due to using "VPPOL for its actual purpose". And for reminding me that it's not all about me. I think Blueboar just can't stand to see MOS working so well and having so much consensus in input; I'll think of him as our Ajit Pai, wanting to let the various independent factions do their own thing even if it's bad for the overall project. Dicklyon (talk) 03:08, 15 December 2017 (UTC)

Please note that I was simply asking “why?” we were getting more discussions than usual ... not passing judgment on the discussions themselves. Blueboar (talk) 21:13, 15 December 2017 (UTC)

But you presented it as "discussions that pit our MOS against various project level guidelines". No such thing is happening. Dicklyon (talk) 04:01, 16 December 2017 (UTC)

See also section(s)

I noticed that those sections have been abusing by editors to "promote" other pages they created or they like. Plus, the policy regarding "See also" sections says that "Whether a link belongs in the "See also" section is ultimately a matter of editorial judgment and common sense." Whether a link belongs in the section mostly depends on editors' POV and is often abused for promotional purposes (the same issue was the problem for ethnic gallery sections in the past and the problem has been solved, see WP:NOETHNICGALLERIES policy). We have already "Main articles", "Further information" links on articles and in addition to this, the useful articles are linked in the bodies of the articles already. Thus, due to the reasons i mentioned above, i think those sections are problematic, have been abusing and surpluss. 66.226.107.42 (talk) 06:38, 14 December 2017 (UTC)

PS:I am unable to edit with my physical ip right now and sorry in advance for this. Thanks. 66.226.107.42 (talk) 06:43, 14 December 2017 (UTC)

You can edit the "see also" section if you don't think the suggestion is relevant, and you don't have to follow a link that simply doesn't interest you. Read WP:ABOUT: "Wikipedia's articles provide links designed to guide the user to related pages with additional information." "See also" sections are part of that feature. Jack N. Stock (talk) 06:46, 14 December 2017 (UTC)

As i mentioned above, those sections mostly depend on the editor's judgment (that is what the policy says) and thus removing or edit-warring over this is meaningless. As for WP:ABOUT, as i mentioned above, we have already links in the bodies of the articles and "Further information", "Main article" links. In other words, see also sections are not "crucial" and unfortunately, have been abusing for POV & promotional purposes. 66.226.107.42 (talk) 06:54, 14 December 2017 (UTC)

It is hard to determine if there is abuse (or not) without some specific examples to discuss. Blueboar (talk) 11:55, 14 December 2017 (UTC)

Exactly; which is why I was pressing you for examples of your complaint (or observation) in the section above. Dicklyon (talk) 22:17, 14 December 2017 (UTC)

We actually do have guidelines on see-also sections:

• Wikipedia:Manual of Style/Layout § "See also" section
• Wikipedia:Manual of Style/Embedded lists § Related topics (navigational lists)

 — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  00:35, 15 December 2017 (UTC)

Removal of COPYVIO content as an exemption to WP:3RRNO

Currently the list of WP:EW#Exemptions to the three-revert rule includes Removal of clear copyright violations or content that unquestionably violates the non-free content policy. This allows one editor to remove such content and by doing so prevent another editor who added it originally from addressing the issue (e.g. properly paraphrasing it) and restoring it. This problem could occur anywhere, but is particularly apparent in articles falling under 1RR. I propose adding an exemption regarding restoring content that was removed on such grounds or on similar grounds. Otherwise, unscrupulous editors are able to use this technicality for suppressing POV they disagree with and pushing their own, even though following the letter rather than the spirit of the rule designed to prevent edit warring goes against common sense. --Wiking (talk) 05:30, 15 December 2017 (UTC)

I don't quite understand. Editor A adds a copyvio, Editor B reverts. This revert is free and does not count against 3RR. Editor A adds a non-copyvio cited rewrite of said content. This is not a revert and does not count against 3RR. If Editor B reverts, it is not covered by the exception. Or am I missing something? —Kusma (t·c) 07:31, 15 December 2017 (UTC)

No that's correct. If editor A had reinserted the same material without re-writing, any reverts of that would not count towards 3rr. Once it has been re-written to not be a copyvio, any reverts of that do count towards 3rr. The problem is where the rewrite is close paraphrasing it may not be a 'clear' copyright violation, which is where it should be taken to the talkpage before being reinserted. Only in death does duty end (talk) 09:00, 15 December 2017 (UTC)

Only in death and Kusma are entirely correct. If the copyright violations are cured, reversion of the rewritten text would not be exempt from 3RR. The Big Bad Wolfowitz (aka Hullaballoo). Treated like dirt by many administrators since 2006. (talk) 14:16, 15 December 2017 (UTC)

I think that much is clear. But is the re-insertion of the cured, rewritten text exempt from 1RR? --Wiking (talk) 15:53, 15 December 2017 (UTC)

Look, these hypotheticals aren't helping much. You've obviously got a specific dispute in mind; show us some diffs and we'll all tell you what's to be done about it. --Jayron32 17:02, 15 December 2017 (UTC)

I see what you mean with regards to 1rr. Editor A inserts material. Editor B removes it as an obvious copyvio (not subject to 1rr or 3RR etc). Editor A then adds material that is not a copyvio - my opinion is this would not be a revert of editor B - this is normal editorial process and how it is supposed to work. While there is an argument that because editor A is reinserting the same material, albeit re-worded, it constitutes a revert, in practice if anyone made a claim this is edit-warring, they would be swiftly told no. And as it would be the first 'revert' by editor A, it would be allowed under 1rr anyway - as the original addition of material does not count towards the 1rr/3rr count. Editor B would then be technically allowed to remove the material again under 1rr, but unless they had a good reason would justifiably be accused of goalpost moving. Only in death does duty end (talk) 17:15, 15 December 2017 (UTC)

This is a very reasonable understanding, but unfortunately it is not shared by all editors. --Wiking (talk) 17:26, 15 December 2017 (UTC)

Which other editors are you having problems with. What is the locus of the dispute? Help us help you: instead of trying to change policy, let us know what the actual problem is and see if we can't help you with that! --Jayron32 18:26, 15 December 2017 (UTC)

See User talk:Wiking#1RR and 24 hour rule; however, the actual revision history of United States recognition of Jerusalem as Israeli capital, unfortunately, is no longer accessible after Diannaa removed much of it. --Wiking (talk) 18:33, 15 December 2017 (UTC)

Adding an exemption similar to this would resolve this ambiguity:

• Reinserting material that was previously reverted due to copyright violations, summarized in a way that avoids close paraphrasing.

--Wiking (talk) 18:11, 15 December 2017 (UTC)

The copyright issue had not been addressed when I arrived at the page. Source article: https://www.haaretz.com/israel-news/1.769498

Bill Clinton declared in February 1992, at the height of the Democratic primaries, that he supported recognizing Jerusalem as Israel’s capital, a step that would alter U.S. policy. Later, during the general election campaign, Clinton attacked President George H.W. Bush for having “repeatedly challenged Israel’s sovereignty over a united Jerusalem.” He promised that he and running mate Al Gore would “support Jerusalem as the capital of the State of Israel.” Indyk, who became a Mideast adviser to the new president, recalls that “we looked at this and said – well, there had just been direct negotiations between the two parties in Madrid; do we really want to do this thing? That was our line of thinking in the first few weeks, and then the Oslo process got underway and made it even more complicated.” By 1995, the administration found itself opposing the Jerusalem Embassy Act, which was passed by wide margins in both houses of Congress, but was left unsigned by Clinton. The bill stated that the American embassy should move to Jerusalem within five years.

Content I removed:

Bill Clinton declared in February 1992, during the Democratic primaries, that he supported recognizing Jerusalem as Israel's capital . Later, during the general election campaign, he attacked President George H. W. Bush for having "repeatedly challenged Israel's sovereignty over a united Jerusalem." He promised that he and running mate Al Gore would "support Jerusalem as the capital of the State of Israel." However, the Clinton administration backed away from this promise as peace talks in Madrid and then the Oslo process got underway. The administration found itself opposing the Jerusalem Embassy Act, which was passed by wide margins in both houses of Congress, but was left unsigned by Clinton. The bill stated that the American embassy should move to Jerusalem within five years.

Overlapping portions are shown in bold. — Diannaa 🍁 (talk) 20:43, 15 December 2017 (UTC)

Yeah... that text is still a bit too close to the original for comfort. A much more substantial rewrite is needed. (Has this been done?) Blueboar (talk) 20:57, 15 December 2017 (UTC)

See, there we go. If Wiking had just told us about the exact problem we could have answered his question directly. The second attempt is still a copyvio, so it should be removed too. If he wants to add text to a Wikipedia article, he needs to learn how to create his own text from scratch, and not just copy and paste it from elsewhere. Problem looks solved to me. --Jayron32 05:45, 16 December 2017 (UTC)

Jayron hits the nail on the head. The Big Bad Wolfowitz (aka Hullaballoo). Treated like dirt by many administrators since 2006. (talk) 17:45, 16 December 2017 (UTC)

Agreed too. Since it was a copyvio both times, no issue. However, I would not interpret a good-faith attempt to solve a copyright problem, when material had been removed for that reason alone, as a "revert". Seraphimblade ^{Talk to me} 18:45, 16 December 2017 (UTC)

This is not the section that had been reverted due to COPYVIO and subsequently re-written. --Wiking (talk) 19:55, 17 December 2017 (UTC)

Ok... so please point us to the section that was. Blueboar (talk) 20:02, 17 December 2017 (UTC)

Like I said, the revision history is no longer accessible. At 18:56, 14 December 2017‎ Seraphim System removed my edit with the comment "3RRNO COPYVIO direct copy and paste from jpost article of significant language; editor warned on user talk page →‎American reactions" and at 19:43 I restored it, using the wording from LEDE of Conference of Presidents of Major American Jewish Organizations instead of quoting the source directly. Both these edits are now lost since immediately after that Diannaa hid some unrelated changes as she described above; however, on my talk page I received a warning, and after I asked for clarification, got another one, and another, with the following point: "AFAIK there is no revert exception for fixing reverts made under the exceptions. (...) You should at this point understand that this article is under a 1RR exception, that means only one revert in a 24 hour period. (...) WP:3RRNO lists the only exceptions, if your reason is not covered by one of them, it is a revert." That's what's brought me here. --Wiking (talk) 20:20, 17 December 2017 (UTC)

Ok... then do what Diannaa did... type out the original text in a quote box... and then the text you wanted to add in another... so we can compare the two and see if they are different enough. Blueboar (talk) 20:34, 17 December 2017 (UTC)

It was not close paraphrasing, I removed two one-line WP:COPYPASTEs. All an editor needs to do to avoid this is to not copy and paste material directly from sources. Any modifications to the 24 hour rule would have to be proposed at ARCA. 1RR is not implicated because in ARBPIA an editor can not restore this within 24 hours anyway. I don't think ARCA is going to carve out exceptions for editors who could have prevented the problem themselves by simply not copying and pasting. Seraphim System ^(talk) 21:50, 17 December 2017 (UTC)

Unlike Diannaa, I don't have access to the original, but like Seraphim System said, it was a copy-paste (of a sentence fragment), which was replaced with another sentence fragment that's currently in the article: "the Conference of Presidents of Major American Jewish Organizations, which comprises 51 national Jewish organizations and was founded to develop a consensus voice among Jewish organizations in dealings with the executive branch". That was literally taken from the LEDE of the linked article and could not raise any COPYVIO objections. And it didn't - I'm afraid you are getting side tracked. As I already explained, Seraphim System claimed that restoring my edit after addressing the COPYVIO issue constituted a 1RR violation, since it's not covered by any exemptions. Now he is changing that claim (even though I quoted him above). --Wiking (talk) 03:10, 18 December 2017 (UTC)

The material I removed was copied from Haaretz, and was added by Wiking to the article United States recognition of Jerusalem as Israeli capital at 8:23, December 11, 2017 (Diff of United States recognition of Jerusalem as Israeli capital). The same content was added by Wiking to the article Positions on Jerusalem at 19:48, December 11, 2017‎ (Diff of Positions on Jerusalem). At 20:33, December 11, 2017‎ a user flagged the article United States recognition of Jerusalem as Israeli capital at having potential copyvio (Diff of United States recognition of Jerusalem as Israeli capital). On 15 December I was alerted by Seraphim System that there was copyvio present. User talk:Diannaa#REVDEL? I checked the article using Earwig's tool and found the Haaretz copyvio. Seraphim system also removed this material which is still visible in the page history and which is copyvio from The New York Times. And with this edit he removed copyvio from The JTA. So there's plenty of legitimate copyvio removal. What Seraphim System removed with this edit was the wording "which represents more than 50 Jewish organizations across the range of ideologies and seeks consensus on US-Israel affairs" which his edit summary says came from the Jerusalem Post (he does not give a specific url as the source and I can't find it online). If your replacement prose "which is comprised of 51 national Jewish organizations and was founded to develop a consensus voice among Jewish organizations in dealings with the executive branch" is still present in the article, as none of Seraphim System's (or anyone else's) subsequent edits removed it. — Diannaa 🍁 (talk) 05:00, 18 December 2017 (UTC)

Thanks for providing the prior version, and yes, my edit is still present, and per Seraphim System, it was a revert of his revert, which violated 1RR, and that's exactly what we are discussing here. --Wiking (talk) 05:11, 18 December 2017 (UTC)

To put it another way: He removed suspected copyvio, you re-worded and re-added the content. Seraphim System then warned you that adding the amended content was a violation of the editing restrictions on the page. So your question is, was this a valid warning? Adding: If it's a valid warning under the current wording of the policy, should the policy be amended to make it such that adding replacement prose for a removed copyvio is an exempted action? — Diannaa 🍁 (talk) 05:27, 18 December 2017 (UTC)

Exactly. --Wiking (talk) 05:29, 18 December 2017 (UTC)

If you look through the edit history there had been seven reverts in 3 days, this is after I politely notified you of the editing restrictions. Maybe I did want to remove it - even though I claimed 3RRNO, it was my only revert that day. I have to claim 3RRNO, in the event that there are further violations, to avoid sanctions myself. I was in the process of filing a complaint for both 1RR and the 24 hour rule - The only reason I didn't go to ARBCOM is because you had not received a DS warning - incidentally, this is not the first time you have evaded sanction at ARBCOM because an editor forgot to template you. Wikipedia:Arbitration/Requests/Enforcement/Archive188#Wiking - you are not a new editor, you are already familiar with these rules. Seraphim System ^(talk) 05:41, 18 December 2017 (UTC)

What I am wondering is are you asking this question here because you think you will be copying and pasting more content in the future? I will point out that Diannaa has already confirmed that copying and pasting is a COPYVIO, and a formal warning about COPYVIO was given to you by an admin. Seraphim System ^(talk) 06:05, 18 December 2017 (UTC)

I've asked you multiple times to stop reading my mind and telling me what I know, what I am familiar with, etc. Once again, let's stay on topic here and not discuss what I may or may not know. I am asking this question here because either the policy or your interpretation of the policy made no sense to me, and I felt that you were abusing it. It would be preferable if it was clarified so that you had no opportunity to abuse it against less experienced editors in the future, whoever they may be. If an inadvertent COPYVIO occurs and is reverted, it can and should be corrected as soon as possible rather than after some delay imposed by you under the threat of sanctions for 1RR violation. --Wiking (talk) 16:15, 18 December 2017 (UTC)

As touching as your concern for inexperienced editors is, you are not a new editor and you are expected to be able to understand what a 1RR restriction means. Your desire to reinsert your content without delay is precisely why we have editing restrictions on these articles. Additionally, it wasn't only one COPYVIO, it was at least three that I have found on this article alone. You have been editing since 2009. Based on my interaction with you and the repeated polite informal reminders I took the time to give you and continued argument and violations that followed those reminders, I feel comfortable bringing this to AE if the disruption continues, where they can clarify the meaning of 1RR and issue a formal warning if it is necessary, Seraphim System ^(talk) 00:57, 19 December 2017 (UTC)

Like I said, it was your abuse of the literal interpretation of the 1RR rule that brought me here in the first place. I do not see anyone else agreeing with your interpretation. You can take your case wherever you'd like, but it may result in self-inflicted sanctions. --Wiking (talk) 03:04, 19 December 2017 (UTC)

@Jayron32, Only in death, Hullaballoo Wolfowitz, Blueboar, and Seraphimblade: Since you were waiting the the specifics, was hoping to hear from you, especially since the issue has not been resolved. I received yet another warning, this time for changing "American reactions" to "Domestic reactions" - so, apparenly, my opponent believes that editing any part of the text is considered a revert since it changes it from the original form, and in this case, bringing up a completely unrelated change made in a different section four days earlier, and therefore claiming that it was my second revert and a 1RR violation. Similarly, when he removed an important and properly sourced detail from the LEDE and I, upon realizing that it was not mentioned in the article elsewhere, restored it in the background section, he considered this to be a revert as well. It seems that we need a narrower definition of what's considered a revert, with exemptions covering these cases. --Wiking (talk) 16:50, 20 December 2017 (UTC)

No longer care... I have come away with the impression that everyone involved with this is “wikilawyering”. Suggest both Wiking and Seraphim go and edit some other articles for a while. Blueboar (talk) 20:56, 20 December 2017 (UTC)

Blueboar (talk · contribs) As long as there are no more COPYVIOs I don't care either, but a proposal that an editor inserting repeated COPYVIOs into an article should be given special leniency under the ARBPIA editing restrictions is clearly disruptive. If it was serious, it would have to be proposed at WP:ARCA. I don't think you are suggesting that I should have left COPYVIOs in the article. Seraphim System ^(talk) 22:38, 20 December 2017 (UTC)

That was not the proposal. The proposal was that curing previously reverted COPYVIO should not be considered a revert, as it was not the intent of 3RR or 1RR. --Wiking (talk) 22:43, 20 December 2017 (UTC)

The best thing to do would be to discuss it with the editor and agree on a rewording together. I did not want to rewrite it because the previous night I was dragged into AE for correcting an obvious error, and reverting a 1RR violation. I was told to bring further 1RR violations directly to AE. I did not rewrite it because I thought rewriting a COPYVIO would be considered a revert, though I see from comments here that the rewrite would fall within 3RRNO as well. I will do this next time, but I think the best thing is to try to reach an agreement first in ARBPIA, where even one-word reverts can escalate into edit wars. That is why we have editing restrictions in this topic area. Seraphim System ^(talk) 23:09, 20 December 2017 (UTC)

I'm glad that you no longer consider a rewrite to be a violation of 1RR or 3RR. If something was removed solely due to COPYVIO, it can and should be re-written and does not require further discussion in ARBPIA or elsewhere. If you revert something for a different reason, next time state the proper reason behind your objections, besides COPYVIO, and we will follow the established protocol. --Wiking (talk) 23:25, 20 December 2017 (UTC)

P.S. I still think that a rewrite warrants its own exemption, since even an experienced editor such as you are can misinterpret the current 3RR rule. --Wiking (talk) 23:27, 20 December 2017 (UTC)

The last time I checked, which was a while ago, the so-called "3RR" policy was written so that any three non-consecutive edits counted for the person trying to add material, because it doesn't matter whether your attempt to add content involved the same or different material. So if, for example, you add "foo" to the lead, and I revert it, and add an image to the first section, and I revert it, and you fix a spelling error in the last section – then that's three "countable" edits against you, because your three unrelated additions have "undone" the previous editors' choice to omit foo from the lead, to not have an image in the first section, and to put a spelling error in the last section.

The justification, when I asked, was that No Good Editor would ever abuse this, but that various Bad Editors would wikilawyer over whether trying to add the same bad content, in different places or with different words, were actually "edit warring". I am uncomfortable with this. If you don't want to get bit by aggressive enforcement of the written rule, then you will want to avoid making three or more non-consecutive series of edits to any page in any day (three, not four, because if your third edit series ends in an edit conflict, then you will have accidentally ended up with four "reverts"). WhatamIdoing (talk) 18:37, 22 December 2017 (UTC)

That doesn't at all match the policy I see at WP:3RR. The key is that a revert is defined as "any edit (or administrative action) that reverses the actions of other editors, in whole or in part, whether involving the same or different material".

• The initial edit adding "foo" wouldn't be a revert unless someone just removed "foo" (or something similar) recently. Otherwise it's not reversing the action of another editor.
• Adding an image wouldn't necessarily be a revert either, although it gets more murky here since it in part depends on whether adding the image is considered reverting the removal of "foo". It would probably depend on the details of the specific situation.
• And fixing a spelling error almost certainly isn't a revert. Unless it's something crazy like warring over a {{sic}}, maybe.

It seems to me that whoever gave you that justification was radically off base. Anomie⚔ 23:37, 22 December 2017 (UTC)

How Wikipedia fights for facts by redefining the truth

After coming across this amazing essay (Wikipedia:Why Wikipedia cannot claim the earth is not flat), one of the most intelligent attempts at addressing a fundamental question in Wikipedia, I am proud to say it also informed this feature, published by Israel's Haaretz newspaper in both English and Hebrew this past week.

The story attempts to show how editors try to defend factual content in an encyclopedia where the definition of what constitutes a fact is also set by the community and is intended for readers with little to no personal experience or understanding of Wikipedia. The main claim in the article is that this is achieved by striving for verification of facts and not absolute truth.

The story attempts to show and debate Wikipedia and its polices implicit position on the question of truth, and, unlike most reports of this style, does not attribute independent agency to Wikipedia, instead addressing how different parts of the community involved in this efforts view it.

Would love to hear what you think. Omer Benjakob (talk) 08:05, 16 December 2017 (UTC)

I´ve enjoyed your articles (assuming you´re that Omer Benjakob), it´s rare to see WP written about at this "deep", so to speak. If you haven´t seen it yet, you may find this discussion a little interesting Talk:Intelligent_design#My_$0.02_on_the_issue_of_bias Gråbergs Gråa Sång (talk) 10:55, 16 December 2017 (UTC)

The article is paywalled, is there any way to get around that? Also, I don't think this is an appropriate place for this discussion. Thanks, Darylgolden^(talk) Ping when replying 11:17, 16 December 2017 (UTC)

Hm, neither is paywalled to me, a location thing? Or one of those "X free articles per month"? BTW, would you say there is an appropriate on-WP place for this discussion? User talk:Jimbo Wales perhaps... Gråbergs Gråa Sång (talk) 11:31, 16 December 2017 (UTC)

Or maybe Wikipedia:Village pump (miscellaneous). Gråbergs Gråa Sång (talk) 12:51, 16 December 2017 (UTC)

Wikipedia:Village pump (miscellaneous) would probably be a better place, though I'm not sure if if it's appropriate even there. Darylgolden^(talk) Ping when replying 13:46, 16 December 2017 (UTC)

"Give me feedback on my off-WP work!" is hard to fit in somewhere, isn´t it? Still, there´s always WP:IAR ;-) (yeah, yeah, that doesn´t quite apply either...) Gråbergs Gråa Sång (talk) 14:03, 16 December 2017 (UTC)

Hey all, I am indeed the author of the article and am pleased that you find it "deep". I was indeed unsure if this is the right place and I think it is telling that "off-WP" work about WP does not necessarily have its own place within Wiki, which I think explains why some essays are indeed meta and abstract, if not to say down right philosophical. Thanks for the link User:Gråbergs Gråa Sång - if anyone else has anymore pages that they think could be of interest to me, or even just stories from inside WP, especially those indicating shifts in what you hold to be important polices or debates about doing so, then send them my way. I think it is important to cover WP - not just as content, but also as a project Omer Benjakob (talk) 09:18, 17 December 2017 (UTC)

Now that is something you should ask for at User talk:Jimbo Wales, I think all kinds of people are watching that. Gråbergs Gråa Sång (talk) 09:33, 17 December 2017 (UTC)

The flatness of the earth may be more controversial than you (and the essayist) think. It's true that almost no scientists have thought the earth was flat since about the fourth century BC, but are these the only reliable sources?

What about artillery people? The trajectory of a shell, we are told, describes a parabola. In Australia and I suspect most of the world, high school students of mathematics regularly solve problems using this assumption, and so I believe do the armies and navies of the world, and with deadly accuracy. But this of course assumes that the earth is flat. If it were not, then the trajectory would be an ellipse. (;-> (The essay does mention this argument, rather dismissively, and IMO inadequately.) Andrewa (talk) 10:24, 19 December 2017 (UTC)

Andrewa, the artillery shell trajectory above is a bad example for a couple of reasons. First, the trajectory remains a parabola relative to a flat plane regardless of where it intersects the ground (higher than the plane on a mountain side or lower than the plane because the range has extended beyond the noticeable curvature of the earth. Like high school students using a theoretical model, gunners use the model only to the point where the errors are minimal with respect to the other errors involved. Basic (short range) gunnery tables can use this model without taking in to account the curvature of the earth. This is in fact why gunnery solutions for longer range artillery engagements (say greater than 25 km) does in fact have to "calculate for the curvature of the earth". Remember the maxim "All models are wrong, but some are useful". And yes, I used to be an expert on such things too. 'Cheers, Loopy30 (talk) 18:06, 19 December 2017 (UTC).

Some excellent points there, and they're exactly the reason that I think it's such a good example. (25km is a bit short, 40 mile bombardments used the parabola model quite successfully in the days before electronic computers.) But your argument the trajectory remains a parabola relative to a flat plane... is interesting. In fact the trajectory is never a parabola, in that it's always better approximated by an ellipse, but only very slightly in the case of a short-range artillery shell flight. The good results obtained by the parabola model are valid evidence that the earth is flat, but we have long had better evidence, and better models based on this evidence. (Similarly "it's flat where I live" is a valid argument. A builder properly assumes that the plumbob gives parallel lines wherever in the house he uses it, and it's close enough, although those "parallel" lines intersect at the centre of the earth.) As many have observed, the dismissal of flat-earth arguments is often more akin to a religious faith in something wrongly called science than to an application of scientific reasoning. That's the point. Andrewa (talk) 20:18, 19 December 2017 (UTC)

I have to say, I'm more than a little disturbed by even the perception that the Günter Bechly article was deleted "as revenge by the scientific community on Bechly for using his status to promote his own religious beliefs". We don't delete biographies for revenge, or because we don't agree with the subject's views.
Or at least, we aren't supposed to. If that did happen (and sadly I don't find it entirely implausible), then it was a serious abuse of process. --Trovatore (talk) 11:21, 19 December 2017 (UTC)

Trovatore reading Wikipedia:Articles for deletion/Günter Bechly may provide enlightenment, or not... Roger (Dodger67) (talk) 11:36, 19 December 2017 (UTC)

Well, exactly.... --Trovatore (talk) 11:44, 19 December 2017 (UTC)

The AfD was not so much an abuse of process as an example of how our processes can go wrong. Most of the arguments on both sides were sufficiently flawed to be discarded by the closer, and they did an excellent job wading through them. But IMO the result was still both wrong and counterproductive. It's not the only pimple on Wikipedia's face, and they'll always be there. See User:Andrewa/silly ideas#Reliability for a blatant case of circular reporting for example. But I'm sure it will eventually be fixed, just as the NYRM2016 fiasco was in time overturned. And ironically, when the Günter Bechly article is eventually recreated, part of the justification will be the sources that now discuss Wikipedia's action in deleting the article. Andrewa (talk) 19:54, 19 December 2017 (UTC)

Someone had the same thought when this was discussed at the fringe noticeboard awhile ago. Stranger things have happened. Gråbergs Gråa Sång (talk) 22:33, 19 December 2017 (UTC)

Indeed. The six star rank article was also deleted (see discussion here), but in that case quite quickly recreated. (It's still such a lousy excuse for an article that it would be better deleted IMO... but some hobbyists own it.) Our processes are (again) not perfect! Can you provide a link to this fringe noticeboard? Sounds interesting. Andrewa (talk) 00:37, 20 December 2017 (UTC)

I could have been more clear: Wikipedia:Fringe_theories/Noticeboard/Archive_58#This_noticeboard_mentioned_in_media Gråbergs Gråa Sång (talk) 08:57, 20 December 2017 (UTC)

All good, and thanks for the link. Very interesting, as you say, and many good points made there. We are to some extent reinventing the wheel here. Andrewa (talk) 09:06, 20 December 2017 (UTC)

It´s hard to avoid such a perception whether true or not, from those who wish to perceive it. The perception that some !voters had been off-WP canvassed may have pissed some other !voters of. Someone can always try to recreate the article or start a deletion review if they think it´s worth it. However, "it would have been wiser, if only for the historical record, to keep Bechly’s entry" (Benjakob) is not WP either. There´s Deletionpedia, though.[43] Gråbergs Gråa Sång (talk) 18:51, 19 December 2017 (UTC)

And at least two other archives, one of them at Wikia would you believe it. See Unimpedia:other unarchives for a list, and if there are others please tell me. Or perhaps we should propose a List of online archives of deleted Wikipedia articles. (;-> Andrewa (talk) 02:04, 20 December 2017 (UTC)

They wouldn´t want to be called archives, but Everipedia [44] and Infogalactic [45]. Dear old Conservapedia doesn't have an article, but they know about him:[46]. Gråbergs Gråa Sång (talk) 09:18, 20 December 2017 (UTC)

Thanks.... as you suggest (I think), these aren't archives in the sense of the three unarchives I've found so far, they seem to be partial mirrors of Wikipedia. I hadn't found (or looked for) such before, but we can expect more of those I guess, especially as people discover how easily and cheaply AI can create and maintain a legal but POV mirror of Wikipedia... these don't look like that. The involvement of Larry Sanger in one of them is particularly interesting, his Citizendium seems dead in the water but that's no reason to assume that this one will be too. And I'm guessing there are and/or will be other satirical sites like my Unimpedia as well.

Very interesting. To me it underlines how important it is for Wikipedia to stick to the 5P (including wp:5P4 which even some sysops now seem to see as aspirational). They are more radical than some think, and more interrelated than might at first be obvious. And without them we become just another blog, and could go the way of Kodak with just as little warning... or perhaps even less.

And incredible as it may seem, we have now strayed into questions that are on-topic for this Village Pump subpage. Andrewa (talk) 16:51, 20 December 2017 (UTC)

View source text next to section titles on protected pages

Moved to WP:VPT § View source text next to section titles on protected pages

 – This would not require any policy changes. — xaosflux ^Talk 16:39, 19 December 2017 (UTC)

Minor edits

Is there a guideline or policy covering which edits should be flagged as minor?

Help:Minor edit covers it well but is not very authoritative, and doesn't link to anything that is (unless I've misssd it). Having been around since a little before that page existed, I think there used to be something, but I can't now find it.

And a guideline seems to me to be a good idea. See Special:Contributions/MaiWardi for some quite major edits marked as minor. Andrewa (talk) 09:44, 19 December 2017 (UTC)

@Andrewa: The help page you link to seems to quite well spell out what is and is not a minor edit. What do you think is missing? RudolfRed (talk) 19:41, 19 December 2017 (UTC)

I think that the criteria for flagging an edit as minor should be recognised somewhere in a guideline. Currently it seems to have no more status than an essay.

The main problem is that even if users blatantly abuse the minor edit flag to try to hide their unsourced and/or POV edits, there's not a lot to be done. (Trying to similarly hide vandalism is not a problem, as the accounts involved are generally vandalism-only accounts anyway, and as such can be (and are) simply indeffed.) Andrewa (talk) 21:26, 19 December 2017 (UTC)

I don't have time to dig them up now, but the AN/ANI archives do have a number of cases where editors have been sanctioned for repeatedly marking non-minor edits as minor. Its considered a form of disruptive editing. (Even if its not listed at WP:DISRUPT which it really should be under evading scrutiny) Only in death does duty end (talk) 08:57, 20 December 2017 (UTC)

Agree it is disruptive, but as you point out not explicitly so. If anyone can find archives of those sanctions I'd be interested. Andrewa (talk) 16:56, 20 December 2017 (UTC)

Definitely worth researching, and the place to codify it would be WP:EDITING policy.  — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  01:39, 22 December 2017 (UTC)

• Mis-labeling of major edits as minor used to be a major problem back when we had a preference setting "mark all edits as minor by default" (before 2011: phab:T26313). It seems much less common these days. But mentioning that it is not OK to mis-label edits as minor in WP:EDITING seems like a good idea. That Help:Minor edit and Help:Edit summary are "information pages" and not "guidelines" is weird, and maybe we should change that. Unlike Help:Move, which explains the technical details (and refers to Wikipedia:Moving a page), these pages actually explain both the technical aspects and the etiquette surrounding the use of the features. —Kusma (t·c) 18:00, 22 December 2017 (UTC)

Minor clarification: we still do have said preference, it's just hidden from the UI. It really should've been removed outright, in retrospect. FACE WITH TEARS OF JOY ^[u+1F602] 00:00, 27 December 2017 (UTC)

• The "This is a minor edit" checkbox should be removed from Mediawiki. That's the real RFC that needs to occur. The feature begs the question what counts as a major vs minor edit and there's no good answer to that because it's intrinsically subjective. Further, there's nothing to stop a person from marking major edits as minor or leaving minor edits unchecked. You can't use simple metrics either like the article diff size, of course, because it is very misleading regarding the impact to the article. As a frequent "minor" editor, I've also always felt having to mark my contributions as minor was slightly demeaning. Given only two choices, it'd be better if we were asked to mark edits as major to indicate "hey, please given my edit extra special proof-reading", not marking them as "minor" to have the effect of saying "hey, this is probably just a punctuation or spelling change you can skip". Bots edits already have their flags and, in my opinion, bot edits should never be marked as minor because bots make too many mistakes. The minor edit feature has been something that strikes me as a malfeature for a number of years now. Removing it entirely is low-hanging fruit for making editing slightly less intimidating for new users. We would gain simpler editing while losing almost nothing. Jason Quinn (talk) 15:55, 23 December 2017 (UTC)

Paid use of administrator tools RfC

An RfC has been started on paid use of administrator tools and disclosure at RfA at Wikipedia_talk:Administrators#RfC_about_paid_use_of_administrator_tools. All are invited to participate. TonyBallioni (talk) 23:41, 20 December 2017 (UTC)

Announce: RfC: Nonbinding advisory RfC concerning financial support for The Internet Archive

Wikipedia:Village pump (miscellaneous)#RfC: Nonbinding advisory RfC concerning financial support for The Internet Archive --Guy Macon (talk) 00:26, 22 December 2017 (UTC)

Proposal to adopt WP:WikiProject Video games/Article guidelines into MoS as "WP:Manual of Style/Video games"

FYI

 – Pointer to relevant discussion elsewhere.

Please see: WT:Manual of Style#Proposal: Adopt WP:WikiProject Video games/Article guidelines into MoS.
 — SMcCandlish ☏ ¢ >^ʌⱷ҅_ᴥⱷ^ʌ<  01:38, 22 December 2017 (UTC)