Jump to content

Wikipedia:Village pump (policy)/Archive 117

Add links
From Wikipedia, the free encyclopedia
Village pump (policy) archive  

This page contains discussions that have been archived from Village pump (policy). Please do not edit the contents of this page. If you wish to revive any of these discussions, either start a new thread or use the talk page associated with that topic.

< Older discussions · Archives: A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, R, S, T, U, V, W, X, Y, Z, AA, AB, AC, AD, AE, AF, AG, AH, AI, AJ, AK, AL, AM, AN, AO, AP, AQ, AR, AS, AT, AU, AV, AW, AX, AY, AZ, BA, BB, BC, BD, BE, BF, BG, BH, BI, BJ, BK, BL, BM, BN, BO · 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22, 23, 24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44, 45, 46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66, 67, 68, 69, 70, 71, 72, 73, 74, 75, 76, 77, 78, 79, 80, 81, 82, 83, 84, 85, 86, 87, 88, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98, 99, 100, 101, 102, 103, 104, 105, 106, 107, 108, 109, 110, 111, 112, 113, 114, 115, 116, 117, 118, 119, 120, 121, 122, 123, 124, 125, 126, 127, 128, 129, 130, 131, 132, 133, 134, 135, 136, 137, 138, 139, 140, 141, 142, 143, 144, 145, 146, 147, 148, 149, 150, 151, 152, 153, 154, 155, 156, 157, 158, 159, 160, 161, 162, 163, 164, 165, 166, 167, 168, 169, 170, 171, 172, 173, 174, 175, 176, 177, 178, 179, 180, 181, 182, 183, 184, 185, 186, 187, 188, 189, 190, 191, 192, 193, 194, 195, 196, 197

Redefinition of revert

WP:3RR and similar restrictions exist to limit the effects of edit warring. They are defined as An editor must not perform more than three reverts on a single page—whether involving the same or different material—within a 24-hour period. This definition depends on the definition of a revert, and it is open to interpretation and abuse. For example:

  • A revert is undoing a specific edit by another user
  • A revert is returning text to a state it existed in before
  • A revert is undoing any work by another user

Each of these definitions has inherent problems that can lead to arguments:

  • A user largely undoing another editor's work but using different words can claim that they were trying to find a compromise
  • Any edit that deletes or replaces a latter (even correcting a typo) undoes the work of an editor who typed that letter, so a WP:GNOME could be accused of edit warring.
  • An editor may unknowingly be returning a piece of text to a state it existed in before a long time.

Another issue with revert is WP:BRD. If on a page under 1RR editor A performs an edit, editor B reverts it, editor A performs the edit again it is A's first revert, but B cannot revert it. However, according to the spirit of WP:BRD, the contested edit should remain off the page while the discussion goes on. With 3RR it's the same, with 2 more cycles of reverts before they are forced to stop and discuss.

I think these problems can be addressed by defining revert for the purpose of 3RR and other restriction differently: "do not commit an edit that is very similar to one already done in the last 24 hours without reaching consensus". It would have the following benefits:

  • Facilitate BRD. Editor A made an edit, editor B disagreed and reverted it, now both have to discuss it.
  • Avoid group revert war. Currently if there are N editors pushing an edit and M editors reverting it, the number of N or M is the determining factor in the state the page will be in before they can begin discussing. With the new definition one of the N editors will make the edit, one of the M editors will undo it, and then they all will discuss.

This definition isn't perfect, it creates a problem with WP:OWN, where a single user will be able the undo any edit by any other editors - since these undoes would be each a unique edit. To handle this case the rule has to be augmented with "...and do not undo large parts of recent work by other editors...".

Are there cases that I'm missing and this definition makes much worse ? “WarKosign” 07:49, 1 December 2014 (UTC)

It looks as if under this proposal a first revert would in a sense be "protected". Reversions are not always right or the best action to take. I know we have to revert vandalism and disruption quickly, but there is too much other reversion without explanation. Part of the trouble is the mechanics of Wikipedia, making it ten times easier to revert the whole thing and pass on, than to look into the matter a bit more, retain a useful part of the edit and change or remove what is objectionable, add a few words of explanation in the edit summary, and often put something on the other editor's talk page. The reversion habit generates a lot of avoidable hostility. I could accept the spirit of the proposal if there was also a duty put on reverters, to ensure that wholesale reverting was the only course, and always provide some explanation: Noyster (talk), 11:47, 1 December 2014 (UTC)
I think the problems begin when a user un-reverts an edit. Per WP:BOLD the first edit in a sequence is fine, and per WP:BRD it is OK to revert it if another editor feels the bold edit violated the consensus. The edit war begin when someone insists on re-introducing the same edit without reaching an agreement on the talk page. “WarKosign” 12:16, 1 December 2014 (UTC)
Rather than Wiki-lawer over who gets to have the "last word" in a revert war, it is better to focus on the intent of 3RR. That intent is that we should not engage in revert wars to begin with. The point is that editors should go to the talk page and discuss instead of engaging in revert wars. We are supposed to hammer out any disagreements on the talk page, and not in the article. The thing is... anyone can end a revert war simply by not reverting (and shifting to the talk page)... so, if you have reverted an edit, and the other editor un-reverts your revert... don't continue to escalate the revert war by re-reverting (even though you might technically be allowed to do so). Temporarily leave the article at the "wrong version" while you discuss the issue and reach a consensus. Blueboar (talk) 12:39, 1 December 2014 (UTC)
There is no need to have 3RR at all if nobody engages in a revert war. One stubborn editor that refuses to discuss is enough to create a disruption, and there must be rules to handle these situations. “WarKosign” 12:47, 1 December 2014 (UTC)
BRD shouldn't be viewed as a free pass for reverters, the page itself linking to Revert only when necessary. I'm saying the talking should start at the first revert. If the original editor meets with a blank reversion, with no indication what was thought to be wrong, they are given little option but to reinstate their edit unaltered, forget the matter, or start a discussion with a lame question like "What was wrong with that?": Noyster (talk), 12:50, 1 December 2014 (UTC)
I agree that proper etiquette when one sees a problematic edit is to create a talk page section with their complaints pinging the original author and then if there is a very good reason to revert the original edit. But again, polite and well-intended editors do not need rules such as 3RR. The rules are needed to force otherwise stubborn editors into a resemblance of politeness. “WarKosign” 12:58, 1 December 2014 (UTC)
WP:3RR already does define what a revert is.
The most obvious problem with the proposed definition here is that it means the first revert won't "count" as a revert, since in most cases it will be reverting to a version that's more than 24 hours old. We don't need to rewrite rules for hypothetical situations like typo fixes or accidents, as Wikipedia is not a bureaucracy. The intent of the rule is more important than the wording.
The spirit of BRD does not mean "the contested edit should remain off the page." Which edit is contested depends on who you're asking. There's no requirement that the original version always be used during the discussion unless the new version has potential issues with BLP or copyright violations. BRD is not a required process. You are free to simply do BD, and only revert if the other editor doesn't respond.
"if there are N editors pushing an edit and M editors reverting it, the number of N or M is the determining factor in the state the page will be in before they can begin discussing" - No, it's not. 3RR is a bright line, but it's not the sole factor considered. From WP:3RR: "Even without a 3RR violation, an administrator may still act if they believe a user's behavior constitutes edit warring, and any user may report edit warring with or without 3RR being breached. The rule is not an entitlement to revert a page a specific number of times." Mr.Z-man 15:40, 1 December 2014 (UTC)
3RR's definition is problematic since it can be taken to extreme. Fixing a typo involves deleting a wrong letter, which reverses the action of another editor who typed this letter.
Which "first" revert do you mean? I'm describing a situation where an article is at a certain state which we'll assume has consensus. Editor A makes a change - and and doesn't matter if this change is a new edit or a revert. Editor B who disagrees weakly with this change should just voice the objections on a talk page. If B disagrees strongly, they should revert and voice the objections.
Let's assume now that they are not so polite and that B considers A's edit so horribly biased it must not stay in the article. Under 3RR A is allowed to make the same edit 3 more times (3 reverts of B's revert), while B is be allowed to revert 2 more times. The result is that A forced their potentially horrible edit to remain while the discussion begins. “WarKosign” 15:56, 1 December 2014 (UTC)
You are showing a serious misunderstanding of both the letter and intent of the edit warring policy. As I said, 3RR is not an entitlement to make 3 reverts. If you do more than that, you will almost certainly be blocked. But the page can be protected or users blocked before that threshold. Basically you're saying that Editor B's initial revert shouldn't even count as a revert for the sole purpose of allowing the "consensus" version (regardless of whether that's really true, all we we know for sure is that it's B's preferred version) to be the version that ends up on the article when A and B hit the 3RR limit. That's not really improving anything. All it does is allow B to edit war one revert longer so that the article doesn't end up in The Wrong Version.
What if there was no consensus? What if B was WP:OWN-ing the article, keeping it in a biased state and independent editor A came along to try to fix it? Policies don't, and shouldn't, assume that either version of an article in an edit war is the "correct" one. Mr.Z-man 17:54, 1 December 2014 (UTC)
I agree 3RR is not ideal. In my opinion 1RR works better; if an editor doesn't accept a single revert there is no reason to think they would accept 3 reverts. My suggestion is to count A's first edit of a stable version as one of reverts and thus to reduce the number of iterations before the editors must begin discussing. Another effect is that while the discussion goes on the article will remain in the state that had consensus previously.
"What if there was no consensus" - even if "now" there is no consensus, at some recent point in time there was a consensus, and then came an editor that changed the artcile from consensus, I called this editor A. It could be that A's edit is correct and justified while B is trying to OWN the article, yet until they (and other editors) reach a new consensus the default should be the previous consensus. “WarKosign” 20:34, 1 December 2014 (UTC)
"at some recent point in time there was a consensus" - Unless you assume consensus by silence, not necessarily. The vast majority of edits are non-contentious and never explicitly discussed. The idea that the "consensus" version or original version should be the default state during discussion is not supported by the letter or intent of any policy. The protection policy states that when protecting a page in a content dispute, it should be left in whatever version is there when the protection is applied, unless there are copyvio/BLP issues or there is an undisputed older version. Mr.Z-man 21:09, 1 December 2014 (UTC)
If "A"'s edit is "correct and justified", he should be able to convince others of that fact. The same goes for "B"'s objection to that edit. Neither will be able to "own" the article in the face of multiple editors trying to do what is right. So... if "A" makes an edit, and "B" objects... all either party needs to do to break the stalemate (and the revert cycle) is file an WP:RFC and let others settle it... stop editing and reverting for a while... call in outside opinions from neutral third parties (per WP:Dispute resolution) and let those outsider's determine whether "A" or "B" has the best argument. Hell... they may even be able to find the middle ground, and suggest compromise wording that both "A" and "B" can live with. Take a long term view... the article may temporarily be stuck at The Wrong Version while everyone sorts out the dispute... but eventually everything will get sorted. Don't insist... convince. Blueboar (talk) 21:19, 1 December 2014 (UTC)

So far I got mostly negative reactions, and I think they are based on the incorrect assumption I'm trying to promote edit warring. This proposed change is intended to reduce edit warring. 3RR and 1RR are intended to limit the number of reverts a single user can (not "entitled to") perform unpunished, but they do not handle group edit warring, and do not promote WP:BRD enough, and this is what I tried to amend. My proposal works best with 1RR, effectively becoming "Any edit that was reverted cannot be re-applied without a discussion. Don't revert more than once per day since you don't own the article." “WarKosign” 13:55, 2 December 2014 (UTC)

I'm not surprised. Dismayed, maybe, but not surprised. To give you an idea of where this stands, last year we had a long discussion about whether this constituted an edit war:
Editor A: Creates an unsourced stub
Editor B: Adds a source
Editor A: Adds a new section
Editor B: Corrects a typo
Editor A: Adds a source
Editor B: Moves a sentence into the new section
Editor A: Awards a teamwork barnstar to Editor B
We literally had people saying that this was an edit war, because "technically, any change is a revert", and that Editor B's first action was "reversing" Editor A's "action" not to have any sources in the article. Yes, it was a stupid position. Yes, we made a small bit of progress on this attitude.
However, the progress that we made did not extend to a correction of the problematic definition, because A "revert" means any edit (or administrative action) that reverses the actions of other editors, in whole or in part, whether involving the same or different material. means that Editor B was "reversing" Editor A's "action" of failing to source the material, his "action" of misspelling something, and his "action" of putting a sentence in a less desirable location, and a couple of people were worried that providing an accurate definition would hamper their ability to punish wikilawyering edit warriors. The fact that people have been yelled at and accused of edit warring for normal collaborative editing by admins who misunderstood this definition did not seem to bother them very much.
One clarification that I think would help is fixing the "same or different material" line. We don't actually mean that if you fix a typo that you're "reversing" an action. If you do this:
  1. reverse a new addition,
  2. wait until the first editor has restored it, and
  3. fix a typo in an entirely different part of the page,
