Wikipedia:Village pump (policy)/Archive 133

Source: Wikipedia, the free encyclopedia.

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: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.

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

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

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

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)
  • Oppose I never understood why schools got a free pass at AFD. GNG and to a lesser extent SNG's work well for other articles and they will be fine in this situation as well. Many school articles I come across are nothing short of promotion as the only source of information comes from their own websites. AIRcorn (talk) 20:35, 9 January 2017 (UTC)
  • Information that meets policy requirements should be kept. If there's not much, consider merging, but if the amount is too much for the merge target then split. They should only be deleted if nothing is verifiable to our standards. I'm not sure if this is a support or oppose - as articles may be merged whether notable or not. For many of these articles this probably means keeping the article but removing anything that lacks references. Peter James (talk) 00:04, 10 January 2017 (UTC)
  • Support until a viable alternative becomes available. The trouble with SCHOOLOUTCOMES as stated is that we're talking about different sorts of secondary schools as if they're all on the same level; some classes of schools, such as American public high schools, will pretty much always be notable as important community institutions, while other classes, such as some of the for-profit schools mentioned above, need to be evaluated on their own merits. Unfortunately, public vs. private isn't quite enough to separate these; in certain parts of America, private schools (and Catholic schools in particular) are held in a similar regard as public schools, while in other parts they aren't, and that's just the situation in one country.
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)
  • Oppose per Sandstein and SamWalton. Merely existing should not make a school presumably notable. Blackmane (talk) 03:43, 10 January 2017 (UTC)
  • Conditional support - I would be in favour if the wording included "government accredited secondary schools". It doesn't matter if they are public or private. A stub with the school's name, location, private/public status, and grades accredited sourced to a government website, and an external link to the school's website if any, should be fine. Any promotional stuff or unsourced information can always be removed. About the academic example above: peer-reviewed journal articles have editorial oversight and also are reviewed by several independent experts, so if many of them cite a professor or researcher, that's a very large number of independent writers who agree that his or her ideas are important. —Anne Delong (talk) 03:50, 10 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)
  • Support, Considering only those schools taking pupils aged 11+ then the current situation seems to be accepted by most editors if one considers the total number of positive edits to such articles over time. As long as suitable references are available and listed correctly in an article then I prefer to maintain the status quo. I would be particularly concerned if the vote goes to the 'oppose' side that we suddenly find a huge number of deletions occurring. I appreciate that others have discussed this but it is still of concern as most editors will not be aware of this discussion. Paste Let’s have a chat. 15:27, 10 January 2017 (UTC)
  • Comment - While I'm normally in favor of
    csdnew
    16:08, 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)
  • Support although to be liguistically correct, my answer to this excellently neutrally made RfC question Should secondary schools whose existence is verified by reliable, independent sources be presumed to be notable? should be Yes. Not only through the already tacit consensus as evidenced by thousands of AfD closures resulting in keep but also based on the arguments above in favour of maintaining the status quo, while pointing out for those providing inaccurate reasons to oppose, that OUTCOMES is neither a policy, nor a guideline, nor technically even an essay or opinion piece - it simply accurately documents a set of clearly evident long-time Wikipedia behaviours, and as such is indeed an acceptable a short cut to the rationale it represents without voters at AfD having to post a list of several hundred or a thousand examples. Not without reason either did the community reach a well established consensus that school articles may not be tagged for deletion per A7, and it was a Wikipedia founder's express opinion that high schools should be considered notable. Naturally G11 and G12 and other criteria remain valid in appropriate cases and should generally be rigorously applied if editing cannot resolve the issues. School articles are not exempt from PROD and where most school articles are made by SPA, deletion by PROD makes AfD unnecessary.Kudpung กุดผึ้ง (talk) 21:10, 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)
  • Oppose Just like every other institution, a school-article should prove their notability, not their existence. And it should prove it with sources IN the article, not by assuming/gambling that sources exist. Schooloutcomes is one of the many locally (i.e. WikiProjects) invented excuses to circumvent the common rules for notability. The Banner talk 23:54, 10 January 2017 (UTC)
  • Support Following Graeme Bartlett line of thinking. I am though uncomfortable with making a definite statement on whether all schools in the 11 to 18 bracket should be considered notable but the alternative is far worse. Firstly, the current obsession with just testing against online sources, skews the debate in favour of a small number of geographic areas, and secondly while my personal POVs against non-state funded 'dame schools', crammers and grooming parlours does not mean that we should exclude coverage. But thirdly, the thought of nights of detailed arguments about whether a vanity funded academy is merely commercial placement or does have some notability.. doesn't bare thinking. --ClemRutter (talk) 01:18, 11 January 2017 (UTC)
  • Support I have always supported this tradition for multiple reasons, most of which have been articulated already. It recognizes that high schools and colleges virtually always receive coverage (and if it's purely local, what's wrong with that?). It saves enormous amounts of quibbling over what sources are acceptable and what aren't (if most of the coverage is about the football team, does that count?). It avoids systemic bias, as noted already by many (sure, American schools can always cite online references in English, but how many other countries can say the same?). To me it is like the SPORTS notability guidelines: if a person has played in a fully professional league, they get an article, no quibbling, no agonizing - because such players have virtually always received coverage, and with the guideline it isn't a matter of debate in each and every instance. BTW my understanding is that this guideline applies to "diploma-granting and degree-granting institutions", not just schools for ages 11 and up - thus ruling out middle schools, trade schools, etc. I would support adding "accredited" to the guideline, although it may not always be possible to provide a link to the accrediting agency and I would not require that. --MelanieN (talk) 01:44, 11 January 2017 (UTC)
  • Support status quo Beyond My Ken (talk) 04:58, 11 January 2017 (UTC)
  • Support If people would really like to double the amount of work at AfD, then a good way of doing it is to remove the practice of treating secondary schools as if they were notable. The practice that we do so is not an attack on the fundamental principle of WP:N or the GNG, but a question of convenience. In that connection, I have to mention the other half of the compromise : not usually treating elementary schools as notable. Before we had the compromise, I and others were quite willing to argue for their inclusion. Some of the arguments were successful, and I have a few hundred US primary schools in mind for which I could realistically try to write articles. The results will, as usual at AfD, depend on who shows up to discuss, as much as on the merits of the article. DGG ( talk ) 05:12, 11 January 2017 (UTC)
  • Support. I'm a long-term supporter of this rule for the reasons elucidated here. -- Necrothesp (talk) 13:40, 11 January 2017 (UTC)
  • Support this seems to be the way the community generally regards the notability of schools so it it is appropriate to confirm the situation. Thincat (talk) 16:11, 11 January 2017 (UTC)
  • Oppose schools shouldn't get an automatic free pass at AFD, and merely being mentioned in secondary sources isn't good enough to warrant an article. Actual depth to coverage in such sources is also a must. We shouldn't ignore any instance were WP:GNG isn't met. In all honesty, this is why the mentioned bit above from WP:SCHOOLOUTCOMES is fucking bullshit. I also concur with Sandstein, Masem, The Banner, Jonesey95, and Czar. Snuggums (talk / edits) 20:32, 11 January 2017 (UTC)
  • Support with hesitation, because I've sounded off in the past about the lamentable quality of many school articles, which are often the last ones we would pick as models or training grounds for budding new editors. So I'm more bothered about what's in these articles than whether they exist at all. I hear those who are unwilling to make further exceptions to the GNG, but the fact is that with schools that bird has flown, long ago, and I can swallow a special status for schools similar to that for villages or pro footballers. The hope would be that once this special status is recognised and regularised, editors would be more willing to bring the articles up to standard. This means: trim promotion and non-neutral prose, trim excessive, trivial and evanescent detail, look for whatever useful information can be found in independent reliable sources, and watch out for those vandals: Noyster (talk), 01:04, 12 January 2017 (UTC)
  • Oppose any form of "inherent notability" for anything. Notability comes from being noted, no more, no less. Schools are long overdue for a cleanup, and in practice, many of them are not notable. There are certain cases where we really can presume every single example of something to be notable (US presidents, chemical elements), but it doesn't hold true with schools. Some are notable, some not. Seraphimblade Talk to me 01:42, 12 January 2017 (UTC)
  • Support - not wanting to repeat what's already been said: briefly, I think the trade-off here between WP:SYSTEMICBIAS and GNG is acceptable. Eustachiusz (talk) 03:49, 12 January 2017 (UTC)
  • Oppose - The GNG would be a much better tool for determining secondary school notability. I really never understood why secondary schools were given a free notability pass to begin with. If they can't meet the GNG, I don't understand how we could hope to write a balanced, encyclopedic article about the school. Wikipedia isn't a simple directory, after all. Kaldari (talk) 07:10, 12 January 2017 (UTC)
  • Support maintaining the status quo. We have had a compromise here for years: verified public and sizeable private and parochial high schools are routinely kept, while primary schools are routinely redirected to their school district or city unless solid evidence is provided to warrant keeping a standalone article. This has worked well for years, while saving us from many endless re-debates about the arcane subtleties of Wikipedian terms of art. "Notability" is not a goal in itself but a linguistic device for discussing whether something will improve the encyclopedia. I acknowledge that the boundaries have been tested and stressed by promotional, COI-driven articles about for-profit schools and a more focused discussion about best practices for handling those promotional articles may be in order. The rest are something we should keep and cultivate. The encyclopedia would certainly not be improved by delegitimizing the high school articles we have. This large category of existing articles is a positive not only for the readily-organized information the articles provide to readers and contributors, but also for its developmental benefits to the project: they are a strong component of the deep, worldwide, gazeteer-like coverage that is one of Wikipedia's best features and aspirations, and as PamD noted above they also provide a means of entry and connection to the project for many new editors. --Arxiloxos (talk) 01:06, 13 January 2017 (UTC)
  • Support the status quo. In its absence we will be flooded with malicious AfDs, and waste far, far more of editors time. We need more "automatic" notability decisions not less. Every silly fight that can be avoided makes the community look less .... silly.
    talk
    ) 01:12, 13 January 2017 (UTC)
  • Support keeping all secondary school articles for now. We might need to figure out a more nuanced solution for certain parts of the world where very limited verifiable information about schools is available. But I would certainly oppose a change to this rule, at least for developed Anglophone countries, where there is usually plenty of verifiable information about schools. I think further discussion about how to handle the different scenarios in different countries, culminating in an agreed subject-specific notability guideline, would be more productive than an all-or-nothing !vote. — This, that and the other (talk) 01:28, 13 January 2017 (UTC)
  • Support the status quo - While in theory
    WP:GNG should be applied to most subjects, User:TheCatalyst31 brings up a great point in how AFDs get difficult. Many people are not so educated, and they may not have time/money to comb through sources all the time. People get grudges if their content is deleted; nobody likes to work hard on something and see their work vanish. Even if the content is not well sourced or not notable, people feel that Wikipedia's not living up to the "Encyclopedia anyone can edit". Of course we shouldn't allow blatant promotionalism (especially from for-profit companies) and some subjects are just not encyclopedic. However as stated on the AFD of the British International School Lagos it often is possible to get info on schools, especially state-run ones. Maybe a better idea is to publish a guide on how to source info for schools in X country, how to find libraries, etc. Make a guide for high school students (the people who we need to recruit as editors, and in fact much of my editing is done for this purpose!) on how to write about their school: How to get sources, what style they should use, etc. I'm happy to start it myself, and for North American students, add how to use boundary maps to determine which communities serve their public schools. WhisperToMe (talk
    ) 09:14, 13 January 2017 (UTC)
  • Undecided – Of note is that per
    WP:FIVEPILLARS, Wikipedia functions in part as a gazetteer, and some gazetteers have historically included content about schools in them, such as in Chinese, Indian and Korean ones, among others (see the Wikipedia gazetteer article for more information and sources). For example, the Gazetteer of the Nellore District published by the Government of Madras in 1942 includes content about secondary schools and middle schools (see Google Books preview example, scroll down on page). The World-wide Encyclopedia and Gazetteer published by the Christian Herald in 1899 contains content about secondary schools (see example, pp. 1042–1043). Another example is the Alexandria Digital Library Gazetteer Content Standard (link
    ), which includes schools in its formulation. More examples in addition to these are available in online searches.
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 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)
  • Oppose SCHOOLOUTCOMES must die! It may have been usefull way back in the infancy of WP, but the way it is commonly applied these days has several negative consequences:
    • It privileges first-world, and more specifically American, high schools. This is a consequence of the (practically) unique obsession with school sport in American society. The smallest "Anytown High" is practically guaranteed regular coverage in the "Anytown Gazette" reporting on the appointment of the new basketball coach or the progress of the school baseball team in the state championship (even if they are ranked 236 out of 242). Contrast that with the situation in many other countries where even the barest hint of proof of existence can be hard to find - and then often only in the local language in a list on an obscure government website or a mention in a report or policy document. Thus it actually exacerbates the
      systemic bias
      of en.WP.
    • It is used as a weapon to summarily shut down anyone daring to question the existence of any high school article, regardless of the quality of the article or the merits of the argument. This is often counter to
      WP:RETENTION
      of editors, particularly the scarce ones from underrepresented countries and demographics.
    • An SNG creates a presumption of notability, not the fact of notability. Any presumption that is not suceptible to testing and consequent possibility of rebuttal is not really a presumption at all. SCHOOLOUTCOMES is often used to basically forbid any testing of the presumption. Countless speedy deletions are rejected and AFDs are summarily closed citing it - a rather bizarre
      WP:ORG standard. Roger (Dodger67) (talk
      ) 13:38, 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)
