Wikipedia:Village pump (policy)

From Wikipedia, the free encyclopedia
Jump to: navigation, search
  Policy   Technical   Proposals   Idea lab   Miscellaneous  
The policy section of the village pump is used to discuss proposed policies and guidelines and changes to existing policies and guidelines.
If you want to propose something new that is not a policy or guideline, use 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.

« Older discussions, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137

Plea for a slightly less blunt WP:G5[edit]

Earlier this month, I went to make sure that the disambiguation page, "Nies" contained Judge Helen Nies, late of the Federal Circuit. I was surprised to find that not only was this entry lacking, but that there used to be a Nies (surname)—a completely innocuous (and useful) list of people sharing that surname—which was deleted with no discussion as WP:G5, a page created by a banned or blocked user. I have seen a number of other instances where perfectly useful and benign pages and redirects have been deleted on this basis, apparently with absolutely no thought going into the process. It is distressing to me to think that our policy is so blunt as to allow (much less require) that we punish our readers for the transgressions of editors through the deletion of good articles on this basis. Is there any way we can refine this policy to avoid outcomes that do more harm than good to the encyclopedia? bd2412 T 23:57, 15 August 2017 (UTC)

I agree with this wholeheartedly. Perhaps a gentle reminder for administrators to use good common sense when thinking of deleting the article at WP:G5? Or change the rationale to "Disruptive creations by banned or blocked users"? I also wonder whether there was a historical reason for this criterion that we are now forgetting... Malinaccier (talk) 00:01, 16 August 2017 (UTC)
Agreed. Judging by content and not by the author makes sense. — Preceding unsigned comment added by Jjjjjjdddddd (talkcontribs) 10:59, 16 August 2017 (UTC)
  • Deleting a disambiguation page is a bit blunt, but I do want to point out that when G5 is applied to BLPs it is often for the case of the protection of the subject: G5 is most commonly applied to sock farms with likely PAID issues. Unfortunately PAID cuts several ways: you have payment for promotion, payment for blackmail (Orangemoody-esque), and also payment to disparage competition. G5 is a blunt instrument, but it is very effective in helping us protect actual people from harm. For these reasons I'd oppose any change to the current wording, but agree that commonsense should prevail in cases like dab pages. TonyBallioni (talk) 00:10, 16 August 2017 (UTC)
    Perhaps we have the beginnings of a refinement there - definitely use G5 for BLPs, probably for any article on an extant business, organization, or product. Avoid using it on useful redirects, disambiguation pages, and the like. The problem, as I see it, is that there is nothing presently in the wording of G5 that even calls for the use of common sense. It does say "Pages created by a topic-banned user may be deleted if they come under that particular topic, but not if they are legitimately about some other topic"; I don't see how that limitation could have been applied in the case of the page deleted in this instance. bd2412 T 02:55, 16 August 2017 (UTC)
Having seen lists created as supporting material for spam articles, and having seen A7 fall from being a useful deletion criterion to becoming a battleground, I favour leaving the matter at the admin's discretion. While I appreciate BD2412's intent, blocked should mean blocked, and blocked users shouldn't be offered loopholes in their blocks. Cabayi (talk) 06:40, 16 August 2017 (UTC)
  • For non-banned editors, we keep their good edits and pages and revert their bad edits and delete their bad pages. If an editor is banned, we also reject their good edits and pages. If we do not delete good pages per G5 or revert good edits on sight, the only difference between banned and non-banned editors is that the banned editors have to change username once per day. —Kusma (t·c) 06:49, 16 August 2017 (UTC)
  • The principle of a ban is very simple: As long as the edit is just the edit of a banned user, it can be removed - revert an edit to an existing page, delete a new page. If an established editor (not necessarily an admin, but clearly not a sock of a banned user) declares that (s)he is willing to take responsibility for that edit, it ceases to be "just the edit of a banned user". This can be done after the edit was removed as well as before - if you restore a correctly G5-ed page, that is generally taking responsibility for it. עוד מישהו Od Mishehu 11:04, 16 August 2017 (UTC)
An important principle here is that the meaning of words like may and can is NOT a synonym for the word must. G5's language is fine, but the problem is enforcement. The problem becomes where damnatio memoriae becomes cutting off the nose to spite the face. We shouldn't have to jump through extra hoops to delete contributions of banned users. However, saying that, we shouldn't feel the requirement to delete them where it creates a greater hassle than just leaving it alone. --Jayron32 11:39, 16 August 2017 (UTC)
To quote the first line of the prose of WP:CSD: The criteria for speedy deletion (CSD) specify the only cases in which administrators have broad consensus to bypass deletion discussion, at their discretion, and immediately delete Wikipedia pages or media. They cover only the cases specified in the rules here. The key words here are "at their discretion". עוד מישהו Od Mishehu 06:22, 17 August 2017 (UTC)
Some administrators seem to be reading "at their discretion" to mean "delete everything without a second thought". bd2412 T 18:23, 18 August 2017 (UTC)
If an admin sees a pattern of bad edits, they may decide reverting some good ones is worth the price of reverting the whole bunch automatically, to avoid the cost of checking every edit which is pretty high. -- GreenC 18:40, 18 August 2017 (UTC)
  • I quite agree with the sentiment set out above by BD2412, in that we are not doing our readers any favours at all, and the phrase used by Jayron32 above about cutting off ones nose seems apt here. While I agree some banned users' contributions are always problematic, others are not necessarily, and admins should be reminded on these occasions to use appropriate judgement, rather than blindly follow the rules as set out. On reading the actual policy, it says This applies to pages created by banned or blocked users in violation of their ban or block, and that have no substantial edits by others. G5 should not be applied to transcluded templates or to categories that may be useful or suitable for merging... Perhaps this could be tightened up somehow, along the lines of "Administrators should use their discretion when applying G5, so that it does not unintentionally inconvenience readers". Aiken D 19:01, 18 August 2017 (UTC)
  • I can't think of anything better to say than TonyBallioni's comment above. Kudpung กุดผึ้ง (talk) 13:56, 20 August 2017 (UTC)
  • Support A number of editors, including some admins, have been interpreting G5, and the banning policy generally, to say that all pages created by banned editors, and all edits made by banned editors, must be deleted on sight. This removes the element of discretion alluded to in several comments above. And deletion is a non-symmetrical operation. It is comparatively easy to find things one wants to delete, for whatever reason -- all our search facilities and navigation aids are in place. But once something has been deleted, an editor must basically already know the exact page or article name to even request undeletion. And only admins can see anything beyond the page title and the reason given in the deletion log. (The log is not really usefully searchable anyway. It is too big, with too many items added every day, and is not in any way indexed.) As a result of this non-symmetry, argumets that deletion is ok because one can ask for undeletion fail. This change would help avoid that imbalance in cases where it should not exist. i would favor going further, and repealing G5 completely. But I don't expect to get consensus for that. DES (talk)DESiegel Contribs 15:07, 20 August 2017 (UTC)