then you have not "reversed the action of the editor" twice. You've only done it once (in step #1). What we mean by that line is that if Editor A adds spam to the lead, and you revert it, and then Editor A re-adds spam with slightly different wording, and you revert it, and then Editor A re-re-adds the spam to a different part of the page, and you revert it—that is an edit war. We don't mean normal editing plus one actual revert.
Also, it would be nice to have the policy directly say that a single revert by a passing vandal fighter is never punishable edit warring. We've had people say that if you're patrolling RecentChanges, and you see something that looks like spam or vandalism (or even something that just doesn't seem to improve the page), that it's your bound duty to first investigate the history to make sure that nobody else has reverted it recently, because if you're the second, third, or fourth person to remove the spam, then you're an evil edit warrior. WhatamIdoing (talk) 16:01, 3 December 2014 (UTC)
  • WhatamIdoing, apparently your explanation there is wrong based on this discussion which resulted in my losing my access to the Template editor usergroup based on me being accused of edit warring for making a series of entirely unrelated edits to a template which were all reverted. Now as far as the whole situation goes, I am over it, but I do find this discussion that suggests that my edits were in fact not edit warring, despite there "seeming to" have been a consensus at the time they were. As such, I intend to re-read this discussion a little more as I am fairly intrigued by this and would love to help with a clear definition of "revert" which apparently isn't very clear at the moment. — {{U|Technical 13}} (e • t • c) 16:52, 3 December 2014 (UTC)
Were you trying to do basically the same thing every time? Adding "tobacco kills people" to the lead, getting reverted, trying "tobacco can make people die" in another paragraph, getting reverted, and then adding "tobacco use is associated with shorter lifespans" at the very end of the article isn't "entirely unrelated". What I'm talking about is more like adding "tobacco kills people" to the lead, getting reverted, and then fixing the spelling of the word research in a different section. WhatamIdoing (talk) 22:03, 3 December 2014 (UTC)
  • No, what I did was set the documentation template to be hidden when editing a template that uses it. Another Template editor objected and reverted it. Instead, I wrapped the entire template in a classed span that did nothing at all to the display of the template for anyone (unless they added special css to their custom css file, which is what I was going to do to hide that template when editing templates so it wouldn't interfere and cause issues with previews). That was objected to by an administrator, and reverted on the basis the the class I used wasn't the same as another class used by a module. So, I made another edit using the the class I was told was preferred to use as it was part of the module (which was insufficient to hide the parts of the template that weren't in the module). That was reverted, the template fully protected, and my permissions stripped. To this day, in order for me to edit a template using {{Documentation}}, I have to remove the Doc template while I'm editing the template and put it back at the end. This is quite a pain and editing shouldn't have to be done this way. — {{U|Technical 13}} (e • t • c) 22:37, 3 December 2014 (UTC)
Three attempts to do basically the same thing (just in different ways) can be edit warring. Of course, it could also be collaborative editing: I tried to do this, you said not to do it that way, I tried to do it another way (one that I thought you would support), etc. WhatamIdoing (talk) 06:32, 4 December 2014 (UTC)
Technical... once you knew that others were objecting to your edits, did you ever go to a relevant talk page and try to explain why you wanted to make the edits you made? The determination as to whether a series of edits is disruptive or collaborative can often rest on doing something as simple as doing that. Blueboar (talk) 13:08, 4 December 2014 (UTC)
  • Blueboar, there was an ongoing discussion about it on my talk page, of which my subsequent edits were what I interpreted the objecting editor was suggesting I do instead of what I had done. I'm sure that if I requested to be in the group again at this point, it would be granted without much hesitation. I don't care to be back in the group for at least a little bit longer, so that's not the point. I'm just interested in how this topic intersects with that situation, and I'm quite interested in making sure that it is clearly defined someplace so that if this situation ever starts occurring again, and I see it or another editor that is aware of that definition sees it, they can say "Hey, take a look at this definition." — {{U|Technical 13}} (e • t • c) 20:14, 4 December 2014 (UTC)
Looks like there is not going to be a definition of what is and what is not a revert. "We demand rigidly defined areas of doubt and uncertainty!" “WarKosign” 19:47, 5 December 2014 (UTC)
A revert is whatever the itchy-fingered administrator wielding his ban hammer wants it to be. Always has been, always will be. Same for a definition of what "edit warring" is. Tiptoethrutheminefield (talk) 21:19, 8 December 2014 (UTC)

Verifiably false statements with unavailable citations

If I have sources to back up my claim that a particular piece of information is false, can I justify deleting it without having access to the sources that are cited for its inclusion in the article? PolenCelestial (talk) 00:41, 6 December 2014 (UTC)

I would not delete without discussion and consensus. You don't necessarily have to have access... but you should talk to those who do.
Remember that things are not always black and white... equally reliable sources often disagree with each other. When this occurs, we (Wikipeida's editors and article writers) have to maintain a WP:Neutral point of view about the dispute. One option is to "present the fact of the disagreement"... and explain what each side says. Blueboar (talk) 01:35, 6 December 2014 (UTC)
Thanks. PolenCelestial (talk) 04:06, 6 December 2014 (UTC)
It might be useful for you to quote verbatim the section of your source to help make your point. Make sure your quotation is accurate. There is no copyright issue in quoting small sections of a source for this purpose. Martin Hogbin (talk) 15:21, 6 December 2014 (UTC)
Especially on the talk page. Blueboar (talk) 02:54, 7 December 2014 (UTC)
If, of course, you have no kind of access to your source and cannot even copy the relevant section manually to the talk page then your case is much weaker. You are then relying on your memory of exactly what the source says. Maybe you misread it or have forgotten exactly what it says. In that case you do not really have a source at all and should aviod making contentious edits. Martin Hogbin (talk) 09:47, 7 December 2014 (UTC)
Does PolenCelestial mean a source being cited to support a piece of information does not actually support that piece of information, but he does not have access to that source to prove it? If a source does not support the content it is being cited as supporting, then the content is actually unreferenced and could be contested and deleted. But to start, and only if I was certain the given source did not support the content, I'd delete the source and fact tag the content for a while, and place a note on the talk page about why I fact tagged it. However, if sources are just in disagreement it would depend on whether one side is a very marginal viewpoint or if the disagreement is more widespread and both viewpoints need to be included in the article. Tiptoethrutheminefield (talk) 17:28, 8 December 2014 (UTC)

Child protection

I'm going to be blunt. The way child protection has been handled both in the past and is being handled at present has been far from ideal. The registration page is completely useless when it comes to informing children and minors about the need to protect their private/personal information and providing information to parents and guardians of children and minors about the potential dangers of children revealing any form of identifying or otherwise personal/private information and the immediately visible nature of userpages and talk pages. The Foundation's Legal Team, Arbitrators and administrators have had to intervene in the past to make use of revdel, oversight tools and bans to ensure that children and minors are protected and that child predators and paedophiles are not able to cause or effect harm on children and minors.

The present system is visibly inefficient, especially given how certain predators and paedophiles were able to do one or more of the following:

  1. possess accounts for as long as they did
  2. edit for as long as they did
  3. communicate with children in an administrative capacity
  4. gain the trust of and manipulate various members of the community in the way that they did

It speaks volumes about the community when the page for account creation does not at the very least contain a transclusion of Wikipedia:Guidance for younger editors and Wikipedia:Advice for parents. It is vitally important that the Foundation and the Community take steps to ensure that parents are made aware of the potential risks and dangers involved with having their child or ward edit on the English Wikipedia or any other Foundation wiki. There needs to be visible information on the account creation page — be it a brief summation of the information as contained on those advisory pages, or even a short statement of rights and responsibilities — something which makes it perfectly clear that the Foundation and the Community are committed to a safe and open environment, not just for the adult editors but for the children and minors who want to make a difference and who want to contribute positively.

I know for a fact that the safety of editors is something which the community takes seriously, but I feel that, of late, there hasn't been enough done to stress the importance that is due to the creation and maintenance of a safe and cooperative editing environment. Everyone deserves to feel safe from credible threats of violence and abuse. Safety is not a privilege, it is a right and it is one which, I feel, has been overlooked or not had as much weight given to it in discourse around and related to policy changes.

I think it also important that we look at redesigning the Main Page to accommodate links to important policies, guidelines and advisory pages. As it stands, the "Wikipedia languages" section is useless, the sidebar exists for that purpose. "Other areas of Wikipedia" could and should be changed to accommodate the navboxes for policies, guidelines and advisory pages. This virulent culture of maintaining the status quo on the Main Page simply because a handful of stubborn editors can't strike a consensus is, frankly, beyond me. The more we bicker and argue, the more Wikipedia becomes the pariah of the major websites in terms of its approach with respect to child protection.

I submit this for community discussion.

James (T • C) • 8:39 AM • 21:39, 4 December 2014 (UTC)

While I undoubtedly support linking to Wikipedia:Guidance for younger editors and Wikipedia:Advice for parents, these pages are too long, IMO, to be transcluded there. עוד מישהו Od Mishehu 12:22, 8 December 2014 (UTC)
@Od Mishehu: Perhaps a collapsible summary (which would be collapsed by default) or a paragraph-long summary indicating the risks of revealing private and identifying information in addition to links to the full pages? In any case, the registration page is worse than those of internet fora. Those at least give weight to the importance of child protection, Wikipedia's is horrendously lacking. James (T • C) • 8:15 PM • 09:15, 10 December 2014 (UTC)
A collapsable section of the expanded size of these pages would still mean loading all that content, and then it disappearing (I don't have a slow connection, yet I see this happening all the time at CFD). The signup page needs to be reasonably compact - and the captcha image counts towards size here, as does all the collapsed content. A paragraph summary with a link to these pages would probably work, IMO. עוד מישהו Od Mishehu 13:28, 10 December 2014 (UTC)

How well is Draftspace working

Sort of a side question, but it's related to the above proposal because people are comparing userfication to Draftspace. So... How is the idea of Draftspace working in practice? How many articles have been sent there since we started the project? How many have been worked on and moved back into Mainspace? I am concerned that Draftspace is simply yet another dumping ground for problematic articles that never get fixed. Some statistics would be helpful. Blueboar (talk) 01:49, 9 December 2014 (UTC)

  • I use draft space to create drafts for pages to be moved into mainspace when I get them into shape. I have on one or two occasions restored a previously deleted article into draft space and then fixed it up and filed a move request to obtain consensus for moving it back into mainspace (Buddha Bar is an example). bd2412 T 02:27, 9 December 2014 (UTC)
  • We need to filter out moves from main space to draft space to study that, which is still impossible to do from the log, we need a database query. I'm not aware of any tool, if anyone could help with that.. It's much less of a dumping ground than user space is, though. Cenarium (talk) 03:59, 9 December 2014 (UTC)


Statistical data: Current AfC pending drafts = 1,014

The following data sets show the comparison of the last three months for the number of submissions per day*:

Date123456789101112131415
Submissions 239 166 192 240 263 88 0 0 0 0 0 0 0 0 0
Date161718192021222324252627282930
Submissions 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
AfC submissions in November 2024
Date123456789101112131415
Submissions 222 212 217 301 131 179 239 313 220 330 193 177 127 264 221
Date16171819202122232425262728293031
Submissions 229 212 219 209 405 436 384 355 278 314 287 281 365 308 391 226
AfC submissions in October 2024
Date123456789101112131415
Submissions 193 269 265 201 190 310 264 196 184 195 181 200 194 175 228
Date161718192021222324252627282930
Submissions 245 309 227 221 221 219 311 251 398 270 287 199 189 200 248
AfC submissions in September 2024
Date123456789101112131415
Submissions 171 150 102 124 179 173 148 168 172 141 139 151 185 193 207
Date16171819202122232425262728293031
Submissions 154 139 121 187 194 198 196 208 138 154 225 300 207 192 209 163
AfC submissions in August 2024
  • approximate only as does not include deletions or multiple re-submissions on the same day
  • In the last two or so years of my participation at AfC have I seen the backlog of number of submissions has been the highest since the move to the Draft: namespace. I personally don't think that the way we did it is working. There was a group of people that were in such a hurry to create this new namespace, move everything into it, and deprecate the old ways of doing things, yet none of them took the time to think about how things should be processed or how to make the workflow work better. They ended up compounding the troubles with the system with new troubles that were caused from rushing towards an end result without planning and setting all the mechanisms in place to make it a useful change. This has been the problem I've had with this all along, and now the numbers are stacking up, and I'm hoping it is starting to be realized. I just hope that there are people interested in working together to develop a completely new system that works before the current hack of a system drives all of the people interested in reviewing new draft submissions away. :\ — {{U|Technical 13}} (e • t • c) 03:02, 9 December 2014 (UTC)
The statistics show that there has been a massive increase in the number of new submissions, it more than tripled, from about 40 a day a year ago to about 150 a day. That's the cause of the backlog, not the move to draft space. If anything it seems that the new process is more attractive, and there are multiple causes to that, including using drafts, so proper pages, better templates and a more streamlined process. AFC is also more heavily advertised, and some of the workload at NPP was simply transferred to AFC. If the workload is excessive, maybe some of it should be put back to NPP by attenuating the recommendation to use AFC at the article wizard for example. Having a namespace can provide additional benefits such as new pages patrol feed, which ought to be implemented sooner rather than later (while deactivating the user feed which is useless). It also means templates work as intended on articles and not as they would on talk pages, and users can use visual editor. I would also suggest to maybe be more inviting to potential AFC reviewers. The move to draft space had to be done eventually anyway because talk pages may no longer exist at some point. Though, the issue at hand is about moving articles to draft space, not AFC. Cenarium (talk) 03:49, 9 December 2014 (UTC)
  • The part that you are missing is that once a draft has been reviewed, it comes out of the categories that populate those templates. The useful part of that data is the last three months. The stuff from a year ago is skewed by the number of those "pending" drafts no longer pending. Another important factor is the backlog never got over 2K without a backlog drive, and there are some in WPAFC that are insisting that others can't run a backlog drive without their approval. This is contributing to the backlog being so high as well. Anyways, the move to Draft: hasn't improved anything, has caused some editors to push too hard and take ownership of the project with a goal to hastily move everything there and drive multiple valuable reviewers away in the process of doing so. — {{U|Technical 13}} (e • t • c) 04:19, 9 December 2014 (UTC)
  • I agree that there is a bit of ownership involved, the process should be more inclusive and open to new AFC reviewers. Still, I thnk the move to draft space was necessary, it may not have greatly improved efficiency but I can't see how it could impair it, and it has other benefits as noted above. It's my understanding that after a draft is reviewed, the AFC template is added to the talk page, which categorizes at the same date. But it's true that the statistics are biased with this method of computation, since it doesn't include deleted drafts, drafts where reviewers forgot to add the talk page template, drafts with wrong date, etc. They can't actually be used to prove anything. Cenarium (talk) 04:47, 9 December 2014 (UTC)
  • I may have been indirectly responsible for an increase in the backlog due to this edit in March which added a link to the article wizard (and requested articles) when viewing a non-existing article... Cenarium (talk) 23:31, 10 December 2014 (UTC)

So... it sounds like the answer to my question is that Draftspace is working... just not working as well as it could (or should). Would that be an accurate assessment? Blueboar (talk) 13:31, 9 December 2014 (UTC)

That's the impression I get. "Good process, not enough volunteers" - the wiki mantra. --NickPenguin(contribs) 15:54, 9 December 2014 (UTC)
I think it's ok but there's still a huge, huge backlog at Category:Userspace_drafts_created_via_the_Article_Wizard. I'm still weeding through five year stale drafts and I assume once those get closer to clear, most editors can focus on the newer drafts. -- Ricky81682 (talk) 00:01, 11 December 2014 (UTC)

gender-ambiguous name

I just made a one-word change to the article Jean Bassett Johnson (after some complications because it was previously mistitled "Jean Basset Johnson", with one "t"). I discussed it at Talk:Jean Bassett Johnson#name and gender:

The name written "Jean" is most often a female name in English. It seems only fair to the reader to clarify that the subject of this article is a man, and to do so sooner than 1/3 of the way through the second paragraph ("he and his wife").
This is probably a touchy subject. There aren't many ways to do this in English without seeming to shout about it. I've changed "Johnson" in the second sentence to "he" for the purpose.

I searched the Pump policy area and found some archived discussion from May under Gender of biographical subjects, but nothing definitive. If you want to discuss this, please {{ping}} me. --Thnidu (talk) 06:07, 10 December 2014 (UTC)

MOS:IDENTITY contains the current guidelines (primarily second bullet, written for people that change gender), however not detailing how high up in an article the first occurence of a gender indication should be noted. --Francis Schonken (talk) 06:50, 10 December 2014 (UTC)
Look at George Eliot for example. The name is unambigously male, the second sentense says "she" and together with the picture there is no ambiguty left. The second paragraph explains the male pen name.

I think in case of Jean Bassett Johnson the hint of his gender can be inserted as early a "...was an American anthropologist and linguist. He conducted field studies...", and together with the photo nothing else is needed. — Preceding unsigned comment added by WarKosign (talk • contribs) 09:43, 10 December 2014 (UTC)

I think that in all such cases (people without gender-related issues where the first name generally belong to the other gender), we should probably make it more explicit than mere use of the pronoun - and "his wife" doesn't quite do that, since lesbian women may end up having wives. עוד מישהו Od Mishehu 13:34, 10 December 2014 (UTC)
I entirely disagree that we need to do anything. Pronouns convey the matter perfectly, we can't anticipate that the reader may or may not have certain gender expectations based on names; Jean is a very male name in much of the world. Even in other cases, the pronoun "he" or "she" will be used within the second or third sentence, which establishes gender instantly for the reader. It doesn't matter whether it is Michael Learned or Tracy McGrady or the Boy Named Sue; there's no need to bend over backwards to draw attention to the fact that it's a person with a name which is more commonly associated with another gender. It's just a name, and we establish gender in natural ways using pronouns. --Jayron32 17:30, 10 December 2014 (UTC)
I'm surprised there is no gender parameter in person infobox. Infoboxes are often imported by external services, and even if the gender is obvious from the content of the article it may not be obvious just by looking at the infobox information presented in some external tool. “WarKosign” 17:41, 10 December 2014 (UTC)
I share your frustration. I have tried to introduce one; see, for example, Template talk:Infobox snooker player#Recent changes. Gender is held as a parameter in in Wikidata (P21), so it could be imported from there. {{Infobox user}} has one; you can see it deployed on my user page. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:47, 10 December 2014 (UTC)
I think the OP's point was that there was no such pronoun, at least not near the top of the article, so (s)he(!) added one. I apreciate and endorse such edits. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 21:50, 10 December 2014 (UTC)

NAC deletes

A discussion at Requests for Closure is questioning WP:BADNAC, specifically, the part about non-admins not closing discussions as delete. I think this is something that needs a larger discussion. I think it's a really bad idea, because tagging articles/redirects as {{db-xfd}} can be misleading, and the deleting admin might not catch that the tag was placed by the closer.--SarekOfVulcan (talk) 22:46, 12 December 2014 (UTC)

Tag for too many citations

Is there a tag to put on top of an article with citation overkill? For example, the HDMI article regularly has three or four references for a stated fact and a total of 209 references, which seems like overkill to me. Especially since it's not at all a controversial topic. I cleaned up a little, but i'd like to leave behind a tag to invite other editors to continue cleaning up. I previously asked this question at the talk page of the citation overkill policy, but no one responded. PizzaMan (♨♨) 14:27, 14 December 2014 (UTC) (PS if i posted this question in the wrong place, please point me to where i should post it)

First suggestion - combine the multiple refs into single citations - second, citation overkill is all too often found on Wikipedia as some editors think is one ref is good, twenty is better <g>. This is not simply solved by tags, it requires a complete change in practice. Sigh. Collect (talk) 15:09, 14 December 2014 (UTC)
Why couldn't a tag help such a change in practice? Either way, may i conclude that it currently doesn't exist (and there is no consensus for creating such a tag)? --PizzaMan (♨♨) 15:23, 14 December 2014 (UTC)
There was, but it was deleted. Mr.Z-man 16:00, 14 December 2014 (UTC)
I'm sure this also violates some kind of WP:policy, but :-( (but thanks for explaining) PizzaMan (♨♨) 16:31, 14 December 2014 (UTC)
  • Mr.Z-man, I don't suppose you would be willing to restore the contents of that template to my userspace or emailing it to me, I was actually considering creating a similar template and wouldn't want it to be a CSD:G4 if I did. If you (or any other administrator) (is|are) willing to do that, I would appreciate it at {{User:Technical 13/Templates/Overcite}} Now that I'm aware a similar template was deleted, I'll happily start a discussion and get consensus for it before moving back into template space, if appropriate. Thanks! — {{U|Technical 13}} (e • t • c) 17:10, 14 December 2014 (UTC)
@Technical 13:: Userfied. Mr.Z-man 17:40, 14 December 2014 (UTC)
I'm not exactly the most experienced WP editor but please let me know if i can contribute. I've written scientific papers and there it's common practice to use just the right amount of citations to support your statements, no less, no more. So perhaps i could contribute from that expertise. PizzaMan (♨♨) 00:34, 15 December 2014 (UTC)

Sure, PM, I've made the first revisions to the wording of the template and improved its features a bit. I've also changed the image to something a little better IMO. Feel free to see what I've done and provide any feedback on development on its talk page or my own. :) — {{U|Technical 13}} (e • t • c) 00:53, 15 December 2014 (UTC)

PizzaMan, keep in mind that WP:Citation overkill is an essay, not a policy or a guideline. Flyer22 (talk) 10:31, 15 December 2014 (UTC)

Should the +reviewer bit be removed from inactive reviewers?

This RfC has closed with a consensus against revoking the reviewer right from inactive reviewers. The userright does not have a high requirement, editors having the right and not using it cause no issues for the encyclopedia, and the Pending Changes log is rarely backlogged so it wouldn't be unsurprising for the right not to be used all that often. Sam Walton (talk) 23:12, 16 December 2014 (UTC)

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

There are currently 8014 reviewers, most of which have not made any reviews or edits to pages under pending changes protection in the last month or so. I'd like to suggest that reviewers who have not made any reviews for a month can have their reviewer bit removed by any sysop. There are a number of reasons for this, including the fact the flag is a common victim of hat collecting; Introducing a timeout, like we have for sysop, should hopefully reduce this. Also, this should better indicate who is actually responding to the requests, and if level 2 is ever rolled out, it shows who is actively using the user right, so who the people to approach are.
--Mdann52talk to me! 16:35, 16 November 2014 (UTC)
Happy editing, L235-Talk Ping when replying 16:40, 16 November 2014 (UTC)

TL;DR: proposal changed to 6 months of inactivity needed, and I'd like people to reconsider oppose opinions. Wall of text: I'd like to change the proposal a bit. I'd like the proposal to be removal if there are no reviews in 6 months. Also, re. no hatshopping seen: then you've never seen WP:PERM/PCR when it's busy- people request it, use it for a couple of days, then never use it again. It's not useful at all for reviewers that don't actually review anything. Also, I'm quite frustrated by what I feel is bandwagoning- people see an almost-empty support section and a quite lengthy oppose section, and have a bias towards opposing and unintentionally don't consider the merits of the proposal. It irks me that if Mdann and I had put down supports "as co-author" the proposal would be in a different direction right now. That was a bit harsh, sorry, but it gets the point across. --L235-Talk Ping when replying 05:09, 17 November 2014 (UTC)

Discussion (reviewers)

When reviewer first became available, it was handed out without request to around 5000 users (mostly by Courcelles [1]), this is where most of the "never reviewed reviewers" came from. –xenotalk 17:37, 16 November 2014 (UTC)

That's correct. Why should we keep these reviewers that aren't interested? --L235-Talk Ping when replying 17:59, 16 November 2014 (UTC)
(edit conflict) @Xeno: I'm not so sure. I've reviewed the logs for a number of accounts with reviewer permission (both recently granted and who have had it for a while), and most of these have never used it (or rarely have used it). User rights should only be granted if they are going to be used, not just so people have something in case it is useful one day. --Mdann52talk to me! 18:02, 16 November 2014 (UTC)
Just more of an observation than anything. If the proposal carries, admins should probably stop handing it out without request. –xenotalk 18:06, 16 November 2014 (UTC)

@Biblioworm: I agree on many points. Reviewer doesn't give you any possibility for abuse, that's true. One consideration here is hatshopping. This proposal would a) reduce the number of hatshoppers with the reviewer permission, and b) increase the rate of reviews as the hatshoppers that are interested in keeping the flag review pending changes. --L235-Talk Ping when replying 17:59, 16 November 2014 (UTC)

  • I would be willing to support the removal of the flag for inactivity, however, 1 month is way too short of a time period. — {{U|Technical 13}} (e • t • c) 21:26, 16 November 2014 (UTC)
    • I'm afraid six months is still too short. Let me make it clear what I would support. I would support removal of the bit from editors who were put in the group more than three months ago without requesting it and have never used it and or users who haven't used it in over a year. The main reason I would support it is to make {{NUMBERINGROUP:Reviewer}} more accurate as to the number of actual reviewers. — {{U|Technical 13}} (e • t • c) 17:09, 17 November 2014 (UTC)
  • Reviewers rights are granted liberally to trusted users regardless of whether they may use it or not because we didn't want this to be a closed system, and also because of PC2, for which there's no general consensus but which is used on occasion. There's no hatshopper issue, most of those users didn't even request it. Cenarium (talk) 22:01, 16 November 2014 (UTC)

Support (reviewers)

  1. Per the nom. I'd recommend a more liberal timespan like six months. Chris Troutman (talk) 00:46, 17 November 2014 (UTC)
  2. Sorta I support removal after 1 year of complete inactivity; it is very easy to request back if someone who has left the project returns in the future. — xaosflux Talk 05:19, 17 November 2014 (UTC)
  3. Sorta. I would say that if someone has been inactive edit-wise for over a year or more then it would probably be a good idea to remove permissions. Why? Because notability guidelines change and we can't automatically guarantee that the absentee reviewer would be aware of how much rules have changed- especially if they were from some of the "wild and wooly" times of Wikipedia. Even if the guidelines haven't had some sort of dramatic change, being gone for a year or more could have a negative impact on how well they remember those notability guidelines or some of the other pertinent guidelines of Wikipedia (BLP, etc). It's not like it's requesting adminship, so it's not that hard to get back and this way we'd ensure that they refreshed themselves on the basic guidelines of Wikipedia. Now if they are active but haven't used their reviewer status, then that's sorta debatable. I suppose that what we could do is just ask them after a few years if they want to continue using it- and more importantly, ask them why they haven't used it. I think that one of the biggest issues here is to try to find out why people aren't using their reviewer permissions and what we can do to improve the chances of them using it. Tokyogirl79 (｡◕‿◕｡) 04:27, 18 November 2014 (UTC)
    I think one of the reasons is that there just aren't that many opportunities to use it. I don't head over to Special:PendingChanges that much at all (just review now and again when they appear on my watchlist), but right now there's only four articles in the list. At least there's no backlog! Putting more pages under pending changes seems to be a good idea, we can obviously cope with it. Dylanfromthenorth (talk) 05:13, 18 November 2014 (UTC)
    Right now, pending changes is only approved for use in fairly limited circumstances - vandalism/disruption from anon/new users that is frequent enough to be considered "persistent", but not so frequent that semi-protection would be a better option. Mr.Z-man 14:05, 18 November 2014 (UTC)
  4. Sort of weakly support, exactly like Xaosflux says. All advanced flags should presumably follow the same rules as the admin bit: If you are 100% inactive (not just inactive on pages requiring that particular flag) for at least one year, then you should probably (I guess) lose the reviewer flag. I don't think that this is hugely important, however. WhatamIdoing (talk) 19:13, 18 November 2014 (UTC)
  5. Support. Use it or (after 6 months of not) loose it. Tiptoethrutheminefield (talk) 15:30, 21 November 2014 (UTC)

Oppose (reviewers)

  1. Oppose. The admin bit is only removed after a year of inactivity because it can be very dangerous if it falls into the wrong hands. Sure, the reviewer permission gives you the ability to approve edits and edit PC protected pages without being reviewed, but it is not a dangerous tool. Besides, suppose a reviewer goes on an extended vacation or is busy doing other things on WP. Doing this would just make things unnecessarily complicated. --Biblioworm 17:27, 16 November 2014 (UTC)
  2. Oppose - (IMO) No real need to remove, unless "extra drama" is needed. Mlpearc (open channel) 17:33, 16 November 2014 (UTC)
  3. Oppose. Accepting reviewer permission does not imply the editor will start watching pages that are not already on his/her watchlist. If there are few or no pages on the reviewer's watchlist with pending changes activated, naturally the reviewer will not have much occasion to use the permission. Jc3s5h (talk) 18:30, 16 November 2014 (UTC)
  4. Oppose per Jc3s5h. This seems to be a solution in search of a problem. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:57, 16 November 2014 (UTC)
  5. Oppose The OP states "There are a number of reasons for this,..." (justifications for the proposal). They have provided a single, IMO rather weak reason. If there are further reasons the OP might like to share them in detail. Otherwise it has no merit. Leaky Caldron 19:13, 16 November 2014 (UTC)
  6. Oppose. Even the most active of editors sometimes go inactive for months, either for RL commitments or wikibreaks. Forcing them to reapply when they return adds an extra layer of bureaucracy and creates unnecessary work for the admin corps. Altamel (talk) 20:09, 16 November 2014 (UTC)
  7. Oppose. Why would we want to remove it? To make it harder for volunteers to do volunteer work? I can't fathom why this would be a good idea. Kaldari (talk) 00:46, 17 November 2014 (UTC)
  8. Oppose. Not everybody edits in every single month, let alone does reviews, and implementing this will greatly reduce the number of reviewers to pass pending changes requests, thereby causing more backlogs. Reviewer permission does not imply that the user will be reviewing pages 24/7. Finally, one can't go rogue with the reviewer permission like they can with admin permission; a wrong review can quickly be undone by any autoconfirmed user, while if a block is mistakenly placed, another admin has to come along and unblock. Epicgenius (talk) 00:48, 17 November 2014 (UTC)
    Still oppose with six months. I'd like to see at least a year of total inactivity (not reviewing inactivity; I mean, zero edits in a year) to remove this right. Epicgenius (talk) 16:49, 17 November 2014 (UTC)
  9. Oppose. I've no idea what we'd gain by removing it from people. If there was a finite number we were able to give out, then maybe, but there isn't a finite number of reviewer permissions. I can well imagine that editors/reviewers like to focus on one type of edit for a good while, then another type etc etc, and those phases could last for any amount of time. I know I do; sometimes I'll be focussing on referencing articles, sometimes on NPP, sometime in AfD, or whatever. Dylanfromthenorth (talk) 01:08, 17 November 2014 (UTC)
  10. Oppose What others have said above is very true. Additionally, compared to recent changes and new pages, the amount of work needed for PC reviewing is magnitudes lower, and reviewers sometimes may not have any pending change to review. And 1 month is way too short, IMO. Zhaofeng Li [talk... contribs...] 04:36, 17 November 2014 (UTC)
    Thanks for changing the proposal. 6 months is indeed better. But anyway, L235, you really should consider our reason given for the opposes before blaming bandwagon. Zhaofeng Li [talk... contribs...] 10:12, 17 November 2014 (UTC)
  11. Oppose This is a solution in search of a problem. If wikipedia had a problem with mass vandalism caused by sleeper PC-approved users, then sure, but there's no utility to be gained by putting an expiry on the tool as a rule. Deadbeef 07:20, 17 November 2014 (UTC)
  12. Oppose Sometimes a whole month goes by without anything to review. Hawkeye7 (talk) 08:14, 17 November 2014 (UTC)
  13. Oppose - Hat collecting is an "issue", but I wouldn't say it rises to the level of a "problem" that warrants the creation of a new process and more work for admins. Also note that the inactivity requirement for sysop doesn't require actually using the tools, just making an edit every 12 months. If we're going to do this (and I don't think we should), using a stricter standard than for sysop doesn't make any sense. Mr.Z-man 15:45, 17 November 2014 (UTC)
  14. Oppose per Mr.Z-man. Ncmvocalist (talk) 15:53, 17 November 2014 (UTC)
  15. Oppose - Not everyone edits in a month and if everyone needs to take breaks and whatnot It's going to be a pain in the arse!, All in all IMHO this'll create more crap instead of less. –Davey2010 • (talk) 16:42, 17 November 2014 (UTC)
  16. OpposeLittle use in removing this bit from people even after long inactivity. Admin bits can be abused or accounts can get compromised and can really damage the wiki. A reviewer bit getting compromised? I'd be more concerned about vandals finding out about the backlinks feature of Twinkle, tbh rather than this. Oppose. Tutelary (talk) 23:14, 17 November 2014 (UTC)
  17. Oppose — I hope the fact that I'm a long-term reviewer doesn't weigh heavily against me here, considering the fact that I haven't done very many reviews (and none in at least a year). I just don't see the point of revoking access to this user right. It's not really the type of tool that's easily abused; you click a button and approve an edit. It also allows you to contribute to PC-protected pages without having to have your every contribution scrutinized beforehand. "Hat collecting" is a ridiculous reason to strip people of advanced permissions; if you are unable to prove that they can't be trusted with them, then why bother complaining? To offset accusations of "bandwagoning", I didn't even read past the first paragraph before I knew that I'd be against this proposal. My opinion here would remain the same if I were the last man on Earth Wikipedia holding it. Kurtis (talk) 17:21, 17 November 2014 (UTC)
  18. OpposeThis is just more trouble than its worth. Unlike with admins, there is no real benefit to removing reviewer rights from everyone who is inactive. Doing so will just waste our admins' time and prevent them from doing more important work. Additionally, what about infrequent reviewers or users who go on long hiatuses? I imagine many people with the reviewer right fall into these category, and it seems silly to remove rights from people who are positively, if infrequently, contributing. Spirit of Eagle (talk) 03:44, 18 November 2014 (UTC)
  19. Oppose- there does not appear to be a problem in need of solving here. So what if inactive users have the reviewer bit? Reyk YO! 07:36, 18 November 2014 (UTC)
  20. Oppose - Pointless bureaucracy, trying to solve a problem that is nonexistent is always a bad idea anyway. Lukeno94 (tell Luke off here) 17:33, 18 November 2014 (UTC)
  21. Oppose As has been noted by many others, no case has been presented that makes it clear that these users having an unused low-level userright causes harm. Should we remove autoconfirmed status from anyone who has not edited a semi-protected page in six months? Should we remove rollback from users who don't use it? Of course not, because it doesn't accomplish anything. Neither would this. Beeblebrox (talk) 22:57, 18 November 2014 (UTC)
  22. Oppose - a solution looking for a problem. --Kudpung กุดผึ้ง (talk) 07:33, 19 November 2014 (UTC)
  23. Oppose - There are only about a dozen pages at Special:PendingChanges awaiting review, and you are going to disparage some six thousand reviewers as "hat collectors" because there aren't enough pages to go around for all of them to review? Maybe the problem is that the process for configuring pending changes settings doesn't configure enough pages? There's about one page on my watchlist that's so configured, and half the time I can just revert it, which doesn't require the hat, which is why I haven't bothered to ask for it. Wbm1058 (talk) 16:38, 19 November 2014 (UTC)
  24. Oppose - pointless work, and no real advantage. HÆDOreply 03:33, 21 November 2014 (UTC)
  25. Oppose I fail to recognize the problem which this proposal would solve. I think the asserted problem is lack of uniformity in the process of maintaining user rights, but this is not recognized problem and I see no argument in this proposal which describes it as troublesome in this case. Blue Rasberry (talk) 15:10, 21 November 2014 (UTC)
  26. Oppose Mostly harmless. Should only be removed if there's evidence of abuse. NE Ent 02:55, 22 November 2014 (UTC)
  27. Oppose Why do we even need to remove their reviewer privileges? It is a total waste of time. What outcome would this have on Wikipedia anyway? The people might be taking a small break. When they come back, they will be distraught to find no reviewer privileges. If we used a robot, that would be faster, but it makes no sense. We need all of the reviewers we can get, anyway. EMachine03 (talk) 22:56, 24 November 2014 (UTC)
  28. Oppose Reviewer is only a small indication of trust. Not much havoc could result from a compromised reviewer account. Even though I strongly supported the sysop timeout, the potential damage here is just too low to justify removal. To me it's a flag that's more similar to autoconfirmed than any kind of sysop level permission. Gigs (talk) 18:28, 26 November 2014 (UTC)
  29. Oppose No sign of there being a problem here to be solved - for example, it would make more sense to remove all permissions to use varying fonts, AFAICT, or require special flags to add images to articles, each of which would seem a far bigger "problem" than has been presented here. Collect (talk) 18:47, 26 November 2014 (UTC) .
  30. Oppose We de-sysop administrators for inactivity as a safety issue, not a punitive one. An authorized user gaining access to the administrator tools is far more dangerous than one that gains access to pending changes review. Therefore I don't see much of a need to stir up drama by removing reviewer tools, in which case we may as well have over user rights, like rollbacker and template editor, removed for inactivity as well. We don't need more drama, do we? --I am k6ka Talk to me! See what I have done 14:46, 29 November 2014 (UTC)
  31. Oppose per WP:VOLUNTEER and even if inactive, we'd still have a pool of reviewers that could become active any time and help if they so choose. --lTopGunl (talk) 16:22, 29 November 2014 (UTC)
  32. Oppose I see no issue that needs to be "fixed" here. Irondome (talk) 22:25, 3 December 2014 (UTC)
  33. Oppose Why should an infrequently-used (rather innocuous) capability be taken away from a user? What would be next, removing the ability to edit articles if none have been edited in the past six months? --R. S. Shaw (talk) 01:08, 4 December 2014 (UTC)
  34. Oppose as a solution in search of a problem, as a proposal that would replace a problem that isn't a problem with a problem that is a problem, because it would create an unnecessary bureaucratic overhead, and because you can't actually do any damage with reviewer rights. HJ Mitchell | Penny for your thoughts? 22:57, 8 December 2014 (UTC)

Other comments (reviewers)

  • If most of the reviewers don't want to review... that says something about how the community views the entire review process. Is (perhaps) the idea a well intended, but failed experiment? Blueboar (talk) 19:20, 16 November 2014 (UTC)
Your first sentence appears to be a non-sequitur. Review is in my experience used for what is on your watch list, and several articles may have multiple reviewers watching but its not a race. Alanscottwalker (talk) 20:17, 16 November 2014 (UTC)
It's more like reviewers don't have much to review, which is a good thing. The backlog is well under control, so on that count this experiment, as you say, is a success. Cenarium (talk) 21:41, 16 November 2014 (UTC)
I'd like to see pending changes used more often but the community only seems willing to apply PC1 (or PC2) for editor behavior issues rather than preventative content protection. Chris Troutman (talk) 00:54, 17 November 2014 (UTC)
  • Not in my case; my recent requests for protection have been for PC, for articles that aren't really getting semi-protection levels of vandalism, but where the vandalism isn't being caught very quickly, and it is happening at least once every couple of days, on fairly high traffic pages. Both were granted, as well. Lukeno94 (tell Luke off here) 19:52, 18 November 2014 (UTC)
  • I'd like to see more pending changes applied to articles as well, especially the extremely popular articles that are vandalized, spam edited, or similarly unhelpfully edited at least once a month. (By this I mean that it's not spam, personal attacks, or vandalism, but people writing in obviously non-usable content along the lines of what you'd read on a fan page or rumor site. You know, the stuff that is almost always inevitably reverted when it's caught.) I know that when I was just getting started with editing I would get very, very frustrated with pages like this and get even more frustrated when the pages would get semi'd but not really protected because the problem editors knew how to get around semi protections. I still get frustrated with those, I must admit. Tokyogirl79 (｡◕‿◕｡) 04:32, 17 November 2014 (UTC)
    • There are probably at least hundreds of thousands of pages where non-usable content is added at least once a month. It would be too contentious (just adopting pending changes is one of the most contentious decision en.wikipedia ever made). It would also risk bogging down the entire system because reviewers would no longer have clear cut criteria, resulting in huge backlogs. This looks more like flagged revs than pending changes, and consensus has always been strongly against flagged revs. I think the only potential extensions are targeted proposals like Wikipedia:Pending changes blocks. Cenarium (talk) 05:39, 17 November 2014 (UTC)
  • As one of the people who helped push the decision on whether to use PC over the finish line after it had been stuck in limbo for several years I have to say it was always the consensus in every discussion I can recall that the reviewer right should be easy to get. In practice (at WP:PERM) it seems it is generally just slightly harder to get than rollback. The reason is that it has as little potential for causing real harm as rollback does. If someone is mis-using this tool, by all means, yank it back, but there is no need to take it away from users just because they aren't using it. If hat collectors think this very low-level tool gives them some sort of prestige that is their problem, there's no need to do anything about it. Beeblebrox (talk) 23:03, 18 November 2014 (UTC)
    • Yep, that was one of the big selling points we used to help get it passed, that it wouldn't be a closed group and that most any sane editor could probably get the permission. Gigs (talk) 18:31, 26 November 2014 (UTC)
  •  Comment: as one of those give the pending changes right without my knowledge or my asking for it, the biggest reason for my not using it was that I didn't know I had it. It was a surprise when I did discover I had it; but once I knew I had it I have used it. Perhaps the best way to get those with this right to use it, would be a message to all who have it that they do and how to use it, and that when it is handed out without the user asking for it for them to receive the same message. Rather than restricting the right maybe the best thing to do is to go in the other direction, grant it automatically (in the same way autoconfirmed is) for everybody, with for example, a registered account of over a year, 1800 edits and no blocks. With it remaining in the remit of admins to grant when the automatic criteria have not been met--KTo288 (talk) 07:58, 14 December 2014 (UTC)
    • With regard to not knowing about it, now the echo extension notifies in case of change of usergroups. I don't think that a mass message would be much appreciated at this point. There has been proposals to grant it automatically after some criteria are met but they failed. They were all made before actual implementation though, as far as I'm aware, and my guess is that a new proposal now may be much more likely to gain consensus. Cenarium (talk) 21:39, 14 December 2014 (UTC)
      • I don't know, the backlog always stays so low, people would probably argue that auto granting isn't really necessary. I personally wouldn't care either way. Don't think it's needed but wouldn't care if it was put in place. Gigs (talk) 17:10, 15 December 2014 (UTC)
The discussion above is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.

Should a Check user issued indefinite block be considered as a community ban?

In a recent ban discussion, and some not so recent ones, editors have opposed the institution of a community ban on the basis that the user under discussion was indefinitely blocked by a checkuser. Their rationale is that such a user is considered de facto banned as only a checkuser would be authorised to lift the block. I use the word "authorised" in the sense that non-Checkuser admins would automatically defer to the CU admin. Thus, for the sake of removing the need for ban proposals and hence saving time, should the community ban policy be amended to any user that has been indefinitely blocked by a checkuser is considered banned and may only appeal to the Arbitration Committee or BASC for repeal of the ban. Unblock reviews should be referred to a CU admin, or some variant thereof? Blackmane (talk) 00:21, 16 December 2014 (UTC)

It sounds like the only practical effect of this would be to basically prohibit CUs from undoing their own blocks. Mr.Z-man 00:28, 16 December 2014 (UTC)
Oops, that's not what I intended. Amended the question in italics. Blackmane (talk) 00:48, 16 December 2014 (UTC)
  • this looks like a solution on search of a problem. HJ Mitchell | Penny for your thoughts? 01:12, 16 December 2014 (UTC)
  • I agree with HJ Mitchell on this one. — {{U|Technical 13}} (e • t • c) 01:14, 16 December 2014 (UTC)
  • Still seeing the same problem here. It would require very significant resources of very busy editors in order to undo a checkuser block. Right now, checkusers can do that themselves. This is overkill. I think probably what you want to say is "Checkuser blocks can be altered or lifted by checkusers and may or may not be related to otherwise-blocked or banned editors. They are not equivalent to or a replacement for a community ban, which is decided by the community as a whole and can be lifted by Arbcom, BASC or a consensus discussion within the community." That is what I'd suggest you aim toward. Risker (talk) 01:16, 16 December 2014 (UTC)
Thanks for that, Risker. That is closer to what I was aiming towards. My wording is quite clumsy on a re-reading. As you well know, indef blocks are not considered community bans unless there are serious follow up transgressions by the blocked user, such as socking, legal threats etc, and even then a ban discussion is still required. However, a CU indef is often treated differently and the comment is frequently "such-and-such user has been CU indef'd, they're as good as banned". This is then considered a good enough reason not to require a community ban discussion. So what I was aiming at was adding it into policy that a CU issued block is as good as a ban and doesn't require a follow up community discussion to formalise it. Blackmane (talk) 01:48, 16 December 2014 (UTC)
There's very little difference between a block and a siteban in practical terms, and community-banning editors who are indefinitely blocked and have no hope of being unblocked in the near future is pointless, because an indef block that has been reviewed by multiple admins and will probably never be lifted is a siteban in all but name. Save community banning for the contentious cases that can't be effectively handled by individual admins. Cf. WP:NOTBURO. HJ Mitchell | Penny for your thoughts? 03:08, 16 December 2014 (UTC)
Hmm, a point that I certainly agree with. It's been raised on AN and ANI enough times. I guess what I'm seeking is some way to avoid the obvious non-contentious multi-reviewed indef blocks being raised on AN and ANI for site ban discussions where it's just about getting a nod from enough people to acknowledge what is already evident. It's less about having something bureaucratic and more about a common sense blurb. Blackmane (talk) 21:54, 16 December 2014 (UTC)
I acrtually did run into a case where a checkuser block was incorrect. To summarize the case, a complete newcomer did 3 reverts on a single article, and got warned about 3RR. Then the user did a fourth revert while logged out. The user and the IP address got a 24 hour block (correctly), and a checkuser block about an hour later. After the original 24 hours were up, the user made a request in which (s)he admitted that (s)he was the anon who did the fourth revert, and said that the log out was accidental. (I've seen this happen to me once in a while, so that lasty claim is plausable.) As there was no evidence of any other sockpuppetry-related issue, several users (including me) argued that the user should be unblocked (on the user's talk page), and (s)he was. עוד מישהו Od Mishehu 10:50, 17 December 2014 (UTC)

When consensus screws thing up real bad

Anyone who has constructive ideas (note: not a rehash of negatives, please!) is welcome to comment here. I was told that this ("Accuracy versus consensus") was not the right place to get input on it. --SergeWoodzing (talk) 19:10, 1 December 2014 (UTC)

It's not really a question of accuracy vs. consensus... it's more a question of what is accurate in English vs. what is accurate in various Scandinavian languages. The English language sources spell the subject's name one way, while Scandinavian sources spell it another way. Since this is the English language version of Wikipedia, we follow the English language sources. Blueboar (talk) 20:12, 1 December 2014 (UTC)
I appreciate your interest and attempt to reply, but you've taken a sloppy look and missed the point. It's not at all question of spelling but of two different names, as different as Edward (Edvard in Swedish and German) versus Howard (Howard in Swedish and German) or as Blueboar versus Bluebear. (See all the other relevant examples I also gave please!) I asked that irrelevant arguments like yours not be rehashed. Spelling is irrelevant here. My name is correctly spelled Sergio in Spanish and Sergius in Latin (those are legitimate exonyms), but Serde or Serve or Serke in no language. If a Serke Woodzing exists anywhere, in any country, in any language, that is not me. Get it? --SergeWoodzing (talk) 00:34, 2 December 2014 (UTC)
Duplications stricken - see here! --SergeWoodzing (talk) 00:41, 2 December 2014 (UTC)
You seem to be forum shopping at Wikipedia:Teahouse/Questions#Accuracy versus consensus and now here. There is already plenty of discussion at Talk:Hedwig of Holstein where it belongs. Please don't forum shop, and don't disparage disagreeing editors or try to ban them from discussing the issue. They have the right to participate. Your excessive bolding is also annoying. If you want support for your case then I suggest trying to find some reliable English sources for the spelling instead of keep arguing that we should ignore consensus and spelling in English sources. PrimeHunter (talk) 04:10, 2 December 2014 (UTC)
"Now here"!? I've struck just about the whole thing and referred the matter on to exactly the page you pointed out! Didn't you notice? What "how here"? I was also specifically referred here from the Teahouse. Didn't you notice that either? I have every right to ask people not to discuss matters that obviously are irrelevant to a discussion I started and to try to get them to focus on the issue. I also have the right to use bold type to remind errant people of what the issue actually is, when they comment without having read. Since the issue is not a matter of spelling - didn't you notice that either? - I'll have to chalk your unhelpful, issue-disregarding and condescending lecture up to what the Swedes call blåskontot. ask: why lecture? Why not contribute something constructive? --SergeWoodzing (talk) 12:15, 2 December 2014 (UTC)
PS PrimeHunter versus Prime Hunnter would be a spelling issue. PrimeHunter versus PrimePunter would be an issue of two different names. That's what this is all about. --SergeWoodzing (talk) 12:22, 2 December 2014 (UTC)
The Teahouse post said "If you wish to propose a change to Wikipedia's policies or procedures, the Village pump is the place to go". You don't appear to be proposing a change to the policies Wikipedia:Article titles#Use commonly recognizable names or Wikipedia:Consensus. You want a specific article moved. That discussion belongs on the talk page of the article. If I was notable and was generally called PrimePunter in reliable English sources then that's what a Wikipedia article should probably call me, with a remark that my Wikipedia username is PrimeHunter. Similar to the opening line already mentioning the German name you want. You don't have the right to decide that our naming policy about common English names is irrelevant and that people must not refer to it in a naming discussion. And you don't define what "the issue" is and control the discussion just because you started it. PrimeHunter (talk) 18:34, 2 December 2014 (UTC)
I do not understand or support your personal opinions about discussions, nor why you think you have the right to order me around like a dictator as if you owned Wikipedia. To me it's very important that we don't all waste a lot of time and energy discussing irrelevant things. Clouding the issue is a destructive discussion tactic, not a constructive one. It's more destructive than me reminding people to discuss a certain issue in a discussion I started, or you doing that too, if you don't want your debate inflated and ruined by virtual filibustering. If someone starts a discussion on a certain issue I would always try to be considerate to everyone involved by discussing that issue, not a lot of things that I would like to steer the discussion away to, but that are not what the discussion is about. It's a matter of consideration, not of what you or anyone else feels I am allowed to do in a discussion I started. You don't make the rules all on your own, and neither do I. If people are considerate, and discuss ethically, we never need to argue about things like this. --SergeWoodzing (talk) 20:50, 2 December 2014 (UTC)

Proposed change to Wikipedia's policy on naming biographies:

  • When it is obvious that an article has been given a name which is not that of the subject person, because of a small amount of English language sources through which that incorrect name has been spread on the Internet, WP:Common sense should prevail. No article should be given a name which is not based on facts as to the actual name of the subject person in his/her life or in history therafter. What a small amount of English language sources tell us is not a fact in every single case. --SergeWoodzing (talk) 21:03, 2 December 2014 (UTC)
The thing is... when the majority of English language sources use name "A"... common sense is for the English language Wikipedia to use name "A". And it is not at all "obvious" that name "B" is in some way more "correct" than name "A". Your campaign is directed at the wrong target. We reflect what the sources say. If you think they are "wrong", take it up with them... not us. Blueboar (talk) 21:51, 2 December 2014 (UTC)
The only real exceptions I can think of are extremely rare exceptions where there might exist only one or two English language sources about a topic which all use the variant name. Actually, in some such cases, I honestly could see saying that the sources are wrong, if, for instance, the publishers or writers or other reliable sources say that there was an error in the texts used. But in such cases, it would still be incumbent on the person hoping to ignore those English uses to verify such information as per WP:BURDEN. John Carter (talk) 02:34, 3 December 2014 (UTC)

Support (naming biographies)

Oppose (naming biographies)

  1. as the proposal is to my eyes excessively long and to some degree redundant, and that there already exists a relevant policy, WP:COMMONNAME, which deals with these matters. John Carter (talk) 21:45, 2 December 2014 (UTC)
  2. Yup... WP:COMMONNAME deals with it well. Blueboar (talk) 21:52, 2 December 2014 (UTC)
  3. An editor shouldn't arbitrarily decide that it's "obvious" that all English sources are wrong and must be ignored. This is the English Wikipedia. WP:COMMONNAME is fine as it is. PrimeHunter (talk) 22:32, 2 December 2014 (UTC)
  4. This is a proposal to disregard verifiability in favor of "truth" (as determined – at best – via original research). "Contradict reliable sources when it seems obvious to you that they're wrong." is about as inconsistent with our core policy as possible. —David Levy 02:00, 3 December 2014 (UTC)

Comments (naming biographies)

Is anyone interested in addressing the actual problem, touched upon by John Carter above (thank you!), or is everyone interested only in defending and perpetuating a system that makes such problems (albeit rarely) come up? Ergo, what do we do when an article has a name which we can agree (given enough interest!) is not correct, as in not factually associated with the subject person? Do we ignore the fact that the arcticle is incorrectly named? Did you all miss the words "small amount" in the proposal or did you just choose to ignore them? Constructive suggestions? --SergeWoodzing (talk) 00:56, 4 December 2014 (UTC)

The constructive suggestion is to find reliable English sources that say that the reliable sources upon which an article is based were actually in error as to the subject name. When all the English language sources call something a particular name, that is its name in English. Unless you can document in reliable sources that the subject, because of confusion or unfamiliarity, is actually supposed to be called something other than what the English language sources are calling it, then you are engaging in original research, pure and simple. Find sources that say other sources are wrong about the name, and people will begin to discuss whether a change can be justified. VanIsaacWScont 01:17, 4 December 2014 (UTC)
That would be fine in a few cases where the subject person is well known enough in English literature to be discussed like that. Obviously (to me), when unfortunate things like this (rarely) happen, that is never the case. Then what do we do, if we all agree that the name is wrong, based for example, on unanimous reliable sources in a language or two of the person's origin(s) where more has been written about h, whereas we only have a very few and questionable English texts with the wrong name? That's what I'm after. --SergeWoodzing (talk) 01:40, 4 December 2014 (UTC)
Well, that's just it: you're the only one that thinks the name is wrong. Aside from you, we actually all agree the exact opposite of what you are trying to claim, and policies like COMMONNAME are a codification of that same agreement by hundreds or even thousands of English Wikipedians for the last decade +. English Wikipedia names its articles on the basis of reliable English language sources, and will only consult non-English language sources when English language sources don't exist. When those English language sources say the name of an article subject is X, that is what our policies and long-standing consensus say our article needs to be titled, and it is immaterial if some other language sources or an editor happens to think the "correct" name is actually Y. When all English language sources call a subject X, that is it's name in English. Period. VanIsaacWScont 02:53, 4 December 2014 (UTC)
I don't trust a Wikipedia editor to decide that there are too few English sources and that the native sources unanimously use another spelling. The whole proposal is based on your quest to change Hedwig to Helwig for a German-Swedish woman. I find many English sources for our current name Hedwig, and did you even try to search for native sources? I immediately found Hedwig in both Swedish and German sources, for example [2] and [3]. By the way, our German article de:Helvig von Holstein is older than the English article and has included the alternative name "auch Hedwig von Holstein" from the beginning. And if you keep claiming that every single use of Hedwig is "obviously wrong" by people who didn't know her only "real" name Helvig/Helwig then [4] is an interesting source. It's a Swedish folder with the same text in Swedish and English. The Swedish text says Helvig. The English (below the child photo) says Hedwig, and only Hedwig. PrimeHunter (talk) 22:28, 4 December 2014 (UTC)
So according to you, Hedwig is the English name form for Helwig, the same name. Mind blowing! No use to even discuss something like that. And it hasn't occurred to you that that the further spreading of this error through WP is exactlty what i'd like to try to prevent. It's been going on for years now. --SergeWoodzing (talk) 00:48, 6 December 2014 (UTC)
Wikipeida is not the place to right great wrongs. The fact is, even if all those English langauge sources are using the wrong name... it is not our job to correct them. We reflect the sources, we don't lead them. If the English language sources are wrong, take it up with the authors and publishers of those sources... convince academics to comment on the error in academic journals, and to start using the right name in their writing. Once that occurs, Wikipedia will quickly follow suit. but as long as the English language sources call her Hedwig, so will Wikipedia... the best we can do is note that Scandinavian sources call her Helwig. Blueboar (talk) 01:22, 6 December 2014 (UTC)
The discussion is about a particular 13th century woman called Hedwig of Holstein in some English sources. If Wikipedia says North Korea instead of "Democratic People's Republic of Korea" then it isn't a general claim that "North" means "Democratic People's Republic of". PrimeHunter (talk) 04:09, 6 December 2014 (UTC)

WP:UE policy covers this. There is further guidance at Wikipedia:Naming conventions (use English) specifically to this discussion No established usage in English-language sources. -- PBS (talk) 14:27, 17 December 2014 (UTC)

policy about images on Wikipedia

Hi, im not sure if there IS a policy about this, but in the article 2013 Egyptian coup d'état there is a picture of dead mursi supporters. Is this really ok on a website viewable by children?

--Knight of Ni (talk) 12:52, 13 December 2014 (UTC)

There is a policy... see: WP:What Wikipedia is not#Wikipedia is not censored. Blueboar (talk) 13:22, 13 December 2014 (UTC)
Generally Wikipedia is not censored. If the image is relevant and provides information useful in the article that cannot be provided by a less offensive image, it should be there. There is another discussion on how potential child readers should be protected, or at least their parents informed. “WarKosign” 13:23, 13 December 2014 (UTC)
I agree, if anyone wants to make a case for removal of this particular image it should be based either on arguments regarding relevance or if someone finds another image that they believe is less offensive as well as equally relevant and useful.--69.157.253.160 (talk) 17:33, 13 December 2014 (UTC)
Everyone above's spot on we're not censored - Although you could simply block the image with Adblock Plus if it bothers you that much. –Davey2010 • (talk) 07:48, 14 December 2014 (UTC)
I think the point is not this specific image but a whole category of potentially offensive images. I can imagine how each image could be somehow rated on some offensiveness scales (sexual 0 to 10, violent 0 to 10, religiously offensive 0-10), and then the readers would be able to set their thresholds, either in wikipedia settings or by blocking a certain html pattern in Adblock. Of course there are big question to answer before it can be done:
  1. Which offensiveness categories to use, how are they chosen ? Many people can take offense at completely different things, which potentially offensive subject is mainstream enough and which is fringe ?
  2. Who decides how offensive an image is in each category ? This is a matter of personal taste and opinions may differ wildly within the same category.
  3. What is the default rating for images that did not undergo this process, such as all the images currently in use ?
“WarKosign” 10:20, 14 December 2014 (UTC)
Been there, done that and discovered a remarkable number of (white, Western, male) editors who were extremely unhappy about the prospect of letting individual readers choose to not load whatever violent, disgusting, or offensive pictures said editors chose to put on a page. (To be fair, it would be a complicated project, but the arguments from ideological purity were far more impassioned.) WhatamIdoing (talk) 02:35, 16 December 2014 (UTC)
Is the racial slur really necessary? Anomie⚔ 13:16, 16 December 2014 (UTC)
Being (accurately) called "white" is not a racial slur.
I suspect that what you meant to ask was, "Is it necessary to point out that there was a dramatic difference in the opinions of male editors from six or eight countries whose population is predominantly white and Western, and editors from Asia, Africa, and South America?" Well, I think it's interesting. There was a significant cultural split in that discussion about whether the reader or the editor controls what the reader views. It lined up better along racial lines (white) than along geographic lines (Northwestern Europe, Australia, USA). Editors who were in the "white, Western, male" group were (taken as a whole) far more committed to making readers display potentially offensive images on the readers' computers than non-white and/or non-Western editors. Is there an actual racial (vs a non-racial cultural) component? I don't know. It's possible that non-white people are more aware of the many forms of exploitation, since they've been subjected to more of it as a result of their races. WhatamIdoing (talk) 21:50, 17 December 2014 (UTC)
Im not here to question the policys of wikipedia. I have the uttermost respect for the guidelines worked out. Since im a editor at the swedish wikipedia at normal times im used tho the guidelines we use, hence my question. I do respect the wiki is not censored-statement, but i DO question the pictures relevanse and necesarity. Even though, I dont think im the right one to make the call. --Knight of Ni (talk) 23:35, 14 December 2014 (UTC)
If you're questioning the appropriateness of a specific image in a specific article, the article's talk page is te place to go; here we discuss general policy issues, not content details for specific articles. עוד מישהו Od Mishehu 06:39, 15 December 2014 (UTC)

Editing by a retired wikipedian

Hi. If some user had marked its page and talk page with the template {{retired}}, could be considered bad faith to edit (and revert editions) and can not write in his/her talk page? I ask it because some user is doing it. (Sorry for my bad English). Best, --Warko talk 04:17, 17 December 2014 (UTC)

I know, my point is that this user is "blocking" the posts in his talk page by putting the template. This not seems correct to me. --Warko talk 04:24, 17 December 2014 (UTC)
The user is Diego Grez. I've not edited his talk page before asking here first. --Warko talk 04:36, 17 December 2014 (UTC)
Sure, I was talking about a "symbolic" block, not a technical one. Thank you. --Warko talk 04:39, 17 December 2014 (UTC)
Off-topic. But if you want to talk about policies, I ask you why you are ignoring the policy of explain reverts? --Warko talk 04:56, 17 December 2014 (UTC)
"If your reasons for reverting are too complex to explain in an edit summary, leave a note on the article's Talk page.". I did that. My question was "off-topic" because it doesn't suit you? [[User:that the unchosen envelope contains twice the sum in the chosen one must always be 1/2, regardless of what sum might be in the chosen envelope. It can be shown mathematically that, if this is the case, the expected sum in both envelopes must be infinite |Diego Grez]] (talk) 05:01, 17 December 2014 (UTC)
No, it is off-topic because this section is called "Editing by a retired wikipedian", not "Neighborhoods of Pichilemu". --Warko talk 05:08, 17 December 2014 (UTC)
  • Comment What about the concerns of using the template for being retired when you're not really retired? The template documentation makes it astoundingly clear that it is used to permanently stop editing, not one time, not 'sometimes here, sometimes not' but permanently. However, we see that this user is using the template and have edited with it on, against the template documentation. Should the retired template be removed? Accordingly to the documentation, it should be. But what if they edit war? Bleh, I don't understand how stuff can be in the template but not enforced. Tutelary (talk) 04:44, 17 December 2014 (UTC)
  • If by symbolic you mean that they will never see any posts on their talk page because they don't look at it anymore, then, yes, you're probably right. However, no-one can make them volunteer on wikipedia to read anyone's message. — {{U|Technical 13}} (e • t • c) 04:47, 17 December 2014 (UTC)
  • I've seen a few editors (over the years) continue to contribute to Wikipedia, while keeping a retirement template on their userpager/user-talkpage. Never did understand the practice. GoodDay (talk) 04:50, 17 December 2014 (UTC)
I could understand if a retired user make a few editions. But Diego Grez has reverted my edits in more than 60 articles. It doesn't seem to me like a real retirement. --Warko talk 05:08, 17 December 2014 (UTC)
I agree that it does seem odd that an editor marks his page as 'retired' and then continues to edit but there is no rule or policy preventing that. I suggest that you follow the standard WP:Dispute resolution procedure if you cannot agree. Martin Hogbin (talk) 10:19, 17 December 2014 (UTC)
Yeah, I will follow that procedure. But first I have to know if the user is "retired" or not. If is retired, I can't have a dispute with a wikipedian is not active. --Warko talk 13:59, 17 December 2014 (UTC)
Are you referring to the Diego Grez who responded just above? If so, I guess you should take him as being active. Just ignore the 'Retired' template. Martin Hogbin (talk) 14:07, 17 December 2014 (UTC)

What if the {{retired}} template included some indication of how active the user actually is? Perhaps number of days since the last edit, or number of edits in the last month. “WarKosign” 14:13, 17 December 2014 (UTC)

Actually, the semi-retired template would be best for Diego Grez. GoodDay (talk) 14:17, 17 December 2014 (UTC)
While I guess there wouldn't be any harm in such an addition to the template, assuming it's possible, it's easy enough already to check a user's contribution history. DonIago (talk) 14:19, 17 December 2014 (UTC)

The thing works this way: if a user edits, he is not retired. If he does not edit, he is retired. The template does not set it: a user may use the template and still edit, or he can be retired and never informed so with a template. So, if there is an ongoing dispute, ignore the template and solve the dispute the regular way.

Having said that, you may check the circumstances in which he "retired". If, for example, someone challenged some action of this user and he made a great scandal about his retirement as a result, only to return less than a month later, take note of that detail. Also if he tries to shield himself from discussion with the "retired" template on an active way (such as replying "I will not reply, I'm retired"). It is not an actionable fault in itself (meaning, nobody will be blocked for doing that), but it is a deception. And, although we assume good faith, our social policies are not a suicide pact, we have no requirement to keep trusting the word of a proved trickster. On the other hand, if he simply added the template silently one day, and then returned to edit as a regular editor, then ignore it. He may have really thought about leaving, changed his mind, but forgot about the template. Cambalachero (talk) 14:39, 17 December 2014 (UTC)

Considering this being the rationale posted along with the retired template, I think Warko's concerns are valid in this particular case. - NQ (talk) 15:20, 17 December 2014 (UTC)
Warko, this is so simple. If an editor edits they are active, if they are not editing they are inactive. No template that they put on their user or talk page governs whether they are active or not. You are right above that you can not have a dispute with an inactive editor, but since you have a dispute there is only one possibility, the editor is active. -- GB fan 23:43, 17 December 2014 (UTC)
I wrote in his talk page, but he reverted my edition. I assume that he is retiring for real this time. --Warko talk 23:49, 17 December 2014 (UTC)
In short, a user reverting a message left by someone else on their talk page does not break any Wikipedia policy. However, you probably shouldn't leave notices like that in another's userspace. It tends to lead to more problems than solutions. Killiondude (talk) 00:02, 18 December 2014 (UTC)
I've never wrote in another's userspace. --Warko talk 00:22, 18 December 2014 (UTC)
You wrote that on his talk page and that is in the userspace. That message was inappropriate. All him removing the message means is that he read it, it does not mean that he is retiring. If you have a dispute discuss it. -- GB fan 00:32, 18 December 2014 (UTC)
If somebody redirects his userpage to his talk page, you can't post on it? I didn't know this rule. --Warko talk 01:11, 18 December 2014 (UTC)
That's not so. Its just means he virtually has no userpage. GoodDay (talk) 01:14, 18 December 2014 (UTC)
What makes you think you can not post to a talk page that is redirected from the userpage? -- GB fan 01:18, 18 December 2014 (UTC)
Ok. --Warko talk 02:18, 18 December 2014 (UTC)

Freebase, Google, Wikidata, Knowledge Graph, and English Wikipedia

Google announced in December 2014 that their Freebase project would close in six months, and that they intend to migrate as much of its content to Wikidata as the Wikimedia community likes. I am writing to invite anyone to comment on this at d:Wikidata:WikiProject Freebase. Freebase could be described as Google's Wikidata.

This matters to English Wikipedia because Freebase was used to power Knowledge Graph, and the advent of Knowledge Graph greatly influenced traffic to Wikipedia. Google search remains the major driver of traffic to English Wikipedia, and therefore Google's interactions with Wikipedia significantly influence how people use Wikipedia.

Whatever happens will be decided on Wikidata. I cannot say what impact the Freebase migration will have on English Wikipedia, any other Wikipedia, or how external websites interact with any Wikimedia project, but my intuition is that the acquisition of such a large collection of datasets into Wikidata could radically change the world's interest in developing automated tools to interact with Wikidata and to increase the exchange rate of information between English Wikipedia and Wikidata.

I regret to say that there is not much to read about this, but what is available is at Wikidata. Blue Rasberry (talk) 19:04, 18 December 2014 (UTC)

Talk page size

NO CONSENSUS
There is no consensus here to elevate the proposed guideline to policy and no consensus with regards to establishing a fixed limit of the size of a talk page. This discussion, when taken together with the accompanying AN/I thread, shows broad consensus that 1000k or larger is 'too large' and in such circumstances users should be asked to archive their talk page. This is basically the limit of the inferences that can be properly drawn from these two discussions. Bellerophon talk to me 11:14, 16 January 2015 (UTC)

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

In response to the HW incident at Wikipedia:Administrators'_noticeboard/Archive267#User_talk:Hullaballoo_Wolfowitz_archival I here by propose that the limit (75kb) set at WP:ARCHIVENOTDELETE is to be made a policy (i.e no talk pages longer than size x) for User talk pages. Avono (talk) 17:40, 12 December 2014 (UTC)

An alternative proposal would be that refusing to archive/reduce a user talk page after being asked by a number of editors (consensus) should be considered being disruptive. Avono (talk) 20:36, 12 December 2014 (UTC)


I'm not entirely sure that would be necessary, although it would certainly be possible to amend the existing guideline to include something to the effect that talk pages which exceed that length can and perhaps should be archived or set up for archiving by individuals other than the user whose talk page it is in the interests of accessibility, and that disruptive edits to the contrary would qualify as disruptive editing as per WP:DE. There will be some blocked or banned users whose talk pages could conceivably get that long as well, and having some way to clearly deal with such occurrences is clearly in the interests of the project. User talk:HiLo48 here and User talk:Carriearchdale here might be further examples. John Carter (talk) 17:58, 12 December 2014 (UTC)
I am open to any suggestions; I Just think this needs to be addressed by the wider community first because it will affect a lot of Editors, thats why I started here. Avono (talk) 18:08, 12 December 2014 (UTC)
The guideline WP:ARCHIVENOTDELETE appears above the user talk page guidelines and so has to do with article talk pages, which indeed should always be archived rather than deleted, and which are frequently archived by a bot. Users do have the right to delete rather than archive their talk pages, although archival is preferred. I agree that there should be some limit on user talk pages. I hadn't previously noticed, until this issue, that 75K was mentioned, so now I need to archive half of my talk page. Robert McClenon (talk) 18:26, 12 December 2014 (UTC)
Well prefered talk page sizes can be further discussed (had to start somewhere). Admins over at WP:AN also had an idea for a consensus based policy based on individual situations. Avono (talk) 18:31, 12 December 2014 (UTC)
Referring to a consensus based policy based on individual situations sounds contradictory. Should the policy be consensus-based, or should it reflect individual situations, or a combination of the above? I agree that some policy should be in force that admins can archive the talk page of an editor whose talk page is problematically large (and that interfering with that policy is considered disruptive). Robert McClenon (talk) 18:39, 12 December 2014 (UTC)

If a page is too long it hangs the browser on older systems. The purpose of a talk page is to allow communication, if the page length prevents that then it is not appropriate. I don't know where to set the limit but it is entirely within the communities expectations that a talk page be usable. Chillum 18:33, 12 December 2014 (UTC)

Is the figure of 75K based on technical knowledge of the behavior of older browsers, or is that just a generic guideline? Robert McClenon (talk) 18:39, 12 December 2014 (UTC)
HW's talk page was around 1000K causing technical problems, maybe set that as the limit? (thought imo it should be around half of it) Avono (talk) 18:45, 12 December 2014 (UTC)
One thousand KB would be a problem at any time, but I have no reason to think that there should be any reason to allow the problem to grow to the point that it causes technical problems. There are perhaps some questions regarding possibly poor transmission speeds in some English speaking areas which might make the page ultimately unavailable at far shorter lengths. 75K to me sounds like a not unreasonable number, although I could I guess allow for some temporary instances of exceeding it without independent archiving if, for instance, some one wins an arb seat and every single person who voted for that candidate drops a note to say "hello, remember that I voted for you the next time someone wants to ban me," or the death or known serious health problems of a popular editor, or someone doing something controversial or attention-getting in the media, or something along those lines, I guess a little leeway might make sense. If a page grows to 100K or more in less than a day, over the proposed 75K, I don't think that would necessarily be considered cause for independent archiving, but that won't happen very often if honestly it ever happens at all. John Carter (talk) 18:55, 12 December 2014 (UTC)
(resp to proposer) Recommend not imposing a talkpage length requirement. Every editor has a different situation at his/her talkpage. GoodDay (talk) 19:01, 12 December 2014 (UTC)
But this isn't so much about the talk page owner as it is about visitors who have said that they have encountered difficulties. If people have a hard time communicating with someone whose talk page is a mile long, then that is a problem that goes beyond the "it's my page and I do what I want" ethos. This brings to mind the occasional flare-up over excessively large or otherwise obnoxious signature lines. Users are given wide latitude in how they can display signatures, and while there's no firm policy, we have a general expectation of conformity to community norms, i.e. no blinking, no multi-line, link your username, etc... When editors violate that, and enough people see it as disruptive, then the community is empowered to compel that editor to comply with the norms of the project. There's many other examples as well, such as when people used to have fake "new message" orange bars on their talk page. Tarc (talk) 19:09, 12 December 2014 (UTC)
I don't believe we should impose any hard limit as a result of people intending to game the system and freedom of the talk page. I believe the threshold should be defined in policy as 'should not become so large that they cause load problems or excessive scrolling to get to the bottom.' Plus I fear that this could become another tool to harass another user who you have beef with. "In a heavy dispute, just archive their entire talk because it's over this hard limit!" Tutelary (talk) 19:13, 12 December 2014 (UTC)
Something could be in place, that points out an editor should comply to requests to archive. GoodDay (talk) 19:17, 12 December 2014 (UTC)

I agree that common sense is better than a hard limit. I would support wording along the lines of If people are telling you that the length of your talk page is making it difficult to communicate with you then you should shorten the page by archiving or removing content. Insistence on keeping a talk page long while others are telling you it is preventing communication can seen as disruptive.

It is to the point and essentially spells out what the community already expects from a talk page. Any action that needs to be taken can be handled under our current disruption policy. Chillum 19:28, 12 December 2014 (UTC)

I agree. Creating specific, detailed rules about each individual type of disruption promotes the idea (whether it's system-gaming or an honest misconception) that anything not explicitly mentioned is permissible (because "there's no rule against it"). If a behavior is disruptive, we needn't check whether it contradicts Wikipedia Title 32, Part III, Subpart A, Chapter 19, Section 337 before intervening. —David Levy 20:25, 12 December 2014 (UTC)

Oppose any policy change per WP:NOTBURO; it's not that hard, when a bunch of editors tell you your talk page is too long, it's too long. NE Ent 22:57, 12 December 2014 (UTC)

  • My thoughts on this are as follows. This was a really poorly thought out and put together proposal that should have been made as a collaboration of editors. It should not have occurred until the situation at WP:AN is resolved in which-ever way it will end up being resolved. I think that setting a number like 75K is excessively low, especially since it is not difficult for a single productive collaborative discussion to take more than that. As I've discussed in other semi-recent discussions for the size of talk archive pages, the most primitive browsers and systems seem to start having troubles around the 120-150K mark. I've championed in those discussions that talk archives should be limited to 150K. I would say that for the actual talk page, the limit should be the the greater of 120K or 31 days of discussions. I would also say that repeated requests for archival either via a new discussion on the user's talk page or by prefixing the {{Archiveme}} template to the top of the page from multiple editors should be an exception to the 'hard set' technical requirements. Allegations that said multiple editors are "ganging up on" or "working together against" need to be validate by some kind of editor interaction log and some kind of evidence they are working together (I'd not be opposed to editors being able to request assistance from someone with access to email logs, but do expect that many others will). While I see a lot of concerns that such a modification of policy will lead to editors attempting to game the system, that is less of an issue to me as it doesn't matter how page sizes be kept down (surely they would grow tired of any attempts to game the system quickly if they see that nobody cares) allowing other editors to easily communicate with them. — {{U|Technical 13}} (e • t • c) 23:30, 12 December 2014 (UTC)
  • As someone who manually archives his Talk pages, I have a couple of thoughts. First, is there any page that details advice about Talk pages? I've let mine frequently get almost to 100K, mostly because I archive when I feel it's time. (I get very little traffic, only 13 archives over the last 12 years.) My longest -- at 120K -- was due to the fact I was basically gone from Wikipedia, received a lot of bot-generated messages, & just didn't care. (If someone is gone from Wikipedia, the last thing that person cares about is whether Talk page size violates policy.) Second, notification bots should be smart enough to detect a {{retired}} tag & not leave messages on Talk pages where the person is gone from Wikipedia, otherwise that'll become a problem. -- llywrch (talk) 18:45, 15 December 2014 (UTC)
  • 75K sounds a but low. The usual recommendation is 100K. Mine often exceeds that (a bit), because I don't pay attention and people are unfortunately slow to complain. On the other side, it's not unusual in a major discussion for discussion page size to get completely out of control, and there's not always a good solution. If you archive discussions, people complain that they can't talk. If you split large discussions to new pages, people complain that you're "hiding" the discussion (or part of it). WP:VPPR may have set a new record last week, when it reached a rather staggering 663K. WhatamIdoing (talk) 02:31, 16 December 2014 (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.

Do we publish information sourced from groups accused of things like war crimes and who are designated as terrorist?

I am asking in reference to File:Anthem of Islamic State.ogg which was recently uploaded by @Syed Aamer Shah (Scientist):. As an additional note this was done without use of the consensus agreed name for the group "Islamic State of Iraq and the Levant" or "ISIL" with the result that names will need to be changed. GregKaye ✍♪ 17:09, 20 December 2014 (UTC)

  • The question may be mute as I have just found the source as "Best Arabic Nasheed ever 2013" from a YouTube channel titled "Islamic Taliban Media" and not, as claimed, from "Islamic State". Never-the-less, an answere to the question would still be appreciated. @Syed Aamer Shah (Scientist): can you explain your upload and chosen use of file references? GregKaye ✍♪ 17:20, 20 December 2014 (UTC)
Statements by groups classified as terror organizations such as Hamas or Hezbollah (either directly or via media outlets and other organizations that do not hide their connection) are routinely used in Wikipedia. The stated rational is WP:NPOV - give both sides equal representation. Using Reductio ad Hitlerum, I wonder why the articles on Nazism and related subjects don't give the Nazi POV "due" representation. “WarKosign” 18:37, 20 December 2014 (UTC)
Yes, attributed statements as to the opinions of ISIL can be cited to documents, interviews, websites, etc. where an ISIL spokesman states those opinions... These are called PRIMARY sources, and within a limited scope can be quite reliable. Blueboar (talk) 21:17, 20 December 2014 (UTC)
A reasonable summary of any orginization's opinions, which can be verified by undoubtedly authentic statements made by the spokesperson of the orginization, may be included in the article of te orginization and/or its activities. Nazism, by the way, should be no exception. These statements must not be overly long (WP:UNDUE), mand must be worded in a way that isn't designed to convince the reader of its correctness. עוד מישהו Od Mishehu 07:25, 21 December 2014 (UTC)

Proposal to elevate Wikipedia:Userfication to guideline status.

Though there is close to a consensus for support, I think the creation of a new guideline needs clearer support than this. Recommend further RfCs at WP:Userfication to address and clarify some of the issues raised here since it's not far off. In particular, some discussions clarifying the differences between userspace and draftspace drafts would appear to be useful. Sam Walton (talk) 23:36, 13 January 2015 (UTC)

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

Over eight years ago, I started a little essay on userfication - the process of moving material to user space for any number of reasons. Since then, the content of the page has been expanded and refined by dozens of editors pursuant to numerous discussions, and has been linked from hundreds of pages where userfication has been proposed, debated, or implemented. I think it's time to acknowledge that this page reflects the broad community consensus on how to treat this practice, and call it a guideline. Cheers! bd2412 T 16:21, 8 December 2014 (UTC)

  • Support I kinda thought it already was. Userfication, while not a guaranteed right, is a fairly commonplace occurrence, to the point where we have an entire page (WP:REFUND) designed to make it easier for people to get stuff userfied. Insofar as REFUND exists and is a working process, Wikipedia:Userfication is the instructions and guidelines for how it works, it makes sense for upgrading the status to a guideline, since that is exactly what it does: guide people in how to use a functioning and accepted Wikipedia process. --Jayron32 17:12, 8 December 2014 (UTC)
  • Oppose For now, at least. It doesn't define well enough how this compares to moving articles to draftspace. Articles with substantial improvement potential, or in which several editors have an interest, should be given greater visibility and more opportunity for collaboration, so moved to draftspace rather than userspace. I would support guideline status if this issue is addressed satisfactorily. Cenarium (talk) 23:57, 8 December 2014 (UTC)
  • Oppose Like Cenarium, I also hesitate to make this a guideline because I feel this practice has an uncertain future. In most cases, I would prefer articles in development to be in draft space because so many drafts in userspace get forgotten forever. If people put them in draft space, others could be prompted to build upon them in ways that would never happen to userfied drafts.
The userfication space is for articles rejected from mainspace, articles which a user does not want anyone else touching, or articles so controversial than keeping them in draftspace draws unwanted attention. I am not sure that I want userfication to be seen as a preferred practice in general cases.
I userfy things a lot - thanks BD2412 for developing and naming the concept - but I think it is not yet clear when this is the best practice. I am sure that there are certain cases when it is best, but not sure what those are. Blue Rasberry (talk) 00:36, 9 December 2014 (UTC)
If it is not clear after eight years and hundreds of uses, then it's not likely that anything will ever be clear on Wikipedia. bd2412 T 00:42, 9 December 2014 (UTC)
I disagree. This could wait some years more. The new development is the draft namespace which, from one perspective, supplants most of the applications of userfication. The draft namespace has not even existed for a year, so in my opinion, 8 years of testing has not happened. Only less than a year has. I am not ready to quickly adopt a community managed process as a guideline when it conflicts with the design inherent in Wikipedia's software structure. Tools exist to process drafts; no Mediawiki software development is done or is scheduled to be done to manage userfied content. Blue Rasberry (talk) 17:00, 18 December 2014 (UTC)
  • Support Nearly a standard process, so i am surprised that it isn't a guideline. Confusion with draft space seems unlikely to me. The Banner talk 01:38, 9 December 2014 (UTC)
  • Support - There may be a need to clarify when to userfy and when to send to draftspace... but I don't think that should stop us from promoting the essay to guideline status. Clarification can always be added. As the nom states... It's time to promote. Blueboar (talk) 01:54, 9 December 2014 (UTC)
  • Support as not only is Draftspace broken and will take a lot of work to repair and hopefully get things back on track (see my little TL;DR rant below), but one of the stipulations for creating Draft: in the first place was a community consensus that it would not replace Userfication or User: drafts. — {{U|Technical 13}} (e • t • c) 03:06, 9 December 2014 (UTC)
  • Support - This describes a common and accepted practice. That's basically the definition of a guideline. Mr.Z-man 03:10, 9 December 2014 (UTC)
  • Support I've personally seen dozens of AfDs end in an article being userfied, so its a pretty accepted practice. The AfD Statistics Tool, which is used to check the AfD history for admin candidates at RFA, even includes "userfy" as a valid vote type. I ultimately agree that the essay has wide community consensus and usage, so it should be promoted to a guideline. Spirit of Eagle (talk) 03:36, 9 December 2014 (UTC)
  • Support - It's a long-term, very common practise that I think should be followed more often. Whilst there may still be room for improvement in the exact wording, I don't see how that should stop this becoming a guideline. Lukeno94 (tell Luke off here) 08:27, 10 December 2014 (UTC)
  • Support The oppose !votes appear to miss what a guideline on enwiki is. This page is the fruit of years of broad community consensus-based discussion. That is the very essence of a guideline. James (T • C) • 8:31 PM • 09:31, 10 December 2014 (UTC)
  • Support - Gives official recognition to documentation of a common community practice. Carrite (talk) 14:17, 10 December 2014 (UTC)
  • Oppose per Cenarium. A good essay but one that I think needs updating. I don't support this as a guideline because it's unclear to me as a user reading it: (1) the text itself ("Like userification, draft space allows editors the opportunity to work on sub-par articles outside of the main article namespace. Draft space, however, may increase the chance of collaboration by placing draft articles in a central location. Another advantage is that incubated articles are automatically "noindexed", meaning they won't show up in search engines.")(2) how this guideline relates to the draft user space and (3) who actually does the "userfication" -- users moving my content? users patrolling article space? me moving my own content? I find this guideline difficult to read and understand and I suspect that this will be much more the case for new users. I also strongly advocate renaming this to "Moving content to user space" for clarity reasons for users who are new to the project, so that they do not have to process yet another wiki-jargon. --Tom (LT) (talk) 23:22, 10 December 2014 (UTC)
    • I think that there is some confusion here about the relationship between User space and Draft space. If, for example, a new editor writes a biography about himself or herself in article space, and it is determined that this editor is not notable, but merely intended to provide the details normally found on an editor's own user page, then it would not make sense to turn that article into a draft. Where material is best left to userspace, userfication is the appropriate process despite the existence of draft space. Note also that editors are as entitled to create drafts in their userspace as they are in draftspace. An editor who is the only substantive editor of an article that is determined to not yet meet encyclopedic standards can ask to have an article moved to their user space in lieu of deletion, so long as it does not violate other policies described at WP:USERFICATION. bd2412 T 20:34, 12 December 2014 (UTC)
      • I believe we're well aware of this distinction, the point is that the essay doesn't explain the distinction well enough. Maybe this could be given some more details in a specific section ? I would also second a rename to avoid wikijargon. Cenarium (talk) 20:54, 12 December 2014 (UTC)
        • The essay existed for several years before draft space existed, so there was no distinction to be made. The mere existence of draft space does not really change anything about the userfication process; it merely adds another option, and we need not set rules about what kinds of things need to go to what kinds of spaces. By the way, I am not strongly opposed to renaming, but I think that's a subject for another discussion. bd2412 T 21:08, 12 December 2014 (UTC)
  • Support - shows common practice. Red Slash 17:16, 13 December 2014 (UTC)
  • Oppose I think its good practise, but prefer that such practise remain voluntary rather than compulsory.--KTo288 (talk) 08:04, 14 December 2014 (UTC)
  • Oppose It's a common procedure, but I think a confusing one. It would be much better to use draft space for all article-in-process material, for then we could devise a single system for monitoring it. DGG ( talk ) 08:16, 14 December 2014 (UTC)
    • @DGG:, if a new, clearly non-notable editor writes a biography about himself or herself in article space, do you think that should go to draft space? Should we not be permitted to move it to user space? If an editor requests that an article they have written (and no one else has touched) be moved to their user space, should we allow that? This proposal has very little to do with draft space, and I find it confusing that people keep bringing up draft space, when many userfication cases are clearly inapplicable to it. bd2412 T 19:07, 20 December 2014 (UTC)
when new clearly non-notable editors contribute bios about themselves in article space, it should not go anywhere, but be deleted. If there are no indications of significance, as is usually the case, A7; otherwise prod or AfD. You're referring to the possibility of it being intended for a user page, which is possible. I suppose they could be asked if they want it there, if it is otherwise suitable. I don't think this is what we generally mean by userification. I've not seen many that would actually be suitable. DGG ( talk ) 19:19, 20 December 2014 (UTC)
Here is another example of use of userfication in accordance with the existing guidance - two months ago, an essay by User:Born2cycle was userfied to User:Born2cycle/Unnecessary disambiguation. It seems unlikely in the extreme that this should have been moved to draft space, and WP:Userfication was specifically invoked in the discussion as a solution to the dispute. bd2412 T 22:06, 22 December 2014 (UTC)
making a user subpage out of it will only result in more pseudo articles escaping detection and remaining indefinitely. At least in draft space we can see them and in a few months get rid of them. DGG ( talk ) 19:19, 20 December 2014 (UTC)
  • Oppose Not yet. As others have noted, the new draft namespace has not been given sufficient coverage. Using the draft namespace should be a clearly enshrined practice, not presented as an afterthought or just "an alternative" to userification. Manul 17:11, 19 December 2014 (UTC)
Why does it need to be an either/or... why can't we promote WP:Userfication to guideline status and use Draftspace? I think they serve slightly different, yet complimentary purposes. Blueboar (talk) 18:31, 19 December 2014 (UTC)
because in practice they remain there forever as pseudo-articles, unless the original deletor from article space or whatever keeps track and brings them to MfD, where they are almost invariably deleted. At least draft space has a mechanism for dealing with them. A clumsy and inefficient method, but they do get dealt with. DGG ( talk ) 19:19, 20 December 2014 (UTC)
  • Comment I would say based on previous experience and the direction of this discussion that "Draftification" is de facto included in "Userfication" and the later is just the more familiar and longer standing term and since there is no wording suggesting, nevermind prohibiting, an article from being userfied to draft space and I'm still unclear as why people who are opposing this simply because Draft: space now exists think that is a problem. — {{U|Technical 13}} (e • t • c) 19:38, 20 December 2014 (UTC)
  • Support It seems to be an established practice in my experience, and I've certainly used it and found it helpful many times.--Slon02 (talk) 22:31, 24 December 2014 (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.

Donations

I have recently decided that Wikipedia, to help maintain it's independence, should be supported with an occasional donation. But I am starting to doubt the sense of my decision, as every article I open in Wikipedia of late is overlain with appeals for more donations, I have made myself visible and my feelgood is being eroded by this policy. — Preceding unsigned comment added by 49.182.15.1 (talk) 21:32, 25 December 2014 (UTC)

Thanks for donating. There is a fundraising campaign this month. meta:Fundraising#December 15, 2014 Campaign Update (written December 15) says: "Banners have been showing to all readers these past two weeks. At this point, we are starting to limit the number of banners each reader sees. We will run the campaign at a higher traffic level again at the end of December for a final year-end push." I guess you are seeing this final push. I don't think the number or type of donation banners has any relation to whether you have donated. Registered users have the option "Suppress display of the fundraiser banner" at Special:Preferences#mw-prefsection-gadgets. It's free to register. PrimeHunter (talk) 22:04, 25 December 2014 (UTC)

dates and places

Is there a policy on which comes first: DATE OF BIRTH or PLACE OF BIRTH?Kdammers (talk) 10:18, 31 December 2014 (UTC)

No, there is certainly not a policy on that. It's possible that there might be a guideline or suggestion somewhere. However, the ultimate answer is going to be "it depends". If you follow the format of "Old King Cole (1664–1708) was a merry old soul", then you'll be listing the dates first. If you don't (or if you don't list the dates at all), then you'll probably be listing the birth place first. The former is very common for articles about long-dead people; the latter is more common for articles about living people. WhatamIdoing (talk) 05:10, 1 January 2015 (UTC)