@
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)
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)
WP:NOTDIRECTORY is a better fit, you are correct. Roger (Dodger67) (talk
) 18:43, 19 January 2017 (UTC)
  • Support Schools in English-speaking countries such as the UK are subject to independent inspection and testing. This provides a good body of source material and so we may safely presume that there's an adequate basis for coverage here. Andrew D. (talk) 13:28, 17 January 2017 (UTC)
  • Oppose. Partly per Sandstein and partly per those who say some version of no inherent (or presumption of) notability.--Bbb23 (talk) 15:05, 17 January 2017 (UTC)
  • Oppose along with some history: In many countries, such as the United States, almost all schools that have the "highest grade" of secondary education would easily meet
    WP:N (e.g. it is a type of school where schools get scant attention from the local press), then the absence of proof along with a small amount of research by an editor seeking its deletion should be grounds to not presume it is notable. davidwr/(talk)/(contribs
    ) 17:56, 18 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)
  • Oppose - Sandstein says it well, and plenty of others have added other relevant points. Consensus is not carved in stone and this project as a whole needs to improve upon the practices of its early days. - Sitush (talk) 01:11, 20 January 2017 (UTC)
  • Support - We keep high schools for very good reasons; not only do they influence the lives of thousands of people but they also play a significant part in their communities. To consider deleting articles on such significant institutions is, frankly, bizarre. Just Chilling (talk) 04:25, 20 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)
  • Informal Support for African Secondary schools, Oppose for other territories: Secondary schools are essentially not news-worthy in many climes. They also lack competitive drive due to thier non-profit nature, as least from my side of the world. Most of what makes other institutions get reguslar coverage in relaible sources doesn't really apply to secondary schools. I'm not saying all educational topics must have this special treatment on wiki but I am of the opinion that an exception should be created for universities and secondary schools, which are part of the standardized mechanism in formulating the educational being of any individual. We don't expect to find multiple significant coverage for Nigerian secondary schools before accomodating them here.
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 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 ) 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)
  • Echoing CalzGuy on it currently trending "no consensus". Regardless of how this RfC closes, even if it closes as support, I think SCHOOLOUTCOMES is no longer workable, and there will need to be further discussion on how exactly to implement the consensus here, or in the case of a no consensus close, to try to arrive at a guideline for schools that can achieve broad community support. TonyBallioni (talk) 18:27, 9 January 2017 (UTC)
  • I agree that there will probably have to be further discussion about where to go next, whichever way the RfC closes, but it's still early days - I can see this one running for a while. Cordless Larry (talk) 18:32, 9 January 2017 (UTC)
  • ? If this is voted down, it will just be another proposal not included in the guidelines. One does not make a consensus by people not voting for something, they make a consensus getting people to vote in favor of something. It will be as it always has been, the edge cases will sometimes get fought about, and the schooloutcomes out so that fights don't have to happen over and over again will be generally followed for the rest. The schooloutcomes thoughts and what gave rise to it are not going to magically disappear. The reasonable improvement from present would be to have a school sng: eg. 25 years, 500 students, acreditation, reference in such and such sources, etc., etc. but obviously that depends on someone really working on it. Alanscottwalker (talk) 18:45, 9 January 2017 (UTC)
    • The way this is being presented, if it passes with Support, then what is at SCHOOLOUTCOMES should be codified better at WP:NORG ("All verified-existing secondary schools are presumed notable"), removing the language at SCHOOLOUTCOMES as duplicative at least with respect to secondary schools. If this passes with Oppose, then the language at SCHOOLOUTCOMES should be changed to reflect that secondary schools are not presumed notable just by sheer existence. --MASEM (t) 19:00, 9 January 2017 (UTC)
    I would go farther and say if this is no consensus SCHOOLOUTCOMES as something that can be referenced in AfD is in shambles, and there would probably need to be more work done on crafting a guideline that could get community consensus on schools. SCHOOLOUTCOMES has the somewhat weird place in AfD because the idea is that it represents a longstanding community consensus on schools. Anything short of a support close here would be a rejection of that idea. TonyBallioni (talk) 19:09, 9 January 2017 (UTC)
    This RfC has already attracted far more comments than the average school AfD, so if consensus either way is reached here, then I would argue that it is more representative of the community's views than any assessment of AfD closes would be. Cordless Larry (talk) 19:12, 9 January 2017 (UTC)
    No. Schooloutcomes is, as the name says, about outcomes, the only way to change that is actually have mass deletions at afd. (and really, no matter how many comment, you don't get a backdoor consensus by finding no consensus or opposition on specific wording of a new guideline, no one has ever proposed before, and never bothered to refine.) -- Alanscottwalker (talk) 19:17, 9 January 2017 (UTC)
    Key is that SCHOOLOUTCOMES is an essay, and it has been used (or misused, depending on one's POV) at AFD to keep articles on schools as the sole argument. It's working on a catch-22 approach: "keep this article on a school because school articles are routinely kept", and allowing those AFDs to close without any attempt to show actual notability or additional sourcing. This RFC seems to be stating do we actually bite the bullet and say that secondary schools should be presumed notable and eliminate the catch-22 , or do we say they are not and eliminate the catch-22 the other way. And as Tony points out above, even a "no consensus" should lead to discussion about what to do about the catch-22 problem. --MASEM (t) 20:32, 9 January 2017 (UTC)
    That's not a Catch-22, even if that word was not overly dramatic, it is another beloved bugbear of Wikipedia, 'consistency', and sure we generally really want to be consistent - to treat like, like - because that is a basis for being neutral and fair (until we are not). You do get a chance to discuss it every-time at Afd, but Afd like every process looks for both a consistent application, and the reduction of transaction costs (eg., don't have lengthy fights about the same thing, again and again). Alanscottwalker (talk) 20:47, 9 January 2017 (UTC)
    But that creates the problem emphasized by the two linked AFDs: resting the argument against the deletion on an essay that describes a practice as to maintain that practice is a self-fulfilling cycle. The closures of the AFDs and the subsequent discussion show it is time to either cement that practice in notability guidelines or get rid of it as to break the cycle. --MASEM (t) 21:17, 9 January 2017 (UTC)
    SCHOOLOUTCOMES has a bunch of other uses, including suppressing the addition/supporting the deletion-or-merge of numerous primary/elementary school articles. We need to ensure that this continues to be the case, whatever the outcome here. CalzGuy (talk) 20:16, 10 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: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)
  • Comment: Supporting SCHOOLOUTCOMES only because we're scared of the amount of work that would suddenly pop up if it is abolished doesn't make sense. Setting up a separate stream for such deletion discussions, so as not to block up the "normal" AFD stream is trivially easy. It will do no harm if we take months, or even a year or longer, to clear out school pages that might no longer qualify for inclusion. Roger (Dodger67) (talk) 10:21, 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)
  • Comment About two years ago, the notability requirements for planets was readjusted, which resulted in hundreds if not thousands of planet articles being nominated for deletion. I was working at AfD at the time, and can attest that going through all of these deletions was a bloody nightmare. However, the majority of the planet articles were non-controversial redirects since they lacked any coverage in reliable sources (or at least beyond a few trivial mentions that confirmed the existence of the planets). This meant that non-admins such as myself were able to substantially help with the workload. With secondary schools, I highly doubt this will occur. At least in the United States, high schools get tons of coverage at the city, township and county level. However, most also receive at least some coverage (of debatable worth) from sources at the state and federal level. There are going to be very few non-controversial AfDs, and the burden of closing them will fall on the admins. WP: AfD will likely be completely and utterly clogged for the foreseeable future if this discussion does not reaffirm the current consensus regarding secondary schools. (I’m not exaggerating here- we have articles on over one-hundred public high schools in the state of Iowa alone, which is roughly the twentieth least populated state in the US). Given this, I believe that some concrete steps need to be taken to keep wp:AfD functional. Spirit of Eagle (talk) 00:18, 22 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
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)
  • Comment about closing - We're still a ways from the 30-day mark, but when the time comes what do people think about requesting a team of three uninvolved editors/admins to work together on the close, as is done from time to time on highly contentious matters. This is something that's come up so many times, and so often, and with so much history that it may be useful. Numerically, at time of writing, it's just about even between support and oppose, which may mean no consensus, but there are nuances, qualifications, interpretations, etc. that suggest something may come out of it. — Rhododendrites talk \\ 15:43, 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)
  • Comment As I suggested earlier, I don't think there should be any outcome from this RFC other than a Nc close, as I think that, with all due respect to the OP, it asked the wrong question. We need an RFC that asks the right question, actually a positive change from observational essay to an agreed policy or guideline. The oppose camp see SCHOOLOUTCOMES as a pseudo-guideline being used to prop up non-notable additions to the project, while supporters see it as a description of the actualité of AFD. It would be much better to define what SHOULD happen at AFD rather than describe what HAS happened previously CalzGuy (talk) 07:14, 31 January 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
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)
  • Assuming the closer has read this far, this RfC is as long as it is short, is as broad as it is narrow, and as skewed as it is straight - on two major points:
  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)
  • There should be a TL;DR summary of this close. My read is; secondary schools are not presumed notable by existance. SCHOOLOUTCOMES can be cited at AfD but may be discounted by the closer. Editors should make a good faith attempt to find sources in local media before nominating a school for deletion. A flood of school nominations in the wake of this close is discouraged. I am sure others took away something different so the closers should write a clear, citable/quotable summary so this does not spawn endless drama about what was meant. None of this is ment to detract from the hard work the closers put into this but this is a topic which needs more clarity than can be found by interpreting such a long closing statement. Jbh Talk 00:58, 23 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
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)
  • The reason the closure is so hard to summarize is that it is not self-consistent. It seems to say there is first of all no consensus to change the statement that secondary schools are always kept if there's real evidence, but there is insufficient consensus to have a rule that they are presumed notable, and insufficient consensus to call anything Schooloutcomes. This ignores the basic principle of consensus, that if there is insufficient consensus to do or change anything, the situation remains as before, not the situation changes in some respects to the extent the closers think desirable. This leaves the matter in more confusion than before--especially so because it fails to take account of the strongest argument: that the rule is just a working compromise essentially balancing keeping secondary schools and redirecting primary schools, and need have no justification except that it works for Wikipedia. (And it does--imagine the entire discussion above needing to be repeated at every secondary and primary school afd--that's the alternative.)
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)
  • The default status of any image on Wikipedia is "not allowed to use it", the burden is on the uploader to prove its status is compatible with our license. See
    WP:IUP. --Jayron32
    14:34, 14 March 2017 (UTC)

