RFC on use of WP:OUTCOMES in deletion discussions

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.


The recent RFC on notability of secondary schools[1] was closed with a finding of 4 keys points, the second of which was that WP:SCHOOLOUTCOMES should be added to the Arguments to avoid in deletion discussions, as it is an accurate statement of the results but promotes circular reasoning.

Since this principle has been accepted, then why should it be applied only to schools? Exactly the same problem of circular reasoning applies to use of WP:OUTCOMES in every other deletion discussion, from astronauts to zoology. The principle is already set out at WP:OUTCOMES#Citing_this_page_in_AfD, but has not been carried through to WP:ATA.

WP:OUTCOMES as a whole should be added to the Arguments to avoid in deletion discussions. --BrownHairedGirl (talk) • (contribs) 05:48, 1 March 2017 (UTC)

WP:OUTCOMES Survey

Thus I oppose to expand that change of appreciation, which by the RfC is only applicable to SCHOOLOUTCOMES, to other topics – at least an RfC is needed for every specific topic of OUTCOMES (or PERENNIAL) to declare it open again for a new WP:CCC appreciation. --Francis Schonken (talk) 07:17, 1 March 2017 (UTC)

Discussion

For those opposing this (that is, they do not want to see OUTCOMES broadly listed at ATA), I would ask if you can point to any specific aspect of OUTCOMES that is a valid AFD point that does not put any weight on past AFD discussions/OTHERSTUFFEXISTS-type argues, the same type of issue of why SCHOOLOUTCOMES was considered circular logic from that RFC. In my read of the other points in OUTCOMES besides schools, all the points seem completely circular to me, putting weight on the results of past AFD rather than any compelling reason (such as meeting notability guidelines) that they are kept. As noted in this survey, even OUTCOMES says it is not to be used as an argument at AFD, so I find it odd that there's opposing to simply formalizing it at ATA. (Again as per my !vote, OUTCOMES is good advice for BEFORE, but AFD should not rest its weight on OUTCOMES). --MASEM (t) 14:00, 4 March 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.

Pre-RfC on IP Block Exemptions

Proposal withdrawn.
The following discussion has been closed by [[User:Guy Macon (talk) 02:56, 5 March 2017 (UTC)|Guy Macon (talk) 02:56, 5 March 2017 (UTC)]]. Please do not modify it.

The discussions above (IP Block Exemptions should be expanded to include accounts (5+ years) in good standing) appear to have reached a consensus that the question concerning IPBE needs to be improved. To that end, I am volunteering to post a proper RfC that (I hope) asks the right question. To start the ball rolling. I am going to ask two questions. and use the answers when writing the RfC.

QUESTION ONE: Should the existing question(s) be closed while we decide on the wording?

  • Support: as proposer. -Guy Macon (talk) 19:51, 3 March 2017 (UTC)

QUESTION TWO: What wording should be the question asked in the new IPBE RfC?

  • Comment: I would suggest responding with Proposed wording: for proposals, Support or Oppose after each proposal, and Comment: for general comments that are not proposals for a specific wording. --Guy Macon (talk) 19:51, 3 March 2017 (UTC)
  • Comment Do we really need a debate on what questions should be asked? Couldn't we draft a policy, put it up for discussion and amend accordingly? --*Kat* (talk) 21:52, 3 March 2017 (UTC)
  • I don't see how. We already drafted a policy, we already put it up for discussion, and we already amended it (in the "restart" section), yet we are no closer to having a wording that most of us agree asks the right question. Far better to try to agree on what the question should be rather than asking new wrong questions again and again. --Guy Macon (talk) 02:23, 4 March 2017 (UTC)

At this point I'd rather see Salvidrim's solution run up the flagpole. If we generally don't do hard range blocks on VPNs, the problem pretty much solves itself. Rangeblocks are something not every admin even knows how to do, so we're talking about a fairly small group that needs to be aware of it and adjust accordingly, and then this issue will pretty much be resolved ermanently without the need for users to make individual requests. Beeblebrox (talk) 04:56, 4 March 2017 (UTC)

  • I would be 100% in favor of this approach. It would offer all the advantages of my original proposal with none of the drawbacks.--*Kat* (talk) 06:26, 4 March 2017 (UTC)
  • I was going to wait till I rested to make comment, but tell me, how do we identify a VPN? Because every single webhost or colocation provider can be used as one. So are we setting every single one of those including the ones CUs have seen abuse from, especially spambots and socks with very sensitive (the best word I can find) histories. May I also remind this group that there are active open proxies on those ranges too? Are we really going to undo all that work? This takes an extremely different tone than the proposed RfC above in that the consensus is forming for established. "Should we therefore grant IPBE to users in good standing and with significant editing histories if they desire to use VPNs?" vs. Unblock any editor from using a VPN. Please take care before setting up an RfC that will have highly detrimental effects, and not reflect the existing direction. -- Amanda (aka DQ) 11:01, 4 March 2017 (UTC)
So, where is this new discussion going? Is any of the experience of the previous failed RfCs taken into account? --Francis Schonken (talk) 11:27, 4 March 2017 (UTC)
From where I stand this seems like an elaborate "going through the motions" exercise, producing reams of text-walls (in content similar to the ones produced less than a year ago), with a more than predictable outcome... can someone explain why & how the new initiative on the same topic would be any different? Maybe better to put a break on it before excessive editor time is further diverted to it (with little more chance to success than less than a year ago)? --Francis Schonken (talk) 11:53, 4 March 2017 (UTC)
Please look again. I realize things have gotten off track in the past 24 hours but before that we had a very productive discussion and came to a consensus that VPNs should not prevent registered users in good standing from requesting and receiving an IPBE.--*Kat* (talk) 20:40, 4 March 2017 (UTC)


  • Oppose both. To be completely honest, I think the time community members are spending on this proposal is better spent editing articles. The current situation basically works, keeps things simple for CheckUsers, and reflects longstanding practice.--Jasper Deng (talk) 16:45, 4 March 2017 (UTC)
  • Oppose both for now because we have not yet had an RFC on if this RFC is appropriate to have before having the RFC. Holy shit, I think I just turned into an Xzibit meme. --Jayron32 20:35, 4 March 2017 (UTC)

does winning Grammy awards make one a musician?

There is an IP address, very active in nominating articles for deletion. They recently placed a ((prod)) on Phil Tan, an article about an individual who has won multiple Grammy awards. I asked that nominator to explain why they ignored WP:MUSIC, which explicitly says winning or being nominated for a high-level music award, like the Grammy, was usually a sufficient indication of notability.

The anonymous contributor claimed WP:MUSIC didn't apply, because the Grammy awards were for the quality of his work as a recording engineer. The anonymous contributor claimed being a sound engineer did not make one a musician.

So, does winning Grammy awards qualify one to have their notability evaluated according to the criteria of special purpose music notability guidelines? Geo Swan (talk) 11:25, 7 March 2017 (UTC)

You're asking the wrong question. The question you should be asking is "Do we have quality source texts about this person's life from which we can research and then write a good enough article". If the answer is yes, we should have an article. If the answer is no, we should not. Articles don't exist about a subject because we can check of an arbitrary box on a checklist. They exist because we have source texts we can use to research and write an article from. I have not even looked at this one person, but you should really ask yourself, before deciding if the article should exist "what is being used to research and then write information about this subject". If the answer is "nothing" or even "not much", then no, don't have an article. --Jayron32 11:44, 7 March 2017 (UTC)
Agree with Jayron... However, it is very likely that someone who has won multiple Grammy awards will have sources that discuss him/her... sources we can use to support an article and establish notability. Yes, there could be exceptions to this (artists who are so reclusive that nothing is known about their life), but this would be extremely rare. So... the best way to "defend" the article from deletion, is to do some research. Find the necessary sources, summarize what they say, cite the sources and Improve the article. Blueboar (talk) 12:00, 7 March 2017 (UTC)
  • In this particular case this was an old article, dating back to shortly after he won his first two Grammy awards. It measured up to the wikipedia's standards, at the time it was written. At the time it was written, it included a long list of external links, instead of the reference style we use now. We shouldn't delete articles, on notable topics, simply because their reference style is no longer up to date.

    I am very sorry to say it looks like nominator 86.20.193.222 nominated the article for deletion without even bothering to look at those existing references.

    It is not that the references to confirm Tan's notability had to be found. It took me about ten minutes to reformat three of those references to the more modern style. Geo Swan (talk) 21:58, 7 March 2017 (UTC)

I agree with Jayron32.
Additionally... please note that this person did not 'win grammies'. Some recordings won grammy awards, and he did some of the back-room work on them. Should the person who does Beyoncé's hair have an article, because she won 5 Grammy awards?
But, I digress. As J said, it's all guidelines; what matters is N. I don't think he meets it, which is why I prodded it. I should probably now go to AFD, but that's pretty hard for an IP user to do.
BTW, the reason I nominated it was, a new user whose AFC had been rejected was using it as an example of OTHERSTUFF.
Maybe others can clean the article up, or fix it, or AfD it.
Geo Swan is just grouchy because I CSD'd a hideous mess of copypasta that he created [2]; the 'history' there is a bit screwy, he's made rather a lot of work.
So now, he's stalking my edits to try to get revenge (e.g. Talk:Don_Bosco_Technical_College,_Cebu - deleted now, but he was complaining about me CSD-tagging an utterly blatant spammy copyvio).
Frankly, I can't be bothered getting into such silly discussions these days.
If it's notable, fine, remove the PROD and fix it. The PROD says that on it. If it's not notable, let it go. Who cares. drops stick 86.20.193.222 (talk) 19:17, 7 March 2017 (UTC)
I fixed the claim that he was a Grammy Winner... that said, given the sources that are currently in the article, I think the subject is boaderline notable. There is enough sourcing to remove the prod at least. The next step would be an AFD nom. Blueboar (talk) 22:19, 7 March 2017 (UTC)

Discussion at Talk:Opinion polling for the French presidential election, 2017#Embedded links in lieu of inline citations

You are invited to join the discussion at Talk:Opinion polling for the French presidential election, 2017#Embedded links in lieu of inline citations. Marchjuly (talk) 23:38, 7 March 2017 (UTC)

RfC on secondary school notability

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

Summary of the close, added 13:28, 23 February 2017 (UTC):


The question asked in this RFC was whether extant secondary schools should be presumed to be notable. Numerically, the respondents to this RFC were about evenly divided between supporting and opposing that statement. However, this is a discussion, and not a vote, and what truly matters is the strength of each side's argument. The opposers have a strong policy-based argument. Requiring the GNG to be satisfied in all cases is a perfectly sensible position, and one that is consistent with all applicable policies. The arguments of the supporters were more mixed. Some arguments, such as "Schools are important to their communities", "Automatic notability of schools are how Wikipedia has always done it, and this has historically served us well", and "School articles are valuable as a recruitment tool for new editors" do not make much sense and were discounted. Another common argument was that removing the protections secondary schools have historically enjoyed at AfD would lead to a flood of mass AfDing. This is a concern to be addressed in a hypothetical implementation, but is not germane to the question of whether those protections should exist. These opinions were partially or fully discounted in our evaluation. The supporters did have some very good arguments mixed in with the poor ones. The argument that sources for secondary schools are more difficult to find than they are for typical topics because they are likely to be concentrated in local and/or print media is very valid. Additionally, the argument that removing the presumption of notability from schools would increase systematic bias is very strong.

Based on the discussion, we find that the community is leaning towards rejecting the statement posed in the RFC, but this stops short of a rough consensus. Whether or not the community has actually formed a consensus to reject the statement posed in the RFC is a distinction without a difference - Either way the proposed change will not be adopted.

Over the course of the discussion, the conversation expanded to include the proper role of SCHOOLOUTCOMES. Citing SCHOOLOUTCOMES in an AfD makes the circular argument "We should keep this school because we always keep schools". This argument has been rejected by the community. Therefore, while SO remains perfectly valid as a statement of what usually happens to extant secondary schools at AFD, SO should be added to arguments to avoid in AFD discussions. Rationales that cite SCHOOLOUTCOMES are discouraged, and may be discounted when the AFD is closed.

Because extant secondary schools often have reliable sources that are concentrated in print and/or local media, a deeper search than normal is needed to attempt to find these sources. At minimum, this search should include some local print media. If a deep search is conducted, and still comes up empty, then the school article should be deleted for not meeting the GNG - Editors are not expected to prove the negative that sources do not exist, but they should make a good-faith effort to find them. If a normal-depth search fails to find any evidence that the school exists, the article on the school should be deleted without the need for a deeper search.

It's worth noting that this discussion does imply that schools are special. We would expect an RFC asking "Should artists whose existence is verified by reliable, independent sources be presumed to be notable?" would be closed quickly and with snowballs. The fact that this was not the case for schools is telling.

It's further worth noting that a flood of AfDs following the addition of SO to the "arguments to avoid in AfDs" list is undesirable. Editors are asked to refrain from making indiscriminate or excessive nominations.

Signed


According to Wikipedia:Articles for deletion/Common outcomes#Schools, commonly referred to by its abbreviated link WP:SCHOOLOUTCOMES, "Most independently accredited degree-awarding institutions and high schools are usually kept except when zero independent sources can be found to prove that the institution actually exists". However, a number of recent AfDs on secondary schools have closed either with no consensus or with consensus to delete. The closing summaries of two of these AfDs, Wikipedia:Articles for deletion/Eden English School Btl and Wikipedia:Articles for deletion/Bal Vikash Secondary School, have included recommendations that an RfC be held on the notability of secondary schools. Following discussion of this at Wikipedia talk:Articles for deletion/Common outcomes#Need for an RfC on schools' notability, there is agreement to hold this RfC, with the following question:

Should secondary schools whose existence is verified by reliable, independent sources be presumed to be notable? Cordless Larry (talk) 19:17, 8 January 2017 (UTC)

Survey

  • It strikes me as rather desperate when the opponents of the status quo point to a single, solitary deletion as "evidence" that the consensus no longer exists. "It's in tatters" as one well-known school deletionist hopefully described it. Er, no! -- Necrothesp (talk) 13:44, 11 January 2017 (UTC)
  • I've not described it as "in tatters" myself, and admittedly there haven't been many deletions, but there does seem to have been an uptick in the number of no-consensus closes. Cordless Larry (talk) 14:34, 11 January 2017 (UTC)