Blocking Policy Purpose and Goals - 3RR and 1RR blocks

I suggest that Wikipedia:Blocking_policy#Purpose_and_goals is amended to reflect common practice that blocks are commonly given out for accidental tripping of the 3RR and 1RR bright-line rules by experienced editors. Such blocks can be misconstrued as punitive and not preventative when given to experienced and otherwise good natured editors, so this policy should reflect and explain this actual practice. Please see a draft in two sections below:

1) Explanation of common practice

Blocks may act as bright line rule deterrents

In certain cases blocks are given out for violations of WP:3RR or WP:1RR bright-line rules, even to experienced editors where such blocks may not be seen as directly preventative. Such blocks are not intended to be punitive, but rather to act as deterrents in order to underline the importance of these bright-lines.

2) Explanation that such blocks can be given on an ex parte basis:

Such bright-line blocks may be applied on the basis of a summary judgment and there is no requirement for the admin to await an explanation from the offending editor before implementing a block.

Both part (1) and part (2) are intended to reflect common practice, particularly at WP:ANI and WP:AE, and I suspect part (2) requires more discussion than part (1).Oncenawhile (talk) 09:11, 21 December 2014 (UTC)

Bright-line rule is "is a clearly defined rule or standard ... which leaves little or no room for varying interpretation". It is not the case with a revert. I tried to have what is and what isn't a revert (re)defined, without success. Currently the same actions of an editor may be considered a violation of 1/3 RR by one admin and not a violation by another. It leaves a lot of room for WP:LAWYERING and WP:GAMING.“WarKosign” 09:23, 21 December 2014 (UTC)
The problem - In the opening post the problem seems to be that even experienced editors might see 1/3RR blocks as punitive rather than preventative.
In my opinion the proposed addition does not directly address that problem, but does welcome interpretations that go beyond that limited issue. So an alternative (which would be redundant with existing text probably) might be