Weather events and notability

I noticed there are already articles on serious winter weather events (ex.

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
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.
Robsinden, 9. Boghog, 10. Bkonrad
+1 IP

At issue is the propriety of employing {{

.

In closing the prior RFC, the closer (

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:

  • 2002 (the year after Wikipedia was founded) and onward (status quo at the moment)
  • The most recent ten years
  • The most recent 20 years, beginning with 2002 for now but moving each year after 2022
  • Some other standard

Discussion of scope of recent year guidelines

  • I personally think that the ten most recent years is a reasonable and manageable scope for these guidelines.
    talk
    ) 22:08, 13 January 2017 (UTC)
  • twenty years max ten years min I tend to consider anything older than 20 years history rather than recent events. I think having it apply to anything older than that is too broad. Likewise, anything in the last 10 years is pretty solidly "recent". Reasonable people will disagree about exactly where the cutoff should be, but I'd be in favor of any proposal within that range. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 01:04, 15 January 2017 (UTC)
  • 2002, but guideline should no longer be called "recent" years. It was "recent" when first proposed in 2009. Some guideline is appropriate for all years, and I believe the start year should be constant. — Arthur Rubin (talk) 07:22, 15 January 2017 (UTC)
  • 2002 for practical purposes, but I'd really like any year for which sourcing is available for this standards defined in the guideline to be met. Scribolt (talk) 10:00, 15 February 2017 (UTC)

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

  • I'm not sure I really have a strong opinion on this, but I do believe it may be wise to have a seperate discussion on the issue of the usefullnes of articles about events that may or may not be relevant 73 years from now. Seems like a case of
    talk
    ) 00:05, 14 January 2017 (UTC)
  • I tend to agree that we shouldn't have articles for years more than 10 years into the future; until a few weeks ago, there weren't articles for years more than 50 years in the future; until a few days ago, 70 years. But I think the guideline should extend as far as we have year articles.... — Arthur Rubin (talk) 07:28, 15 January 2017 (UTC)
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.
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)
  • Short term Applies to all year articles in the future. Medium term Update the guideline to remove future events Long term discussion need as per above as to whether we should have future year articles and what they should contain.
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 {{

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

  • A category seems rather obvious. It would only need to be updated once a year so it would be exceptionally easy to maintain. If the mechanism that would automatically link all three things is technically possible that would be helpful as well.
    talk
    ) 22:12, 13 January 2017 (UTC)
  • I think it should be a maintenance category, since readers wouldn't find our organization by applicable policies too useful. I think an edit notice would be useful, but I'm not sure how I feel about it yet. If there is consensus, I'd support automation. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 01:25, 15 January 2017 (UTC)
  • Yes, there should be an obviously visible link into the guideline. Scribolt (talk) 10:00, 15 February 2017 (UTC)

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

  • I think continents are a poor indicator for evaluating global relevance: something covered in the US, UK, and Australia alone would qualify. Number of countries might be a better indicator, though I'm not sure if it's the best. -- King of ♠ 05:28, 14 January 2017 (UTC)
  • I think it can be improved, but I'm in favor of keeping it until a solid improvement is proposed. I don't see the US, UK, and Aus example as a problem: coverage in all three shows that it's internationally notable for the anglophone world (which is what enwiki primarily serves). Going off number of countries would really privilege regional coverage over truly global coverage sinceis also being discussed countries close to each other will probably report on each other, and those should go in regional articles like 2004 in Europe. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 01:33, 15 January 2017 (UTC)
  • Needs to be some proxy for international significance; possibly, an item which belongs in a regional article shouldn't be here. I'm afraid that would be subjective, and probably subject to as the current regime as argument. — Arthur Rubin (talk) 07:51, 15 January 2017 (UTC)
  • As per Wugapodes. Could be better, will do until its improved by those closer to it. Scribolt (talk) 10:00, 15 February 2017 (UTC)
    • @King of Hearts:, do you mean all three of US, UK and Australia ("alone" to mean not including other countries in coverage)? Because that would be 3 continents... :-)Jack N. Stock (talk) 19:32, 23 February 2017 (UTC)
      • I'm sympathetic to Wugapodes's viewpoint that it may in fact be enough. But if something has only been covered in the American and Chinese press and nowhere else, I'd argue that it is at least as significant, if not more so, than something covered in the American, British, and Australian press and nothing else. So my primary concern is about the choice of metric rather than the cutoff used on that metric. -- King of ♠ 01:00, 24 February 2017 (UTC)
  • Pretty much everything of national significance in French politics would count, since France includes pieces in South America (French Guiana), Africa (Réunion and Mayotte), and North America (Guadeloupe and Martinique), as well as Europe. For a lesser issue, anything in Russian or Turkish politics being reported in North America or Africa would also qualify. If you want this kind of rule, you should specify something like "three different countries, each on a different continent". Nyttend (talk) 00:09, 1 March 2017 (UTC)
    • That also runs into difficulties, e.g. a minor international incident between Egypt and Israel reported on in those countries and Greece but nowhere else would qualify, but a much bigger incident between Zambia and Zimbabwe reported on in every country in sub-Saharan Afica but not further afield would not. Number of countries would be significantly biased towards European events as Europe has significantly more countries per km² than any other continent. Thryduulf (talk) 19:32, 3 March 2017 (UTC)

"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

  • I think the inclusion criteria for Births and Deaths might be a little too high; I understand that it is intended to counter systemic bias (in past years, Births and Deaths sections were overwhelmingly filled with people from the Anglosphere or Europe; some of whom had no interwiki links at all), but I fear that in the process it might actually enhance systemic bias, since I presume in many cases people from the Anglosphere or Europe would have more articles about them in other Wikipedias than those from non-Anglophone or non-European countries. How about lowering the requirement: instead of at least nine interwiki links, how about lowering the required number to five or six? I would agree with the current guideline provided that it should apply to people from the Anglosphere, but more leniency should probably be given (maybe on a case-by-case basis) to people from non-Anglosphere countries (i.e. China, Japan, Brazil, Kenya, etc.)
    csdnew
    16:43, 14 January 2017 (UTC)
  • What if we used similar standards as events? Rather than interwiki links, it's based on how international the coverage is. Or combine the two? The death is reported on in at least three countries/continents and has at least X interwiki links. Perhaps 3 so that significant figures in developing countries whose wiki may not be very robust can still be included if they're notable enough for inclusion in, for example, English, German, and French wikipedias. Wugapodes [thɔk] [ˈkan.ˌʧɻɪbz] 01:38, 15 January 2017 (UTC)
  • I think the criteria may be too lenient.... The "three continent rule" has been subject to debate before. The existing rule is objective. Still, a feel for what difference there would be for different options would be helpful in weighing alternatives. — Arthur Rubin (talk) 08:08, 15 January 2017 (UTC)
  • Lacking a better (more objective and/or easier-to-use) rule, I believe it is good enough, eventhough it's self-referencing in a way. Looking at the number of people included in the past few years, it could even be moved up a notch or two (i. e. 10 or 11 interwikis). — Yerpo Eh? 08:23, 20 January 2017 (UTC)
  • Silly criteria - many well known people only have articles written after they die in a language other than that native to the person. And does the mere existence of some stub in some other language elevate the otherwise locally known to worldwide known. Most other language WP's have similar notability criteria to the English language one. So putting "Joe Blow was an Olympic participant" or "Joe Blow was a professional <sport> player" or "Joe Blow was a member of the legislative assembly of state/province" translated into French, Spanish, German, Scots, Simple, and whatever Google translate would spit out, with a citation to something to show notability, on 9 other sites achieves instant qualification. Carlossuarez46 (talk) 02:54, 3 February 2017 (UTC)
  • Should focus on notability, not Wikipedia coverage (which sadly isn't always the same thing). No immediate suggestions though. Scribolt (talk) 10:00, 15 February 2017 (UTC)
  • The bit about "due to circumstance" ought to be relaxed; for example, the death of Florence Green, the final surviving veteran of World War I, belongs in the 2012 article: her death was much more significant than that of most figures on the list, e.g. an actor, a swimmer, or a football referee. Not sure how to relax it, however, aside from a general encouragement to treat certain high-profile deaths as events. Nyttend (talk) 03:09, 1 March 2017 (UTC)

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

policy
?

Discusion of Wikipedia:Recent years as an editing guideline

  • While I think more initial input would have been desirable, this has been used as an editing guideline for nearly eight years, so it should probably remain one regardless of how it got there int he first place, with tweaks as needed. Hopefully this discussion will attract more users to this area and consensus will be easier to determine in the future.
    talk
    ) 00:48, 17 January 2017 (UTC)
  • There seems to be debate as to whether it should be considered more than a WikiProject essay. I think it should be a guideline, but I believe there would be pushback if it were made a guideline unless considered now to be an essay and promoted to guideline. — Arthur Rubin (talk) 21:56, 23 January 2017 (UTC)
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.
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.
csdnew
00:43, 15 January 2017 (UTC)
  • I don't know quite what to do here, the idea was to get more users to comment on these things so we can say we have a consnesus one way or the other, but hardly anyone is participating. I put here instead of at RY itself and listed it at
    talk
    ) 23:19, 18 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.