As for what this discussion is really about—as I understand it—the precedent of keeping all secondary school articles comes from earlier in WP history where some basic categories of articles were presumed notable just to save some time and nonsense at AfD (a decade ago... when it was a free-for-all of new editors, especially high school boys writing about their high schools). But AfD works differently now, and all AfD discussions are essentially about whether the sourcing exists to support an independent article—apart from some specific topic areas, mostly sports biographies and, e.g., "school outcomes".
This discussion is also about our article quality. When a topic is a valid search term—as all established secondary schools are—we merge its sourced contents to a parent article so that readers can find sourced information on it. But we do little good for our readers by serving secondary school articles absent of the Wikipedia sourcing standards that we apply to the rest of the encyclopedia. Unsourced articles invite cruft (an empirically true broken references theory), and set lower expectations for the standard of acceptable writing on Wikipedia. It's time to extend our universal sourcing standards to secondary schools, and accordingly, to cover more unsourced topics in their parent articles (merging as appropriate). I am no longer watching this page—ping if you'd like a response czar 18:28, 9 January 2017 (UTC)
The reason I can't support just getting rid of SCHOOLOUTCOMES without an alternative, though, is it would make a lot of vulnerable articles subject to deletion due to the current situation at AfD. The point of presuming notability for certain topics is to correct an imbalance between what GNG is supposed to mean (multiple, reliable secondary sources) and what it usually turns into at AfD (multiple, reliable secondary sources that will probably only be looked for online, by a handful of people who are probably from North America and Europe, possibly only within Google results unless someone with access to a paywalled database stumbles across the AfD, with a seven-day time limit at best, and subject to people arguing that "multiple" means a higher number than what you found or that local or even regional sources don't count despite that not being part of the GNG). Given how many high schools are in rural areas, making it more likely that archived print sources won't be easily accessible, or in countries that don't have the same internet presence as English-speaking countries in the West, these are particularly relevant concerns, and I'm uncomfortable throwing existing articles on schools into that mess with no precautions to avoid deletion on account of sloppy research. I've pulled too many articles from the brink of deletion on account of nominators, and subsequent !voters, who did a poor job of WP:BEFORE to trust the process to work for these articles, and if AfD gets flooded with school stubs after a change to SCHOOLOUTCOMES there may not be enough editors able to do the research to prove all the notable ones really are notable within a week. TheCatalyst31 ReactionCreation 03:09, 10 January 2017 (UTC)
(edit conflict) Please correct me if I'm wrong, but my understanding of your point is that, because AfD has problems, we should ignore the GNG for schools. I'm sympathetic to your point about how this will impact the bias of our coverage, but I don't think we should be going around the GNG just to have thousands of permanent stubs. If anything, that's what the GNG is meant to prevent. It may well be the case that there are thousands of reliable sources on Example High School in Ruraltown, Statesota locked away in my grandmother's attic, but if no one knows that, we can't use the possibility that sources may possibly maybe exist somewhere but we just haven't looked hard enough to justify subverting the GNG. If sources can't be found to satisfy the GNG, it doesn't satisfy the GNG. Full stop. If sources are eventually found, it can be recreated. We shouldn't doom ourselves to eternal searching for sources because maybe we just didn't look hard enough. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 03:54, 10 January 2017 (UTC)
In secondary school AfDs, a common argument is that while sources are hard to find online, they must exist offline and at some point, someone with the necessary language skills could find them and use them to expand and improve the article. I'm sympathetic to that argument, but do we actually have any examples of school articles where that has happened? Cordless Larry (talk) 07:26, 10 January 2017 (UTC)
@Cordless Larry: On the Spanish Wikipedia (which lacks Schooloutcomes) I started es:Liceo Mexicano Japonés and got an AFD: es:Wikipedia:Consultas de borrado/Liceo Mexicano Japonés - it took a lot of effort to keep the article. While it was a Spanish-language article, many of the editors could understand English, but several were doubting possible notability until I got someone at University of Southern California to scan parts of a master's degree thesis which talked about the school. One of the other articles was in Japanese but had an English title/abstract. I have been a longtime editor since 2003 and knew the "process" on how to keep articles; a novice I think would have had much more difficulty, even if he/she spoke Spanish. Also, there was one editor who was trying to force a delete even after I presented source after source after source, and I really, really grew to resent that (and I wasn't the only one who felt that way). I think having SCHOOLOUTCOMES prevents these kinds of scenarios from happening. WhisperToMe (talk) 06:32, 14 January 2017 (UTC)
That's a good-faith and plausible suggestion, except that in some countries it is not the government that accredits schools. In the United States there are six regional accrediting commissions which evaluate and accredit schools and colleges. Example: the Western Association of Schools and Colleges[3] is the accrediting agency for schools in California, Hawaii, and Guam, as well as foreign schools. I favor saying "accredited" but not "government accredited". --MelanieN (talk) 01:34, 11 January 2017 (UTC)
In general I do agree that secondary schools should be considered notable - but there has to be a limit; if I, as a certified teacher, tutor three secondary students from the local high school in my home in the evenings, is my home a school which should have an article? I'd say it was more of a small business. Many people home-school their own children. Are they notable? "Accredited" doesn't mean anything if it doesn't say by whom; "with government-recognized accreditation" or some similar phrase would be more specific. —Anne Delong (talk) 05:08, 29 January 2017 (UTC)
  • The supporters of SCHOOLOUTCOMES often argue that it helps counter that bias, Narutolovehinata5, because it means that schools in developing countries are kept even if few online sources exist. Cordless Larry (talk) 16:31, 10 January 2017 (UTC)
Support. The current standard is reasonably efficient, and removing it would result in an inordinate amount of time, energy, and resulting rancor as we debate (likely) hundreds if not thousands of resulting AFDs. This is not to say that carefully tailored exceptions could be carved out of the existing standard. The Big Bad Wolfowitz (aka Hullaballoo). Treated like dirt by many administrators since 2006. (talk) 18:10, 10 January 2017 (UTC)
Please note that the concerns of massive timesinks of AFD noms is a point I tried to address in the section below, namely that we actually should avoid encouraging mass rushes of AFDs of secondary schools and use other processes. It is a very valid concern but we do have policy via WP:FAITACCOMPLI that would prevent that, and we should have a plan going forward if its removed. --MASEM (t) 18:15, 10 January 2017 (UTC)
  • That's ridiculous. If we do that then we may as well abandon GNG entirely for vast parts of the world, and not merely in the schools topic area. That systemic bias exists may be true but we have to accept that some things (most things!) can't be fixed by WP alone. - Sitush (talk) 22:09, 10 January 2017 (UTC)
  • I wasn't aware that Jimbo set policy or guidelines, and his opinion is of no more weight than mine or yours. Times change, and that OUTCOMES has become a self-fulfilling essay is all the more reason why we need to revisit it and address the underlying shortcomings that are now apparent and which make it problematic. - Sitush (talk) 22:13, 10 January 2017 (UTC)
  • Thanks for your comment about the "support" versus "yes" wording, Kudpung. I see this as more about yes/no than support/oppose too. Cordless Larry (talk) 22:21, 10 January 2017 (UTC)
  • It shoudl be noted that Jimmy Wales' comment about schools was in the very early days of the project, after which we have actually developed the notability guidelines that hold us to higher standards, so resting too much on Wales' comment doesn't reflect the changing consensus. Comparing schools to Pokemon characters is definitely apples-to-oranges, but at one point we did have articles for each Pokemon but since have developed a WP:POKEMON test to follow notability practices. There is no reason we could now do the same with schools. (And I would expect that if SCHOOLOUTCOMES is nixed, that we would have to re-examine CSD criteria for schools) --MASEM (t) 23:42, 10 January 2017 (UTC)
Per the five pillars and Wikipedia's partial functionality as a gazetteer, it would be aligned with Wikipedia's core purposes to consider developing a guideline for secondary schools that are verifiable but otherwise not correspondent with notability guidelines to be merged into articles about the school district authorities that manage the schools, or to the city/town/village articles where they are located. Another idea is to merge such articles into lists of schools per geographical region, such as by county. Such recommendation could be added to WP:NSCHOOL if a consensus to do so were to occur. This would serve to improve the encyclopedia, and is also functionally correspondent with WP:ATD-M. North America1000 09:29, 13 January 2017 (UTC)
I am aware that primary and middle schools that don't meet WP:GNG already are supposed to redirect to their school district and/or a daughter article listing schools in that school district (for U.S. and Canada public schools), or to the locality (for schools outside of the U.S. and Canada and private schools) WhisperToMe (talk) 13:05, 13 January 2017 (UTC)
The problem with using the Gazetteer aspect is that this is only being applied to schools, and secondary schools at that. The argument if you want to got the gazeteer route is then we should be doing not only secondary schools, but also primary schools, government buildings (town halls, police + fire departments), parks and other similar areas, and potentially other features like churches. That line of logic gets very hairy very fast, for an encyclopedia. (If we were just indexing places and coordinates, as it what a gazetteer primarily does, this wouldn't be a problem, but we want more content than just name and coordinates). Practically, our implementation of being a gazetteer gets to the resolution of towns and villages and geographical landmarks recognized by an appropriate governing agency; anything more detailed than that falls outside of what we consider to be our gazetteer function. --MASEM (t) 17:28, 13 January 2017 (UTC)
My proposal above is only based upon secondary schools, not all those other topics. North America1000 18:02, 13 January 2017 (UTC)
And my counterpoint is that while the logic works for secondary schools, there are buildings/facilities that are as equally important if not moreso than schools that would also fall under the gazetteer logic that we should track, but we don't. --MASEM (t) 18:30, 13 January 2017 (UTC)
SCHOOLOUTCOMES isn't a policy or guideline. It's a representation of fact. It won't die until the facts change and more editors !vote to delete or merge. CalzGuy (talk) 13:56, 13 January 2017 (UTC)
You're missing the point that it is used to actually prevent such !votes from happening, it has effectively shut down the debate. Like a dictator who was properly elected 20 years ago, who abuses his incumbency to prevent any subsequent elections that may unseat him. Roger (Dodger67) (talk) 14:22, 13 January 2017 (UTC)
An essay has no power to prevent an AfD taking place. In fact, if you want an AfD to take place no one can stop you. What SCHOOLOUTCOMES does is to suggest beforehand that actually it's a pointless exercise. But if you want to plough that pointless furrow, no one here can stop you. But a lot of us may just step in and !vote to keep, and in doing so will sort of prove the point. So how would SCHOOLOUTCOMES "die" in any case? CalzGuy (talk) 15:40, 13 January 2017 (UTC)
You are proving the point about the problem of SCHOOLOUTCOMES with regards to secondary schools. It cannot be used to say "an AFD on a secondary school will be useless" and thus prevent anyone from filing an AFD. It cannot be used in an AFD to say "well, SCHOOLOUTCOMES says we don't delete schools, so this can't be deleted" (which happens all too much). The problem of SCHOOLOUTCOMES is that it is a leftover of pre-notability periods on WP. If it was being used properly, then at AFD on a secondary school, people would !vote keep by showing there are some secondary sources about the school (even if not perfectly at GNG-type levels, enough to give presumption of notability), or otherwise delete/merge/etc. Then, if it was the case that the near majority of such AFDs that "keep" was the most common result, then SCHOOLOUTCOMES would make sense. But that's not how it is developed or used anymore - its the catch-22 self-fulfilling cycle that is getting worse. --MASEM (t) 16:09, 13 January 2017 (UTC)
Continuing the above thread: It is trivial to find concrete examples of SCHOOLOUTCOMES being used to shut down discussion. See Wikipedia:Articles for deletion/Benicia High School, for example. SCHOOLOUTCOMES is specifically cited as the reason to keep the nominated article, completely shutting down discussion and effectively preventing secondary schools from being nominated for deletion. That is why this RFC is happening. More examples: Wikipedia:Articles for deletion/Carman-Ainsworth High School, where there are many links to guidelines and policies, and all discussion is preempted by SCHOOLOUTCOMES; another good discussion is at Wikipedia:Articles for deletion/Tenby International School, Penang (2nd nomination). I suggest that regardless of the outcome of this discussion, we should create or change a guideline around notability of secondary schools. The current situation is not tenable. – Jonesey95 (talk) 16:18, 13 January 2017 (UTC)
CalzGuy, your first point has it exactly backwards. If we repeal SCHOOLOUTCOMES and return to a pure GNG standard, the systemic bias here will become much worse. As you point out, schools in America and other English-speaking countries do tend to have easily-findable coverage and are thus much more likely to have articles. Schools in less-developed or non-English speaking countries are much less likely to have such coverage and will get deleted or never accepted in the first place. One of the main benefits of SCHOOLOUTCOMES is that it helps to mitigate our bias against material from less developed and non-English speaking countries. (It does not eliminate it entirely because we still need confirmation that the school exists and is a secondary school.) --MelanieN (talk) 19:01, 13 January 2017 (UTC)
Except part of that systematic bias is that these secondary school articles often weigh heavily on the use of local sources to support notability, which isn't really in the spirit of notability on a global encyclopedia. Local papers covering local schools lack true independence we want for notability sourcing (these can be used to augment that, however!) If AFDs were done in absence of SCHOOLOUTCOMES and considered the type of coverage these Western schools were getting, most of these would still be deleted because of that local coverage, which is a different way to approach fixing that systematic bias while meeting the notability guidelines we expect for any other topic. We need to bite the bullet and accept this is the case though. --MASEM (t) 19:08, 13 January 2017 (UTC)
I intentionally add "local" content to Wikipedia because people care about their hometowns and want to introduce them to the world. It's a motive for editing Wikipedia that can be used to recruit people. WhisperToMe (talk) 20:09, 13 January 2017 (UTC)
While is one very very fragile step away from COI editing. There's a level of resolution we want to keep to avoid extremely localized topic for this reason. Articles on towns are good collectors for such information because that also fits our gazetteer function well. --MASEM (t) 20:17, 13 January 2017 (UTC)
@Masem: I think the public understands the natural desire for one to write about their hometown/what they like. Where COI is worrisome IMO is if it's a for-profit company (especially if they're paying you), or a BLP case, or a case where someone's sole goal is to make a topic look good. We need to give into inclinations of "I like this, so I'll write about it" without allowing it to go too far, or allowing for profit/professional PR motives/BLP issues from becoming a problem. If it's a teenager writing on Wikipedia for the first time just adding info about a hometown he cares about deeply, just give him a heads up on how to write objectively about where he's from, but if it's somebody working for a company doing PR ask them to do edit requests and not touch the article directly. @Masem: WhisperToMe (talk) 20:50, 13 January 2017 (UTC)
@Dodger67: I think that SCHOOLOUTCOMES actually makes it easier to write articles about schools in the developing world. In the U.S. it's easier to find secondary sources about U.S., Canadian, European, etc. high schools, and it's easier to find sources on them in English. If you're writing about a Japanese high school you may encounter a language barrier. If you're writing about an Ivorian high school, you may find evidence that it exists on a government website, or on the AEFE (if a French international school) or ZaF (if a German international school), but it may be harder finding secondary source info directly on the web. SCHOOLOUTCOMES treats all senior high schools equally.
I held a Wikimedia workshop at a Chinese university where I asked students to write about their high schools. I told them "why not check the newspapers for info on them" and they said they didn't think the newspapers had any info on their high schools. In my hometown the Houston Chronicle covers high school info regularly (and I'm not including routine coverage).
WhisperToMe (talk) 20:09, 13 January 2017 (UTC)
Dodger67 - You have managed to get this 100% backwards. Schools in the English-speaking industrial world are virtually 100% guaranteed to pass GNG and articles on them will not be challenged. The effect on the stubby articles dealing with schools in the developing world will be immediate and massive — and guess what: nobody is gonna come to their aid. You have just made the opposite case, you need to either flip your opinion from oppose to support or to get real about what the impact is gonna be. Carrite (talk) 14:42, 19 January 2017 (UTC)
Carrite I'm not at all convinced that most English-speaking industrial world high schools could genuinely pass WP:ORG or WP:GNG. The articles about the vast majority of such schools depend on a combination of firstly routine coverage of the "it exists" variety, such as government reports and database-like records such as proof of accreditation, and secondly mere local coverage in the form of local news media reporting on the school's basketball team, new principal, etc. If school articles did not have this "special protection" they have enjoyed over so many years we would have far fewer articles, even about American high schools. Now take the counter-example of Indian villages. Clusters of nearby villages tend to have a shared local authority for various purposes such as a clinic, post office, police station and other government services which may also include a small high school. The cluster of villages would also contain one or more temples. An article about the temple has very little chance of getting created, but if it does get written, it invariably gets deleted fairly quickly as not notable. However the article about the school, which arguably is just as significant to the community as the temple (or clinic), and based on essentially the same sources as the temple article, is permanently exempted from deletion by SCHOOLOUTCOMES. In my country, South Africa (which has a very well developed media sector, as large and active as many "first world" countries) I guesstimate that perhaps only about one hundred schools could genuinely pass WP:CORP or WP:GNG, and IMHO that's perfectly ok, because Wikipedia is not an indiscriminate collection of information. -- Roger (Dodger67) (talk) 16:30, 19 January 2017 (UTC)
Pretty sure that WP:INDISCRIMINATE is about what kind of information - and more pointedly, the format thereof - we collect and not about which topics are or are not covered. Jo-Jo Eumerus (talk, contributions) 17:08, 19 January 2017 (UTC)
Jo-Jo Eumerus If all one can properly source about a school is that it exists then the article about it is effectively a "listing", WP:NOTDIRECTORY is a better fit, you are correct. Roger (Dodger67) (talk) 18:43, 19 January 2017 (UTC)
It seems obvious to me that such an assurance would need to be in the original RFC proposition for contributors to take account of it. They don't seem willing to accept post-haste assurances that it won't happen. With all due respect to the original proposer, I wonder if the proposition itself is somewhat flawed, in that it doesn't provide alternative actions in case of opposition. CalzGuy (talk) 15:33, 19 January 2017 (UTC)
The lack of that consideration of process is why I started the section below. It really should go hand-in-hand. And even if it was the case that we didn't have process, the AFD issue would be something covered under WP:FAITACCOMPLI, that flooding AFD with school articles would absolutely not be appropriate. It would just be better to have an explicit process statement to know how we'd go forward if SCHOOLOUTCOMES is removed. --MASEM (t) 15:42, 19 January 2017 (UTC)
Apologies for not including that in the question, CalzGuy, but that question was a result of discussion at Wikipedia talk:Articles for deletion/Common outcomes#Need for an RfC on schools' notability and nobody suggested it there. I also think there's merit in keeping the question simple, and dealing with the consequences separately once consensus has emerged. Cordless Larry (talk) 07:59, 20 January 2017 (UTC)
Don't apologise. I don't think it would have been an obvious thing to do. However, I do think that once this discussion is closed as "No consensus", as it undoubtedly will, we will then need to have another discussion on where to go next, as I think there is a consensus for some change. It's just a matter of figuring out what. CalzGuy (talk) 09:22, 20 January 2017 (UTC)
Echoing Cordless Larry here that from the discussion about having the RfC, the question of process was not an obvious one at the time. As I have expressed below, I am of the view that anything short of a close in the affirmative here will require more work on drafting a process and then probably another discussion on where to go. I think the advantage in separating the discussions and keeping it simple is that it allows people to comment on the question of notability itself, which has never really been answered by a guideline, just SCHOOLOUTCOMES. TonyBallioni (talk) 00:32, 22 January 2017 (UTC)
Just Chilling We routinely delete churches, temples, town halls, post offices, hospitals, and many other institutions that also play a significant role in communities - high schools are the only "category" of such institutions that are specially protected. Roger (Dodger67) (talk) 07:01, 20 January 2017 (UTC)
Im just reminding you Dodger67 (and anyone else reading this, including the eventual closer) , that the RfC question is: Should secondary schools whose existence is verified by reliable, independent sources be presumed to be notable? OUTCOMES is not metioned and is therefore not the subject of this RfC. You can't ban its use. To do so would be to invite a list of several thousand AfD closures being posted on each new AfD as the documentary evidence that has produced the precedent. That said, 'churches, temples, town halls, post offices, hospitals, and many other institutions' are not, unlike schools' exempt from CSD-A7. Kudpung กุดผึ้ง (talk) 02:55, 25 January 2017 (UTC)
And how do we do that? One at a time at AfD. Hope to see you there, wasting 5 minutes per debate or more checking sources as we wade through the flood of new articles on elementary schools... Carrite (talk) 15:09, 20 January 2017 (UTC)
  • Rubbish. We're not primarily a social experiment and all this carping about systemic bias, using it as a way to avoid our encyclopaedic requirements, is just bleeding heart stuff. How much time should we allow? Do you have any idea how many false statements are made on articles concerning the Indian sub-continent? - Sitush (talk) 21:54, 22 January 2017 (UTC)
  • Your rationale does not necessarily apply outside the developed countries, nor does it satisfy even WP:V, which needs multiple independent sources and not, for example, town council minutes. - Sitush (talk) 15:53, 28 January 2017 (UTC)