Sometimes those who are blocked react negatively, but all editors - new and experienced alike - are expected to assume that the admin who imposed the block acted with a good faith belief that the block was needed to prevent further edit warring and to encourage consensus-seeking discussion.

This alternative text directly addresses the statement of the problem by the OP, while striving to avoid unintended consequences. But doesn't the policy already say that?
NewsAndEventsGuy (talk) 09:40, 21 December 2014 (UTC)
AGF is not required when bad faith is evident. Nor should we ignore cases where an admin acts in good faith, but improperly or unjustly. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:29, 21 December 2014 (UTC)
Hi User:NewsAndEventsGuy, can you clarify which part of the proposed text you would suggest replacing with your draft? Subject to Andy's comments, I am fine with your addition. Oncenawhile (talk) 13:19, 21 December 2014 (UTC)

In my opinion, blocks should not be the main way that WP works. Treating people who, in a moment of excitement or by mistake, breach a rule as criminals breeds ill feeling and resentment and may drive away good editors.

If we are to give blocks for 3RR infringements, for moments of over zealousness, then we should automate the process so that it always happens. This is the only way, in my opinion, that the argument that blocks are protective could be sustained. I am not proposing this, just saying it is the only way that I would accept it.

I believe that, except for editors who regularly and conistently edit war, blocks should always be preceeded by a warning, explaining what the problem is and how the dispute might be better resolved by all parties. The real problem is that we have no adequate dispute resolution system. Martin Hogbin (talk) 09:45, 21 December 2014 (UTC)

Firstly 3RR (and even 1RR where applied) is not a bright-line rule; there is no such limit on reverting blatant vandalism, for instance. This would make it hard to detect automatically. Secondly, the problem of blocks being applied punitively, or otherwise excessively, would be best addressed by restraining (or re-training) admins who breach policy, and betray the community, in such a manner. We should also look to a tool for expunging block logs; or at least adding annotation, when bad blocks are made. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 11:29, 21 December 2014 (UTC)
"a tool for expunging block logs..." Great another thing to litigate! Paraphrasing Capt Picard in "Insurrection", does anyone remember when we were article editors?NewsAndEventsGuy (talk) 12:30, 21 December 2014 (UTC)
Andy, you ar quite right. I was not advocating automatic blocks just saying they are the only kind that I would support. The real problemis that ther is no adequate dispute resolution system. Martin Hogbin (talk) 13:04, 21 December 2014 (UTC)
Indeed. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 13:06, 21 December 2014 (UTC)
Hi Andy, I agree with you also, except where you write "3RR is not a bright-line rule". WP:EW states that "there is a bright-line rule called the three-revert rule (3RR)" - i.e. 3RR is by definition a bright-line rule. Oncenawhile (talk) 13:14, 21 December 2014 (UTC)
Indeed it does; it then goes on to list a number of exceptions, which prove that it is not a bright line rule. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:04, 21 December 2014 (UTC)
  • Wikipedia should strongly discourage the robotic application of blocks for things like 3rr and 1rr. Counting reverts is just stupid. What's necessary is to look at which editor (if any) is trying to communicate and explain what they are doing, and trying to seek compromise, and which editor is just revert warring, or stonewalling, or being silly. Policy should say that such blocks are allowed if they serve the goal of helping editors to write articles; but when blocks don't serve that purpose, they aren't done. Jehochman Talk 13:23, 21 December 2014 (UTC)
  • Oppose the above changes. Ignoring for a moment my long-standing objection to the mere existence of 3RR, the notion that admins should apply blocks automatically and without even minimal investigation merely because of some "rule" should not be put into writing like this. Do any of the hundreds of admins sometimes do this? Sure. Should they? No. Proper application of 3RR should occur when an admin has judged that the block is necessary to stop an edit war. The above statement encourages admins to make improper 3RR blocks: for two examples, to block a new user who is unaware of 3RR and never been warned before, or even worse, to block a stale 3RR violation merely because someone hit 3RR. All blocks, including 3RR, must occur in the context of admins making judgement calls on whether or not the block is prudent and necessary to stop ongoing disruption, and in situations where something less sever than a block could accomplish the same, it should be used. We should never encourage a block-first and ask-questions-later ethos. Ever. --Jayron32 14:38, 21 December 2014 (UTC)
  • Oppose the above proposals; I don't have much to add to what Jayron32 (and Jehochman) said as it encapsulates my thoughts into far less text than I would have used. In terms of what has brought rise to this proposal, it is probably not coincidence that the user making this proposal was blocked for about 10 minutes nearly 1 month ago in relation to 1RR/edit-warring. It was his first block, and the capricious nature of blocks was clearly felt by him (and it is a pity that he had to go through that). However, even after having had the benefit of reading the entirity of the archived request for arbitration enforcement (AE) here, including the exchange he/she had with another AE admin there, I still maintain a view that this proposal is (and some of the comments made at the time were) misguided. The real reason that incident received the attention that it did was due to the occasionally helpful but sometimes harmful arbitration-imposed discretionary sanctions (DS) regime, and the nature of the particular topic area and editors involved. I believe this would have been handled differently - so that no block was imposed immediately - if the complaint was not made at AE, and possibly if other admins handled it (though the admins I have mentioned by name in this comment may be in a better position to opine on the latter part). Not saying it was a bad block; just it could have been handled differently. But in sum, although any block can be given on an ex-parte basis technically, that doesn't mean that is what should necessarily be happening for incidents like this, or encouraged explicitly via policy. I also don't (yet) believe the proposed amendments are an accurate reflection of common practice. Ncmvocalist (talk) 16:25, 21 December 2014 (UTC)
Hi User:Ncmvocalist, you're absolutely right. I was blocked, so I went to WP:Blocking policy and realised that the "Purpose and Goals" section failed to include anything on 3RR / 1RR, where such a block is often not directly preventative. In fact, the Purpose and Goals section as it currently stands can be seen as contradictory to common practice at ANI and AE. So I came here to try to bring the de jure and de facto one step closer together.
What I see from this conversation so far is a mild consensus that the application of 3RR / 1RR blocks has little basis in actual policy. But I don't see much enthusiasm for actually progressing policy drafting on this. It seems to be a similar dynamic to that shown in User:WarKosign's thread to define what constitutes a revert - consensus that policy is unclear, but an apparent lack of enthusiasm to progress to an improved policy. Do you think that's fair or am I misreading things? I am happy to work to help corral a consensus here if people think it is worthwhile. Oncenawhile (talk) 17:15, 21 December 2014 (UTC)
@Oncenawhile: I think you may be misreading/misunderstanding in a lot of respects. I don't understand how you came to a view that blocks are often not directly preventative with respect to 3RR and 1RR or that there is a consensus that such blocks are not based in policy. At most, I'd say users here are questioning the value of 3RR and 1RR, but are suggesting that if we must continue to keep revert revision rules for a set number (be it 3 or 1), it is better to try to attempt to discuss the matter with the user in breach than to block where possible - but it is not a strict requirement as that will not always be appropriate or may likely to be ineffective sometimes too. So they are suggesting it ultimately depends upon the circumstances of each case, but the policy as it stands is good (without the amendments proposed here). Ncmvocalist (talk) 17:34, 21 December 2014 (UTC)
Hi Ncmvocalist, I agree with your summary - to answer your first point, I have simply extrapolated one step further. To my mind:
  • "it is better to try to attempt to discuss the matter" because "blocks are often not directly preventative" (i.e. since a discussion or warning should produce the same result with experienced editors)
  • Since in this situation blocks are "not a strict requirement" they are therefore "not based in policy" (i.e. the relevant policy WP:BP is silent on this type of block)
Either way, I agree with you.
Since as you say it ultimately depends on the circumstances of the case, administrators currently have no guidance at all from WP:BP on the community's views re applying blocks in 3RR/1RR cases. How about the below as a proposed redraft:

Blocks may act as bright line rule deterrents

In certain cases blocks are given out for violations of WP:3RR or WP:1RR bright-line rules, even to experienced editors. Such blocks are not intended to be punitive, but rather to act as deterrents in order to underline the importance of these bright-lines. Sometimes those who are blocked react negatively, but all editors - new and experienced alike - are expected to assume that the admin who imposed the block acted with a good faith belief that the block was needed to prevent further edit warring and to encourage consensus-seeking discussion.

Blocks for 3RR / 1RR infringements are not a requirement and depend on the administrators' judgement of the facts of a given case. Administrators are encouraged to attempt to discuss the matter with the user in breach where possible before implementing a block, however such bright-line blocks can be applied on the basis of a summary judgment as there is no requirement to await an explanation from the offending editor before implementing a block for a clear breach.

Oncenawhile (talk) 22:47, 21 December 2014 (UTC)
Although our text claims there's a bright line, the fact is that two reasonable admins can view specific nuances differently. So what we have now is really a "sorta-brightline rule". Get over it folks, it's an imperfect world. Now notice sentence 1 in this new proposal, which begs the question "What certain other violations do not merit blocks?" If we were to adopt that without answering the question, the rule then tends towards a "MUDDY LINE RULE IN A DIM ROOM". NewsAndEventsGuy (talk) 13:11, 22 December 2014 (UTC)
  • Oppose 3RR is one of the few policies that have worked very well for the last 8 years. I don't think it is broken. Chillum 18:29, 22 December 2014 (UTC)
  • Oppose per Jayron32. NE Ent 10:13, 23 December 2014 (UTC)
  • Even if it is disputed that 3RR blocks are preventative in the sense of preventing damage (point 1 in WP:BLOCK#PREVENTATIVE), I think you'll agree that they are preventative in the sense of serving as a deterrent to the continuation of present disruptive behavior (point 2), and most importantly, they encourage a more productive, congenial editing style within community norms (point 3). So this kind of block is well within the confines of the blocking policy. Cenarium (talk) 17:18, 25 December 2014 (UTC)
  • Oppose 3RR has long been one of the most broken parts of the pedia. It is crazy that we go through four levels of warning before blocking blatant vandals, but for 3RR we block goodfaith editors without warning. There is an easy solution now available to us, use edit filters to warn people who are potentially breaching 3rrr in such a way that to save a potentially breaching revert they have to click a button that they are reverting blatant vandalism. ϢereSpielChequers 11:59, 26 December 2014 (UTC)
  • Comment - The idea that we have to go through four levels of warning before blocking blatant vandals is a myth. Going through levels of warnings is optional. Vandals are often blocked after fewer warnings than four. Robert McClenon (talk) 03:30, 2 January 2015 (UTC)
  • Oppose . Cenarium spells it out well. Ive never had any problems with the current system, but generally admins don't and they don't often make mistakes with it. It's the users who don't fully understand the policy who want it changed, although it should be blatantly obvious to anyone that edit wars are not the right way to resolve content disputes. --Kudpung กุดผึ้ง (talk) 08:40, 2 January 2015 (UTC)

Bright-Line

I will restate that User:Pigsonthewing is good-faith mistaken in saying that WP:3RR is not a bright-line rule. It is a bright-line rule, in that any editor violating it is likely to be blocked. The existence of the specific exceptions does not mean that it is not a bright-line rule. The specific exceptions are needed precisely because it is a bright-line rule with exceptions. WP:1RR is a bright-line rule if the ArbCom or the enforcing admin made it a bright-line rule. Robert McClenon (talk) 13:38, 21 December 2014 (UTC)

Suppose editor A changed a few words in an article. Then editor B made a change somewhere else in the article, then editor A reverted B's edit. One could argue that since A's first edit removed words that someone else typed, it was a partial revert, followed quickly by a second revert - hence A arguably violated 1RR. The possibility of argument whether A's first edit is or is not a revert makes revert rules non-bright-line. “WarKosign” 14:22, 21 December 2014 (UTC)
Well done; now read the whole of what I wrote, and tell me how you would automate the application of such a rule. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 14:59, 21 December 2014 (UTC)
How do you automate the application of the rule? You don't. Rules that have blocking provisions are enforced by human administrators. Even if it is very clear that an edit violated 3RR, the administrator must decide how long to block. Sometimes it isn't obvious that an edit is a revert. Sometimes it is obvious that an edit is a revert. In the latter case, 3RR really is a bright-line rule, with specified exceptions. Robert McClenon (talk) 16:34, 21 December 2014 (UTC)
It's unambiguously a bright-line rule, especially in contrast to the general provisions of WP:EW — whether or not you're edit-warring is subject to interpretation, but deciding whether or not you've violated 3RR only requires the decider to follow a checklist. A bot could block for 3RR violations, but this would be a bad idea because 3RR violations don't mandate a penalty: as humans, we need to decide whether a block (or any other sanction) be warranted. Sometimes people violate 3RR but shouldn't be sanctioned; we might decide that blocking in a specific situation would cause more problems than it would solve, and WP:IAR says that such a block shouldn't be done. It's all a matter of deciding what, if anything, is the appropriate response to someone going past the bright line. Nyttend (talk) 19:31, 21 December 2014 (UTC)
Nyttend, can you show me the bot that can reliably recognize whether a straight-up reversion was due to BLP rules or not? Because if you can't—and I've not seen one yet that can—then a bot cannot "block for 3RR violations", because the bot cannot figure out whether 3RR was actually violated. "Three edits" is not the same as "three reversions" (something that even some admins have trouble remembering). Even a dozen uses of the WP:UNDO button does not necessarily mean a violation of 3RR. There are seven listed exemptions, and if you happen to be faster than the bots at catching poop vandalism, then you can revert an unlimited number of times. WhatamIdoing (talk) 06:49, 22 December 2014 (UTC)

Nyttend I have made a bot to detect 3RR, it used checksums of pages to determine if a revert to a prior version was done. It resulted in over 50% false positives. It cannot tell what is vandalism or BLP violation etc, it cannot tell if there was a discussion and consensus on the talk page before the final revert was made. It cannot tell when two users believe they are acting in good faith and discussion is a better option than blocking.

I turned that bot off because the hits it was giving me were just wasting my time. The line may be an unambiguous bright line to a bright a person but not to a computer. Chillum 18:32, 22 December 2014 (UTC)

About five years ago there was a bot that would generate a list of possible 3RR violations. Generally it wasn't worth it for an admin to look at the results, because there were so many false positives. You would almost never want to block for a 3RR that nobody had reported. Somebody needs to report it, announce it as a violation, and then we need the usual set of warnings. You prefer that the reported person will have a chance to respond, especially if they are new. The need to close reports in a timely fashion doesn't allow for a response from the reported person in every case. Usually a block would be issued only if you see there is a problem that is bound to continue unless an admin does something. Admins like to mediate if they can; a lot of reports at AN3 involve 3RRs that didn't lead to a block. EdJohnston (talk) 03:41, 23 December 2014 (UTC)
I wouldn't ooppose an other test of a bot reporting 3RR issues, but I definitely wouldn't trust one to block over 3RR until we have a clear test with reporting. I wold also like to point out that I think that bot-blocking should only be done where the need is urgent (such as AntiAbuseBot did for a specific sockpuppeteer, before we had the edit filter); I doubt that edit warring would ever get that bad. עוד מישהו Od Mishehu 13:57, 24 December 2014 (UTC)

(RfC): Should WP:BLOCK include any reference to 3RR?

Proposal (WP:BLOCK explanation re 3RR)

Thanks all for the useful inputs above. To try to corral some actionable items, or else to close this discussion down, I propose the following simple question:

  • Question: Should WP:BLOCK include any reference to 3RR at all, specifically should it include some explanation of community policy regarding blocks relating to 3RR?

Please note that I have specifically not included any proposal regarding what such drafting might look like, as there appear to be a wide variety of views on this topic, and we can deal with specific drafting afterwards if there is a consensus to add anything. Oncenawhile (talk) 22:12, 24 December 2014 (UTC)

Support (WP:BLOCK explanation re 3RR)

  1. [supporting comments]

Oppose (WP:BLOCK explanation re 3RR)

  1. [opposing comments]

Policy question on blocking EDU top level domains

Hi. I hope this is the right place to post this. I also hope this is not an old beaten-up dead horse. :) I was recently having a conversation with my niece and the topic of Wikipedia came up. It seems that her college's IP range has been blocked by WP and nobody on campus can edit WP as an anonymous IP, including the faculty!. Some professors, especially adjunct professors, and even some staff are reluctant to officially be a part of WP in case their contributions might negatively impact their jobs. I realize that the open wifi networks on modern college campuses have a high potential for abuse but do we really want to block skilled academicians from making valuable contributions to the encyclopedia? 104.32.193.6 (talk) 18:39, 26 December 2014 (UTC)

How are they blocked? I realize that you're using an IP instead of a real account, but most serious Wikipedia editors don't. - Lisa (talk - contribs) 18:44, 26 December 2014 (UTC)
I would have to ask my niece on "how". She just said she tried to edit WP a few times and always got a "This IP is blocked" type message from WP. She was not that specific. She goes to AVC (avc.edu) so maybe there is just a single IP blocked and she was assuming? :: Perhaps what Xaosflux suggests below is the actual issue (proxy servers)? 104.32.193.6 (talk) 22:37, 30 December 2014 (UTC)
It is very unusual for us to block an entire university IP range and generally it only happens if there is no other way to stop a large amount of vandalism. The only example I recall is when some idiot professor told his class to vandalise Wikipedia on purpose as an experiment. If you tell us the IP range under consideration, we can investigate the reasons and lift the block if appropriate. On the other hand, you seem to suggest that using an IP is a way to remain anonymous. That is the opposite of the facts. In a university environment any clever student can trace an IP number to the computer using it. On the other hand, if someone logs in properly using a pseudonym (as most people here do) only a few Wikipedians with special powers can see where the login comes from. Zerotalk 20:12, 26 December 2014 (UTC)
My thoughts exactly. Blueboar (talk) 20:58, 26 December 2014 (UTC)
I disagree on remaining hidden. At my university, there are hundreds of computers accessible by any student or faculty member, and dozens accissible to any person who is in one of the many buildings where they are sitting near the doors. There is no login procedure or any other way of determining who is using a particular computer. It doesn't matter that "any clever [IT-oriented] student" might be able to track the IP. We don't have closed-circuit cameras on the computers, so just getting an IP hardly identtifies the user. Kdammers (talk) 02:43, 2 January 2015 (UTC)
Good point. I hadn't thought of that. 104.32.193.6 (talk) 22:37, 30 December 2014 (UTC)
How do you know that "some professors, especially adjunct professors, and even some staff are reluctant to officially be a part of WP in case their contributions might negatively impact their jobs"? Is this according to your niece? How does she know? Has she sat down and personally talked to a large number of personnel and asked them directly? It seems like a strange claim to me, one most likely based on personal hunch rather than anything concrete. As for the IP block, everything Zero said is valuable. Jason Quinn (talk) 20:59, 28 December 2014 (UTC)
Fair enough. I was going by her comments and didn't question her statements. I have heard that "tenure politics" can be pretty ugly from friends in the teaching profession but I have nothing I can cite WP style. 104.32.193.6 (talk) 22:37, 30 December 2014 (UTC)
A login need not be one's real name. And as the original poster possibly has been told, there are some good reasons why one would not want to use a login that coul be publicly traced or matched to the actual person. In a way, that's even *more* untraceable than editing without logging in, because it prevents revealing even your IP address. DMacks (talk) 21:14, 28 December 2014 (UTC)
  • Additional notes: our blocks are only ever to ip addresses or wikipedia usernames, we don't have the capability to block by DNS (e.g. *.edu); Some campuses may use proxy services, routing large amounts of outbound traffic through one ip address, if that address is blocked it can impact everyone using that proxy service. — xaosflux Talk 03:17, 29 December 2014 (UTC)
@User:Xaosflux: Question: When a "request" to ban an IP goes to an admin is any effort made to determine if it is an EDU domain before proceeding? Should there be? 104.32.193.6 (talk) 22:37, 30 December 2014 (UTC)
I don't think it's usual to check out the details of who might control the IP, but most requests are for a single IP address, so it will only affect (in theory) one computer. It's actually a bigger problem for Asian and African users, because "one IP address" can be the sole source of internet access for whole towns. WhatamIdoing (talk) 22:49, 30 December 2014 (UTC)

Please see my various replies above. While I think the question is valid, the example (my neice) may have been overblown because I assumed she was accurate in her various comments. Family... they can get you in sooooo much trouble! :) 104.32.193.6 (talk) 22:44, 30 December 2014 (UTC)

Before placing a range-block, I would perform a more in-depth review then a single address, even more so if it will be lengthy, additionally I'd be much less likely to also enable autoblocking of logged in users from such a block. — xaosflux Talk 23:31, 30 December 2014 (UTC)
But as far as stopping immediate disruption/vandalism of the project, just because an address is associated with a school doesn't give it any special passes for me--most schools give out free wifi to anyone these days, so the edits could be from anyone. — xaosflux Talk 23:33, 30 December 2014 (UTC)

How uninvolved does an editor need to be to collapse talk page threads/thread contents and how much time should be left since last edit before collapse?

I am particularly interested in a case of a type of article that may attract a set or regular editors on a potentially controversial topic. Where is the cut off as far as interest is concerned with regard to the use of templates such as template:collapse top and Template:Archive top. In any case where the validity of a collapse is questioned how possible is it just to remove another editor's collapses? Is this something that can immediately be done or is it necessary to ask the editor that performed a deemed unnecessary collapse to perform a revert. GregKaye 14:36, 3 January 2015 (UTC)

There is no specific, codified requirement or restriction with respect to elapsed time or involvement. Editors are expected to use good judgement with respect to other Wikipedia policies and principles. I can't help but wonder if you have a specific instance in mind, but I'm not sufficiently curious enough to try to look for it in your contribution history. TenOfAllTrades(talk) 14:44, 3 January 2015 (UTC)
The only real rules about any sort of discussion closure are: Is it likely that the user has an interest in closig the discussion in one particular way, to the point that (s)he would be unlikely to close it if the consensus clearly went in the other direction? If the case is borderline, would the user be tempted to judge the dsiscussion fairly, and not be too tempted in one direction? עוד מישהו Od Mishehu 19:04, 3 January 2015 (UTC)

TenOfAllTrades, עוד מישהו, Thank-you both. I noticed that the archive top template gives the limited advice "It should not be used by involved parties to end a discussion over the objections of other editors", and the collapse top template gives no advice or guideline. I should give some thought on what might be added to this if anything. Any thoughts? In the case of the talk page I am thinking about there is clear good intention and and clearly, good reason for closure in several cases. It's just that thread closure situation generally got me thinking. GregKaye 03:30, 4 January 2015 (UTC)

  • The archivetop tpl does not collapse a thread. It is generally used only for a specific debate or discussion (e.g. RfC) or as a signal to physically archive cases from noticeboards. It is unusual to use the green collapsetop system on talk pages unless the content to be collapsed is completely off topic or otherwise irrelevant or undesirable, or in the case of relevant additional detail such as a table or a list for example, to reduce clutter. Talk page threads get physically archived as and when necessary; this may be done by a bot or manually at the discretion of the parent project or other users. --Kudpung กุดผึ้ง (talk) 03:44, 4 January 2015 (UTC)

Policy on nationality statements

Nationality is always a contentions topic. In accordance with the fundamental principles of WP it is important that we treat this subject neutrally in all articles. At present there is no clear guidance on how to do this, and thus results in various regional and separatist group using WP as a promotional vehicle for their cause. It also results in squabbles and edit wars over who 'owns' the good and the great.

I think it would be beneficial to have a community-wide discusssion in order to provide policy guidance on this issue. The important thing is to keeep WP neutral and stop it being used to push any particular POV. What is the best way to start this process? Martin Hogbin (talk) 10:06, 5 December 2014 (UTC)

Could you give an example, even abstract, of what you mean by "various regional and separatist group using WP as a promotional vehicle" and neutral vs non-neutral treatment of nationality statements ? Neutral POV is always a concern, and there are policies for exactly that reason. “WarKosign” 11:02, 5 December 2014 (UTC)
One example of the kind of thing that I am talking about is the discusssion at Talk:James_Clerk_Maxwell#Nationality. Maxwell's nationality is listed as 'Scottish' which from an international or diplomatic perspective does not exist. All inhabitants of the UK have British nationality.
In my opinion, the problem is that the discusssion rapidly moves from the factual to arguments about personal self-identity and strong feelings of cultural, ethnic, and historical identity. Let me make it quite clear that I have no desire whatever to suppress any of that, only to prevent it from being expressed in a statement of nationality, especially in an infobox, where readers should expect something factual that takes a world view supported by official reliable sources. I would therefore propose that 'nationality' should only refer to an independent state recognised by the UN. This is a simple, non POV, easily undersood and enforced rule that gives a clear level of consistency for our readers. It does not in any way prevent cultural, ethnic, and historical identities from being expressed in articles.
Another example would be the nationality of Marie Curie. This is a more complicated case but sime simple rules, relating formal and verifiable facts would, in my opinion, help. 'Nationality' should be treated as a formal fact, decided by diplomatic status. Country of birth, self-identified geographgical home, places of residence, nationality of parents are all important facts but they are not 'nationality'. The problem is that everybody wants to 'own' the good and the great. Martin Hogbin (talk) 11:58, 5 December 2014 (UTC)
In most cases, self-identification is best. Where the nation no longer exists, I suggest we still use the term the person would have recognized as their nationality. Not just "current nation sovereign over the person's birthplace." Alexander the Great was Macedonian. Collect (talk) 12:18, 5 December 2014 (UTC)
Self-identification is a recipe for endless arguments. Where the subject is a national of an independent state, 'nationality' should be of that state. Other facts should be stated in context if supported by reliable sources. Martin Hogbin (talk) 12:44, 5 December 2014 (UTC)
I think that your exaple contains several claims that are arguable and are very far from neutral point of view. Scottish people "are a nation and ethnic group native to Scotland", which I believe makes them a nationality.Nationality "differs technically and legally from citizenship". A Scottsman living in the USA is likely to still declare his nationality as Scottish. Are you denying ethnic minorities living in exile their nationalities ? What about immigrants, does their nationality suddenly change ?
There is no single definition of nationality, so no matter how you propose to determine it, many people would disagree. It's a matter of reaching a (painful) consensus in each individual case.
In my opinion, self-identification is a good start in many cases. “WarKosign” 13:24, 5 December 2014 (UTC)
WarKosign, You have a point about ethic minorities, especially where they don't identify with the state that defines their nationality, and where their own state exists today. However, the issue that Martin has raised does not concern ethnic minorities, neither does it concern historical boundary changes, nor does it concern a subject who was uncomfortable with his official nationality. For your information as a side issue, most Scots are ethically indistinct from the English. Only the Gaelic Highlanders in the north west stand out as being in any way ethnically distinct from the rest of the population of Britain, and they are only a small minority within Scotland, albeit that aspects of their culture such as kilts, tartan, and bagpipes, have been adopted by the Lowlanders since the nineteenth century in order to forge a Scottish identity. Also, Martin is quite happy to have the subject described as Scottish in the main body of the text. He simply wants the nationality field in the info box to read correctly. At the moment it is wrong, firstly because in the time of the subject, the status of 'British citizen' did not exist. The subject was a 'British subject' and so the nationality field should read 'British' and not Scottish. 109.152.249.9 (talk) 16:16, 5 December 2014 (UTC)
The best thing to do is walk away from the British -vs- English, Scottish, Welsh, Northern Irish/Irish usage argument. I tried adopting British & United Kingdom to bios in the past & was unsuccessful. GoodDay (talk) 17:30, 5 December 2014 (UTC)

(edit conflict)In any case, what is 'nationality'? Are you saying no one can be of Kurdish nationality, Scottish nationality, etc? We have an essay Wikipedia:Nationality of people from the United Kingdom. What do you think of it? You're going to have a hard time insisting that every UK citizen be called British. And how do you deal with dual nationality if you won't allow self-identification? I still identify with my home country, I wouldn't want a nationality foisted upon me. Dougweller (talk) 17:42, 5 December 2014 (UTC)

In the case that Martin is referring to, the subject is described as Scottish in the main text. Martin is not complaining about that. He simple wants the nationality field in the info box to read 'British'. Do you have any evidence that this particular subject would have objected to his official nationality? 109.152.249.9 (talk) 18:44, 5 December 2014 (UTC)
If it's about a specific case, it's best to reach a consensus on the relevant talk page with people somewhat familiar with the subject. “WarKosign” 19:44, 5 December 2014 (UTC)

Dougweller, like it or not, like most people, you do have a nationality foisted upon you. If you have a passport it will be the nationality that is written on it, it will be the independent state to whose laws you are subject, or the country whose embassy you would usually go to if you got into trouble in a foreign country. You are free to describe yourself and self-identify in any way that you wish but your nationality is a simple matter of fact. I cannot, and do not, insist that every British national is decribed as 'British', just that their Nationality is stated as 'British'.

To counter the misinformation: "nationality" is nothing to do with "British". There is no "official nationality". There is no such thing as "British nationality". There is no mention of "British nationality" (or any nationality) in UK passports or on UK birth certificates. People are called "British citizen" on UK passports. Citizen means having the full rights of citizenship of the UK. The UK, since its establishment, and as currently established, is a union of nations. One of those nations is Scotland. So, by definition, it is possible for someone to be described as Scottish or of Scottish nationality. Also, but I could stand to be corrected on this, on birth certificates of persons born in the UK I think the particular royal coat-of-arms of the nation in question (be it Scotland, England, Wales, etc,) appears. Tiptoethrutheminefield (talk) 15:46, 8 December 2014 (UTC)
Tiptoe, I'm afraid you are wrong. British nationality is clearly defined in this government website https://www.gov.uk/types-of-british-nationality/overview British citizenship has been a sub-set of British nationality since 1983. 109.152.249.9 (talk) 16:04, 8 December 2014 (UTC)
None of that is to do with the concept of "nationality" as expressed in this RfC, which is about being a member of a nation. There is no nation called Britain so there is no British nationality. Tiptoethrutheminefield (talk) 16:27, 8 December 2014 (UTC)
Tiptoes, The document in the link makes it quite clear that there is British nationality. 109.152.249.9 (talk) 16:44, 8 December 2014 (UTC)
No, it simply uses the term, colloquially, to refer to citizenship. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:16, 16 December 2014 (UTC)

I am looking for a general policy

This is not just about a specific case it is about how to maintain a NPOV policy for Wikipedia. The probem with many bios is that various groups of editors want to try to claim ownership of the good and the great using the term 'nationality' (and maybe to disown certain less agreeable characters). In the example of Maxwell, he was born in Scotland to Scottish parents, educated in Edinburgh, Cambridge, Aberdeen and London, where he did his most important work. I do not think it is known how he self-identified. Now all that cannot posssibly be condensed into the name of a single country but at present, he is being 'claimed' by Scotland. I am not trying to claim him for England, London, or Britain; no one should be doing that. The details of such matters can be explained in the text but his nationality was 'British'. He was ultimately subject to the rule of the UK Parliament. Scotland has a separate legal system from the rest of the UK but, if the UK parliament had, for some reason, conscripted Maxwell to fight in a war. Maxwell would have had to do so. Had he had, say, French or German nationality he would not have had to fight.

The case of Marie Curie is still more complicated and regularly the subjecty of edit wars.

I am proposing that in all cases where reasonably practicable, the term 'nationality' should be reserved for the legal nationality of the subject based on the independent state to whose laws they are subject. The aim is to prevent the term from being abused as a means for various people to try to claim the good and the great for their own.

I propose to formulate the wording for a RfC to get the widest possible input from the WP community. Martin Hogbin (talk) 15:17, 6 December 2014 (UTC)