Join WP Japan
! 23:38, 16 March 2017 (UTC)
And to specifically answer your question, the three lists mentioned are not copyright infringements. ···
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 ^
[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.
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)
  • Lists that are compiled from subjective criteria are considered copyrightable, and thus full replication of the lists are inappropriate without prior permission (as we have for the various AFI lists). Contrast that to lists developed from data (such as the top selling books or films), or lists from a rigorious voting process, such as a list of Best Picture for the Academy Awards - this is data and not copyrightable. --MASEM (t) 04:57, 17 March 2017 (UTC)
  • Yes. Generally, cvio. Alanscottwalker (talk) 15:25, 17 March 2017 (UTC)
  • Yes. In order for a list to not be copyrighted, it must:
  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)
  • Yes per Wikipedia:Copyright in lists, "ordered rankings based on judgement, such as the top 50 most influential Muslims" are copyrighted. The concept of the list may be notable but the ordered list itself is copyrighted and incompatible for sharing on Wikipedia without a wiki compatible license from the copyright holder. Blue Rasberry (talk) 19:12, 20 March 2017 (UTC)

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.

@

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
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: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.

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)
  • Oppose. This is the one wrong result. The reader is helped by consistency. These will alll be used in lists and categories, wherre consistency is particularly important. DGG ( talk ) 00:33, 6 February 2017 (UTC)
  • Support Although someone really needs to table an amendment to *policy* that states where MOS guidelines are disputed by local consensus, uninvested editors should back away. I would also support any MOS-update that states Railway article terminology has to comply with Thomas the Tank Engine. While I agree in theory with DGG above consistency in lists and categories can be important - lists and categories are not the primary function of an encyclopedia. Only in death does duty end (talk) 10:26, 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)
  • Support allowing both variants. Disputes can be settled by local consensus, after an examination of sources related to the specific railway or station in question. Yes, we will have a few difficult cases where the sources are not clear. Despite this, I think we should avoid adopting a "one size fits all" rule on this... because, whichever "rule" we adopt, we will simply end up with endless arguments about how our "rule" is wrong. In other words, we will end up with more disputes if we adopt a "one size fits all" rule than we will by allowing both variants. Blueboar (talk) 15:18, 6 February 2017 (UTC)
  • Both variants should be allowed. There is no extra "clarity" here - both clearly and unambiguously refer to something to do with a railway where the gauge is narrow(er) than some standard - that is undoubtedly why usage without hyphen exists in substantial numbers across the English speaking world, and it is well within standard written English grammar to drop unneeded hyphens. The claim of "consistency" is without merit as shown by the fact that we do not demand everyone write like everyone else (especially on something so wide-spread, and on an issue where insisting is so obviously narrow-minded and bizarrely inflexible.) We allow such minor leeway (and, indeed much larger leeway) for very good reasons too numerous and too embedded in our system of writing (although an article should be internally consistent). Alanscottwalker (talk) 20:00, 6 February 2017 (UTC)
  • Oppose inconsistency and ambiguity – no editor is being compelled or even asked to help, just to not interfere when things are moved toward compliance with the MOS, in favor of the interests of readers. Bermicourt started this mess by interfering after all articles had been made consistent, pretty much without objection except for his on Narrow-gauge railways in Saxony which he reverted back to hyphenless form (as he has a right to revert bold moves); so we went to discuss on the talk page there, and while that was not going in his favor he went and moved the rest of the articles about European countries, none of which had been objected to for a month. This is pure disruption, bad for the reader, bad for consistency. So now we're here, on advice of the closer there, to decide. So let's decide. Dicklyon (talk) 21:08, 6 February 2017 (UTC)
    • Bulldozing opponents might be fun in real life but it is extremely destructive at Wikipedia which relies on volunteers who maintain and build article content. Dashes are not as important as collaboration. Johnuniq (talk) 23:32, 6 February 2017 (UTC)
      Are you in the wrong section? Nothing about dashes is being discussed here. Dicklyon (talk) 00:11, 7 February 2017 (UTC)
  • Oppose. As this proposition is inherantly contrary to WP:Consistency, which is stated to be a policy document and thereby does not permit such latitude. Cinderella157 (talk) 08:05, 7 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)
  • Support allowing both per Blueboar. Mike Christie (talk - contribs - library) 13:19, 11 February 2017 (UTC)
  • Oppose – all "editor freedom" does is cause trivial content disputes and long AN/I threads. Laurdecl talk 08:00, 16 February 2017 (UTC)

Main RFC Survey

Please Support or Oppose including the hyphen in the titles.

  • Support. The list above clearly shows how it's easier for non-experts to pick up the word group if there's a hyphen ... not to mention our own style guidance and that of the style authorities on both sides of the Atlantic. Tony (talk) 09:10, 4 February 2017 (UTC)
  • Oppose There is a view espoused by a handful of hyper-active editors here that styleguides mandate all uses of a particular phrase and that any single deviation from this is some sort of thoughtcrime. That is nonsense: language is simply not that consistent. Nor does WP policy follow such a line, instead we have WP:COMMONNAME and WP:NEOLOGISM which state that WP should follow the practice in use, not mandate its own claims and force them on top of reality.
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
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)
  • Support—with the common sense recommendation that proper names be exempt.
    19:45, 19 February 2017 (UTC)