One of my projects in my second coming on Wikipedia was to increase the number of notable and popular secondary schools on Wiki. I noticed that out of about 10,000 sec schools in Lagos/Ogun axis, where I'm based, there were only about ten with wiki articles. This isn't too surprising when you note that less than 100 of this 10k can boast of an existing website. The way these schools operate and are structured, there will always be limited coverage. Nonetheless, I started creating articles on the most popular and notable, especially the public ones. I have created Lagos State Model College Badore,Federal Government Girls College, Ipetumodu, Lagos State Model College Kankon, Lagos State Junior Model College Kankon, Lagos State Model College Igbonla, Lagos State Model College Badore, Landmark University Secondary School, Lagos State Junior Model College Badore, Covenant University Secondary School, etc. One of my secondary school schools even got speedied twice and a COI tag wrongly placed on it. It was funny to me because the school in question is one that all Nigerians are familiar with, because it was used to act a national series of immense popularity some decades ago. You can verify my statement yourself, if you know any Nigerian who's less than 40 years, just ask him/her if he has heard of Binta International School, I'm 98% sure that his response will be yes. Or better-still, ask any Nigerian editor on Wikipedia, the response will be the same. I really got angry by the COI tag that was placed on the article. I think we need to be soft on African secondary schools as long as the information is verifiable.
I went through many of the oppose votes and I think the fear is that they don't want Wikipedia to get clumped up with thousands of poorly written articles, which is an understandable position. This is why I will only support for African articles, because I know that will never be the case for them. The Nigerian secondary schools with minimal online coverage are essentially notable enough for inclusion on Wikipedia. I'm voting for this to be an informal policy. — Preceding unsigned comment added by Darreg (talkcontribs) 14:01, 1 February 2017 (UTC)
I also looked at the evolution of the Outcomes page itself. After some minor adjustments in wording, the initial statement regarding schools was the one found here. This was expanded a bit in late 2007, to give detail regarding different types of schools (i.e., primary vs. secondary), as shown here. The big change took place in May 2009, with its changing of "in most cases being kept" to "being kept". The edit that made this change is here. Its edit summary cited this sparsely-attended discussion as the basis for making the change. That discussion was not the subject of an RfC and I could find no evidence that it was publicized anywhere other than on that Talk page. In early 2011, there was a brief attempt to declare "per se notability" for high schools, but there was an immediate objection and, in that day's flurry of edits (see here), something looking quite like the current version came into being.
These two observations show that there has never been a consensus on the treatment of secondary schools. At the very least, the Outcomes essay should be amended to reflect this fact. NewYorkActuary (talk) 20:17, 5 February 2017 (UTC)
See WP:NOTAVOTE. Looking over this discussion it is abundantly clear that the Oppose arguments are heavily based on policy and guidelines while the Supports are largely silent on that subject. The reviewing Admin is going to have to weigh the respective arguments and determine if the various retentionist arguments outweigh our guidelines and policy. -Ad Orientem (talk) 15:25, 6 February 2017 (UTC)

Process to consider

Working on the presumption that this may close in opposition, there is clearly a concern about the status quo of school articles. As part of the consideration here, I would suggest that if this does close this way, that all existing secondary school articles should at least be kept and there should not be a rush of mass deletions per WP:FAITACCOMPLI to remove them. However, fair AFD challenges can be held, recognizing that OUTCOMES no longer is supported here. Where possible, editors should be encouraged to merge info about secondary schools into articles on the notable city/town/school system and redirects left behind, avoiding the AFD process and keeping past contributions. This avoids any aggressive, disruptive approach if this should as suggested and alleviate fears that thousands of articles will suddenly be sent to the void. It will take a case-by-case review of each to determine what should be done, in such cases, and that will take many man-months of evaluation. --MASEM (t) 17:51, 9 January 2017 (UTC)

Given that the current 'vote' is 13:11 in favour of oppose, I would have to say I would hope that would be closed as "No consensus" rather than oppose, if it was closed just now. Having said that, I do agree that any change to consensus here, should not result in mass deletions. Rather, it should result in the development of a guideline, which may or may not result in deletions. CalzGuy (talk) 18:21, 9 January 2017 (UTC)
Yeah, I'm not saying it will close "oppose", but I think we do need to broadly address the concerns of those !voting "support" that worry what would become of the articles that already exist. I think it is necessary to address what should or should not happen should "oppose" be the result as to alleviate some of those "support" concerns. By no means am I saying this RFC is done and over with. --MASEM (t) 18:38, 9 January 2017 (UTC)
@Masem: I'm wiling to start a guide on how to improve high school students to ensure that those that already exist can be developed as well as they can be. I've written many high school articles, mostly in North America but some also for international private and state-operated schools around the world. I actually encouraged Chinese university students in a workshop to start writing about their high schools, and this is a way to get Wikipedia to grow. WhisperToMe (talk) 09:16, 13 January 2017 (UTC)
Good luck with that. The grand compromise between deletionism and inclusioniam would be flushed, the SCHOOLOUTCOMES essay reduced to nothing. Deletionists might think they're "upholding standards" and eliminating a bunch of really terrible articles about high schools from India, but what they are actually doing is opening up the floodgates for about 100,000 American and English elementary schools to have vapid fluff pieces with news about Mrs. Finley the principal and what is served for lunch on Fridays. You think I joke. Carrite (talk) 15:15, 20 January 2017 (UTC)
If SCHOOLOUTCOMES were to be eliminated, notability of schools would default to WP:NORG, and key in there is WP:AUD "On the other hand, attention solely from local media, or media of limited interest and circulation, is not an indication of notability; at least one regional, statewide, provincial, national, or international source is necessary." Now, we'd have to be careful ("This school is acredited by the state's board, so there's your one statewide source!"), the implication is that this should be a secondary source, not primary. But we have the language in place to prevent a flood of primary schools from being created because of that. --MASEM (t) 15:18, 20 January 2017 (UTC)
Spoken like somebody that doesn't spend a lot of time at AfD. Carrite (talk) 15:18, 20 January 2017 (UTC)
I agree that the AfD process would probably be flooded with AfDs should this not close as support initially, but I also think Masem has a point that WP:FAITACCOMPLI does exist. The issue is how to deal with editors who would likely make WP:POINTy nominations afterwards (I have no one in particular in mind here, just a gut feeling.) I'm not sure what the best practical way to prevent that is if the RfC closes NC or oppose, but I also feel that the sheer volume of work that it would take for people to nominate a ton of schools would keep people at bay for a while, especially since I doubt this will close as outright oppose at this time (but who knows, I could be wrong and we have plenty of time left in the RfC.) TonyBallioni (talk) 00:43, 22 January 2017 (UTC)
As I said above, to my eyes, the primary issue regarding a lot of primary and secondary schools is probably not so much their notability as such, but whether there is really enough encyclopedic content to merit a separate article. In cases like this one, I think that there actually are probably quite a few relevant reference works relating to the topic, and they would, I think, probably be the best indicators of how we should proceed here. The primary question there being what content to have in articles on specific institutions, and what content to have in school districts, or similar bodies, and how much really encyclopedic content that leaves over for separate articles on specific schools in those bodies. Now, I myself wouldn't necessarily have any real objections to, for instance, articles on schools of any level, primary or higher, which seem to be one of the few or only schools (either at that level or higher) operated by a specific entity, like a church. But how to deal with content on specific schools as opposed to their governing bodies, where such include several similar schools, is another matter entirely. John Carter (talk) 21:11, 25 January 2017 (UTC)
Personally, I would like to see some alternative policy to schooloutcomes created. I know for a fact that there are many secondary schools that there is a lot of encyclopedic things to say about, but that would probably end up at AfD is no replacement policy existed. Spirit of Eagle (talk) 07:03, 28 January 2017 (UTC)
Seconding. The notability of secondary schools has been a highly debated topic on Wikipedia, and there is a lot of nuance within the discussion that needs to be accounted for. Spirit of Eagle (talk) 21:05, 28 January 2017 (UTC)
I'd also support that. SCHOOLOUTCOMES is aprox. a decade old, and anything that would change it in one way or the other would have a huge impact. Having a team of uninvolved closers seems ideal. TonyBallioni (talk) 05:13, 31 January 2017 (UTC)
I'd support that approach too. Cordless Larry (talk) 17:34, 4 February 2017 (UTC)
Done. — Rhododendrites talk \\ 20:42, 4 February 2017 (UTC)
That's what this RFC was intended to do, by posing the question if secondary schools were notable, which was what the various no consensus AfDs seemed to be disagreeing on. The argument from the keeps traditionally being that SCHOOLOUTCOMES has long established that schools were notable and the deletes being that proof of meeting GNG or WP:ORG was required in the moment. This RfC was intended to resolve that by asking the most basic neutral question possible. If it closes NC or oppose, I agree that more work will need to be done on a new guideline, but I think the reasoning behind this RfC was sound and that it was the right question to ask. TonyBallioni (talk) 14:24, 1 February 2017 (UTC)
The RFC is a single question to do with notability of secondary schools. There is much more required to be covered, and agreed, if a guideline (policy is probably OTT) is to come into play. For instance, there be nuances of geography, or of age of pupils, or of age of schools. Is a school notable if the building in which it is housed is notable? What about elementary/primary schools? What about all-through schools. This RFC is only about a single aspect of the whole. The discussion needs to be widened. CalzGuy (talk) 16:20, 1 February 2017 (UTC)
If the RfC does close anyway other than the affirmative, then yes, you are right. The point is that it wasn't entirely clear before this started that something more than a "yes or no" was needed here. All the advice provided was for a narrowly construed RfC which is why it was framed this way. If this is closed in a way other than "support" the closing statement and this RfC will be able to serve as a starting point for a future discussion and will allow those of us who want to take part in drafting it to consider points that I don't think would have been considered if this RfC did exist. Personally, I think a wider RfC would have been even more likely to lead to a NC close than this one if there was not a more narrowly construed comment period first. tl;dr: You're right moving forward if this doesn't close support, but I still think this was the right starting point. TonyBallioni (talk) 16:31, 1 February 2017 (UTC)
A 'No consensus' close will leave the status quo as is. It will be no different from a Support close because that's where we are just now. CalzGuy (talk) 06:33, 2 February 2017 (UTC)
We normally determine no consensus based on whether or not there is consensus,regardless of where it may happen to lead. Ay way, I think there is very clear consensus, far outreaching the result here--essentially no high school afd where the school clearly had real existence and was clearly a high school has closed as delete for lack of notability in the last 5 or 6 years. The argument that we must have sourcing for verifiability is of course valid as far as the verification of the facts in the article is concerned, but that's irrelevant, for meeting WP:V is a good deal less than the specific types of sourcing that shows notability. DGG ( talk ) 00:28, 6 February 2017 (UTC)
Except that a point that is absent or underemphasized but core to this is how does WP:NORG's Audience guidance fit into secondary school notability. Many examples of "kept" secondary schools presented during this violate WP:AUD by using strictly local sources (that otherwise meet V/RS), but this point is never really brought up during AFD because you have a lot of people shouts "SCHOOLOUTCOMES". We need to get rid of SCHOOLOUTCOMES regardless of which way consensus falls, either by explicitly writing the allowance for secondary schools into NORG, or otherwise not given secondary schools that free pass at notability. I agree that this RFC doesn't answer that question but we now know better how to word it, including stipulation that if the "no free pass" is the agreed option, we are going to grandfather all existing school articles to avoid flooding AFD. --MASEM (t) 15:14, 7 February 2017 (UTC)
  1. Schools don't 'not exist'. School articles are generally written about schools that exist. As coord of the WP:WPSCH for years (and genuinely active at it to boot), I've rarely come acrosrs a school being invented for the purpose of hoax. School articles may often sound somewhat promotional, but they ae mainly written by the children that attend them - or alumni and let's face it, most people are proud of their schools and without them they wouldn't be able to read or write or know that the world is not flat - let alone edit Wikipedia. Practically everyone on the planet goes to a secondary school with the exception of some remote developing regions. It's therefore fair to say that schools have an impact on society. On the other hand Not everyone has eaten in a small Mitchelin starred restaurant in the Netherlands that gets an article without so much as a nod, and doing so would not make them nutritional scientists, heart surgeons or astrophysicists. What's missing in this debate is rather a large portion of common sense - an expression we're not supposed to use on Wikipedia.
  2. None of the opposers have any respect for the sensitivities of the dedicated editors and admins who have the burden the workload presented a) by new page patrollers who without a clue are allowed to tag articles and send them down various sewers of deletion or conversely let the clearly non notable or spammy for-profit high street cram school through. To oppose this motion would open the flood gates to the likes of those who with alarming regularity over the years now and again decide to send a bunch of school articles to AfD because between meals in their 'notable' restaurants, they have noting else better to do. Kudpung กุดผึ้ง (talk) 12:22, 12 February 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.