There are different definitions of nationality, different rules concerning how it is determined and how it can or cannot channge. A few examples:
  • Soviet subjects had an internal passport, with their nationality/ethnicity stated, and used for official or unofficial discriminaton by the authorities. The nationality of a child was of one of the parents, usally be parent's choice. There was no way to change the registration (except bribing a clerk).
  • Israel citizens had their ethnicity ("nation") stated in the ID cards, as plain "Jew" or "Arab" till 2005 and currently encoded (different number of asterisks for each nationality). For a child to be considered to be of Jewish nationality the mother has to be Jewish, I'm not sure if for other enthnic groups it is determined by the mother or the father. A person undergoing Conversion to Judaism under certain condition can change the registred nationality. Nationality of non-citizens and their relatives detrimes their ligibility for Israeli citizenship.
  • A person born to Dutch parents is considered Dutch national by the Dutch law. A child born to non-Dutch parents in Netherlands is normally not considered Dutch national.
  • A person born in the USA to parents of any nationality is considered an American national. "Americans do not equate their nationality with ethnicity, but with citizenship", therefore there are many Americans that are proud of their deverse enthnicity, such as Italian American, Chinese American, etc.
As you can see these laws are complicated, depend on many details and often conflict with each other, so I don't think there can be a simple policy in wikipedia to determine a person's nationality. “WarKosign” 18:06, 6 December 2014 (UTC)
I do not see as much of a problem as you do. Whatever the laws of a country on nationality those are the laws that we should apply.
I am not suggesting that we equate nationality with ethnicity, religion, self-identification or anything else. That is exectly my point. Nationality is determined by the laws of the countries of which a person may be a national. This is an objective criterion which does not depend on interpretation by editors here. As it is now, there is a continual clamour for ownership of the good and the great. Martin Hogbin (talk) 18:24, 6 December 2014 (UTC)
In some cases giving the correct nationality of a subject might look incongruous but that can be explained in the text. That must surely be better than trying to sum up issues of birthplace, national identity, ethnicity, religion in just one term. Martin Hogbin (talk) 18:27, 6 December 2014 (UTC)
I think you are confusing the nationality with citizenship. In many countries they are the same, in many others they are different.
Applying the laws: What is the nationality of a child born to a Dutch father and a Jewish mother in the USA who later repatriated to Israel ? Dutch, American or Jewish ? It is not up to us to determine the nationality in complicated cases, it is up to reliable sources (including the person in question themselves as a primary source) to tell us what the nationality is. “WarKosign” 19:41, 6 December 2014 (UTC)
I cannot answer your question but I can say for sure that there will be an answer, determined by the relevant laws of The Netherlands, US and Israel. Whatever those laws say is the nationality we must use in WP. It could be dual or triple or they might even be stateless but whatever it is it will be a matter of fact, not something that we as editors of an encyclopdia can make up. The person concerned cannot decide either, in many cases that may wish that they could but nationality is not decided by a person's feeelings or self identity, it is decided by the nationality laws of the relevant independent states.
My main point is this. If we use the international legal position to decide on what nationality to use there can be no arguments or edit warring it will just be a matter of fact. If we allow nationality to be decided by editors here, even by considering sources, or by the person concerned we have a recipe for endless conflict, and worse than that, we mislead our readers by giving them someone's interpretation of what nationality should be. Martin Hogbin (talk) 22:29, 6 December 2014 (UTC)
It would be original research and therefore prohibited. Deciding whether and how the laws of different countries apply to specific people is the lawyer's and government clerk's job, and even they don't always agree. If we use our own judgement we mislead the readers even more, since then we would be giving our own interpretation of what nationality should be, and we are (mostly) not experts. See this article. “WarKosign” 08:53, 7 December 2014 (UTC)
It would be exactly the opposite, it would be determining a matter of fact. The legal nationality is determined by the laws of the coutries involved; no decisions by editors here are required.
In fact, any other method is OR. How exactly would you propose we decide on a person's nationality? Martin Hogbin (talk) 09:39, 7 December 2014 (UTC)
We do not decide, we represent reliable sources. If there is a contradiction between the sources, we represent all the POVs.
Please read WP:SYN carefully: If we have a source saying that people born to British parents in the UK are British, and another that says that X was born to British parents in the UK, it makes perfect sense to reach the conclusion that X is British - yet it is OR/SYN, therefore we do not do it. Instead we find a source that reaches this conclusion for us. “WarKosign” 20:46, 7 December 2014 (UTC)

The only original research relating to this debate, has been on the part of editor FF-UK who is using his own interpretation of census data in order to argue that British nationality no longer exists. British nationality does exist, and it is mentioned frequently on the news. I'm very disappointed that few editors have picked FF-UK up on what he is doing. He is using his own original research in order to push the political cause of burying British nationality. 109.152.249.9 (talk) 20:12, 7 December 2014 (UTC)

IP 109.152.249.9, I know that you have been contributing to WP for only a few days, but before accusing anyone of using original research you should make sure that you understand what it means. You must also stick to the facts, as in other walk of life you must not lie or dissemble. Had you taken the trouble to find out about OR you would have understood that the policy applies to Articles only, it has no effect on Talk Pages. As my only contributions to the James Clerk Maxwell article have been three reverts (all over the last three months) of edits which have sought to change the long standing (eight years) entry for Maxwell's nationality as Scottish, then it is obvious that there is no OR involved on my part as I have contributed no new material whatsoever. As I have said, OR does not apply to talk pages, but in any case I have not used any OR in my talk contributions. I have certainly NOT argued that British nationality no longer exists! What I have done is to cite the results of the 2011 censuses in each of the nations of the UK to demonstrate that only a minority of UK citizens consider themselves to be British as opposed to English, Scottish, Welsh, Irish or some other nationality, this is fact as recorded in the census reports cited. I have also cited references to the fact that Scotland IS a nation, and there IS such a thing as Scottish nationality. By comparison, those who disagree with what I have written on the talk pages have not cited any references to the contrary. Proving that British nationality exists (which is not actually disputed by anyone as far as I know) is in no way a proof that other nationalities do not exist. I expect you to acknowledge what I have written here, and offer a full apology for your false accusations. You need to do this both here and on the other talk pages (including all the talk pages of other users) where you have made similar false accusations. You must undertake not to repeat such lies, and to ensure that your future contributions to WP are made in an honest manner, if you do not know something, do not make it up! FF-UK (talk) 14:47, 8 December 2014 (UTC)
IP 109.152.249.9, I know that you will have seen this by now as you have been busy editing. Why have you not had the decency to respond with your apology? FF-UK (talk) 20:21, 8 December 2014 (UTC)
I am actually disputing that British nationality exists in the way it is being presented here. The words British, British nationals, Briton, etc. are often used very loosely, but can anyone present official documents with the exact words "British nationality" on them? "British national" is not the same as "British nationality". Tiptoethrutheminefield (talk) 16:20, 8 December 2014 (UTC)
How about The British Nationality Act 1981 that defines all this in law. Bagunceiro (talk) 15:53, 9 December 2014 (UTC)
Tiptoethrutheminefield, in what way do you think 'Nationality is being presented here? As the originator of this RfC, I mean it exactly as stated by Bagunceiro, the official nationality of a person. Martin Hogbin (talk) 12:24, 10 December 2014 (UTC)
It does? Where? It refers a lot to "British citizenship", but the only uses of "British nationality" I found were titlees of acts of parliament. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:25, 16 December 2014 (UTC)

RfC (nationality)

The outcome was not to change our current practices.—S Marshall T/C 11:34, 19 January 2015 (UTC)

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

How should we show the nationality of a person in WP? Martin Hogbin (talk) 13:02, 8 December 2014 (UTC)

Please note that this RfC applies only to direct statements of nationality such as, 'The nationality of Joe Soap is XXX', or to the 'nationality' field in an infobox. It is not entended to apply to general descriptions in the text, such as 'The French scientist...'.

This has been a contentious and disputed topic on many talk pages. It is not clear at what level of independence and autonomy we can assign a nationality.

Proposal

We should only allow 'nationality' to refer to an independent state. For current states we should only allow states which are Member states of the United Nations. Nationality should show the independent state to whose laws the person was/is subject. (Dual nationality should be stated as such) Martin Hogbin (talk) 13:02, 8 December 2014 (UTC)

As it seems that most of the respondents have not understood the proposal, let me make clear again that I am not referring to how we describe someone, that can be in a variety of ways (British, Cornish, European) and should, as always, be based on what is said in sources. I am talking about how we dirctlys state their nationality. In an infobox for example. Martin Hogbin (talk) 17:47, 9 December 2014 (UTC)

Support (nationality)

  1. This policy avoids enless arguing and edit warring between separatist and other groups of editors. Details of the exact state of affair for issues such as ethnicity, religion, internal state or country, or self-identification can be described in the text but 'nationality' should be reserved for the independent state to whose laws the person was/is subject. Martin Hogbin (talk) 13:02, 8 December 2014 (UTC)
  2. GoodDay (talk) 13:43, 8 December 2014 (UTC)
  3. 109.152.249.9 (talk) 15:21, 8 December 2014 (UTC)
  4. Wholehearted, strong support. For those who insist nationality is something subjective and "citizenship" is the correct term, perhaps we should change the word "nationality" to "citizenship" if that would appease them. The concept that we're trying to capture is which sovereign nation(s) the subject "belongs" to, not what they personally most identify with or anything of that ilk. WaggersTALK 13:01, 9 December 2014 (UTC)
  5. The fact that only four contributors seem to have supported a no-brainer of a call for an infobox field to have a defined, consistent, clear and objectively verifiable application as against 19 who seem to think it should be a free-for-all based on whatever random descriptions of a person passing editors can dredge up one or two examples of from Google tells you all you need to know about why Wikipedia content is so regularly ridiculed and meaningless. Any serious publication defines its terms and sticks to that definition. Instead, people seem to want readers to come across a one-word description of someone's "nationality" and have no idea in each case whether the classification refers to membership of a nation-state, common – but, inevitably, rarely universal – third-party description of ethno-national identity or self-assertion of the latter. The fact that there are different uses of the term "nationality" in some contexts is not an argument for that free-for-all but precisely the reason infoboxes need to be clear about what exactly they are asserting. And that should of course be the most commonly understood usage, which also has the advantage of simplicity and objective verifiability in most cases. N-HH talk/edits 22:27, 20 December 2014 (UTC)
    I'm sure that the Hispanic leaders of the Puerto Rican independence movement would be overjoyed to find out that their nationality is now unambiguously American. I'm even more sure that the best way to describe a Kurd's nationality is based on which side of the Syria/Iraq border she happened to live. And most of all, I know that the nationality of someone living in Tibet is completely black-and-white--they're Chinese, end of story, and there is no room for reasonable minds to differ. Do you want to volunteer to edit those pages? Red Slash 08:12, 26 December 2014 (UTC)
    I'm equally sure that those very same Puertorriqueños, if faced with a situation in which (legal) nationality mattered, e.g., being arrested in another country, would be waving their blue passports in the face of every official and demanding that their American nationality be respected. Nationality (in the legal sense) is about whose laws you are—and are not—subject to, and which nation is legally obligated to protect you from abuses by other states. It's not about which nation you wished existed or wished would protect you or which one feels like home to you.
    The same is true for Kurds: they have a nation that is supposed to protect them, and which nation that is depends very much on which side of the border they happen to live on. If you're a Kurd who happens to be a (legal) national of Iraq, then only Iraq has the right and the duty to protect you. Kurdistan isn't a nation and therefore cannot, and no other nation has that relationship with that Kurd. WhatamIdoing (talk) 20:03, 26 December 2014 (UTC)
And none of that is Wikipedia's problem, or mine, at least in this respect. That is their "Nationality", as usually defined in the real world. I am aware of the complex identity issues and that they need to be reflected in text. The point, as explained one might have thought, is to define a term, "Nationality", from the outset – in the way that the world generally does, re passports and which embassy you would go to if in trouble overseas, for better or worse – and then have clarity and consistency in the use of that description in an infobox field. Far more problems are created on WP pages when you allow that one-word description to mean whatever any passing ethno-nationalist flag-waver wants it mean on that individual page, even if there might be legitimate real-world problems in a few cases. Do you think this kind of random micro-description is the way forward, for example, User:Red Slash? And are you volunteering to edit that page? N-HH talk/edits 23:52, 27 December 2014 (UTC)
No, the Puerto Ricans (it seems odd to use the Spanish word and then capitalize it) would rely on their citizenship, not their nationality. Red Slash 09:08, 29 December 2014 (UTC)
No, they wouldn't. International laws about nationality, not citizenship, is what requires other countries to respect the USA's involvement in these people's (hypothetical) diplomatic problems.
I admit that this is an arcane little detail that doesn't matter to most people (because most people are both nationals and citizens of exactly one state), but it is actually nationality that matters in this situation. (The essential difference is that nationality is about nations deciding which one of them is responsible for you, and citizenship is about your role in shaping the [Old French] "cite" [the source of the word citizenship].) If you read the article on Nationality, you'll even find a list reliable sources that explain. WhatamIdoing (talk) 21:51, 30 December 2014 (UTC)

Oppose (nationality)

  1. Oppose Nationality "differs technically and legally from citizenship". Some nationalities are shared by several states, some nation states have significant minorities of a different nationality, some nationalities do not have a national state at all. Enforcing wikipedia to have a a 1-to-1 relation between states and nationalities misrepresents the reality. More importantly, wikipedia represents the sources. If the sources say that a person has a certain nationality, this is what we report, whether this nationality has a state, and whether this state is recognized in any way by the UN. Writing anything contradicting reliable sources is WP:OR. “WarKosign” 13:26, 8 December 2014 (UTC)
  2. Oppose Definition of Nationality: "The status of belonging to a particular nation". This RfC has been raised as a result of a lack of consensus on the nationality to be used for citizens of the UK, which is a union of several different nations. As the aforementioned WP article Nationality acknowledges, the meaning: is not defined by political borders or passport ownership and includes nations that lack an independent state (such as the Scots, Welsh, English, Basques, Kurds, Tamils, Hmong, Inuit and Māori). There is longstanding guidance on the subject at Wikipedia:Nationality of people from the United Kingdom. The 2011 UK census required people to state what national identity they regarded themselves as being: English, Welsh, Scottish, Northern Irish, or British (as well as non-UK identities), multiple identities were permitted. The results (England and Wales, Scotland, Northern Ireland) showed that a minority of UK citizens regard themselves as British, either exclusively or in combination with another identity. The census demonstrates that the proposed policy would not be an appropriate solution in the case of the UK, and the existing practice should remain. One size does not fit all. FF-UK (talk) 15:48, 8 December 2014 (UTC)
  3. I understand the frustration of people edit warring over whether somebody is British or Scottish, or Greek or Macedonian, but I don't believe this proposal is the answer. For a start, many article subjects were born, lived and died long before the UN was created. And it would be seriously jarring to have to arbitrarily confer on somebody who died 1000 years ago the 'nationality' of a state they could never have conceived of. My own suggestion would be accept that 'nationality' does not equal 'citizenship' and 'nation' does not equal 'nation state'. So for living and recently dead people, we can separately describe their nationality and citizenship. For long dead people, then a self-attributed nationality is probably the only sensible thing to give, and that might well be a nationality that no longer exists. -- chris_j_wood (talk) 16:17, 8 December 2014 (UTC)
  4. Strongly oppose, if I were ever to have a WP article devoted to me then the only acceptable nationality would be Scottish, and do not assume that means I support the SNP, they are totally misguided.71.228.66.131 (talk) 17:10, 8 December 2014 (UTC)
  5. I Agree with all the reasoning expressed above. I have come across a lot of arguments about Armenian nationality being placed in articles dealing with persons born it the Ottoman empire,, or having parents who were born in the Ottoman empire. Does an Ottoman-era Armenian cease being an Armenian when the land he was living in became the Turkish republic? Or is the father still an Armenian because he was born in 1910, but his son not an Armenian because he was born in 1940? What happens to Turk, Greeks, Armenians, Kurds, Arabs, etc., in this proposed "nationality to refer to an independent state" context? There are nations without independent states, there are nations divided between independent states, there are independent nation states, and there are independent states containing multiple nations. Having a fixed rule will not work because there are so many varying definitions of nationhood. The point of an article should be to tell the reader about the subject of that article, so in many cases it will be appropriate to describe a person's national identity by their nation rather than by their citizenship because nationality does not mean the same thing in multi-nation states as it does in single-nation states. Also, people can change their citizenship, and states, especially ones containing multiple nationalities, have a habit of vanishing from history. I think these things need to be decided on a case by case basis, but putting together some guidelines and precedents would also help things. Tiptoethrutheminefield (talk) 17:05, 8 December 2014 (UTC)
  6. Oppose: the issues of nationality, citizenship, ethnicity, race, and all the like are far to complex and nuanced for a single "one-size fits all" definition. Anything which says "Only people that meet XYZ conditions can claim ABC nationality" which are as broad as this fail to understand what a complex world this is, and this is a fundamentally bad idea for that reason. --Jayron32 17:14, 8 December 2014 (UTC)
  7. Oppose There are too many definitions of nationality by too many sources for it to be a useful term. We should more specific terms like "citizen of", "born in" or "identifies as". CombatWombat42 (talk) 19:21, 8 December 2014 (UTC)
  8. Oppose – "Nation" is a complicated word. It is best to avoid it altogether, as its multiple meanings make it useless in these types of contexts. RGloucester — ☎ 21:57, 8 December 2014 (UTC)
    @RGloucester: On that basis would you support my suggestion (below, in the "Change the word" section) that we either remove Nationality from infoboxes or change it for the word Citizenship? WaggersTALK 15:43, 9 December 2014 (UTC)
  9. Oppose because it isn't Wikipedia's job to try to redefine words for our own convenience. A ridiculous suggestion. AndyTheGrump (talk) 22:51, 8 December 2014 (UTC)
  10. Oppose We should follow the general Wikipedia principle. What do reliable sources say? If reliable sources call a person 'Kurdish', then Wikipedia should also describe the person as Kurdish, even though there is no country associated with that nationality. LK (talk) 10:02, 9 December 2014 (UTC)
  11. As noted in following discussion. Collect (talk) 16:33, 10 December 2014 (UTC)
  12. Oppose Really awful idea, presumably based on a misunderstanding of the constitution of the UK. This is admittedly complex but it may be worth reading up on it before making any more suggestions like this one. --John (talk) 19:20, 12 December 2014 (UTC)
  13. Of course not. Nationality ain't "belonging" to a sovereign state. And the proposal is even worse than that because it suggests that the state (if modern) must be a UN member in order to receive recognition. Wow. Palestinians and Kosovars and Romani and First Nations people and Catalans and Kurds and ... etc. are already discriminated against enough. Red Slash 17:07, 13 December 2014 (UTC)
  14. Oppose Diktats such as this, works counter to common sense and consensus building. Anecdotally yes their does appear to be edit warring with regards to British/Scottish nationality e.g. Gerard Butler and Andy Murray, brought about because of the referendum earlier this year, however I expect this to abate once the passions awakened by this event dampen down. Even in those cases and in even cases where I would expect greater friction (e.g. Nikola Tesla, he's Austrian the successor state of the nation he was born in, Croatian the successor state of the territory that he was born in, Serbian since even though he was born in Croatian territory he was Orthodox and not Catholic, American the nation he emigrated to) the articles as they appear to the reader are sensible and coherent. Yes there may be conflict behind the scenes as an examination of the talk page, and hidden messages will show, however the articles will gravitate to a consensus that the majority of editors can agree on, and does not intrude into the reader's experience.--KTo288 (talk) 07:41, 14 December 2014 (UTC)
  15. Oppose This simply will not work. Nationality is complex and personal. Some BLPs would end up with nationalities that the subject expressly rejects. Also, if we are to restrict it in this way then we should equally insist that every nationality is cited. Is the exact citizenship of most people known? --Escape Orbit (Talk) 18:49, 14 December 2014 (UTC)
  16. Oppose This contradicts established Wikipedia policy, in particular WP:RS. "Nationality" of a person is whatever reliable sources say it is. Anything else is original research.Volunteer Marek (talk) 20:07, 16 December 2014 (UTC)
  17. Oppose arbitrary action which fails to comply with fundamental policies WP:V / WP:OR -- TRPoD aka The Red Pen of Doom 21:44, 16 December 2014 (UTC)
  18. Oppose Frankly, given the whole discussion comes about from objection to discussing Scottishness as a nationality, it has a somewhat nasty, racist taste to it. Adam Cuerden (talk) 21:48, 16 December 2014 (UTC)
  19. Oppose These issues should be dealt with by consensus on relevant talk pages on a case by case basis using the best available RS. I take User:Volunteer Mareks approach on this as eminently sensible. Irondome (talk) 22:18, 17 December 2014 (UTC)
  20. Oppose — I don't really see the point of defining "nationality" in such restrictive terms. If anything, it may come back to bite us all in our collective asses as a means for certain people to delegitimize the aspirations for self-determination among ethnic groups such as the Kurds or the Tibetans. Also, "we should only allow states which are Member states of the United Nations"; so what should we use for places like Palestine or Kosovo? I don't think I'd feel comfortable referring to Kosovo Albanians as "Serbian" or Northern Irish people as "British", particularly not in an infobox, which to an outsider may appear very authoritative in its designations. No, this just opens up a whole new can of worms for very little potential benefit. Kurtis (talk) 00:00, 21 December 2014 (UTC)
  21. Oppose The world is not box-shaped and this is another attempt to over-simplify a complex and contentious topic. Ben MacDui 17:11, 21 December 2014 (UTC)
  22. Oppose this simplistic and inappropriate concept, attempting to apply a Procrustean solution to a complex situation. --Orange Mike | Talk 02:57, 22 December 2014 (UTC)
  23. Oppose Nationality is not defined by the sovereign state in which the subject lives, was born and/or which passport they hold. Nationality is one's national origin or identity, and belonging to a particular nation; a nation; an ethnic or racial group. Daicaregos (talk) 12:13, 22 December 2014 (UTC)
  24. Oppose, nationality is far too complex and thorny a problem for a simple cookie-cutter policy like this to make any sense. Let us decide difficult cases on a case-by-case basis, based on what the sources say, like we do everywhere else. Lankiveil @ Alt (speak to me) 06:04, 23 December 2014 (UTC).
  25. Oppose - Not only members of the United Nations are relevant nations. --NaBUru38 (talk) 15:18, 24 December 2014 (UTC)
  26. Oppose - I don't support this type of blanket approach. You can belong to a stateless nation, and if reliable sources describe that person as such, then that's what we should put in the appropriate article.--Slon02 (talk) 22:28, 24 December 2014 (UTC)
  27. Aside from the obvious BLP breaches involved in ascribing a nationality that people consider incorrect; There are various nationalistic/secession disputes in which Wikipedia would no longer be seen as a neutral voice. I'm not disputing that the current system is complex, but it is our job to explain the complex not to oversimplify to the point of getting things wrong. Many calculations would appear simpler if we decreed that Pi was equal to 3.00, but our aim is accuracy not simplicity. ϢereSpielChequers 12:14, 26 December 2014 (UTC)
  28. We should generally follow what reliable sources associate a person with, although if there are none then the respective sovereign state is a sensible default position. There are too many historical and political special cases for as simple a rule as this to be of much use.  Sandstein  09:09, 31 December 2014 (UTC)

Discussion (nationality)

This is Forum shopping, see Wikipedia talk:Nationality of people from the United Kingdom#Where did it all go wrong?. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 15:30, 8 December 2014 (UTC)

Where's the harm? There's only 2 possible results, here - 1) a consensus or 2) no consensus. GoodDay (talk) 16:02, 8 December 2014 (UTC)
It is not forum shopping at all. WP:Nationality of people from the United Kingdom has never been policy it is just an essay written by a small number of editors, with dissenting opinion suppressed. I am looking for wide community consensus not just for the UK but for all countries. Martin Hogbin (talk) 16:09, 8 December 2014 (UTC)
I referred to a previously-started discussion, not an essay. Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 23:28, 16 December 2014 (UTC)

According to this proposal, what should be written as the nationality of those born in states that are not members of the UN, such as Palestinians? I suppose this proposal would strip Pope Francis of his Argentinian nationality, even though it's unclear which one should be used, since Vatican is not a recognized UN member state and even if it was, "Vaticanian" is not a nationality. “WarKosign” 15:42, 8 December 2014 (UTC)

Actually - Vatican City is a member of two of the oldest international organizations, which are now specifically agencies under the UN (ITC (1865 founded, Vatican City has been a member since 1929) - now ITU, and the UPU (founded 1874, Vatican City a member since 1929) (status disputed 1870 to 1929). It issues passports, has legates to other nations, and is a "nationality" by law. Sorry to break the example :) Collect (talk) 15:07, 9 December 2014 (UTC)
  1. You are confusing citizenship and nationality. I never said there is no Vatican citizenship, only that there is no such nationality. There is no "Vatican nation", there are no "native Vaticanians". Everybody in Vatican were born elsewhere and have some other nationality, about half of them keep dual citizenship.
  2. The proposal as it was written was to include only nationalities of states which are members of the UN, which Vatican is not. “WarKosign” 15:26, 9 December 2014 (UTC)
I fear you elide the fact that the UN gives Vatican City "permanent observer status". Your standards would have said Switzerland was not a "nation" until 2002. And that Germany (BDR and DDR) were not "nations" until 1973, so people born in them had no "nationality." As that is clearly an absurd result, we accept that being a member of UN agencies indicates nationhood. Cheers. Collect (talk) 16:31, 10 December 2014 (UTC)
Assuming you're replying to me - this is not my standard, I oppose the idea that UN has anything to do with a person's nationality. “WarKosign” 16:40, 10 December 2014 (UTC)
It is no different from 'Place of birth' in a few cases this might be difficult to determine from available sources, although there will be a factual answer, but is most cases determining nationality the way that I suggest will be quite straightforward. Allowing any group of people to claim to have their own nationality will not solve any problems. Martin Hogbin (talk) 16:06, 8 December 2014 (UTC)
Yes, but place of birth =/= nationality, and sovereign state of citizenship =/= nationality. A nation and a sovereign state are not identical concepts. Often enough they are, but there exist MANY times when a group of people are reliably (and justifiably) thought of as a "nation" and which are not identical in membership to "citizenship" within a sovereign state. The way you dismiss the situation by implying a lack of ingenuity on the part of people who meet that definition is problematic. When you say "Allowing any group of people to claim to have their own nationality..." makes it seem like any such claim cannot be in earnest, or that we as editors cannot adjudge the difference between an earnest, historical, and justfiable claim of non-state nationhood (by such groups as say the Iroquois, Tibet, Kurds, Basque) with those of people who clearly do not have such a valid claim (such as political stunts like Principality of Sealand or the like) misses the point. That's why we make earnest self-identification as the most important claim there can be. If a person earnestly identifies themselves as Spanish or Basque, we respect that identification, without making our own arbitrary distinctions about which kinds of ethnic identifications are valid, and which are not. --Jayron32 17:24, 8 December 2014 (UTC)
Allowing smaller groups of people with less autonomy or independence (such as the Scots, Welsh, English, Basques, Kurds, Tamils, Hmong, Inuit and Māori) does not solve any problems. There will always be smaller groups within those groups which some individuals will want to identify with. Not all Scots are the same, are we to have Highlanders and Lowlanders and what about Essex man? It will be a never-ending conflict. All the states of the US, which is a federation have more right to nationhood than any of the groups mentioned above.
Please note that this is not an attempt to suppress the identity of anyone. People will still be able to be described as Scottish, Inuit, a London Boy, a Jew or whatever we like but in the text, where we can explain the reasons behind the description. The problem that we have in many articles are that groups are using 'nationality' as a way to claim ownership of the good and the great and to support various separatist movements. Let us just treat nationality like 'date of birth' or 'place of birth'. It should be a simple well-defined, easily verifed fact, not a political statement. Martin Hogbin (talk) 16:26, 8 December 2014 (UTC)
Just to be clear, I am not proposing that historical characters must be given nationalities based on current states, only that when current states are applicable that we use only independent states, not regions within them. Martin Hogbin (talk) 16:33, 8 December 2014 (UTC)
Have you noticed how many editors are raising complications that don't even arise in the case of James Laidlaw Maxwell? In most cases there won't be complications, such as have been raised, and when they do arise, they can be discussed individually on a needs be basis. 109.152.249.9 (talk) 16:51, 8 December 2014 (UTC)
Since you mentioned "most cases" I thought of China, 91% of the population are "Han Chinese", but there are ~112M people of 55 other nationalities. Even if the suggested criteria is correct for 64M citizens of the UK, it is wrong for double that many in China alone. “WarKosign” 17:17, 8 December 2014 (UTC)
Well what about James Laidlaw Maxwell? It would be a great help if you could give us your opinion on a particular case. He was a British national under both the law of the time and the existing law. Would you describe his nationality as British or Scottish? Have a read about him please. 109.152.249.9 (talk) 17:24, 8 December 2014 (UTC)
I couldn't find any sources giving his nationality/ethnicity, but since he was born in Scotland if I had to guess I would go with Scottish. The guess is of course unusable on WP. “WarKosign” 18:30, 8 December 2014 (UTC)

WarKosign, No need to guess. He was Scottish and British, and his nationality was British. 109.152.249.9 (talk) 19:17, 8 December 2014 (UTC)

How do you know, are there reliable sources saying "James Laidlaw Maxwell was of British nationality" ? If you're concluding from some rules yourself, maybe you're correct, but it's WP:OR and is as useless as my guess. “WarKosign” 19:27, 8 December 2014 (UTC)
Can I suggest we retire James Laidlaw Maxwell as an example for this discussion. I think he has long passed the point of usefulness for this discussion, which is in danger of becoming about the nationality of James Laidlaw Maxwell rather than how we deal with all the different nuances of nationality. -- chris_j_wood (talk) 10:16, 9 December 2014 (UTC)
I'm afraid it was about him from the beginning. “WarKosign” 11:24, 9 December 2014 (UTC)
Maybe I'm wrong here, but isn't the issue really about James Clerk Maxwell, not James Laidlaw Maxwell? The former is much more famous, therefore providing more opportunities to fight over what nationality he was.  :) The latter article doesn't even have an infobox, and I have seen discussions of what nationality should be stated in the infobox, so I'm thinking we are really talking about JCM. In my opinion, the sources seem to support the "nationality" of Scottish, though I would be in favor of doing away with the "nationality" parameter altogether (perhaps just for controversial cases) in favor of just saying where the person was born, resided and died. As for Pope Francis, I hope that part of the discussion is just a joke. He didn't stop being Argentinian just because he got a live-in job in another country. Neutron (talk) 00:54, 13 December 2014 (UTC)
From our readers' perspective

The most important thing from our readers' perspective is that they know what we mean; what verified fact we are informing them of. The proposed policy makes this quite clear; we are telling them the independent state to whose laws the person is subject.

There may be other meanings of the word 'nationality' in use but, if we go beyeond the proposed definition (which I believe is how the term is most commonly understood) how will our readers know what we are telling them? Do we show the smallest group that has ever claimed nationhood of which they are a member? Do we allow people to choose their own nationality by basing it on self-identification? Is it the group of people who claim ownership to this great person, or the group on whom we can foist ownership of the evil? Is it just promotion from some separatist movement? Maybe it just the consensus of the day? How are our readers to know what we are trying to tell them?

Ther may still be problems with the proposed definition if souces are not clear but at least our readers will know what we intend to tell them. I cannot think of any other definition of 'nationality' that is usable and having no definition of waht is to be put onto a field in an infobox makes the field completely pointless. The only other rational proposal is never to talk of 'nationality' at all.Martin Hogbin (talk) 17:22, 8 December 2014 (UTC)