Threaded discussion

  • I don't really understand Andy Dingley's long opposing rant after he stated that he doesn't really care. In particular, I tried to be clear that hyphens are usually not used in proper names, so there should be no worry on North Wales Narrow Gauge Railways if it's the proper name of the subject of the article, and if it's not then it would be correct to fix the case, too. Dicklyon (talk) 17:38, 4 February 2017 (UTC)
    And that's the problem. You don't understand anything more than a simplistic one-rule-fits-all styleguide. Andy Dingley (talk) 18:09, 4 February 2017 (UTC)
    User:Andy Dingley, your posts are moving from low- to high-level irritability. It would be more productive if you were less personal. Tony (talk) 04:42, 5 February 2017 (UTC)
    Yes Tony, threatening people with Arbcom for disagreeing with them does tend to have that effect. Andy Dingley (talk) 11:26, 5 February 2017 (UTC)
    Andy, ignore it. You do good work on WP. You deserve to react calmly if the waters are ruffled. Tony (talk) 11:52, 6 February 2017 (UTC)
    I have no trouble at all parsing what Dicklyon is saying, which clearly indicates understanding of proper names and that a style-guide rule about hyphenation would not apply to one. It appears to me that the failure to understand or to be flexible is coming from the opposite direction, from individuals so used to and so personally invested in insider writing about the topic than they are unable to understand (or, much more likely, unwilling to concede) that they cannot force everyone else to write about trains the way a trainspotter would when writing for other trainspotters.  — SMcCandlish ¢ʌⱷ҅ʌ≼  22:50, 4 February 2017 (UTC)
    Well, it would make life a lot easier if you, Dicklyon and similar were simply banished from any discussions regarding MOS. Perhaps there are already restrictions - I don't know because every time I see such names at the Pump, ANI etc, I've tended to switch off after a few minutes of reading. - Sitush (talk) 00:35, 6 February 2017 (UTC)
    Thank you for lending credence to my comment about generalized anti-MoS ideology and personal vendettas. Your comment is not constructive. ―Mandruss  00:59, 6 February 2017 (UTC)
  • I'd just like to chime in here, as I do every time I see an argument about small horizontal lines, to point out that this is a ridiculous, pointless dispute that matters only to the people involved. I would suggest you host any further discussion in
    talk
    ) 18:53, 4 February 2017 (UTC)
    matters only to the people involved - I would suggest that people generally don't get involved in things that don't matter to them, so you could say that about any issue, making it unremarkable.
    I'll also note that this is not about hyphen-vs-endash, nor about spaced-endash-vs-unspaced-endash, which could be somewhat more easily dismissed as trivial pedantry. It's about clearly identifying an adjectival phrase as such for readers who are not familiar with the term "narrow gauge". Thus, argument about small horizontal lines appears to miss the point in a knee-jerk negative reaction to a legitimate MoS issue. ―Mandruss  20:29, 4 February 2017 (UTC)
    Agreed. However, Beeblebrox raises a valid point, in that these disputes are about trivia yet become disruptive when pursued, and seem to come up again and again. The typical pattern is that an editor doing
    WP:COMMONNAME), and they go that way whether dragged out over 30 RMs or settled in an RfC. It costs a lot less editorial time to RfC it, and sets consensus-determination precedent that is easier to find and more persuasive.

    It's also proven more effective to RfC these matters at VPPOL rather than at WT:MOS, because on multiple occasions the result of RfCs at MoS have been ignored by those who didn't get their way and the issue has been re-shopped in an "anti-RfC" to try to overturn it here at VPPOL (ironically, the "walled garden" reasoning Beeblebox suggests should keep MoS disputes at MoS tends to have the opposite effect). So, just cut out all the middle-man processes and do the one that matters most, for any titles/style dispute that gets entrenched and affects more than a trivial number of articles, if a multi-page RM fails to resolve the issue (or it is not limited to title disputes).
     — SMcCandlish ¢

     ≽ʌⱷ҅ʌ≼  22:50, 4 February 2017 (UTC)

  • The opposition on this is grounded in two obvious fallacies: 1) that there is no comprehensibility difference, and 2) that the sources don't agree with the hyphenation. Both of these have been shown to be faulty. First, only someone already deeply familiar with the topic knows that a railway
    term of art is "narrow-gauge" (or "narrow gauge" as a noun phrase rather than a compound adjective: "this is a narrow-gauge railway" versus "this railway has a narrow gauge", a distinction most people learn in elementary schools or in their early ESL classes), but that "gauge railway" is not a railway term of art. The topic has many "foo railway", "foo railroad", and "foo rail" terms of art ("slate railway", "commuter railroad", "double-headed rail" etc., etc., etc.), so there is nothing obvious or intuitive about how "narrow", "gauge" and "railway" relate to each other in such a construction, except to experts. The very purpose of hyphenation of compound adjectives is to clearly link two words that form a single modifier, as distinct from independent modifiers (an "ugly brown dog" and an "ugly-brown dog" are not the same thing; I might have a magnificent, title-winning dog that someone feels is of an ugly-brown color, while if the dog itself were ugly, it wouldn't win conformance championships). Second, it's already been amply demonstrated that a) the sources in the aggregate do not prefer to drop the hyphenation, only specialist materials do so, and b) even those do not do it consistently.  — SMcCandlish ¢
     ≽ʌⱷ҅ʌ≼  23:06, 4 February 2017 (UTC)
    The fact that the ambiguity and confusion are real is easy to see with a web search for "a gauge railway". Even our article on Rapla exhibits this problem (I just now tagged it for clarification). You see it at Getty Images, this illiterate blog, this funny page, and some that just fail to copy the gauge template contents when they mine wikipedia. Even some conference publications and articles. Same for "the gauge railway", like in "The width of the gauge railway is 760 mm" and "Additionally, the gauge railway line will feature". These are probably all mistakes, but they indicate that this kind of unfamiliar construct is not the easiest thing for editors and writers to understand and get right. The hyphen can only help. Dicklyon (talk) 00:56, 5 February 2017 (UTC)
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)
  • @
    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
"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)


  • This looks interesting; I'm tempted to try closing it. Any objections? ~ J. Johnson (JJ) (talk) 01:02, 8 March 2017 (UTC)
    None here. Best of luck. ―Mandruss  01:07, 8 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.

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:

  • have been around for five years and
  • have at least a thousand not-minor edits to their name.
  • Have not been blocked by an admin the last five years.

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)
  • talk
    ) 19:16, 26 February 2017 (UTC)