SCHOOLOUTCOMES post-script & implementation

...200+ comments, 24,000+ words, and yet nobody even mentioned the existence of WP:Notability (high schools) (a failed proposal, now tagged as an essay). WhatamIdoing (talk) 21:13, 22 February 2017 (UTC)

I believe that all of the points in that essay were raised above and discussed thoroughly. – Jonesey95 (talk) 23:01, 22 February 2017 (UTC)
Unless I am misreading this (it is a bit long and an executive summary would be helpful) Secondary Schools are not presumptively notable and SCHOOLOUTCOMES is discouraged from being cited at AfD. Further SO should be added to the list of arguments to be avoided at AfD. All of which said the closers seemed to also be saying that schools are different in an undefined way and editors should take a deep breath before sending school articles to AfD with an emphasis on due diligence and searches for sources. -Ad Orientem (talk) 03:47, 23 February 2017 (UTC)
Not helpful when the local print media is in Bodo. I don't know where this leaves us. Jack N. Stock (talk) 05:00, 23 February 2017 (UTC)

Ad Orientem, you've pretty much hit the nail on the head. I'll update the close with a summary to avoid further confusion. Jacknstock, references/sources do not have to be in English, so it kind of leaves you in the same position you were in before. Primefac (talk) 13:28, 23 February 2017 (UTC)

The close urges preventing a rush to AfD because of this, and I think if there are any disruptive editors who flood AfD they can be dealt with on a case-by-case basis. I don't want to get into instruction creep here. I do think it would be better to possibly copy the close and the summary to a WP-namespace page other than outcomes because I think the actual wording of the long form close is useful and the current permalinks to "this February 2017 RfC" could be intimidating to some newer users who very well could be writing school articles. TonyBallioni (talk) 18:22, 23 February 2017 (UTC)
What do you all think about preventing "a rush to AfD" (or even a good-faith effort) by adding prominent recommendations that non-notable schools use the WP:Requested merge process instead, since that is normally the best alternative? WhatamIdoing (talk) 19:07, 27 February 2017 (UTC)

Does anyone agree that this is not a good venue for ongoing discussions? The RFC has been closed. We should all leave quietly and find a new place to discuss better ways forward, shouldn't we? CalzGuy (talk) 18:36, 23 February 2017 (UTC)

I don't see any problem discussing how we are implementing the suggestions made by the closers which affects multiple P&G pages. The changes being made refer back to this discussion so that it thus helps a person coming in fresh to see what else is being done as to not make this closing action disruptive. (Key is is that no one is complaining about the close result, which would be inappropriate to go on about). --MASEM (t) 18:56, 23 February 2017 (UTC)
All notability rules are guidelines only. Suggestions to change WP:N to policy have been consistently defeated. DGG ( talk ) 19:14, 11 March 2017 (UTC)
I intend to argue just as before at afds: in practice we always keep secondary school articles if there is actual evidence for verification. DGG ( talk ) 19:14, 11 March 2017 (UTC) DGG ( talk ) 19:14, 11 March 2017 (UTC)

Removing edit protections from files

I've made a proposal here, posting this here to solicit more opinions. Jo-Jo Eumerus (talk, contributions) 14:51, 12 March 2017 (UTC)

RFC on Fabergé egg naming convention

A recent page move discussion has raised an interesting question regarding the disambiguation of Fabergé egg titles. I have started an RFC in an attempt to codify the naming conventions of these eggs. Please join in the discussion here. Primefac (talk) 17:08, 13 March 2017 (UTC)

valuable picture of trump's childhood

I just found a valuable picture of trump's childhood (here: [6]) that is cool to upload for the article. Can anybody do this? Alborzagros (talk) 11:15, 14 March 2017 (UTC)

I don't see any indication that the photo is under a free license. Do you know where it's indicated that it was released under one? It wouldn't be old enough to be public domain, so we'd need an explicit free license release. Seraphimblade Talk to me 12:09, 14 March 2017 (UTC)
Is it ok?


Alborzagros (talk) 12:42, 14 March 2017 (UTC)

2016 is not between 1923 and 1977. Jack N. Stock (talk) 12:58, 14 March 2017 (UTC)

Time of taking picture is important. isn't it? Alborzagros (talk) 13:00, 14 March 2017 (UTC)

Yes, but so is time of publication. Note that the template says that the photo was published during that time frame, not taken during it. Do you have any indication that the picture was published then, and that there was no copyright notice? (The photo itself doesn't have to have a copyright notice; if for example something it appeared in had a notice, that could cover it as well.) It is very unlikely that this photo is public domain. Seraphimblade Talk to me 13:16, 14 March 2017 (UTC)

Weather events and notability

I noticed there are already articles on serious winter weather events (ex. January 2009 North American ice storm, January 1998 North American ice storm). However, there does not seem to be any specific guideline on about those kind of events - what makes them notable enough? WP:EVENT states general things, such as that the event has lasting impact, a large enough geographical scope, and significant coverage. Now, my question is, how large must that be? Is coverage in multiple new sources - including some outside the countries affected ([7] [8]) enough to demonstrate significant coverage? Does an event that causes major disruption to road and air traffic (including cancellation of thousands of flights - throughout North America in this case) ([9]) have enough of an impact? I'm asking this (yes, you've guessed, mostly because of the actual weather here) mostly because of the lasting impact criteria. The question is: If an event meets and exceeds the criteria for having a large enough geographical scope and significant coverage, but the impact (however major) is only short-term, should it be included? - In other words, is it notable enough? Thanks (from snowy Quebec)! 69.165.196.103 (talk) 13:02, 15 March 2017 (UTC)

I'm not sure it is possible to be any more explicit that EVENT already is, but the folks at Wikipedia:WikiProject Meteorology may be able to provide some more insight. Beeblebrox (talk) 23:33, 15 March 2017 (UTC)

Developing guidelines for adding open license text into Wikipedia

Hi all

I have been developing guidance on adding open license text into Wikipedia, with the idea of setting up a process to adapt and add existing open license text into Wikipedia. The potential for adding open license text is huge e.g there are over 9000 open license journals. This guidance could be used by both Wikipedians and as an expert outreach tool for experts who have already written suitable text which is available under an open license.

Something lightweight, perhaps one or two paragraphs at most would be ideal to help someone understand quickly how to adapt text, the text would have links to further reading if needed.

My main stumbling block is I can find very little information on adapting the tone of open license text to the tone of Wikipedia. I also know there would need to be information on neutral point of view etc.

All suggestions greatly appreciated.

Thanks

John Cummings (talk) 11:22, 16 March 2017 (UTC)

It has been a while since I last checked, but I was under the impression that the term "inverted pyramid" was more prominent in the MOS than it is now. This is one place where it is mentioned, and perhaps this is helpful? - Wikipedia:Summary_style and Wikipedia:Summary_style#Levels_of_detail - "Summary style is based on the premise that information about a topic need not all be contained in a single article since different readers have different needs... This can be thought of as layering inverted pyramids where the reader is first shown the lead section for a topic..." -- Fuzheado | Talk 11:37, 16 March 2017 (UTC)

Use of Template:Interlanguage link in template space

The following discussion is an archived record of a request for comment. Please do not modify it. No further edits should be made to this discussion. A summary of the conclusions reached follows.
Procedural close. The previous RFC ended a week ago (plus one day). There are other questions that could be valid RFCs (such as officially determining if an interwiki link is truly an "external link"), but simply reopening the original discussion in a different venue does no good. Primefac (talk) 18:21, 16 March 2017 (UTC)
  • As the closer of the previous RFC, I want to explicitly endorse the above close. I explicitly cautioned TonyTheTiger: Don't jump directly to Village Pump, the community likes to have some time for things to process and settle after an RFC.[10] Alsee (talk) 03:15, 17 March 2017 (UTC)

Should the use of ((Interlanguage link)) in templates be allowed? An RFC at Wikipedia talk:Categories, lists, and navigation templates on the use of Template:Interlanguage link in template space closed as no consensus. The participants in that discussion were as follows

Supporters: 1. TonyTheTiger (as RFC nominator), 2. Randy Kryn, 3. Gerda Arendt, 4. Jc86035, 5. Andrew Dalby, 6. Hawkeye7, 7. K.e.coffman, 8. Thincat, 9. Finnusertop, 10. Iazyges, 11. Sadads
Opponents: 1. Frietjes, 2. The Banner, 3. PBS, 4. MilborneOne, 5. Walter Görlitz, 6. Izno, 7. Plastikspork, 8. Robsinden, 9. Boghog, 10. Bkonrad +1 IP

At issue is the propriety of employing ((ILL)), which creates a small foreign language wikipedia link to accompany redlinks, in the following ways Old revision of Template:The Sea-Wolf, Old revision of Template:White Fang, Old revision of Template:The Twelve Chairs, Old revision of Template:2010-2019VSFashion Show, Old revision of Template:2000-2009VSFashion Show, Old revision of Template:1995-1999VSFashion Show, Old revision of Template:2010–19 Sports Illustrated Swimsuit, Old revision of Template:1990–99 Sports Illustrated Swimsuit, Old revision of Template:1970–79 Sports Illustrated Swimsuit.