Repealing G5 completely.....Probably followed by repealing WP:PAID.....And laying a welome-mat for the paid-editors-guild.....Sigh......Winged Blades of GodricOn leave 15:57, 20 August 2017 (UTC)
  • Oppose any change. That some admins speedy delete articles created by UPE sockfarms and the like instead of expecting volunteers to verify/fix them is one of few rays of hope that Wikipedia won't end up as a spam-ridden garbage dump. I don't blame editors for deleting seemingly innocuous pages rather than spending hours checking for misrepresented references and all the other tricks UPEs use. Some collateral damage is unavoidable. Rentier (talk) 16:50, 20 August 2017 (UTC)
  • Oppose - Unfortunately, some socks are skilled at creating pages which look useful and are full of subtle problems. G5 and BAN allow us to act first and ask questions later. Any established user who is willing to take responsibility for a specific banned user's edit can save it from being removed; however, to require users to check before they revert or delete is unreasonable. עוד מישהו Od Mishehu 11:40, 21 August 2017 (UTC)
  • Oppose any changes since we're making this formal now. I oppose any change that would take the discretion to protect living persons from admins. Actual people are infinitely more important than articles and with sock farms we simply don't know if there is Orangemoody-esque blackmail going or worse, if the article has been created as a coatrack to defame the other person. Both of these happen a lot more frequently than people who don't work in new pages realize. I'd also like to repeat my above call for commonsense and discretion: minimizing the collateral damage here is also important. Having a informal hierarchy of when we should and shouldn't use G5 would also be helpful, and I think that was what this original post was about. TonyBallioni (talk) 17:19, 21 August 2017 (UTC)
  • Use a footnote: Nies (surname) is a good example to use in an explanatory footnote that WP:Common sense has to be applied. Using a footnote for this would obviate any need to change the extant wording of G5. Actually, the same footnote could also be used for G4: Do not delete a page that simply has the same name as a page previously deleted. The rationale for the original deletion has to still apply to content of the new page, which may be something completely different, or someone else's much better article on the same topic as the original page. If people don't like footnotes, it could be done as a short section of regular text.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  21:51, 23 August 2017 (UTC)
  • Oppose any changes to G5 per WP:BMB. -- Tavix (talk) 12:26, 25 August 2017 (UTC)
  • Oppose any change to G5. Firstly the article is deleted only if the sock or the banned editor is the sole contributor if other editors have made major contributions it is not deleted.Those indef blocked or banned should not edit in the project while blocked or banned Pharaoh of the Wizards (talk) 19:16, 25 August 2017 (UTC)
  • Support change The sense I have from this discussion is that this rule must be enforced, common sense be damned. Which is ridiculous, & threatens the validity of the project. If a rule violates common sense, then the rule is wrong; we need to acknowledge that there are exemptions to this rule. (As an aside, were I faced with this situation, after verifying the article in question was unobjectionable other than being the production of a banned contributor, I'd make a copy, delete the original article & its edit history, then recreate it under my own name -- thus taking responsibility for any errors it might have. And taking responsibility is at the heart of WP:IAR.) -- llywrch (talk) 22:58, 6 September 2017 (UTC)
That's fine - note the sources, preserve the copyright-free infrastructure of categories and Defaultsorts and so on, then re-create the article yourself in your own words, checking the sources and updating "access date". The blocked editor does not get the satisfaction of seeing "their" article survive. I think that's a key element of G5. PamD 08:26, 7 September 2017 (UTC)  :::@Llywrch: - forgot. PamD 08:26, 7 September 2017 (UTC)
  • Support It's about time we put a stop to this. Per PamD, if an admin deletes an article under G5, they must rebuild it. Hawkeye7 (talk) 09:25, 7 September 2017 (UTC)
Under that regime, if a banned user creates an article full of made up facts and made up references, then the deleter would be obliged to spend far more time, properly researching and correcting it all. It isn't sustainable. Burninthruthesky (talk) 11:59, 7 September 2017 (UTC)
I wasn't thinking of going that far. Take RAF Shepherds Grove for example. The admin deleted the article under G12, then re-created it with the copyvio components missing. This is simpler than deleting and revdel-ing. But an admin has to do this work. I cannot access the deleted text because I'm not an admin. Hawkeye7 (discuss) 22:29, 8 September 2017 (UTC)
I'm not proposing any such regime, just commenting that if Llywrch finds it offensive to delete an article they are quite at liberty to reconstruct it. That's very different from saying that "if an admin deleteds an article under G5, they must rebuild it". Please don't misrepresent my words. PamD 12:12, 7 September 2017 (UTC)
  • Oppose any change per WP:BMB and WP:NOTMANDATORY. Existing policy already allows discretion for good edits to be left as is, but there is no obligation to keep them. Burninthruthesky (talk) 11:59, 7 September 2017 (UTC)
  • Oppose: a blocked editor should not have the satisfaction of seeing their sockpuppet article creations exist in the encyclopedia; that would only encourage future sockmasters. PamD 12:12, 7 September 2017 (UTC)
  • Oppose eroding one of our only measures against large-scale paid editing and other long-term disruptions. Common sense discretion is already part of our guidelines in such cases, but due to the sheer amount of work some human mistakes will happen - any editor in good standing can easily fix them just like we would fix any other good-faith mistake. Also, DABs and redirects have been misused by sockfarms in the past and should not be excluded from admin deletion. GermanJoe (talk) 13:10, 7 September 2017 (UTC)

Upgrading WP:INFOCOL[edit]

I think time has come to upgrade the status of Wikipedia:Infobox consolidation from a mere essay, so that it standardisation and consolidation process may speed up a little. -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 02:23, 23 August 2017 (UTC)

That's not written in guildeline style, and many points in it are just someone's opinion. A few points in it should probably be integrated into WP:INFOBOX and/or MOS:INFOBOX, as appropriate. What it is, is someone's attempt at an FAQ [or "a FAQ", depending on how you say "FAQ"], which makes it an essay, especially since these mostly do not appear to be questions that are actually frequently asked. Some of the points in it do not really pertain to infoboxes in particular, but are just standard WP:TFD operating procedure for templates in general: we merge redundant ones when possible, to reduce the confusing profusion of low-use templates.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  21:31, 23 August 2017 (UTC)
Can you please guide on how to improve it to standards? -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 15:34, 24 August 2017 (UTC)
No, because as I said, "a few points in it should probably be integrated into WP:INFOBOX and/or MOS:INFOBOX, as appropriate", while some of it's subjective, and other parts aren't specific to the issues but are general "what we do with redundant templates" stuff. WP is not in the habit of promoting essays to guidelines, nor creating new guidelines. I can't even remember the last time we did that. We don't need new guideline pages, only refinements to the existing ones, when there's an identifiable problem that can be addressed by doing so. What ongoing, recurrent problem is addressed by anything in that page? In what way(s) is it not already addressed by extant policies, guidelines, and TfD procedures? "I want to promote my essay to guideline status" isn't a valid rationale.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  16:51, 24 August 2017 (UTC)
In that case, can you please help me in integrating "a few points in it into WP:INFOBOX and/or MOS:INFOBOX, as appropriate"? -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 05:11, 25 August 2017 (UTC)
In theory, though this is a busy time. The first steps are identifying specific problems to solve, demonstrating they're real problems, and demonstrating that existing guideline/policy language doesn't already cover it (i.e., it could be a behavioral problem on the part of a certain editor or group of editors rather than a guideline wording problem). We don't have guidelines about problems that are only theoretical. When you've identified a clear hole in the guidelines and that it needs to be plugged, I'm pretty good at wordsmithing the plug for the hole. I want to reiterate that much of that page is just describing what WP:TFD already does, so that's all "rehash" material. What is unique to the infobox issue(s)?  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  07:11, 2 September 2017 (UTC)
Such a policy is needed to reduce comments in discussions like [1]. Also check out {{Infobox fashion designer}} and {{Infobox Hindu leader}}, such Infoboxes should have been merged long before, but more like these still exist. Arguments like these erupt in almost every merge discussion and then the discussion forum gets converted into polling booth based on such arguments. That is why such a policy is needed as there is a good enough policy to describe conditions for deletion of a template but not for merger, specifically for Infoboxes. -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 16:08, 6 September 2017 (UTC)
Another [2] -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 15:42, 9 September 2017 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Now even admins doing the same thing here. -- Pankaj Jain Capankajsmilyo (talk · contribs · count) 12:21, 13 September 2017 (UTC)

WP:ACTRIAL date[edit]

Hi all, just posting here that Wikipedia:Autoconfirmed article creation trial is currently scheduled to go live on 7 September 2017. This is pending final security review of the code by the WMF. The trial is currently scheduled to last 6 months, with data being reported as the trial is conducted. TonyBallioni (talk) 22:07, 24 August 2017 (UTC)

Thanks for posting. L3X1 (distænt write) 13:06, 29 August 2017 (UTC)
Good to know! —TheDJ (talkcontribs) 11:16, 31 August 2017 (UTC)

As an update, this has been delayed until 14 September due to technology problems with visual editor. For more information see WT:ACTRIAL. TonyBallioni (talk) 19:49, 6 September 2017 (UTC)

Articles about churches; titles of the format St. X ('s Church), Somewhere[edit]

Not sure if this the right place for what I have to ask: if not, please redirect me. A colleague recently created an article St. James, Levoča; this was then moved by a third party, without discussion, to St. James Church, Levoča. (It's since been moved, and appropriately imo, to Basilica of St. James, Levoča, but that's another story).

On the talk page of the article I noted:

--- This is a tricky one. It seems that all varieties of punctuation are used for this purpose on Wikipedia. For examples:

and sometimes without the '.' after St, e.g.:

And there are doubtless other versions as well. ---

There doesn't seem to be a WP standard. If it were up to me, I would propose the format St. X's Church, Somewhere. (And, by the way with >'s< even if the saint's name ends with an >s<). Should there be an attempt to create a standard, and if so, what's the best way to go about it? Thanks, Smerus (talk) 10:50, 31 August 2017 (UTC)

I suspect this is likely to fall foul of WP:ENGVAR. As different countries can puncuate differently. Have you identified if there is a national cause? (eg the US use St. James' Church, UK St. James's etc) Only in death does duty end (talk) 14:09, 31 August 2017 (UTC)
Well I'm not going to lose too much sleep over >'s< or >'< after a name ending in s. But the more important issues for standardisation are a full stop after St, the inclusion of the word Church, a comma before the placename, and the placename itself not in brackets. These ideas are surely not too controversial - or are they?--Smerus (talk) 16:45, 31 August 2017 (UTC)
I have no strong opinion about this myself. However, when looking for examples I noticed similar issues with schools (St. Paul's School (New Hampshire) versus St. Paul's College, Hong Kong) and streetnames and the like. So if we decide on a consistent application we may should consider to cover those as well. Arnoutf (talk) 17:14, 31 August 2017 (UTC)
As to the full stop. please see Wikipedia:Manual of Style#Full stops and spaces:
Standard North American usage is to end all abbreviations with a period (Dr. Smith of 42 Drummond St.), but in standard British and Australian usage, no stop is used if the abbreviation ends in the last letter of the unabbreviated form, except when confusion could result (Dr Smith of 42 Drummond St).
This would appear to be an ENGVAR issue, so we follow those rules - see, for example, Labor Party (United States, 1996) vs. Labour Party (UK), which illustrates different spellings for the word "Labo(u)r". עוד מישהו Od Mishehu 13:41, 1 September 2017 (UTC)
This is one where we simply can not set a standardized style... because there is too much variation in reality. The best we can do is deal with it at the article level... on a church by church basis... deferring to the common usages of reliable sources that discuss each specific church. Blueboar (talk) 22:05, 1 September 2017 (UTC)
I would love to have a standard (specifically the one advocated by Smerus, as ambiguity- and confusion-proof), but we've been over this many times before. The fact of the matter is that some of these places have had set-in-stone names since before English punctuation was standardized, and consequently have "hardened" into strange constructions like St Johns Church without the apostrophe. People who think in an "official name" way argue to keep them that way, and those who think in a "common name" way also make the same argument, because most of the RS use the "official" spelling. This view isn't crazy, it's just prioritizing the expectations of readers already intimately familiar with the subject over those of everyone else, and over consistency.

As for the "James'" versus "James's" matter, it is simply not true that this is a WP:ENGVAR matter; style guides on both sides of the Atlantic recommend both. It's primarily a split between academic-style clarity ("James's") and news-style expediency and compression ("James'"). Same goes for dot-dropping; even in British academic style, the only dots dropped are those in acronyms like AIDS and those in abbreviations formed by contraction so that they start and end with the same letters as the full word (Dr for Doctor, but Prof. for Professor). It's only the British journalism publishers that are dropping almost all dots.

In both cases, because WP is an encyclopedia not a news source or any other journalism publication, we should follow the academic, clearer, hard-to-misinterpret style, as we do in virtually all other style matters. We do this with numeric material (e.g. "9 pm" or "9 pm", "23 cm", "3 ft", etc., not "9pm", "23cm", "3'". We also do it with various non-numeric cases where academic and news style conflict; e.g. is using spaced and unspaced en dashes (for different purposes) and unspaced em dashes, in prescribed ways found in academic style guides, while news style has no en dash at all, and only uses unspaced hyphens (for unspaced en dashes) and unspaced em dashes (for unspaced em dashes and spaced en dashes). I could list out dozens of other examples.
 — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  06:56, 2 September 2017 (UTC)

I am assuming a nationalistic split: British journalistic style guides (such as my favourite, Guardian Style) tend to recommend writing "s's", whilst academic ones (like NHR) prefer to lose the second "s"—"s'". From a British perspective, it looks a little odd for a second "s" to be present, but I do not think that it will cause too much of a problem. Im my experience (although I cannot say that I have spent that much time in such places), churches seem to go for ending with an apostrophe, but—again—whilst it may be comparatively rare, it would certainly not come as too much of a surprise to see the extra "s" tagged onto the end. I would go with what the churches themselves choose. I cannot imagine that stylistic purity is their main concern, but we would at least be providing readers with a realistic and truly reflective impression of what they would see (and, presumably (unless they have some national database containing perfectly-styled church names ... highly unlikely), it is the place's proper name). I am sensing a slight link with MOS:TMRULES here, in that the question of whether we should be "correcting" the language of names, etc, seems to be at the forefront of the discussion. –Sb2001 talk page 23:44, 8 September 2017 (UTC)
  • Why do we need a standard? It would seem the disadvantages, increased bureaucracy, would outweigh any advantages. RileyBugz会話投稿記録 21:43, 2 September 2017 (UTC)
  • That won't do. On the same argument (i.e. that some people would object to it), the setting of any standards in WP would be a non-starter. The reason we have standards in WP is (in part) to attempt to convey reliable and hard-to-misinterpret information. The chaos over church names, if we leave it as it is, is an abdication of responsibility. So I am with SMcCandlish. Smerus (talk) 10:40, 3 September 2017 (UTC)
  • I already answered the "why" question: because it reduces ambiguity and confusion (and thus disputation). There is actually less bureaucracy in imposing a single standard across-the-board than in trying to maintain a system of confusing "multi-standards" and when to apply them and how to resolve disputes about them.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  00:07, 4 September 2017 (UTC)
Are there formal standards, though, besides that we do what reliable sources do? And wouldn't this only cause confusion for people who edit, and edit in areas related to churches? I honestly don't think that a new editor or a reader would really notice a specific standard in this area. And it just adds one more to the policy/guideline pages; why don't we just follow whatever reliable sources call it? Isn't that the one standard for articles? Also, I think that such a thing would in fact increase the confusion; if a reader or editor sees a church called in reliable sources xyz, won't they look up xyz? And if we instead have it as xzy, and it doesn't appear in the top search results, then how can we say that we are doing our job? It ignores the standard of following what others have. RileyBugz会話投稿記録 00:22, 4 September 2017 (UTC)
That's a slew of points and questions, some unrelated, some unclear, and some redundant. I'll respond to them in the order they're presented:
Extended content
  • The first could mean one of at least three things:
    • If you mean "Is there a formal standard, off-Wikipedia, for how to write things like this?" – Of course not, because there is no formal standard for anything in the English language; we have no equivalent of the Academie française.
    • If you mean "Does WP already have its own internal formal standards about this particular matter?" – Obviously not, or this discussion wouldn't exist.
    • If you mean "Does WP have formal style standards that we use, in lieu of just copy-pasting from sources?" – Yes, at WP:MOS and its subpages (plus WP:AT policy can be seen as a style standard of a sort). Running with the third interpretation of that question, it's standard operating procedure for MoS, like any other publisher's house style guide, to set an internal standard for any particular style matter. That is what a style guides does and exists for.
    • Regardless, your supposition that WP derives its style from mimicking sources on a topic-by-topic basis is completely incorrect.
  • Your second (question) and the third (sentence) that follow it are self-contradictory; you can't in the same breath suppose that a standard will confuse someone if you also believe they'll never see it.
    • But the premise of the second point doesn't hold up, or the world would have no style guides. Everyone who is literate is familiar with the idea of a style guide and with the fact that they differ and thus that styles vary. Everyone competent to work on Wikipedia is aware that different publishers have different style guides with different rules in them.
    • The third point is true and well known, but not important: No one is required to read and follow MoS, or any other guideline or policy, before they edit here. After they're made aware of one, they're expected to abide by it, but even this is not "enforced" with regard to MoS (they only way you'll get in any MoS-related trouble is by a) being a flaming gas-bag of hate or WP:GREATWRONGS activism over style trivia until community patience wears out, or b) interfering with others editors writing MoS-compliant material and bringing non-compliant material into compliance. MoS exists primarily for WP:GNOMEs. The average editor doesn't read MoS or most of our other guidelines.
  • Your fourth point just reduces to "why do we have any rules? wouldn't it be simpler to delete all guidelines and policies?" It's tautological that having a new rule adds a rule.
  • Your fifth point (after the semicolon) doesn't work when the RS are not consistent, when most of the RS use a style that is confusing or otherwise non-encyclopedic, and in various other contexts. The WP:Specialized-style fallacy is usually in play any time someone wants to apply the "follow the sources" article content rule to an internal WP style guideline, because sources reliable for facts about something are not the most reliable sources for how to write accessible English about that topic, for a general audience. Only style guides are, we have our own, and it's already based on the best-accepted, off-Wikipedia style guides. No external third-party source dictates to WP what its style guide says. Only consensus determines its content, based on a combination of what external style guides say, with more weight given to mainstream and academic ones that niche ones (a form of non-neutrality, which would not be permitted in articles), what mainstream reliable publications are doing if they all seem to be pretty consistent (original research which is also forbidden in articles), and community experience of what does and doesn't work well here (also original research). The content policies do not apply to internal WP materials like guidelines, only to encyclopedic output.
  • Your sixth point is repetition, so I give a repeat answer: WP's MoS and its title policy are not articles and article-related rules not only do not apply to it, they couldn't logically or practically be made to apply. It's like supposing that the rules of a boxing match apply during the business meeting for drafting the rules.
  • Your seventh point is largely repetition again, the first half already addressed. The second half is easily answered: we have redirects for a reason, and the reader will end up at the right article no matter what spelling or punctation they happened to encounter for the same place in whatever it was they were reading elsewhere. It's the very idea of trying to differentiate WP articles on all these places by "magically different" spellings, which vary in unexpected and inconsistent ways, that is apt to lead to confusion and to difficulty in finding articles or editing them without conflict. Especially given that, on average, it's going to be people unfamiliar with a place (and any peculiarities about how locals spell it) who are most likely to look up the place here, not people who live next door to it (they might be more apt to edit about it but are also more apt to want to fight with people over spelling trivia).
  • Your eighth point (final question) is covered by the last answer. As long as we create redirs, they'll get to the same article, and no one will care or make much of a fuss about it (unless their primary motivation for participating in Wikipedia is picking fights over style trivia (see WP:NOTHERE, WP:COMPETENCE, WP:5THWHEEL) because we're all smart enough to see that the world isn't consistent about the spellings of these things, but that being consistent within a single publication is a benefit both to readers and to editorial maintenance. If this were not the case and were not clearly proven by experience, WP would have no style guide, nor would anyone else.
  • I have no idea what your last sentence means, but doubt that it's not already covered by the above.
PS: Trying to make your point with a series of rhetorical questions, mostly repetitive and laced with appeal to emotion, is unhelpful. I have the patience, sometimes, to do a point-by-point to try to answer something like this, but most editors do not and will just ignore posts like that.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  08:57, 5 September 2017 (UTC)
Ok. I will then support a standard, as long as such a standard is not more than a paragraph long. Otherwise, it would definitely be more complex to navigate than is needed. RileyBugz会話投稿記録 20:31, 5 September 2017 (UTC)
I think standardization of church names can only be a good thing. While I agree with most of the above, ENGVAR is definitely a factor and I'd oppose using St. for British churches. My experience on Commons is that without any standard, things end up in a hopeless mess, and imposing a standard shouldn't cause problems.
There are a few other issues around naming of churches: Capitalization (Church or church); Multiple dedications (Ss Peter and Paul or St Peter and St Paul); Variation in Saint name (St Mary or St Mary the Virgin); Repetition (eg St Erth's Church, St Erth)--Nilfanion (talk) 01:28, 4 September 2017 (UTC)

The title of the article is supposed to be the commonly-used form of the name. So "St" or "St." will vary (mostly ENGVAR), some will be Church of Saint James Intercisus, others St James' Church, Arnside. What's important to the reader is to have a clear, comprehensive, clearly-orderered disambiguation page like the one at St. James' Church. I don't care what we call that dab page as long as there are incoming redirects from every reasonably imaginable variation, to gather together all the search terms our readers might use: this looks pretty good, though you may be able to think of additions.

So I'd oppose any guideline which tries to standardise titles of articles for churches (and of course there's the additional minefield of "What is a "church"? Are we talking about the body of people who currently meet in the school hall up the road on Sundays and Tuesdays, or the fragmentary stone remains of the 11th century parish church which has not been used for worship for a couple of centuries but still stands as a listed building?"

And while you're talking about the "unambiguous" standard of "St. X's Church, Somewhere", remember the potential problem of "Somewhere": Plenty of churches are known by their street name, or should it be village/suburb, or nearby town? Stand well away. PamD 08:14, 7 September 2017 (UTC)

Article deletion for TOU violations?[edit]

Do we have a definitive policy statement about deleting articles due to TOU violations? Specifically, undisclosed paid editing. I'm looking at Wikipedia:Articles for deletion/Gene Freidman, attempting to close the discussion. One of the assertions there is, The creator violated our TOU so we should delete the article. This is a common claim at AfDs, but I can't find a definitive policy statement one way or another. The TOU certainly gives us the legal right to Refuse, disable, or restrict access to the contribution of any user who violates these Terms of Use, but that's not the same as it being our policy to do so. I'm not looking for advice on how to close the AfD, just a better understanding of our policies. -- RoySmith (talk) 19:24, 2 September 2017 (UTC)

We don't have such a policy yet. Jo-Jo Eumerus (talk, contributions) 19:52, 2 September 2017 (UTC)
  • I've taken a look and I've read through that AfD again. Wikipedia's general inclusionist philiosophy is sometimes too wildly applied, especially by participants at AfD who may be less faniliar with our guidelines or who may have an axe to grind with other editors in the discussion or the nominator. IMO, in the absence of a local ruling, we should interpret the WMF ToU as being sufficiently broadly construed to delete such content, particularly in the case of a BLP that might technically pass our notability guidelines. It's loss is no grave concern because if it hadn't been paid for contrary to policy, it would not have existed anyway (at that time). That said, I'm in favour of deleting all works by paid undisclosed paid editors but for a very different reason than most people and one that never gets mentioned - but that would be another debate. Kudpung กุดผึ้ง (talk) 22:14, 2 September 2017 (UTC)
    • Tend to agree. If the subject is self-evidently notable, a clean article about them can be created. We don't want to be in a WP:BOGOF loop, where Company A hires Paid Editor B to create some shlock, and the Legit Editors C through Z spend a lot of time trying to fix the bogus article. We should only have the article if the legit editors conclude we need one and it's done right the first time.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  00:02, 4 September 2017 (UTC)
  • TOU is a legal contract between a user and WMF. Its enforcement is responsibility of the parties to this contract - WMF in this case. Other persons have noting to do with it unless they are specifically authorized by WMF. So, in absence of a community policy, TOU is irrelevant to any our internal process. Ruslik_Zero 18:54, 4 September 2017 (UTC)
    Not really. People get blocked for ToU violations all the time, by WP admins, not by WMF attorneys.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  08:10, 5 September 2017 (UTC)
    Many of the ToU are included in our policy; violating those policies is blockable by WP admins, violating the ToU is blockable by the Foundation. עוד מישהו Od Mishehu 20:59, 7 September 2017 (UTC)
    It's this hair-splitting? The short of it appears to be that, yes, people can be blocked for ToU violations. Since Jimbo's backing-away from acting as a "super-admin", all of this seems to be handled by admins anyway, and even in cases where it's not (are there any?), what difference does it make? The end result is the same. If people can be blocked (one way or another) for ToU violations, it would seem to stand to reason that other community actions, like page deletion, can be as well. I do agree that most of the ToU under which that would be common are already also policy-codified, at WP:NOT and elsewhere, but I don't see that any loophole is created, whereby if we've missed a ToU element in the policies, that its somehow fair game to exploit. That's already covered by WP:GAMING and WP:LAWYER.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  04:09, 8 September 2017 (UTC)
  • Local en.Wiki policy can only supersede the WMF terms of use on this matter with a large sitwide RfC adapting a change. We have not done so, therefore removal of content and/or deletion is justified under the TOU unless there is an explicit en.Wiki policy authorizing otherwise. Since there is no special procedure for it, the correct venue for discussions involving clear TOU violations that are not also G5 or G12 eligible is AfD unless the meet any of the other CSD. Until such a point that the local community here authorizes otherwise, undeclared paid editors have as much right to have their content on en.Wiki as copyright violators: both being explicitly disallowed by the TOU. TonyBallioni (talk) 04:34, 8 September 2017 (UTC)
Technically, the TOU doesn't state what needs to be done about paid editors - only that they are required to disclose their connection with clients. In particular, it doesn't make any statement about contributions - paid editors who fail to disclose may suffer sanctions, but the content they add is not banned as such. Traditionally, we've retained the content of paid editors unless it met the criteria of CSD or failed at AFD, and keeping the content is not a specific problem under the TOU. - Bilby (talk) 10:56, 8 September 2017 (UTC)
RoySmoth has pointed out above the passage in question that is applicable. We have the right to remove any content that is in violation of the TOU, and the way we can do that is through the regular deletion process. TonyBallioni (talk) 12:51, 8 September 2017 (UTC)
If the community wishes to delete paid content, the community is welcome to. I just wished to clarify that your statement was misleading when you wrote "undeclared paid editors have as much right to have their content on en.Wiki as copyright violators: both being explicitly disallowed by the TOU", as the TOU does not explicitly disallow content from paid editors. - Bilby (talk) 13:11, 8 September 2017 (UTC)
It does, as they have no right to contribute if they are in violation of them. I don't consider that misleading. TonyBallioni (talk) 13:20, 8 September 2017 (UTC)
Given how the TOU is being stretched recently in regard to paid editing, it is important that we remain accurate in how we describe it. The TOU only mandates that paid editors must disclose - how we manage instances of non disclosure is a choice the community here makes, rather than something directly determined by the TOU. - Bilby (talk) 13:33, 8 September 2017 (UTC)
  • Object example of the day: [3]. Wow! — fortunavelut luna 09:43, 8 September 2017 (UTC)
  • The policy we do have is WP:PAID which implies that the community can create a policy that all PAID-violations are auto-delete cases (which it hasn't done yet). I myself closed a similar AFD as "no consensus" (as Sandstein did in this case). Basically, the point is that we don't have a "fruit of the poisonous tree" policy (yet) and creating one is not what AFD is for. Regards SoWhy 10:16, 8 September 2017 (UTC)
    • The problem is that the policy has no enforcement power. From the points of view of the people making money creating these articles, and their clients, the only effective deterrent is to delete the article. We allow people to make throw-away accounts, so banning is meaningless. If you hire somebody to create a vanity article for yourself, and that person's account d'jour gets banned but the article remains, You're happy. Your paid editor is happy. Everybody is happy but us. So, we need a more effective enforcement tool, and the only one I can see that will work is deleting the article. -- RoySmith (talk) 11:48, 8 September 2017 (UTC)
      • Feel free to propose an actual change to WP:PAID to that effect. Yours might be a sensible argument to achieve this. However, as noted, current policy does not allow this. Regards SoWhy 12:21, 8 September 2017 (UTC)
        • No change is needed: the TOU say that material in violation with them can be removed. Absent an explicit local consensus otherwise, that is the policy. You're right that there is no auto-delete. It is a valid argument at AfD, however, which with PROD is currently our only way to deal with this. Your view that it is not a valid deletion rationale would actually be the change in policy without consensus here. Local en.Wiki policy has not chosen to exempt users from the TOU, because it effectively gets rid of WP:PAID by leaving it with no enforcement mechanism. TonyBallioni (talk) 12:51, 8 September 2017 (UTC)
          • Please quote the section of the ToU that says so. I re-read them and I cannot find any such rule. As far as I can tell, the ToU only contain rules, they lack "punishments". That is for individual projects to decide per ToU #10: "The community has the primary role in creating and enforcing policies applying to the different Project editions." (emphasis added). The ToU explicitly call upon each and every project to create rules how to handle violations of the ToU (which is why Commons or Species for example are allowed to have a policy that does not require paid contributors to identify themselves). Regards SoWhy 14:10, 8 September 2017 (UTC)
            • Sure, section 5 explicitly prohibits undisclosed paid editing, and also requires a positive consensus to allow for a change to that on a local wiki (as Commons and Species have done). Section 10 allows the Foundation to remove or deny access to any contribution in violation of the TOU. It is the primary role of the communities of the local wikis to enforce, as you have pointed out. Prohibitions must have an effective enforcement procedure, otherwise they are not prohibitions, but merely suggestions. Lacking a clear policy to deal with this specific case, we are empowered to enforce the TOU through our standard local procedures, which are blocks and AfD. To argue that lacking a local policy the TOU cannot be enforced is in effect changing the disclosure requirement to be non-existent, which is explicitly prohibited without consensus. en.Wiki has not created an alternative disclosure policy as of yet, so we therefore have our standard enforcement mechanisms in place to deal with violations. TonyBallioni (talk) 15:36, 8 September 2017 (UTC)
              • So you admit that #4 of the ToU does not contain any instructions how to handle such content. The rest is one (imho invalid) interpretation of local policies which explicitly do not cover these edits. WP:BLOCK covers those editors as "disruption only" accounts but it does not say "delete stuff created by those editors after blocking" (neither does WP:BAN incidentally). So if the policies do not allow for deletion of edits by blocked/banned users made before the block/ban, why should it be different for PAID violations? After all, vandalism is against the ToU as well and yet no one would argue to delete all good edits a vandal made just because they were later blocked for vandalism. And neither WP:DEL-REASON nor WP:NOT explicitly list violations of WP:PAID as reasons for deletion. Your POV might be ultimately become widespread consensus but the point is this: Don't try to interpret policies to fit the desired outcome, start an RFC to create a policy that explicitly says so. After all,having it clearly written down one was or another will save us from further discussions like this and doesn't force admins at AFD to judge issues that AFD is clearly not meant for. Regards SoWhy 16:43, 8 September 2017 (UTC)

────────────────────────────────────────────────────────────────────────────────────────────────────It is up to local consensus to determine how to deal with it in each specific case. The POV you are arguing for is essentially trying to circumvent the requirement that local communities must positively adopt an alternative to the disclosure requirements by making the requirements non-enforcable. I also have not said here that current policy allows for speedy deletions of all cases, which seems to be your understanding of what I'm arguing. I think it should, but there is not consensus for that yet. My view is quite simple: where local policy does not have any special procedures for dealing with it, we deal with the articles on a case by case basis through the standard local process, which is AfD. We are allowed to argue global policies and TOU in those discussions, since barring an explicit local consensus, they apply to us. Discounting them has no basis in policy, and is in contradiction of the requirement for an alternate disclosure policy to gain acceptance. You are free to argue at AfDs that we should not delete paid discussions per PRESERVE or WP:N or a policy or guideline of your choice, but arguing form the global TOU is equally valid, and as in all cases where there is a tension in the policies and guidelines, it is up to the closing admin to weight them on their relative strength.

I'd give the same advice to you: don't try to do an end-run on an alternate disclosure policy on en.Wiki, which is what refusal to enforce them is. If you think that we should adopt a Commons style policy, please start the RfC. Otherwise, the TOU control, and we have our standard local means of enforcement to apply. TonyBallioni (talk) 17:00, 8 September 2017 (UTC)

To be honest, deleting content doesn't generally affect the paid editors that we are targeting. By the time we spot and delete the articles, they have generally been paid and have received a positive review. Very occasionally we delete content before the editor is paid, but in most of those cases the editor blames "evil Wikipedians", so the feedback is normally still positive or, at worst, left blank. The problem is that freelance paid editors do not generally have an ongoing relationship with their clients, so problems that emerge after they have been paid don't directly affect them. This is frustrating, as they are generally misleading their clients by not revealing the status on Wikipedia and the additional risks that hiring them entails, making it unethical on multiple levels. - Bilby (talk) 13:20, 8 September 2017 (UTC)
Since you mention reviews, I assume you are referring to freelancers using sites like Upwork. I think it's safe to say that they are a relatively small fraction of the paid editors. The bulk of the market are paid editing companies and PR firms that create Wikipedia pages as an extra service for their clients. Deleting content they add must surely translate into a significant reduction in leads through referrals, and for those at the higher-end, reputational damage. The second reason I favour deletion of such content is that UPEs tend to use various tricks to maximise the probability that their creations will "stick". These include misrepresented or outright falsified references, sometimes to offline sources, which require a large amount of work to check. Since the subjects are almost exclusively non-notable and borderline-notable living persons and organisations, it's an exceptionally bad use of volunteer time. Rentier (talk) 16:21, 8 September 2017 (UTC)
I don't know of any figures as to whether PR firms or freelancers are responsible for most of the paid editing - my guess would be that the freelancers edit more articles, but that the PR firms make more edits on individual articles. However, it is largely moot, because most of the paid editing we detect seems to be from freelancers, in which case deleting is rarely an effective preventative tool. Very occasionally it makes a difference, but as someone who has been deleting the work of paid editors for many years, I've almost never seen it make an impact on their future jobs. - Bilby (talk) 17:38, 8 September 2017 (UTC)
In the absence of reliable figures, all I can offer are a few anecdotes. The Anatha Gulati group doesn't seem to belong to a freelancer -- and its size dwarfs most other UPE sockfarms. I am not aware of any freelancers who handle such volumes. I also don't think the impact on freelancers is negligible. Following the deletion of a number of articles at the end of July, the number of Upwork jobs awarded to BusInCordoba each month dropped from a stable level of 5-8 throughout 2017 to just one in August. I suspect this was caused by their Upwork success rate dropping below the "top rated" threshold of 90%. The success rate can drop without any visible negative feedback as it's based on a private rating given by the clients. It's just one data point (perhaps the person went on vacation), but it suggests that the deletion can have a preventive effect. Admittedly, the impact of similar deletion on Highstakes00 was much smaller, but so was the fraction of identified accounts to the total number inferred from their Upwork history. Still, their success rate dropped by a few points and is no longer perfect. And even for Upwork freelancers, offline referrals by past clients -- which will dry up if the content is deleted -- are an important source of new business. I know because I used to be one. Rentier (talk) 11:14, 9 September 2017 (UTC)
I have a list of over 100 paid editors from Upwork. The only means I've found of having an impact by deleting articles is to do so after they've created the page but before they've been paid. This is a very small window, and only occasionally is it hit. Some seem to make it extremely small, although I suspect that comes from the arrangement they have with their client. In some cases I've even hit that window, only to see them get positive feedback and a comment that "it was out of their control". In cases where it happens too often, the paid editor normally starts a new account - it is a bit of a loss for them, but a bigger hit for us. That may prove to be the case with BusInCordoba's recent drop in work. So yes, we can have an impact in some cases, but deleting doesn't make much of a dent unless we can get the articles at the right time, and that's mostly to do with when we detect them instead of how quickly they are removed. Just tagging at the right time is effective, but the solution for me is in rapid detection, rather than in what we do to the article next. - Bilby (talk) 03:23, 11 September 2017 (UTC)
  • We do allow content from banned users (like with COI editing), if other editors in standing accept responsibility to that content. If the article's content does not fail any policy and another editor is willing to vouch for that and take that responsibility from the banned user, there's no point in deleting the content. --MASEM (t) 13:19, 8 September 2017 (UTC)
  • The Terms of Use state that "If your account or access is blocked or otherwise terminated for any reason, your public contributions will remain publicly available..." So, automatic deletion would itself violate the Terms of Use because the contributions would then no longer remain publically available. You therefore need some other reason to delete besides the ToU violation. Andrew D. (talk) 17:42, 8 September 2017 (UTC)
  • User:Andrew Davidson That wording should be changed from "will" to "may". Common sense (to me) says we're not legally bound to keep ToU violation content publicly available.
  • It would be good to hear from legal department if content given in violation of the ToU is legal for us to licence (i.e. fruit of the poisonous tree / aiding and abetting a civil offence).
  • For borderline notability (which is common), we should just delete all promo, and speedily per DEL#4, DEL#14.
  • For clearly notable, maybe case by case. I've updated this in WP:BOGOF to reflect this, which basically raises the bar for promo, but doesn't drastically change things. Widefox; talk 15:45, 12 September 2017 (UTC)
  • The legal status of all material published by Upwork freelancers without going through OTRS is questionable. All rights to such work are owned by the client. I fail to see how asking a freelancer to post text on Wikipedia implies releasing it under a free license. The clients are generally ignorant of our policies (such as WP:PAID) and it's hard to argue that they are familiar with our licensing requirements. It would be good to hear a professional opinion on this. This is a purely legal question, independent on the attitude one may have regarding the undisclosed paid content. Rentier (talk) 16:27, 12 September 2017 (UTC)
There's the copyright which the contributor always retails anyhow (see WP:C), but the question is... if it's not legal to edit, then (due to legals which I'm guessing at)...can we legally licence it? I would guess from the ToU wording above that the legal line is we can retain and use it. If not, it would have to be deleted anyhow. So (thinking aloud) seems ToU doesn't constrain us, but this should be clarified. Widefox; talk 16:43, 12 September 2017 (UTC)
I think the question Rentier is raising is who retains the copyright for commissioned works: the client or the freelancer or firm. If the client retains it, there is an argument under our copyright policy that we can't host the text without an explicit license from the copyright holder, which the freelancer would be unable to provide. This is an even bigger question for text that is written by a client and given to a freelancer or firm as something to base an article off of. In those cases, the client all but certainly holds the copyright on the text, and its a valid question as to whether or not giving it to someone to post on Wikipedia is the same as licensing it themselves if they were to do it. TonyBallioni (talk) 17:05, 12 September 2017 (UTC)
TonyBallioni, Yes, it's not clear that the editor is the copyright owner, so which of these apply (Licensing of Content (1. a. Text to which you hold the copyright, 2. c. Importing text found elsewhere or that you have co-authored with others needing OTRS). My point is different, more general about whether it's possible to have 7. Licensing of Content agreement at all from a prohibited activity. Widefox; talk 01:55, 13 September 2017 (UTC)
Forgive my naïvety: Is this why we allow paid editors to be OTRS agents? Kudpung กุดผึ้ง (talk) 07:16, 16 September 2017 (UTC)

Reversion[edit]

I don't intend to argue ovver a change I made that was reverted. But surely there must be a place where people can post a formal objection to what they feel is a thoughtless, immproper, and unexplained reversion. It is hard to find if there is such a place. I did make a note on the reverters talk page that he was lowering the quality of the article, although ai did not mention that he was violating policy. ( Martin | talkcontribs 17:24, 4 September 2017 (UTC))

There is such a place and it is called the talk page of the article. Ruslik_Zero 18:13, 4 September 2017 (UTC)
The talk page of the user, though, is the first step. If it seems to be a habitual pattern, try WP:ANI.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  08:09, 5 September 2017 (UTC)

The talk page of the article seems like such a toothless action, as well as pointless. I know one should expect good intentions by all editors, but this route seems so unlikely to be helpful that I just don't care that much, and as a consequence, accept that Wikipedia will be subject to snopes level misinformation. The lie that TEPCO propagated for its own cover is that the grid went down at Fukushima Daiichi. The main article avoids this claim after a long battle, but this is an attempt to re-introduce that claim is a more subtle way, lower down, using the term "blackout", with a link that explains that it can be due to a grid failure. There was a power failure at Fukushima, but not due to grid failure, so the wording and the link are inappropriate. Many obvious proofs, not the least is that Daini, on the same grid, had power. I will post this also on the talk page. Little Good that that will do. I did post an objection on the users talk page, although nothing yet, and I expect little. He made no comment as to his original reversion, even though I explained the edit on the article talk page. Now he has replied - with insults! No point talking to him! Go see for yourself. Talk:Fukushima_Daiichi_nuclear_disaster#loss_of_power_vs_black_out( Martin | talkcontribs 16:15, 5 September 2017 (UTC))

There are also WP:Noticeboards for all the WP:Core content policies. As a very general matter, I don't think raising single-editor issues at article talk pages works very well; it tends to devolve into a he-said-she-said personality conflict that other editors of the article will tire of quickly (bt;dt).  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  04:04, 8 September 2017 (UTC)
Building consensus is slow. WP:DR is a good alternative when there are literally only two editors and the two editors reach an impasse. --Jayron32 16:15, 8 September 2017 (UTC)

A statement from WMF staff about RfC referrer info discussion[edit]

It's been one month after the RfC discussion on referrer info was closed. For notification, one of the WMF staff members posted her statement at Wikipedia talk:Village pump (policy)/RfC: Wikimedia referrer policy about the discussion. --George Ho (talk) 12:10, 9 September 2017 (UTC)

Does/should WP:NOFULLTEXT apply to more than just primary sources?[edit]

The wording of Wikipedia:Do not include the full text of lengthy primary sources is rather confusing. It starts "Wikipedia is not a mirror of public domain or other source material", suggesting that the guideline applies to all sorts of sources, but the title of the page refers to primary sources only. I would be interested to hear opinions on whether the guideline applies to articles such as Science and technology in Turkmenistan, which has been copied in its entirety from a UNESCO report, and if it doesn't, then whether the guideline should be changed so that it does. Cordless Larry (talk) 14:09, 10 September 2017 (UTC)

  • As another data point, we most certainly do have many articles on demography that were copy/pasted from the CIA World Factbook and many articles on American municipalities copied from census databases. There is no problem as such with these and I think the idea that we shouldn't host them is silly. Unless someone has a better alternative, then that is exactly what we should do (consider how difficult it would be to write an article on science and technology in Turkmenistan). Wikipedia is not Wikisource but that shouldn't stop us from using quality public domain sources (e.g. 1911 Encyclopedia Britannica) as the basis of articles. ―Justin (koavf)TCM 17:50, 10 September 2017 (UTC)
Point taken about demographic statistics, but I think my issue is that whereas those involve copying facts and figures in from external sources, the sort of copying going on at Science and technology in Turkmenistan involves importing opinions (such as "President Berdimuhammadov is far more committed to science than his predecessor"). Copying such large portions of a secondary source such as this presents significant NPOV problems, in my view. Cordless Larry (talk) 18:03, 10 September 2017 (UTC)
Sure but the solution is to just change the text. It's in the public domain and no one expects integrity of the original source material (like on Wikisource), so I think we are better off having a copy/pasted public domain article by experts on an obscure topic than having nothing. ―Justin (koavf)TCM 18:06, 10 September 2017 (UTC)
Yep, I agree that the text should be changed, hence my question about whether WP:NOFULLTEXT prescribes this. Cordless Larry (talk) 18:19, 10 September 2017 (UTC)
@Cordless Larry: The direct answer would be no. Moreover, we also need to be very clear: that there is no minimum requirement for changing the text beyond effectively turning into an article, especially when the content is already encyclopedic in nature with features such as being well written, neutral and well researched. Remember, our goal is to create Encyclopedic content. Sadads (talk) 13:09, 11 September 2017 (UTC)
Also, this section of the plagiarism guideline, explicitely welcomes these additions. Sadads (talk) 13:12, 11 September 2017 (UTC)
  • See WP:NOTMIRROR #3, a policy page where the "Wikipedia is not a mirror of public domain or other source material" opening words of the Wikipedia:Do not include the full text of lengthy primary sources guidance seem to have originated from. No, the guideline which, according to its title, only speaks about "primary sources" should not be extended beyond its scope to say also something about non-primary sources: non-primary sources are already covered by policy, and if they need separate treatment in a subsidiary guideline, that would necessarily need to be under a different guideline title. --Francis Schonken (talk) 19:06, 10 September 2017 (UTC)
  • I really don't understand why we would punish or be unhappy with the kinds of additions: expert written content that is reasonably neutral, from sources with a reputation that are reasonably neutral (i.e. UNESCO), is quite commendable. How else can we expect the coverage? Moreover, the bias introduced by the source, if the language and argumentation is sufficiently removed, shouldn't introduce any more bias than an average contributor -- whether new or experienced. We definitely have tons of materials from US GOV sources (including whole articles about military units, NASA-related writing on swaths of space and climate science, etc). We should be encouraging the practice of using open-access content to fill vital content gaps. This feels like favoring rules, rather than the spirit of Wikipedia. Sadads (talk) 12:35, 11 September 2017 (UTC)
    • If it was reasonably neutral, I wouldn't have so much of a problem, Sadads, but Science and technology in Turkmenistan is really UNESCO's view of science and technology in Turkmenistan. I've already highlighted "President Berdimuhammadov is far more committed to science than his predecessor" as an example of unattributed POV above, but there are further problems with other articles created from the same UNESCO report. World Science Day for Peace and Development tells us that "The impact of science on people's daily life and its profound societal implications, including those of an ethical nature, make scientific literacy a prerequisite for effective democratic processes". Scientific mobility presents case studies in the manner of an essay. World Conference on Science is worse still. Science and technology in Benin seems to give policy advice: "By diversifying its economy, Benin would reduce its reliance on fluctuating global market prices for commodities and create jobs for its rapidly growing population". These are just a small number of the many issues caused by copy-pasting in article-length portions of text, which could be avoided if contributors used the sources as we would any other source, rather than copying them word-for-word. Cordless Larry (talk) 13:34, 11 September 2017 (UTC)
      • @Cordless Larry: In general, those articles are reasonably neutral (as opposed to perfectly nuetral) , especially for a relatively new contributor -- its actually of better quality than what we get from most folks with specific background knowledge. I think we need to treat someone doing something like this as if they are learning the practices of our community: we are getting high quality content on topics that would otherwise not be covered. If you notice the less-than-neutral language, you should provide specific feedback, like you would with any other pattern of bias, either by: a) removing the text that is biased or being clearer about the attribution of that opinion (i.e. instead of "By diversifying its economy, Benin would reduce its reliance on fluctuating global market prices for commodities and create jobs for its rapidly growing population" "According to UNESCO, by diversifying its economy, the country of Benin could "reduce its reliance on fluctuating global market prices for commodities and create jobs for its rapidly growing population"); or b) using this as momement where we should be educating the new enthusiastic contributors, with specific and constructive feedback. However, that is no reason to institute additional policy/guidelines by rewriting existing policy/guidelines -- nor to assume that this practice of using open-license text is at the root of the problem -- rather this is a specific directed feedback concern. Sadads (talk) 13:56, 11 September 2017 (UTC)
        • I have been discussing this with the editor concerned and will continue to do so, Sadads. My comments here weren't so much a request for instituting additional guidelines, but rather to get clarification on what this particular guideline covers, as there is some confusion about this (see Talk:Chinese Academy of Sciences#Restoration of reform section). This confusion stems in part from the title addressing primary sources but the introduction possibly suggesting that it applies more widely (which I see you have tried to address here - thanks for that). Cordless Larry (talk) 14:10, 11 September 2017 (UTC)
          • @Cordless Larry:, one of the issues is there is no to very little guidance about transforming text from an external source into the 'voice' of Wikipedia, I've tried to collate some resources and guidance here, in a length that won't cause people to just TL;DR. Do you have any specific suggestions for that? I think using the word bias isn't overly useful as it has such a broad scope. What I'm hearing from you is something like 'attribute any recommendations or points of view to their sources'. Thanks, --John Cummings (talk) 14:27, 11 September 2017 (UTC)
          • Again, the "primary sources" related guideline only covers "primary sources": making it say something outside that scope would not be appropriate under that guideline title. The related policy (WP:NOTMIRROR #3) is however not limited to primary sources. But I'd stop that route (both the "primary sources"-related guideline as the related WP:NOT paragraph). Seems like what you're looking for is the combination of WP:BALASPS with WP:GNG:
            1. If UNESCO is the only possible source for the "science and technology in <country>" topics, these articles should be deleted or merged while not passing WP:GNG
            2. For each of these articles which have more than one reliable source, WP:BALASPS should be applied: see what other sources say and put it together, summarized, under a WP:NPOV umbrella. --Francis Schonken (talk) 15:37, 11 September 2017 (UTC)

──────────────────────────────────────────────────────────────────────────────────────────────────── Is UNESCO a neutral source? Given its makeup, I'm a bit dubious. Who actually wrote the text that was copied into the article? Doug Weller talk 18:21, 12 September 2017 (UTC)

I'm not sure that UNESCO is any less neutral than 1911 Britannica or the CIA World Factbook, say. So while I have some concerns about Science and technology in Turkmenistan they are more about the nature of the content, rather than the fact that material from UNESCO is being added. In my view the article as it stands is overly focused on the present government's policies, and doesn't quite have the tone of an encyclopedia article. That said, those are both things that can be addressed by working on the article. The Land (talk) 19:02, 12 September 2017 (UTC)
They can indeed be addressed, The Land, but Science and technology in Turkmenistan is only one of a number of such articles, and according to this news report, there are plans for more. It would be better to get these articles right from the time of creation, rather than us being left with hundreds of them to clean up. Cordless Larry (talk) 20:28, 12 September 2017 (UTC)
Well sort of - yes it would be nice for people to create only articles that are perfectly referenced and immaculate - but that has never really been the way Wikipedia has worked. I think in this case we need to consider whether the value being added by this initiative exceeds the hassle of any necessary cleanup. To that, I would definitely say yes... after all, we scarcely have any editors already working on topics like science and technology in developing countries, and as a result very little coverage of it. The Land (talk) 09:08, 13 September 2017 (UTC)
I'm not insisting that the articles need to be perfectly referenced and immaculate, just that they follow some of the basic rules of WP:NPOV. Cordless Larry (talk) 11:31, 13 September 2017 (UTC)

Other guidance that may be applicable is WP:COI. John Cummings, in residence at UNESCO, is apparently the main editor importing unedited UNESCO text. We could ask this editor to filter out UNESCO's opinions (such as assessing a president's commitment, speculating about the connection between "scientific literacy" and "democracy" or giving advice to the rulers in Benin), or at least set such opinions in quotation marks with in-text attribution (UNESCO's reports are a *primary source* for UNESCO's opinions, so the primary source-related guidance could come in after all). CIA views imported in Wikipedia by someone in residence at CIA have been rejected by the Wikipedia community before (and drastically removed – if I remember correctly even an IP-rangeblock was applied to prevent further editing from within the CIA's premises). So, I'd suggest to start with such filtering out of UNESCO's opinions ASAP. --Francis Schonken (talk) 12:10, 13 September 2017 (UTC)

What I meant to say with the previous paragraph is that there is a huge difference between a Wikipedia editor importing data from the CIA World Factbook (which was used as a commendable example above), and someone sitting at a desk within a CIA building and updating Wikipedia articles with opinions about the reliability of politicians and regimes from the CIA's viewpoint (which was cleanly and forcefully rejected by Wikipedia editors, being dragged to COI noticeboard and so forth). I'm not saying which one of the two situations is most comparable here, but was a bit alerted by the "in residence at UNESCO". --Francis Schonken (talk) 12:52, 13 September 2017 (UTC)

I think that Susan Schneegans is doing most of the importing, Francis Schonken. According to her user page, she is the editor of the source material is being imported from. Cordless Larry (talk) 12:56, 13 September 2017 (UTC)
Imagine this had been brought up at WP:COIN instead of here where it was connected to the less applicable NOFULLTEXT guidance: by this time John and Susan would probably have been in the phase where they would have been begging to get their user rights back... So I'm happy it was brought up here (COIN can be a bit hit-first-think-later). Nonetheless: John and Susan, please consider the filtering I proposed above (and commit to it explicitly), or this will predictably, almost unavoidably I'd say, be sorted as a COI sooner or later. --Francis Schonken (talk) 13:16, 13 September 2017 (UTC)

Merge discussion: WP:Naming conventions (identity) to WP:Manual of Style#Identity[edit]

FYI: Pointer to relevant discussion elsewhere.

Please see "Wikipedia talk:Manual of Style#Merge draft WP:Naming conventions (identity) to MOS:IDENTITY?", a proposal to merge perennial draft material at WP:Naming conventions (identity) to the WP:Manual of Style in one way or another (probably a section at MOS:BIO), since it is a draft style guideline with almost nothing in it that pertains specifically to article titles (i.e., it is not a naming convention).  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  07:47, 11 September 2017 (UTC)

Wikidata descriptions still used on enwiki[edit]

After Wikipedia:Village pump (proposals)/Archive 138#Rfc: Remove description taken from Wikidata from mobile view of en-WP, the Readin Team from the WMF told us that "we have decided to turn the wikidata descriptions feature off for enwiki for the time being."

This turns out to be untrue: online one specific instance of this (standard mobile view) has been turned off, other mobile views (through the Android app c.s.) and other uses of this Wikidata description on enwiki (search, related articles, ...) have not been turned off. Apparently we should have known that the Reading Team is not responsible for what happens for our readers through other channels like the Android App.

The Wikidata descriptions are short, unsourced descriptions of the subject, which are shown in our articles but don't appear in e.g. the history of the article. You can find changes to it by turning on "Wikidata" in your watchlist options, but this also includes tons of unrelated and/or very cryptic changes in your watchlist. The end result is that very little people actually look at these Wikidata changes and patrol them. Vandalism on these descriptions, which is instantly visible to our readers at enwiki, remains unchecked for hours. Only a handful of people patrol this, meaning that such vandalism often remains for hours or days. I don't blame those people who do patrol this, as they are doing a valuable job; however, as a community, Wikidata is not ready or willing to deal with this adequately.

Examples of vandalism or at least poor such edits from today include Margaret Qualley, called a bitch today for more than four hours[4]; Moulden, Northern Territory, an Australian suburb which suddenly had a terrible crime rate for 10 hours[5], and the nasal cavity, which for thirteen hours was described as Jjhghh[6]; Prince, hardly an obscure, unwatched article, was changed from a "singer" to a "pop" in his description 6 hours ago and not corrected at the time of writing[7].

Other BLP violations (like a Mexican actress who suddenly was labeled a swinger for 7 hours([8]) luckily never made it here because we don't have an article on them yet...

Vandalism also happens here, of course, but at least it is usually spotted and reverted faster, and we can deal with the offending editors (e.g. blocking) or protect the page. Page protection does nothing against changed at Wikidata, and people banned at enwiki are happily editing Wikidata.

Do we really need a new RfC to confirm the very poorly implemented consensus of the previous RfC, or can we just state that the WMF should fully respect the previous RfC and the promise they made there in closing, i.e. remove the use of Wikidata descriptions anywhere on enwiki? @OVasileva (WMF): as the WMF editor who made that commitment. Fram (talk) 14:36, 11 September 2017 (UTC)

Olga has replied to the ping. CKoerner (WMF) (talk) 18:12, 11 September 2017 (UTC)
  • It actually seems better to have a "short description" editable on Wikidata than to automate things (PageImages used to automatically produce an image for a page, something that should have human oversight). While Wikidata editing should be integrated more closely with the client wikis (for example, Popups could help me to view Wikidata diffs in my watchlist; Wikidata edits shouldn't behave differently from others in an "integrated" watchlist), I am also really tired of this anti-Wikidata crusade. The wiki spirit is fixing things, not turning everything off because it doesn't quite work yet. What I am missing, though, is a concerted effort to gain editors for Wikidata (it is not currently a particularly inviting place). —Kusma (t·c) 14:54, 11 September 2017 (UTC)
  • Wikipedia itself has plenty of problems, hence the need to fix. Morphing another project that simultaneously relies on WP and also feeds into it is just madness and, well, circular. That's why I am not surprised if there are indeed people on some sort of crusade against it, just like they crusade against Commons.
FWIW, unticking the Wikidata box on my watchlist doesn't alter what is shown. (Firefox 55.02 on Ubuntu 16.04). - Sitush (talk) 15:04, 11 September 2017 (UTC)
  • (ec)"Fixing things", as suggested at the RfC, would mean creating a cross-wiki template which every language would fill, maintain, ... where needed for their own language, and which would be a part of the actual article, using the actual existing interface (watchlist, undo, block, ...) while producing the same end result in mobile view, searches, ... This (a language-dependent text based on the language-independent Wikidata, combining essentially the worst of both worlds) is not the way forward, and spending time on polishing this turd is not "the wiki spirit" but a desparate attempt to push Wikidata without any concern for what is actually best for our readers and for the editors here. "A concerted effort to gain editors for Wikidata" may be the subject of a different discussion, but doing this by forcing editors to watch and edit two sites instead of one (or three instead of two if you add Commons), where the new one has a different structure, culture, ..., seems not the way to go. Fram (talk) 15:05, 11 September 2017 (UTC)
The stand-alone App has its own development team that is unrelated to the mobile view as I recall, so its unlikely without WMF-top down management getting involved, that anything could be changed on the App end as a result of an RFC here. RE Kusma, it has come up before that Wikipedia would like short descriptions (which are not in themselves a bad idea) to be editable and controlled by Wikipedia, because our policies on verifiability etc, as well as the base editor numbers, mean that a)its less likely to have unspotted vandalism, b)anything that is will be picked up earlier. There is the related issue that the description on wikidata could be in fact sourced and verifiable (from Wikidata's perspective), but be completely out of line with what our policies require. Do you want to guess what will happen if we start deleting information from Wikidata because its causing a BLP violation on a wikipedia article being displayed on Android/iPhone? I am starting to think that essentially we need to migrate enough editors to Wikidata to *enforce* Wikipedia policies on it given the WMF's push to integrate it into everything.
RE Sitush: The comparison with commons is really a different kettle of fish. A lot of the complaints about commons are about the scope of the material contained there, not the useability of the material. Their policies are actually stricter than we allow for on ENWP. So essentially almost anything on Commons is useable in an ENWP article as long as it is in scope. The same cannot be said of Wikidata, because their basic inclusion policies are non-existant. Only in death does duty end (talk) 15:11, 11 September 2017 (UTC)
There is no way you can enforce Wikidata to "*enforce* Wikipedia policies". First of all, you probably mean "English Wikipedia policies". The Wikipedia in a default language is indeed the biggest WMF project but by far not the only one, and I am very happy that the vast majority of Wikidata admins and active users are monolingual. There is no way one project can enforce their policies on another project. Concerning deleting clearly wrong data - well, Wikidata has edit summaries, and as soon as these are used to explain that the data are clearly wrong, I do not see much of a problem and would in fact welcome this activity on Wikidata. Specifically for vandalism, it is much more productive to revert it to the last non-vandalized version, which only requires an extra click, but even just removing it would be a progress. The main problem of Wikidata is that it is severely understaffed, and indeed users who patrol changes just do not have the capacity to track all of them in real time (it currently has 39 thousand items).--Ymblanter (talk) 15:25, 11 September 2017 (UTC)
Yes, Only in death, I am aware that the causes of the pushback are different. But, still, people are pushing back. As it happens, and ignoring the content issues re: "porn" etc, I don't think Commons is particularly good at containing a bad situation - copyright violations are legion. En-WP certainly has problems, and Wikidata has a ton more than both. - Sitush (talk) 23:08, 11 September 2017 (UTC)
Want to bet? 50 more users could have swung the last RFC on Wikidata into having something *approaching* a reliable source/BLP policy. If the complaint is about 'there are not enough people', well if you want more people I am more than happy to rustle up some, but be warned the first goal will be to put in place policies to make wikidata useable on ENWP. I and other editor's don't want to do this because everybody hates canvassing and laying down ultimatums, but wikidata is swiftly heading towards the point where it, as a project, willingly puts acceptable policies in place, or it will be excluded from any relationship with ENWP. Which obviously will put a cramp in the WMF's and the small number of Wikidata user's plans. Only in death does duty end (talk) 16:08, 11 September 2017 (UTC)
You may be sure that as a Wikidata crat I will just cross out the votes which were clearly canvassed, this happened in the past though not so often. But if someone wants to work on Wikidata on a somewhat regular basis, even if this work is just removing statements which are obviously wrong, they are clearly welcome, and their opinions on RfC will clearly be taken into account.--Ymblanter (talk) 16:15, 11 September 2017 (UTC)
(edit conflict) @Only in death, if you rounded up a bunch of en-wiki people who weren't active on Wikidata to try to sway one of their RFCs, it would almost certainly be declared null-and-void and everyone involved blocked. As a thought experiment, what would your reaction be if POTW canvassed a bunch of his friends to set up accounts on en-wiki and vote to abolish WP:BLP or WP:RS? How would the process in the opposite direction be politically or ethically any different? If Wikidata is causing serious problems, the solution is to cut Wikidata loose until they fix the problems of their own volition, not to arrange an invasion by a coalition of en-wiki and commons and try to run it as an occupied territory. ‑ Iridescent 16:15, 11 September 2017 (UTC)
Well quite, which is why I expect the end result that it will be (attempted) cut off entirely. One of the main complaints from the wikidata crowd is that not enough people want to join the project. People (from ENWP) are not actually interested in joining the project because its base aims are off-set from what wikipedians want to do. The fact that the average wikipedian is accustomed to much more rigorous sourcing requirements doesn't seem to trigger the thought at all that they might want similar standards. In answer to your thought experiment, I have no ethical problems with enforcing standards on a project that is currently (through technical means and the WMF's 'enhancements') enforcing its content onto ENWP's articles without the same level of scrutiny. If we are required to have it encroaching into ENWP content, then it should be required to meet the same standards as anything on ENWP. I have no political or ethical problems with that upsetting people whose walled garden gets a bulldozer from the street to make that happen. I would still vastly PREFER to cut it off entirely, but if we have to go through a fucking humongous bitch-fest with the WMF to do so (as per visual editor, superprotect), it will be extremely contentious discussion. The simplest solution would be for Wikidata to adopt stricter standards than all the projects require (thus satisfying every language's requirements) much like commons, but there is little inclination or indication that will happen. Ever. Only in death does duty end (talk) 16:28, 11 September 2017 (UTC)
Why do not you fork Wikipedia then? There will be no WMF, no Wikidata, and, actually, no need to have Wikidata.--Ymblanter (talk) 16:40, 11 September 2017 (UTC)
So your solution to 'ENWP has issues with Wikidata having huge sourcing problems' is not 'fix Wikidata' its 'Fork ENWP so you don't have to deal with Wikidata'. And you wonder why I think the wikidata crowd have no inclination to do anything. Only in death does duty end (talk) 16:44, 11 September 2017 (UTC)
Not really. You just seem to be unhappy with the existence of WMF and existence of Wikidata. You generally do not care a fuck about other projects, except for may be Commons which provide images - but images could also be uploaded locally. However you have no problems with using servers they provide and using the code they have written (you are not a developer, are you)? I would guess just fork and be done with it.--Ymblanter (talk) 16:51, 11 September 2017 (UTC)
By the way, it is of course useful for the sake of the argument to label me as a part of the "Wikidata crowd", however just to note that here, on the English Wikipedia, I happen to have made approximately 15 times more edits that you have.--Ymblanter (talk) 16:53, 11 September 2017 (UTC)
  • AFAIK Wikidata *is* a fork of Wikipedia (from multiple languages' Wikipedias I suppose). At least at en.wikipedia data from Wikidata should not re-enter the encyclopedia per WP:CIRCULAR, which is a policy here. --Francis Schonken (talk) 17:07, 11 September 2017 (UTC)
@Only in death: I think you are probably right that the motivation for (some) Wikidata editors is indeed "off-set from what wikipedians want to do". When I am editing on ENWP, my focus tends to be at the individual article level, with the aim to make that article as clear and accurate as I can: my enemies are inaccuracy and unclarity and punctuation-inside-quotes, and I want to root them out. On the other hand, on Wikidata my key motivation is improving the results that I and others can get from queries, at scale (in part to make possible a project to upload with proper categorisation several tens of thousands of map images to Commons). As part of that I can accept a certain degree of unreliability in the data -- to some extent it's inherent in handling any data at scale, to some extent it's part of being a wiki, to some extent it's simply part of how Wikidata has been built up. Of course I'd like the data to be as good as possible, but what I *need* is "good enough to be usable". For the applications I have, better coverage and completeness may be worth some unreliability -- if I know the data may have some unreliabilities, I can treat it as such, and try to filter or cross-check or improve it. But I can't filter hits from my query if I don't get hits at all. So yes, it can be a different mindset, with a different set of balance of advantage compared to WP when it comes to false-negatives (data that's not there) against false positives (data that's not right). To some extent it can be the perspective of search -- we can accept some bad search hits, but the priority can be making sure we get the good search hits. That's probably reflected in Wikidata's attitude to unsourced data: sourcing is valued; but unsourced data is better than no data at all; and then it can be up to users to decide what level of sourcing they need, depending on their application.
I think there seems to be a panic here, that some seem to have about Wikidata, which in my opinion is overblown. Realistically, data from Wikidata is only going to be visible in a limited number of templates, most of which will have no BLP-type risk at all. Yes, Wikidata is a wiki, it's not 100% reliable; it may even as a project not have reliablity focus as Wikipedia. But fundamentally, from the article perspective, it's just a different place to store some of the data. The key thing is for tools and processes to be able to minimise the practical effect of the data happening to be in a different place -- eg so that changes ping watchlists and vandal-screens as one would want, but don't swamp them. It's also possible to write templates so that changes on Wikidata don't automatically change article text, but merely lead to a discrepancy being pinged, triggering a hidden category that can then be investigated.
On the other hand, for some templates it is far easier to manage the data centrally on Wikidata. Consider for example {{Art UK bio}}. The URLs at Art UK are mostly stable. However, they change unpredictably (without any redirects) if Art UK changes either the name or the birth date or the death date of the painter. So they need to be checked regularly. With the data on Wikidata, I can get the full set of the current links with a query in 30 seconds, which I can then feed to a URL-checking script. But if the data is on Wikipedia, I need to run a scraper over all the template instances, just to get where the templates currently point to. Having found out which URLs are broken, and tracked down new values for them, on Wikidata I can update them simply by cutting and pasting from a spreadsheet to a tool called Quick Statements, which will update the statements on Wikidata and the process is all done in a couple of minutes. But if the data is stored on Wikipedia, I would need to write (and get approved) a bot to update each of those template statements. For a job like this -- a large set of (uncontroversial) external links -- having the data held systematically on Wikidata makes it far easier to manage and to check and to keep correct. As well as meaning every other language Wikipedia also gets its links updated as well. For content like this, central management really does make sense. Jheald (talk) 18:40, 11 September 2017 (UTC)
  • Comment - I have the impression that since descriptions are article as well as language-specific so closely bound to articles, a solution may be to provide an optional template allowing to add those at the top of articles (i.e. {{description|1=...}}). Internally it would not matter how those were processed/cached/displayed/stored (including on wikidata), but the source would remain directly as part of the article and managed/patrolled by the same language-specific project editors... —PaleoNeonate – 16:21, 11 September 2017 (UTC)
  • Comment Short descriptions are something we need for mobile. They need to be stored somewhere. A more productive focus (IMO) for this conversation would be: what is the big deal about those descriptions being stored on Wikidata rather than in a field in some non-visible template here -- can we identify what the issues are, and can we fix them, so that it doesn't matter where the descriptions are held ?
- The most important issue (again, IMO) is whether changes to the descriptions get shown in an efficent and useful way in Watchlists and edit-patrolling tools here. (ie: so that the tools pick up all the changes that are relevant, but without getting swamped by all the changes that are not relevant.)
- A second issue is that many of the current short descriptions on Wikidata may not be very good. (But they are usually better than nothing).
- A small third issue is that sometimes the descriptions contain Wikidata "use notes", that really ought to be separated off to a different field.
Wikidata needs short descriptions anyway -- they're generally just what you may want to be able to return in a query to give a brief description of the item retrieved; they're the basis for disambiguation on Wikidata; and they give Wikidata editors useful brief (< 10 word) orientation of what the item is about. So that's why the descriptions are valuable from the Wikidata side. I would suggest that they are also rather more visible (and accessible at scale) on Wikidata than they would be in blind Wikipedia template fields.
To me it would seem to make a lot of sense for the editing efforts of both communities to be combined to refine a single set of descriptions, rather than quality being lost by efforts being diffused. As I said, I don't see why it should matter where the data is stored, so long as the tools are aware of it, and it can be properly policed. Am I seeing this correctly, or is there something I have missed? Jheald (talk) 16:56, 11 September 2017 (UTC)
FYI, we had invisible templates before Wikidata existed (can't remember their name currently). After giving Wikidata the opportunity to harvest these invisible data, the invisible mainspace content was systematically removed (after a slow and somewhat painful process of finding consensus on how to do that). --Francis Schonken (talk) 17:07, 11 September 2017 (UTC)
WP:Persondata is the only one I know of which was invisible. --Izno (talk) 17:14, 11 September 2017 (UTC)
Yeah, that's the one I had in mind. --Francis Schonken (talk) 17:17, 11 September 2017 (UTC)
Jheald, I think what you're missing is that there appears to be little interest from most enwiki editors in engaging with Wikidata as you describe. It's probably true that if a large number of enwiki editors began editing Wikidata enthusiastically, many problems would go away. The learning curve for Wikidata is slow to climb, however, and I suspect many content editors here don't want to do what feels like gnomery. I'm an IT professional and have no problem with the complexity, but I want to write articles. I don't want to keep an eye on a database to make sure the articles I write don't get messed up -- or if I do have to keep an eye on it, I don't want to go to another website to do so. One watchlist is plenty (and turning on Wikidata in one's watchlist is unfortunately not very helpful). I see little likelihood of the WD editing community growing to a size that would resolve this, nor of the editing environment becoming integrated between the two. Without one or the other of those, I don't see this conflict being resolved. Mike Christie (talk - contribs - library) 17:23, 11 September 2017 (UTC)
@Mike Christie: Good point, Mike, but then this is what some of what is proposed (that seems to be making people come out with the torches and pitchforks) is actually supposed to make easier -- so, an edit box so that people can edit "short descriptions" without leaving Android; a facility to make editing possible through templates, so that people can fix facts without ever having to go to Wikidata, without leaving Wikipedia.
To me, the key issue that I think most needs to be fixed is getting the Watchlist (and vandal-fighting) integration much much better. What I think would make all the difference is to be able to see any change that alters the output HTML of a page -- and not to see any change that doesn't. And for the page-history by default to show any edits that changed the output HTML -- whether the data was changed through a Wikipedia edit or a Wikidata edit -- without showing changes that eg only affect other languages, or indeed no wikis at all. And for the line in the history to have an "undo" button, that undoes the change, regardless of where it was made. And for anti-vandal tools to be similarly agnostic as to whether the data happens to be stored here or happens to be stored on WD.
I think WD will be more accepted when for practical purposes it no longer matters whether the data happens to be stored here, or happens to be stored on WD. I think it's been clear for at least 18 months that this was a major issue that needed to be a priority area for development. I hope that, going forward, it now will be. Jheald (talk) 18:19, 11 September 2017 (UTC)
Jheald: I agree that those things are probably prequisties for people to stop caring about this issue; there are probably more, though. I suggested here a list of issues that would have to be resolved, drawn from the discussions on that page. I'm undecided on several of those issues. One I think is very important is having a unified, clear, comprehensible watchlist. Without that it seems to be too hard to keep an eye on what's going on with the articles one watches. Mike Christie (talk - contribs - library) 18:54, 11 September 2017 (UTC)
It will probably never be resolved. It is unfortunate though that people do not see obvious things. Wikidata was originally created not to provide descriptions for Android. The two immediate goals were (i) to centralize interwiki links (ii) to centralize some sorts of info. For example, we have a lot of information here, on the English Wikipedia, about mayors of obscure Ukrainian towns. This info is typically unsourced and is almost always outdated. Nobody here has issues with it. However, on Ukrainian Wikipedia this info is up-to-date and sources to (unsuprisingly) Ukrainian language sources. There is nobody here who updates the English Wikipedia info on a regular basis, but Wikidata is updated, and often has sourced statements. And this is exactly why it was created. However, an idea that this info can be propagated further to the English Wikipedia meets almost universal opposition, because Wikidata has a different verifiability standard. And, not suprisingly, nobody cares about what data we have here.--Ymblanter (talk) 17:34, 11 September 2017 (UTC)
Re. "...not suprisingly, nobody cares about what data we have here" – maybe, as a first step, stop insulting the people you'd rather be trying to charm. For the mayor of an obscure Ukrainian town I think readers should rather go to Wikidata (knowing they're not on en.Wikipedia any more), than being presented, in en.Wikipedia, some data of unclear origin with little or no possibility to subject to a normal WP:VERIFIABILITY vetting. --Francis Schonken (talk) 18:14, 11 September 2017 (UTC)
(By your logic, I am insulting myself). The data on Ukrainian mayors is in the English Wikipedia, and is of very poor quality. Check Kropyvnytskyi as a typical example: the mayor in the infobox is unsourced, it has never been sourced as far as I can see, and I see no mechanism how this one would be replaced with the next one when he retires or does not get reelected. Indeed, this is clearly contrary to our verifiability policy and even WP:BLP (may be the person is offended to be called mayor), but nobody hurries to enforce these policies. Wikidata btw does not have a mayor for this city, and in this sense it is better verifiable than the English Wikipedia.--Ymblanter (talk) 18:22, 11 September 2017 (UTC)
So your example is just a red herring. You don't seem to care about the mayor of that town, nor here, nor at Wikidata. In sum: charm = zero for trying to illustrate convincingly this would somehow necessitate Wikidata to override the WP:CIRCULAR policy. --Francis Schonken (talk) 19:44, 11 September 2017 (UTC)
To be honest, I do not see any connection between you write and what I write, and I do not feel like trying to convince people who already have a strong opinion on the subject. I suggest we stop the discussion here. He that hath ears to hear, let him hear.--Ymblanter (talk) 19:52, 11 September 2017 (UTC)
I would love to see more data stored centrally (say, on Wikidata) so it can be easily updated on all Wikipedias, and everywhere that some data is used. When a city's mayor or population changes, wouldn't it be nice not to have to find all of the lists that mention this and manually edit all of these pages? (The German Wikipedia solves the population problem by an elaborate and somewhat confusing system of templates; instead of duplicating effort/templates, maybe we could do that centrally?) The main problem is I don't know how to use Wikidata for this, and barely understand its function for interwikis (finally found out today that there is an interwiki problem resolving mechanism, which is backlogged for a rather unflattering couple of years). Is there a tutorial somewhere? c:File:An Ambitious Wikidata Tutorial.pdf isn't one that tells me what to do (other than to build Wikidata without immediate benefit to Wikipedia). The explanation on Wikidata, d:Wikidata:Introduction, tells me I can access the data using a "Lua Scribunto interface", which is linked to mw:Extension:Wikibase Client/Lua, a page that mainly tells me I am not part of the intended audience. There seems to be room for improvement. —Kusma (t·c) 20:10, 11 September 2017 (UTC)
I am also not a tech wizard, but I think it can be done reasonably painlessly, and even with control over the sources which Wikidata uses for such statements. If there is consensus that this information can be used here (either shown directly via templates, or transferred by bots on a regular basis), one can ask on Wikidata how it could be implemented.--Ymblanter (talk) 20:26, 11 September 2017 (UTC)

One major weakness I find with Wikidata is that there is no clearly marked place for newbies or non-technical folks to ask questions. One issue I've been wanting to bring up there is the fact that the office of Roman consul is almost always occupied by two people, however the data object for it over there does not allow me to intuitively indicate colleagues of consuls. Although there appears to be something similar to the Village Pump over there ("Project chat"), lurking there leaves me the impression it is the domain of techies talking to other techies; much like reading a mailing list on Open Stack for the first time. Also I know from experience techies can be very dismissive about newbies' questions. (And I don't want to explain a thousand years of Roman history in a few paragraphs in order to prove I know what I'm talking about in order to learn how to add a freaking field.)

I'm not bashing Wikidata, mind you. I can see the potential it has for Wikipedia. It's that considering it as a project, it's still very user unfriendly -- unless you are one of the people who are deeply into it, & willing to figure out all of its bits & pieces. (It took me a week to figure out how to add the information that a given fact came from en.wikipedia. And I've spent the last 20 years making a living working with computers -- I can only wonder how daunting it could be for someone not technically inclined?) -- llywrch (talk) 22:16, 11 September 2017 (UTC)

@Llywrch: On the consul point, it looks like Wikidata could use a new qualifier property, "held office with", that could be attached to the statement "position held:" "consul", "start time:" "date", "end time: date".
Wikidata is still quite a young project, and one of its characteristics is the ability to quite easily extend the data model in this way, to capture relationships which are not yet modelled well. So ultimately what one would do would be propose something like "held office with" as a new property to add, at d:Wikidata:Property proposal/Organization. The proposal would then be open for discussion, as to whether this is indeed the best way to capture the relationship, or whether there's a better way or something else could be re-purposed or whether a slightly different approach might be more general or flexible. But if nobody raises any counter-suggestions, usually a new property like this would be approved in a couple of weeks, and then data could start being loaded.
That's the formal procedure for proposing a new property (like an RfC); but of course it makes perfect sense to see what people think more generally first in a less formal way, by first raising the issue at eg d:Wikidata:Project Chat or d:Wikidata talk:EveryPolitician or d:Wikidata talk:WikiProject Heads of state and government. Yes, much of the discussion on any of those pages can often get quite technical, with people thrashing out the detail of quite fine points of how to model things. It's a fair point that Wikidata needs better support for new editors, and perhaps an equivalent of en-wiki's WP:Teahouse. But there's a lot of good will, with editors committed to helping other editors solve problems and improve the data -- if somebody wants to know how to do something on Wikidata, or how to model some relationship, they will get taken seriously, and people will do their best to help. Jheald (talk) 09:30, 12 September 2017 (UTC)
@Llywrch: I've opened a discussion on how to best indicate the other(s) of a set of joint office holders at d:Wikidata_talk:EveryPolitician#Joint_office_holders Jheald (talk) 21:48, 12 September 2017 (UTC)
@Llywrch: So it turns out that there is already a Wikidata property used for this, d:Property:P1706 ("together with"). The data is still rather under-populated, but here's a query to show the consuls for whom there is currently another consul specified: tinyurl.com/ybhqb7ep (hit the big blue button at the mid-left to run). You may want to kill the "query helper" bit of the code display, which isn't very helpful. Apologies for the over-precision in the date shown - this is a known issue with the query service which it's tricky to make combine data held in two different fields (date, date-precision) in its output. Remove the '#' (= comment) signs around the "OPTIONAL" bracket at start of lines 8 and 10 to get the full list of people currently recorded on Wikidata as having been a consul. Or click on any of the Q-numbers in the first results column to see how the data for the person has been entered on Wikidata. Hope this helps! Jheald (talk) 09:27, 13 September 2017 (UTC)
According to a considerable group of Wikimedians, complex interfaces are a great way to proof a user's 'competence', because it shows that people are really very committed to participating and have moderate intelligence. So it's probably a feature Wikidata considered worth copying from their predecessors. I'll leave it up to you to decide how this reflects on you and/or that line of reasoning... :) —TheDJ (talkcontribs) 22:46, 11 September 2017 (UTC)
According to my notifications, I've made a shed-load of edits to Wikidata when, to my own knowledge, I've made none at all. That perhaps is something to do with the WMF legals and attribution but it is confusing and not appreciated. - Sitush (talk) 23:11, 11 September 2017 (UTC)

RfC: exceptions to WP:CIRCULAR allowable for Wikidata?[edit]

Malformed RfC.There seems to be valid problems with the framing, scope et al.Winged Blades Godric 03:22, 12 September 2017 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Should an exception be inscribed in WP:CIRCULAR (and/or other parts of the WP:VERIFIABILITY policy), and/or in the WP:RS guidance, that would allow Wikidata information, which may have originated from en.Wikipedia, from a Wikipedia in another language, or may be user-generated at the Wikidata website itself, to be (re)inserted in en.Wikipedia? And if so, at what level and/or under which conditions?--Francis Schonken (talk) 20:09, 11 September 2017 (UTC)

Discussion[edit]

  • No, not under any guise or format. --Francis Schonken (talk) 20:09, 11 September 2017 (UTC)
  • I see no reason to treat Wikidata differently from Wikipedia: we copy information all the time (just like when we translate articles from other Wikipedias), but we use external reliable sources for verification. We should encourage sourced content to be copied between wikis, and discourage unsourced content being copied. —Kusma (t·c) 20:16, 11 September 2017 (UTC)
  • Comment This is a badly formulated RfC by a biased user. Obviously Wikidata should not be treated any differently from other WMF projects. However nobody ever suggested to use it to overcome WP:CIRCULAR. As far as I know nobody reinserts unsourced user-generated content into Wikipedia, and this is not a real issue. The real issue is what Wikidata content can be actually used in Wikipedia and what are the best practices to use it. This RfC does not attempt to answer this issue.--Ymblanter (talk) 20:21, 11 September 2017 (UTC)
  • Comment. I'd suggest withdrawing this. Wikidata is sufficiently contentious that launching an RfC without prior discussion is likely to be unproductive; and the community only has patience for so many RfCs on the topic -- we should agree what the key issue is before starting an RfC. Mike Christie (talk - contribs - library) 22:35, 11 September 2017 (UTC)
  • Comment - malformed RfC. You may get comments but you won't get results. - Sitush (talk) 23:13, 11 September 2017 (UTC)
The above discussion is preserved as an archive of the debate. Please do not modify it. Subsequent comments should be made on the appropriate discussion page (such as the article's talk page or in a deletion review). No further edits should be made to this page.

RfC: Description field from Wikidata in any view of en-WP[edit]

pulled for now. May re-open if the response goes sideways. Jytdog (talk) 05:48, 12 September 2017 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Re-stating this RfC from March of this year, which asked Do you support the following statement: "The description taken from Wikidata that is currently being loaded in mobile views of en-WP pages, must be immediately removed from mobile views of en-WP pages".

The WMF were at that time including the description field from Wikidata in other views of en-WP content (the Android and iOS apps, at least), and continued to do so after the RfC closed.

Do you support the following statements:

  1. The description taken from Wikidata that is currently being added to any mode of viewing en-WP pages and that is published by WMF, including the Android and iOS apps and the mobile view, must be immediately removed and must not be restored without obtaining prior consent of the en-WP community via an RfC here at VPP.
  2. The staff of WMF who continued publishing the Wikidata description field in the apps after the March RfC had been closed, have ignored the clear sense of the en-WP community that there were governance problems with their deciding to do this, and serious issues with violations of en-WP's BLP and Verify policies being published in a way that made them appear to be en-WP content, produced by the en-WP community.
  3. The staff of the WMF responsible for the continued publishing of the Wikidata description field in views of en-WP content in the android and iOS apps and any other views of en-WP content after the March RfC closed, are hereby banned from en-WP, with a standard six month offer. (we can figure out who that is, exactly, if this is "yes") Jytdog (talk) 00:40, 12 September 2017 (UTC)

!votes (description field RfC)[edit]

  • Yes to all three. See below. Jytdog (talk) 00:41, 12 September 2017 (UTC)

Discussion (description field RfC)[edit]

  • The principles that we stated in the March RfC obviously generalize to any view of en-WP content. That apparently needs to be made explicit.
I don't know who the individual(s) is/are who made the decision to ignore the March RfC with regard to the views on the apps (and any other views of en-WP content). I imagine others can identify them easily. But in my view, individuals who so blatantly ignore the consensus of this community have no place in this community, as long as they continue to violate WP:CONSENSUS, WP:BLP, and WP:V this way, and as long as they continue to act as though the WMF's role is to make decisions about content. Jytdog (talk) 00:53, 12 September 2017 (UTC)
It appears that it was a misunderstanding. Ovasileva's explanation seems plausible to me. Since they have already said they are planning to make an additional response, I would suggest waiting for that as point 1 of this RfC may be unnecessary depending on that response. I think your points 2 and 3 should be separated from any RfC on Wikidata in any case, even if you don't believe OVasileva's statement. I'd add that I think banning is a sufficiently major penalty that we should not hold an RfC to ban someone that says we'll figure out later who it is we're going to ban. Mike Christie (talk - contribs - library) 01:30, 12 September 2017 (UTC)
The reasons en-WP people reacted as they did, were stated very clearly in their responses in the RfC. Please do read it. The BLP and V issues are made clear, as are the governance issues.
I cannot begin to understand how anybody actually reading what the community said in the RfC, and understanding it, could read it so narrowly as to apply only to mobile. The persistence in the apps, is either a blow off, or incompetence, as the issues are exactly the same. We ban people who severely harm content for either reason.
Opening up that incompetence thing a little - people who are given authority are trusted to know what they know and don't know, and to be sensitive to what they don't know that they don't know. If anything was unclear about the fundamental issues identified in the RfC, that should have led them to start a conversation to learn about them.
I don't know everything the WMF is doing with content. I am now aware that there is mobile, android app, and iOS app. I have no idea if there are more. I am uninterested in playing whack-a-mole. That is crazy, really.
They should not have been playing mixmaster with content anyway, and their lack of understanding of the problems it causes just underlines that.
This whole RfC is meant to put a very very bright line around that.
I made the points separate so they would be !voted on separately. Do as you will. Jytdog (talk) 03:57, 12 September 2017 (UTC)
Jytdog, I am more than happy to help if necessary. However I request you withdraw this RFC for the moment. I would like to see what response we get from the WMF at WT:Wikidata/2017_State_of_affairs#Wikidata_article_descriptions. Parts of the WMF are as bad as ever, but some people there really are trying to do better. I agree their partial removal of descriptions was nonsensical, but it is possible they had tunnel vision. There's at least a chance that they'll be willing to clean it up amicably. We can ramp up the issue if we don't get a reasonable response soon. Alsee (talk) 04:53, 12 September 2017 (UTC)
OK, willing to pause this for now. Jytdog (talk) 05:48, 12 September 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.

Further conversation[edit]

There's a response and follow up conversation to this topic happening at Wikipedia_talk:Wikidata/2017_State_of_affairs CKoerner (WMF) (talk) 13:08, 14 September 2017 (UTC)

Notice of Discussion at Wikipedia talk:Manual of Style/Capital letters[edit]

There is an RFC about the capitalization of formal titles such as "Duke" and "King" (essentially, the question is when to capitalize and when to use lower case) that could use input from the broader community (I have already posted a request at the the peerage and baronage Wikiproject). Please see: WT:MOSCAPS#RfC on capitalization of job titles. Blueboar (talk) 14:41, 12 September 2017 (UTC)

RFC: "Exemption from WP:V" at Wikiproject Days of the year[edit]

There is a discussion underway at Wikiproject:Days of the year regarding whether to require direct sourcing per WP:BURDEN. At least one editor thought that a notice should be posted here to ensure we get broad consensus. Toddst1 (talk) 17:25, 13 September 2017 (UTC)

ACTRIAL Live[edit]

So that everyone here know WP:ACTRIAL just became active a few hours ago. It is scheduled to run for 6 months, followed by a month off, and then a community discussion to decide how to deal with new content created by new users moving forward. TonyBallioni (talk) 23:46, 14 September 2017 (UTC)

  • I supported the ACTRIAL years ago, and thereafter read some of the discussion from the developers.  Thank you for the good news.  Unscintillating (talk) 22:14, 16 September 2017 (UTC)
Here's to that. Even in my state of burnout, I enthusiastically applaud this move. The Blade of the Northern Lights (話して下さい) 01:38, 17 September 2017 (UTC)

Meta RFC on change to paid editing policy[edit]

Just a quick note, as this will have implications here. There is currently an RfC on Meta which will require paid editors to provide links from user pages to off-wiki details if they wish to edit. It may be of interest. - Bilby (talk) 04:47, 16 September 2017 (UTC)

Interesting detail on that page. Most of the oppose !votes have emojis bit none of the support !votes do. I wonder why? --Guy Macon (talk) 14:19, 16 September 2017 (UTC)
en.Wiki vs. meta practice. Most of the !voters there probably aren't that active on meta so they just followed our practice. TonyBallioni (talk) 14:28, 16 September 2017 (UTC)
But why would the support !voters be mostly people not active on meta while the oppose !voters are mostly people who are active on meta? Not that it matters, but I am curious.
On a more serious note, would it be worthwhile to see how many !votes are from SPAs? Paid editors might be motivated to stack the votes... --Guy Macon (talk) 14:48, 16 September 2017 (UTC)

Removal of speedy deletion tags by non-admins[edit]

I know it's only been a day but I think we can close this per WP:SNOW. It's clear that this proposal, certainly made in good faith, will not gain consensus because of the reasons mentioned in length by multiple users, especially, but not limited to, the fact that once anyone, admin or not, disagrees with a tagging in good faith, speedy deletion no longer is appropriate. Regards SoWhy 20:09, 17 September 2017 (UTC)
The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

TL;DR: only allow administrators to remove CSD tags except for nominator withdrawals or blatant bad-faith nominations.

Hello all,

I've recently had a few speedy deletion tags that I've put on articles removed by non-admins who aren't the page creator. The large majority of these have had to be prodded or taken to AfD with many of the !voters concurring with the deletion per CSD. The most recent case was on Wrong time where a completely invalid rationale for reverting was given by a particular user, who it would do me no good to mention by name, and I re-instated the CSD tag and left a note with an extended rationale on their talk page. An uninvolved administrator has since deleted the page under the speedy deletion criteria which I nominated it on.

The current CSD policy is unclear and only mentions removal by non-admins in passing when referring to the already-banned practice of page creators removing CSD tags.

My proposal is that the CSD policy should be changed to note that only administrators can decline speedy deletions except in cases of self-reverts by the nominator or blatant bad-faith nominations, for example this.

Thanks,

DrStrauss talk 21:30, 16 September 2017 (UTC)

  • This seems reasonable, since a CSD tag is supposed to bring a page to the attention of an administrator, it seems counterproductive to remove them before this happens. (unless of course it is a bad faith nomination). Either way, this needs to be clarified. Α Guy into Books § (Message) -  21:36, 16 September 2017 (UTC)
  • Oppose Speedy deletion is for uncontroversial deletions only. The proposal would mean that all non-admins who oppose deletion need to contest the speedy deletion nomination in the same way that the creator of the page needs to contest the speedy deletion. A speedy nomination that is contested is by definition controversial, and will be declined. If you're looking for a better way to detect bad faith removals of speedy deletion nominations, this is not it. Mduvekot (talk) 21:59, 16 September 2017 (UTC)
  • Oppose there are good reasons that good faith contributors who are not admins can remove a CSD tag from an article. I've saved several articles that others have hastily tagged during NPP from deletion, and the majority of them are from non-Anglophone regions. I fear this exact proposal would increase systemic bias on Wikipedia by making it easier to delete needed articles in non-Anglophone majority regions, and would be a net negative on the content front, which is the most important part of the encyclopedia (its why we are all here).
    That being said, there is at least one user who is on a de facto topic ban from removing CSD tags(this user agreed to stop removing tags because the other option was WP:AN to get a formal topic ban). There is a rough consensus in the community. If a non-admin is disruptively removing tags in a way that is causing more work for other users in a way that is seen by the community as harming Wikipedia, we have a means to stop it: a topic ban discussion at WP:AN (not ANI). To my knowledge this has really only been an issue with one or two specific users, and we've managed to avert formal sanctions. If a user keeps disruptively removing CSD tags, discuss it with them, and if there is a general consensus amongst users who are active at NPP or AfD that their actions are harmful, take it to AN. This allows Wikipedia to grow while having an option to prevent disruption in certain cases. TonyBallioni (talk) 22:04, 16 September 2017 (UTC)
  • Oppose - at first blush a reasonable suggestion, but actually a solution looking for a problem. Kudpung กุดผึ้ง (talk) 22:24, 16 September 2017 (UTC)
  • Oppose when someone A7s a book, I expect the first patroller who knows better to revert the CSD tag, even if they are not an administrator. Patrollers make mistakes, administration shouldn't have sole responibility for cleaning those mistakes up. — InsertCleverPhraseHere (or here) 22:37, 16 September 2017 (UTC)
  • Oppose--Per Tony.Winged Blades Godric 02:59, 17 September 2017 (UTC)
  • Oppose - per what everyone's already said here. Ivanvector (Talk/Edits) 03:02, 17 September 2017 (UTC)
  • Oppose It is an absurd idea that "good faith" mistakes made in CSD nominations are always spotted by a deleting admin. List of fictional characters with disabilities was in main space when nominated for WP:G13[9] (only applicable for draft and user space) and was then speedy deleted.[10] Our deletion procedures can be careless and it requires careful editors to prevent bad deletions. Thincat (talk) 14:56, 17 September 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: Should the WP:TALK guideline discourage interleaving?[edit]

Opinions are needed on the following matter: Wikipedia talk:Talk page guidelines#RfC: Should the guideline discourage interleaving?. A permalink for it is here. Flyer22 Reborn (talk) 02:16, 19 September 2017 (UTC)

Proposal regarding WP:OR and terrorism[edit]

Problem:

  • Terrorism-related pages, especially lists of terrorist events, are plagued by original research and synthesis by editors. On list pages, often list entries are made where the source does not support the label of "terrorism" (recent examples: [11], [12], [13], [14], [15]). Other times, the mere mention that ISIL, Al Shabab, or the PKK are suspected appears to prompt editors to add events to the lists, even if terrorism isn't mentioned (e.g., [16], [17]). The issue here is the assumption that all acts by these groups are, by default, terrorism and not some other form of violence such as insurgency, guerrilla tactics, etc. This assumption, while perhaps often correct, still constitutes original research as it is the editor making the connection, not the sources. Currently, the lists of terrorism incidents address this latter issue by including "attacks by violent non-state actors for political, religious, or ideological motive".
  • Related, articles about events often are labeled "terrorism" without proper sourcing or prematurely. This prompted EvergreenFir to make WP:HOLDYOURHORSES because breaking news and first responders too often mislabel events in the initial aftermath. The mere rumor of someone hearing Allahu Akbar sends news reporters and editors into terrorism-labeling mode long before such information is verified by investigators. Examples are the initial reporting on 2011 Norway attacks and 2016 Munich shooting.

Possible solutions:

  • Address this issue by amending WP:OR to require:
  1. Reliable sources explicitly label an event or related individuals as "terrorism" or "terrorist" in their own voice or that Reliable sources report that some official related to the investigation of the event (e.g., mayor, police chief, government spokesperson) has used the label "terrorism" or "terrorist".
  2. Cases where terrorism is "suspected" should be labeled as "suspected" by Wikipedia as well until this suspicion is officially confirmed or denied.
  • A guideline be set regarding the lumping of "attacks by violent non-state actors for political, religious, or ideological motive" into terrorism-related articles and lists

Comments: We understand that carving out a specific topic for special attention in policy pages is undesirable to some editors. However, we believe this deserves special attention because of (1) the seriousness of the label "terrorist", (2) the persistence of the problem across multiple articles, and (3) the contentiousness of the topic vis-a-vis politics and religion. We already have discretionary and general sanctions related to this area (WP:ARB911, WP:ARBAP2, WP:TROUBLES, WP:ARBPIA, WP:GS/ISIL), demonstrating it is a perennial topic for disputes. As such we believe that this broad topic warrants specific attention by Wikipedia policy. The goal of this proposal is to provide clarity to editors and to establish a community norm regarding the application of the label "terrorism".

Signed, EvergreenFir and Doug Weller; Posted by EvergreenFir (talk) 02:01, 20 September 2017 (UTC)

Discussion - terrorism[edit]

Before consideration of any formal proposal occurs, I think this needs input and wordsmithing by folks. I'm open to suggestions as to where any such language should go (perhaps a guideline, add to WP:OR, or some other place I've not thought of). Should some consensus emerge, a formal proposal would be the next step I think.

I'm curious if people share my concerns about the automatic inclusion of any acts by "violent non-state actors". Currently, executions by ISIL are included on these lists. I'm personally on the fence about this, but if folks felt strongly one way or another, I think that's fine as long as we can clarify the position. EvergreenFir (talk) 02:01, 20 September 2017 (UTC)

I do have concerns that very frequently, right after an event like a bombing, that we do get reports "police are treating this as a terrorist event", which does not necessarily mean that the event will prove out to be terrorism-related (and we need to presume that "terrorism" without context means international terrorism as opposed to domestic terrorism). When law enforcement uses that language in the short-term and hours after the event, that means they gain special powers to quickly deal with the matter (eg [18]) but that should not mean to us that the event is a terrorism-related event. Calling something a terrorist event can only happen after arrests have been made or perps identified and their motives figured out, and far too often the media jump the gun on this. We shouldnt be trying to classify these events as terrorism for at least a day after the event and no earlier than until suspects are determined and preliminary motives worked out. --MASEM (t) 06:11, 20 September 2017 (UTC)
Hmmm. We call Juggalos terrorists at Juggalo gangs with citations to US government documents. Falun Gong is listed as a terrorist group by the Chinese government, but we don't mention this in their article (but we do quote someone accusing China of being practitioners as state terrorism because of how they have reacted to Falun Gong.) So if a government calls a group a terrorist group, do we include that information? If other governments disagree (as they do in the case of Falun Gong), do we include that? --Guy Macon (talk) 06:13, 20 September 2017 (UTC)
@Guy Macon and Masem: I agree with both of you. Guy Macon, you make a good point. Who gets to define a group as terrorist? Perhaps we need to leave it to just the sources, independent of the labels used by government officials and law enforcement? But that would mean the sources needs to use it in their own voice, not just quote someone. Or leave it to a third party like an NGO? EvergreenFir (talk) 06:37, 20 September 2017 (UTC)
Guy Macon We call Juggalos gangs criminal street gangs, not terrorists, and there's a bit there that looks like a BLP violation as it says someone was arrested for allegedly forming a terrorist group, but see this and this. So we have a paragraph in the article that makes it look as though there was a terrorist plot, but there was no such plot. This looks like an example of the problem. As for who, the Myanmar issue is interesting. Are all the people the government is calling terrorist actually terroists?[19] I don't know. Doug Weller talk 18:37, 20 September 2017 (UTC)
As Doug Weller noted above, he removed one of the places where we call (some) Juggalos terrorists[20] (good call on the removal, BTW) before claiming that "we call Juggalos gangs criminal street gangs, not terrorists". Yet the Juggalo gangs article still says "The other 10–15% make up the Juggalo subculture's criminal element, which has been linked to numerous crimes including extortion, murder, domestic terrorism, drive-by shootings, drug trafficking, arson, burglary, armed robbery, aggravated assault, and weapon offenses, and has been documented collaborating with a wide array of street and prison gangs" (Emphasis added). I just looked at the citations for that claim and could not find anything supporting either the "terrorism" claim or the 10–15% estimate. We need rock solid citations before claiming that 150,000 people are terrorists. --Guy Macon (talk) 21:32, 20 September 2017 (UTC)
If there is any place for this (or further need for it), it is not WP:OR but rather WP:BLPCRIME. Ultimately, what is said about some act of terrorism needs to pass that bar. If people are engaging in WP:OR, point them to that particular policy, remove or reword the offending material, and move on. --Izno (talk) 11:21, 20 September 2017 (UTC)
@Izno: BLPCRIME seems like a good place for cases of individual "terrorists". I think Doug Weller and I were suggesting something more broad because this is a perennial and frankly intractable issue. But perhaps specifying for individuals and pointing to OR in that specification would be enough. Doug might be able to explain the admin side more. EvergreenFir (talk) 18:05, 20 September 2017 (UTC)
I have a problem with relying on law enforcement sources when calling a group terrorists and especially with relying on law enforcement estimates for how many people are in the group. Law enforcement has every reason to exaggerate the problem, plus they pretty much only have information on those who are caught comitting crimes. Far better would be estimates from academics, especially sociologists. --Guy Macon (talk) 21:39, 20 September 2017 (UTC)
I don't know if sociologists would have better estimates than law enforcement in all cases. Some very reputable ones might, but plenty of sociologists seem to have the opposite bias to law enforcement these days; underplaying the problem in some cases to make minorities or members of certain groups look better. We should use a combination of the most reputable sources available (each case is different), and report on what they say, as usual. — InsertCleverPhraseHere (or here) 21:49, 20 September 2017 (UTC)
True, but in theory a sociologist will actually do a random survey with a defined methodology and publish it in a peer-reviewed academic journal before making a factual claim. A cop has absolutely no way to know how many law-abiding juggalos there are -- they are invisible to him -- and no way of estimating the total number of lawbreaking juggalos; he only sees the ones in his jurisdiction and he only sees the ones who get caught. --Guy Macon (talk) 22:08, 20 September 2017 (UTC)

Discussion at NSPORTS[edit]

Hello all. In an effort to finally resolve the never-ending and annoying GNG v SSG issue, I've proposed a revision of the NSPORTS introduction. The problem was the subject of a VPP discussion this year. You are all invited to take part in the discussion. Thank you. Jack | talk page 06:20, 20 September 2017 (UTC)

Two clarification RFCs at the Manual of Style[edit]

FYI: Pointers to relevant discussions elsewhere.

Comments sought at:

Both of these are follow-ups to rather lengthy prior discussions on the same pages.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  19:07, 21 September 2017 (UTC)

PS: This may also be of interest:

 — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  19:39, 21 September 2017 (UTC)