I went ahead and did all that, as well as notifying at
talk
) 19:36, 26 February 2017 (UTC)
  • Thanks. If I have missed any other little steps, please let me know or go ahead and correct. (Sidenote: I'm off to work now and won't be back to discuss further for several hours) --*Kat* (talk) 21:56, 26 February 2017 (UTC)
  • Oppose any blind automatic granting of any userright as this proposal entails as written. I really don't care if you have been around for 5, 10, or 15 years. And you can do 1,000 edits in a month if you try. Edit count is never a good standard by which to grant userrights by in my opinion. If you need it, request it. If you aren't actively using it it should be removed. That is my stance on all userrights. --Majora (talk) 20:39, 26 February 2017 (UTC)
    • I was trying to come up with objective guidelines. If you have better guidelines, please feel free to suggest them. I also don't understand why you "don't care" how long a person has been around. Do you truly see every editor as a potential vandal? --*Kat* (talk) 21:36, 26 February 2017 (UTC)
      • It has nothing to do with seeing every editor as a potential vandal. Userrights should never be automatically granted. Ever. Period. That is my view and the view of a great number of other people as well. --Majora (talk) 21:40, 26 February 2017 (UTC)
        • So you would agree to my suggestion of essentially rubber-stamping any valid requests for this, as long as it is not done automatically? (Addendum: If you disagree, please explain why - what specific costs or dangers you feel there would be to such a policy. Obviously, it would have major benefits in terms of making users more satisfied and more able to edit the way they prefer, so you need to present specific costs or dangers to answer that.) --Aquillion (talk) 01:06, 27 February 2017 (UTC)
          • What is the difference between "rubber-stamping" something -- that it, approving it without evaluating it -- and automatically granting that same thing? They are synonymous, are they not? And how would one know that a request is "valid" unless one evaluates it, in which case there's no "rubber-stamping" involved. In short, what are you saying? Beyond My Ken (talk) 03:38, 27 February 2017 (UTC)
        • Majora presumably does not object to
          WP:EXTENDEDCONFIRMED, which are both automatically granted user rights. (If Majora does object because of the principle, then someone could look into revoking both of those on Majora's account, but I recommend against it.) WhatamIdoing (talk
          ) 19:24, 27 February 2017 (UTC)
          • @WhatamIdoing: Hilarious. I was against ECP to begin with and autoconfirmed is a necessary evil to get around the thousands upon thousands of protected pages (many of which I have on my watchlist and help maintain). Again, as I have said numerous times in this discussion. Need versus want. Autoconfirmed and extended confirmed is a necessary "right" that allows continual editing of the project. I don't have a problem with necessary rights. I have a problem with hat collecting. Which is essentially what "I want it!!!!" boils down to. --Majora (talk) 23:09, 27 February 2017 (UTC)
            • What? No, they aren't. You can edit just fine without either one, as plenty of new editors can confirm. I think you are much too confident in your own ability to detect through the Internet what other people's personal security circumstances might be. Opabinia regalis (talk) 00:19, 28 February 2017 (UTC)
  • Oppose per Majora. Also, believe me, some sockmasters do go to great lengths to create and raise sockfarms to gain any automatically-granted access such as being autoconfirmed.--Jasper Deng (talk) 20:43, 26 February 2017 (UTC)
    • Autoconfirmed's 4 day, 10 edit requirement is a much lower bar than the proposed 5 year, 1000 edit threshold. The only advantage an abusive editor would gain from IPBE is the ability to behave badly with his home ISP while editing blamelessly via a VPN. It would take less effort to acquire access through an alternate network—a trivial task for many. Rebbing 21:22, 26 February 2017 (UTC)
    • Additionally sockmasters are the exception rather than the rule.--*Kat* (talk) 21:36, 26 February 2017 (UTC)
  • Question: First let me say I am no expert on IP users and enforcement actions against IP spammers. The objections above are to any *automatic* "right" maintained by software. I agree with such objections. I think this objection could be addressed if a request was required first, and then this would be a guideline for approval, not automatic right granted, giving an opportunity to look at IP edits to see if there is a problem before being granted the *privilege*. So I am inclined to support under those revisions. --David Tornheim (talk) 21:04, 26 February 2017 (UTC)
    @David Tornheim: The current guidelines for IPBE are already less strict than this. There are not silly numbers or bars that someone has to meet first. The current guidelines are if you need it and are in good standing you get it. That is in line with every other userright on the project. This RfC would actually increase that bar, not lower it, if it was anything other than an automatic granting. --Majora (talk) 21:15, 26 February 2017 (UTC)
    Would it? I read the guideline before posting. My impression was that it was only granted in extenuiating circumstances. Such as if your natural (ISP granted) IP address was blocked due to someone else's actions? --*Kat* (talk) 21:36, 26 February 2017 (UTC)
    Hence the "if you need it" part of the current policy on granting IPBE (and all other userrights for that matter). --Majora (talk) 21:40, 26 February 2017 (UTC)
    I don't **need** it. I just want it. I *can* log out of PIA and edit but I don't like doing so. --*Kat* (talk) 21:52, 26 February 2017 (UTC)
    And I want a million dollars and a fully paid private jet to take me wherever I want. "Wanting" something is not how we do things here. Even the lowest barred userrights (rollback and PC) require some sort of proof that you need the right to continue editing normally. You Can't Always Get What You Want. --Majora (talk) 21:57, 26 February 2017 (UTC)
    @*Kat*: Do you want this to be *automatic* without request, or granted with a request having to be made first? --David Tornheim (talk) 22:03, 26 February 2017 (UTC)
    @David Tornheim: I would prefer automatic. Most of the affected users wouldn't know to ask for it. That hurts wikipedia. If someone abuses it can be revoked easily enough.--*Kat* (talk) 04:24, 27 February 2017 (UTC)
    @David Tornheim: That said... I can compromise. If the community is very much against an automatic granting of a user right. I can compromise. --*Kat* (talk) 04:36, 27 February 2017 (UTC)
    Wait, hold on, Majora: Why are you opposed to Kat (and others in the same situation) getting this right? It is obvious that Kat is not part of some sort of sinister troll-network, which is really the only thing that matters here; and even if they were, this is not a right that (when given to just a few accounts) can cause much disruption. A million dollars and a private jet are expensive; granting Kat the ability to post using a VPN is free. I can understand, sort of, the opposition to granting it automatically, but I don't understand why you feel the right should be reserved only for the most extreme of circumstances - I feel that anyone who can make a good argument of "I would benefit from it" ought to have it. (Trolls are unlikely to request it because doing so only increases the attention focused on them and because, again, the benefits in exchange for the risks are so minor.) If you want to oppose granting this right to anyone who would benefit from it, you need make an argument for the harm or cost that would come from doing so. --Aquillion (talk) 23:05, 26 February 2017 (UTC)
    You have put words in my mouth Aquillion that I never said. I'm opposed to anyone getting any right they do not need. If you need IPBE to edit normally, by all means, ask for it. I will stand behind you in your request. I will not, however, stand behind you just because "you want it". That isn't how any userright works, nor should it. --Majora (talk) 23:40, 26 February 2017 (UTC)
    But there's a middle ground you're deliberately ignoring. What about users who would benefit from being able to edit via VPN (because they prefer to use a VPN constantly for whatever reason), but who do not strictly need it? What is your basis for refusing to allow them to do so? My feeling is that if someone requests the ability to edit via VPN, some other user should have to present an argument why they shouldn't get it. If you can't come up with that argument (and you've presented absolutely no reason to deny it here), then they should get it. Anything else would be pointless and unproductive legalese. Giving the ability to edit via VPN to someone like Kat makes it easier for them to edit the way they prefer and makes it more likely that they will edit prolifically, which benefits the encyclopedia as a whole; if you can't come up with a specific counterargument (some cost or danger that would arise from granting it to them), then your objections are groundless and ought to be disregarded. --Aquillion (talk) 01:02, 27 February 2017 (UTC)
    (sigh) Wanting to edit through a VPN and needing to edit through a VPN are two completely different things. Again, want and need is the crux of what I am getting at. Very few people need a VPN to edit. Those whose government are monitoring them being the big one that comes to mind. Simply because you want to edit using a VPN does not mean you should have this userright. And there are dangers to this right as there are dangers with any right. Seeing as we have gotten into the "your objections should be disregarded" territory I don't see how continuing this conversation is a positive course of action. --Majora (talk) 01:16, 27 February 2017 (UTC)
    I want to know more about the practical end of this distinction you're drawing. Who exactly is supposed to determine me whether my use of a VPN is truly "needed" or merely "wanted"? How is some person who is not me supposed to know what I actually "need" to edit Wikipedia? WhatamIdoing (talk) 19:24, 27 February 2017 (UTC)
    @WhatamIdoing: It is rather simple in my mind. Do you require it to edit. The vague "privacy" reason is meaningless without a further reason. As stated above, government surveillance is a major aspect that would warrant the use of anonymizing proxies. A paranoia that you are being watched is also meaningless. Take the China example. There is no paranoia there. The Great Firewall is a known surveillance apparatus that affects editors based in, or travelling to, mainland China. Besides the blanket blocking of zhwiki and the occasional blocking of enwiki, this would require the use of an anonymizing proxy. As a side note, most of these IPs are probably blocked globally and would require a global IPBE which are given out far more easily on meta anyways. There are very few reasons why someone would need to edit through a proxy beyond simple paranoia which Wikipedia should not be party to. Occasionally wanting to edit through a proxy is also meaningless as there is really nothing that is that important that goes on here that cannot wait for you to get somewhere where you don't feel the need for one. --Majora (talk) 23:09, 27 February 2017 (UTC)
    So if I say that I won't edit without it, then you would say that I need to tell you my reason, and then you would pass judgement on whether my reason is good enough – according to your values and your circumstances and your understanding, rather than mine. And if you decide that my reason isn't good enough for you, then your reaction is basically "Good riddance, and don't let the door hit you on your way out!" I cannot support that. Individual editors are best suited to make their own decisions. We have in this discussion an editor who has largely stopped editing because of IPBE problems. Not editing because we're imposing an artificial hassle = not good for Wikipedia. This should be the encyclopedia that anyone can edit – not the encyclopedia that anyone who feels comfortable editing without a VPN can edit, or the encyclopedia that anyone who's willing to constantly log in and out of a VPN can edit. (Imagine doing that while trying to search for sources: Login to use a search engine, logout to get back to Wikipedia, login to click a link that explains more in the source, logout to finish editing... Requiring that of editors would be stupid, and it only hurts us.)
    I think that your hat-collecting idea is irrelevant. IPBE isn't a "hat". It's a way of enabling editors to do normal, everyday things. It confers no extra abilities to the editor; it merely puts them back on a level playing field. WhatamIdoing (talk) 00:30, 28 February 2017 (UTC)
  • Support, or, failing that, support a general rule that anyone who meets those rough criteria can get it rubber-stamped without the need for extenuiating circumstances. I don't see any reason why this right shouldn't be granted to any established user who would benefit from it, since it costs us nothing and has almost zero risk. --Aquillion (talk) 23:05, 26 February 2017 (UTC)
  • If such a user asked for the bit, you can expect it would be granted. So no change to policy is needed. Graeme Bartlett (talk) 23:44, 26 February 2017 (UTC)
    • Is this true? Some people above seem to feel that the bit should only be granted to people who absolutely need it (ie. some people are arguing that simply preferring to edit from a VPN for privacy reasons is insufficient, and that it should be denied.) I feel that this is the real question we ought to be addressing; the mechanism by which it is granted is less important than the standard for doing so ("only grant when absolutely necessary" vs. "grant on request unless there's a compelling reason otherwise.") --Aquillion (talk) 01:08, 27 February 2017 (UTC)
      • Speaking from experience, the granters of this bit are not autocratic jerks. If they feel you're a trusted editor (this, of course, is key), and you state why IPBE would make your editing easier, you'll likely be granted the right. --NeilN talk to me 02:07, 27 February 2017 (UTC)
        • "the granters of this bit are not autocratic jerks": Given that you're one of the autocratic jerks that I previously had to deal with, who hassled me about my username, you'll hopefully understand why I don't take your word on this. Sławomir Biały (talk) 14:28, 27 February 2017 (UTC)
          • Thank you for proving my point. The only admin present in this topic used his judgement and made quite reasonable posts. --NeilN talk to me 14:46, 27 February 2017 (UTC)
  • Oppose per Majora: I usually edit at home and school which autoblocks affected the school IP address mostly from vandals in the school, and strongly oppose the 5 year requirement that don't make sense either. I'll alternatively support a 6 month requirement instead. KGirlTrucker81 huh? what I've been doing 00:36, 27 February 2017 (UTC)
    I'm not against a 6 month requirement. I just figured that people would scream that that wouldn't be long enough.--*Kat* (talk) 04:19, 27 February 2017 (UTC)
  • Oppose as written. I do not agree with this userright being handed out automatically. The vast majority of users do not need it. Also, once you've met this threshold without using IPBE, why would you all of the sudden need it? Doesn't make a lot of sense.
    talk
    ) 01:55, 27 February 2017 (UTC)
    I figured that setting this to "automatic" would make it easier to implement -- from a technical standpoint. I was hoping that the five year limit bar would reassure people that the IPBE couldn't be easily abused.--*Kat* (talk) 04:19, 27 February 2017 (UTC)
    On another note, you know what doesn't make sense to me? A blanket ban of edits from a proxy IP address, regardless of whether the editor is in question is an anonymous newbie or a logged in user who has been part of wikipedia for more than ten years.--*Kat* (talk) 04:19, 27 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.
talk
) 22:49, 27 February 2017 (UTC)
  • Oppose - per Beeblebrox. Any editor who needs it should simply ask for it. Beyond My Ken (talk) 03:42, 27 February 2017 (UTC)
    Then can I propose that that be made more clear on the IPBE page? I came away (and per user Majora, still get the feeling) that only those with the greatest need be granted an IPBE. --*Kat* (talk) 04:19, 27 February 2017 (UTC)