In closing the prior RFC, the closer (Alsee, noted that the broadly defined external links have been opposed in templates for a long time as was made clear in this 2012 edit to the guideline. The closer noted that an RFC on the subset of external links known as interwikis had been discussed in a prior 2015 RFC that closed with 3/4 opposed to an exception for using interwikis in templates. Above we considered an exception for a small subset of interwikis known as the foreign language wikipedias and the above RFC closed as no consensus. The prior RFC contested whether there was ever support for the 2015 change to the guideline opposing non-English wikipedia links. The prior RFC suggested coming to Village pump if that RFC close remained contentious.--TonyTheTiger (T / C / WP:FOUR / WP:CHICAGO / WP:WAWARD) 15:22, 16 March 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.

Combining AfC reviewers and new page reviewers

There is an ongoing discussion about combining AfC reviewers into the new page reviewer user right. Your comments and opinions would be welcome. ~ Rob13Talk 03:26, 17 March 2017 (UTC)

Multi-part RFC on Wikipedia:Recent years

The following discussion is closed. Please do not modify it. Subsequent comments should be made in a new section.
21:45, 13 January 2017 (UTC)

Scope of recent years guidelines

This has been discussed several times on the talk page of the guideline, but due to low participation a consensus is not clear and there is no set definition of what qualifies as a recent year. Should the scope be limited to:

Discussion of scope of recent year guidelines

Scope:future years

Wikipedia already has articles for every year in this century, all the way up to 2099. Given that these will all one day come under the recent years guidelines as time marches on, should articles on future years be subject to the recent years guidelines? If so, how far into the future should the guidelines be applicable?

Discussion of scope:future years

When this is concluded I plan to open another discussion specifically on these articles, it seems a little nuts to have "predicted events" of little to no consequence that may or may not occur 75 years from now. Beeblebrox (talk) 00:51, 17 January 2017 (UTC)
Maybe this needs its own discussion/RfC - many of these future year articles have no references whatsoever, and per WP:TOOSOON and WP:V they might need to be deleted at this point in time. And anyway, I agree it seems absolutely bizarre to have them. Triptothecottage (talk) 03:45, 18 January 2017 (UTC)
I agree: a discussion needs to happen. There simply isn't enough reliable information about events beyond 10 years into the future to justify creating an article, & creating one beyond then is just too tempting for someone looking for an easy way to up their editcount. -- llywrch (talk) 20:38, 25 January 2017 (UTC)
My reasoning as being so harsh regarding future predictions in the year articles is mostly due to manageability of dynamic information such as this. Imagine NASA announce that plan to place a human on Mars in May 2025 attracting considerable news coverage. So, we have a future year with a significant anticipated event. Various Mars & Mars landing articles are created, updated by a large number of interested Wikipedians. The 2025 article is updated, presumably by the much smaller subset of Wikipedians who like to update year articles. Later on, the launch is postponed to July, generating less media coverage and the Mars Wikipedians are all over it, but we're relying a Year Wikipedian being aware of the new date and remembering that this exists in a future year article and doing it themselves.
And also, Wikipedia is not a calendar. Scribolt (talk) 10:00, 15 February 2017 (UTC)

Recent years category/edit notice

Currently, the only tool in use for identifying articles within the scope of the recent years guidelines and advising users of the existence of said guideline is ((Recent years)), a talk page template advising users of the existence of these guidelines and advising them to read them before adding anything. There does not appear to be a category or a standard edit notice to better organize these articles and better inform users of these specialized guidelines.

Shoud a category for identifying and organizing these articles be created? Should there be a standard edit notice attached to all articles bound by the recent years guidelines so that users who do not check the talk page first will still receive notification of these specialized guidelines? If technically possible, should all three be linked so that adding the notice to the talk page automatically adds the article to the category and generates the edit notice?

Discussion of Recent years category/edit notice

The "three continent rule" for events

Current wording:

New events added must receive independent news reporting from three continents on the event. This is a minimum requirement for inclusion. Events which are not cited at all, or are not Wikilinked to an article devoted to the event, may be removed.

Should this rule be continued to be used as the minimum threshold for inclusion of an event in a recent year article? Is there a better metric that might be used?

Discussion of the "three continent rule" for events

"Ten languages rule" for births and deaths

The current rule for inclusion for births and deaths of notable persons are as follows:

Births:

Births are only to be included if there are Wikipedia articles in English and at least nine non-English languages about the individual in question.

Deaths:

The same criteria apply to deaths as to births, with the addition that the number of non-English Wikipedia articles is taken at the time of the person's death. Persons whose notability is due to circumstance rather than actual achievement (e.g. oldest person in the world or last surviving person of [x]) do not meet the basic requirement for inclusion.

Should these continue to be the minimum standards for the inclusion of births and deaths in recent years articles? Is there a better metric that might be used?

Discussion of the "ten languages rule" for births and deaths

Wikipedia:Recent years as an editing guideline

The Recent years page was created on January 5, 2009. After some discussion between about five users on the talk page, it was moved into project space and marked as an editing guideline one week later. This does not appear to conform to the usual process for elevating advice or essays to the status of editing guidelines. However, it has been used and basically accepted as the standard for articles on recent years since that time.

Should Recent years continue to be marked as an official guideline, relegated to essay status, or promoted to a policy?

Discusion of Wikipedia:Recent years as an editing guideline

It appears the tail wagged the dog on this one. Guidelines are supposed to be written to reflect best practices already in use, but in this case the guideline seems to have come first and dictated the practice. However, at this point it has been in place for long enough that it does seem to be the accepted guideline, and this discussion is drawing so little input that it looks like it will stay that way. Beeblebrox (talk) 21:13, 8 February 2017 (UTC)

General discussion of recent years guideline

Please leave any comments that do not fit in any of the above sections here.

As I mentioned above, I raised it here to see if the topic will get more discussion, as I had previously raised it in the WikiProject talk page but the discussion went nowhere. Narutolovehinata5 tccsdnew 00:43, 15 January 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.

Are top lists copyright infringement ?

I've found many articles as Tozai Mystery Best 100, 20th Century's Greatest Hits: 100 English-Language Books of Fiction, The Guardian's 100 Best Novels Written in English, The Top 100 Crime Novels of All Time that seem to be copyright infringement. Is it ? Elfast (talk) 23:34, 16 March 2017 (UTC)

If it's just a simple list, they can not be copyrighted due to lack of original content. This essay addresses the issue and has links to relevant policies and guidelines. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 23:38, 16 March 2017 (UTC)
And to specifically answer your question, the three lists mentioned are not copyright infringements. ···日本穣 · 投稿 · Talk to Nihonjoe · Join WP Japan! 23:39, 16 March 2017 (UTC)
This is absolutely incorrect, as noted below. They all are subjectively selected lists, so this are all copyvios. --MASEM (t) 04:58, 17 March 2017 (UTC)
What Masem said. The Guardian list is certainly a copyright issue, being a completely subjective 'Best of' list based on unknown criteria by a single author. Which I will nominate for speedy as soon as I work out how. The other two are less obvious but going by the essay you yourself linked would likely be considered copyvios. Only in death does duty end (talk) 15:47, 17 March 2017 (UTC)

Thank you for your answer. Nevertheless, in the article you link, you can read "A complete or partial recreation of "Top 100" or similar lists where the list has been selected in a creative manner" is "unacceptable use."". It contradicts your view. Elfast (talk) 23:58, 16 March 2017 (UTC)

What is often referred to as a 'laundry list' are not copyrightable. But when it comes to an organization issuing a list derived from its own its own effort. Then I agree that this seems like a copyright infringement. Of course, if the organizations are very 'notable' their lists become generic but not quite. For instance, the current Dewey Decimal Classification is still proprietary. So think you have a good point. Maybe these articles need to go for AfD.--Aspro (talk) 23:56, 16 March 2017 (UTC)
Today I learned that the Dewey Decimal is proprietary. Thanks for that tidbit! :D ^demon[omg plz] 00:48, 17 March 2017 (UTC)
I used to work shelving books in a large library and I didn't know that either. Crazy. Beeblebrox (talk) 04:50, 17 March 2017 (UTC)
'Effort' is actually the wrong word in this context, as the US does not recognise 'effort' but does recognise 'creativity'. You could put a lot of 'effort' into creating a list from publically known facts but as 'effort' isnt recognised, it wouldnt be copyrightable (unlike in other parts of the world where even databases compiled from public data can technically be copyrighted due to the amount of 'effort' used to create them). A subjective list contains substantially more 'creativity' but could contain much less 'effort' and would be copyrightable in the US. I could create my 'Top ten list of films involving sharks' in about 5 minutes, it would take me substantially longer to create 'Top ten most profitable shark films' Only in death does duty end (talk) 16:09, 17 March 2017 (UTC)
  1. Have completely objective criteria.
  2. The idea behind the list must be onw which a person may be reasonably likely to come up with withou having seen the sorce. So if Only in death were to create a "Top ten most profitable shark films", the idea behind the list may be copyrighyted.
עוד מישהו Od Mishehu 19:10, 18 March 2017 (UTC)

Wikipedia talk:Administrators#Proposed: Minor change to inactivity policy notifications

Interested parties, please see Wikipedia talk:Administrators#Proposed: Minor change to inactivity policy notifications, an RFC which seeks to modify how and when administrators are given notification regarding pending removal of administrative permissions. –xenotalk 19:57, 20 March 2017 (UTC)

RfC: Hyphen in titles of articles on railways of a narrow gauge

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 articles with "Narrow gauge railways" and such in their titles include a hyphen as "Narrow-gauge railways"? And is there any tweak needed to the guidelines at WP:HYPHEN to be more helpful in deciding such things? Dicklyon (talk) 05:58, 4 February 2017 (UTC)

Neutral background

Many articles were moved in late December and early January to include a hyphen, and then after about four weeks were disputed and moved back. Discussions at various places left the matter unresolved, and an RFC was recommended.

Affected articles include but are not limited to the ones in this template, which works the same with and without the hyphen due to the redirects:

Other pages moved in early January to include a hyphen, but not explicitly disputed or moved back, include Narrow-gauge railroads in the United States, Narrow-gauge railways in India, Narrow-gauge railways in China, Narrow-gauge railways in Canada, Narrow-gauge railways in former Spanish Morocco, Narrow-gauge railways in former French Morocco, Narrow-gauge railways in Oceania, Narrow-gauge railways in South America, Narrow-gauge railways in North America, Narrow-gauge railways in Asia, Narrow-gauge railways in Africa, and possibly others. Presumably if this RFC has a robust outcome it will apply to these as well.

@Bahnfrend, No such user, Bermicourt, SMcCandlish, Cinderella157, Tony1, Necrothesp, Mjroots, Corinne, Checkingfax, Scribolt, Mandruss, and Andy Dingley: Pinging participants of prior big discussion at Talk:Narrow_gauge_railways_in_Saxony in case any of them didn't see the notices. Dicklyon (talk) 17:48, 4 February 2017 (UTC)

The case for hyphenation in these titles

It is standard practice in English to help readers parse phrases involving compound modifiers before nouns by using hyphens to hold the compounds together. As WP:HYPHEN states, hyphens are used:
3. To link related terms in compound modifiers: [Specifically, compound attributives, which are modifiers of a noun that occur within the noun phrase. (See hyphenated compound modifiers.)] – Hyphens can help with ease of reading (face-to-face discussion, hard-boiled egg); where non-experts are part of the readership, a hyphen is particularly useful in long noun phrases, such as those in Wikipedia's scientific articles: gas-phase reaction dynamics. However, hyphens are never inserted into proper names in compounds (Middle Eastern cuisine, not Middle-Eastern cuisine).

The application to the compound "narrow gauge" when used before a noun is clear: the hyphen helps the reader, especially the general or naive reader unfamiliar with the phrase, to quickly parse "narrow-gauge railway", and not have to consider whether the intended meaning of "narrow gauge railway" might have been a "gauge railway" that is narrow. This is common courtesy to help the reader, and has no downside or negative impact on any reader. There is nothing special about titles that would suggest a different style from what is appropriate in the text.

Sources are mixed on hyphen usage, since it is common practice for writers to drop such hyphens when writing for an audience that they feel is so familiar with the term-of-art phrases that they don't need help to easily read them. But in the case of "narrow gauge", which is well known to rail fans but less so to the general public, usage in books is actually a strong majority in favor of hyphen usage. See n-gram stats from books: [11]. Even if it were only 50% used in sources, it would be wise to follow the advice of our style guidelines and most external style guides and dictionaries to make it easier for the general readership rather than the specialists.

There is no ENGVAR issue here. Using the n-grams link above, but modifying the language domain from English to British English and American English, it can be seen that while the relative frequency of railway versus railroad changes enormously, as expected, the relative frequency of hyphen stays in a strong majority in both variants.

Dictionaries specifically list the adjective form of "narrow gauge" as hyphenated: dictionaries, [12], [13], [14], [15], [16].

Within specialist literature, the hyphen is still sometimes used, and in literature for the general public it is sometimes omitted, but it is better to follow standard practice and guidance than to be that random, and it is much better to help the general reader than to try to mimic the specialist.

Note also that in company names, signs, headings, titles, and such that are Title Case or all caps, it is more common to omit hyphens. So the appearance of these terms unhyphenated but capitalized should not be taken as evidence of any preference one way or the other.

Note that WP:MOS, including WP:HYPHEN exists to set a style and prevent style disputes so we can all get back to work on non-trivia. It did not prevent a battle in this case, but I think it is clear enough and probably does not need any particular amendment in this area.

Examples of titles with hyphenated compounds used as adjectives

Most Wikipedia titles involving compounds such as narrow body, broad spectrum, standard definition, short range, high speed, low pressure, small cell, large scale, wide angle, and such do use the hyphen in a way exactly analogous to what is proposed for narrow gauge. Examples:

Please respond to this opening case in the discussion section below, not here. Dicklyon (talk) 06:44, 4 February 2017 (UTC)

The case for no hyphenation in these titles

The phrase “gauge railway” by itself is meaningless. In fact, the only other modifiers that I can think of other than narrow are broad/wide, standard, miniature, and “out-of-” (however, no argument about using hyphens for the last one). Therefore, the argument requiring hyphenation is pointless, and this attempt to enforce one particular POV should be dropped in favour of common usage, which seems to vary slightly from one side of the Atlantic to the other. (This point was made in an earlier discussion, but Dicklyon now seems to be walking it back.) The suggestion made by the nominator that the average reader needs the hyphen in “narrow-gauge” for comprehension is pure and simple condescension. So in a word:
Oppose. Useddenim (talk) 17:33, 4 February 2017 (UTC)

@Bermicourt, Bahnfrend, and Mjroots: This RFC is ready for an opening statement by someone opposing the hyphens. Dicklyon (talk) 06:46, 4 February 2017 (UTC)

Side Survey: The case for not really caring one way or the other / The case for editorial freedom

because I don't. Beeblebrox (talk) 06:58, 4 February 2017 (UTC)

Note that these should not be counted as opposing the proposition of this RFC, as these editors (or most of them) have put the oppose !votes already in the survey below. Dicklyon (talk) 23:41, 5 February 2017 (UTC)

Note: that is disingenuous and highly misleading; we do oppose the proposal because it would force us to adopt one of the two common variants used by the sources. But thanks for alerting me to vote below as I hadn't, despite your comment --Bermicourt (talk) 20:14, 6 February 2017 (UTC)
Thanks for clarifying your position, and you're welcome for my alert. I don't know why Optimist thought it a good idea to add this side survey, and I was certainly not being disingenuous in trying to call attention to the confusion. Please AGF. Dicklyon (talk) 21:08, 6 February 2017 (UTC)
"Uninvested"? If you think anyone who has no especial fondness for a particular topic is uninvested, you're mistaken. Everyone working on the encyclopedia is invested, even those who participate in discussions by announcing that they don't care about the outcome. Primergrey (talk) 14:34, 6 February 2017 (UTC)
I think someone whose presence at a railway article is only there to enforce a general usage MOS rule which may not be appropriate given the specific circumstances is uninvested in railway articles yes. They might be invested in the MOS... But ultimately no one outside of railway article editors and their readers care about the hyphen usage on railway articles. The world is not going to end if narrow-gauge is hyphenated. It really does not matter. Only in death does duty end (talk) 15:14, 6 February 2017 (UTC)
"and their readers" is the important part. Dicklyon (talk) 15:16, 6 February 2017 (UTC)
Being invested in the encyclopedia means being invested in all articles therein. To dismiss an editor trying to uphold site-wide style guidelines as "uninvested" runs counter to WP's stated purpose as a generalist encyclopedia. Also, "the world is not going to end if narrow-gauge is hyphenated", if true, is an excellent reason to support hyphenation. Primergrey (talk) 17:13, 6 February 2017 (UTC)
No, it is not. There is actually little support to make it apply everywhere. Alanscottwalker (talk) 16:30, 7 February 2017 (UTC)

Main RFC Survey

Please Support or Oppose including the hyphen in the titles.

There is a case for consistency with names that are created on WP. So I have no problem with "Narrow-gauge railroads in the US", nor even "Narrow gauge railroads in the US" (I really don't care what our "default styleguide in the absence of any external influence" says. But when the name is based on an external source, those sources should be followed, not the styleguide.
Why do external names matter for the hyphenation of narrow-/ gauge? After all, there are very few of them (although the North Wales Narrow Gauge Railways didn't hyphenate). Because this isn't just a question of hyphenating narrow-gauge, it's also the question of capitalising "Line" in "Heart of Wales Line". The two naming issues should have been raised in the same RfC. But whilst the narrow-gauge one is broadly linguistic and hardly appears in sourced proper names, the capitalisation issue certainly does. Yet if the easier narrow-gauge issue can be won, that then establishes a "precedent" for WP naming, including the case issue - when in fact, WP does not follow WP:PRECEDENT in such cases. Andy Dingley (talk) 12:04, 4 February 2017 (UTC)
The AT policy page has consistency as one of the five characteristics of good article titles. Primergrey (talk) 20:15, 11 February 2017 (UTC)
It also says "These should be seen as goals, not as rules", and makes it clear that the rules on article titles are for the benefit of readers. If I thought that readers would suffer in any way (by being unable to find the right article, or by being confused as to the topic of an article, for example) I'd agree we need to enforce a rule here. WP:COMMONNAME, which is the next paragraph in AT, says editors should reach a consensus, and includes "usage in the sources used as references for the article" as one of the inputs to that consensus. To me, this all means we don't have to have hyphens in these article names. If they already had hyphens we should leave them in; if they don't, leave them out until there's a consensus among editors working on the article that they should be changed. Mike Christie (talk - contribs - library) 22:06, 11 February 2017 (UTC)
The MOS is not policy and the policy-based reason to "defy" MOS is in the MOS itself: ... it is best treated with common sense, and occasional exceptions may apply. The MOS itself is contentious, as the 190-page archive of its talk page alone shows, so no false impression need be created. Eggishorn (talk) (contrib) 04:42, 18 February 2017 (UTC)

Threaded discussion

There is no ambiguity and no confusion here. All of the links you have posted are very obviously nothing more than careless proofreading or editing errors, pure and simple. To say, as you do, that such obvious careless errors demonstrate confusion is like saying that the spelling of the word "Michael" is unclear and ambiguous because a lot of people misspell it as "Micheal". In other words, it is a grasping at straws, nonsense argument, which wrongly and disrespectfully treats Wikipedia readers as a mob of fools. Bahnfrend (talk) 11:33, 5 February 2017 (UTC)
If any editor took my remarks as treating them as fools, or otherwise disrespectfully, I sincerely apologize. My remarks were about the ambiguity in parsing unfamiliar terms, and pointing out errors that might have been caused by that ambiguity as seen by unfamiliar writers or editors, and conjecturing that that evidence supports the interpretation that there is real ambiguity there for those unfamiliar with the concept, while acknowledging that many of those are simple errors of transcription or something. It's OK with me if you disagree; it won't make me think less of you. But the ad hominem might. Dicklyon (talk) 17:31, 5 February 2017 (UTC)
  • @SMcCandlish The only fallacy is that "arguments against enforced hyphenation are 'obvious fallacies'". First, the idea that you have to be "deeply familiar" railways to understand the term is an insult to the commonsense of the majority who don't need a grammar lesson to work it out. Second, the sources favour neither variant (we agree to that extent) except in North America, thus there is an element of WP:ENGVAR to this which simply reinforces the Wiki principle of leaving editors to decide for themselves as they had been doing happily for years, until this over-zealous, pro-hyphen crusade came along. Bermicourt (talk) 18:12, 5 February 2017 (UTC)
Can't say I care that much either way, but as regards having to be deeply familiar and a specialist etc, I think it would have been sensible to ease off on the rhetoric and not post such thoughts until checked against a well-known not-that-specialist series of publications aimed at those who have not yet had the benefit of much schooling. If you Google "Thomas the Tank Engine narrow(-)gauge" it will be found that Thomas has "Narrow Gauge" Friends, except in WP where his friends are "narrow-gauge". Just saying....Rjccumbria (talk) 18:44, 5 February 2017 (UTC)
Many of the Thomas books and other books by Awdry [17] [18] [19] [20] use "narrow-gauge engine", "narrow-gauge friends", "narrow-gauge railways" and "narrow-gauge rails" with the hyphen, but omit it when capitalizing as "Narrow Gauge". Pretty standard, and reported with links in the previous big RM discussion. Except this one gets mixed up and even uses the hyphen in capped "Narrow-Gauge Engine". Dicklyon (talk) 18:49, 5 February 2017 (UTC)
The Thomas books were first published between 1945 and 1972, and therefore cannot be described as a useful guide to present usage of hyphenation. Bahnfrend (talk) 04:09, 6 February 2017 (UTC)
Agreed. It's hard to tell which are the ones written since 1983 by his son Christopher, which modern editions might have been re-edited, etc. Dicklyon (talk) 04:39, 6 February 2017 (UTC)
In any case (apologies for having taken a break from this, and for obviously failing to be adequately clear first time round what the point I thought I was making was), the point I thought I was making was not that "TtTE avoids hyphenation, so should we" (give me some credit, chaps!) , but that some of the rhetoric was OTT counter-productive shooting from the hip. Far from the un-hyphenated form being some arcane perversion known only to specialists, it is one potentially known to any child whose reading age stretches to Thomas the Tank Engine (mind you, they could probably also tell the difference between a diplodocus and an apatosaurus better than most grown-ups). I suppose we should be grateful that (as far as I am aware) we have yet to be told that hyphens are a mandatory requirement under health and safety legislation.
Do I see from the above that people who learned punctuation in the third quarter of the twentieth century will not have valid opinions on best practice? That could be just the excuse I need to slip away from this...Rjccumbria (talk) 10:12, 6 February 2017 (UTC)
Whether sources from that era reflect current usage is orthogonal to what anyone's personal opinion is. Regardless, a) it's clear that the materials you pointed to mostly do hyphenate except in proper names (which is a common but not universal alteration), and b) waht writers of children's books do wouldn't tell us much about how to write encyclopedic prose; we learn that from academic versus casual style guides, and from what high-quality but general-audience sources do, and the answer is "hyphenate compound adjectives, either uniformly or possibly with the exception to not do so when there is no possibility of confusion" (an exception which does not apply here; Dicklyon already pointed to numerous cases of things like "the gauge railway" and "a gauge railway" in professionally edited material, where writers had mistakenly parsed "narrow gauge railway" as "a gauge railway that is narrow".  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  12:36, 12 February 2017 (UTC)
Bermicourt, your ENGVAR theory is completely refuted by stats from British English books. If there's a small difference in the proportions, it's likely attributable to the higher proportion of rail-specialized publications in the UK compared to the US. But it's still a good super-majority hyphenated there. Dicklyon (talk) 18:49, 5 February 2017 (UTC)
But you are uninterested in external sources and consider only the hyphenation styleguide to have any effect. You've just moved (undiscussed, naturally) dual mass flywheel to the hyphenated form, despite the unhyphenated form being universal in the drivetrain industry.[21][22]
You come here, presenting yourself as supporting the use of sources for one case (narrow gauge railways) when there is very little difference of opinion over that particular naming question, yet when there are other issues (such as capitalising "Line") that are contested, your behaviour is to ignore all sources, provided that you can find even one,[23] no matter how non-RS or poorly copyedited that coincides with your prejudical view to enforce the styleguide regardless. Andy Dingley (talk) 09:07, 6 February 2017 (UTC)
How many times do we have to go over this, Andy? I think I've covered this with you at least half a dozen times already, on three or four different pages now. "[I]n the drivetrain industry" = in specialized sources written by specialists to other specialists. WP is written for a general audience, not a specialized one. What do general-audience, mainstream publications prefer, and what to the style guides they follow (and on which MoS is based) advise, for such constructions? Hyphenation of the compound adjective. Only someone steeped in drivetrain lore has any idea whether the unhyphenated "dual mass flywheel" means a "mass flywheel" of a dual-construction nature (a "dual, mass flywheel"), or flywheel of a "dual-mass" sort (a "dual-mass flywheel"). Specialized publications sometimes drop hyphenation, commas, and other clarifiers because they are certain that their narrow, focused readership all already know the answer and have internalized this terminology in great detail. Do you really think we haven't already been through this same argument many times with regard to medical terms, legal terms, computer science terms, etc., etc., with the same result? Do you really think railroads are somehow raising a new issue here? They most definitely are not. This is time-sucking rehash of perennial "my topic is somehow a special snowflake" tedium.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  10:25, 6 February 2017 (UTC)
Unless you three are now so close that you're claiming to speak for each other, I have little interest in what you've said there and am still waiting for Dicklyon's explanation of his moves.
Yes, there is an awful lot of ICANTHEARYOU: Dicklyon is dragged to discussions where he puts forward a reasonable case that relevant eternal sources should be taken into consideration; but then the way he acts, by continuing to make undiscussed page moves against such sources, is at odds with this. I make no excuse for seeing that the naming of an obscure drivetrain component should be taken from the drivetrain industry, the one place it's discussed authoritatively. Andy Dingley (talk) 13:27, 6 February 2017 (UTC)
I do support the use of sources (that's where all info in WP comes from, and informs us about style, too), but I'm not an advocate of "follow the sources", a discreditted anti-MOS campaign from Pmanderson of years past. Where sources are mixed, as S has pointed out, we follow the MOS. In the case of the dual-mass flywheel, I'm seeing 6 of the first 10 book hits with hyphens, but that's not the reason I moved it. I moved it because it was unclear without the hyphen (except to the those in drivetrain business, granted). Dicklyon (talk) 15:51, 6 February 2017 (UTC)
By the way, I held off on tuned mass damper, because I could not clearly determine which of the two meanings was intended, or whether both work fine. Books sometimes use hyphen, but not often enough to convince me that the small minority with hyphens are correct. So I left it, even though sources are a little bit mixed and I think the hyphen would probably signal the intended meaning better in this case. Dicklyon (talk) 16:05, 6 February 2017 (UTC)
Bermicourt, please do not engage in circular reassertion of points that have already been refuted; it's just a frustrating waste of everyone's time. Dicklyon provided ample evidence already of real-world confusion that "a gauge railway" is a real term. This is incontrovertible proof from multiple publishers that people are confused on the matter (even professional editors and writers). Second, "the sources favour neither variant" is precisely the situation in which "just do what MoS says and move on" always applies automatically. This kind of scenario (and the habit of people to argue incessantly that their option is the One True Way) is why MoS exists at all. Only in the opposite situation, when the RS are consistently in favor of one particular option and it differs from MoS's default, do we not do the MoS default. This is also the WP:COMMONNAME policy, BTW, so you can stow any "just a guideline" handwaving: "prevalence in a significant majority of independent, reliable English-language sources". Third, a slight alleged regional preference for one variant over another has nothing to do with WP:ENGVAR. Please actually go read ENGVAR. It's about norms of standardized English usage that have "strong national ties"; a slight leaning in one direction or another in dialects that each demonstrate both approaches, in practice and in style guides, is neither a dialectal norm nor a strong national tie, but exactly the opposite of both. But as Dicklyon notes, your nationalist assumption is false anyway, and the hyphenation is found aplenty in British materials, too. It's just not preferred in the trainspotter publications you are cherry picking to try to "win". I also have to point out that you can't denigrate the MoS and those who seek compliance with its MOS:HYPHEN provisions, out of one side of your mouth, while crying for the overextension of the MOS:ENGVAR part of it to suit you whims, out of the other. That's like being an atheism activist most of the time, but insisting on your devout Catholicism on Sunday when you hope a desperate prayer will be answered.

This is very simple: If everyone understands the form with the hyphen (even if some, due to familiarity with the term find the hyphen unnecessary for their own, personal, individual comprehension), but some people may not understand without the hyphen (even if you believe that number is small or you think they're ignorant), then the obvious answer is to use the hyphen, since it costs nothing and helps some readers, and helping ignorant readers become better-educated readers is WP's primary raison d'etre. That's all there is to it, and it's how encyclopedic writers approach every such question, from whether to break up a long sentence, to which word order to use, to whether an illustration of something may be needed.
PS: I'm going to laugh very hard if you make some kind of "inefficiency and bother" pseudo-argument about hyphens, after the amount of editorial time you have wasted fighting in vain over this trivia, and since a hyphen and a space take up the same room and require the same number of keystrokes.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  10:25, 6 February 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.

IP Block Exemptions should be expanded to include accounts (5+ years) in good standing

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.


For the past three years I have been using Private Internet Access VPN to make myself harder to track on the Internet. I don't see myself stopping this practice anytime soon. The only problem is that I can't edit wikipedia while logged into PIA. Most of the IP addresses are hard-blocked. So, most of the time, I simply don't edit wikipedia at all. I was hoping that this problem would resolve itself, but it has not. So here I am, proposing a solution.

Although I understand the need to block anonymous edits and new-account edits on proxy-IPs, I do not understand why this block must be so comprehensive that it prohibits veteran wikipedians like myself from being able to edit while logged in.

There is a technical solution already available to users in my position. It is called the Wikipedia:IP block exemption. IP block exemptions are automatically granted to bots and admins. Ordinary editors who are impacted through no fault of their own can also be granted IP Block Exemptions -- but only in extraordinary circumstances. My proposal is that this policy be relaxed. I also request that exemptions be granted to accounts that:

Very, very few spammers and sock-puppeteers are willing to create an account, contribute over a thousand (non-minor) edits, and wait five years for IP Block Exemption status just so that they can abuse the exemption status. But, if there are any, they will lose their exemption.. Keep in mind that this exemption would only apply to accounts that meet the above criteria.--*Kat* (talk) 13:14, 26 February 2017 (UTC)

While I wouldn't be opposed to this, it would be almost a complete 180 of how IPBEs are currently used. See for example Wikipedia:Administrators' noticeboard/Archive279#IPBE - IP block exemption removals where last year an 'audit' was done on every account that has IPBE and if they were not actively using it, the right was removed. Jenks24 (talk) 13:29, 26 February 2017 (UTC)
Annoyingly so, for those of us that had this exemption, were not "actively" using it, but then had it revoked only to discover later when they got caught in an IP block trap. Whatever methodology was used for the supposed "audit" was seriously misguided. It apparently never occurred to those parties responsible that editors who are IP block exempt often edit from dynamic IP addresses, which are only blocked some of the time. It may be months without getting caught in a block. Also, it is not very easy to get administrators to grant IP block exemption. They make it seem like it is some kind of once-only special favor. If it is to be understood as a temporary status, then getting it should be far more automatic than it was when I had to spend hours arguing over irrelevant things like my username (you read that right!) in order to get exempted. In fact, this interaction gave me a disgust with administrators here that I still bear. Sławomir Biały (talk) 13:50, 26 February 2017 (UTC)
At least you didn't get accused of abusing it for edit warring, especially on a page where there isn't enough diff to support the claim that you had a disputed, let alone edit-warred. —Codename Lisa (talk) 15:21, 26 February 2017 (UTC)
This seems like a reasonable change in policy, perhaps with the addition of a 1-year inactivity removal to reduce the risk of compromised accounts. If someone has been around long enough and proved that they're not causing disruption to the encyclopedia, they should be allowed to edit from wherever they want. — Train2104 (t • c) 16:22, 26 February 2017 (UTC)
Strong opposition to any sort inactivity removal. I normally edit from home, but sometimes I edit from a job site in China. My employer requires that I only connect to the Internet through TOR when onsite in China, so I requested and was granted IPBE. The thing is, I may spend years between the times when I need IPBE. Right now, every so often I use TOR from home, just because someone might decide that I am not using it enough, but that is actually sub-optimal. Not only is it slower, it makes it harder to run a checkuser on me. Removal should start with asking me on my talk page, then seeing that I have edited Wikipedia to make sure I wasn't on vacation or something. --Guy Macon (talk) 19:56, 26 February 2017 (UTC)
I was referring to inactivity as in "no edits at all", not inactivity as in "no edits requiring IPBE". Just like admins are desysopped after a year. — Train2104 (t • c) 03:25, 27 February 2017 (UTC)
I went ahead and did all that, as well as notifying at WT:IPBE. Beeblebrox (talk) 19:36, 26 February 2017 (UTC)
You'll note I said opposed as written. I am open to the idea of a reasonable proposal to change the conditions under which we grant IPBE, I just don't think automatically granting it after five years is the right approach. Beeblebrox (talk) 22:49, 27 February 2017 (UTC)
@*Kat*: I read over the granting at WP:EXEMPT and it seems to me that any editor who was blocked "through no fault of their own" could reasonably be expected to get the privilege:
IP address block exemption allows editors to edit without interruption, when their usual IP address would otherwise be blocked through no fault of their own.
Although it does say in other places that it is only granted under "exceptional circumstances," I believe that was meant to apply to editors requesting it for Tor. I got the impression that being blocked through "no fault of your own" immediately qualifies as an "exceptional circumstance." If that's what confused you, perhaps a suggestion about a slight revision to the page is in order? (To be honest, I think it is one of the better more concisely written pages on rules.)

Or is there another issue? Perhaps that long-term editors might not realize they can request the permission? There is a section that says:
In addition, IP address exemption may also be given by an administrator without a request, to prevent good-faith editors being affected by a hard IP address range block.
It seems you want this to be more automatic. Instead, I would support giving automatic notice to any user meeting the above requirements of the ability to request the exemption. I would support automatic notice for even a much lower threshold. Would that solve the problem?
--David Tornheim (talk) 11:30, 27 February 2017 (UTC)
The part you quoted is intended for someone whose *normal IP* is impacted by a vandal's IP block. My normal is not being blocked. My "chosen" (for lack of a better word) IP is being blocked because it is an open proxy IP. I don't have a problem with open-proxy IP blocks. I've reverted too much vandalism not to understand why they are necessary. What I do have a problem with is open proxy IP blocks impacting long time editors who have done nothing wrong. --*Kat* (talk) 14:19, 27 February 2017 (UTC)
@David Tornheim:, WP:EXEMPT makes it very clear that, "Editing via an anonymous proxy can be easily abused, so it is only granted under exceptional circumstances." THAT is what I would like to change. While I would prefer for the exemption to be granted automatically, if that isn't feasible at this time then it isn't feasible. But I definitely want to see this bar against VPNs lifted.--*Kat* (talk) 14:26, 27 February 2017 (UTC)
@*Kat*: Okay, I don't know this well enough to know whether the word "exceptional" for Tor is too high a standard. I could see the potential for abuse, but I am not sufficiently familiar with that. I think the requirements you listed above are in a sense "exceptional". So perhaps there could be a change that those editors meeting the threshold you identified would meet the "exceptional" standard, but rather than be automatically granted by a bot, that an admin would have to review the request before it is "automatically" granted. I definitely understand the concerns about having a bot do it. A slight revision to the language on the WP:EXEMPT page would make that possible if there is sufficient support for such a change. --David Tornheim (talk) 14:54, 27 February 2017 (UTC)
*Comment I don't see this RfC as asking the right question. I think IPBEs should be easily granted, without the need for editors in good standing to jump through hoops. (Perhaps granted by request from any user with a certain number of mainspace edits, been around for several years, no block log, or some other reasonable proxy for assessing "in good standing".) I also feel that some test should be incorporated into policy, to make this easier for administrators to check. At the moment, the policy seems quite vague and discretionary, and I think this leads to needless issues both for editors wishing to obtain IPBE and administrators determining whether granting this status is appropriate. However, I don't think they should be automatically granted, as that creates a needless avenue for abuse. Sławomir Biały (talk) 13:20, 27 February 2017 (UTC)
This having been said, the right to privacy is something that is explicitly recognized by the foundation, in the privacy policy, which states "we believe that you shouldn’t have to provide personal information to participate in the free knowledge movement", and a commitment to "[use] reasonable measures to keep your information secure." This ought to include the freedom to use a VPN to avoid snooping ISPs, and the right should be granted upon request to any editor in good standing who asks for it. Sławomir Biały (talk) 19:47, 27 February 2017 (UTC)
  • Do you have a method that allows editing from webhosts/proxies without IPBE? --Guy Macon (talk) 15:32, 27 February 2017 (UTC)
Guy Macon — we know there are methods, because this is exactly how archive.is got black-listed. Basically someone used non-public (or just public, but not yet detected) proxies to add links to thousands of pages. The issue was not so much with the site itself, but rather with the modus operandi of one(?) user who just changed IP as soon as he/she/they got blocked. Carl Fredrik 💌 📧 19:41, 27 February 2017 (UTC)
Absolutely my friend -- stop hardrangeblocking to allow registered accounts. The old argument about attribution issues only applies to unregistered editing, and problemtic behaviour can lead to account blocks no matter whether the account is used on a dynamic or static IP or a VPN/webhost.  · Salvidrim! ·  19:45, 27 February 2017 (UTC)
Sorry, but claims that "this isn't a discussion about [the title and opening paragraph of the discussion]" will get you nowhere. If you want the blocking of open proxies to stop, you will have to post an RfC asking that question. See [24], [25], and [26]. --Guy Macon (talk) 22:47, 27 February 2017 (UTC)
That would be a useful allocation of funds from the McDuck moneypit they are building. And of course, since it would be useful, its unlikely to ever happen. Only in death does duty end (talk) 17:19, 27 February 2017 (UTC)
  • That's not a solution. I usually am logged into a VPN. Which means that my IP address is autoblocked. *And* it changes all the time. You are saying that I should request an unblock everytime I want to change a paragraph. This is not a feasible solution since it would take longer to get unblocked than it would take to change the paragraph. And then I would probably have to do it all over again the next time I see something that needed to be fixed. --*Kat* (talk) 21:09, 27 February 2017 (UTC)
  • I didn't say anything like that! Please reread my offer again! Just Chilling (talk) 01:59, 28 February 2017 (UTC)
However I disagree with some of the points that are suggested here as to how the right would be given. While it is true that it is very unlikely that a vandal or disingenuous person would wait 5 years to later start sockpuppeting – this may open the floodgates for a stream of paid editors creating hundreds of accounts today, which could be used in 2022. This is not a good solution, even though we really ought to be far less rigid when handing out IP-block-exempt rights. Unfortunately I don't have any solution that would avoid this issue, but I think it's important to note that the issue is worth looking into.
The biggest hurdle to implementing this is the cut-off of only being able to go back 6 months through checkuser. We could potentially allow anyone with more than 1000—10,000 edits to edit through an IP-block, as long as we could checkuser them back further. Carl Fredrik 💌 📧 19:34, 27 February 2017 (UTC)

Restart

I think we need to completely start over here. Many users have expressed support for some sort of change/relaxation of the conditions under which we grant IPBE, but very few are supportive of this specific proposal. So, let's try this again.

Currently, "because I want to use a VPN" is not a valid reason for granting IPBE, even to experienced users, even though it is granted to admins by default and they are therefore free to use VPNs if they wish. Should we therefore grant IPBE to users in good standing and with significant editing histories if they desire to use VPNs? Beeblebrox (talk) 22:55, 27 February 2017 (UTC)

I think it's important to keep in mind that currently there are only 145 non-admin users who have this right. The majority of them are either operating from behind firewalls in places like China or are regularly affected by blocks that are not targeted at them. The risk involved in opening this up is that, as we have al seen, sometimes even highly experienced users turn out to also be highly experienced sockpupeteers. If they are using VPNs Checkuser is pretty much useless at detecting sock farms. So, this is the risk we would be taking if we decide to do this. Beeblebrox (talk) 23:02, 27 February 2017 (UTC)
Beeblebrox, where do you get the idea that there are 145 non-admin users who have this right? If I go to Special:Listusers and request IPBE users, I see only 113 names, and at least one of them is an admin's public-computer sock (it's mine, Nyttend backup), which has the right because I travel a lot and not too uncommonly find blocks on public computers or other networks. Nyttend (talk) 19:22, 28 February 2017 (UTC)
That's what it says at the IPBE page, must be outdated. Beeblebrox (talk) 19:35, 28 February 2017 (UTC)
The IPBE page pulls directly from ListUsers. Special:ListUsers/ipblock-exempt does show ~140+ usernames.  · Salvidrim! ·  19:51, 28 February 2017 (UTC)
Silly me — I just discovered my mistake. I reached the final page and ran a search for (IP block exempt), which returned thirteen results, but of course it doesn't count users who have other rights as well. Nyttend (talk) 20:00, 28 February 2017 (UTC)
I think we need to start by accepting that with a certain level of dedication and sophistication, a sockmaster will be able to avoid all of our technical means of detection. I'm not going to spill the WP:BEANS, but its out there. Actually they can already do this with IPBE, if they are willing to put the time and effort in necessary to pass an RFA. Luckily, the number of sockmasters that are willing to make that effort to do either is small enough that we really don't really worry about it. So if we were talking enough edits to be in RFA territory, we are setting the bar high enough that few sockmasters would be willing to make the commitment. At that point the risk is really previously good editors who turn to socking after already meeting whatever criteria we set of IPBE. But there really isn't much we can do between just accepting that risk, or just saying no... The only thing I can come up with would be to restrict IPBE editors from editing in sensitive areas (noticeboards/areas with sanctions/related to arbitration) when using a VPN, such that either socking or violating this rule could be detected by Checkuser. Personally, I'd accept the risk even without such a restriction, and support something in the neighborhood of 20k edits & 2 years as a guideline for waiving the "need" criteria in an IPBE request. Monty845 04:39, 28 February 2017 (UTC)
20K might be a bit much. I've been here for 12 years and was active for at least 7 of them (not consecutively) and I've only got 5K. Maybe 20K is easier to get now than it was a few years ago though. Either way, seems a bit steep to me.--*Kat* (talk) 09:24, 28 February 2017 (UTC)
I think you've got something here. This would be easier to implement and would not require a lot of admin time. Beeblebrox (talk) 19:37, 28 February 2017 (UTC)
It's more of a mindset change. (And coding tweaks to ProcseeBot probably).  · Salvidrim! ·  19:51, 28 February 2017 (UTC)
It would make socking marginally easier, as one could create an account from some clean/public location, and then sock from home via VPN. I don't really know how big an issue that would end up being... We could probably do a softblock trial and just make sure we can easily roll it back if we see a flood of socking... Monty845 23:35, 28 February 2017 (UTC)
Dedicated sockers are already finding plenty of ways around the roadblocks we try to impede them with, so I don't foresee this option changing much. Miscreants with too much time on their hand have always and will always continue finding ways to haunt the project no matter what we do.  · Salvidrim! ·  01:30, 1 March 2017 (UTC)
(edit conflict) So at this point, I've stopped going after most webhost blocks for a year or two now at least, UNLESS I see abuse of the range. So all my blocks over these past 2 years are because of abuse. Futhermore, People ask me to go block the potential proxy that users rotate through like they get new IPs at the push of a button, I refuse as it's a waste of my time. So that's a lot already thats left open.
The reason I set them to be webhost blocks is so that any admin who is informed on proxies can make a legitimate change to them, otherwise, you'll just see me going right back to checkuser blocks on the ranges, which then increases the additional load on checkusers with block appeals that aren't worth the money they were written on, as it's harder to tell a legitimate user from a sockpuppet. Don't belive me? Read back to 2013 where I had a week and a half of hell and was berated for my well-intentioned actions. Post that, it then proceed through a month long audit of my actions. That said, reading through, I got a lot more support than I had realized, but I still only remember the bad end of it 4 years later, and it's molded into me hard. I've also had several more recent cases where the user gets upset when I ask them about their editing on a proxy, as they think they are exempt from such investigations having IPBE.
If the community wants to allow clear use of IPBE for any established editor on the fact that they want a VPN, then i'm going to be walking away from any investigations that involve webhost/proxy usage as a CU. This will only result in more "established user" sockpuppets from getting through. It's extremely hard for me to tell if Joe 1 is a different person from Joe 2 on a webhost/proxy, if they use the same software. Without the limit from people using a VPN...there is no point to CU investigations on VPNs. So you'll have more evasion, more major sockmasters getting away (including extremely abusive ones), and more community members frustrated over the lack of good that checkusers can do or have the ability to investigate. If your going to force the softblocking of proxies and webhosts...the same thing applies.
To be clear, if someone has a pressing issue that requires the privacy of a VPN, I do not hesitate in granting IPBE either. So I ask to trust your checkusers to handle the private request reasons and assign IPBE when appropriate. -- Amanda (aka DQ) 01:46, 1 March 2017 (UTC)
Trust the government...they're here to help.  :-P --*Kat* (talk) 01:36, 2 March 2017 (UTC)
On a more serious note: It isn't that I don't trust you. I just don't understand why I should have to justify my decision to use a VPN.--*Kat* (talk) 01:36, 2 March 2017 (UTC)
  • For the benefit of the closer: I would also Support the suggestion as proposed, to allow IPBE to be granted more freely to established users. It's not my preferred solution as explained above but it's a solution I can still support.  · Salvidrim! ·  16:50, 3 March 2017 (UTC)
@Someguy1221: So you are against it just because you don't see a pressing need for it?--*Kat* (talk) 04:33, 1 March 2017 (UTC)
You're right, they just go and find an admin who is willing to do it. I also frequently forget the last step, most CUs do. And I think one big issue around this is define long term/established/whatever. Long term users won't ask for this to sock, my experience is when they are already socking or they won't ever sock. -- Amanda (aka DQ) 04:17, 1 March 2017 (UTC)
I'm not sure I do either. Others have said it is because they wish to maintain their privacy, but if you are just a username on a screen, only a CU can find out anything you don't tell them yourself, and a CU will only look if there is reason to suspect abuse. If instead you are frequently caught in blocks intended for others, that is already a valid reason to grant IPBE. On the other hand, all admins get this by default and don't have to justify using a VPN, ever. Beeblebrox (talk) 23:56, 1 March 2017 (UTC)

As described in a document saved by GCHQ, Palantir fielded a team in 2008 and tackled one such scenario using its own software. It was a powerful marketing opportunity at a conference filled with potential buyers.
In the demo, Palantir engineers showed how their software could be used to identify Wikipedia users who belonged to a fictional radical religious sect and graph their social relationships. In Palantir’s pitch, its approach to the VAST Challenge involved using software to enable “many analysts working together [to] truly leverage their collective mind.” The fake scenario’s target, a cartoonishly sinister religious sect called “the Paraiso Movement,” was suspected of a terrorist bombing, but the unmentioned and obvious subtext of the experiment was the fact that such techniques could be applied to de-anonymize and track members of any political or ideological group. Among a litany of other conclusions, Palantir determined the group was prone to violence because its “Manifesto’s intellectual influences include ‘Pancho Villa, Che Guevara, Leon Trotsky, [and] Cuban revolutionary Jose Martí,’ a list of military commanders and revolutionaries with a history of violent actions.”

That said, I should mention I have substantial reservations about VPNs. The ideological leader of the world, China, has already begun substantial and effective crackdowns on VPNs. The powerful elite behind omnipresent copyright surveillance in the U.S. certainly likes them no better. The VPNs may promise to limit record-keeping, yet all of them know that their days are numbered and in the end their best hope to make money and avoid prosecution involves some kind of deal involving those records. And using one provides extra documentation of identity and communications. I therefore don't mean to recommend them like they were a silver bullet, but ideologically I would like to see Wikipedia step out of lockstep with the computer surveillance state. Wnt (talk) 18:03, 2 March 2017 (UTC)
@Wnt: The level of non objective content in your comment above is concerning. Wikipedia and its servers are guests of a State for which you speak against. The way you have phrased this post seems to suggest that Wikipedia should be at odds with the State that hosts it, not only is this extremely dangerous but also seems to violate the principle that Wikipedia is not an experiment in anarchy. I agree that VPN use should be unrestricted but only on the principle merit that it cannot be avoided and thus methods that work either need to be implemented to completely stop VPN use for everyone or it should be available to anyone. A failed system is a worse example than no system at all and if the system is required by practical need then it should be implemented to at the very least, work. Now anarchy is not the aim of the game here nor is it to try and counter Government surveillance of the country which implements this according to its Laws which are the same Laws the Wikimedia foundation is governed by. ὦiki-Coffee(talk to me!) (contributions) 01:08, 3 March 2017 (UTC)
Let's try to avoid arguing general political ideology unless it really can't be avoided. This is a discussion about Wikipedia practices, not about how we feel about the State. --Trovatore (talk) 03:50, 3 March 2017 (UTC)
@Wiki-Coffee: Wikipedia is not a "guest" of a State - it was founded and run by citizens of a State, who have rights. If that State were to make a law that forums cannot allow people to post if they come from a VPN, or unless they sign up with their official ID cards and identity verification fob device, well, then that would be a law, and WMF might follow it or take it to the courts. (I'd predict B, wouldn't you?) But until such time, if the State is going to set up a "voluntary" surveillance program, or if other States run surveillance abroad, we have the choice whether we want to help that or not. I'd say B again. Wnt (talk) 16:14, 3 March 2017 (UTC)
@Wnt: I think that I can understand your point. Basically, we should accommodate the needs of people who are so vain that they genuinely believe a countries government would be interested in them for no reason and that supporting the needs of paranoid and irrational individuals is of greater importance than protecting the integrity of Wikipedia by preventing sock-puppetry and POV-Pushing from socks. ὦiki-Coffee(talk to me!) (contributions) 18:28, 3 March 2017 (UTC)
@Wiki-Coffee: This sort of "paranoid and irrational" namecalling never deserved respect, but today... have you ever heard the name Erdogan? Have you encountered articles like [27][28][29][30]? Modern mass surveillance goes a hell of a lot further than the occasional Marcus Garvey - the example I give is of a whole country where people thought they had a "democratic" society and now anyone accused of reading the wrong book or talking to the wrong person is living in fear. And ... even now, Turkey is still reckoned one of the freer countries in the Middle East, God help the poor bastards. Now - people hope that thinking that way would be paranoid for Americans, but who knows? It takes all types to make a balanced social ecosystem. If some people encrypt their communications and cache guns in the desert, maybe the rest of us won't need to have done so. Wnt (talk) 20:23, 3 March 2017 (UTC)
I am confused how concerns about privacy over public networks, unsecured WANs, and ISPs became a discussion about state surveillance. While there certainly are justifiable concerns about surveillance from government parties &endash; local law enforcement Stingrays, federal spying programs, international espionage, or editing behind a national firewall &endash; often the primary goal in using a VPN is to prevent private, non-governmental parties, from obtaining unsolicited access to information. Sławomir Biały (talk) 14:34, 4 March 2017 (UTC)
@Sławomir Biały: There is a smooth gradient between public and private spying. For example, see the conflict HBGary and "Anonymous" hackers - was that a public or a private action? Business is crime is law. Wnt (talk) 12:06, 5 March 2017 (UTC)
I'm not disagreeing, but dismissing concerns over privacy as anti-government paranoia seems to miss the point. Data is stored and shared by many parties, most of which are actually private entities. It's the weakest links in that chain that we should be concerned with. That might be a local law enforcement Stingray, or a poorly secured WLAN in a coffee shop. By saying that we don't want "government" to have access, most folks take that to mean the NSA. That just invites spurious arguments like "If you aren't doing anything that would place the national security of [...] at risk, then you have nothing to hide." The point is, everyday citizens should be concerned with their privacy, and not because of the NSA. However one feels about the Men In Black, there are plenty of (other?) bad guys out there to be worried about. Sławomir Biały (talk) 14:51, 5 March 2017 (UTC)
  • I'm not sure I understand. None of Guy's remarks indicated that he wants admins to ignore WP:DUCK and act as a rubber stamp. Nor does he suggest that editors should or will go admin shopping in a quest for approval.--*Kat* (talk) 17:49, 3 March 2017 (UTC)
  • He isn't disagreeing or agreeing with me. He is answering my question ("If anyone thinks that what I just wrote is not what this particular section of this RfC is asking, let me know and I will post Yet Another RfC.") by saying that there is at least one person who thinks that what I wrote is not what this particular section of this RfC is asking. Make that two, because I agree with him on that point. Clearly, a more carefully worded RfC is needed, which will appear shortl as soon as my nimble fingers start typing it in a new section. --Guy Macon (talk) 19:38, 3 March 2017 (UTC)
  • No admin can ever be positively required to take an admin action. We can always decline to push a button. So I can always answer a request to give IPBE (or any other user right) with "Sorry, but I'm not comfortable doing that." Seraphimblade Talk to me 23:20, 3 March 2017 (UTC)

Proposed draft of new policy

Draft withdrawn

With respect -- and great appreciation for his support -- to Guy Macon I'd really rather us not get bogged down in a discussion on what we should discuss next in this discussion on changing the IPBE policy. so, if I may, I'd like to proposal a revised policy here.

Current wording

Editing via an anonymous proxy can be easily abused, so it is only granted under exceptional circumstances. Examples of editors who may reasonably request an exemption include users who show they can contribute to the encyclopedia, and (for existing users) with a history of valid non-disruptive contribution, but are either being hindered by restrictive firewalls, or for exceptional reasons must edit via anonymous proxies.

However, many users are known to access through open proxy unknowingly due to the default setting of their browser. Before you apply for IP block exemption (which may take time and is not guaranteed to be granted), you should check the internet connection preference of your browser and change it to no proxy access.

Note that avoidance of checkuser, or specific checkusers, is not usually considered a sufficient reason – concerns over checkusers should be discussed with the Arbitration Committee or ombudsman.

Who may request
An editor who has genuine and exceptional need, and can be trusted not to abuse the right.
How to request
Email the functionaries team or contact a CheckUser directly, explaining why you need to edit via anonymous proxies. Administrators who are contacted through other means may need to consult a checkuser to confirm the problem.


New Wording (proposed)

Editing via an anonymous proxy can be easily abused, and therefore will not be granted without deliberation. Examples of editors who may reasonably request an exemption include users who show they can contribute to the encyclopedia, and (for existing users) with a history of valid non-disruptive contribution, but are either being hindered by restrictive firewalls, or for reasons of their own, would prefer to edit while logged into a VPN.

Note that avoidance of checkuser, or specific checkusers, is not usually considered a sufficient reason – concerns over checkusers should be discussed with the Arbitration Committee or ombudsman.

Who may request
Any editor with an account that is in good standing and who has a significant history of positive (non-disruptive) contributions to Wikipedia.
How to request
Email the functionaries team or contact a CheckUser directly, explaining why you need to edit via anonymous proxies. Administrators who are contacted through other means may need to consult a checkuser to confirm the problem.

Okay...discuss. --*Kat* (talk) 22:05, 3 March 2017 (UTC)

edited to add part about significant editing histories--*Kat* (talk) 12:13, 4 March 2017 (UTC)

I think we need to treat those who cannot edit without a VPN (or equivalent) differently from those who could edit without one, but for any reason prefer to edit using one. We should only consider a request for IPBE from a new editor if they have a "genuine and exceptional need". The burden would be on the requester to provide justification. We should consider the request of an experienced and trusted editor without requiring them to provide any justification, though with an opportunity for discussion if anyone has a particularized objection to the editor receiving the right. There would be a reputable presumption that IPBE would be granted when requested by such an experienced editor. Monty845 05:20, 4 March 2017 (UTC)
  • Strong oppose Ladies and Gentleman, this proposal could be seen to be a violation of the principle that Wikipedia is not an experiment in democracy or anarchy.
Wikipedia is an encyclopaedia, a wonderful one at that. It’s a place for objective content which helps people access knowledge. Unless there is evidence to suggest that allowing wider access to IP Block exemptions, particularly to subjectively “trustworthy editors” is going to help Wikipedia by allowing for more useful contributions this policy suggestion is utterly redundant. ὦiki-Coffee(talk to me!) (contributions) 10:25, 4 March 2017 (UTC)
Coffee I would like for the VPN blocks to be done away with as well. But that proposal didn't achieve any kind of consensus. I was hoping that I'd missed something when Beetlebrox came out in support of the measure but judging from Amanda's response I didn't. Expanding on the IPBE is the next best thing -- and it is what has achieved has achieved consensus. Amanda can live with it and so can I. Since we are on opposite ends of this spectrum I think that means it has the best chance of actually effecting change. --*Kat* (talk) 11:43, 4 March 2017 (UTC)
  • Oppose (& proposing a rationale for closing this discussion without further ado) – I just had a look at Wikipedia talk:IP block exemption: seems the issue has been discussed for over a year, with multiple RfCs, the last one of these ending in a WP:SNOW close. When the topic was launched here at WP:VPP, no noticeable reference was made to that prior discussion (and its outcome), so to me this seems like a sort of ask the other parent, because if participants here would have been more aware of prior discussion I suppose this would have seen a WP:SNOW close long ago. Instead, we're just taking editors' time for something that sooner or later will receive its (half molten & watery, but predictable) SNOW close anyhow.
Now the reason why I went to look at Wikipedia talk:IP block exemption is that I was going to propose to close the discussions here at VPP and suggest not to come here again before at least at the IP block exemption talk page something would become apparent as not necessarily ending in a SNOW close. I still think that a good mode of operation: close this VPP discussion (and all other threads on the same topic). Keep discussions at the IP block exemption talk page until something with a sort of rough consensus there is worth taking the wider editor community's time for. --Francis Schonken (talk) 10:55, 4 March 2017 (UTC)
I did 'not' forum shop. I wasn't aware of the discussion on the IPBE talk page. I ran a search for "VPN" on the Village pump and skimmed WP:Perennial. Didn't see anything that fit. Which is when I posted here.--*Kat* (talk) 11:43, 4 March 2017 (UTC)
No problem. Just inviting to do so now (i.e. look at the previous discussions – I gave the links to the major ones below), and then see whether we still need to go through with this new extremely similar exercise. Well, anyhow, for the next time: if you want a guideline or policy to change it is *always* a good idea to look at the talk page of that guideline/policy to see whether someone else had the same idea before (and if so, how that idea was received by other editors). And not start a new discussion about the same at VPP without linking to the last one on the same topic. I.e.: the last *closed* one; if you'd come here when there's still an open discussion there it would definitely be forum shopping (*unintentional* forum shopping if you didn't take the trouble to look at the policy's talk page, but still something we'd try to avoid, have the same discussion about the same topic in two different places at the same time). --Francis Schonken (talk) 12:02, 4 March 2017 (UTC)
  • Strong oppose "significant editing histories" has been excluded, which was directly included above. If you want to reduce it to that and that gets passed, i'll turn in my checkuser bit. No way in hell is a new user going to get IPBE without providing a damn good reason for it. And i've only picked that single part out of more issues. -- Amanda (aka DQ) 11:30, 4 March 2017 (UTC)
My apologies. That was 'not' omitted on purpose. I was in a hurry when I typed up this section and clearly I should have waited until such time when i was not.
  • Comment Clearly I have made a mis-step. My intention was to come up with some verbiage that we could put on the IPBE page. I didn't expect everyone here to like it but I figured we could make more revisions and come up with something better, much like we did with the original proposal. I'm sorry. It wasn't my intention to sink my own proposal. --*Kat* (talk) 11:53, 4 March 2017 (UTC)
For clarity, continue to oppose the proposal after it was updated. --Francis Schonken (talk) 12:26, 4 March 2017 (UTC)
  • Oppose In addition to my comments above, m:No open proxies is a global policy. Therefore I do not support expanded usage of VPN's.--Jasper Deng (talk) 16:40, 4 March 2017 (UTC)
    • The Meta policy doesn't prohibit editors from receiving IPBE in order to edit via proxy, and it explicitly states that "legitimate users . . . are not the intended targets" of proxy blocks. Rebbing 17:05, 4 March 2017 (UTC)
      • @Rebbing: But it does give reasons for why open proxies are generally not allowed and why IP block exemption should be granted on a need, not a want, basis.--Jasper Deng (talk) 20:23, 4 March 2017 (UTC)
  • Support. Several of the reasons given for opposition don't hold water. @Rebbing: it is up to people at Meta to try to interpret their policy in a way to make some claim against this one based on it, and only after discussions there that, even if they find that, might choose to modify that policy not to conflict this one. We are making up our minds now and if they want to try to override us that is their crusade to fight. @DeltaQuad: "significant edit history" may not occur, but "a significant history of positive contributions" is actually more demanding. And as for whether there have been previous discussions -- we have seen that "consensus can change", too often for worse but in this case it could be for better. Wnt (talk) 19:40, 5 March 2017 (UTC)
  • I didn't propose that new wording. I'm fine with the basic significant editing history, so i'm not sure why I was pinged. -- Amanda (aka DQ) 22:11, 5 March 2017 (UTC)
  • Oppose as this would undoubtedly increase the burden on CUs per DeltaQuad. I'd prefer not to exacerbate the already difficult task of sockpuppet investigations by muddying the waters. (If a number of CUs voice the opposite to my assumption I would be happy to switch my !vote). --Majora (talk) 22:18, 5 March 2017 (UTC)

More discussion

Clearly I was wrong to try and draft a new policy. Or perhaps the big mistake was in trying to pound out a draft in the six minutes that were available to me before I left for work. Regardless it was a mistake. One made in good faith, but a mistake none the less. I apologize for contributing to the derailment of this discussion.--*Kat* (talk) 09:55, 6 March 2017 (UTC)

I still didn't see any reactions of yours to that closed talk page content (unless if I missed something). I'd be happy to know what you think. --Francis Schonken (talk) 10:10, 6 March 2017 (UTC)

Okay, I've read the entire talk page. It seems that there is pretty broad support (if not a true concensus) for the IPBE guidelines to be relaxed. However, the actual proposals to do so have all been rejected as too broad or too complex (although technically that one was SNOWed). Having read through the opposition's remarks for all of the proposals, I get the feeling that no proposal to relax IPBE would achieve consensus -- on that page, at least. --*Kat* (talk) 10:16, 7 March 2017 (UTC)

Hence my proposal not to come to WP:VPP with this issue again prior to reaching a rough consensus with the Wikipedia talk:IP block exemption regulars (there's a technical & general WikiMedia protection strategy angle to this that prevents any change without having the CU and related type of editors on board). --Francis Schonken (talk) 07:07, 9 March 2017 (UTC)
I'm hoping there won't be a "next time". If you look at the Restart section you will see where quite a few people (approx 66%) agree that merely wanting to use VPN shouldn't be a barrier to being granted a IPBE. What we lack is agreement on how the new policy should be worded. --*Kat* (talk) 09:10, 11 March 2017 (UTC)
Nah, in my appreciation the current WP:VPP discussion(s) on this topic is/are going nowhere, for lack of solid basis. So, whatever is debated and/or preferred here, the looks of it are that it won't lead to anything in terms of policy change while nor the current CU editors (on a local level) nor those responsible for WikiMedia's broader protection strategies are on board. Elegant way of saying: time sink, don't get your hopes up for change where it seems extremely unlikely. I'd have closed the whole thread on this basis if I hadn't been involved in these discussions. --Francis Schonken (talk) 09:26, 11 March 2017 (UTC)
I've asked Amanda to draft the new policy. I don't know if she will but I hope we can wait a few days to find out. --*Kat* (talk) 05:04, 12 March 2017 (UTC)
This is known as forum shopping. Don't do it. Above, I explained what forumshopping is, so I think the qualifier "unintentional" no longer applies. --Francis Schonken (talk) 09:43, 12 March 2017 (UTC)
Oh please. How the Hell is that forum shopping? I asked @DeltaQuad:to to come up with the new proposal because although she doesn't entirely agree with relaxing IPBE she seemed to recognize that this is what the majority of people here wanted. I figured that anything she came up with would be acceptable to all sides, provided that a desire to use VPN was no longer a hard barrier to being granted an IPBE. Furthermore, as a CU she understands the technical constraints that made other proposals unworkable.--*Kat* (talk) 21:02, 12 March 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.