Nope - you aren't giving a 'verified fact' at all - instead, you are asserting that your particular definition of 'nationality' (which may not be shared by our readers) is the only correct one. Do I need to explain exactly how many Wikipedia policies that violates? AndyTheGrump (talk) 23:08, 8 December 2014 (UTC)
I am not asserting anything. Im only suggesting that, in Wikipedia article, we stick to a well-defined and easily verified meaning of the word, especially in infoboxes. If we do not do that then we cannot use the term at all. What can it possible mean if we are free to decribe a person born in France to French parents, who holds a French passport and has no dual nationality and has never been naturalsied into another nationality as having German nationality? Martin Hogbin (talk) 16:36, 9 December 2014 (UTC)
Here are today's news items from the British Broadcasting Corporation. http://www.bbc.co.uk/news/uk-30374247 (British base jumper) http://www.bbc.co.uk/news/uk-england-bristol-30375335 (British businessman) http://www.bbc.co.uk/news/uk-30383202 (two British tourists) http://www.bbc.co.uk/news/uk-england-hampshire-30378006 (missing British man). How many more of these do we need to convince some people here that British nationality does exist and that it is in widespread use? 109.152.249.9 (talk) 19:14, 8 December 2014 (UTC)
Martin Hogbin wrote: "The proposed policy makes this quite clear; we are telling them the independent state to whose laws the person is subject." Really? Surely a person is subject to the laws of the country of which they are a citizen, but also the jurisdiction they happen to be in at any point in time. An American in many US states can legitimately carry a pistol, but an American (other than one to whom special rights had been granted, such as the President's Secret Service bodyguard during a Presidential visit) who tries to carry a pistol in the UK is going to end up in jail, very rapidly, and for a long time. Any more woolly thoughts to offer to us Martin? FF-UK (talk) 01:24, 9 December 2014 (UTC)
IN BBC-speak, "British" = resident of the UK but not English (or at least not from the south of England). An "English athlete" is a successful athlete from England. A "British athlete" is a successful athlete from Scotland or Wales or Northern Ireland. A "British football fan" is an English football thug who has broken the law. A "British tourist" is a drunken English tourist abroad. Tiptoethrutheminefield (talk) 15:50, 9 December 2014 (UTC)
How can I make this more clear? I am not referring to how we describe someone, 'British', 'Cornish', 'European' might all be valid and correct descriptions. I am only talking about specific claims of nationality, in an infobox under the 'nationality' field for example or if we were to say, 'this person's nationality is Cornish'.
The anonymous unsigned contribution above is a particularly unhelpful one, There is no question that describing a person who comes from Cornwall as Cornish is valid, as is describing a native of any European country as European, but Cornwall is a county, Europe is a continent, neither are, by any stretch of the imagination, nations. Therefore, neither can have a nationality attached to them. But, this is a straw man argument, no one, as far as I can tell, has suggested otherwise. What we should be concerned with is the nationality associated with those nations which are not independent, but nevertheless are clearly identifiable as nations, typically England, Scotland and Wales, and anywhere else with comparable characteristics. FF-UK (talk) 23:01, 9 December 2014 (UTC)
Yes, I did forget to sign above. Who decides which are nations and which are something else; editors here? You have consistently failed to explain to me why Scotland, which is part of a Unitary state should have a nationality and Texas, which is a part of a Federation and which has a nationalist movement should not. You simple brush aside Cornish nationalism by saying they are 'just a county'. By what right do you make these decisions?Martin Hogbin (talk) 11:06, 10 December 2014 (UTC)
We use sources, I have provided sources for Scotland being a nation (eg the speech from former Prime minister Gordon Brown in defence of the union, and for Scottish being a nationality (the Lord Lyon King of Arms states: "this is the correct flag for all Scots or Scottish corporate bodies to fly to demonstrate their loyalty and their Scottish nationality." See http://www.lyon-court.com/lordlyon/236.html). I have also provided a source to explain to you why Texas cannot be considered a nation, the decision of the Supreme Court on that matter. "In the Constitution, the term "state" most frequently expresses the combined idea just noticed, of people, territory, and government. A "state," in the ordinary sense of the Constitution, is a political community of free citizens, occupying a territory of defined boundaries, and organized under a government sanctioned and limited by a written constitution, and established by the consent of the governed. It is the union of such states, under a common constitution, which forms the distinct and greater political unit which that Constitution designates as the United States, and makes of the people and states which compose it one people and one country." I have not seen any official sources from you which support your claims about Texas and Cornwall, and I would point out that the previously referenced England and Wales census reports that only a small minority, 14%, of the population of Cornwall claims Cornish national identity. Sources Martin Hogbin, sources. FF-UK (talk) 16:34, 10 December 2014 (UTC)
Martin, you did not limit your initial proposal to just infoboxes, and many articles do not have infoboxes anyway. Maybe a direction to take would be to revise the text used in infoboxes, rework it so that there is not a connection made between citizenship and nationality. So someone in an infobox can be described as a citizen of Turkey can still also be called a Kurd, and so on. Tiptoethrutheminefield (talk) 03:30, 13 December 2014 (UTC)
Ahhh .. Sorry. I see things along those lines are being suggested below. Tiptoethrutheminefield (talk) 03:33, 13 December 2014 (UTC)
Change the word

To most people, nationality and citizenship are interchangeable, and perhaps the word "nationality" was used originally when the original editors meant "citizenship". According to some in the discussion above, "nationality" is a fluffy, transient thing that an individual can seemingly make up and change on a whim. As such it can never be pinned down and perhaps doesn't belong in an encyclopaedic article about them unless their nationality is something that they're particularly known for. Citizenship is much more clear cut and definitive, and I suspect that's what the creators of {{Infobox Person}} and the like really meant when they used "nationality". So instead of quibbling about what "nationality" may or may not mean, let's settle on the meaning we want (something definitive, robust and reliably source-able) and use the word that best describes that concept. Let's drop "nationality" in favour of "citizenship" so we can stop the silly arguments. WaggersTALK 13:13, 9 December 2014 (UTC)

If it's about citizenship, I think there is very little to discuss. A person holding a British passport may consider/declare themselves to be Scottish, a Highlander, a Nairnshireman or anything else as they like while the fact of having a certain citizenship is official, registered and hard to dispute. Citizenship should not be limited to UN member states, since there are exceptions such as micronations. “WarKosign” 14:25, 9 December 2014 (UTC)
I contest that "to most people nationality and citizenship are interchangeable". For many people around the world, they would not consider their nationality to be simply the sovereign state they are official citizens of. Now, whether or not we want Wikipedia to report citizenship or nationality, both, neither, or some combination thereof, is an unrelated issue. But you CANNOT say that people consider the two concepts similar or identical. For you they may feel that way, but you can't demand that you're own personal perspective is universal. There are a multitude of perspectives on this... --Jayron32 14:47, 9 December 2014 (UTC)
I also don't agree that "to most people, nationality and citizenship are interchangeable", and don't have much to add to Jayron32's comment in that regard. Ncmvocalist (talk) 15:03, 9 December 2014 (UTC)
"Now, whether or not we want Wikipedia to report citizenship or nationality, both, neither, or some combination thereof, is an unrelated issue." - no, this is the very crux of the issue being discussed above. If we've been saying "nationality" when what we've meant is "citizenship" all along, we have a very straightforward way forward. On the other hand, if nationality is so ambiguous and poorly defined, it has no place in an infobox and we have another very straightforward way ahead. WaggersTALK 15:17, 9 December 2014 (UTC)
But what we mean is not necessarily citizenship, or necessarily nationality. It can be one, the other, both, or neither, depending on the context. Both citizenship and nationality can be important for understanding the biography of a person. So in some cases can ethnicity, race, gender, and a whole slew of other personal identifiers. Sometimes those traits are important, sometimes they are not, and sometimes more than one of them are, sometimes in different ways, and sometimes none of them are important. It isn't helpful to say "We report this one and only one personal characteristic, we report it all the time, and we don't report any of the others". THAT'S the big problem here. There is not a simple solution to this, because it is not a simple issue. People want it to be simple and organized and it just isn't. Wishing it were so doesn't make it so. --Jayron32 17:15, 9 December 2014 (UTC)
Of couse life is not simple and no one is trying to make it so but we must be clear what we are telling pepole. If anyone would like to come up with an unambiguous term that we can use as a field in an infobox to indicated the independent state(s) to which a person belongs I would be more than happy to use it, and to delete the imbiguous and popularly misunderstood fields of 'Nationality' and 'Citizenship'. Martin Hogbin (talk) 10:27, 10 December 2014 (UTC)

Why is there such a resistance to the usage of British or United Kingdom in the intros & infoboxes of so many UK bios? England, Northern Ireland, Scotland & Wales make up the United Kingdom, so what's the problem? GoodDay (talk) 15:41, 9 December 2014 (UTC)

UK (and quite a few other states) make up the world, so why not say that your nationality is Earthian ? It's a matter of personal preference. If a UK citizen may decide to declare their nationality as British or as English/Scottish/Irish, both are equally fine since it's a personal matter of feeling belong to a nation. The citizenship is British in either case. “WarKosign” 15:55, 9 December 2014 (UTC)
But why is there resistance on Wikipedia to have British/United Kingdom in these articles? either in place of or along side English/England, Scottish/Scotland, Welsh/Wales & Northern Irish/Northern Ireland? GoodDay (talk) 15:59, 9 December 2014 (UTC)
Nothing wrong with being British, if this is what a person calls themselves. “WarKosign” 16:04, 9 December 2014 (UTC)
Why are we putting so much stock into what a person calls themselves? If one's a human & declares he/she's not a human, does that have to mean he/she isn't a human? These people who were born & live in the UK, are British, whether they like it or not. You can declare your red car is coloured blue, but it's still a red car. GoodDay (talk) 16:09, 9 December 2014 (UTC)
Exactly! Nationality is something that is decided by the states with wich you have some kind of legal connection. In most cases it is very simple, you have the nationality of the independent state in which you are born and the same as your parents. In more complex cases the relevant nationality laws will decide but in all cases it is a matter of fact rather than something you can decide for yorself. That is the reason for wanting to define nationality in this way; we no longer need to have arguments about what someone called themselves or what someone else called them.
WarKosign, I think you are confusing nationality with ethnicity. Martin Hogbin (talk) 16:26, 9 December 2014 (UTC)
Unfortunately, using 'citizenship' instead of 'nationality' does not help much. In the UK the situation regarding citizenship is quite complicated with citizenship being a sub-category of nationality, see British nationality. No dobt there are complications in many other countries. Martin Hogbin (talk) 16:27, 9 December 2014 (UTC)

My answer to GoodDay's question is that the majority of people in the UK have long regarded themselves as belonging not to the UK, but to the constituent country of the UK from which they are from. As in other nations, national pride is a significant factor in the lives of many peoples and therefore the nation they identify with is also of significance. However, we do not need to speculate on this, there is hard data. In 2011, for the first time, quantitative data was gathered by the UK censuses which required people to state what national identity they regarded themselves as being: English, Welsh, Scottish, Northern Irish, or British (as well as non-UK identities), multiple identities were permitted. The results (England and Wales, Scotland, Northern Ireland) showed that a only minority of UK citizens regard themselves as British, either exclusively or in combination with another identity. The majority identify themselves as belonging to their own constituent nation. The actual percentages vary, but are all in the region of 70% of English, Scottish and Welsh residents identifying themselves as English, Scottish or Welsh respectively (rather than British). The area with the highest percentage (just under 40%) of those identifying as British is Inner London, which the census analysis identifies as having a high proportion of immigrants, suggesting that immigrants are more likely than natives to identify as British. FF-UK (talk) 16:41, 9 December 2014 (UTC)

But, they're British. My concern is the resistance being shown here (at Wikipedia) by editors. Again, you declare yourself a Martian, but that doesn't make you a Martian. GoodDay (talk) 16:47, 9 December 2014 (UTC)
GoodDay, you may declare yourself a Martian if you wish, but I am English. FF-UK (talk) 16:52, 9 December 2014 (UTC)
You're British & there's nothing you can do about. But, this is Wikipedia & so yes, you certainly can (and are) doing something about :( GoodDay (talk) 17:04, 9 December 2014 (UTC)
It least, your nationality is 'British', FF-UK. You can describe yourself any way that you like. If people could change their nationality just by thinking of themselves differently there would not be a long fence with armed guards separating the US from Mexico. Mexicans would be able to say, 'I now consider myself to have US nationality' and just walk accrosss the border as US nationals. Martin Hogbin (talk) 18:08, 9 December 2014 (UTC)

Jayron32, you say, 'nationality, citizenship, ethnicity, race, and all the like are far to complex and nuanced for a single "one-size fits all" definition'. You are absolutely correct, of course, that is exactly why I am trying to avoid doing this. Citizenship, ethnicity, race, and all the like should be discussed in the text, based, as always, on what sources say. Martin Hogbin (talk) 18:03, 9 December 2014 (UTC)

So why should nationality be treated differently ? If anything in the list of attributes is relatively simple it's the citizenship - having a certain citizenship is a well-defined, documented and verifyable fact. “WarKosign” 18:13, 9 December 2014 (UTC)
WarKosign, if you can proove that you are correct in saying that, 'having a certain citizenship is a well-defined, documented and verifyable fact' we would have a simple solution; just give a person's citizenship and remove all reference to 'nationality' from infoboxes and direct statements, but I fear it may not be so simple, have a look at the British Nationality article, which shows that in at least one case it is more complicated. Martin Hogbin (talk) 18:31, 9 December 2014 (UTC)
Did you mean British nationality law ? The law is complex, but if we have a source saying that someone aquired a British citizenship at birth or at some later date - it's a simple statement that is not open to interpretation. “WarKosign” 20:41, 9 December 2014 (UTC)
See, now we're getting into language issue. What it means to be a "British national" is a specific and legally defined thing, in many ways in this one context in means what "citizenship" often means in other countries. It's a word choice here (one ensconced in law), however one can be both simultaneously a legally defined "British national" and also be Scottish. To imply that one must choose between one or the other, or that Wikipedia must only define people as one and ignore the other, is a major problem. Why must we be forced to make an artificial choice between the two: Cannot one be both a legal British national, and of Scottish nationality (or English or Welsh or Northern Irish)? Being one does not exclude being another at the same time. Ethnic classifications are not either-or propositions, and yet people seem to be demanding that they are. But back to the crux of the issue: What we're talking about is the use of the word "national" (nationality, etc.) in the specific context of the UK, and in the more specific context of this one law: But the existence of this law does NOT make us ignore the very real issues of nationality outside of the British context, nor does it make us ignore the very real issues of various ethnicities within the UK itself. Demanding that we ONLY classify people because one sovereign state uses one specific word (in a somewhat idiosyncratic way, I might add) is a bit off... --Jayron32 04:26, 10 December 2014 (UTC)
Thanks for at least getting involved in a rational discussion but again you misunderstand me, I am not trying to classsify anyone. The idea that all people can be completely classified with a single term is obviously absurd and it is not what I am trying to do. I am talking about how we decide what to put in the 'Nationality' field in an infobox. The idea of an infobox is that it gives basic, simple, easily verified, facts about the person, and does not deal with compex isssues of self-identity or how you are considered to be by the rest of the world. Take, for example the, Place of birth' field in an infobox and consider the case of a man who was born in London at 6:00 in the evening but next tmorning was taken back to his home in Paris where he lived and worked for the rest of his life. In every respect, this man would be considered a Parisian and that would be a perfectly good description of him but the 'Place of birth' infobox field would have to show London, because that is where he was born. His ethnicity, self-identified group, how he was regarded by the world, legal nationality, place where he was best known, might all be different places, and these should all be mentioned in the text (based of course on what reliable sources say) but none of that can make his 'Place of birth' anything other than London.
If we treat the nationality field differently, how will our readers know, which paricular informal meaning of nationality WP editors have chosen for that person. All Im am suggesting is that we standardise the 'Nationality' filed in an infobox so that readers know what it is telling them. My only agenda is to keep WP factual and neutral. Martin Hogbin (talk) 10:23, 10 December 2014 (UTC)
British nationality law "is the law of the United Kingdom that concerns citizenship". In the context of the article nationality and citizenship are used interchangeably. In other contexts the word nationality has other meanings, therefore we better stick to citizenship, which is unambiguous. One can be a British citizen ("national") and belong to the Scottish ethnic group ("nationalility"), there is no contradiction between the two affiliations except the confusion between the words. “WarKosign” 05:18, 10 December 2014 (UTC)
Fairly obviously (the clue is in the name), British nationality law is the law of the United Kingdom that concerns citizenship of all the people who have British nationality. The British govenment clearly have no power to determine the citizenship of anyone else. Martin Hogbin (talk) 10:30, 10 December 2014 (UTC)

Both |nationality= and |citizenship= have been available in that infobox since 2007 or so. If "nationality" is too difficult to source, or if you've got disputes between people who think that different levels of nations ought to count more than others, then stop using it, and put |citizenship= in the box instead.

Also, for the dispute at the essay, some people might like to read what the UK's government says at http://www.ons.gov.uk/ons/guide-method/measuring-equality/equality/ethnic-nat-identity-religion/national-identity/index.html It appears that the Office of National Statistics believes that "Scottish" is properly considered a national identity rather than a nationality. WhatamIdoing (talk) 04:26, 10 December 2014 (UTC)

One option worth considereing would be to insist on strict and authoritative sourcing for all statements of nationality or citizenship. By this I do not mean that we find in the book, 'Great inventors of Cornwall' as line saying, 'Joe Soap' was a Cornish chemist', or a book saying 'Fred Bloggs was a British statesman' but a clear and specific statement of nationality, for example 'Ola Nordmann had Norwegian nationality' or 'Ola Nordmann was a Norwegian national', or 'Unce Sam was a US citizen'. That would conform to the highest standards of WP and might resolve this dispute. Martin Hogbin (talk) 11:19, 10 December 2014 (UTC)
The problem with that is that such statements tend not to be made unless nationality and/or citizenship isn't 'obvious' - see how long it takes you to find an explicit statement that for example David Cameron is a British citizen... AndyTheGrump (talk) 11:25, 10 December 2014 (UTC)
So what do you suggest that we put in the infobox under 'nationality'? Do we just make something up? Martin Hogbin (talk) 12:21, 10 December 2014 (UTC)
I believe we should avoid the term "nationality" entirely , since it can mean either citizenship or ethnicity. We should use ethnicity and/or citizenship to describe people.
In case of a hypothetical Scottish UK citizen there is no argument that his ethnicity is Scottish and citizenship is British, while you can argue for a long time what his nationality is.
It works for ethnic minorities, a state with several different ethnic groups, an ethnicity split between several states, etc. I do not see a case that ethnicity/citizenship combo doesn't cover. Do you ?
"John Doe was a French musician with German citizenship who lived and worked in Italy". “WarKosign” 13:19, 10 December 2014 (UTC)
WarKosign, I agree with you that if there is no agreement on how to define nationality in an info box, then it should be abolished altogether as it becomes wide open to abuse. On a side note, there is no such thing as Scottish ethnicity. There is a major ethnic fault line running between the Highlands and the Lowlands, with the Highlanders being Irish and the Lowlanders being English. There is however a modern Scottish national identity. 109.152.248.204 (talk) 17:15, 10 December 2014 (UTC)
Frankly, infoboxes are supposed to be quick summaries of what's in the article. When the question of nationality or citizenship or ethnicity is complex or controversial so that it cannot be included in the infobox in a manner which is not controversial (in good faith, at least), misleading, incomplete, or excessively lengthy, then it should simply be left out and set out at reasonable length in the body of the article. That's not just true for nationality/citizenship, it's true for any information in an infobox. The summary nature of infoboxes far too often causes them to be battlegrounds and that's not good for the encyclopedia (or for those of us who work in dispute resolution). Anyone up for an attempt to include this concept at MOS:INFOBOX? Regards, TransporterMan (TALK) 17:45, 10 December 2014 (UTC)
TransporterMan, I agree entirely. In the case that brought this matter here in the first place, the nationality field is being abused by Scottish separatists who are trying to usurp the sovereign British nationality with a subordinate Scottish nationality. The solution would appear to be to remove the nationality field altogether and to deal with the subject's origins in the main body of the text. 109.152.248.204 (talk) 17:57, 10 December 2014 (UTC)
Where does this nonsense about "abused by Scottish separatists" come from? Do you have one iota of evidence that this is a real issue? If not, then do not keep attempting to set it up as a straw man. FF-UK (talk) 17:57, 10 December 2014 (UTC)

IP 109.152.248.204 why do you keep changing your identity? Yesterday you were posting as 86.180.32.141, before that it was 109.152.249.9, and you first became involved in this subject as 86.145.98.85. These are all BT WiFi public hotspots. Are you doing this to confuse other WP editors? If not, then please register so that your identity becomes consistent. Thank you. FF-UK (talk) 17:57, 10 December 2014 (UTC),

This is just Unionist-ultras trying to remove any modern reference to English/Scottish/Welsh. It happens all over wikipedia, usally to Enlgish related articles. Nothing but modern politics wiggling it's way into wikipedia.--86.159.27.234 (talk) 20:06, 10 December 2014 (UTC)

That statement from another BT WiFi hotspot IP is as groundless as the other IP's statement above. There is no evidence for either extreme and making such claims does not help rational discussion. FF-UK (talk) 20:35, 10 December 2014 (UTC)
Of course there is evidence. Why do you think this discussion is so heated? And the proposal is not restricted just to the UK. Turkish "ultras" (to borrow the anon's word) have been for decades trying to remove any modern reference to Kurds or Armenians or Greeks in Turkish related articles. And Greek "ultras" do it for Greek or Cyprus related articles. And I'm sure Russian "ultras" do their bit too, and Albanians, .... the list is probably endless. Tiptoethrutheminefield (talk) 03:40, 13 December 2014 (UTC)
I haven't seen any Greek editors, even if misguided, that pursue this specific type of activity, related to suppression of national origins. Care to show some diffs about that? Δρ.Κ. λόγοςπράξις 03:52, 13 December 2014 (UTC)
Nobody was trying to suppress Scottish identity. The subject James Clerk Maxwell is described as Scottish in the lead, and nobody has been challenging that. Editor FF-UK is however suppressing the subject's British nationality in the info box by usurping it with a Scottish nationality, when no such sovereign nationality exists. The correct way to do it would be to have the subject described as Scottish in the lead and to have his nationality stated correctly as British in the info box. It would then be correct and balanced all round. 109.152.248.204 (talk) 07:13, 13 December 2014 (UTC)
Which meaning of the word "nationality" are you using, ethnicity or citizenship ? If we do not use the ambiguous word "nationality", there is far less dispute. "James Clerk Maxwell had Scottish ethnicity and British citizenship." Any objection ? “WarKosign” 08:04, 13 December 2014 (UTC)

Warkosign, There was no such status as 'British citizen' in Maxwell's time. It only came into existence in 1983. Maxwell was a 'British national'. As regards Scottish ethnicity, there is no such thing. The Scottish Lowlanders, of which Maxwell was one, have English ethnicity. Maxwell is already described as Scottish in the main body of the text, and nobody is objecting. The objection is about usurping the sovereign nationality in the info box with 'Scottish nationality' which has no administrative signifance. If agreement can't be reached as regards the info box, then it's best to remove the nationality from the info box altogether, just as you suggest. That would leave Maxwell described as 'Scottish' in the main body of the text, in line with most modern sources. Nobody is objecting to describing Maxwell as Scottish. The objection is about the words 'British Citizen' and 'Scottish national'. 109.152.248.204 (talk) 14:55, 13 December 2014 (UTC)

Dear IP, Maxwell's relation with the UK was what is called citizenship today, therefore today we can say that he was a citizen. Maybe you are correct and at that time it was called being a national (as it is sometimes called today), but the term is ambiguous (could mean either citizenship or ethnicity) and the proposal is to use other, unambiguous terms instead.
According to this article the Scottish people "are a nation and ethnic group native to Scotland", so how can you say there is no Scottish ethnicity ? “WarKosign” 15:16, 13 December 2014 (UTC)
You need to read up on your history of Scotland. There is no such thing as Scottish ethnicity. You'll find that the Lowlanders are English and the Highlanders are Irish, although that is perhaps somewhat of a simplification, because there has been a lot of mixing over the centuries. Even the great Scottish hero William Wallace was English. On the other matter, on what manner of reasoning can you deny that Maxwell has British nationality while claiming that he has Scottish nationality? British nationality, a term which is still in use today and about which there is legislation, is his sovereign nationality. See this website https://www.gov.uk/types-of-british-nationality/overview 109.152.248.204 (talk) 17:34, 13 December 2014 (UTC)
That's a bad understanding of history, as it assumes that no ethnic group can ever change or evolve, that no new ethnic groups ever get created, old ethnicities die out, etc. What a strange way to think about the world, that all ethnic groups have existed statically since God created the earth, and haven't moved or changed or anything in all that time. Of course, modern Scots and modern Irish ethnic groups evolved from common ancestors, and the influence of the English and later Normans on Lowland/Southern Scottish people is well documented, but those historical truths doesn't mean that Scottish ethnicity doesn't exist. Of course it does. Else, we could claim that the English don't exist, because they're really just Northern Germans & Southern Danes, and we should just count the English as a subset of Danish nationality for that reason. That's self-evidently silly. Just as your assertion is. --Jayron32 18:39, 14 December 2014 (UTC)
Jayron, An English speaking British ethnic group has evolved from all the various Celtic, Anglo-Saxon, and Dane inputs. There are still remnants in the Highlands and Islands, North Wales, and Northern Ireland, that are sufficiently different from the mainstream British ethnic grouping that they might be considered as culturally diverse, but even they are very much diluted from their original form, and well integrated into British society. There is no such a thing as Scottish ethnicity. Anybody who has ever worked amongst British people could tell you that Scots integrate perfectly, and that they are no more diverse from the Kent and Sussex man, than is the Scouser or the Geordie. Read Billy Connolly on the matter http://www.theguardian.com/culture/2014/feb/17/billy-connolly-not-vote-scottish-independence-referendum 109.152.248.204 (talk) 00:21, 15 December 2014 (UTC)
Billy Connolly is a funny man, but he's hardly an expert on the history of the Scottish people... --Jayron32 05:34, 15 December 2014 (UTC)
Jayron32, The blending and creating of a new ethnic grouping that you are talking about above, took place in an all British context within the British Isles. It is not the case, as you seem to be implying, that a unique Scottish ethnicity emerged and diverged from the rest of the British Isles. It's true that in Victorian times, the Lowland Scots, while on the one hand becoming ever more closely integrated with the English, adopted aspects of the Gaelic Highland culture, such as the tartan, the kilts, and the bagpipes, but that is all very superficial in the context. If you check out some Lowland Scottish regiments such as The Royal Scots or the King's Own Scottish Borderers, you will discover that their history is not quite as Scottish as you would think. In fact they were never Scottish enough to be allowed to wear kilts. At Edinburgh Castle they always wore tartan trousers as opposed to kilts. 109.152.248.204 (talk) 13:21, 15 December 2014 (UTC)
IP 109.152.248.204, as I have pointed out on article page, there is nothing anachronistic about stating Maxwell's citizenship as British. The word citizen is defined as "A legally recognized subject or national of a state or commonwealth, either native or naturalized." which fully encompasses the situation as it stood in Maxwell's day. You cannot just ignore the proper meaning of a word to suit a desire to restrict its use. In the same way you do not need to redefine "nationality", it has a perfectly established meaning as "The status of belonging to a particular nation". With regard to the specific case of Scotland, we know that Scotland is a nation, and has been for over 1000 years. I have referred already to the former Prime Minister's speech which referred to: "whether Scotland is a nation; we are, yesterday, today, and tomorrow", that view is clearly shared by the current Prime minister who has said in a pre-referendum speech: "This is a decision that could break up our family of nations, and rip Scotland from the rest of the UK.". Even Simon Heffer, no fan of Scotland, repeatedly describes Scotland as a nation when writing in the Daily Mail! Note, none of these three eminent people could in any way be described as Scottish nationalists, but they all recognize the status of Scotland as a nation. The long standing status quo in the James Clerk Maxwell article properly and accurately represents Maxwell's status as a British Citizen (Subject) having Scottish nationality. These are facts, everything presented against the status quo is merely opinion unsupported by relevant sources. The boxes in question are "Nationality" (nowhere in the template information is that defined as having the restricted meaning of "sovereign nationality") and "Citizenship" (nowhere in the template information is that defined as having a restricted meaning of excluding the status of "subject"). It is not good practice in a discussion such as this to attempt to redefine words to a specific meaning which suits your personal PoV, provide no references which would support that view, and then go on to conduct your case based on that idiosyncratic interpretation. I wonder why you are even continuing to press this PoV when on the Maxwell article talk page you have already volunteered your acceptance that "Attempts to define nationality at the village pump failed". FF-UK (talk) 15:40, 13 December 2014 (UTC)
I'm not redefining any words. I'm going by the words used in the law. See here https://www.gov.uk/types-of-british-nationality/overview Maxwell was a British national under both today's law and the law of his own time. So how can you argue that we should put Scottish nationality in the info box as opposed to British nationality? Either put both or do away with the nationality field altogether. Is it not enough for you to have him described as Scottish in the main body of the text? And why do you want to describe him as being a British citizen when under the law at the time he was a British subject? Is it because you think the term 'British citizen' makes it look as though he wasn't really British, but only British on paper? You can use a dictionary to prove that nationality and citizenship mean the same thing, but why not stick with the usages that are actually in use in the context according to the law? Why would you have to call Maxwell a British citizen when he was a British national in law? And why would you call him a Scottish national when he is also a British national? Why would you deny calling him a British national when he was a British national? 109.152.248.204 (talk) 17:44, 13 December 2014 (UTC)
  • As a North Briton, I want to make clear that it is wrong to be trying to parse out ethnic definitions of "Scottish", "English", &c. One simply won't get anywhere if one tries to define a "Scottish" ethnicity. There is no coherent Scottish ethnicity, no more than there is a coherent English ethnicity. Britain has had so much movement, migration, invasion, &c. that all groups are heavily diluted and jumbled. Britons do not think in terms of ethnicity when they say that someone is "Scottish" or "English". People do not refer to David Cameron is Scottish because he has Scottish ancestry, nor do they call Her Majesty a Scot because her mother was Scottish. Applications of "Scottish" and "English" are cultural and geographical, rather than based on ancestry. People that have lived in Scotland all their lives but that speak with old-fashioned upper-class accents are often not considered "Scottish" by many Scots. These people might be just as "ethnically" Scottish as anyone else, but their cultural origin is in the highly anglicised Scottish upper class, which people perceive as apart from Scotland even though it has been part of Scottish society for centuries. In other words, one simply cannot think in terms of ethnicity when thinking about how to label Britons. One must go based on what reliable sources say, self-identification, and, failing those, pure citizenship. RGloucester — ☎ 17:58, 13 December 2014 (UTC)

I just wish to add to the statements suggesting that this is simply the wikipedia version of a wider effort by UK Unionists to remove as many cultural and national references to Scotland as possible in the wake of the recent independence referendum. It is couched in friendly language, referring to neutrality, and somehow suggesting that this is a broader concern globally rather than focused precisely on the Scottish situation... but as the conversation has progressed, it is bluntly clear that this is about Scotland and the continued assault on Scottish identity by British unionists. As this matter is (despite the fervent wishes of the unionists) still a highly contentious live issue within Scotland and the wider UK, I do not believe that it is appropriate in any way to make a formal ruling in this way; not least one that enforces a colonial position. FDCWint (talk) 22:07, 14 December 2014 (UTC)

It's quite likely that some editors feel there's a devolutionist agenda behind opposition to usage of British/United Kingdom, in these UK bio articles. IMHO, it's best that both sides refrain from accusing each other of political PoV pushing, as such mud-slinging will only cause the discussion to turn ugly & unproductive. GoodDay (talk) 16:25, 15 December 2014 (UTC)
Whilst I can see your point, the fact is that the IP Address 109.152.248.204 has essentially contributed nothing to Wikipedia other than to crank this particular issue; every contribution in their history is either on this topic, or badgering anyone who has disagreed with them with messages on their talk page - yours and mine included. If there were voices on that side of the debate who were actually engaged with the site in other capacities, it might be easier to accept a more noble motivation. FDCWint (talk) 21:36, 16 December 2014 (UTC)

I'll rephrase the question: what are readers interesed in see in the infobox? Several foreign-born Hollywood and Miami residents have American nationality. But I wouldn't be interested to see that a certain actor or sports competitor is American - Hélio Castroneves is Brazilian and Hugh Jackman is Australian. That's what the infobox should say. I guess that's what we call nationality, rather than citizenship. --NaBUru38 (talk) 18:03, 17 December 2014 (UTC)

Nationality Tutorials

In response to editor KTo288, I would say that at the moment of writing, the Andy Murray article is done correctly, whereas the Gerard Butler article is done wrongly. There is always a common sense way to do these things, where controversy may arise. Perhaps a wiki-Nationality tutorial class should be set up with worked examples. Let's take Samuel Cunard as an example. I would say that his article is correct as it stands. Nova Scotia was a British colony and a British settlement in Cunard's time. It only federated with Canada two years after Cunard's death. Cunard was born to British parents and was ethnically British himself. Canadian nationality only came into existence in 1921, while Canadian citizenship only came into existence in 1947. As far as I am aware there have been no attempts to ascribe Cunard with Canadian citizenship, but if such attempts were to be made in the future, as could well happen, I would say that they would be misinformed. It would be an attempt to stamp an identity upon a historical person, which that person would never have related to. Likewise every subject can be dealt with using common sense. In Tesla's case, he straddled many fault lines, but looking now at his article (Nikola Tesla), it appears to me to have been done correctly. His national identity is covered in the lead while his locations and citizenship are covered in the info box. There does however appear to be a gap in the info box for the post 1867 Austro-Hungarian Empire period. In modern day cases where an ethnic minority grouping is hostile to the political status quo, then you describe them in the lead according to their preferred designation, avoid nationality in the info box, and simply state the place of birth, using the name of the country as per the existing boundaries. Eg. Mr X is a Kurdish engineer. In the info box, avoid nationality and simply state Born:- Ararat, Turkey. What you should never do is promote in the info box an aspiring nationality that supports a separatist cause, such as Scottish. It's either British or nothing, while Scottish can be used in the lead. 109.152.248.204 (talk) 15:34, 14 December 2014 (UTC)

My point is that through collaboration we are getting it right more often than not, without the need for edicts on how to do this. In contentious cases we are achieving a consensus which the majority of editors can put their names to. The compromise of not stating a nationality, just a place of birth, with details in the lede, is a good one. However for compromises to work they have to be agreed upon and accepted by thos in dispute, not imposed on by decree.--KTo288 (talk) 20:33, 15 December 2014 (UTC)
No, that is OR. We cannot make up nationalities based on collaboration. Maybe we should change the word, but we should have a way of simply stating the independent state to which a person legally belongs. Looking at the 'Oppose' responses above it seems that many editors are wishing to make some political point through the nationality field in an infobox. This seems to be more and more how WP works. Editors here are to be arbiters of the truth rather than writing facts; we are now to decide the political divisions of the world. Martin Hogbin (talk) 11:05, 16 December 2014 (UTC)
The state the person belongs to is called "citizenship". The word nationality can mean either citizenship or ethnicity, so to avoid confusion we should report citizenship and/or ethnicity and avoid the confusing term "nationality".“WarKosign” 11:46, 16 December 2014 (UTC)
No, that is not so. Citizenship implies right of abode. I agree with using a clear and well defined term but unfortunately 'citizenship' is not it. Martin Hogbin (talk) 13:23, 16 December 2014 (UTC)
I do not understand your point. Of course (normally) a citizen of a certain state has the right of abode in that state. Other people who are not citizen may have right of abode as well, but it's beside a citizenship which is a specific legal relation between a person and a state that can be described in an infobox.“WarKosign” 07:15, 17 December 2014 (UTC)
Citizens have a right of abode and a right to participate in the political life of the state (e.g., to be elected to Parliament). Nationals may have neither of these rights. Both nationality and citizenship are separate, specific legal relationships between a person and a state. WhatamIdoing (talk) 21:21, 17 December 2014 (UTC)
Delete the field

When in doubt, throw it out. We should delete the Nationality/Citizenship fields entirely, as I rarely see them being used in non-UK bio infoboxes. I see no reason for giving the UK bio infoboxes special treatment. GoodDay (talk) 14:19, 16 December 2014 (UTC)

I agree. There is no general agreement amongst editors what the field represents so how can we expect our readers to know what we mean. Martin Hogbin (talk) 14:26, 16 December 2014 (UTC)
Anyone reading a box which says English will understand that the person comes from England. That is not too difficult. FF-UK (talk) 15:36, 16 December 2014 (UTC)
Or that it's an Englishman who lives in China.“WarKosign” 15:38, 16 December 2014 (UTC)
The birthplaces are already mentioned in the infoboxes, therefore the nationality/citzenship fields are not necessary. The UK doesn't deserve special treatment. GoodDay (talk) 15:40, 16 December 2014 (UTC)
That is exactly the problem. It is not clear what the 'nationality' field is meant to mean. It seems that FF-UK want to use it to show where a person 'comes from', whatever that means. Martin Hogbin (talk) 16:50, 16 December 2014 (UTC)
A term in an info box should always have a readily understandable meaning for the benefit of the readers. It appears that those who have opposed making the definition clear, want to be able to decide nationality based on consensus. That does not make for a reliable encyclopaedia. Either define it or delete it altogether. Defining or deleting it, it doesn't matter which, makes it more difficult for editors to abuse it. Those who want to retain it, and in an undefined state, clearly have an agenda. They see that an undefined nationality field provides them with the opportunity to put distorted information into articles under cover of consensus. 86.129.126.155 (talk) 18:16, 16 December 2014 (UTC)
I support deleting the field. Many countries that traditionally used "nationality" are getting away from this practice. The only place "nationality" exists is in a person't passport. It's not clear how this is determined. If a child is born to parents of different nationalities, how is the child's nationality determined, especially if all three are citizens of the same country? This is an arbitrary designation that doesn't belong in an encyclopedia. USchick (talk) 18:34, 16 December 2014 (UTC)
Does anyone have an idea of how many different kinds of infoboxes this might affect? I've seen the problem arise in articles about historic people using infoboxes such as {{Infobox writer}} (which has nationality, citizenship, and ethnicity fields) in cases where the nation in which they born and lived has ceased to exist and become something else or changed names, especially when the change has political or ethnic implications. Also, if there's a serious desire to eliminate those fields, the attempt is going to have to be more formal and better publicized than just this discussion (and I wouldn't give a nickle for its chance of succeeding even with that formality and publicity) as there are too many vested interests in particular infoboxes for a general discussion here to satisfy everyone without that. Regards, TransporterMan (TALK) 19:02, 16 December 2014 (UTC)
You are right about vested interests. It seems that everyone wants to own the good and great. Martin Hogbin (talk) 19:18, 16 December 2014 (UTC)
Wikipedia:Ownership of articles is against policy. If a Wikipedia tool serves no other purpose, perhaps it's time to get rid of it. I bet someone really smart could get a bot to do this. USchick (talk) 19:53, 16 December 2014 (UTC)

I would support this proposal, but only if you take the rest of the person-infobox with it.Volunteer Marek (talk) 20:10, 16 December 2014 (UTC)

Martin, while I don't disagree with you, that's not quite what I meant: I simply meant that the people who regularly use, for example, {{Infobox writer}} may have a completely different feeling about and put a different strength of importance on the nationality and citizenship fields than those who use, say, {{Infobox scientist}}. Regards, TransporterMan (TALK) 22:00, 16 December 2014 (UTC)
I would bet that the field is still used and fought over so that various factions can claim ownership of the good and the great. My original point was simply that this field should be reserved for something well defined, and understood by our readers. As it is now, and looks to remain, the field can indicate an undefined melange of legal nationality, citizenship, ethnicity, workplace, birthplace, self-identity, and stuff that, 'everybody knows', decided on a case-by-case basis by the editors that happen to be involved with the article. Martin Hogbin (talk) 23:16, 16 December 2014 (UTC)
If you delete the field, then how will you handle the thousands of people who are nationals but not citizens? These people are not stateless; they're just not citizens. Since this applies to biographies of long-dead people, please note that this status encompasses a large fraction of articles about people before the 19th century, including nearly all women in history. WhatamIdoing (talk) 21:24, 17 December 2014 (UTC)
National and Nationality are two different things. To complicate things further, different countries have different laws about "nationality" and some countries don't recognize it at all. So how can we expect to resolve these issues in an info box? By deleting this very ambiguous term, it doesn't take anything away from the person at all. It's still the same person, but without an ambiguous label. The only way to verify it is to look at their passport. Can we do that? USchick (talk) 21:37, 17 December 2014 (UTC)
If you have American nationality, you are an American national. If you are an American national, then you have American nationality. They aren't "two different things". (The word nationality gets used for multiple things, just like the word tissue does, but that doesn't mean that a national does not have nationality.) WhatamIdoing (talk) 21:56, 17 December 2014 (UTC)
That may work in America. Not in other countries. USchick (talk) 20:56, 22 December 2014 (UTC)
USchick, I would be very interested in seeing an example of this. Please tell me: For what country is it possible to be a national of that country, but not have that country's nationality? NB that I'm talking about the legal type of nationality, of the sort used in this treaty, which defines the term this way: ""nationality" means the legal bond between a person and a State and does not indicate the person's ethnic origin". Please give an example of a person having that particular kind of legal-not-emotional "nationality" for a country without also being that particular kind of legal-not-emotional "national" for said country. WhatamIdoing (talk) 00:19, 25 December 2014 (UTC)
If you have an Italian-American or a Chinese-American person, clearly "American" is the citizenship. How would you name their property of being Italian or Chinese ? Many people call this nationality, while others call the citizenship nationality. There is a lot of confusion over these words, so it is much better to use unambiguous terms such as birthplace, ethnicity and citizenship instead of the vague "nationality". “WarKosign” 11:25, 23 December 2014 (UTC)
You describe such people as being ethnically Italian or Chinese. In other contexts (e.g., the census), you might describe them as being racially white or Asian. They stopped being Italian or Chinese nationals when (if) they formally severed ties with their country of origin. If they never did that, then you can identify the as being Italian and American, or Chinese and American, with the legal connection to the two countries being co-equal. WhatamIdoing (talk) 00:19, 25 December 2014 (UTC)
Is this a European Union treaty? There are countries in Europe that are not part of the EU, like Eastern European countries that used to be part of the Soviet Union. You were a "national" of the Soviet Union (or any post-soviet country) and had your "nationality" listed in you passport as something different. A politician in Ukraine had this issue come up early in their campaign and it was a very big deal for the rest of their political career. Yulia Tymoshenko her father was a Soviet national and "His Soviet passport gave his nationality as Latvian." Yulia Tymoshenko#Family and personal life. Anyone in the Russian Empire was a Russian national, but their "nationality" was assigned to them and often it wasn't "Russian." A Jewish person in the Russian Empire and in the Soviet Union had "Jewish" assigned to them as their "nationality" and there was no way of getting out of it. I don't know how many post -Soviet countries still follow this system today. In Eastern Europe this is a very big deal even now. Unless you can look it up in each individual passport, there's no way of knowing. A passport is a primary source, and Wikipedia policy leans toward secondary sources. I hope that helps to explain it some. USchick (talk) 03:47, 25 December 2014 (UTC)
Latvia is (and was nominally, even under the USSR) a sovereign nation, so that's not an example of someone having Latvian nationality without being a Latvian national. (It wasn't technically possible to be "a Soviet national"; you had to be a national of one of the members of the USSR. It also wasn't possible to have "a Soviet passport", because they were issued by each of the member states, not by the USSR itself. He presumably had a Latvian passport that was issued while Latvia was a member of the USSR.)
Your Russian examples are using nationality to mean ethnic origin, not to mean a legal bond between a person and a nation for international/diplomatic purposes. It's true that the "fifth record" of the internal passport was labeled "национальность", which literally translates as "nationality", but it actually meant and was used for "ethnicity", which is why "Jewish" was a possible answer. (I've read that this conversation would be easier in German, because they have completely separate, unrelated words for these concepts, and don't have a bad habit of using the neutral-sounding "nationality" when they mean "ethnicity".) WhatamIdoing (talk) 20:54, 26 December 2014 (UTC)
I support this proposal; I don't see what these fields actually add to the articles, apart from giving insiders something to argue over. If someone's nationality or citizenship is really interesting enough to discuss, it should be done in the article itself. Lankiveil (speak to me) 11:00, 23 December 2014 (UTC).
That is absolutely right. The main purpose of the nationality field in bios is for various factions to calim ownership ofthe good and the great.
De jure nationality is well defined but not that important or interesting. Martin Hogbin (talk) 10:11, 29 December 2014 (UTC)
Require strict sourcing

If this proposal is defeated, as looks likely, all statements of nationality will be in limbo with no clear meaning for the word 'nationality'. Deleting the field from infoboxes is problematic and unlikely to succeed. I therefore suggest that we revert to the most basic principle of WP and requite strict sourcing for any infobox nationality that is in the least bit contentious. By strict sourcing, I mean a good quality, unbiased, reliable source which actually makes the statement that XXX has YYY nationality. Statements that XXX was a Londoner, New Yorker, Cornishman, or English are not sufficient, we must find a source specifically stating the nationality of the subject. No source; no nationality.

This new proposal is stricly in accordance with the most basic WP policy and is the only way that I can now see of making the 'nationality' field meaningful. Martin Hogbin (talk) 16:37, 17 December 2014 (UTC)

Wikipedia already has a rule to that effect. It's been in existence about as long as Wikipedia has. We don't need new rules. It's always been that every statement of fact should be verifiable. --Jayron32 03:24, 18 December 2014 (UTC)
I am not proposing a new rule but it has often been assumed that nationality in uncontentious so that many statements of nationality are unsourced. As it is quite clear from this RfC that statements of nationality are highly contentious, we have no option to apply standard WP policy on the subject, which is that without a reliable source we cannot make a statement of nationality. Martin Hogbin (talk) 09:10, 18 December 2014 (UTC)
Sounds good. So if a source such as this says "All though everyone in the UK has a British citizenship they have different nationalities" this is what we write. And since these sources say James Clerk Maxwell's nationality was Scottish, this is what we write. “WarKosign” 12:18, 18 December 2014 (UTC)
You are joking of course. You have cited a junior school web page as a source on nationality. You should read WP:RS before making any further suggestions. Martin Hogbin (talk) 12:39, 18 December 2014 (UTC)
Did you also Google for 'British' nationality? There are quite a few sources giving his nationality as British. AS the sources do not agree we should not give any nationality. Martin Hogbin (talk) 12:44, 18 December 2014 (UTC)
It has probably slipped Martin Hogbin's attention that sources rarely make definitive statements in the form "John Bull has English nationality", the normal form is something like "John Bull was English". This is equally true within WP articles. It is from within the body of the article that the précis that we call the infobox gleans its facts. Is Martin Hogbin really suggesting that only the precise form "John Bull has English nationality" is acceptable as a WP source? If so, then that specific proposal needs to be tested by a separate RfC, and not as yet another twist to this failing proposal that Nationality should have a specific meaning on WP as opposed to its generally understood meaning, which is the one described in dictionaries. FF-UK (talk) 13:51, 18 December 2014 (UTC)
"Nationality" has two different meanings in dictionaries. Real life is not so simple as those who write encyclopedias would like. The shortest yet completely accurate encyclopedia would be much larger than all the encyclopedias in the world; it would have to be housed on another planet. Richard Gill (talk) 11:47, 26 December 2014 (UTC)

The problem here seems to be two fold... 1) There is a lot of (perfectly understandable) POV pushing when it comes to nationality... editors who themselves identify with a particular nationality want to claim notable people as "one of us". It makes them feel proud. However, 2) we have to remember that notable people can have multiple nationalities... for example, someone who was born of Irish Parents, lived in London until age eighteen, but then moved to Edinburgh when he spent the rest of his life... Is that person Irish (based on parental heritage)? English (based on birth place) or Scottish (based on where he spent most of his life)? That is a situation where "British" seems appropriate. But now change that to French parents, born in London, moved to New York... There is no unifying term like "British"... so is the person French, English or American? You can make a good argument for each... and you can also make a good argument for all of the above or for none of the above. I tend to lean towards the later... nationality is not always clear cut. And when it isn't clear cut, often the best (most neutral) answer is to simply omit mentioning the subject's nationality completely. If you don't mention it, there is nothing for the POV pushers to argue about. Blueboar (talk) 16:55, 24 December 2014 (UTC)

But if the "Nationality" field in the infobox is taken to mean here – as it does in most places – the state of which the person in question is a citizen/subject/whatever, the discussion is simple in 99% of cases. There is consistency in meaning and the classification is easily and definitively determined and verified. It's what we have now, where it seems "Nationality" can mean whatever individual editors on individual pages want it to mean, including sometimes the broader concept more often known as "National Identity", that is precisely what leads to arguments: sources will always differ and/or describe the same person in multiple ways, and the individuals in question themselves might assert multiple and/or different identities from day to day. I've seen far too many pages where editors say "here is one source that happens to describe person A as being XX-ish; XX is, according to this other source, a nation in one sense of the term; hence person A is of XX-ish nationality". And then suddenly that trumps and excludes any other description, whether complementary or contradictory, and is what goes in the infobox, simply because it suits the editor to fix on that one option. It renders the information meaningless and WP a playground for utterly trivial nationalism. N-HH talk/edits 22:00, 24 December 2014 (UTC)
It would be great if those contributing to this discussion could inform themselves of the differences between nationality and citizenship before commenting. --John (talk) 22:47, 24 December 2014 (UTC)
Agreed. Reading British nationality law would be a good start. Martin Hogbin (talk) 10:48, 29 December 2014 (UTC)
Nationality of people from the United Kingdom

As so much of this discussion centres on the situation regarding Wikipedia:Nationality of people from the United Kingdom then I suggest that all of those taking part could usefully familiarize themselves with that. It is a distillation of the outcome of previous discussions which can found at Wikipedia talk:Manual of Style/Biographies/2007-2008 archive: British nationality. FF-UK (talk) 13:51, 18 December 2014 (UTC)

Do please read this essay but also look through the associated talk pages, as I have, to see how few of the editors supported what is said. The essay is nothing more than the views of a handful of editors on the subject. Martin Hogbin (talk) 17:37, 28 December 2014 (UTC)
Admit that the word has two meanings

Try looking up the word "nationality" in a dictionary, and read the wikipedia article Nationality. The word has two common meanings. (1) a legal meaning, namely that of being "subject" of a "nation state". (2) an affective (emotional) meaning, the "tribe" you associate yourself with (by birth or by adoption). Hence many people have several nationalities. I propose that we admit that the word can have different meanings, and that a person can have two different nationalities at the same time (or more than two): their nationality "de jure" and their nationality in an affective sense need not coincide. Notice that the word "nationality" only exists with these modern meanings (and has always had both these meanings) since about 1830. The nation state was a nineteenth century invention, and according to some, a disastrous invention. Labelling people by nationality is about power, about asserting power or ownership. Richard Gill (talk) 11:43, 26 December 2014 (UTC)

This is a very good point and it leads to a simple conclusiom. We cannot have a single field in an infobox just labelled 'Nationality' because nobody will be able to tell what kind of nationality it refers to.
Suggestions to improve this would be:
1) Remove, or at least leave blank, the field.
2) Have one field and call it 'Nationality de jure'. A more general discussion of the subject's nationality could be put in the text, if this is considered important.
3) Have two fields: 'Nationality de jure' and 'Nationality something else. Martin Hogbin (talk) 17:45, 28 December 2014 (UTC)
As I've previously proposed, go with option #1. The vast majority of bio articles don't use them. GoodDay (talk) 17:51, 28 December 2014 (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.

Minor Change to CSD:G13

This a recommendation for a minor change to the Speedy Deletion guideline G13. It concerns the deletion of abandoned AfC's. A note should be included that a bot edit for adding the page to a category should not reset the 6 month time period. A bot edit does not show that the article is not abandoned therefore should not reset the time. EoRdE6(Come Talk to Me!) 01:10, 8 January 2015 (UTC)

Oppose and Speedy Close to refer the discussion back to Wikipedia:Administrators'_noticeboard#Category:AfC_submissions_with_missing_AfC_template where the best place to discuss AFC involved procedures should start. User should not be rewarded for WP:FORUMSHOPing around to get their PoV to win. Hasteur (talk) 03:53, 8 January 2015 (UTC)
This was created long before your post at AfC, so actually you are the one forum shopping. So I suggest closing the AfC forum, and keeping the main discussion at AN. EoRdE6(Come Talk to Me!) 04:12, 8 January 2015 (UTC)

Please move your discussion to the newly created conversation at WT:CSD as requested by an admin. Thanks! EoRdE6(Come Talk to Me!) 05:08, 8 January 2015 (UTC)

Format of titles on a Talk Page

I posted this question at the following Help Desk: Wikipedia:Help desk#Format of titles on a Talk Page. (You can see the discussion there.) I was directed to post it here, on this page. The question is: Is there any rule, policy, or standard regarding the format of a title of a Talk Page? I have always assumed that it is supposed to mirror the actual article title, with the word "Talk:" preceding it. So, for example, see this Talk Page: Talk:List of The King of Queens episodes. Are the words "The King of Queens" supposed to be italicized or no? I am referring to the Talk Page, not the actual article page. Thanks. Again ... some discussion has already ensued on this topic at Wikipedia:Help desk#Format of titles on a Talk Page. Joseph A. Spadaro (talk) 17:49, 9 January 2015 (UTC)

I oppose any mass effort to insert such display titles onto talk pages. If in a few articles you are working on, it makes you feel better, fine. But as any kind of a standard practice, no. -- TRPoD aka The Red Pen of Doom 18:24, 9 January 2015 (UTC)
Thanks. And what is your reason/rationale? Joseph A. Spadaro (talk) 18:32, 9 January 2015 (UTC)
Talk pages are not articles. It is not necessary to bring them to article standard. --Redrose64 (talk) 23:34, 9 January 2015 (UTC)
Clearly, I realize that Talk Pages are not Article Pages. What is the "harm" in doing it correctly? What is the argument against accuracy? I still am not sure what the argument/logic/reason is? Thanks. Joseph A. Spadaro (talk) 23:43, 9 January 2015 (UTC)
Aren't there enough arguments over trivia without introducing yet another point? Make-work proposals to add tags or change talk-page titles are unlikely to assist the encyclopedia. Johnuniq (talk) 23:51, 9 January 2015 (UTC)
(different comment) When you say "doing it correctly" this implies there is a standard ... and there is not. Also, the only "harm" I see arising would be the implication that there is a standard, leading others to draw time away from encyclopedia development to address perceived stylistic concerns on non-article pages. --User:Ceyockey (talk to me) 23:54, 9 January 2015 (UTC)
Yup. Unless the talk page title is actually misleading (which a mere lack of italics clearly isn't) there is no merit in tinkering with it - and it can be irritating to people who have pages watchlisted. AndyTheGrump (talk) 00:00, 10 January 2015 (UTC)
Alright. Let me ask the question another way. If I change it to italics and another editor keeps changing it back, what should I do? Joseph A. Spadaro (talk) 00:13, 10 January 2015 (UTC)
Say "I don't give a fuck" and move on. Oiyarbepsy (talk) 00:16, 10 January 2015 (UTC)
Per WP:BRD, you should do one of the following.
  • Try to gain consensus for the change on the talk page. If unable, gracefully move on. Or,
  • Decide that you have better things to do with your time on Wikipedia. ‑‑Mandruss ☎ 00:17, 10 January 2015 (UTC)
Yup. Find something more f-----cking important to fuss over. AndyTheGrump (talk) 00:19, 10 January 2015 (UTC)

Thanks. Apparently, that other editor stop reverting the edit. So, apparently, it's become a moot point. Thank you. Joseph A. Spadaro (talk) 21:22, 10 January 2015 (UTC)

Style for Hebrew calendar dates and conversions

On a bunch of articles of biblical figures such as Reuben (Bible), I've found dates formatted for example as "14th of Kislev(November 16)". I put a space in front of the open parens, making "14th of Kislev (November 16)". Is the first a special style for dates in the Hebrew calendar with conversions, or should I carry on? If there is a relevant guideline for alternate calendars and date systems in general, please point me to it. --Anon423 (talk) 18:39, 9 January 2015 (UTC)

Well as written it doesn't make sense. In order for the 14th of Kislev to correspond to November 16th, it would have to specify a year, which would be even more important than the day/month of the Western Calendar.Naraht (talk) 20:02, 9 January 2015 (UTC)
Also all of the places that I found them are done by one IP user (197.242.127.193) so I'm going back and removing them all (and at least one, the western month day *never* aligns with the jewish month and day.)Naraht (talk) 20:10, 9 January 2015 (UTC)
Thanks for the reply. I'd originally been made aware of those articles by changes to various articles for days in the year, such as November 16, where the same IP editor had added those biblical figures under their Gregorian birthdays. After seeing you'd reverted the date conversions on the pages of biblical figures such as Levi, I went and reverted those additions on the days of the year as well. That should take care of all that user has erroneously done. --Anon423 (talk) 08:10, 10 January 2015 (UTC)

Banning policy and IAR

This is something I’ve wanted to post for a long time, but have never gotten around to it until now. I guess I was just worried about being seen as a “bleeding heart” towards banned users. In my view, site bans are unevenly enforced. I’ve seen banned editors have their new accounts exposed, only to be allowed back onto the project after a community discussion (with mixed results). Conversely, I’ve also seen editors blocked indefinitely with widespread community support at AN/ANI, despite making nothing but positive contributions, solely because they were banned.

Consider this scenario: an editor first registers an account on Wikipedia at 13 years of age. They make some productive edits, but are ultimately too emotionally driven to be a collaborative presence on the project. It is later discovered that they were operating a massive sock farm to carry out all sorts of nastiness: vandalism, trolling of the most heinous variety (death threats, ethnic slurs, legal threats, fake suicide threats, etc), attempting to “out” a contributor, etc. They were indefinitely banned. After six or so months of continuous activity and trolling, they stop editing altogether. One year later, they register a new account and begin making constructive contributions. This time however, there is no trolling or anything of the sort; they are simply a productive editor. In fact, they have become a very prolific member of the community, racking up thousands upon thousands of edits and making significant contributions in their areas of expertise (be it article writing, RC patrol, volunteering at the help desk, or anything else of that nature). After ten years of uncontroversial editing, their prior identity is revealed.

My questions are as follows:

  1. Would the correct course of action be to immediately block them indefinitely (talk page access revoked, email disabled, autoblock enabled) and place a sockpuppet notice on their userpage? Does the block of a long-term, prolific contributor for ban evasion warrant a post to AN or ANI? If so, would you be inclined to support a (renewed) community ban?
  2. Should this user be forced to undergo the standard offer, or appeal their ban via the ban appeals subcommittee?
  3. Would their age at the time of the original ban be considered a mitigating factor? Does their recent history largely invalidate their troubled past, or does it demonstrate contempt for the community and its rules?
  4. Given the nature of their past activities (death threats, outing, massive sockpuppetry, etc), can an unban ever be considered a possibility?
  5. Assuming you feel that this sort of editor ought to be blocked, should more efforts be undertaken by the community to identify and expose these sorts of ban evaders wherever possible, as a means of holding them accountable for their past actions?

The overarching question is – where do we draw the line? Can IAR be applied to banned users? Kurtis (talk) 13:43, 4 January 2015 (UTC)

Well... my first reaction would be to question the likelihood of your scenario... leopards don't change their spots quite so quickly. Someone who was as disruptive as you present is unlikely to completely change their ways after just one year.
But (to play devil's advocate) - let's amend your scenario to a slightly more realistic one... a 13 year old kid is banned for highly disruptive editing... and stays away for 5 years or so. He does a lot of growing up during those years, and now realizes that his prior behavior was wrong. Now, at 18, he is starting college and signs into Wikipedia (under a new identity) and constructively edits from then on.
Chances are, no one is going to notice (or care). It is extremely unlikely that anyone would discover his prior identity ... because he is not giving anyone a reason to even wonder whether the two identities are connected. The issue of his prior identity is simply not going to come up, unless he mentions it himself (again unlikely).
OK... let's say he does mention it... first it would be a very WP:DICKish thing to report him, given the behavior of his new identity. I would say that (in this very unlikely scenario) we should invoke IAR and simply "forgive" the banned editor his youthful transgressions. Blueboar (talk) 15:00, 4 January 2015 (UTC)
Hmm, I disagree about the "leopards not changing their spots quickly" thing when it comes to adolescents. You'd be surprised - I find that kids mature very fast in a short amount of time. ;)

Otherwise, I agree with the points you've made. I do not think the banning policy should be a suicide pact, and IAR should apply in those sorts of cases. That's just my opinion, though. I'd imagine some people would disagree with me, and their reasons would likely be valid. Kurtis (talk) 15:37, 4 January 2015 (UTC)

I would say that if a user who was site-banned is capable of making thosands of edits with a new account, over several years, without anyon e suspecting them - that probably means that the ban is no longer necessary. Add the age of the user at the time of disruption - and no action could possibly be necessary. Bans, like blocks, are preventitive, not punitive - and I doubt that even Grawp ould be denied an oter chance of the community could be convinced that he will behave. עוד מישהו Od Mishehu 22:22, 5 January 2015 (UTC)
What if they invented a flying car? Would you still drive it? What if we collected 20 years of checkuser information? What if we could use checkuser information to fuel flying cars? This whole scenario is terribly convoluted. Some of our members hold long grudges, but I don't think that if the last transgression is more than five years ago and there has been a lot of good behaviour since has been shown many would still care so much that they believe the user should remain banned. I do believe we should all move on - but this kind of situation would be so rare that we should probably look at it case by case. Martijn Hoekstra (talk) 16:31, 6 January 2015 (UTC)
Hypotheticals, Martijn. Hypotheticals. ;) Kurtis (talk) 17:54, 6 January 2015 (UTC)
For the record, I would definitely drive a flying car fueled by checkuser information. bd2412 T 21:26, 8 January 2015 (UTC)
I think it would be a grossly irresponsible use of IAR to allow back a banned user who engaged in making death threats. There is a line and terrorizing our users crosses that line. Such a user should be blocked for block evasion if they come back. The standard offer makes it very clear that it is not for anything serious such as something you would involve the police over. Death threats means no standard offer. Chillum 22:03, 8 January 2015 (UTC)
Does it make a difference if we're talking along the lines of fake death threats (i.e. blatant trolling), as opposed to legitimate threats of violence? Kurtis (talk) 17:51, 10 January 2015 (UTC)
Such cases seem to be sufficiently rare that they can be handled as they are now: on a case-by-case basis. Circumstances vary so much from one banned individual to the next (consider the elaborate baroqueness of the hypothetical scenario we've been given) that trying to create a firm rule now will either result in an unsatisfactory outcome when we try to apply it, or require us to create a complex and over-engineered policy to try to capture every single possible hypothetical. And even an over-engineered and hyper-detailed policy might still break down when today's hypothetical discussion crashes into real circumstances (and an evolved community) some years in the future. Finally, building an extremely specific framework and ruleset now invites wikilawyering and targeted gaming of those rules later. TenOfAllTrades(talk) 22:53, 8 January 2015 (UTC)

In the hypothetical, (A) yes it would be dickish to report them but there are dicks around, and (B) the reformed ed you describe likely has the maturity to just accept the nuisance of formal appeal, and (C) if the community is unable to welcome the reformed person back, then that would be a sign our dysfunction has finally gotten the better of us. I prefer to keep hope alive and trust the rest of you. In the death threat example, I prefer to apply the US standard - innocent of crime until proven guilty, and no double jeopardy. In the scenario presented, should a prolific contributor who has atoned wear a millstone of shame until they die? Sanctions should be preventative, not punitive. However, a key point of your example worth emphasizing is that they returned in a single guise. That's very different from an IP hopping sock. Both should have to go through the process of formal return, but the former's history shows a lot more respect for the community than the latter. NewsAndEventsGuy (talk) 18:16, 10 January 2015 (UTC)
If the question being asked here is' Can IAR be applied to banned users?' the answer is self-evidently yes - that is what 'ignore all rules' means. As to whether it should, it will clearly depend on particular circumstances, and since the discussion here relates to an entirely hypothetical situation, there is nothing to be gained in debating how to handle this particular imaginary scenario. I can seen nothing in this discussion that amounts to evidence that we have any specific problem: instead there seems to be an assumption that Wikipedia policy has to cover every possible future hypothetical scenario. That is simply not the case. We are here to build an encyclopaedia, not to construct a Byzantine system of rules and regulations just for the fun of it. AndyTheGrump (talk) 18:18, 10 January 2015 (UTC)
"We are here to build an encyclopaedia, not to construct a Byzantine system of rules and regulations..." Too late! NewsAndEventsGuy (talk) 22:09, 11 January 2015 (UTC)
  • The scenario I've created was more or less a means in which to gauge multiple different variables that would be taken into consideration when debating whether or not an editor should be blocked for ban evasion. Specifically, it considers the user's age, the offences for which they were banned, the amount of time that has elapsed, and their contribution history to date. The intention was to gauge where the community stands on the issue of ban evasion when mitigating factors are considered, and to see if the policy as it is currently should be revisited. I'm inclined to agree with AndyTheGrump and TenOfAllTrades that creating a "one size fits all" solution or a complex set of guidelines would be too bureaucratic for something which is best handled on a case-by-case basis. Kurtis (talk) 18:40, 10 January 2015 (UTC)

Changing templates

I raised the following issue at Wikipedia talk:WikiProject Classical music: The two templates IMSLP and IMSLP2 were nominated for merger. Someone put a notice at the top of the template that the templates were up for merger. Now, everywhere the template appears, it includes that notice. Like this:

Free scores by Beethoven at the International Music Score Library Project (IMSLP)

I asked that the notice be moved so that it does not appear in article space, and was told that this was policy.

It seems that, if this is policy, it is one of the more idiotic ones I have encountered. I would guess that at least 50,000 people or more read articles with those two templates every day; of those, maybe one or two are interested in a technical discussion about merging templates; the others are simply confused by an irrelevant message.

If this really is the policy, it should be changed forthwith. If it is not the policy, could someone please remove this ridiculous message from article space? Thanks, --Ravpapa (talk) 06:28, 7 January 2015 (UTC)

I now see that the same thing happens with {Template:Infobox musical composition}. --Ravpapa (talk) 06:38, 7 January 2015 (UTC)
What is your alternative plan to advertise mergers and deletions? --  Gadget850 talk 10:51, 7 January 2015 (UTC)
I hadn't really thought about it. It seems pretty silly to advertise mergers and deletions to a vast audience of people who have absolutely no interest, and who don't even know what a template is. Wouldn't it make more sense to post notices on the relevant project pages, and at Wikipedia:Templates for discussion? People who are interested in technical issues like these probably watchlist those pages.
Imagine if, every time there was a technical issue in Unix, all the Unix users all over the world got a message, "We are considering a change in the salamander widget. All users are invited to voice their opinions." What are normal users - secretaries, businessmen, students - supposed to think of such a message? --Ravpapa (talk) 12:06, 7 January 2015 (UTC)
See also Wikipedia_talk:Templates_for_discussion#The_majority_of_deletion_and_merger_proposals and Wikipedia_talk:Templates_for_discussion#Can anything be done?. I personally support wide advertisement of discussion. I don't really have a preference for where this discussion is held, but consolidating it to a single venue is better than the fractured discussion that is arising now. Martijn Hoekstra (talk) 13:38, 7 January 2015 (UTC)
  • As long as some TfD nominators refuse to notify major template contributors and active WikiProjects about the proposed deletion or merge of templates within their scope, there is no alternative. In the absence of direct notice of concerned parties, this is how most concerned editors learn that a TfD is pending; both the template to be merged and the surviving must be noticed. Ironically, some TfD nominators, perhaps from ignorance, also fail to properly use the TfD notice template options, effectively placing the TfD notice template at the top of every article where the subject template is transcluded -- the ugliness complained of above.
Several regular TfD participants are fond of saying that TfD "is an invitation to discuss the template"; well, it's rather difficult to have a good-faith discussion about merging or deleting a template when most of the concerned editors and WikiProjects aren't even aware of the pending TfD. Not tagging the subject templates and not notifying the major contributing editors and WikiProjects is horrible practice. And, yes, the failure to consult and notify is one of the principal reasons for the increasingly hostile atmospherics of TfD discussions (that and the snarky "we know better" comments from some regular TfD participants). Like a handful of other "specialist" backwaters, TfD discussions too often devolve into a series of personalized arguments between a handful of regular participants and those editors drawn to the discussion by the particular topic under discussion. The failure to consult and properly notify the concerned editors and WikiProjects only exacerbate the perception that some regular TfD participants are determined to achieve their desired deletions and merges with the minimum discussion possible with template stakeholders. Dirtlawyer1 (talk) 15:28, 7 January 2015 (UTC)
To those advocating the hiding or removal of these messages, I refer you to the answer that I gave ten months ago. The discussion was moved to this page a few hours later, and may now be found here. --Redrose64 (talk) 15:44, 7 January 2015 (UTC)
  • Redrose64, to me, there is a fundamental difference between that discussion and this one where-as that discussion was whether or not deletion notifications should be hidden from readers and this one is about whether or not merge notifications should be hidden from readers. Some may ask, what is the difference. Deletion means it is gone, no substitute, it will no longer be available and this effects readers as much as editors. Merge means that the functionality of the template will still exist, just as a part of another template. The reader doesn't see any difference in the end result in these cases, and should not be burdened with having to read about them all over the place. To be clear, my position on hiding deletion tags has not changed, the outcome of those discussions effect everyone. That said, I support hiding merge messages from readers. — {{U|Technical 13}} (e • t • c) 16:14, 7 January 2015 (UTC)
Some merge discussions end up with massive loss of functionality. Somebody once told me that "once a template is at TfD, all options are open". That may even mean that a discussion initially proposing a merge closes as "delete". BTW a bit off topic, but relevant to a thread from a few days ago - if you (Technical 13) follow the diff link that I gave, you'll find immediately above my post, Legoktm asking for RfCs not to be conducted on VPT, so I'm not the only one. --Redrose64 (talk) 16:35, 7 January 2015 (UTC)

Well, I had no idea this was already a topic of discussion. When I first saw the notice (and I am a pretty experienced user, both editorially and technically), I assumed this was a bug. Now that I have read the discussion, I realize that, like in the old joke about Microsoft, this is not a bug but a feature. I guess some people think this message adds something valuable to my user experience when I am reading about Beethoven's Grosse fuge. So, I'm kind of sorry I brought it up.--09:47, 8 January 2015 (UTC)

I share Ravpapa's concern with this 'feature', and I note and agree with Technical 13's comments. So, er, how do we take this further?--Smerus (talk) 10:40, 8 January 2015 (UTC)
We need to increase participation at TfD, not decrease it. Other relevant threads have taken place at WT:TFD, and include: Wikipedia talk:Templates for discussion/Archive 14#Make notifying significant editors of deletion mandatory (4 August 2013), and Wikipedia talk:Templates for discussion/Archive 15#Discussion to add instructions to use "noinclude" tags for highly-visible templates (24 April 2014). IIRC others have occurred on this page, at WP:VPR, and at WP:VPT; possibly elsewhere. --Redrose64 (talk) 11:10, 8 January 2015 (UTC)
Redrose, you may well be right about increasing participation, but advertising the issue to hundreds of thousands of people, none of whom care and none of whom have the least understanding of what you are talking about, does not seem a reasonable way of increasing participation.
But rather than just be negative, here is a suggestion: why not have a checkbox in the user preferences that says "I am interested in seeing technical messages"? Then display those messages only to users who might be interested? You could even display them more boldly, because you know people who are seeing them have actually asked for them. I realize this would involve a bit of work on the part of you tech honchos, but it would address notification only to those users who would be likely to participate in a discussion. Otherwise, what you are doing is like putting a billboard for ice machines in Alaska. --Ravpapa (talk) 12:14, 8 January 2015 (UTC)
Dreaming up solutions is still much better than throwing our hands up in the air. The main problem with notification of template discussion we have in my perception is that we have no good way to notify interested parties, since nobody who uses template x also watches template x (for some reasonable approximation of nobody). The only way we currently have is the invasive tagging of both pages, and displaying the notification to everybody. So I boldly created a bugreport: T86159. Don't expect this to be fixed tomorrow, but at least it's now brought to attention. For now however, I still think we definitely shouldn't do anything that decreases the visibility of discussions on template. Martijn Hoekstra (talk) 12:33, 8 January 2015 (UTC)
The bug received the priority "Needs volunteer" which means that it is unlikely that it will receive much attention any time soon (unless someone here jumps in. Any takers?). Don't expect this to be done tomorrow now means don't expect it the day after tomorrow either. Martijn Hoekstra (talk) 09:47, 9 January 2015 (UTC)
  • Martijn, I'm actually quite surprised it wasn't closed as invalid or wontfix. — {{U|Technical 13}} (e • t • c) 13:49, 9 January 2015 (UTC)
    Why? Martijn Hoekstra (talk) 14:43, 9 January 2015 (UTC)
    • Because in general, Martijn, the people watching a page aren't going to want to watch the dozens or hundreds of templates and meta template that are transcluded on those pages. Carrying out that request will quickly change people watching 100 pages into people watching 2,000 pages and those watching 2,500 pages into ones watching 50,000... It's overwhelming and unwelcomed. — {{U|Technical 13}} (e • t • c) 18:17, 9 January 2015 (UTC)
      Hmm, I doubt that that's true and overwhelming. I'll query some. Martijn Hoekstra (talk) 18:36, 9 January 2015 (UTC)
      • Querying 10 random articles...
        1. Woodsmoke and Oranges - Transcluded templates (31)
        2. Rex Lassalle - Transcluded templates (8)
        3. The Lure of the Big Game - Transcluded templates (26)
        4. Wągrowiec - Transcluded templates (82)
        5. Androka - Transcluded templates (56)
        6. Lauro Kurtz Airport - Transcluded templates (58)
        7. 1999 ASB Classic – Singles - Transcluded templates (70)
        8. Jesse James Garrett - Transcluded templates (27)
        9. Matt Cepicky - Transcluded templates (31)
        10. Zaprešić - Transcluded templates (105)
      • This is an average of 49.4 templates per page. So, a person with those pages would have a total of 504 pages on their watchlist instead of the 10 they selected; a person with 100 pages, would have about 5,040; a person with 2,500 would have about 126,000; a person with 10,000 would have about 504,000. That is why I'm surprised it wasn't quickly shot down as no way in heck... — {{U|Technical 13}} (e • t • c) 19:12, 9 January 2015 (UTC)
        I suspect many of those templates are duplicates, and many of templates receive far fewer edits than the articles. I'll let you know when my queries finish. Also, the bug report is "better template watching", not necessarily watchlisting in this way, though it was my first suggestion. Martijn Hoekstra (talk) 19:35, 9 January 2015 (UTC)
        My current watchlist contains 5,894 plus talk pages. A total of 14,977 unique pages are transcluded from those pages. 7,906 of those are in template space; most of the non template space ones are process pages like AfDs which are transclued on the date page. That comes down to a little more then one template per page on average. It'll take me a little longer to get the recent edit counts, but I suspect that these will be far lower for templates then for articles. Martijn Hoekstra (talk) 19:56, 9 January 2015 (UTC)

A better software change is on the watchlist star, an option "Watch this page and all transcluded templates" and also "watch this page and all subpages". This would provide the same benefit Martin's proposed change does, without burdening those who don't want to see the templates. Oiyarbepsy (talk) 00:22, 10 January 2015 (UTC)

Excellent suggestion! --Ravpapa (talk) 06:42, 10 January 2015 (UTC)
In that case, Wikipedia:Village pump (proposals)#Better watch list options Oiyarbepsy (talk) 07:24, 10 January 2015 (UTC) Pinging @Ravpapa:, and spelling the name correctly this time Oiyarbepsy (talk) 07:25, 10 January 2015 (UTC)
I'm working on a JS userscript proof of concept technical doohicky for this. This is compounded by me trying to write javascript without actually having learned javascript or knowing javascript well, so it's taking a little longer than I would have liked. Martijn Hoekstra (talk) 16:07, 10 January 2015 (UTC)
This is coming along well. I would use this feature. I note that templates on a page can change, meaning the button will need to be reclicked afterwards to watch the new templates. Also, it will be quite hard to unwatch in bulk: If a template is removed from a page, all other pages on the watchlist will need to be checked before unwatching automatically. —PC-XT+ 23:17, 10 January 2015 (UTC)
Ha, you'd be sorely mistaken! The fact of the matter is that I'm starting to believe that one of the design goals of JS was to annoy me to the greatest possible extent. I think I'll have something bad in about two days, after which I'll recruit more help making it not bad. Martijn Hoekstra (talk) 12:27, 12 January 2015 (UTC)
Martin, please continue discussion at the topic I opened and linked to above. Everything since I posted that topic qualifies as off-topic here. I noted there that the watch all templates option needs to be dynamic, which I seriously doubt you can do with a javascript routine. Oiyarbepsy (talk) 15:33, 12 January 2015 (UTC)
This must be the discussion with the most severe case of wanderlust Wikipedias history. As a side note, whatever I make as a userscript for myself or for demonstration purposes as a proof of concept needn't anything, other than meet my own expectations. Martijn Hoekstra (talk) 16:02, 12 January 2015 (UTC)

A Wikipedia hosted alternative to current reliance on outside email

Wikipedia has clear policies on such things as WP:CANVAS and yet it provides an email service via Special:EmailUser. It even provides the Template:You've got mail. Once this has been used and personal details have been swapped there can be no end of conferencing, planning and requesting of support and I do not think that this is the way things should be in our encyclopaedia. I was wondering if there might be any way of developing a Wikipedia based system within which messages could be sent privately but in a way that would leave an information trail in case there was a need for information to be checked by an authorised person? GregKaye 20:02, 8 January 2015 (UTC)

  • I would tentatively support such a thing, but I am a bit concerned that if Wikipedia were to offer a semi-private mail function, there would be efforts to hack it and liabilities where those efforts succeeded. bd2412 T 20:23, 8 January 2015 (UTC)
  • Making a centralised information trail in case there was a need for information to be checked by an authorised person sounds like something the NSA/GCHQ/etc. would have orgasms over. Not that they can't already hack people's emails, but conveniently storing all communications by Wikipedians in a central database? BethNaught (talk) 20:36, 8 January 2015 (UTC)
  • Oppose Waste of resources; what's to stop anyone from just publishing an e-mail address on their user page? Or any number of other methods (some people already link to a Facebook profile, etc.). Orange Suede Sofa (talk) 20:37, 8 January 2015 (UTC)
  • Oppose per above by BethNaught and Orange Suede Sofa. And because I'd be very wary of setting up a system which allowed such messages to be read by 'authorised persons' unless there were stringent checks and balances involved - which I doubt that the WMF would want to get involved in. AndyTheGrump (talk) 20:44, 8 January 2015 (UTC)
  • This sort of already exists. The actual text of the email isn't stored, but sending an email is stored with checkuser results. The recipient is also stored, encrypted, but I don't think there's anywhere in the CU interface it's actually accessible, so it would require a WMF employee with database access to retrieve it (I think the purpose is mainly for dealing with threatening or otherwise illegal emails rather than canvassing). Of course this, and the proposal here, are fairly trivial to get around, per Orange Suede Sofa. Mr.Z-man 21:03, 8 January 2015 (UTC)
I think that GregKaye needs to clarify whether the proposed 'information trail' includes the contents of communications, or just the identities of the sender and receiver. AndyTheGrump (talk) 00:16, 9 January 2015 (UTC)

I think I could be okay with the information trail if its use was highly restricted, such as to oversighters only, for example. Oiyarbepsy (talk) 05:06, 9 January 2015 (UTC)

  • Oppose vehemently: I don't like other people reading my private communications, especially "authorized" people. When countries do that kind of thing, it has a name. --Ravpapa (talk) 09:47, 9 January 2015 (UTC)
  • Oppose As others have pointed out this only works if the content of the messages are stored and also only if it actually prevents off-line communication which it doesn't. Finally Wikipedia is not a social network and the presence of a full blown semi-private chat system seems like it would be easily abused in an area outside Wikipedia's remit with all the other costs involved ( especially those for dealing with complaints about messages, threats etc. that would surely happen under a general messaging system ). PaleAqua (talk) 17:27, 9 January 2015 (UTC)
  • oppose in any cost - benefit ratio this is a pure loser all around and it will not prevent the issue it seeks to curb anyway. -- TRPoD aka The Red Pen of Doom 18:30, 9 January 2015 (UTC)
  • Comment I think this is a fairly moot proposal as there is already logging that can only be accessed by WMF staff that are granted with access to email information by going directly through the server. Now... If this proposal was to have WMF host it's own webmail service (since there are issues with sending mail through the system to multiple free email clients Phab:T66795), then I would expect to see some support of that. — {{U|Technical 13}} (e • t • c) 19:17, 9 January 2015 (UTC)
  • Comment from nom, I don't understand the objections to the idea in principle. Whatever Wikipedia says in regard to the things that it claims that it is not, Wikipedia is an anarchy. All of its rules are determined by consensus sans any arch leadership and the auspices of inter wiki communication would be no exception. In most circumstances there would be no need to check communication and, in situations where editors stuck to guidelines based activities, I can't imagine that there would be any need to. However, in situations in which activities such as canvassing or incitement were suspected, I think that it would be reasonable for posts to be looked at by consensus by a specifically authorised admin who could then report back on or declare contents as relevant. No user need have automatic access to content. GregKaye 18:53, 10 January 2015 (UTC)
You may be happy with admins reading private conversations - it appears that others here aren't. They are appointed by the community to carry out publicly-visible functions, and can be held accountable for such. Having them delve into matters where nobody can see the evidence is outside their remit, intrusive, and open to abuse. And in any case, given that contributors wishing to engage in canvassing etc can quite easily do so through other means, the proposal singularly fails to solve the problem it purports to address. AndyTheGrump (talk) 19:17, 10 January 2015 (UTC)
AndyTheGrump It is not that I am happy about admins reading private conversations. I am unhappy that there are private conversations and further that there is no visible trail to indicate that these conversations are occurring. This flies in the face of other areas of policy. GregKaye 12:14, 11 January 2015 (UTC)
There is no Wikipedia policy whatsoever against contributors having private conversations - and if there were, I would cease to have anything whatsoever to do with the project. This is an online encyclopaedia, created by volunteers.It is not a fucking police state. AndyTheGrump (talk) 14:44, 11 January 2015 (UTC)
Greg, your proposal reveals a fundamental misunderstanding of the right to privacy. A communication is considered private if a user has a reasonable expectation that the channel she is using is private; to read or eavesdrop on that communication is a violation of the fourth Amendment of the US Constitution. A user of a Wikipedia email system would certainly have such a reasonable expectation, and the communication is therefore inviolate. If Wikipedia were to eavesdrop on a conversation on its email network, it would be violating the law, and subject to a suit in torts. See, for example, Expectation of privacy, Email privacy, United States v. Councilman (specifically relevant to this idea). --Ravpapa (talk) 14:41, 11 January 2015 (UTC)
Ravpapa Not at all. Perhaps there could be a feature by which an editor can leave a transparent talk page edit that would send an email to a user saying that direct communication is desire and that an email address is requested. The other editor could then transparently respond in a process that would give the email address and then it would be known that the two editors were capable of off site communication. GregKaye 14:51, 11 January 2015 (UTC)
Or maybe Wikipedia could transparently mind its own fucking business. AndyTheGrump (talk) 14:54, 11 January 2015 (UTC)
Then perhaps I didn't understand your suggestion correctly. I thought you were talking about creating a Wikipedia-hosted alternative to email, where users could exchange messages with a reasonable expectation of privacy, but that certain Wikipedia officials would be authorized to examine those emails, thus violating that privacy. That is precisely the scenario which is forbidden by United States v. Councilman. Isn't that what you are talking about? (and incidentally, publishing the fact that authorized people could scrutinize your presumed private communications would not in any way mitigate the reasonable expectation of privacy). --Ravpapa (talk) 07:09, 12 January 2015 (UTC)
  • Support I am a bit in two minds about this but at the moment it is too easy for people to pass their own email address back when replying to mail on Wikipedia rather than doing it via wikipedia. I have no problem with Wikipedia storing the mail if a big warning is given when the mail is started, I think in fact it is a good way to stop its abuse. The alternative is for Wikipedia to just completely remove its support for email. Dmcq (talk) 19:18, 11 January 2015 (UTC)
    The problem there is that we have at least two processes that currently rely on email, for which a 100% secure alternative would be needed before we turned off email. The two that I am thinking about are (i) obtaining a new password if you have forgotten yours; (ii) filing a request for oversight. --Redrose64 (talk) 00:06, 12 January 2015 (UTC)
  • Comment - Talk pages are a great place to have conversations that other people can check. Adding <div style="display:none;"> to the top of your talk page should give it the same level of privacy as the proposal at hand. moluɐɯ 19:52, 11 January 2015 (UTC)

Date format.

Hi
However for several years I'm active on pl:wiki, here on en: I just put only the first steps. I don't want to fall into any conflict at the beginning, so maybe I will ask here first. My doubts concern date format. I've make some edits on Constitution of May 3, 1791 changing date format into the right one. Now the question is - what is the "right" date format. Although I know that american use mm/dd/yy format (even if I don't understand why) and (possibly) half of articles have this date format, I cannot agree with Constitution of May 3. The integral name of this document is Constitution of 3 (Third) May.
Maybe this is some Tilting at windmills, but it lead me to question - why and when mm/dd/yy format began to be used? I didn't find any answer in Calendar date, just that all standards point dd/mm/yy (of course in some variations - most important is day before month). It's free to use any format I want, while editing of creating new pages? In the past, I saw some edids, that convert dd/mm/yy into mm/dd/yy format. This format is most promoted?

Gregory --Blueye (talk) 10:33, 10 January 2015 (UTC)
ps. If I make glaring language errors, feel free to tell me that. — Preceding unsigned comment added by Blueye (talk • contribs) 10:29, 10 January 2015 (UTC)

For acceptable date formats see MOS:DATEFORMAT. Per Date format by country modern Poland and Lithuania use Day Month Year format, so per MOS:DATETIES the article should use that format. But MOS:DATEFORMAT does "not apply to dates in quotations or titles", thus if "Constitution of May 3, 1791" is the official title, then it should be used. But looking at the article history, there seems to be some editing on that; this need to be discussed on the article talk page, where there is discussion from 2012. --  Gadget850 talk 11:21, 10 January 2015 (UTC)
First and foremost, these date formats should be consistent with the article title, which remains in the mdy format. Given that such a change is likely to be controversial, I would suggest the following course of action.
  • Revert the changes you have made so far to the date format.
  • On the article talk page, request a move to change the article title to the dmy format. The article has 64 watchers, and a move request is automatically posted where it can be seen by the entire community, so you will likely get a healthy amount of participation in the discussion.
  • If the move request is successful, then make your format changes to the text.
  • If there is no consensus for the move, accept the community's judgment and move on.
For general discussion about the two formats, I would suggest Wikipedia:Reference desk/Miscellaneous. ‑‑Mandruss ☎ 12:24, 10 January 2015 (UTC)
This is one of the pedantically contentious problems that English Wikipedia is stuck with. You might also have a look at WP:Engvar where the same issue arises with spelling and other things.
Generally, use the style appropriate for the article and do not fight over it. Martin Hogbin (talk) 13:16, 10 January 2015 (UTC)
WP:Engvar has nothing to do with dates. MOS:DATETIES is the guideline. --  Gadget850 talk 14:48, 10 January 2015 (UTC)
I did not say that it did I merely pointed out a similar issue. Martin Hogbin (talk) 17:58, 10 January 2015 (UTC)
Also note that there is no comma in the dmy format. It would be 3 May 1791, not 3 May, 1791. ‑‑Mandruss ☎ 15:31, 10 January 2015 (UTC)

MOS:DATETIES only applies to topics with ties to an English-speaking country. The concept is that most of the readers of the article would be from the country the article is closely tied to, so most of the readers would be more comfortable with the date format in that English-speaking country. Since Poland and Lithuania are not English-speaking countries, we do not try to guess what format an English-speaking reader of an article about a Polish or Lithuanian topic would be most comfortable with; MOS:DATETIES does not apply to this article. Jc3s5h (talk) 18:10, 10 January 2015 (UTC)

Thank you all for reply and some advices. I will read all those guidelines. --Blueye (talk) 10:27, 12 January 2015 (UTC)
BTW Maybe this is some question with no answer, but why there are two main date formats? (mean day before month and oposite. Dont care about comas or dots - those are details) Is there any historical reasons? --89.71.65.202 (talk) 20:10, 12 January 2015 (UTC) (That was me --Blueye (talk) 20:12, 12 January 2015 (UTC) )
For general discussion about the two formats, I would suggest Wikipedia:Reference desk/Miscellaneous. ―Mandruss ☎ 20:15, 12 January 2015 (UTC)
(edit conflict) Because some of us are British and some are American, and ne'er the twain shall meet. You say tomato, and I say tomato. --Redrose64 (talk) 20:20, 12 January 2015 (UTC)
One of us is Dan Quayle. You say potato, he says potatoe. ―Mandruss ☎ 20:26, 12 January 2015 (UTC)

Requesting an editor to be banned when they are already blocked

I've seen recently a lot of editors nominating indef blocked editors to be community banned. The general reply is that there is no difference between the two and it is a waste of time. WP:BANBLOCKDIFF, which gets pointed to a lot, seems to say nothing on it being the same. In particular, it says that banned users are definitely not part of the community, while blocked editors are. It doesn't it mention it there, but the processes for appeal are harder for a banned user than one who is blocked. So: should we be requesting bans for editors who are indeffed? It ought to be clarified in policy some way. KonveyorBelt 02:19, 12 January 2015 (UTC)

The likely central point being intended is that a user whose main account is indefinitely blocked, and no administrator is willing to unblock that account, the user can be considered de facto banned. Martijn Hoekstra (talk) 14:47, 13 January 2015 (UTC)

Quotation marks in article DISPLAYTITLEs

Input would be much appreciated at Wikipedia talk:Article titles/Quote tags. Should <q>...</q> be encouraged in article titles as in Into the Dalek? —174.141.182.82 (talk) 21:09, 12 January 2015 (UTC)

Archived userfication discussion closed

Just a heads up that I have closed the proposal regarding elevation of WP:USERFICATION to guideline status. Sam Walton (talk) 23:39, 13 January 2015 (UTC)

WikiProject Women

Please see meta:Grants:IdeaLab/WikiProject_Women for discussion of a proposed place where "registered women editors may join the group and discuss Wikipedia related matters." NE Ent 19:48, 10 January 2015 (UTC)

I a bizarre move all of the opposition votes have been moved to the talk page. Does anyone know why this has been done? --Mrjulesd (talk) 13:24, 13 January 2015 (UTC)
@Mrjulesd: That's a question to ask at a page directly concerning the discussion, which is on meta:, not here - this thread is merely a notification. If you're interested, they were moved by Siko (WMF) (talk · contribs) contactable on meta: as Siko (WMF) (talk · contribs). --Redrose64 (talk) 14:59, 13 January 2015 (UTC)
I believe that ==Opposition== sections are never used at IEG; it's more like an approval voting system (to the extent that it's a vote at all, which it fundamentally isn't). In the instant case, if the goal is to find out who would voluntarily participate in a smaller, thematic community, then it really doesn't matter how many people would not participate (even after discounting the views by people who learned about this proposal at Reddit rather than by being part of the Wikimedia community). WhatamIdoing (talk) 00:11, 15 January 2015 (UTC)

Rules and policies for disambiguation pages

Where can I find the rules and policies for disambiguation pages? Specifically, I am interested in the rules for providing a parenthetical description of an individual. For example, if there are several individuals named "Robert Smith", they might be disambiguated with a parenthetical description that says "actor", or "singer", or "baseball player", or "politician", or "author", or such. Where are the rules for all that? I had assumed that these parenthetical descriptions should reflect the "status" or "job" or "role" of the person, as in the examples I gave. But, I ran across some that did not follow this method and used words such as "wrongful conviction", as in this instance: Ryan Ferguson (wrongful conviction). I would think a better parenthetical would be something like "convict", "prisoner", "ex-convict", "former inmate", or some wording that reflects his "title" or "role" (almost like a "job description"). A generic broad noun such as "wrongful conviction" seems to make no sense in "describing" the man. Thanks. Joseph A. Spadaro (talk) 17:32, 11 January 2015 (UTC)

Do you really think that it is possible to have hard and fast rules for every possible future article? And no, Ryan Ferguson (convict) is not 'better' - it is worse, since it omits the most salient fact about his conviction. AndyTheGrump (talk) 17:39, 11 January 2015 (UTC)
What the fuck kind of response is that? I came here, asking for help. Don't be an asshole. Joseph A. Spadaro (talk) 18:20, 11 January 2015 (UTC)
(1) I asked for direction to the pertinent Wikipedia policy page (which is the whole point of this Village Pump). And which you did not provide in any way, shape, or form. (2) Where did I state that it is possible to have hard and fast rules for every possible future article? (3) If "convict”" is not better, why is a similar articled disambiguated as Charles Hudspeth (convict), with exactly that same word, "convict"? Leave me alone, if you have no intention on helping with what is a reasonable and appropriate question for this page. Joseph A. Spadaro (talk) 18:27, 11 January 2015 (UTC)
(after ec) I don't see that Andy's response call for that sort of accusatory reaction. The relevant guideline is at WP:NCPDAB. FWIW, I agree with Andy. This appears to be a person known primarily for the fact of being wrongfully convicted. "(convict)" is not better better because the person's notability is associated with his being wrongfully convicted. Perhaps Charles Hudspeth (convict) could have a better disambiguating term. older ≠ wiser 18:33, 11 January 2015 (UTC)
Very much like your recent thread, #Format of titles on a Talk Page, and many others in my experience with you. Frankly, your bedside manner sucks (as does Mr. Grump's a lot of the time, but that's no excuse), and if you keep it up the community will gradually stop responding to your questions at all. ‑‑Mandruss ☎ 18:35, 11 January 2015 (UTC)
Asking for direction is not what this Village Pump is for. The page starts: "The policy section of the village pump is used to discuss proposed policies and guidelines and changes to existing policies and guidelines". One of your examples is "baseball player" but we actually say "baseball". See Wikipedia:Naming conventions (baseball players)#Disambiguation. PrimeHunter (talk) 22:49, 11 January 2015 (UTC)
Hi I agree with Andy too. Because in my eyes the goal is to enable people to make a decision about which page to select as easy as possible. Therefore use the most prominent fact where the person is known for. This is also much easier for the contributor. — Preceding unsigned comment added by 83.160.83.146 (talk) 12:34, 14 January 2015 (UTC)
Ryan Ferguson (convict) would be a serious WP:BLP violation. He's not a "convict", i.e., a person whom the court believes has committed a crime; Ferguson permanently stopped being a convict the moment that the court vacated the conviction. He's the victim of a miscarriage of justice. Ryan Ferguson (proven innocent) would be much more appropriate. WhatamIdoing (talk) 00:19, 15 January 2015 (UTC)

Is this a valid usage of galleries per WP:GALLERY? (It is being aggressively added by two COI users, but this is a different issue).--Ymblanter (talk) 18:43, 11 January 2015 (UTC)

There is another one here and I guess in hundreds more articles.--Ymblanter (talk) 18:44, 11 January 2015 (UTC)
Yes I agree it is currently a misuse of a gallery and more suitable for wikipedia commons. It isn't too big and with a little work it might be possible to make it okay. What is really needed is some text underneath each picture saying what aspect of the topic it is illustrating, basically they should make a case for why they are there over and above just being nice paintings. Dmcq (talk) 19:08, 11 January 2015 (UTC)
I agree that what's needed is more compare-and-contrast sorts of information. I've got no problems with having half a dozen paintings of a town in the town's article, but it needs to be in a section that has actual content. I'll have a go at Staraya Ladoga to see if I can give an example that is clearer than what I've said here. WhatamIdoing (talk) 00:23, 15 January 2015 (UTC)
Okay, see Staraya Ladoga#Sights and landmarks to get an idea. It's not perfect, and I don't know enough about the subject matter to make it perfect, but it should give you the idea. There's a specific, labeled theme (churches that are landmarks) for the gallery and it's in a relevant section (the sections about landmarks). WhatamIdoing (talk) 00:42, 15 January 2015 (UTC)
Thanks, Dmcq and WhatamIdoing--Ymblanter (talk) 08:03, 15 January 2015 (UTC)

Redirects for plural nouns

I'm not an expert on policies and procedures, but there are, IMHO, problems if somebody is looking for the plural (of an animal, particularly, such as in names of sports teams) and they are redirected to the animal article (singular), which further directs them to a disambiguation page for the singular (which they don't want, of course, and which they therefore may just ignore), which is sometimes pretty long, and which may include, along with the many singular references, a few plurals. Coyotes is an example of this. It has about 75 entries(!), only 14 of which are for the plurals, and it isn't easy to find them (especially the Marine aviators).

Similar problems exist with Penguins, Lions, and Tigers, which are some sports teams I'm familiar with. Ravens handles it differently, but the disambiguation page doesn't even mention the bird or the other singular disambiguations. Eagles, IMHO, handles it the best -- searching for Eagles redirects you to Eagle, which has two hat notes: one directing to a disambiguation page for Eagle, and another to a disambiguation page for Eagles. Both pages have a lot of entries, and there isn't much chance of someone accidentally going to the wrong one.

IMHO, the Eagles style is the best, and would be good for Coyotes, with a separate ambiguation page for the plurals. Also IMHO, Ravens should be rejiggered to that format, as well. I can see the problems for users here, but my own skills are not great when dealing with redirects and disambiguations. Maybe somebody has some ideas on this. Lou Sander (talk) 16:34, 12 January 2015 (UTC)

I haven't formed an opinion on the method I prefer, but it's clear that our treatment of these situations is not consistent. There are at least three methods in use; for the sake of communication let's call them Coyotes, Eagles, and Ravens. It's worth reaching a consensus, codifying it somehow in a guideline, and fixing the deviants (I'm not terribly busy and could volunteer to assist in the latter). I'd also suggest that the scope isn't limited to animals, e.g. see Airplanes, an example of the Coyotes class. ―Mandruss ☎ 18:36, 12 January 2015 (UTC)
Note: While one could claim the usual need for flexibility, and some probably will, there are situations where the benefit of consistency outweighs the need for flexibility. I believe this is such a situation. And, as with any guideline, this wouldn't be a hard rule and could be deviated from when there is a compelling need to do so. I don't see a compelling reason why coyotes, eagles, and ravens shouldn't be handled in the same way, or airplanes for that matter. ―Mandruss ☎ 19:05, 12 January 2015 (UTC)
There is yet another form of this in use: searching for the plural Cardinals takes you directly to a disambiguation page for the singular Cardinal, which has links to articles involving both singular and plural forms of the word, but doesn't mention the plural forms at the top. Lou Sander (talk) 13:27, 13 January 2015 (UTC)
The thot plickens. ―Mandruss ☎ 13:32, 13 January 2015 (UTC)
There isn't a primary topic for Cardinal, so I suppose that linking the plural directly to the disambiguation page is a good move. IMHO the plural form should be mentioned at the top of these disambiguation pages, though (if the disambiguation items include plural forms). That would be an improvement in, for example Coyote (disambiguation) and Cardinal (disambiguation). Lou Sander (talk) 13:54, 13 January 2015 (UTC)
IMO, when there are multiple meanings for the plural, it should generally have its own dab page (such as Eagles); in cases like Cardinals and Giants, if the plural has no PTOPIC, then the dab page should be at the plural title - see Cubs and Senators as examples. עוד מישהו Od Mishehu 17:01, 13 January 2015 (UTC)
+1 → Od Mishehu --User:Ceyockey (talk to me) 00:32, 15 January 2015 (UTC)

By the way, here's an oter model to look at - Dodgers redirects to Los Angeles Dodgers, not to Dodger (an article, not a reirect or a dab). עוד מישהו Od Mishehu 18:33, 13 January 2015 (UTC)

Pen/Stage names vs real names in the body of the text

In the text of the article in our article on Mark Twain, we routinely refer to the subject by his pen name (as in "Twain grew up in Hannibal, Missouri" and "In 1847, when Twain was 11, his father died of pneumonia") and only mention his real name (Clemens) in passing.

However, in the text of our article on Deadmou5, we routinely refer to the subject by his real name (as in "Zimmerman was born in Niagara Falls, Ontario" and "In 2007, Zimmerman began his own record label") and only refer to his stage name (Deadmou5) in passing.

I don't really have a problem with the fact that the two articles do things differently... but it did get me wondering... Do we have guidance on this? Or is this the sort of thing that we leave up to editorial judgement and article level consensus? Blueboar (talk) 14:35, 13 January 2015 (UTC)

IMO, the key question is what the primary name of the person is. The lede should always start either "Real name (lifespan), better known as Pen Name", or "Pen Name (lisespan), born as Real Name" (or something like that); beyond that, COMMONNAME should be used unless there's a good reason not to. I'd imagine that the reason for Deadmou5's deviation from this, is that it would make the article less readable for someone who skips the lede. עוד מישהו Od Mishehu 17:11, 13 January 2015 (UTC)
Two big differences between these two examples. One, the name Mark Twain is extremely well-known worldwide, his works published in at least 72 languages. Deadmau5, not so much. Two, Mark Twain actually looks like a name rather than a username. As for guidance, I doubt it; a guideline would deprive us of something to argue about. ―Mandruss ☎ 18:34, 13 January 2015 (UTC)
Well... that holds true for the real names as well: "Samuel Langhorn Clemens" is far more widely known than "Joel Thomas Zimmerman" is.
I suppose my question comes down to this: both Mark Twain and Deadmou5 are the COMMONNAME for the respective article subjects... so it struck me as odd that one article uses the COMMONNAME in the text (and not the real name) while the other uses the real name in the text (and not the COMMONNAME). As I said, I don't have any real problem with the choice at either article, just wondering if there was a guideline or policy that expressed a preference on the issue. If it's the sort of thing we leave to editorial consensus at the article level, that is fine too. Blueboar (talk) 19:04, 13 January 2015 (UTC)
As I said, I doubt there's a guideline, but I'm prepared to be corrected. Btw, I note that you write "Mark Twain" correctly but require a redirect to avoid redlinking "Deadmou5", lending a wee bit of support to what I said about "Mark Twain" being more well-known. ―Mandruss ☎ 19:29, 13 January 2015 (UTC)
Re "Deadmou5" being a redirect... sorry, my error... I simply mistyped. I meant Deadmau5 (which is not a redirect). Blueboar (talk) 13:56, 14 January 2015 (UTC)
It's something it would be hard to make direct policy on: Consider, for example, George Elliot, Richard Bachman, Mark Twain, Barbara Vine, Pliny the Elder, Caligula Spy, John Wayne. I think that in four of those we'd be better using their psuedonym/nickname, one is a border case, one has his own article on the pseudonym and one on his real name, and one is best known by the pseudonym, but oh god would using it cause problems, and one of those - Ruth Rendell/Barbara Vine is a person who uses different names for different types of books, or did, anyway back when I last read her. I think you can decide which is which otherwise. One could also add Prince (or, worse, File:Prince_logo.svg), Madonna, and Cher.
It's hard to make policy on this, but I think we can still get through with a little common sense and rough guidelines. Barring another Chelsea Manning incident, anyway.
Of course, if you do have a good suggestion, by all means give it. I think George Elliot is the hard one of the list, as her pseudonym was primarily used in order to hide from prejudice against women, which leads to some harder questions. Adam Cuerden (talk) 20:17, 13 January 2015 (UTC)
OK... using common sense and allowing editorial preference at the article level works for me. As for suggestions... no. Trying to force some sort of consistency between articles would probably be a mistake here. This is probably one of those areas where it is best to be flexible. Thanks. Blueboar (talk) 13:56, 14 January 2015 (UTC)

As it happens there's already a truckload of guidance on this in WP:MOSBIO:

Applying MOS to filmographies, or not

We need a consensus at the filmography project regarding accessible tables with rowspan. Xaxafrad (talk) 06:19, 14 January 2015 (UTC)

@Xaxafrad: Have you informed WT:WCAG? --Redrose64 (talk) 10:42, 14 January 2015 (UTC)
No, but I will now. Thanks. Xaxafrad (talk) 20:59, 14 January 2015 (UTC)
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Village_pump_(policy)/Archive_117&oldid=1090621649"