@
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)
@
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 *Kat*, it doesn't appear that you even attempted requesting IPBE before opening this RFC. I'm not familiar with typical practices at IPBE, but there's at least a chance that a lot of people's time could have been saved, avoiding this entire RFC. And if you were declined, then at least you'd have some concrete example to consider whether IPBE practices need changing. Alsee (talk) 11:50, 27 February 2017 (UTC)
    • Guilty as charged. I looked at the WP:EXEMPT and determined that under those guidelines I did not quality. At all. WP:EXEMPT makes it very clear that only an editor with "genuine and exceptional need" should be granted an IPBE. As I stated above, this is not something I need; it is something I want. There is nothing preventing me from editing Wikipedia with my normal IP *except* my own desire to stay logged into my VPN. I can't be the only one in this position so I decided to make Wikipedia a better place by proposing a solution.--*Kat* (talk) 14:19, 27 February 2017 (UTC).
    I think it was better that *Kat* made this RfC to address the concern, rectifying any actual problem for all editors similarly situated, rather than focusing primarily on his/her approval. If *Kat* had been denied, and then made this
    WP:RfC, it would appear more self-serving than to make this request on behalf of all similarly situated editors. --David Tornheim (talk
    ) 15:01, 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)
  • Oppose: IPBE should not be automatically granted or automatically removed. IPBE should be the result of an administrator looking at your edit history and deciding that you are unlikely to be a sleeper sockpuppet. Administrators should be instructed that a desire for privacy through a VPN or TOR is considered to be enough reason to grant IPBE, and to focus on the question "Do I think this will be abused" rather than on "can they prove that they really need this"? After this closes, we should have an RfC concerning what I just wrote concerning administrator instructions. --Guy Macon (talk) 13:26, 27 February 2017 (UTC)
  • Comment - This isn't a discussion about IPBE, this is about allowing editing from webhosts/proxies for established editors (5+years or some other metrics), and should be clearly framed that way.  · 
    14:09, 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)
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.  · 
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)
  • Comment Only expansion I see here would perhaps be temporary IPBE, if you are going into an area where you will be forced to use a VPN, but still want to edit. Iazyges Consermonor Opus meum 14:13, 27 February 2017 (UTC)
  • Comment This is something that is going to have to be addressed in some way sooner rather than later. Private VPN usage due to security concerns is on the rise. Only in death does duty end (talk) 14:32, 27 February 2017 (UTC)
  • Comment I agree with User:Only in death. Every security expert says to use VPNs on public networks. This issue should be resolved somehow. Maybe Wikimedia can have it's own VPN just for editing Wiki projects. Or whatever. Felsic2 (talk) 16:46, 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)
  • Oppose - this is a solution in search of a problem. Which editor in good standing who needs an IPBE has been denied one? If the OP needs an IPBE then if they ask on my talk page they can have one! If there are privacy issues then go to
    WP:UTRS where I spend much of my time! Numeric criteria are no good - so an editor has no blocks, it does not mean that they are not problematic - admin judgement has to be used because the protection of the Project is the overarching requirement. Just Chilling (talk
    ) 19:16, 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)
  • Support in principle, oppose these conditions — I had the right prior to 2016 because I travel extensively, it was removed last year because I hadn't struck upon any issues then (which per definition I would have not have noticed) — and was currently not abroad. Within a few months I struck upon the issue while traveling (within Sweden as well, mind you) — which forced me to waste hours applying for a new exception, and wasted time from an administrator that had to look into the issue and verify that the IP I was editing from really was blocked, and was blocked for something unrelated to me. The issue has arisen at hotels, libraries and some campuses I've visited.
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)
  • Comment Our approach to this problem is increasingly out of date and out of step with both "mission-aligned" external groups such as the Electronic Frontier Foundation and with other common security advice. Current procedure for obtaining IPBE expects disclosure of the circumstances that necessitate it, which is obviously counterproductive for those who really do have compelling serious security concerns, and unnecessarily restrictive for those who are just privacy-minded. It's time we modernized our management of this issue.
    This was discussed a bit after last year's IPBE audit, but a few proposals were made that weren't workable, and nothing really congealed into a better proposal. Unfortunately, this one isn't really workable either, as amply covered above - edit-count thresholds are both gameable and counterproductive, account-tenure thresholds are not all that meaningful, and in any case, five years is hugely excessive.
    Realistically, although socking by established users is more disruptive than socking by garden-variety trolls, it is also less common and often noticed behaviorally. It would be interesting to have more data, but I don't think we have strong evidence now that relaxing requirements for IPBE for established users would lead to such a significant increase in disruptive activity that it wouldn't be worth doing. Opabinia regalis (talk) 22:03, 27 February 2017 (UTC)
  • Oppose/Comment. I am opposed to automatic granting of rights to people who may not need them. I am opposed to arbitrary limits for edit counts or tenure in order to qualify. I am opposed to people hanging on to rights when they are no longer needed. However I do support some relaxing of the current wording of the policy. The policy was written a long time ago, before Edward Snowden, proper Wikimedia HTTPS, and all that. -- zzuuzz (talk) 22:23, 27 February 2017 (UTC)
  • Support dropping "need" as a criterion. I don't think the proposed five-year threshold makes a lot of sense. But I think Majora's "need versus want" is not a useful demarcation for this sort of thing. No one "needs" to edit Wikipedia in the first place. If a trustworthy editor judges that editing through a VPN will facilitate editing, there's no good reason for us to get sticky about whether it is "necessary". --Trovatore (talk) 00:23, 28 February 2017 (UTC)
    • I agree with you. It shouldn't be about whether I think your circumstances are sufficiently dire to absolutely require it; it should be about whether you'd (at least occasionally) use it. WhatamIdoing (talk) 00:30, 28 February 2017 (UTC)
  • Oppose One user having difficulties of their own making isn't an issue. This is a solution to a problem that doesn't exist in the first place. Lugnuts Precious bodily fluids 08:44, 1 March 2017 (UTC)
  • Oppose as written. I wouldn't like to see the right automatically granted, and I also think the five year requirement is far too long. Even if we made it a few months and a thousand edits, that will dissuade all but the most determined sockmasters (and those highly determined ones will find a way whether we grant people IPBE or not.) What I would support, as always, is granting IPBE on request to any established user in good standing (without trying to too tightly define that) with the clear proviso that "I want to use this service for privacy reasons" is a good enough reason. Wikipedia should be a supporter of open use of the Internet, and that includes, if one desires, the ability to use it without being tracked. Seraphimblade Talk to me 03:16, 2 March 2017 (UTC)
  • Oppose Let me put it simply, if this were to be implemented do you understand what'd happen if experienced users turned, there'd be almost no way to determine the entire situation. The Ricky81682 affair already affirms that it's a credible possibility. As anyone else who works at SPI would say, I'm vehemently in opposition. --QEDK () 06:01, 16 March 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?

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.
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.
talk
) 19:35, 28 February 2017 (UTC)
The IPBE page pulls directly from ListUsers.
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)
  • Support As per the above, it's obviously a balancing act. That being said, it's hard to see why experienced editors should be limited in this regard. Sockpupeteers are of course a problem, but anyone who is openly disruptive will be hopefully be caught before they get this far, or at least before they do substantial damage. We shouldn't live our lives running around in fear of sockpuppets. Additionally, the additional scrutiny brought by an IPBE request may actually help detect some sockpuppets. Certainly that's enough to make me think it's worth it. Tamwin (talk) 05:36, 28 February 2017 (UTC)
  • Support Obviously. Sure, sometimes good editors go bad but they are the exceptions rather than the rule.--*Kat* (talk) 09:24, 28 February 2017 (UTC)
  • Alternate support - The question is "should established users be allowed to edit via VPN" and my answer is "yes" but I don't think IPBE is the solution. Instead of allowing IPBE for established users, we should stop hardrangeblocing VPNs/webhosts. 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. Softrangeblocks can continue disallowing unregistered editing via VPNs/webhosts.  · 
    13:36, 28 February 2017 (UTC)
    Would there be any downside to using soft blocks instead of hard blocks for VPNs? --Guy Macon (talk) 14:38, 28 February 2017 (UTC)
    The old attribution argument hasn't had any credibility for at least a decade (if it had any at all). The real problem with softblocking proxies is the prolific abuse from vandals and sockpuppeteers who tend to use them to operate large numbers of accounts. Accounts are easy to create. -- zzuuzz (talk) 14:42, 28 February 2017 (UTC)
    You can block account creation on a rangeblock without disallowing editing for logged-in editors.  · 
    14:50, 28 February 2017 (UTC)
    And it's easy for any vandal who is rangeblocked to find another IP address in order to create accounts. -- zzuuzz (talk) 15:01, 28 February 2017 (UTC)
    Which is besides the point of this discussion, it is neither easier nor harder for someone to find a different range whether the original range is softblocked+ACD or hardblocked.  · 
    16:06, 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.
talk
) 19:37, 28 February 2017 (UTC)
It's more of a mindset change. (And coding tweaks to ProcseeBot probably).  · 
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.  · 
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.  · 
    16:50, 3 March 2017 (UTC)
  • Oppose: I honestly don't see a pressing need to allow people to use VPN, TOR, or other proxy services simply because they want to. Yes, any sufficiently intelligent and committed sockpuppeteer can still manage to make himself checkuser-proof, but from my experience at SPI, that does not appear to be most sockers. Most of them are demonstrably lazy, stupid, and/or ignorant of how the internet functions. If you make it easier to sock, there will be more socking. The WMF privacy policy never promises that all of your information will be invisible to everyone, only that it will be invisible to the public, and almost every user of the site. Someguy1221 (talk) 02:46, 1 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)
  • It occurs to me that if an email from OP had shown up in my inbox, I'd have spent a few minutes poking around to see if everything was on the up-and-up, flipped the switch, and then tried to remember to come back in a month and ensure it was being used properly. Truthfully, I likely would forget that last step. Long term good faith users are not going to ask for this flag to start socking, and while we need to be vigilant about handing this right out, we treat it entirely too carefully. People who want to make trouble aren't likely to start contacting checkusers with an open invitation to pull their data and investigate. Courcelles (talk) 03:36, 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.
talk
) 23:56, 1 March 2017 (UTC)
  • Strong support. I think far too much is being made over the difference between "wanting" versus "needing" to use a VPN. Privacy is a basic right, that is explicitly acknowledged by the WMF. It is also a necessity in today's world. Furthermore, one needs a VPN in order to secure this right of privacy. (Ever edit from a coffee shop? from work? from an unsecured WAN? over cable lines owned by an ISP? yeah, I thought so.) It may or may not be that there are immediate consequences to a lack of privacy, but that is usually only clear in hindsight (after arrest and torture, having assets frozen, identity stolen, personal details posted, or other unpleasantness). Unless administrators are granted prescient abilities to determine whether some such unpleasant circumstances are going to come about as a result of lack of privacy, they have no business determining whether an editor wishing to use a VPN to secure privacy comes from a "need" for this basic right, or a mere passing fancy. Sławomir Biały (talk) 00:52, 2 March 2017 (UTC)
    @Sławomir Biały: took the words out of my mouth and made them better. I'm not hiding from Wikpedia, I'm concealing my presence on the net by masking my IP. I'm making it harder for individuals and groups with the means and motivation to know what websites I am visiting and when. Using the VPN gives me peace of mind and for the most part the Internet is exactly the same when I am logged in as it is when I am logged out. There are only two things I can't do while logged into VPN: order a pizza and edit wikipedia.--*Kat* (talk) 01:09, 2 March 2017 (UTC)
    You want privacy of a kind unknown to the vast majority of internet users. If it is that important, why not buy a VPN service that is not used by trolls to attack Wikipedia and so which is not blocked? The comments by
    WP:LTA cases, Amanda's comments seal the deal—privacy of the kind wanted is not available for free, and a very experienced checkuser has noted that open slather on IPBE would make checking too hard. Johnuniq (talk
    ) 01:50, 2 March 2017 (UTC)
    You could demand committed identities from exempt editors. That would obviate the need for checkusers. Sławomir Biały (talk) 02:01, 2 March 2017 (UTC)
    I don't think {{committed identity}} is relevant to Amanda's point. It is not desirable to publicly discuss checkuser procedures but we have a clear statement that Amanda will not be able to pursue socks who operate through webhosts/proxies, presumably because there would be too much noise due to assumed valid users who are using them for assumed valid edits. Johnuniq (talk) 02:42, 2 March 2017 (UTC)
    @
    Amanda (aka DQ)
    00:15, 3 March 2017 (UTC)
    You could confirm an institutional email address, telephone number, or other publicly accessible piece of information. Doesn't OTRS regularly have to do this sort of thing? Sławomir Biały (talk) 00:42, 3 March 2017 (UTC)
    @
    Amanda (aka DQ)
    06:41, 3 March 2017 (UTC)
    @
    WP:AGF no longer a guiding principle of Wikipedia?--*Kat* (talk
    ) 06:25, 3 March 2017 (UTC)
    @ 06:41, 3 March 2017 (UTC)
    There is nothing in this proposal that says you should ignore WP:Duck and grant this access right indiscriminately.--*Kat* (talk) 17:49, 3 March 2017 (UTC)
    Not that it should matter, but I do use a paid VPN. Private Internet Access isn't free. It is, however, quite popular with VPN users because it doesn't log anything. But we are getting off topic here. This isn't about me. This is about Wikipedia's policies. And privacy.--*Kat* (talk) 04:16, 2 March 2017 (UTC)
    As far as I know, Wikipedia does not maintain a list of VPN providers that are not blocked. And in any case, there is no guarantee that a VPN provider which is not blocked now will remain so. I have used paid VPNs in the past which were eventually blocked. Sławomir Biały (talk) 12:52, 2 March 2017 (UTC)
    Some of the time the IP blocks I come across are specific to my paid VPN service. Perhaps I should be paying more? --*Kat* (talk) 17:49, 3 March 2017 (UTC)
  • Support. A desire for privacy is sufficient reason. I don't use a VPN to hide from checkusers or to sock. I use one because, first, I use public access points with some frequency and it is insane to connect unprotected to those, and second, because I want to put one more stumbling block in front of entities (public or private) that want to track my Internet activity. Sure, Wikipedia doesn't track anyway and I wouldn't really care about my information being available here, but Wikipedia is not the only site I visit and a VPN is either on or off. I can use it since admins can bypass those blocks, but it's hardly fair I can do that and many other good-faith users cannot. Someone who is so determined to sock that they will work up an account to the "good standing" level is going to find a way to sock, period. It's hardly like use of a VPN is the only way to do it. The "good standing" requirement will dissuade those casually considering socking, and they're the only ones it's possible to dissuade at all. Seraphimblade Talk to me 03:25, 2 March 2017 (UTC)
  • Support. I think "do you need it or do you just want it?" is an arrogant and obnoxious question. That's my main concern here. I'm OK with a reasonably high bar for evidence that an editor is trustworthy, but a trustworthy editor should not be asked why they "need" to do something. --Trovatore (talk) 04:25, 2 March 2017 (UTC)
  • Oppose I suppose that current protection mechanisms exist for a reason, and are built on prior experience. My own experience as a regular editor is that some ten years ago one would far more easily get entangled in an IP sock fight with uncountable ramifications than more recently. I'd listen to the people managing SPI, because obviously they're doing a good job. VPN-related strictures can be bypassed via a standard operational mechanism without endangering the general protection level. So what does one want: not having to jump through any hoops if one wants to bypass VPN strictures without obvious rationale? Don't see what would be the advantage of that. --Francis Schonken (talk) 09:52, 2 March 2017 (UTC)
    Comment. I don't say that editors requesting IPBE shouldn't be asked for a reason. I object to framing it as a requirement for a need. Kat, I think, has presented a reason. She judges it prudent to use VPN for everything, not just Wikipedia. That's a perfectly plausible reason, if not necessarily a need. If IPBE asks for a reason of that level of significance, together with an established pattern of behavior that inspires trust, it seems to me that it would be quite time-consuming and difficult for a sockmaster to establish a farm of identities that can all meet that burden, and almost impossible to avoid giving them away with common tropes/word choices/speech patterns/etc. --Trovatore (talk) 10:23, 2 March 2017 (UTC)
  • Support per Trovatore. If someone has a valid reason and is well-established and trustworthy (long edit history and no evidence of problems) there's no reason we shouldn't give it out. --Jayron32 14:45, 2 March 2017 (UTC)
  • Support per Sławomir Biały and others. According to The Intercept,

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)
@
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)
@) 18:28, 3 March 2017 (UTC)
@
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)
  • Support granting IPBE in both proposals I agree with others that proposal statement could be formed better. The position that I support is granting easier IPBE to trusted users. It is too difficult to get this user right to the correct people who need it. I understand and recognize the need for a strong vetting process when this right is issued, but right now, the process is too indistinct to describe and too onerous to recommend. I have done editing to Wikipedia:Open proxies, Wikipedia:Blocking_IP_addresses#Open_proxies, Wikipedia:Blocking_policy#Open_or_anonymous_proxies, Wikipedia:Advice to users using Tor, meta:No open proxies, and also posted lots of notes at meta:Grants:IdeaLab/Partnership between Wikimedia community and Tor community. I am convinced that there are no clear answers to be found on how IPBE is issued or managed, other than the approval process requires meeting unpublished criteria that are not cross-checked to meet the demand of what most Wikimedia people want. I feel that most Wikimedia community members would want for logged-in accounts that have passed a high standard challenge to prove their trustworthiness would support giving exemption to people who profess a need. My objection is that there is no standard, not even a high one, that a person can pass to get this right. I want a standard defined and the right awarded, and then over time I want the standard discussed so that it can align with community need. Among the people who might want to edit through a VPN include anyone who values their privacy as a personal choice and people who value their privacy as they edit political or illegal Wikipedia articles like LGBT+ related topics or articles about opposition parties in governments which discourage that. Right now, there is no way for a person with privacy concerns to publicly state their problem because many people who want privacy do not want to draw attention to the fact that they want privacy. The conversation needs to start somewhere, and it can start by vetting this person to have the userright. If things check out as they saw they do, then a user with a huge number of edits and 5 years of editing is a fair candidate for an increased level of trust. Blue Rasberry (talk) 22:21, 2 March 2017 (UTC)
  • Support second proposal. I don't think it makes sense to automatically grant it to anyone, but "I want to use a VPN" seems like a legit reason to me, assuming that the account is a) somewhat experienced and b) in good standing. If they abuse it, it can be removed with a few clicks of a button. -- Ajraddatz (talk) 22:42, 2 March 2017 (UTC)
  • Support: "Because I want to use a VPN" and "Because I want to use TOR" are indeed valid reasons for granting IPBE, to users in good standing and with significant editing histories, subject to the discretion of the deciding administrator. In other words, not automatically accepted and not automatically rejected. 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. --Guy Macon (talk) 02:46, 3 March 2017 (UTC)
    My reasoning: privacy concerns are a perfectly good reason for requesting IPBE, and the user should not be asked to "supply a good reason". That being said, a vague "this one smells wrong" feeling is a perfectly good reason for an administrator to reject an IPBE without prejudice (meaning that another admin is free to grant it). "Does this user really need IPBE?" is the wrong question for an admin to ask. "Do I trust this user to not engage in socking?" is the right question for an admin to ask. --Guy Macon (talk) 02:54, 3 March 2017 (UTC)
    This seems reasonable.--*Kat* (talk) 06:39, 3 March 2017 (UTC)
  • Support What Guy Macon said. 'I would like my privacy protected' is a perfectly valid reason. The problem I forsee is 12 months down the line another checkuser deciding on a whim that everyone who has IPBE doesnt have need of it in their opinion and removing it. So there needs to be a policy change to explicitly prevent this, either in the Checkuser policy or IPBE to prevent 'sweeps'. Only in death does duty end (talk) 09:41, 3 March 2017 (UTC)
  • Comment - before people get carried away with @Guy Macon:'s comment, note that the question before us, what I and the others supported, was "Should we therefore grant IPBE to users in good standing and with significant editing histories if they desire to use VPNs?" That is a call for admins to grant the right, not to think about it on a case by case basis and use any or no justification ("smells wrong") to deny it. The proposal doesn't take away their discretion when evaluating "good standing" or "significant editing histories", until such time as those things are better defined, but it does require them to evaluate those things fairly and act on them as appropriate. Too much "discretion" here only encourages the situation Guy suggested - asking another administrator. The admins don't seem to like it when you ask Daddy because Mommy said no, so the excessive discretion would likely be followed up with an interpretation we absolutely didn't vote for, namely prohibiting any admin from reexamining the first admin's verdict, at which point the whole procedure becomes extremely arbitrary and subject to personal politics and perhaps ethnic affiliations or stereotypes. Wnt (talk) 16:39, 3 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)
  • 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)
  • Oppose per my rationale in the previous section. --QEDK () 06:03, 16 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

.

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.
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
    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.
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)

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.