Cannabis Ruderalis

Content deleted Content added
Cunard (talk | contribs)
Line 1,134: Line 1,134:


Perhaps it might be a good idea to write some guidance describing cases when a request for closure is or isn't appropriate? I'm only aware of [[WP:CLOSE#Which_discussions_need_to_be_closed]], which is quite vague. I'd also like to put in an argument for ''not'' de-archiving discussions, especially if the issue is contentious - a few days between the closure and post-closure discussion can make the procedure seem more measured and reduce the feeling of immediacy from editors who feel strongly about the issue. My feeling is to say that there's [[WP:NODEADLINE]], and if nobody ever checks, then the RfC question is probably no longer an important issue. [[User:Sunrise|''<b style="color:#F60;font-family:Times New Roman">Sunrise</b>'']] <i style="font-size:11px">([[User talk:Sunrise|talk]])</i> 00:06, 24 July 2015 (UTC)
Perhaps it might be a good idea to write some guidance describing cases when a request for closure is or isn't appropriate? I'm only aware of [[WP:CLOSE#Which_discussions_need_to_be_closed]], which is quite vague. I'd also like to put in an argument for ''not'' de-archiving discussions, especially if the issue is contentious - a few days between the closure and post-closure discussion can make the procedure seem more measured and reduce the feeling of immediacy from editors who feel strongly about the issue. My feeling is to say that there's [[WP:NODEADLINE]], and if nobody ever checks, then the RfC question is probably no longer an important issue. [[User:Sunrise|''<b style="color:#F60;font-family:Times New Roman">Sunrise</b>'']] <i style="font-size:11px">([[User talk:Sunrise|talk]])</i> 00:06, 24 July 2015 (UTC)

*WhatamIdoing has raised this issue repeatedly. Two previous discussions are [[Wikipedia talk:Administrators' noticeboard/Requests for closure/Archive 1#Cunard is still adding dozens of requests]] (July 2014) and [[Wikipedia:Administrators' noticeboard/Archive268#Severe backlog at WP:ANRFC]] (January 2015). In both discussions, I explained my closure requests in detail.<p>I think Scott summarized it very well at [[Wikipedia talk:Administrators' noticeboard/Requests for closure/Archive 1#Too many discussions being added]]: <blockquote> Lack of resolution to ongoing debates is a continuing issue on this project. If there are too many things listed here, it's because there are too many things left unfinished. It's a reflection of reality. As Cunard points out in his admirable response in the "September 2013" link above, not having a formal closure can also lead to misinterpretations (or deliberate ignorance) of consensus by persons in disputes, and not provide a recourse for editors attempting to enforce consensus. Having an accepted closure to point to will be immensely useful in many subsequent debates. We should encourage these. Making them is tough work, and I think that's what's putting editors off doing it, not seeing the number that need to be done.</blockquote> Robert McClenon, one of RfC's dedicated and hard-working closers, explained why formal closure of even seemingly "consensus is clear discussions" is helpful at [[Wikipedia:Administrators' noticeboard/Archive268#Benefits of Formal Closure]]: <blockquote>I have closed several RFCs where I thought that consensus was clear, but that required follow-up for either of two reasons. Either one of the posters ignored the consensus, in spite of the formal closure stating the consensus, or one of the posters objected to the close and requested that I re-open the RFC to allow them to insert a statement. When there was move-warring against consensus or edit-warring against consensus, formal closure put the enforcing administrator on firmer ground in enforcing consensus. Formal closure establishes what the consensus is, unless reviewed. Otherwise the resulting [[WP:ANI]] thread would itself have had to establish consensus before warning or blocking, causing drama on a drama board. In cases where I have been asked to re-open a closure, I have instead asked for closure review. Without closure and closure review, the most likely result would have been edit-warring.</blockquote> The recent backlog is because I did not update the closure requests list for around four weeks. (In the past, I updated it every two or three weeks.) In the past when a large number of requests has been added, the backlog has returned to a reasonable number within two weeks. [[User:Cunard|Cunard]] ([[User talk:Cunard|talk]]) 03:51, 24 July 2015 (UTC)


== RfC: On Software Notability. ==
== RfC: On Software Notability. ==

Revision as of 03:51, 24 July 2015

 Policy Technical Proposals Idea lab WMF Miscellaneous 
The policy section of the village pump is used to discuss proposed policies and guidelines and changes to existing policies and guidelines.
If you want to propose something new that is not a policy or guideline, use the proposals section.
If you have a question about how to apply an existing policy or guideline, try one of the many Wikipedia:Noticeboards.
This is not the place to resolve disputes over how a policy should be implemented. Please see Wikipedia:Dispute resolution for how to proceed in such cases.

Please see this FAQ page for a list of frequently rejected or ignored proposals.



MOS:IDENTITY clarification

As is to be expected, there's some issues brought up at Talk:Caitlyn Jenner on how to handle certain aspects of self-identity in Wikipedia articles. MOS:IDENTITY clearly indicates that in issues of self-identified gender, Wikipedia defaults to the most recently expressed wishes of the subject of the article. The question is, to what extent does MOS:IDENTITY apply. Does it apply only to the article about the subject, or does it apply Wikipedia wide, to every article, and in every context. The specific question came up with how to identify Ms. Jenner in regards to her participation at the 1976 Summer Olympics, she identified at that time as a male. We know that in the article about her, we use her preferred name and female pronouns throughout. The reasonable question becomes, in articles where the time period in question does not include the phases of her life where she self-identified as female, do we use her current identity or her historic identity? To put this up to a !vote:

Option 1)
  • In articles outside of the biography itself, the timeframe of which only covers the period when the person self-identified as one gender, with a particular name, default to the historic name and gender
Option 2)
  • In every article across Wikipedia, all mentions of the transgendered person should use their current name and gender identity.

I don't really have a horse in the race, but I wanted to see what the consensus was, so it could be clarified in the relevant guidelines and policies. --Jayron32 02:35, 2 June 2015 (UTC)[reply]

This RfC illustrates recent consensus (or lack thereof) about MOS:IDENTITY, it's worth giving a look. Diego (talk) 12:24, 2 June 2015 (UTC)[reply]

Adding a third and fourth option per suggestions in the general discussion below. They seem to be a viable compromises between options 1 and 2 above.

Option 3)
  • In articles outside of the biography itself, use the person's chosen name, but include previous name in parentheses if directly relevant or when discussing events for which the person was notable and known by their previous name (e.g., athletic awards) prior to name change. Example, in a list of Olympic gold medalists, the entry Caitlyn Jenner (then Bruce Jenner) would be used.
Option 4)
  • In articles outside of the biography itself, use the person's previous name, but include current name in parentheses. Would be used when previous name is relevant or listed in a historical context (e.g., list of sports awards). Example, in a list of Olympic gold medalists, the entry Bruce Jenner (now Caitlyn Jenner) would be used. (3 and 4 added by EvergreenFir (talk) Please {{re}} 20:32, 2 June 2015 (UTC))[reply]

Sorry for coming a bit late to this party but I added a fifth option down below:

Option 5)
  • #Option 5 (no new rule, treat on a case by case base): avoid a "one size fits all" solution for the subsidiary, event and overview pages mentioning the person exclusively in an earlier period: approach these in a case-by-case logic, exerting caution, good taste, editor discretion – for clarity: without amending or cutting back any of the existing rules like MOS:IDENTITY that seem to work fine in the surroundings for which they were devised. --Francis Schonken (talk) 20:39, 10 June 2015 (UTC); updated for clarity 08:03, 11 June 2015 (UTC)[reply]

Option 1 (preserve historic gender)

  1. Support - Thanks for starting this! I support this for historic purposes, such as athletic accomplishments, as well as for past relationships that are over (Kris Jenner was married to Bruce Jenner; she was not married to Caitlyn); but not for continuing relationships (ie Brody Jenner's parents are Caitlyn Jenner and Linda Thompson) МандичкаYO 😜 02:55, 2 June 2015 (UTC)[reply]
    To add on to Wikimandia (—МандичкаYO)'s point, something definitely needs to be done regarding the marriage aspect; see this edit, where Andreas11213 understandably stated, "This implies that she was in a lesbian relationship when she was in fact not. She was married to Bruce Jenner not Caitlyn Jenner." Flyer22 (talk) 04:48, 2 June 2015 (UTC)[reply]
    The major factor to consider with these other articles is that, as we do our best to get it right with Caitlyn Jenner, we must also get it right with Kris Jenner as this is also a WP:BLP. So on Kris Jenner's article, it would not be particularly fair or accurate to say her wife for 20 years was Caitlyn Jenner. That would be very misleading in a biography about her, because yes it does imply she was a lesbian, or she that knew Bruce identified as Caitlyn even though she claims she didn't, or any of of the complicated things that we have no business trying to work around. МандичкаYO 😜 05:01, 2 June 2015 (UTC)[reply]
    @Wikimandia: Kris Jenner's page would state that she was married to Caitlyn Jenner while she was living as a man. Ogress smash! 22:02, 3 June 2015 (UTC)[reply]
    That would be incorrect. It would also be incorrect to list "Caitlyn Jenner" as Brody's father. Kris and Brody might not support the use of female pronouns or "Caitlyn" to describe their husband/father respectively. There is no reason to favor Caitlyn Jenner's transition name and gender over the historical name and gender that they presented to other living people or where historical events make the name and gender relevant such as the winner of the Men's Decathlon and credits in movies long since finished. --DHeyward (talk) 10:52, 7 June 2015 (UTC)[reply]
  2. In general support but there are complications. Jenner's interview mentions being dressed in women's underclothes in the past when presenting as a male publicly, so there is the issue of what gender they considered themselves at what times. Gaijin42 (talk) 03:28, 2 June 2015 (UTC)[reply]
    Not really. We only deal with the public aspect that is covered by reliable sources. Most likely she identified as female from very early in her life and I've not seen anything mentioning a fluid gender where she identified differently. Regardless of what underpants she wore, she was publicly male, won the Men's Decathlon, played multiple male roles in media, fathered multiple children, etc, etc. Whether she wears boxers or briefs or can still pee while standing up is not relevant to historical and public facts. Nor is it relevant to current events where she identifies as female and her name is Caitlyn. --DHeyward (talk) 10:39, 7 June 2015 (UTC)[reply]
  3. Support - I think it would be silly to start listing "Caitlyn" as a medalist in the "Men's" event. Alternatively, in cases where it's ambiguous which is more appropriate, she can be listed as Caitlyn (formerly Bruce) Jenner? Just a thought. -War wizard90 (talk) 04:08, 2 June 2015 (UTC)[reply]
    Not sure where I stand yet, but could it not be listed as Bruce (now Caitlyn) Jenner? Vyselink (talk) 19:46, 3 June 2015 (UTC)[reply]
    It's called a "redirect". Ogress smash! 20:50, 2 June 2015 (UTC)[reply]
  4. Support - It makes no sense to refer to Jenner as a "she" when Jenner was legally a Male. — Preceding unsigned comment added by 2601:4a:101:8610:99fa:284d:2c1d:1380 (talk • contribs)
    'legally' is not the threshold under our policy around biographies of living people. To make it that threshold would be to draw an entirely uneven and artificial line (as well as a tremendously unfair one) Ironholds (talk) 07:26, 2 June 2015 (UTC)[reply]
    Should we base Wikipedia on legal definitions, then? A tremendous number of things would need to change. Also, which legal system did you mean? Ogress smash! 20:50, 2 June 2015 (UTC)[reply]
  5. Support - She's drawn her own line of demarcation for us. Before today, his accomplishments were as Bruce Jenner; from today onward, her life is as Caitlyn Jenner. --Drmargi (talk) 04:49, 2 June 2015 (UTC)[reply]
    Did she? Awesome. Just when I thought I couldn't like her more, she does that for us!!! МандичкаYO 😜 05:01, 2 June 2015 (UTC)[reply]
  6. Support obviously this may not apply to every case, but generally pre-Caitlyn Jenner articles and links should be Bruce Jenner articles, links, or accomplishments. That's what redirects are for. Fyunck(click) (talk) 05:19, 2 June 2015 (UTC)[reply]
  7. Support During the times of his major public appearances, the Olympics (and all of his athletic career) and all of his post athletic movie and TV career, and celebrity existence until 2015, HE was known as Bruce Jenner, performing in male roles and events. To ex-post facto refer to such a notable identity in a new transgendered identity is to go back and rewrite history. That is not wikipedia's role. In fact, we are specifically supposed to follow sources. The reporting of his accomplishments in anything written before 2015 refers to this individual in a male identity. Before we change every record of his appearance before 2015, somebody please show a source contemporary to those activities using the new female name. Its is clearly impossible because the name did not exist publicly until a few days ago, so all of this change to content is unsourced and against key wikipedia policy. That goes the same for any individual undergoing the transgender change. If they have a historical public identity, we should follow that up to the point in time they announced their change. Certainly we can cross link so we can see who they are now, but for example Chaz Bono was seen millions of American television viewers as Chastity. Bradley Manning is the name reported of the individual originally charged with espionage. These situations are confusing enough to follow, obviously beyond the norm. Repeating: To artificially rewrite history, against the reporting of sources is not wikipedia's role. Trackinfo (talk) 05:45, 2 June 2015 (UTC)[reply]
    Neither is deadnaming or denying a BLP's right to self-determination and self-identity, so your emphasis of male pronouns is unnecessary. I'd suggest revisiting it. Ironholds (talk) 07:26, 2 June 2015 (UTC)[reply]
    Support - Agree that it would be entirely confusing to refer to Caitlyn Jenner competing in male sports. Are we to assume that official Olympics records have been updated to change Bruce to Caitlyn? Seems very unlikely to me. I wouldn't see a problem with the form "U.S. track and field athlete Bruce Jenner (now Caitlyn Jenner) won the gold medal for decathlon, setting a world record of 8,634 points." That form could be mentioned in the guideline, but it should be a tentative mention. It should be clear that the new name may be shown following the then-current name, but that it's local discretion. And that form is much preferable to "Caitlyn Jenner (formerly Bruce Jenner)" in a male context.
    Additionally the question of which name to link when both are given is closely related to this question, is almost as important, and probably should be addressed in the guideline as well. "Bruce Jenner (now Caitlyn Jenner)" or "Bruce Jenner (now Caitlyn Jenner)"? Or, for that matter, "Bruce Jenner (now Caitlyn Jenner)"? This will be a battleground issue and will need resolving before long, but I guess we don't need to complicate this discussion further. ―Mandruss  07:33, 2 June 2015 (UTC)
    Moved to Option 4. ―Mandruss  22:12, 2 June 2015 (UTC)[reply]
  8. Oppose per WP:BLP - The concerns expressed at MOS:IDENTITY apply to all content about the person, not just the biography article, as being the safest with respect to protection of the living person. Talking about "the historic gender" or "historic identity" is one of those misconceptions that the rules in the guideline try to address - gender identity has a biological component, so self-identification is the most reliable source, and in transgender persons often goes all the way to when they presented a different public identity. If the problem is one of using female to someone competing in male disciplines, that can be explained by mentioning the fact that she's a transgender woman - which would be relevant in that context (Transgender in sports is a notable topic). I think using the name used at the time would be OK (in this case Bruce) as it was the name used for registration in the competition, but not using the male pronoun. See Wikipedia:WikiProject LGBT studies/Guidelines and the proposed Wikipedia:Naming conventions (identity)#Sex and sexual identities for criteria commonly used by the LGBT wikiproject. Diego (talk) 09:17, 2 June 2015 (UTC)[reply]
  9. Support - I also think War wizard90's additional idea is even better, listing in some cases "Caitlyn (formerly Bruce) Jenner". As currently in her article (and infobox) it would seem Caitlyn Jenner was married in a lesbian relationship, which is not the case. --Gonnym (talk) 10:04, 2 June 2015 (UTC) Moved to Option 4. --Gonnym (talk) 09:41, 18 June 2015 (UTC)[reply]
    You don't need to repeal MOS:IDENTITY to avoid that problem as this option proposes, just clarify the sentence. Diego (talk) 10:07, 2 June 2015 (UTC)[reply]
  10. Support using the Caitlyn name in some form in all body-text. For more constrained historical situations (tables, lists, etc) it may be better to use Bruce Jenner with a footnote (or similar) containing the new name and potentially a longer explanation. Stuartyeates (talk) 10:35, 2 June 2015 (UTC)[reply]
  11. oppose a blanket "preserve historical gender" as a clear conflict of Wikipedia:Manual_of_Style#Identity. But we do need to be clear about things - a Caitlyn - Kris Jenner marriage would still be illegal in about half the states. -- TRPoD aka The Red Pen of Doom 12:23, 2 June 2015 (UTC)[reply]
    @TheRedPenOfDoom:: legal standards may not be the best standard to use here, as even the law is not entirely clear on what happens assuming you are just talking about the US. Ogress smash! 21:52, 2 June 2015 (UTC)[reply]
    The legal implications are of a concern to us via BLP - implicating that living people were in a "same sex marriage" when such were illegal in all 50 states. -- TRPoD aka The Red Pen of Doom 22:20, 2 June 2015 (UTC)[reply]
    No offense, but this seems like concern trolling: how does this affect Wikipedia, exactly? You are suggesting a BLP about a living person can't state they were married and use pronouns because same-sex marriage was illegal? What does that even mean? What concern is that? Ogress smash! 21:59, 3 June 2015 (UTC)[reply]
    WP:BLP is quite clear that we do not propagate improper implications about living people. Making claims/implications that someone was in an illegal marriage is one of the many things that we should be quite concerned about. -- TRPoD aka The Red Pen of Doom 16:16, 6 June 2015 (UTC)[reply]
  12. Support for all historic cases. The person's name at the time of the event is the name that should be used in our articles. ¡Bozzio! 13:24, 2 June 2015 (UTC)[reply]
  13. Support using historic gender and name in articles talking about past events, although I like the idea of a parenthetical like, "Bruce (now Caitlyn) Jenner." For examples where we already follow this format see Metta World Peace formerly Ron Artest. When discussing his career prior to the name change is is referred to as Artest. After the name change he is referred to as World Peace. We should do the same thing with Jenner. When discussing his previous life and accomplishments, refer to him as a male named Bruce. When discussing her current life and accomplishments, refer to her as a female named Caitlyn. Explain the situation wherever clarification is needed. ~ ONUnicorn(Talk|Contribs)problem solving 14:57, 2 June 2015 (UTC) (Moving support to Option 4; since that's essentially what I'm arguing here.)~ ONUnicorn(Talk|Contribs)problem solving 18:17, 3 June 2015 (UTC)[reply]
  14. Support. Kris married, um, the other person when that person went by "Bruce", and they divorced while the other person still went by "Bruce". Kris was never married to the other person when the latter was known as "Caitlyn". To say that Kris married Caitlyn is like saying they are a lesbian couple, which is patently false and thus a BLP violation. Besides, it would be confusing to say, "Caitlyn competed in male sports". It just doesn't happen. Epic Genius (talk) 16:30, 2 June 2015 (UTC)[reply]
  15. Support. It is way too confusing and contradicts the historic reliable sources otherwise. I'm sure there will be exceptions, but the general rule should be to use the historic gender and name outside of the main bio article when referencing the past. Rreagan007 (talk) 16:50, 2 June 2015 (UTC)[reply]
  16. Oppose - MOS:IDENTITY is policy and specifies that we use the current gender identity throughout the article. The subject's preference overrides any and all arguments. WP:BLP does not leave us the option to choose this. Skyerise (talk) 16:52, 2 June 2015 (UTC)[reply]
    WP:SOURCE is also policy, a policy I would suggest is an even bigger policy. We have a dispute between policies and it should be settled by a discussion, and hey look at this, Here's a discussion. Your policy does not trump seeking a solution. As I suggest elsewhere, nobody can produce a historical source for the names and gender identity that were revealed later. In the case of Jenner, "Bruce" is documented winning the Olympic gold medal, "Bruce" was the celebrity, TV and Movie star. "Bruce" is in the opening credits of the Kardashians. Caitlyn appeared into the public's view of this individual in 2015. If Caitlyn is the chosen identity, it was not revealed to the public until 2015. Until that time, based on sources, we should not go back and rewrite information that is contradictory to the existing sources. To do so would be . . . what's the word? . . . its our favorite word on wikipedia: UNSOURCED. Trackinfo (talk) 08:45, 3 June 2015 (UTC)[reply]
    Trackinfo, like I noted in the second subsection, MOS:IDENTITY is a guideline; it's not yet policy, and might not be policy in the future. Flyer22 (talk) 01:07, 5 June 2015 (UTC)[reply]
    I'm not even sure the difference, though Policy sounds more important. Whatever hierarchical level, I have suggested on the Caitlyn Jenner talk page that this MOS needs to be revisited in light of the crazy effect its application is having. Trackinfo (talk) 06:20, 5 June 2015 (UTC)[reply]
    Trackinfo, WP:Policies and guidelines explains the difference. Flyer22 (talk) 11:15, 5 June 2015 (UTC)[reply]
    MOS:IDENTITY is NOT policy, it's only a guideline. That's even stated at the top of the page. --AussieLegend () 13:56, 6 June 2015 (UTC)[reply]
  17. Support for historical events per WP:V. The preponderance of reliable sources would say that Bruce won the decathlon, or married Kris, or won the "Associated Press Male Athlete of the Year", not that Caitlyn did. --Ahecht (TALK
    PAGE
    ) 16:54, 2 June 2015 (UTC)[reply]
    Note that the concerns of harm towards living people justify the exception to using the common name, as WP:BLP override other policies regarding the amount of detail from sources to use in such cases. Diego (talk) 17:12, 2 June 2015 (UTC)[reply]
    For my enlightenment, and possibly that of others, please explain how Ms Jenner will be harmed by our acknowledgement that she won gold in men's Olympics as Bruce, especially if we acknowledge her current name at the same time. Does avoiding harm mean the eradication of any mention that a man named Bruce Jenner ever existed? What policy support exists for that, that doesn't require a ton of subjective interpretation? ―Mandruss  17:34, 2 June 2015 (UTC)[reply]
    The problem is not in the verifiable fact that Jenner won the competition under the name of Bruce (nor hiding that fact is mandated by the guideline); the problem is using the male pronouns "he, him" on someone who identifies as a woman. See Wikipedia:Gender identity#Self-identification and Wikipedia:Gender identity#Retroactivity (which explains it better that I could), and the various statements by official psychiatric organizations linked from it. As for whether the person named Bruce Jenner that won the Olympics was a man, that's something to ask miss Jenner herself; common courtesy as well as WP:BLP and WP:NPOV require that we don't assume that she was a man merely because other people said so, nor because she looked like one. Diego (talk) 18:09, 2 June 2015 (UTC)[reply]
    I don't think it's proper to use pages classified as essays as bases for arguments here. They are someone's opinion and lack community consensus; that's why they're only essays. As for BLP and NPOV, I said "doesn't require a ton of subjective interpretation". You can't just throw policy links around, please point to specific language in either policy that clearly supports your claims. ―Mandruss  18:16, 2 June 2015 (UTC)[reply]
    In more ambiguous cases I might agree, but in this case we don't have to ask Ms Jenner now because we know that at the time the person named Bruce Jenner publicly self-identified as male and entered the Olympics as a male. --Ahecht (TALK
    PAGE
    ) 22:14, 2 June 2015 (UTC)[reply]
  18. Support as a general rule. We shouldn't go back and anachronistically change the maiden name of an athlete to their married name. Nor would we go back and change all mentions of Ron Artest]] to Metta World Peace from the point before he changed his name. The same should be true here. Of course, if the IOC were to go and retroactively change this, then we have an entirely different discussion on our hands. Resolute 17:19, 2 June 2015 (UTC)<[reply]
    Strike that, I misread the question. Resolute 17:21, 2 June 2015 (UTC)[reply]
    Strike my strike. I think it remains relevant. Resolute 20:03, 2 June 2015 (UTC)[reply]
  19. Support Jenner should be referred to as "Bruce Jenner" when discussing events that happened before June 1, 2015 and as "Caitlyn Jenner" when discussing events that happened afterwards. It is the same reason we have articles called Fall of Saigon, Battle of Königsberg, and Battle of Stalingrad instead of "Fall of Ho Chi Minh City", "Battle of Kaliningrad", and "Battle of Volgograd". [[[Kris Jenner]] was never married to a woman named Caitlyn, only to a man named Bruce. Bobby Martnen (talk) 17:56, 2 June 2015 (UTC)[reply]
  20. Support - It was Bruce who won it at the time. It would be confusing to say Caitlyn as it would give the appearance that Caitlyn actually competed and won it. Keep it simple and preserve what has actually happened and move foward from there.AlaskanNativeRU (talk) 19:04, 2 June 2015 (UTC)[reply]
  21. Support - This seems to be the sensible approach. I can't imagine that other encyclopedias, almanacs, and various information repositories would revise their historical coverage of subjects to align with their current gender identity.- MrX 19:12, 2 June 2015 (UTC)[reply]
  22. Support - Although I'd be in favor of a clearer proposal, I feel inclined to this proposal on the hand. I think the issue is pretty clear-cut: we should use whichever name juridically in force at any given peculiar moment (e.g .Bruce Jenner in 1976, Caitlyn Jenner in 2015). That's a juridical issue, and we hardly can fight against that.
    When it comes to gender, we should distinguish between "gender identity" (subjective experience) and "gender" (an immutable biological component). Once an individual is born male, he will always remain a male. That's also the case with medical records. We can pay homage, however, to the individual's "subjective experience" by respecting and acknowledging one's right to choose his/her name. That's different from the biological gender (he/she), though. Jayaguru-Shishya (talk) 19:41, 2 June 2015 (UTC)[reply]
    Individual's name is a juridical matter. When it comes to that, I think we should use whichever name in force at the particular moment (e.g. Bruce Jenner in 1976, Caitlyn Jenner in 2015). In technical terms, I think that "gender as a subjective experience" is mostly manifested through the choice of name, and by respecting this right we'll afford dignity towards these individuals the best. Cheers! Jayaguru-Shishya (talk) 15:53, 3 June 2015 (UTC)[reply]
    Jayaguru-Shishya, perhaps read the Gender, Sex and gender distinction, Third gender, Genderqueer and Gender variance articles and some of their sources; gender is defined in a social context significantly more than it is defined in a biological context, and it commonly is not immutable. Flyer22 (talk) 14:52, 3 June 2015 (UTC)[reply]
    If I wasn't clear, I generally adhere to the sex and gender distinction, "gender" often means "gender identity," and some transgender people consider being transgender a biological matter while other transgender people don't (or consider it a nature and nurture matter). If you reply to me on this topic, there is no need to WP:Ping me. Flyer22 (talk) 14:58, 3 June 2015 (UTC)[reply]
    @Flyer22: Please see my recent post here: [1]. Cheers! Jayaguru-Shishya (talk) 15:33, 3 June 2015 (UTC)[reply]
    Noted. Flyer22 (talk) 16:00, 3 June 2015 (UTC)[reply]
    If names are a juridical matter, would you say that Marilyn Monroe be referred to as Norma Jean Mortenson?? --Alison (Crazytales) (talk; edits) 14:15, 5 June 2015 (UTC)[reply]
    If Norma Jean Mortenson won a gold medal at the 1952 Summer Olympics, the winner's name should not be retroactively changed to "Marilyn Monroe" on Wikipedia to suit fan sensibilities. Same principle. Carrite (talk) 20:19, 5 June 2015 (UTC)[reply]
    But surely a chart showing gold medalists would be much more informative to the reader if it conveyed that the person they know as Marilyn Monroe was one and the same as the Norma Jean Mortenson who won the medal. Similarly, this list of NBA MVPs relegates to footnotes and links the rather significant fact that the 1970-71 winner, Lew Alcindor, and the 1971-72 winner, Kareem Abdul-Jabbar, are in fact the same person. It would give the reader a much more accurate picture of the true history if that were made explicit in the table itself.--Trystan (talk) 03:14, 6 June 2015 (UTC)[reply]
  23. Oppose in current form. WP:Gender identity explains how names are retroactively changed for trans folks unless the individual specifies otherwise. As mentioned in the discussion below, something like Caitlyn Jenner (formerly Bruce Jenner) would be a good compromise as it respects the person's identity while informing readers of the previous name. EvergreenFir (talk) Please {{re}} 19:50, 2 June 2015 (UTC)[reply]
  24. Support - It simply makes the most sense and is least likely to cause confusion. Clarity and accuracy should be our primary goal. -R. fiend (talk) 20:21, 2 June 2015 (UTC)[reply]
  25. Oppose - this is transphobic as heck. I note the arguments in its favor are often, if I may quote above, "gender (an immutable biological component)", which is purely false. Gender is not immutable. Hell, sex isn't immutable. Also note harm and BLP issues. I also note that people who aren't transgender always get their wishes respected without comment, such as with Prince, or, more infamously, Drake Bell, who insists that he's going to keep referring to Caitlyn as "Bruce" - even though his own birth name is actually not Drake, it's Jared, and yet Wikipedia covers both individuals without comment. I could make a HUGE list here of people who use a different name than their birth name: essentially half of everyone famous changed their name. Exceptions to the use of old names, such as winning awards under another name, can be explained easily without insisting articles about Laverne Cox, Janet Mock, Carmen Carrera, Geena Rocero, Isis King, Gisele Alicea, Leyna Ramous, Dina Marie, Nina Poon, Juliana Huxtable, Niki M'nray, Pêche Di, etc. all insist on using male pronouns and names for them. Right now, Laverne Cox's article states she has an identical twin brother: did that make anyone's head explode? Do we need to go in and explain that they used to be identical twins because? NO. It's incredibly disrespectful; I'm actually outraged at the votes for this policy, and it sure doesn't make anything "more encyclopedic". Ogress smash! 20:48, 2 June 2015 (UTC)[reply]
  26. Support for sports achievements I think it is more misleading to list medals won etc. as Caitlyn Jenner as opposed to Bruce Jenner. The context of sports is a gender-divided one: nothing can change the fact that Caitlyn Jenner competed in the men's division as a man in her track and field career. Certainly her biography should not refer to her as "he" during this period, as a biography is more of a continuous narrative, rather than the historic one here. I certainly would not consider referring to her as "Bruce Jenner" on Athletics at the 1976 Summer Olympics as offensive without personal statements to the opposite. Probably a more sensitive approach would be to use the name as competed, but avoid the masculine pronoun where possible using a more neutral "Jenner" instead. In the biography I think we should make reference to her having "competed in the men's decathlon", which is a neutral statement of fact that clarifies the gender division yet subtly avoids making any explicit statement about her gender. SFB 21:23, 2 June 2015 (UTC)[reply]
  27. Support It is misleading to say a female won a male's event in Jenner's case, it is also very confusing at bits for other instances. I feel this should be a case by case basis though. - Knowledgekid87 (talk) 01:00, 3 June 2015 (UTC)[reply]
  28. Support - . When it comes to name changes, we always take historic context into account. For example, Saint Petersburg (Russia) has undergone multiple name changes... and we (correctly) use the most modern one as the title of our article... HOWEVER we maintain the use of it's historic names when discussing the city in historic contexts (for example, when discussing the city during WWII, we talk about the "Siege of Leningrad"... we don't retro-actively "modernize" the name to: "Siege of St. Petersburg"). I understand the need for sensitivity where gender Identity is concerned, but accuracy in historic context is also important. So... in the Jenner case, I would definitely change the title of the Bio article - but I would allow the use of "Bruce" when talking about her in a historic context (such as her athletic carrier)... I would also use "Bruce" in other articles that mention her in a historic context (such as United States at the 1976 Summer Olympics) I think it would be historically inaccurate to "update" the name in those situations. Blueboar (talk) 13:08, 3 June 2015 (UTC)[reply]
    I'm sorry but that is such innaposite or poor reasoning that I feel constrained to respond, a living person is not a thing - a city is a thing. This living person known then as X and now Y is not in the least innaccurate. Alanscottwalker (talk) 14:00, 3 June 2015 (UTC)[reply]
    Then let's take the example that is about a living person ... let's look at a woman athlete who, subsequent to her athletic career, changed her name. Look at Karyn Bye-Dietz. The bio article correctly uses her current married name (appropriate because that is her current name) but our article on United States at the 2002 Winter Olympics lists her by her historic name (ie her maiden name) in the team roster for the Woman's Ice Hockey team (appropriate because that was the name she had when she was on the team). In other words, we use historic names of living people when discussing those people in historic contexts. Blueboar (talk) 12:39, 7 June 2015 (UTC)[reply]
    That still makes no sense as a blanket rule. When discussing living people, it surely makes no sense to assume by rule they are historic things because they most certainly are not. We just cannot treat the widely commented upon and the not widely commented upon, or the controversial and the uncontroversial, or the usual and the unusual in exactly the same way everywhere, as that's so far from what writing an encyclopedia is about - to reflect the actual complexity of things as much as possible. The desire of some here to put their editing preference in a particular article into a general rule is bad for articles and bad for the encyclopedia. Alanscottwalker (talk) 13:18, 14 June 2015 (UTC)[reply]
  29. Support use of facts at the time rather than preferences afterwards. -- Necrothesp (talk) 13:56, 3 June 2015 (UTC)[reply]
  30. Support While a person can change who they are, that does not make the past change. We should describe things as they happened at the time. Chillum 18:10, 3 June 2015 (UTC)[reply]
  31. Oppose I really don't see why this is necessary, and it seems to me that it basically invalidates people's identities. Cam94509 (talk) 18:28, 3 June 2015 (UTC)[reply]
  32. Overwhelmingly support – Any other option smacks of pure "historical revisionism". And that's true, whether it's names of people, places, or things. --IJBall (talk) 20:01, 3 June 2015 (UTC)[reply]
  33. Strongly oppose. The MOS is clear that whatever identity the person adopts should be used for every phase of their life. The guidelines couldn't be clearer. Liz Read! Talk! 21:25, 3 June 2015 (UTC)[reply]
    The guideline says specifically says "pronouns, possessive adjectives, and gendered nouns". It says nothing about name. --Escape Orbit (Talk) 17:07, 4 June 2015 (UTC)[reply]
  34. Support: Despite the shortcomings of MOS:IDENTITY, you can't erase the past. Life is a continuum. The Dissident Aggressor 22:13, 3 June 2015 (UTC)[reply]
  35. Support: With the former name link working as a redirect, this sounds like the most practical option. If the person in question objects, I'd then support option 4. --Waldir talk 10:10, 4 June 2015 (UTC)[reply]
  36. Support. Simply because the other options so poor. Kendall Jenner was not born to Caitlyn Jenner and Kris Jenner, because Caitlyn Jenner did not exist at the time. So Option 2 is historical revisionism and leaves the reader with more unanswered questions than answers. Option 3 is confusing (she was born to Caitlyn and then a second time to Bruce??) and Option 4 seems like a distracting tangent taking the reader off the article topic into someone else's life-story. Caitlyn's identity is fully recognised in her own article, that is her right. But why should anyone have the right to re-write history? --Escape Orbit (Talk) 17:02, 4 June 2015 (UTC)[reply]
  37. Support As others have pointed out, it makes very little sense to list Caitlyn as having won a men's event, but there are other issues. One editor is running around changing all instances of "Bruce" to "Caitlyn" citing MOS:IDENTITY (see example). I asked about this at WT:TV and a suggestion was to use "Caitlyn Jenner (credited as Bruce Jenner)". The problem with this is that at the time it was "Bruce Jenner (credited as Bruce Jenner)". Retroactively changing all occurrences of "Bruce" to "Caitlyn" is effectively changing history, like saying that American astronauts planted six international flags of surrender on the moon simply because the stars and stripes have now faded. Jenner has decided to identify as Caitlyn now, but does Caitlyn deny she was ever Bruce? It's fine to use the present name in the BLP but outside, we should be using what is verifiably correct back whenever, especially when it applies to something like 34-year-old episodes when Caitlyn Jenner did not exist. --AussieLegend () 20:55, 4 June 2015 (UTC)[reply]
  38. Support - Take the activism elsewhere. Records are historic and changing names on them to suit self-righteous sensibilities is anachronistic and makes us look silly, both. Carrite (talk) 00:59, 5 June 2015 (UTC)[reply]
    Support - past accomplishments were awarded to Bruce Jenner. It makes the most sense to keep those events surrounding Bruce Jenner with Bruce Jenner's name. We can redirect to Caitlyn Jenner. Inks.LWC (talk) 04:12, 5 June 2015 (UTC) Apparently I !voted twice (I guess I forgot I came here the first time). My second !vote was lengthier and sums up my thoughts better than this one; I have kept that support !vote below, unstruck. Inks.LWC (talk) 02:01, 8 June 2015 (UTC)[reply]
  39. Oppose - A trans person on here will have being trans associated with their past. It makes no sense deny a trans person's identity across their entire past until they come out. It's a serious breach of respect. Gwenhope (talk) 07:01, 5 June 2015 (UTC)[reply]
  40. Oppose - It's important to note that most often, a subject will be referred to with their surname as pretext for a sentence. And on the issue of pronouns, only confusion and inconsistency comes from mixing it up. Wikipedia should be easily read and understood. These things can be dealt with in the lead. Glitchygirl (talk) 10:56, 5 June 2015 (UTC)[reply]
  41. Support Historical accomplishments should be attributed to the name in the historical records, that is what is verifiable. This is not just for this specific case but for all cases. We should not be rewriting history, but reporting things as they happened. -- GB fan 11:53, 5 June 2015 (UTC)[reply]
    So basically you are saying that transgender people have no right to be credited by current name for their past accomplishments? They are to be ghettoized and have their accomplishments stripped from them simply because they changed their gender? Perhaps we should do the same to people who convert to Judaism. Or for black people. huh? Skyerise (talk) 12:01, 5 June 2015 (UTC)[reply]
    No I am not saying that transgender people should have their accomplishments stripped from them. Their accomplishments are their accomplishments no matter what their current name. Their previous name should be retained for their previous accomplishments and their new name should be for all new accomplishments, that is what the reliable sources say and so should we. The same should be done for people who convert to a different religion. Let's say a Catholic priest converted to Judaism, we wouldn't say he was a Jew when he was a catholic priest. As far as black people, no one changes their ethnicity/color of their skin so I do not know what that has to do with this conversation at all. -- GB fan 12:27, 5 June 2015 (UTC)[reply]
    So I'm sure you've taken the time to look into this deeply, read the psychological studies about the emotional harm and suffering that transgender people go through and which continues after transition when people insist on using their "real" name, and that because of this most major style guides have decided that they should always be referred to by their new name. And yes, to a lesser degree, we should respect anybody's name change. All it takes is an additional citation. But I guess that's too much work for you to respect people's current identities. Skyerise (talk) 13:14, 5 June 2015 (UTC)[reply]
    I completely respect everyone's current identity, just like I completely respect their historical identity. -- GB fan 13:48, 5 June 2015 (UTC)[reply]
  42. Oppose this retrograde nonsense. Protonk (talk) 13:06, 5 June 2015 (UTC)[reply]
  43. Oppose. Protonk captures my feelings well (although I'd probably add more frustrated monosyllabic noises). Ironholds (talk) 13:26, 5 June 2015 (UTC)[reply]
  44. Strongest possible oppose. Per Protonk and the current MOS:IDENTITY. This doesn't "clarify" MOS:IDENTITY, it regresses it. --Alison (Crazytales) (talk; edits) 14:15, 5 June 2015 (UTC)[reply]
  45. Support. Seems to me the difficulties encountered in Caitlyn Jenner point to serious problems with MOS:IDENTITY. In both Jenner's Olympic record and marriages, the encyclopedic narrative gets blurred. There's no perfect answer here: we are bumping into the limitations of the language. But I think that, as a general rule, staying with the historical gender allows Wikipedia to be more faithful to the contemporary references we rely on. Barte (talk) 16:00, 5 June 2015 (UTC)[reply]
    Oh yeah, it's way too difficult to add a second reference for the name change. Sorry to put you through so much bother to be respectful to other people. Skyerise (talk) 16:02, 5 June 2015 (UTC)[reply]
    More faithful to the references? Because, what, the reference might have the wrong name? Like we had this conversation for Prince. Ironholds (talk) 16:36, 5 June 2015 (UTC)[reply]
  46. Support per the several comments above of Wikimandia, War Wizard90, Fyunck, Trackinfo and MrX: this is a simple matter of historical accuracy. Retroactively renaming/regendering a person who has lived, worked and competed as a man for 65 years -- and for 40 of those years as a very prominent public figure -- is the worst kind of historical revisionism, and begins to take on unintended comical aspects when we attempt to re-write history based on an ideologically-driven public awareness campaign. I am all for acknowledging the present reality of Jenner's gender identity with a measure of compassion and sensitivity, but we must also acknowledge the historical reality that existed for most of the last 65 years. Doing otherwise is simply not factually accurate, and the idea of rewriting Wikipedia sports articles to suggest that Caitlyn Jenner won the Olympic gold medal in the men 's decathlon in 1976 is nothing less than bizarre. Dirtlawyer1 (talk) 16:56, 5 June 2015 (UTC)[reply]
  47. Support. We really can't say Caitlyn competed in the men's decathlon or that she was married to Kris Jenner, because both are false. But than again, I'm a male sports fan. Calidum T|C 17:23, 5 June 2015 (UTC)[reply]
    @Calidum: Please explain in what way they are false. Are you saying that Bruce and Caitlyn are not the same person? A person won a decathlon and a person married. "Caitlyn Jenner" is a name that references that person and, at least on Wikipedia, is unique. So yes, the individual now named Caitlyn, the same individual, did those things. Why would a name be more important than personhood? Skyerise (talk) 20:29, 5 June 2015 (UTC)[reply]
  48. Support I'm afraid that many editors care more about a specific POV and are using this issue as a means of advocacy. What is important is to write articles that are sourced and readable. Using a specific gender thoughtful articles to please activists is a disservice to the reader. Taking into account the timeline of transition (which this option does) is the only way to not confuse the reader. If the activists are offended by this, well tough shit.69.143.188.200 (talk) 19:16, 5 June 2015 (UTC)
    If you think our readers are genuinely so incapable of thought that they couldn't understand the very rudimentary elements of gender transitions, it's you doing the disservice. People seem to be talking a lot about how this is "POV activism": if treating our subjects with human decency and respect is "POV", something is very wrong with what we consider neutrality. Ironholds (talk) 15:31, 6 June 2015 (UTC)[reply]
  49. ***If you think the jarring pronoun usage employed in this article is comprehensible, then you should find a new hobby as you're a detriment to the project. 69.143.188.200 (talk) 22:24, 9 June 2015 (UTC)[reply]
  50. Support - either this or option 3 (I think the person's chosen name and gender should be used, but possibly, in very unusual cases - such as in the case of winning an Olympic medal - the previous name can be denoted. TMagen (talk) 16:52, 6 June 2015 (UTC)[reply]
  51. Support - for historical events. The source for the 1976 Summer Olympics decathalon says "Bruce Jenner", not "Caitlyn Jenner", so to change this from "Bruce" to "Caitlyn" violates WP:V and WP:SYNTHESIS. Until we have a source that says that Caitlyn Jenner won the 1976 decathalon, it is synthesis to take one source that uses Bruce Jenner as the winner and another source that says that Bruce Jenner identifies now as Caitlyn Jenner and then take those two sources to mean that Caitlyn Jenner won the decathalon. Inks.LWC (talk) 18:33, 6 June 2015 (UTC)[reply]
    The suggestion that changing "Bruce" to "Caitlyn" (or changing other trans peoples' names) violates SYNTH and/or V has been made before, but is controversial and AFAICT not widely-held. Compare our articles on various chemicals, where sources saying "H2SO4" or "sulphuric acid" has a certain property are routinely cited in support of statements that "sulfuric acid has [such-and-such property]". -sche (talk) 20:44, 6 June 2015 (UTC)[reply]
    I see no issue with SYNTH there, because the article would not be reaching a conclusion not explicitly stated by the sources. In those sources, H2SO4 is the same thing as sulphuric acid. In the articles regarding Jenner's accomplishments, they were written before Jenner identified as Caitlyn. In chemistry articles, H2SO4 was identified as sulphuric acid when the article was written; the same is not true of articles written about Jenner pre-transition. Inks.LWC (talk) 21:41, 6 June 2015 (UTC)[reply]
  52. Support People in Wikipedia are notable and if there history is covered in Wikipedia it's generally notable and public. Jenner's transition is very public and virtually all of her public life has been portrayed as male to the public. We cannot rewrite history. Jenner's movie and TV credits will not be updated. Jenner was male when competing in the Olympics. There's no indication that Jenner wishes to separate her public life as "Bruce" from her public life as "Caitlyn." Sensitivities to deadnaming may not even be wanted or applicable to Jenner as she has chosen to transition in a very public way and her fame as "Bruce" is certainly a part of the notability of her transition. We should not be scrubbing her history as if being "Bruce" was shameful or hurtful. It is much more confusing to have names that don't match credits in media or history books. --DHeyward (talk) 10:25, 7 June 2015 (UTC)[reply]
  53. Oppose. This would introduce a practice of misgendering into Wikipedia policy, which would be transphobic. The gender assignment done to a person by anonymous health personnel at their birth is no more valid (but rather less valid) than the gender identity a person chooses for themselves. And I find the term "historical gender" patronising and ridiculous. A transgender person has only one gender and that is the one that they say they have. Using outdated pronouns or names and inventing terms like "historical gender" take away transgender people's right to define themselves. - MellowMurmur (talk | contributions) 20:33, 7 June 2015 (UTC)[reply]
  54. Mild Support Let's not introduce unnecessary anachronism. I don't see anything transphobic or discriminatory, when talking about past events, about mentioning the persona that the transgender person assumed publicly and socially at the time. It's a whole different matter than in an article where this person is the main topic, as many discussions here have established. Option 4 is descriptive and correct enough though. Place Clichy (talk) 12:09, 8 June 2015 (UTC)[reply]
  55. Support - Caitlyn Jenner did not exist prior to the publishing of the Vanity Fair article. The former Bruce Jenner article is now correctly titled Caitlyn Jenner, and deals with the subject appropriately. All references in the future should refer to this individual as Caitlyn, and use the appropriate terms her/she, etc. Prior to this year, all references should reflect the accuracy of the history, that Bruce Jenner existed and accomplished those things under that name. I would oppose any of the other 3 alternatives. Onel5969 (talk) 17:42, 8 June 2015 (UTC)[reply]
    Caitlyn Jenner has been in existence since October 28, 1949. She went by a different name publicly until a few days ago, but she was still the same continuous person. It is not historically inaccurate to credit the same continuous person under a different name, though per Options 3 and 4, it makes sense to me to include both names for clarity (but only because she was already publicly notable under her previous name). Funcrunch (talk) 20:04, 8 June 2015 (UTC)[reply]
  56. Support Stick with what the references say and don't try to revise historical info. As for this being "offensive", so what. WP:NOTCENSORED applies here. There is a lot of stuff on wiki that is offensive some group or other, some stuff is personally offensive to me, and we have chosen to ignore those concerns when a valid encyclopedic goal is being met. Geraldo Perez (talk) 22:34, 8 June 2015 (UTC)[reply]
  57. Support Caitlyn didn't win the decathlon -- Bruce did. It's fine to have a footnote indicating the gender transition and name change, but to suggest that "Caitlyn Jenner" won an Olympic gold medal in 1976 is simply not what happened. I don't see what's so hard about this -- when Caitlyn was Bruce, refer to her as Bruce (that's who she was at the time). To say that Caitlyn won the decathlon is as silly as saying that Bruce is being presented a special Espy for bravery. It's just not how it happened. 173.160.130.14 (talk) 23:37, 8 June 2015 (UTC)[reply]
  58. Oppose. The other options would be preferable. Weakening MOS:IDENTITY like this opens the door to wikilawyering from trolls who insist on misgendering people. The status quo version has issues, of course, but they can be resolved through options 3 and 4. NinjaRobotPirate (talk) 05:24, 9 June 2015 (UTC)[reply]
  59. Support for sports achievements per the argument made by Sillyfolkboy above. Sideways713 (talk) 10:06, 10 June 2015 (UTC)[reply]
  60. Support especially for sports achievements, per Knowledgekid87 and SFB (Sillyfolkboy) above. —Wasell(T) 12:18, 10 June 2015 (UTC)[reply]
  61. Support for sports achievements Jenner, as a man, won the Olympic medals in the men's category, and in retrospect saying that a woman won those events is historically and factually inaccurate. Randy Kryn 12:32, 10 June 2015 (UTC)[reply]
  62. Oppose This option, which fails to even acknowledge the name the person has chosen after transitioning, is not consistent with the "high degree of sensitivity" mandated by BLP. Gender identity is a matter where this sensitivity is particularly important, considering the history of discrimination, prejudice and non-recognition that the trans* community has suffered. Neljack (talk) 07:43, 13 June 2015 (UTC)[reply]
  63. Oppose using only historic name without reference being made to newly chosen designation.
    Where possible also oppose the making of any reference to gender where possible which may raise confusion for readers many of whom will have come to an encyclopedia article on a sporting event so as to read about that sporting event. Why say either she or he when "Jenner" is would be sufficient in most if not all cases. We are dealing with a person here and one who, while identifying as a female, was seemingly comfortable with the use of the male pronoun in the early June interview. GregKaye 14:55, 13 June 2015 (UTC)[reply]
  64. Oppose using only the historical name; we should use both names. Even aside from the issue of respecting their choice, this could easily cause confusion when eg. someone searches for information about them using their current name. --Aquillion (talk) 07:09, 14 June 2015 (UTC)[reply]
  65. Support, to preserve the historic record. The name and identity of the person at the time iscussed are simply facts, we must clearly report those. Using both names would be acceptable in some cases. DES (talk) 12:02, 18 June 2015 (UTC)[reply]
  66. Oppose Per BLP and MOS:IDENTITY. Misgendering in general is highly insulting not only to the individual in question but also to all others in similar situations. Further this doesn't seem to match what is done in other cases of name changes based on the comments others have made about Muhammad Ali for example below. PaleAqua (talk) 17:16, 21 June 2015 (UTC)[reply]
  67. Support to preserve history accurately, and not confuse readers.Godsy(TALKCONT) 03:29, 22 June 2015 (UTC)[reply]
  68. Support This is an encyclopedia and the facts should be presented accurately. As a reader above mentioned, we wouldn't call the Battle of Stalingrad the "Battle of Volgograd"...we use the historic name. If someone was known as one name for a particular event or at a particular time, that is the name that should be used. AHeneen (talk) 22:04, 22 June 2015 (UTC)[reply]
  69. Support We should be writing about what actually happened. This is in keeping with the wishes of our current test case, and I don't see how anyone else in such a situation would take offense. DPRoberts534 (talk) 05:28, 28 June 2015 (UTC)[reply]
  70. Support for historical events. I don't think the question of synthesis has been adequately explored to say that it has been rejected. To avoid questions regarding MOS:IDENTITY, pronouns should be avoided, and the article about the person should generally be under his/her current name (but see Cat Stevens for an exception to the general statement). — Arthur Rubin (talk) 21:42, 12 July 2015 (UTC)[reply]
  71. Support for historical events and other events prior to a name change. The person who won an Olympic medal in 1976 was Bruce Jenner, not Caitlyn Jenner. --Bookworm857158367 (talk) 00:04, 16 July 2015 (UTC)[reply]

Option 2 (use most recent gender across all Wikipedia articles)

  1. Support. This is the current consensus per MOS:IDENTITY, which has been thoroughly discused to its current form (search for 'identity' at the MOS archives for many of the arguments held in the Support section which have already been addressed). Diego (talk) 09:17, 2 June 2015 (UTC) - Moved to Option 4. Diego (talk) 13:44, 3 June 2015 (UTC)[reply]
  2. Oppose. Deal with it on a case-by-case basis. There are many places where MOS:IDENTITY is guaranteed to be confusing. Epic Genius (talk) 16:32, 2 June 2015 (UTC)[reply]
  3. Support - this is basically policy; MOS:IDENTITY specifies that we use the current gender identity throughout the article. The subject's preference overrides any and all arguments. Skyerise (talk) 16:52, 2 June 2015 (UTC)[reply]
    Note: MOS:IDENTITY is not yet a policy; it's a guideline. I'm not sure it will be policy in the future. Flyer22 (talk) 14:25, 3 June 2015 (UTC)[reply]
  4. generally support as current policy. But there are places where the gender change will need to be made clear in articles outside of the subject themselves. the case of the Caitlyn /Bruce - Kris Janner marriage for example. We run into BLP issues from both parties involved. -- TRPoD aka The Red Pen of Doom 19:49, 2 June 2015 (UTC)[reply]
  5. Support - it's incredibly transphobic not to use the preferred pronouns and name of the individual. No one blinks at calling Prince "Prince". There are only a limited series of spaces where the individual's birth gender or name need be indicated, and those would be specific exceptions. BLP is a big issue here, but it's not the only place it would be an issue. Ogress smash! 20:33, 2 June 2015 (UTC)[reply]
  6. Oppose. Per my comments above, that goes against what the sources said at the time. Going against what is reported in sources is a key wikipedia principle that should not be violated. It is essentially wikipedia rewriting history. Trackinfo (talk) 21:07, 2 June 2015 (UTC)[reply]
  7. Oppose. Many media houses preserve historic gender and name when discussing a trans person's past. Wikipedia does not need to blaze a new trail in this regard. Binksternet (talk) 23:00, 2 June 2015 (UTC)[reply]
  8. Oppose. I am with Binksternet on this one, we aren't here to break barriers we are here to write an encyclopedia. - Knowledgekid87 (talk) 01:07, 3 June 2015 (UTC)[reply]
  9. Support The only situation this causes problems with is when the subject waffles on whether they're transitioning or not, in which case it could turn into a chore constantly updating 'all references to the subject in every article to be consistent with their current wishes. But I think that would be the exception, and were it to become an issue... WP:IAR. —Locke Colet • c 02:27, 3 June 2015 (UTC)[reply]
  10. Oppose. Links to past articles should remain Bruce, or say Caitlyn, then known as Bruce Jenner. --Frmorrison (talk) 16:53, 3 June 2015 (UTC)[reply]
  11. Support This is really the only way of looking at this that doesn't wind up being super invalidating, and is in line with previous consensus. Cam94509 (talk) 18:30, 3 June 2015 (UTC)[reply]
  12. Oppose: Per binksternet. Take your activisim elsewhere. This is an encyclopedia. The Dissident Aggressor 22:13, 3 June 2015 (UTC)[reply]
  13. Oppose - we shouldn't be re-writing history or using sources that aren't there. Fyunck(click) (talk) 23:12, 3 June 2015 (UTC)[reply]
  14. Oppose - The Decathlon was won by a man named Bruce, the same man who married Kris Jenner. The fact that he wants to be called "Caitlyn" now does not change historical facts. Bobby Martnen (talk) 02:18, 4 June 2015 (UTC)[reply]
    @Bobby Martnen, the decathlon was not won by a name, it was won by a person That person is still living and has taken a new name. Are you denying that the person now known as Caitlyn won the decathlon? Are you denying their right to change their name? Or do you think "names" are more important than "persons"? Do you think a person should be denied being properly credited for their past accomplishments just because they changed their name? Or because they changed their gender? Or does the fact that she's now female squick you out and you'd rather not see it in articles you work on? No accusations here, just questions. Skyerise (talk) 19:38, 5 June 2015 (UTC)[reply]
    the decathlon was not won by a name, it was won by a person More specifically, it was won by a person named Bruce, not by a person named Caitlyn and the name is important. That the person may have changed their name is irrelevant. I doubt Caitlyn Jenner can drive on Bruce Jenner's driver's license or travel on Bruce Jenner's passport and if Caitlyn Jenner was claiming she won the decathlon she'd have to prove that she was Bruce Jenner. --AussieLegend () 14:06, 6 June 2015 (UTC)[reply]
    Actually it is quite common for trans people to use drivers licenses and passports with their previous names on them for a period of time after beginning to use a new name, as there is a lot of paperwork and time involved; each agency has different requirements. I don't know if Caitlyn has changed any of her identity documents yet. But it hardly seems relevant to the discussion of whether to list her current name in a Wikipedia article that links to her biography which explains her gender transition. Funcrunch (talk) 16:01, 6 June 2015 (UTC)[reply]
  15. Oppose - An over-the-top, extremist misreading of the MOS suggestions. Carrite (talk) 01:03, 5 June 2015 (UTC)[reply]
  16. Support and suggest a couple of the people opposing read the discretionary sanctions in this area before hitting "save" again. Ironholds (talk) 01:57, 5 June 2015 (UTC)[reply]
  17. Oppose - a blanket ban will produce situations where Wikipedia contains nonsensical or misleading statements. --Carnildo (talk) 02:54, 5 June 2015 (UTC)[reply]
  18. Support - It's an issue of respect and simply that. A trans person's wikipedia article will have their transgender nature included. That clears up all the other issues (such as people listed as X gender having won Y gender's event, etc. etc.) Gwenhope (talk) 07:01, 5 June 2015 (UTC)[reply]
  19. Support - MOS:IDENTITY reads like a guideline already grounded on the consideration of gender theory, e.g. just as with sexual orientation, gender identity was developed in the womb separate from the body. One wouldn't postulate that a gay man or woman chose to be this way; they must have always been. It's the same with trans people. As long as we point out the exact date of coming out in the lead—Prior to June 2015, Caitlyn Jenner was referred to as Bruce Jenner—there won't be any confusion. Glitchygirl (talk) 10:04, 5 June 2015 (UTC)[reply]
  20. Support as within the spirit of the current MOS:IDENTITY. I'm not quite sure how to handle the supposed thorny BLP issues with implying that Kris Jenner was in a lesbian marriage. I think that Caitlyn being trans and (at least publicly) identifying as male during their marriage is pretty common knowledge; I can't see how a commonsensical reading of anything around Kris and Caitlyn's marriage would be construed as Kris being in a lesbian marriage. --Alison (Crazytales) (talk; edits) 14:25, 5 June 2015 (UTC)[reply]
  21. Oppose for the reasons of historical accuracy which I expressed under Option 1 above. When someone has been a prominent public figure as a man, we should not attempt to rewrite history to reflect later transgender revelations. We can and should acknowledge the present reality of Jenner's gender identity with compassion and sensitivity, but rewriting 65 years of the personal gender history of a prominent public figure is almost Orwellian in character. Dirtlawyer1 (talk) 17:06, 5 June 2015 (UTC)[reply]
  22. Oppose This standard appeals to activists who claim (without any merit) that misgendering a subject in an earlier phase of life harms all Trans people. That it bothers the activist is no concern of ours. Writing comprehensive articles is the only concern.69.143.188.200 (talk) 19:24, 5 June 2015 (UTC)[reply]
  23. Support: As a transgender person myself, I hate being called by my birth name. Charlotte Allison (Allen/Morriswa) (talk) 20:54, 5 June 2015 (UTC)[reply]
  24. *This of course has zero validity, unless you are Jenner. I fail to see how a few Trans people's personal preferences are used as the basis for a policy. 69.143.188.200 (talk) 01:22, 6 June 2015 (UTC)[reply]
      • Probably because most trans people are in agreement on this topic. Easily verifiable on the internet and at Deadname. 03:02, 6 June 2015 (UTC)
        • Jenner answered the queston for her in the Vanity Fair article Bissinger apologizes to Jenner for repeated pronoun confusion and asks whether she is sensitive about it. “I don’t really get hung up,” she tells him. “A guy came in the other day and I was fully dressed—it’s just habit, I said, ‘Hi, Bruce here,’ and I went, Oh fuck, it ain’t Bruce, I was screwing up doing it.” Different strokes. The biggest difference with Jenner and most other people (not just transgender people) is fame and celebrity status for 40 years prior to transition. She chose to publicly transition in way that isn't available to hardly anyone. Also, celebrities manage their image. It was true before her transition and it is true after. Virtually everyone doesn't know Jenner any more after her transition than before her transition unless they are personal friends or family. --DHeyward (talk) 09:04, 8 June 2015 (UTC)[reply]
      • Now discarding someone's opinion because they are transgender is out of line, although that's not exactly what you wrote. Note that the discussion here is a general one, not about Jenner. Place Clichy (talk) 18:03, 8 June 2015 (UTC)[reply]
  25. **** No, that would be sn ad hominem attack. But the flip side is "I is trans" is an appeal to authority, as if trans opinions should have more weight. They don't.69.143.188.200 (talk) 22:12, 9 June 2015 (UTC)[reply]
  26. Oppose We shouldn't be changing history. --AussieLegend () 14:16, 6 June 2015 (UTC)[reply]
    @AussieLegend: presumably your next edits will be to rename the crap out of things at the article on Prince (musician) hmn? Ironholds (talk) 15:29, 6 June 2015 (UTC)[reply]
    No, because that is the BLP and this discussion is about MOS:IDENTITY's application outside the BLP. --AussieLegend () 15:37, 6 June 2015 (UTC)[reply]
    @AussieLegend: So the album articles, then? I note that The Black Album (Prince album) currently describes itself as " the sixteenth studio album by American recording artist Prince" - this is ludicrous! It's rewriting history! He wasn't called Prince at the time! Why aren't you fixing it? Ironholds (talk) 15:41, 6 June 2015 (UTC)[reply]
    There's a practical issue there. You can't really call him "unpronounceable squiggle" in the article. That's certainly an issue where things have to be handled on a case by case basis. --AussieLegend () 15:52, 6 June 2015 (UTC)[reply]
    There's no such thing as "outside the BLP" in Wikipedia. The BLP policy applies to all articles and non-article spaces, everywhere in the project. Diego (talk) 17:44, 6 June 2015 (UTC)[reply]
    If you read the discussion again you'll see here that BLP refers to the subjects biographical article. --AussieLegend () 12:43, 8 June 2015 (UTC)[reply]
    If you read the policy on which MOS:IDENTITY is based, you'll see that whether the content is located or not in the biography article is irrelevant to the protections WP:BLP provides. The reasons why MOS:IDENTITY is written that way do not dissappear when you move to a different article. Diego (talk) 12:50, 8 June 2015 (UTC)[reply]
  27. Oppose. Deal with it on a case-by-case basis. Even if facts are offensive, they are still facts. We recognize more recent changes by acknowledging the current state, not by pretending that history was different than it was. Being deliberately offensive is wrong. Publishing false information is wrong as well. Jacona (talk) 15:54, 6 June 2015 (UTC)[reply]
  28. Support this as my first choice, especially in articles that mention someone who subsequently became notable but who was not notable at the time the article is concerned with. For example (using a non-trans example): someone made the point (apparently in another discussion which has since been archived, or perhaps on WT:MOS) that Michelle Obama's article says things like "Obama attended Whitney Young High School, Chicago's first magnet high school", and Whitney M. Young Magnet High School's article mentions "Michelle Obama" among its alums, even though she wasn't "Michelle Obama" at the time she attended the school. For articles that mention someone who is now known under name Y, but who was notable under name X at the time the article was concerned with (like articles that mention Jenner's Olympic performances), I concede that using only the current name could be less clear than either of the options I have voted on below as my second and third choice options. -sche (talk) 17:58, 6 June 2015 (UTC)[reply]
    Then this would also work in the theoretical since precedent is being set. If 20 years from now, former president Barak Obama remarries and decides to take his wife's legal name of Snickley, we would have to go back and change all references of the 44th president of the United States to President Barak Snickley. Sorry but I'm not ok with that. President Snickley pushed through Obamacare/Snickleycare? President Snickley was the first black President? Or other choices, even if mentioned in the article 100 times, every occurrence would be "President Snickley (President Obama)". Fyunck(click) (talk) 20:05, 6 June 2015 (UTC)[reply]
  29. Support. Doing anything but this would constitute misgendering. The gender assignment done to a person by anonymous health personnel at their birth is no more valid (but rather less valid) than the gender identity a person chooses for themselves. And I find the term "historical gender" patronising and ridiculous. A transgender person has only one gender and that is the one that they say they have. Using outdated pronouns or names and inventing terms like "historical gender" take away transgender people's right to define themselves. - MellowMurmur (talk | contributions) 20:33, 7 June 2015 (UTC)[reply]
  30. Oppose It will depend on the person. From GLAAD media guide -> "Unless a former name is newsworthy or pertinent, use the name and pronouns preferred....". In the case of Jenner, winning the Men's Decathlon as "Bruce Jenner" created her notability and both name and gender are newsworthy and pertinent. Articles that refer to Jenner's olympic achievement and are written historically should use the name and pronouns that are the most comprehensible to our reader. We should not have asterisks, parentheticals, explanations, (i.e. "as Bruce") etc, etc, to explain a transition which is not relevant to the notable historical event or use pronouns that would require such an explanation such as "she won the Men's Decathlon." The whole concept of "respecting the person" is thrown out the window when the focus of every achievement is solely viewed through theitr transition. The wikipedia articles mentioning Jenner are starting to read like "Psst, she's transgender" at every reference to their accomplishments which seems to be the result of activism without regard for the person. --DHeyward (talk) 08:38, 8 June 2015 (UTC)[reply]
    From a purely encyclopedic aspect, the fact that a woman won a male-specific category seems particularly relevant to the granting of the award. The explanation of how that happened (that the woman at hand is transgender, and was publicly standing as male at the time) requires more clarification than a mere psst, in my humble opinion - and certainly more than total silence or an unexplained redirect. Diego (talk) 10:06, 8 June 2015 (UTC)[reply]
  31. Oppose per anachronism. Next we know, the Republic of Turkey was defeated in World War I, Napoleon invaded the Soviet Union, and Christopher Columbus discovered the United States. Place Clichy (talk) 12:09, 8 June 2015 (UTC)[reply]
  32. Oppose. Revisionism, writing things directly at odds with the primary sources, is not scholarship. --SmokeyJoe (talk) 12:15, 8 June 2015 (UTC)[reply]
  33. Oppose. Revisionism. We have sources for the info, stick with what they say. Geraldo Perez (talk) 22:40, 8 June 2015 (UTC)[reply]
  34. Comment make use of current name in tandum with previous name where practical and where it doesn't conflict with another BLP. Avoid using gender pronouns using surname where practical. GregKaye 15:29, 13 June 2015 (UTC)[reply]
  35. Generally oppose using only the new name. I'm divided on this one, since I think it's context-sensitive, but in general in historical contexts it seems to me that there's a good chance that people will come to the article knowing or searching for their old name; if we don't include a clarification, they could be confused if they don't find it. However, the old name could be omitted in cases where it's unlikely that they have any particular fame under that name (eg. if for some reason an article is discussing them before they were famous, mentioning their old name might be unnecessary.) --Aquillion (talk) 07:12, 14 June 2015 (UTC)[reply]
  36. Strongly Oppose This simply blurs, distorts, or even falsifies history. The name, identity, and gender that were in effect at the time being discussed in an article are facts of history. To omit or change them is out-and-out wrong. Acknowledging the new name and identity also is another matter. DES (talk) 12:11, 18 June 2015 (UTC)[reply]
  37. Strongly Support I'm not sure why this is such a big issue. If Jenner had changed her last name, then it would have absolutely appropriate to make retroactive edits. I don't see how this is any different than a change in her gender identity and first name. While we are on the topic, somebody definitely needs to change her picture at the top of the page! It is nothing short of ridiculous that a dated picture is still up there, given that she has made such a dramatic change in appearance. I know this has been recently changed, and I think it is disrespectful that the editor did not use a picture of Jenner as female-presenting. ralevudwu (talk) 10:10, 02 July 2015 (UTC)[reply]
    This "un-option" has been superseded by Option 5, below
  38. Oppose as historical revisionism. We must include the name the person was using at the time in most articles. — Arthur Rubin (talk) 21:45, 12 July 2015 (UTC)[reply]
  39. Oppose as frequently misleading, in that it would imply the spouse of the earlier time was in a homosexual relationship, or that a sports team was coed or that a military unit was coed. It would make some "The first woman to " do something like make a pioneering flight or achieve something impressive like climbing a mountain or winning a prize. The Vanity Fair article about Jenner used Bruce and "he" for historic events and Caitlyn and "she" for recent events. I favor using the previous name and pronoun for historic events, with the subsequent name in parenthesis: Bruce Kenner (later Caitlyn Jenner) won an Olympic medal and fathered several children. Edison (talk) 22:27, 15 July 2015 (UTC)[reply]
  40. Oppose per my above comments. It causes confusion and contradicts reliable historical sources. When referencing historical events, the historical gender of that time should be preserved. Rreagan007 (talk) 02:24, 21 July 2015 (UTC)[reply]

Oppose both

  1. First of all, it has to be a bad idea to say we need a policy rule now to deal with this one subject's emergency case. We should approach this on a case by case basis in various dispute resolution forums, if need be, before we jump to straight-jacket policy provisions, in that way experience will guide consensus, and perhaps down the road we may make a reflective policy. Alanscottwalker (talk) 19:40, 2 June 2015 (UTC)[reply]
    We have a policy; it's MOS:IDENTITY. Oddly enough Wikipedia has included articles about transgender individuals before this. Ironholds (talk) 01:56, 5 June 2015 (UTC)[reply]
    Sure we have, and we don't need new policy, for all articles because some want a Jenner rule. Alanscottwalker (talk) 22:45, 5 June 2015 (UTC)[reply]
    @Ironholds: MOS:IDENTITY is only a guideline, it's NOT a policy. WP:V is a policy. --AussieLegend () 14:13, 6 June 2015 (UTC)[reply]
    There's no need to use EXTRANEOUS CAPS LOCK. WP:V is indeed a policy! WP:BLP is also a policy. One of those two is associated with a Board of Trustees mandate to treat article subjects with respect and human decency; guess which? Ironholds (talk) 15:28, 6 June 2015 (UTC)[reply]
    This isn't about WP:BLP, it's about the applicability of a guideline. --AussieLegend () 15:41, 6 June 2015 (UTC)[reply]
    It's absolutely about WP:BLP, which mandates treating subjects with respect, when you start arguing that we have to rely on the old details because verifiability is The Most Important Thing. In BLPs, verifiability is not the most important thing. Ironholds (talk) 17:29, 6 June 2015 (UTC)[reply]
    No, we're not talking about BLP. We're specifically discussing how this guideline should be applied. The outcome of this discussion will have absolutely no effect on WP:BLP or how it is applied. --AussieLegend () 09:16, 7 June 2015 (UTC)[reply]
    Yes, it's about BLP. Basically, it would be changing the combined effect of MOS:IDENTITY and BLP from saying that we must treat all living subjects respectfully to saying that we must treat all living subjects respectfully except transgender people, authorizing transphobes to deadname and misgender them, things which are known to be emotionally harmful to transgender subjects. How is that not a BLP issue? Skyerise (talk) 15:44, 7 June 2015 (UTC)[reply]
    But it's not about WP:BLP. MOS:IDENTITY is a guideline extraneous to WP:BLP, which doesn't even mention it. Your argument that the combined effect would be "except transgender people" is absolutely incorrect. Transgender people will be treated with the same respect as anyone else, but without denying history. You have, for example, absolutely no evidence that Jenner wants now to be referred to as Caitlyn for past achievements. That's merely your assumption and you're making the decision for Jenner without considering her personal preference. That's incredibly disrespectful. --AussieLegend () 16:03, 7 June 2015 (UTC)[reply]
I think your rationale is quite offensive, harmful and irrespecive against trans-people, Skyerise. Jenner gained his merits in the field of sports as a male, and now without even asking, you'd like to change that? Have you ever considered that gender identity might not be an on/off switch? Jenner, indeed, might have achieved a lot while still cherishing his male gender idenity, and only later had the urge to change his gender, Caitlyn, as nowadays we call her. We should respect that and not look down on the person's identity in play. Jayaguru-Shishya (talk) 19:23, 9 June 2015 (UTC)[reply]
  1. Disagree. We simply have to make the choice that causes the "least harm". The harm of deadnaming is documented. Applying BLP would say that we do not deadname unless the subject has specifically said they want to be identified by past name and gender pre-transition. Jenner has not issue such a statement. Skyerise (talk) 16:15, 7 June 2015 (UTC)[reply]
    Who are you to say that this does no harm? Jenner might be proud of past achievements regardless of the name. She might see the recent name change as an achievement in itself, she may even want to keep the the old records as they are. The point is that you don't know and arbitrarily making decisions for people when they haven't asked you to is grossly disrespectful, as well as violating WP:NPOV. Your decision to decide what Jenner wants without asking her may be doing immense harm. --AussieLegend () 16:24, 7 June 2015 (UTC)[reply]
    Since when did we get out of the encyclopedia business and start judging harm in relation to factual information? If some dude is convicted of murder we certainly say so even if he claims he didn't do it and it hurts him emotionally to read about it. We simply go with sources regardless. Fyunck(click) (talk) 16:46, 7 June 2015 (UTC)[reply]
    In the cases of interaction with others, misrepresenting the gender of one, then misrepresents the gender identification of all others involved. Certainly that is a violation of WP:BLP. In Jenner's case, saying his three wives married a woman, his six children were fathered by a woman, and in the mis-representation of Jenner's athletic performances, are some are using the MOS:IDENTITY guideline to claim (in Wikipedia's voice) that Jenner surpassed and preceded many women's athletic performances, thus denying each of other the women who achieved their record setting performances their position of notability. That is a giant snowball of individuals potentially displaced or offended by people using MOS:IDENTITY to rewrite history. I'm also going to say for the record. This is not about transphobia, it is about accurately reflecting history. But that term is getting thrown around, including at me. While my own reputation is not subject to BLP, I'm certainly offended at the base level of name calling that is part of this argument. Stick to the facts. Trackinfo (talk) 17:17, 7 June 2015 (UTC)[reply]
From GLAAD media guide -> "Unless a former name is newsworthy or pertinent, use the name and pronouns preferred...." For someone like Jenner where, who in 1976 won a gold medal in the "Men's Decathlon" and the name "Bruce Jenner" is well-known throughout the U.S. as one of the greatest Olympians of all time, both the name and gender are newsworthy and pertinent. It is true that we try to do the least harm and articles in present tense should not be written with wrong names or gender. To the extent that deadnaming is harmful, we should limit it to places where it is newsworthy or pertinent such as in the articles regarding notable historic events. What we should also call out as harmful is the parenthetical/asterisk/"pssst" campaign to make sure that Jenner's transition is mentioned as far and as wide as possible by misusing pronouns such as "she" when discussing the "Men's Decathlon" or deliberately calling out the name in the source and also the chosen name in articles that cover 40 years (such as "Caitlyn Jenner (as Bruce Jenner)" in the olympic articles. These actions don't represent a "minimal harm" activity, they represent an activist approach to making gender transition the only relevant fact in Jenner's life extraordinary life. These activities don't reduce deadnaming and don't reduce harm. Instead, they shrink the person's lifetime of accomplishments into a whisper that sounds like "pssst...she's transgender. did I mention she's transgender? you should know she's transgender" at every turn. That's harmful and counter to the objective of doing the least harm. --DHeyward (talk) 09:44, 8 June 2015 (UTC)[reply]
DHeyward I have similar views as you have presented above and wondered how you would view a proposal, where ever possible, to refer to Jenner as "Jenner" where practical in instances in which a personal pronoun might otherwise be used. GregKaye 15:33, 13 June 2015 (UTC)[reply]
That's fine except it's often difficult in a narrative. I'd prefer narratives that are present tense first. In credits and tables, though, the sources aren't changing. For example, the credits in all the kardashian episodes are "Bruce Jenner as Himself." That won't be updated by the producers and creates a quandary for sourcing and I'd rather just see the historical credit as it appears on the show with the correct wikilink back to Caitlyn Jenner. There's nothing we can do about the credits that show up in the films, records, shows, etc. How do we deal with that case? "Caitlyn Jenner as Herself (credited as Bruce Jenner as Himself)" or even "Caitlyn Jenner as Bruce Jenner" is just too much and doesn't do a thing to reduce the use of the deadname and gender identification because it's a permanent fixture of the episode - mixing names and gender calls even more attention to the deadname and gender. I'd prefer not making a big deal out of it and she is certainly aware that all the credits and memorabilia use her previous name. She's not abandoning her old name and life as much as embracing her new one and this is apparent in her childrens use of "dad" to refer to her. the gender connotation is less than the historic value as a term of endearment. We seem to be losing sight of how she is reacting in order to fit a preconceived idea of how to treat every single transgender person. --DHeyward (talk) 23:01, 13 June 2015 (UTC)[reply]

Option 3 (use both names, current name first)

  1. Support - Seems like a good compromise that respects the person's identity but informs readers of the historic name. EvergreenFir (talk) Please {{re}} 20:33, 2 June 2015 (UTC)[reply]
  2. Oppose having the Olympic records say "Caitlyn Jenner (formerly Bruce Jenner)" is a terrible idea. He won them as Bruce Jenner but now she is Caitlyn Jenner. Fyunck(click) (talk) 20:46, 2 June 2015 (UTC)[reply]
    Yes, both names with the then-current name first keeps things in the correct time context, which sounds more natural, while acknowledging and showing respect for the change. It's the sensible middle solution. This is what I suggested in my Option 1 !vote, and I don't think we need an Option 4 to cover that solution. ―Mandruss  21:00, 2 June 2015 (UTC)[reply]
    @Mandruss: So previous name first, current name in parentheses? That would work too. Honestly I think a 4th option like that would be better than having people who like that idea peppered through option 1. When this many folks are commenting, keeping things clear is useful imho. I'll make a fourth option unless someone strongly disagrees. EvergreenFir (talk) Please {{re}} 21:46, 2 June 2015 (UTC)[reply]
    @EvergreenFir: Yes, "Bruce Jenner (now Caitlyn Jenner)". Which will read better and without the linking problems of "Bruce (now Caitlyn) Jenner", by the way. I'm all for an Option 4 if you want to do it. ―Mandruss  21:51, 2 June 2015 (UTC)[reply]
    @Mandruss: Done! EvergreenFir (talk) Please {{re}} 22:08, 2 June 2015 (UTC)[reply]
    (edit conflict)@Fyunck(click): Do you mean like Cassius Clay oops I mean Muhammad Ali and Lew Alcindor (now Kareem Abdul-Jabbar) or Ahmad Rashad oops I mean Bobby Moore. Looks, we currently have no system. The three examples I just cited show three long-standing Wikipedia articles which deal with name changes in 3 different ways. The first notes the person's current name (ignoring the name they went by during the time period of the article in question) the second notes both names (but gives primacy to the name they were known by at the time) and the third notes only the name they were known by at the time, ignoring the current name. At the very least, Wikipedia should have some guidance for these situations. I'm not saying this solution is the best of the three (or perhaps more to come) options, but there needs to be some standard, which is better than no standard. --Jayron32 21:01, 2 June 2015 (UTC)[reply]
    A lot of tables don't have that kind of room. You also have to take context into it. For way more than half of Ali's boxing career he was known as Muhammad Ali, not Cassius Clay. Same with Abdul-Jabbar (Lew Alcindor). In their field they had dual names and it makes sense to choose the more prominent one in their field. Jenner in sports was only known by one name, Bruce Jenner. The sports fields should reflect that and it's why there is notability in the first place. Just redirect to her current name of Caitlyn Jenner and all will be well. Fyunck(click) (talk) 05:03, 3 June 2015 (UTC)[reply]
    Yes, by wholesale ex post facto name changing, wikipedia has the FACTS wrong at your link, against the sources at the time. Cassius Marcellus Clay Jr. won the Olympic gold medal. Under that name, he had a building professional career until he defeated Liston and publicly changed his name. The name Muhammad Ali was publicly unheard of, associated to that individual, until AFTER the Liston fight. I dare anybody to find a source written before the Liston fight that refers to him that way. And the wikipedia article for Ali correctly reflects that history. Same story with Kareem Abdul-Jabbar; find any coverage written during his UCLA career under that name. John Wooden referred to him as Lewis his entire life. Find a 1969 source reporting the NBA draft, what name goes #1? In other places I have shown Olympic athletes, particularly females, change their public names at given points in their career; Mary Decker -Tabb -Slaney,.and we report their name at the time. Trackinfo (talk) 21:48, 2 June 2015 (UTC)[reply]
    @Fyunck(click): Please use the correct pronouns. Even when speaking of Caitlyn in the past, the pronouns are her/she. We had major problems with this during the Manning dispute. EvergreenFir (talk) Please {{re}} 21:43, 2 June 2015 (UTC)[reply]
    What? Bruce Jenner was a he when he won the decathlon. Bruce Jenner was born a he. Today Caitlyn is a she. That is proper enough by my book. You can put in this encyclopedia whatever you'd like, but I won't be bound to it on a talk page. Back to the story at hand, in tennis the ladies get their names placed in charts as they were at the time they won tournaments. If they later get married and change their names, their main bio may or may not change with the marriage, but the tournaments keep the old name that they played under. If they married while still playing tennis we weigh the proportion of tournaments played under each name in deciding what to use throughout wikipedia. Keeps it simple and easy. Fyunck(click) (talk) 23:01, 2 June 2015 (UTC)[reply]
    Again, please don't misgender. I'll post info about the arb com case related to this FYI. EvergreenFir (talk) Please {{re}} 00:58, 3 June 2015 (UTC)[reply]
    Don't order people around. If he wants to call him Bruce and "he" that's his business.69.143.188.200 (talk) 01:26, 6 June 2015 (UTC)[reply]
    No, it isn't "his business". Intentional misgendering is not acceptable on Wikipedia. There's a reason that administrators have authorized discretionary sanctions for misgendering on articles and talk pages referring to transgender people. Funcrunch (talk) 02:19, 6 June 2015 (UTC)[reply]
    I suggest you read the sanctions again. Your interepeation is faulty. Sanctions are for willful disruption. Eg tranny, heshe name calling.69.143.188.200 (talk) 02:21, 7 June 2015 (UTC)[reply]
    I read it, and I don't see it there or listed in Wikipedia policy. I don't feel I'm misgendering but I do feel you are if referring to the winner of the Olympic decathlon as a woman/she/her, since that's probably against the Olympic rules. But it doesn't bother me at all how you want to refer to Bruce or Caitlyn. It only bothers me if you start putting warning notices on my talk page about sanctioning me for some odd reason. I'm only trying to help here, but if I have to adhere to some odd political correctness when I feel I'm helping, or I have to walk on glass whenever I post... then it's probably not worth my while to lend a hand. Fyunck(click) (talk) 01:49, 3 June 2015 (UTC)[reply]
    IMO, the notice was deserved for misgendering. Here's the applicable quote from MOS:IDENTITY (emphasis added): "An exception to the above is made for terms relating to gender identity. In such cases, Wikipedia favors self-designation, even when usage by reliable sources indicates otherwise. Any person whose gender might be questioned should be referred to by the pronouns, possessive adjectives, and gendered nouns ... that reflect that person's latest expressed gender self-identification. This applies in references to any phase of that person's life, unless the subject has indicated a preference otherwise. Direct quotations may need to be handled as exceptions (in some cases adjusting the portion used may reduce apparent contradictions, and "[sic]" may be used where necessary)." Skyerise (talk) 14:12, 5 June 2015 (UTC)[reply]
    You'll notice it was talking of titles and prose, and did not say discussion pages. It's different from your WP:Battleground notice and probably why you threw it at me. Fyunck(click) (talk) 08:53, 6 June 2015 (UTC)[reply]
  3. Oppose. Introducing anacrhonisms degrades the historical accuracy, and therefore degrades this project. Resolute 16:11, 3 June 2015 (UTC)[reply]
  4. Support 3 and 4 This strikes a good balance between accuracy (which requires using the current name) and readability (which requires including the previous name). Regardless of whether Jenner was really born he and changed, really born he and didn't change, or really born she and mistaken for he, the jury's still out on the truth of it. The polite thing to do in the meantime is take Jenner at her word. We can always change it back to "Bruce" if hard evidence ever proves us wrong. Darkfrog24 (talk) 18:27, 3 June 2015 (UTC)[reply]
  5. I'm not expressing a specific support or opposition to this proposal. There are probably times, specifically in an introductory situation to a longer paragraph, where this might be appropriate. As far as for athletic results or other involvement in timely events, we should be consistent across all of wikipedia and use the name that was published at the time. To do otherwise violates the sources at the time and would put wikipedia at odds with reports of the events. We can wikilink to the article that will further explain the name changes these individuals have adopted later in life. That would go for athletes who changed their names for any reason religious (Cascius Clay, Lew Alcindor), marriage or theatrical purposes (Chad Ocho Cinco). And so if it is a potentially confusing situation, we should have the option to explain where needed. That absolutely does not mean, in the Jenner situation, that we need to put Caitlyn in every result or credit. As I posted into Talk:Caitlyn Jenner, those marks were set by a male athlete named Bruce Jenner and will never qualify to be accepted as women's marks, no matter what the current chosen name is. To put wikipedia policy above what the press reported and what the world governing body accepts means wikipedia policy needs to be changed to adopt to us reporting reality. We should all know; failure to report proper information; to report just what the primary source wishes to be published without perspective is wrong. Trackinfo (talk) 23:40, 3 June 2015 (UTC)[reply]
  6. Oppose a general rule like this. Case by case, use common sense. Carrite (talk) 01:02, 5 June 2015 (UTC)[reply]
  7. Support 3 or 4 without preference (I'm double-voting, sorry, but this discussion looks like it can't be tallied by # anyway). Either "Caitlyn Jenner (then Bruce Jenner)" or "Bruce Jenner (now Caitlyn Jenner)" seems fine to me. The important thing here, as I see it, is to write in a way that is respectful of her identity but still useful and clear to Wikipedia editors, and omitting the male name from athletic events that were and still are male-only doesn't serve the latter goal. –Roscelese (talk ⋅ contribs) 13:45, 5 June 2015 (UTC)[reply]
  8. Support in context of athletic accomplishments, as a compromise between respect for the athlete and accuracy to the sources. I slightly prefer this option over option 4 because it places respect for the athlete first. --Alison (Crazytales) (talk; edits) 14:27, 5 June 2015 (UTC)[reply]
    Clarification: I think this should apply to athletes who change their name for non-gender-related reasons too, like the oft-aforementioned examples of Mohammed Ali, Karim Abdul-Jabbar, and Metta World Peace. --Alison (Crazytales) (talk; edits) 14:30, 5 June 2015 (UTC)[reply]
  9. Support along with option 4. With both names listed and a footnote explaining the transition, there will be no confusion and it is not "rewriting history". Funcrunch (talk) 15:01, 5 June 2015 (UTC)[reply]
  10. Oppose per Fyunck and Resolute's comments above. Historical reality is what it was; present reality is what it is. Change is a universal constant, and life is messy. Imposing retroactive and anachronistic solutions on history is a bad idea; and it's an even worse idea when it's ideologically driven. Bruce Jenner now redirects to the Caitlyn Jenner-titled article; let the bio article explain present reality, and leave the past reality alone in our sports history articles. Dirtlawyer1 (talk) 17:12, 5 June 2015 (UTC)[reply]
  11. Support 3 or 4 without preference per Roscelese. We are in the business of clearly and concisely conveying information. We should convey what name was in use at the time. We should also connect that to the current name. We should avoid making any assumptions about how familiar people might be with the subject, or assume that they will follow every single link. I don't see how indicating "Her name was X at the time, but you may now know her as Y", is anachronistic, and it can be done clearly and concisely in two words.--Trystan (talk) 18:54, 5 June 2015 (UTC)[reply]
  12. Support along with option 4. I would prefer this option but I would be satisfied with either. This avoids confusion and respects her identity. If people want to put her former name for verifiability purposes, I would be fine with that. Options 3 and 4 don't bring up a "historical revisionism" argument or a "not respecting identities argument", and both are relatively concise and easy to do. BenLinus1214talk 20:35, 5 June 2015 (UTC)[reply]
  13. Oppose We don't need both names. We have redirects to avoid that. --AussieLegend () 14:09, 6 June 2015 (UTC)[reply]
  14. Support along with option 4, per Roscelese. I have a slight preference for this option as it puts her current name first but I would be fine with option 4. These two options avoid rewriting history, accurately summarize the situation as it happened (which is that she won the medal while competing as Bruce Jenner), and respects the person's gender. Ca2james (talk) 16:08, 6 June 2015 (UTC)[reply]
  15. Support This option or option 1. People change their names for all sorts of reasons, including having different names in different languages, marriage and divorce, gender transition, personal beliefs, or for career purposes (like actors). Beyond the most important reason, of respecting a person's chosen identity and gender, flip-flopping between names is cumbersome, confusing, and prone in inconsistency. If it is truly important, a person's former name can/should be noted - but they should not be identified by that name (or certainly the adherent gender). TMagen (talk) 16:50, 6 June 2015 (UTC)[reply]
  16. Support this (as my second choice); see my comments above about option 2. -sche (talk) 17:59, 6 June 2015 (UTC)[reply]
  17. Support: Good compromise between identifying people by what they are called today and not confusing readers who know them by a previous name. --Guy Macon (talk) 18:06, 6 June 2015 (UTC)[reply]
  18. Oppose Why should articles, that aren't even about a particular person, have to include a history of that person's name/gender changes? Surely the only relevant name/gender is the one they had at the point they are relevant to the article? Anything further is setting off on a tangent leading the reader away from the point. Do we have a policy like this for those who change name through multiple divorces? --Escape Orbit (Talk) 18:22, 6 June 2015 (UTC)[reply]
  19. Oppose This is incorrect for the same reason as Option 2: anachronism. I don't see anything transphobic or discriminatory, when talking about past events, about mentioning the persona that the transgender person assumed publicly and socially at the time. It's a whole different matter than in an article where this person is the main topic, as many discussions here have established. Option 4 is descriptive enough, and corrects this issue. Place Clichy (talk) 12:09, 8 June 2015 (UTC)[reply]
  20. generally acceptable particularly in cases where the person was significantly notable before "coming out" or where BLP concerns about other living people are involved. -- TRPoD aka The Red Pen of Doom 20:11, 9 June 2015 (UTC)[reply]
  21. Support in Jenner's case and within sports related articles. I don't think that this applies will apply to all other biography related articles. I think that all pronoun use should be avoided as confusing for readers if an unexpected pronoun is used and potentially offensive if it is not. 14:29, 12 June 2015 (UTC) revised GregKaye 15:47, 13 June 2015 (UTC)[reply]
  22. Support This seems like a sensible compromise that balances the "high degree of sensitivity" required by BLP with the need to avoid confusion. Neljack (talk) 07:47, 13 June 2015 (UTC)[reply]
  23. Support per Neljack. Ed [talk] [majestic titan] 03:41, 14 June 2015 (UTC)[reply]
  24. Support, with the conditional that it's context-sensitive and the old name could sometimes be omitted (and probably only needs to be mentioned the first time they come up in an article.) In general this seems like the best compromise; it clearly respects their identification, while providing enough information that people who are only familiar with that section of history using their old name will be able to follow the article. As I said in my comment for option 2, though, I feel the old name could be left out in situations where there's unlikely to be any serious confusion. --Aquillion (talk) 07:14, 14 June 2015 (UTC)[reply]
  25. Oppose for the same reasons I oppose option 2. The historical name should be used for referencing historical events. Rreagan007 (talk) 02:26, 21 July 2015 (UTC)[reply]

Option 4 (use both names, previous name first)

  1. Support along with option 3. EvergreenFir (talk) Please {{re}} 22:07, 2 June 2015 (UTC)[reply]
  2. Support - Agree that it would be entirely confusing to refer to Caitlyn Jenner competing in men's sports. Are we to assume that official Olympics records have been updated to change Bruce to Caitlyn? Seems very unlikely to me. Both names with the then-current name first keeps things in the correct time context, which sounds more natural, while acknowledging and showing respect for the change. It's the sensible middle solution. ―Mandruss  22:12, 2 June 2015 (UTC)[reply]
  3. Support. This is how a majority of publishers handle the issue. Wikipedia should not blaze a new trail on this issue. Binksternet (talk) 23:02, 2 June 2015 (UTC)[reply]
  4. Support I would support this proposal as well as it lies in the middle more. - Knowledgekid87 (talk) 01:02, 3 June 2015 (UTC)[reply]
  5. Support The talk page for the article on the Decathlon now has this: We can debate the name, but there's no question that Caitlyn is a notable exception to the statement that men typically compete in the decathlon and women in the heptathlon. A woman who has accomplished the amazing feat of winning the Olympic decathlon - an event completely dominated by males -deserves at least a statement about it in this article. Simply putting Caitlyn Jenner would encourage such thinking.Richardson mcphillips (talk) 02:18, 3 June 2015 (UTC)[reply]
  6. Support Although I personally prefer Option 3, per my note in the General Discussion about how cis athlete name changes have been handled on Wikipedia, I think this option is a reasonable compromise. Funcrunch (talk) 04:56, 3 June 2015 (UTC)[reply]
  7. Support. This is the compatible with MOS:IDENTITY, factual and informative, so I don't think they are disrespectful. I don't care much between options 3 and 4, though this one is gaining traction and more likely to lead to consensus (see that many people supporting Option 1 agreed to use both names, and were made bephore options 3 and 4 were created). Diego (talk) 13:44, 3 June 2015 (UTC)[reply]
  8. Support. In the 1976 men's Olympic decathlon, Caitlyn Jenner competed under the name "Bruce Jenner". Excluding "Caitlyn" from the article could be taken as an affront to Jenner (and would likely lead to well-meaning new users putting "Caitlyn" back in). Excluding "Bruce" would create unnecessary confusion (and would also likely lead to well-meaning new users putting "Bruce" back in). The name that Jenner competed under should be listed first, followed by her current name. Howicus (Did I mess up?) 16:20, 3 June 2015 (UTC)[reply]
    Wait. Are you seriously proposing to alter history on the basis of not "causing affront"? Do you realize just what kind of slippery slope that is? Resolute 16:30, 3 June 2015 (UTC)[reply]
    Compiling new knowledge is not rewriting history, it's adding to it. Please don't use such hyperboles. Diego (talk) 16:37, 3 June 2015 (UTC)[reply]
    It's not hyperbole. Retroactively changing names of historical record is rewriting history. At the very least, if you are going to do it, do it consistently and go retroactively change the name of every person who later changed their name - either by marriage or for other reasons. Resolute 16:54, 3 June 2015 (UTC)[reply]
    There are countless examples of names being updated in historical listings after an athlete, actor, or other public figure changes their name. I cited one example in the General Discussion below: Muhammad Ali's name listed with Cassius Clay in parentheses for the list of heavyweight boxing champions. Go to a few movie cast listings and you'll see "Joe Schmo (as John Schmo)". Cis people change their names all the time and get acknowledged without people complaining about "rewriting history". It's really not that different here. Funcrunch (talk) 03:36, 4 June 2015 (UTC)[reply]
    And as was explained before, Ali was notable because he was a boxer. We only get one title and Muhammad Ali was chosen over Cassius Clay because it was much more notable. In lists where people are counting victories and stuff it is much better for readers to be consistent instead of putting in both Cassius Clay and Muhammad Ali. If Jenner had also competed a good chuck of her sports lifespan as Caitlyn, then we would have to decide which is better for our readers to follow. Which was more notable in sports/Olympics/track and field events, etc... But that's not the case here. We had to make decisions about tennis great Helen Wills notability and whether we should title her article that or Helen Wills Moody. We went with the former because it was more notable. These decisions are made all the time and editors are usually pretty reasonable on coming to a conclusion. But forcing a conclusion on past historical events because of a sex-change that happened long after sports retirement, doesn't sit too well with the wikipedia way of doing things. At least not from my vantage point. Fyunck(click) (talk) 09:11, 4 June 2015 (UTC)[reply]
    Actually, I would disagree with both of you and offer a more simple reply: The existence of a mistake made in the past does not represent a justification for repeating that mistake in the present. The proper solution here is to correct those other anachronisms, not create more. Resolute 13:29, 4 June 2015 (UTC)[reply]
    Excluding "Caitlyn" from the article could be taken as an affront to Jenner... Not to mention that excluding it would also be confusing, since Caitlyn Jenner is the title we use for the biography. Both names need to be connected for the sake of those of us editors who have first learned about this person from her Wikipedia article. Diego (talk) 16:35, 3 June 2015 (UTC)[reply]
  9. Oppose. Introducing anacrhonisms degrades the historical accuracy, and therefore degrades this project. Resolute 16:12, 3 June 2015 (UTC)[reply]
    That would be a decent argument to oppose Option 2 or Option 3, since they both would state that Caitlyn Jenner won gold in the decathlon. It is not anachronistic to say that Bruce won the medal and is now named Caitlyn, any more than it would be anachronistic to update Thomas Jefferson with facts related to Jefferson's legacy in the 21st century. Articles are not frozen in time. ―Mandruss  16:32, 3 June 2015 (UTC)[reply]
    We're talking about different things here. Updating Jefferson's own article with changes to his legacy is not the same as altering the historical record of articles about the 1976 Olympics by introducing an anachronistic name change. I completely understand that people want to avoid a repeat of the Chelsea Manning mess; respecting the individual as she wishes to be viewed in her biography, and in other articles related to her person, is laudable and desirable. But changing the historical record of her competitions respects neither WP:BLP nor the individual. Rather, it is a violation of WP:SYNTH, WP:POV and others. Resolute 16:54, 3 June 2015 (UTC)[reply]
    I'm sorry, but I still think you're arguing under the wrong Option. Option 4 does not change anything about the competition, it merely inserts a parenthetical note about a later name change. There is nothing even remotely improper about doing that. ―Mandruss  17:26, 3 June 2015 (UTC)[reply]
    No, I am arguing under the correct option, and I maintain my opposition for my stated reason. Resolute 18:41, 3 June 2015 (UTC)[reply]
  10. Support using historic gender and name in articles talking about past events, making note of the new name/gender in a parenthetical. I find it preferable to have the past name first in these situations hence, "Bruce (now Caitlyn) Jenner" or "Ron Artest (now Meta World Peace)". With Artest, since his career in basketball continues, I would even be inclined to use that format for things he did before the change, and for things he did after the change say "Meta World Peace (formerly Ron Artest)" to preserve the continuity and make clear that this is the same person; but I wouldn't necessarily connect Bruce with Caitlyn going forward - just backwards, as she's no longer a competitive athlete; I'd only do that where relevant. To be clear, what I'd like to see with Jenner: when discussing his previous life and accomplishments, refer to him as a male named Bruce and note that she is now a female going by Caitlyn. When discussing her current life and accomplishments, refer to her as a female named Caitlyn. Explain the situation wherever clarification is needed. ~ ONUnicorn(Talk|Contribs)problem solving 18:18, 3 June 2015 (UTC)[reply]
  11. Support 3 and 4 This strikes a good balance between accuracy (which requires using the current name) and readability (which requires including the previous name). Regardless of whether Jenner was really born he and changed, really born he and didn't change, or really born she and mistaken for he, the jury's still out on the truth of it. The polite thing to do in the meantime is take Jenner at her word. We can always change it back to "Bruce" if hard evidence ever proves us wrong. Darkfrog24 (talk) 18:29, 3 June 2015 (UTC)[reply]
  12. Oppose - there would be times that this format would be helpful, but not as blanket coverage for all things in her past life. Especially not for Olympic records and such. Fyunck(click) (talk) 23:18, 3 June 2015 (UTC)[reply]
    @Fyunck(click): In your Option 3 oppose you say, "He won them as Bruce Jenner but now she is Caitlyn Jenner." That is precisely what Option 4 says, so I don't understand your oppose here. Further, the description of Option 4 is quite clear that it is not "blanket coverage for all things in her past life". ―Mandruss  08:32, 4 June 2015 (UTC)[reply]
    That was simply a statement, not what should be done to every article. And it's quite clear that it is blanket coverage so I'm not sure what you're reading. The description says "In articles outside of the biography itself, use the person's previous name, but include current name in parentheses. Would be used when previous name is relevant or listed in a historical context (e.g., list of sports awards). Example, in a list of Olympic gold medalists, the entry Bruce Jenner (now Caitlyn Jenner) would be used. That is pretty much every time as far as I can tell. The Olympics in particular should say simply "Bruce Jenner" and the redirect will take care of the rest. Fyunck(click) (talk) 08:53, 4 June 2015 (UTC)[reply]
    @Fyunck(click): Maybe the language could be clarified even further, but I don't read it as applying to all references prior to June 2015. My clues are "when previous name is relevant" — it won't be especially relevant in all cases — and "e.g., list of sports awards" — it's relevant in our example case because of the official records and widespread news coverage using the old name. In other words, if we currently mention somewhere (outside Caitlyn Jenner) that Bruce Jenner broke his arm in 1970, I don't have a problem with changing that to "Caitlyn Jenner" or "Caitlyn Jenner (then Bruce Jenner)", and I don't think Option 4 would preclude that usage. That would be a case not covered by guideline and therefore local discretion. EvergreenFir crafted the Option 4 language, so perhaps s/he would care to weigh in here. As for whether to include "(now Caitlyn Jenner)" in the Olympics reference, see the comment in my !vote, "It's the sensible middle solution." What I meant by that is that some give is required on both sides if we're going to reach a consensus here. Option 4 requires one side to mention the name "Bruce" in that case, despite their desire to omit it, and requires the other side to mention "Caitlyn" in that case, despite their desire to omit it. It's a compromise, and that's not the dirty word that many seem to think it is at Wikipedia. "The redirect will take care of the rest" assumes that the reader will click through to the target article, and that will often not be the case. ―Mandruss  10:38, 4 June 2015 (UTC)[reply]
    @Mandruss:I agree 100% with you that compromise is not a dirty word (like it has often become on wikipedia). Here is how I read Option 4 (and I don't see any other way to interpret it). "We always use Caitlyn Jenner in place of Bruce Jenner. But in rare cases outside the biography, when relevant, it will be ok to use Bruce Jenner (now Caitlyn Jenner). That's it... no other options." To me that's not right and is blanket coverage. Now if it had said something like the following I might be more likely to support: After June 2015 we will generally use 'Caitlyn Jenner.' There will be some uncommon times after June 2015 where it will be appropriate to use 'Caitlyn Jenner (formerly Bruce Jenner).' Prior to June 2015, when dealing with sports in lists, she will be shown as 'Bruce Jenner.' When talking in prose about the sports achievements, the first mention should be 'Bruce Jenner (now Caitlyn Jenner)' and all subsequent use should simply be 'Bruce Jenner.' When not talking about sports achievements, prior to June 2015, it will depend on the situation as to whether first use should be 'Bruce Jenner (now Caitlyn Jenner)' or 'Caitlyn Jenner (formerly Bruce Jenner)', but usually Caitlyn Jenner (formerly Bruce Jenner) will be preferred. As in saying in '1970 Caitlyn Jenner (formerly Bruce Jenner) broke her arm.' But perhaps also '100 year old farmer John remembers sitting little 2-year-old Bruce Jenner (now Caitlyn Jenner) on his knee and telling the boy about how fast he ran when chased by a bull." This allows some flexibility in usage. To me that's more like compromise. But I didn't write the options nor did I come in here with an agenda. I happened to notice it when dealing with a different situation. That's my two cents, but as it is written I can not support this option. Fyunck(click) (talk) 18:56, 4 June 2015 (UTC)[reply]
    Something tells me some clarification is needed, if we disagree this much on the meaning of three sentences. But your proposed interpretation would be incomprehensible to the average editor. Try putting that in a new Option 5 and see if you get any !votes besides your own (include a flowchart please). Nothing like this ever needs to be that complex, and complexity is our enemy when it comes to guidelines. ―Mandruss  20:06, 4 June 2015 (UTC)[reply]
    Well, @EvergreenFir: wrote option 4. Ask her to clarify the exact meaning since you might be voting for something you don't want. You had asked for compromise and mine is a compromise. It is long but could certainly be shortened. I was simply trying to convey how I thought the usage of Jenner should be handled in a way that I could support it. Fyunck(click) (talk) 21:25, 4 June 2015 (UTC)[reply]
    Pinged with no answer so I'm thinking it's probably what I had said. Fyunck(click) (talk) 16:50, 7 June 2015 (UTC)[reply]
  13. Support: I think option 1 is the most practical (since a redirect --or a piped link-- ensures the later identity is correctly indicated), but if the person in question expresses that such treatment would bother them, then this is the right compromise, I think. --Waldir talk 10:14, 4 June 2015 (UTC)[reply]
  14. Oppose a general rule like this - Case by case, use common sense. Carrite (talk) 01:01, 5 June 2015 (UTC)[reply]
  15. Oppose. Ironholds (talk) 01:55, 5 June 2015 (UTC)[reply]
  16. Oppose One of our roles as Wikipedia editors is to get the facts right. The fact is Caitlyn Jenner has always been a woman, was a woman when she competed in her various Olympic events, and should be recognized as a woman. I see that some are objecting to this on the basis that it's just self-evident that a woman could not have won the decathlon competition in 1976. While it's completely up to the IOC to list the winners how they wish, it's up to use to get it right. There's no real debate that Caitlyn won the Decathlon in the Montreal Olympics. We need to recognize that fact and let people know of that reality. Listing "Bruce Jenner" as the winner is revisionist history - it's pretending that someone besides Caitlyn won. Similarly, Caitlyn needs to be recognized for her other athletic accomplishments. Among those are:
    1) Being the best female performer over 100 meters in 1976
    2) Being the best female performer over 400 meters, ever
    3) Being the best female performer in the high jump in 1976
    4) Being the best female performer in the long jump in 1976
    5) Being the best female performer in the decathlon, ever.
    Again, it is up to the IAAF to ratify times how they see fit. However, it's our duty to note the facts - (1) Caitlyn is a woman, (2) Caitlyn has always been a woman, and (3) Caitlyn actually achieved all these performances.
    One of our other important roles as Wikipedia editors is to be effective advocates for social justice. We cannot do this if we commit violence on trans* people by misgendering or deadnaming them. By denying Caitlyn - and the trans* community as a whole - ownership over her own athletic performances, we are erasing her identity for our own comfort. I strongly strongly strongly urge that "Caitlyn" be used universally. 2602:306:808C:2100:7D00:A53D:7E6:9379 (talk) 15:12, 6 June 2015 (UTC)CaitlynFan[reply]
    You seem to be under the misinterpretation that the role of " Wikipedia editors is to be effective advocates for social justice". It is not. -- TRPoD aka The Red Pen of Doom 16:03, 6 June 2015 (UTC)[reply]
    We can advocate social justice while still staying within those suggestions. Reporting the facts - as relayed to us by reliable media sources - can be social justice advocacy. For instance, saying "Caitlyn Jenner had the fastest 100 meters of any woman in 1976" is NOT original research. If we said "The IAAF should ratify Caitlyn Jenner's 1976 100 meters as the fastest by any woman in that year" we might be taking it too far. However, simply stating the facts - (1) Caitlyn is a woman, (2) Caitlyn ran faster than Annegret Richter in 1976 - is not going beyond any rule you cited to. 2602:306:808C:2100:7D00:A53D:7E6:9379 (talk) 16:12, 6 June 2015 (UTC)CaitlynFan[reply]
    I'm sorry, but that's just ridiculous. You are first of all an obvious sock since that user's only edits have been to vote here, and second, you are an obvious troll as well trying to delegitimise the conversation by saying extremist things that transgender women would never claim. I'm trans and I think you're trying to dirty the pool to make trans people look both extreme and kind of awful as well. Ogress smash! 08:40, 7 June 2015 (UTC)[reply]
    I believe that the original piece was second-degree humour, and/or reductio ad absurbum. In this light, I enjoyed reading it. However, for the sake of clarity and now that the IP is blocked, it may be a good idea to bar the vote. Place Clichy (talk) 12:09, 8 June 2015 (UTC)[reply]
  17. Oppose, forces transgender individuals to be identified using a name that emphasized their past gender first. Uncool. Skyerise (talk) 12:03, 5 June 2015 (UTC)[reply]
    That's a seriously problematic phrasing. There is no "past gender." She was always a woman. It's this sort of clueless phrasing that makes dealing with allies so difficult. 162.235.91.193 (talk) 20:35, 5 June 2015 (UTC)CaitlynFan[reply]
  18. Support 3 or 4 without preference (I'm double-voting, sorry, but this discussion looks like it can't be tallied by # anyway). Either "Caitlyn Jenner (then Bruce Jenner)" or "Bruce Jenner (now Caitlyn Jenner)" seems fine to me. The important thing here, as I see it, is to write in a way that is respectful of her identity but still useful and clear to Wikipedia editors, and omitting the male name from athletic events that were and still are male-only doesn't serve the latter goal. –Roscelese (talk ⋅ contribs) 13:45, 5 June 2015 (UTC)[reply]
  19. Oppose per Fyunck and Carrite, and for the reasons of historical accuracy which I expressed under Option 1 above. When someone has been a prominent public sports figure as a man, common sense suggests that we should not attempt to rewrite history to reflect later transgender revelations. We can and should acknowledge the present reality of Jenner's gender identity with compassion and sensitivity, but attempting to rewrite 65 years of the personal gender history of a prominent public figure is divorced from reality. Dirtlawyer1 (talk) 17:22, 5 June 2015 (UTC)[reply]
  20. Support along with option 3. See my comment there. Both make sense to me. BenLinus1214talk 20:36, 5 June 2015 (UTC)[reply]
  21. Oppose We don't need both names. We have redirects to avoid that. --AussieLegend () 14:11, 6 June 2015 (UTC)[reply]
  22. Support along with option 3, per Roscelese. I have a slight preference for option 3 as it puts her current name first but I would be fine with this option, too. These two options avoid rewriting history, accurately summarize the situation as it happened (which is that she won the medal while competing as Bruce Jenner), and respects the person's gender. Ca2james (talk) 16:09, 6 June 2015 (UTC)[reply]
  23. Support this (as my third choice); see my comments above about options 2 and 3. -sche (talk) 18:00, 6 June 2015 (UTC)[reply]
  24. Oppose Per my opposition to Option 3. Why should articles, that aren't even about a particular person, have to include a history of that person's name/gender changes? Surely the only relevant name is the one they were known by at the point they are relevant to the article? Anything further is setting off on a tangent leading away from the point. Do we have a policy for this for those who change name through multiple divorces? --Escape Orbit (Talk) 18:24, 6 June 2015 (UTC)[reply]
  25. Support Although it is wrong to say that a person (actually, a persona) participated in an event when they didn't, it is perfectly relevant to mention their subsequent change. Place Clichy (talk) 12:09, 8 June 2015 (UTC)[reply]
  26. Support as "Bruce Jenner (now Caitlyn Jenner)" Oppose use of pronouns when practical and when "Jenner" would suit. GregKaye 15:50, 13 June 2015 (UTC)[reply]
  27. This would also be an acceptable compromise, though I prefer option 3 since it puts the emphasis on the subject's self-identification and thus better fulfils BLP's requirement of a "high degree of sensitivity". Neljack (talk) 07:52, 13 June 2015 (UTC)[reply]
  28. Weak support. I prefer option 3, since it respects their self-identification more clearly, but in terms of clarity this would at least be better than using only one name, and it doesn't ignore their self-identification entirely. --Aquillion (talk) 07:16, 14 June 2015 (UTC)[reply]
  29. Partial support: I'm mostly going with Option 5, but my reasoning there makes Option 4 the default for most cases that fit the criteria a) context pre-dates the name change, and b) the name-at-the-time is important; for other cases see my Option 5 comments. Also, don't be hidebound about it; the exact formatting and wording need not be set in stone; sometimes a simple piped link will work fine, especially in lists and tables.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  17:26, 14 June 2015 (UTC)[reply]
  30. Support as most closely satisfying the condition that we recognize the subject's current identification (as Caitlyn) and that we provide accessible information (and so a person who has seen the name Bruce Jenner in an article about those olympics someplace should not be thoroughly confused). To those people who believe this is incorrectly gendering Caitlyn; we cannot speak to how Caitlyn experienced gender back then, but Caitlyn did present the name "Bruce" to the world, and that's all we are saying, I believe. Vanamonde93 (talk) 03:31, 15 June 2015 (UTC)[reply]
  31. Support per Roscelese and others (I'm also good with option 3 if the consensus it for that). I believe that without this, the information in sporting events (as an example) would not make sense to a reader not familiar with their recent lives. --Gonnym (talk) 09:50, 18 June 2015 (UTC)[reply]
  32. Strongly Support This, or perhaps option 3, is probably the best choice in most cases. It preserves historical accuracy by clearly indicating who was identified, and how, for historic accomplishments or as a participant in historic events. Yet it also makes a clear link to the preswent, and provides a rader with both possibly useful search terms to learn more about the person involved. This is they way we should help our reders, by presentign the full facts, not a distorted revision of them, nor one thast ignores relevant later developments. DES (talk) 12:28, 18 June 2015 (UTC)[reply]
  33. Oppose for the same reasons as I opposed options 2 and 3. The historical name should be used when referring to historical events. Rreagan007 (talk) 02:27, 21 July 2015 (UTC)[reply]

Option 5 (no new rule, treat on a case-by-case basis)

  • Support option 5: no way the 1976 Summer Olympics article is ever going to be *exactly* the same as the United States v. Manning article or Rape in Germany (§ Notable offenders, third bullet), or 1968 in music (§ Release Date Unknown, last of the entries starting with S), or 12th Annual Grammy Awards (§ Classical, 5th bullet), etc., so any new rule that is passed as an "ad hoc" solution for the first case is going to have a destabilising effect on other pages that seem to have found some sort of equilibrium the way they are now, but with different solutions. Editor discretion is what is needed in all of those cases, not bulldozering in a new rule, which to all extents and purposes would be instruction creep. So if this RfC comes to a conclusion w.r.t. Jenner in the 1976 Summer Olympics article I'm fine with that, but I don't see any reason to extrapolate to remotely similar cases. --Francis Schonken (talk) 20:39, 10 June 2015 (UTC)[reply]
  • Oppose. The current set of rules are not broken and do not need fixing. --Guy Macon (talk) 02:36, 11 June 2015 (UTC)[reply]
    • ? exactly what I meant: don't change the current rules (they seem to work pretty well for the main biography pages, and that includes the rules I added [3]), don't add new restrictive ones (for the subsidiary, event and overview pages mentioning the person exclusively in an earlier period: approach these in a case-by-case logic, exerting caution, good taste, editor discretion) – nothing broken, nothing needs fixing. --Francis Schonken (talk) 05:57, 11 June 2015 (UTC)[reply]
    Also: keep current specific guidelines where they are now, i.e. below "policy" level, thus allowing for the occasional exception when circumstances warrant it (per usual guideline provisions). --Francis Schonken (talk) 09:40, 11 June 2015 (UTC)[reply]
Yeah, Macon clearly meant "oppose new rules".  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  17:20, 14 June 2015 (UTC)[reply]
  • Support, but explain the options: Not a "rule" per se, just give examples. I'll draft them right now: Don't be hidebound about details; the exact formatting and wording need not be set in stone. Original-then-current works best when the context pre-dates the name change and in which the name-at-the-time is clearly important. When it's not (but still pre-dates the name change), use current-then-original in most cases, though current-only can work in cases where the name/gender is totally irrelevant (to everyone, not just gender language activists). When it post-dates the name change, use current-only, unless the former name is genuinely relevant, in which case use current-then-former. Former-only is never appropriate, in the form [[Bruce Jenner]] but may work fine as [[Caitlyn Jenner|Bruce Jenner]], especially in tables or lists. Inserting "now Caitlyn Jenner" or whatever at every single instance would be WP:POINTy browbeating; do it once per article (or occasionally more frequently; use the same rubric as for appropriate vs. over-linking). Avoid gender-specific language in all these cases, so the he/man vs. she/woman issue simply vanishes. Short version: Use common sense and rational thinking, focused on reader's needs and expectations, not how you personally want to change the world. PS: This analysis doesn't even have anything (other than the avoid gender-specific language bit) to do with gender. I would treat David Johansen vs. Buster Poindexter exactly the same way. [Or would; looks like he's gone back to Johansen after becoming mostly-independently notable under the later name for a while. That actually makes him an interesting test case, but I don't want to lay out a big logic tree about how to treat coverage of him in three different periods but under two names, right in the middle of this more focused discussion.]  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  16:53, 14 June 2015 (UTC)[reply]
  • Don't let this proposal distract us. The current rules were clearly written by a consensus tipped by advocates in violation of WP:SOURCE amongst other policies. They knew they were violating a policy at the time and had to write the exception into the guideline. Some cases are more equal than others. The rules are broken and need to be fixed. A band aid doesn't fix the problem, in fact a temporary solution only lasts until someone rewrites each article affected. We need a policy ground to stand on not excepted by a misguided guideline. Any other identity change, essentially name changes, are treated with a time base. There is an announcement date for the new identity. Usually it can be precisely defined though some cases come out of the closet more ambiguously. Sometimes nicknames evolve into a notorious stage name over a period of time, but even then, there is a range that can be defined and frequently there is a story behind it, which wikipedia should tell. Back to the original point, the information is there in contemporary sources. They don't go back and reprint newspapers with new names.
We've dealt with this before, we have examples and a precedent. Not even his birth name, "Duke" Morrison was credited in his first movie in 1929, John Wayne became the credited name in 1930. We've discussed before, Cassius Clay won the gold medal and beat Sonny Liston. He went by Cassius X. for a month but Muhammad Ali is the boxer the world came to know. If you were alive at the time, you would remember that was contentious too based on different prejudices than the current transgender situation. The point is, we should not go back in time and rewrite history. This is not fiction. We/wikipedia should report accurately what happened. The MOS:IDENTITY should be rewritten to conform to current policies. Trackinfo (talk) 08:10, 17 June 2015 (UTC)[reply]
Maybe there's a conflation of two different issues here, falling under different sets of policies/guidelines:
  1. Article title, falling under WP:AT, and particularily relevant, under WP:SPNC:
    → all following the same rules, whether there's a physical sex change or not: such change does *not* automatically lead to the article being moved to the new name (FYI, Beate Schmidt for the last of the examples listed above). As such not falling under whatever the MOS page WP:IDENTITY has to say on the topic.
  2. How the subject is referred to in secondary articles:
    → Works fine without the MOS needing a rewrite...; the MOS doesn't even say anything about which first name should be used where, editor discretion rarely leads to problems here (see for example "Schmidt was sentenced to 15 years in prison and detention in a psychiatric hospital" in Rape in Germany#Notable offenders avoiding to use "she" in combination with "Wolfgang"), and certainly not something to write a new "one size fits all" rule about. --Francis Schonken (talk) 10:20, 17 June 2015 (UTC)[reply]
Common sense would certainly be the correct option. We don't have that. We have people actively trying to post ridiculous statements like Option 4 #16 above into the wikipedia voice, using MOS:IDENTITY as the justification. Sure, the IAAF won't recognize those statements, I've explained why. Of course other sources don't report this. But those are only facts, which wikipedia should ignore in order to conform with this altered reality. It has a cascading effect. WP:BLP this affects every other displaced, legitimately female (XX) athlete over a 40 year history. Trackinfo (talk) 19:01, 17 June 2015 (UTC)[reply]
Well good, reason it out then on the page or use WP:DR, and common sense will prevail then - there will probably be several common sense solutions depending on the context -- so, you don't need VPP intervention from the top down. Alanscottwalker (talk) 19:10, 17 June 2015 (UTC)[reply]
I'll argue, others have been reverting. The problem is, and the reason I came to this discussion, MOS:IDENTITY is a current guideline that gives them the right to ignore sources and write what they want, in order to prove their WP:POINT to the general public. Fighting against a WP:POV written policy makes it harder. Trackinfo (talk) 09:25, 18 June 2015 (UTC)[reply]
MOS:IDENTITY doesn't give a right to ignore sources, the new name needs to be exquisitely sourced before it can be used. What the guideline does is encouraging editors to use more recent, up-to-date sources over older, obsolete ones that didn't know better when they were written. Diego (talk) 09:32, 18 June 2015 (UTC)[reply]
Getting Trackinfo's issue (I think), here's my response --Francis Schonken (talk) 10:04, 18 June 2015 (UTC)[reply]

Unilateral changes to MOS:IDENTITY

Francis Schonken made a bold edit to MOS:IDENTITY while this discussion was still ongoing (unclosed). I reverted it because I see no consensus for it here (and it would be best for us all to wait until this RFC is closed to see what consensus is, rather than for one involved participant to try to judge that consensus is in his favour); I also think the edit effectively repeals MOS:IDENTITY (which I see no consensus for in this discussion) and fails to understand that it is explicitly set up as "An exception..." to other criteria; it also controversially suggests that saying "she [trans woman] did x" would violate content policies — a notion which has been suggested before by a few users, but has never AFAICT gained anything even approaching consensus. Rather than proceed to discuss his edit per BRD, the same user re-inserted it, citing WP:VPP#Option 5 (no new rule, treat on a case-by-case basis, which shows two users supporting and one user opposing his idea, and which doesn't come close to the level of support other options in this thread have. The user has yet again inserted his preferred version in what certainly resembles and attempt to prejudice the outcome of this RFC, and has told me to "take it to talk", getting WP:BRD quite backwards. Can someone else look into this? -sche (talk) 18:05, 23 June 2015 (UTC)[reply]

WP:BRD? Really? see below... --Francis Schonken (talk) 07:00, 24 June 2015 (UTC)[reply]
As remarked above, MoS, a guideline, was written as to override policy. There's no policy-level agreement to do that. I removed the policy infraction, while my first attempt to only mitigate the policy-infringing statements was reverted. --Francis Schonken (talk) 18:20, 23 June 2015 (UTC)[reply]

From WP:NPOV, second and third paragraph of the lede:

NPOV is a fundamental principle of Wikipedia and of other Wikimedia projects. It is also one of Wikipedia's three core content policies; the other two are "Verifiability" and "No original research". These policies jointly determine the type and quality of material that is acceptable in Wikipedia articles, and, because they work in harmony, they should not be interpreted in isolation from one another. Editors are strongly encouraged to familiarize themselves with all three. This policy is non-negotiable, and the principles upon which it is based cannot be superseded by other policies or guidelines, nor by editor consensus.

I bolded cannot be superseded by other policies or guidelines in the above – as such a no-brainer to remove from a guideline any statements that explicitly try to supersede this.

Further: "When there is a discrepancy between the term most commonly used by reliable sources for a person or group and the term that person or group uses for themselves, Wikipedia should use the term that is most commonly used by reliable sources; if it isn't clear which is most used, use the term that the person or group uses." is an erroneous and misleading summary of the quoted policies. These policies don't let themselves be condensed to a few soundbites, otherwise these policies wouldn't have so many ifs and buts. Remove summary that only leads to non-comprehension and discussion.

Also: "Wikipedia favors self-designation" is bad style (Wikipedia is not a sentient being that can favor or disfavor whatever); and infringes both WP:NPOV (if anything Wikipedia should be neutral on the topic of self-designation) and WP:NOT (e.g. WP:NOT a means of promotion). So, remove until a more appropriate way to express this has been found. --Francis Schonken (talk) 06:46, 24 June 2015 (UTC)[reply]

You are entirely misreading IDENTITY and going against a couple years worth of discussion. Take up your beef at the village pump. EvergreenFir (talk) Please {{re}} 21:21, 24 June 2015 (UTC)[reply]
This is the village pump. --Francis Schonken (talk) 21:40, 24 June 2015 (UTC)[reply]
Lol so it is. Well then let the discussion continue here. I see no issue with NPOV, V, or OR and the IDENTITY text. EvergreenFir (talk) Please {{re}} 21:47, 24 June 2015 (UTC)[reply]
WP:IDENTITY as written is unreconcilable with WP:V. --Francis Schonken (talk) 21:50, 24 June 2015 (UTC)[reply]
This is what I have been arguing in as many places as possible. The current version of MOS:IDENTITY deliberately goes against core policy. It is written to nullify policy because this case is so exceptional. Transgender people are more equal than others." The WP:ADVOCATES got what they wanted written. They knew it was wrong when they wrote it so they had to write grammar to build in the exception. even when usage by reliable sources indicates otherwise, nullifying WP:SOURCE, WP:V. They even had to put words into wikipedia's voice. "Wikipedia favors self-designation," This exception is the cause of our problem. It clearly has to be changed. How do we change it to something that conforms with existing policy? Francis Schonken made a bold move to try to fix the problem. If not Francis, when will someone come in here and settle the issue? Or will this discussion just hang around until it drops off into the archive with no decision and is forgotten? That's the ticking time bomb I've been expecting already. We've been at this since June 2. Trackinfo (talk) 22:36, 24 June 2015 (UTC)[reply]
MOS:IDENTITY is perfectly fine with WP:V, specifically the section of WP:V about individuals being experts on themselves: WP:ABOUTSELF. There's nothing wrong with saying WP favors self-designation for certain things (religion, gender identity, etc.) as it can still be verified with statements by the individual themselves and that they would have the most recent and accurate info on the topic. Perhaps your concerns would be fixed if we update WP:ABOUTSELF to say that self sources are preferred in specific, limited cases like sexual orientation, gender identity, religion, etc.? EvergreenFir (talk) Please {{re}} 22:59, 24 June 2015 (UTC)[reply]
About themselves is fine. The conflict, with sources, is when it goes against their interaction with others, which affect WP:BLPs of the others; when it goes against sources, causing wikipedia to misstate historical facts, as in purported females acting in male roles. If the transgender people have no established history and can operate in their own bubble, there is no conflict with sources. But with notable figures, the kind of people we deal with on wikipedia, when they have a known public history but wikipedia reports the story differently, it damages the entire credibility of wikipedia's ability to report any fact correctly. Trackinfo (talk) 23:22, 24 June 2015 (UTC)[reply]
It's not difficult to reword stuff to avoid confusion. If your issue is with pronouns, that's a different issue. EvergreenFir (talk) Please {{re}} 23:59, 24 June 2015 (UTC)[reply]
It's not about pronouns. And on Jenner, I was finally the one to gender neutralize a bunch that nobody else seemed to tackle. I'd invite you to tackle the sentence: "Jenner contended that she likes the cereal and eats the breakfast cereal two to three times per week." with time appropriate language. The issue I have raised is about reporting historical fact. We have editors trying to report in the wikipedia voice that Caitlyn Jenner achieved female athletics records that (XY) Jenner would never be qualified to hold, WP:BLP displacing decades of legitimate (meaning XX) female athletes; plus that Caitlyn Jenner married three women; fathered 6 children (4 of them notable); that Caitlyn played male roles on television and in a couple of bad movies. Those things were accomplished by a person representing to be a male by the public name of Bruce Jenner. If Bruce was Caitlyn at the time, perhaps Jenner wouldn't have been nominated for the 1980 Golden Raspberry Award for Worst Actor, because she was doing a much better job pulling off the male part than the ex-jock, male actor Bruce Jenner did.. And in the other film, it was Adam Sandler who transgendered the award by winning the Golden Raspberry Award for Worst Actress. OK, I digressed. Sources throughout that era report Bruce's name, its engraved on the many awards. Wikipedia reporting otherwise, because the current draft of MOS:IDENTITY allows it to, means we are not reporting the true facts that are known to anybody who has followed this story through time. You will not find a source written before 2015 that mentions the name Caitlyn Jenner. Until we fix the problem, the loophole in MOS:IDENTITY is inviting editors to insert incorrect facts. Trackinfo (talk) 11:19, 25 June 2015 (UTC)[reply]
She (Jenner) was always a woman. If you identify as a woman (meaning you consider yourself to be a woman), you are a legitimate woman. Adam Sandler was not "transgendered," the Worst Actress award was a joke and not serious self-designation. Read WP:ABOUTSELF. Clr324 (say hi) 15:16, 14 July 2015 (UTC)[reply]
Clr324, do you have a reliable source for that assertion about this BLP? Not every transwoman subscribes to the story that "I am a woman, therefore I have always been a woman". Some of them take a more genderfluid approach, some believe that they were once male and have changed, and still others have other stories about their personal experiences. WhatamIdoing (talk) 18:25, 16 July 2015 (UTC)[reply]
@WhatamIdoing: Is Caitlyn genderfluid or views herself as changing genders? If so, and she prefers the past tense he, yes it would be best to use the past tense he as per the MOS. Ms. Andrea Carter here (at your service) 18:32, 16 July 2015 (UTC)[reply]
I don't know, as "celebrity gossip" is a section of the newspaper that I can't be bothered to read. I've noticed a lot of people making assumptions, but I've not seen anyone producing any sources on it. Perhaps nobody knows. Jenner may not have it all formulated into media-friendly soundbites and conveniently labeled pigeonholes yet (if ever – there is no rule that says you must have a story that makes sense to other people, or that the story you identify with today must be the story you stick to until death). But in the absence of sources directly addressing the issue, I believe we should be cautious about assigning life stories and personal beliefs to anyone. WhatamIdoing (talk) 19:58, 16 July 2015 (UTC)[reply]
@WhatamIdoing: I do agree. However, the MOS says to use the current gender self-identification in the past tense and the only objector has removed their objection. Ms. Andrea Carter here (at your service) 20:29, 16 July 2015 (UTC)[reply]
  1. Move the first sentence of the first paragraph ("Disputes over how to refer to a person or group are addressed by Wikipedia content policies, such as those on verifiability, and neutral point of view (and article titles when the term appears in the title of an article).") down, i.e. below "An exception to the above ...". (side remark: besides overcoming the unwanted exception to core content policy, it is also maybe better not to start a section with "Disputes...", so moving the sentence about how to resolve disputes – not assuming "dispute" is necessary to continue reading - down, so that it concludes the section, seems like a better idea from that perspective too).
  2. insert the qualifier "most of the" in "..., even when usage by reliable sources indicates otherwise", thus: "..., even when usage by most of the reliable sources indicates otherwise", indicating that this can't be done when all of the reliable sources indicate otherwise.
  3. As for getting rid of "Wikipedia favors ..." (which is unreconcilable with WP:NPOV), replace it by "give precedence to ..." --Francis Schonken (talk) 05:52, 25 June 2015 (UTC)[reply]
OK then for this implementation in three steps of "It's not difficult to reword stuff to avoid confusion"? --Francis Schonken (talk) 22:15, 25 June 2015 (UTC)[reply]
I agree with the first point; I think the second sentence is the main point for the first bullet, and the current first sentence works better as an independent third bullet. As it is currently written, I don't read the "exception" language in the second bullet as being an exception to core policies, because nothing in WP:MOSIDENTITY conflicts with core policies.
For suggestion 2, I don't understand the point of it; it seems like unnecessary added words. If there are reliable sources as to someone's self-identification of their own gender identity (as we of course require), then it can't be the case that there is zero usage of that identity in reliable sources.
I don't have any objection to the wordsmithing suggested in point three. Phrasing a style guideline as an imperative (with Wikipedia as the implied speaker) or as "Wikipedia <verb>" is all the same; neither is plausibly a violation of NPOV. The imperative formulation is probably, clearer, though both formulations are found in the MOS.
It would probably be best to wait for a few more people to comment and a clear consensus to develop before making any changes.--Trystan (talk) 00:20, 26 June 2015 (UTC)[reply]
OK, I don't see a problem splitting the first and second sentences of what is currently point 1 into separate bullet points and moving the first sentence to the end of the section. (Alternatively, indent and italicize the first sentence at the top of the section à la the "For results of past discussions" and "See also" pointers at the top of other sections, leave the second sentence as bullet point 1, and reword "exception to the above" to "exception to the preceding point" or such.) (Straying off topic: do people confuse Arab and Arabic so often that the main MOS needs to explain the difference between them, as it does now, or could we move that point to a subpage?) I think the second point is unecessary for the same reasons as Trystan; if one does want to add "most", I note that one could say "in most reliable sources" more concisely than "in most of the reliable sources". For for point three, as Trystan has said, either formulation is fine, "neither is plausibly a violation of NPOV [and] both formulations are found in the MOS", in fact there's another "Wikipedia [verb]s" phrase in the first bullet point we're discussing: "Wikipedia should use the term..." (which one could trim to just "use the term..."). -sche (talk) 06:09, 26 June 2015 (UTC)[reply]
  • OK, will proceed with first point, seems uncontroversial
  • Second point:
    • "(write something in the encyclopedia) ...even when usage by reliable sources indicates otherwise" is in direct conflict with WP:V. WP:V is one of the three core content policies. so "is in conflict with core content policy" is a correct appreciation.
    • "in most reliable sources" could (and will by Murphy's law) be read as "in the most reliable sources", so incites to give precedence to less reliable sources. We're going for avoidance of confusion here – I'm no fan of overly long formulation either (I'd cut the whole sentence – in fact it contributes nothing), but "most of the" doesn't have this ambiguity.
    • reformulate as "... even when only covered by a minority of the reliable sources." would avoid the confusion too, so maybe that's preferable.
    • or, as "... even when only covered by recent reliable sources." shorter, more to the point, no bloat.
  • "Wikipedia <verb>" is not the problem. "Wikipedia favors" is: if Wikipedia favors something over something else it is not neutral, so direct conflict with WP:NPOV. The only "Wikipedia favors" sentence I see possible is "Wikipedia favors neutrality". --Francis Schonken (talk) 07:04, 26 June 2015 (UTC)[reply]
Both WP:V and WP:NPOV (including DUEWEIGHT) allow for giving more weight to the "best and most reliable sources". The best and most reliable sources recommend, as a general practice, respecting individuals' expressed gender identity when using gendered terms. The best and most reliable source for a specific person's gender identity is that person's self-identification (as quoted in reliable sources such as the mainstream media). All MOS:IDENTITY says is not to override the best sources with a less discriminate tally of gendered-language usage across every source that could be considered reliable. There is no conflict.--Trystan (talk) 14:39, 26 June 2015 (UTC)[reply]
Re. "All MOS:IDENTITY says is not to override the best sources with a less discriminate tally of gendered-language usage across every source that could be considered reliable." – that's what we want it to say, not what it actually says. It says "Wikipedia favors (some type of content), even when usage by reliable sources indicates otherwise".
Then of course deciding that a source is more reliable depending on what that content is (not in the MoS, but in Trystan's comment above) is even worse WP:V-wise. --Francis Schonken (talk) 15:53, 26 June 2015 (UTC)[reply]
I said nothing of the sort. The best and most reliable sources on this issue are determined by professional and scientific expertise (e.g., the American Psychological Association), not by their position on the issue. I was summarizing what they do in fact say, not providing criteria on how to select them.--Trystan (talk) 18:00, 26 June 2015 (UTC)[reply]
You are suggesting a broad generalization based on one aspect suggesting American Psychological Association might have an opinion on other subjects. My concern is that backwards rewriting of historical events. We have a name (and gender representation) associated with historical events. To say that American Psychological Association, now, has an opinion on a name or gender dating back years, decades or longer, and that overrides what was written at the time will cause wikipedia to disagree with those historical sources. That's a lot of overriding because of one expert. Trackinfo (talk) 16:48, 27 June 2015 (UTC)[reply]
We often disagree with historical sources when they turn out to be wrong. We have 76 years of sources treating Pluto as a planet, but even in historical contexts, we make it clear that it is a dwarf planet that was previously considered to be a planet. We don't write in a way that suggests it was a planet and then stopped being one.
Where a person's previous gender expression is relevant, it can be made clear what gender they represented as at a given time while also respecting their later statement of their gender identity.--Trystan (talk) 15:15, 28 June 2015 (UTC)[reply]
All you want the MoS to say is "...follow the self-designation as contained in the most up-to-date reliable sources" instead of "...Wikipedia favors self-designation, even when usage by reliable sources indicates otherwise". Is that a correct summary? Anyway less charged with hyperboles that go against the grain of WP:V/WP:NPOV/WP:OR, and also using a language that is more becoming to a style guide. --Francis Schonken (talk) 18:48, 28 June 2015 (UTC)[reply]
  • I have mentioned this elsewhere, but I think it worth repeating here... There are actually two issues being conflated here... 1) the issue of what name to use in any given article or list, and 2) the issue of what gender pronouns to use. I think it would be helpful to separate these two issues. Names do not limit a person's identity. A woman can be named "Bruce" and a man can be named "Caitlyn". We can thus treat a change of name that stems from gender identity the same way we treat a change of name that stems from any other cause (such as a marriage, adoption, or simple desire of the person to use another name) - by following the sources and using the appropriate name in the appropriate historical context. As for gender pronouns... that is a more debatable issue, but one that we have a workable solution for: avoid all pronouns (don't use "he" or "she"... use "Jenner"). Blueboar (talk) 15:47, 28 June 2015 (UTC)[reply]
  • The biggest problem with this, if you ask me, is that MOS:IDENTITY is located in the MoS, which is a mere guideline. I'm not sure why it is located in the MoS at all. In fact, it would make much more sense to spin it off as a policy of its own. RGloucester 14:56, 29 June 2015 (UTC)[reply]
    I would support spinning IDENTITY off as a policy of its own, but I think it's understandable why it has been covered in the MOS (and I think it's reasonable for it to stay in the MOS in the interim, until such time as it's spun off as a policy of its own). As I wrote a while ago, "does this person profess the Jewish faith?" and "is this person transgender" are content questions which must be answered by reliable sources (and in both cases, the most reliable source for the information is the person themselves, and Wikipedia requires self-identification), while "should this person be referred to as a 'Jewess' or a 'Jewish woman'?" and "should this person be referred to as 'he' or 'she'?" are plausibly viewed as style questions, as can be seen from the fact that reliable sources from 1843 saying Foobar Smith killed "two Jewesses" can be used to support the sentence, in our article on Smith, that he killed two Jewish women — the sources verify the content, and we're just choosing which words to use to convey the content. Likewise, if sources from before Manning transitioned said "Bradley Manning visited France and he speaks French", but then sources from after Manning transitioned discovered and published "Chelsea Manning previously claimed she spoke French, but in fact she does not", Wikipedia wouldn't state "Bradley Manning speaks Frenchold source; Chelsea Manning does notnew source" — sufficiently many editors would be able to recognize the mathematical identity of Bradley=Chelsea to recognize that the new source was correcting the old source, not making an unrelated claim about a different person. (But as I noted: A thing that is "just a question of style" is sometimes dismissed as unimportant, with the implication that any answer to the question is "fine"; it should be clear that these questions of style are not unimportant, and some possible answers, such as "refer to that person as a 'Jewess'", may cause great offensive.)
    How would one go about elevating and moving IDENTITY? Start an RFC "Should the guideline currently located at MOS:IDENTITY be moved to Wikipedia:Foobar and adopted as a policy?" ? (WP:PROPOSAL seems to suggest doing that, but then says consensus is rarely accomplished that way, which leaves me unsure.) -sche (talk) 19:23, 29 June 2015 (UTC)[reply]
I suppose Blueboar's suggestion could work:
  • "Manning visited France, and Manning speaks French"
  • "Manning previously claimed speaking French, but in fact doesn't speak the language"
  • "Manning claimed to speak Frenchold source; In fact, Manning does notnew source
Let's not overcomplicate. --Francis Schonken (talk) 20:39, 29 June 2015 (UTC)[reply]
If you want to change "Wikipedia favors" to something like "give precedence to", I have no objection. (I do note, however, that WP:POLICY says "policies, guidelines, and process pages themselves are not part of the encyclopedia proper. Consequently, they do not generally need to conform with the content standards. It is therefore not necessary [...] to phrase Wikipedia procedures or principles in a neutral manner".) -sche (talk) 19:23, 29 June 2015 (UTC)[reply]
WP:POLICY is a guideline.
"WP:NPOV is non-negotiable, and the principles upon which it is based cannot be superseded by other policies or guidelines, nor by editor consensus" (see quote above) is policy.
Yeah there's no policy reason why a style guide shouldn't display stylistically bad choices – for me that's just a common sense argument. If you want to argue "bad style is better while WP:POLICY allows us", yeah, sure, go ahead. But don't expect me to fall for such argument. –Francis Schonken (talk) 20:39, 29 June 2015 (UTC)[reply]

The former

"... In such cases, Wikipedia favors self-designation, even when usage by reliable sources indicates otherwise."

has now been changed to (adding bolding to show difference):

"... In such cases, give precedence to self-designation, even when usage by reliable sources indicates otherwise."

I propose to update this further to:

"... In such cases, give precedence to self-designation as explicited in reliable sources that contain up-to-date information on such self-designation." (as contained in the most up-to-date reliable sources).

...same guidance, but with less of a "defy WP:RS" spirit (plus other advantages described above). --Francis Schonken (talk) 05:20, 30 June 2015 (UTC)[reply]

OK for this then? --Francis Schonken (talk) 09:00, 1 July 2015 (UTC)[reply]
Updated the proposed phrasing a bit to make it clearer (an up-to-date source that ignores the self-designation should not be followed in this respect). --Francis Schonken (talk) 11:56, 1 July 2015 (UTC)[reply]
I think there would need to be some alternative way of expressing what "but don't look at usage" is trying, perhaps ineffectively, to convey. I like -sche's approach above. It could be something like "...In such cases, give precedence to self-designation as reported in reliable sources. While a specific person's self-expressed gender identity is a question of content, use of pronouns and gendered terms is a question of style on which an article may differ from the sources used. Any person whose gender might be questioned..."--Trystan (talk) 15:55, 1 July 2015 (UTC)[reply]
Yeah, think that'll work. --Francis Schonken (talk) 06:35, 3 July 2015 (UTC)[reply]
So no-one thinks I'm taking credit for someone else's ideas, I point out that the "give precedence to" snippet which I implemented and which seems to be being described above as my language is actually what Francis proposed; I just implemented it because it had agreement here but no-one had bothered to implement it. :b
I'm wary of changing "even when usage by reliable sources indicates otherwise", because even if the intention is not to change the effect of the guideline, I think a wording like "as [explicited/reported] in [up-to-date/...] reliable sources" would lead more people to think that the guideline was saying the same thing that many people erroneously think WP:AT says, "[the only criterion is,] count how many reliable sources use each name, and title the article whatever name the largest number of sources use".
I don't mind having the MOS specify / explain "while a specific person's self-expressed gender identity is a question of content, use of pronouns and gendered terms is a question of style on which an article may differ from the sources used", if people agree that that interpretation is correct. It would certainly help explain things to the small percent of commenters who, in most of the trans BLP RMs I've seen so far, question if / suggest that "using other pronouns/names/synonyms violates WP:V!". -sche (talk) 18:12, 6 July 2015 (UTC)[reply]
Sorry, no. "People might misunderstand WP:AT" is a less big problem than "people actively misunderstand core content policy". So retracting my initial support for the mentioning of "content" in the MoS. If this has anything to do with "content" it shouldn't be in the MoS. No beating around the bush.
A person's self-identification needs to be covered by reliable sources, or it shouldn't be in Wikipedia. Core content policy, no ifs and buts. No suggestion this doesn't apply to self-identification. Self-identification reported in a tabloid exclusively? No content for Wikipedia. "Outing" of self-identification by someone's acquaintance on a blog? Not a sufficient reason for Wikipedia to start rewriting before the sourcing is WP:V-proof, etc. --Francis Schonken (talk) 18:58, 13 July 2015 (UTC)[reply]

Tx you all for collaborating on the current updated text. As I see it issues have been resolved, and I suppose there's no problem to remove the {{underdiscussion}} tag that links to this VPP section from the MOS. --Francis Schonken (talk) 07:25, 15 July 2015 (UTC)[reply]

Exploring possibilities to turn transgender guidance into policy

Re. "How would one go about elevating and moving IDENTITY?" I started a separate subsection. I see a few possibilities:

  1. Write a separate page with the guidance as you would like it. Put a {{essay}} or {{proposal}} template on top of it. Announce it on this page, and ask cooperation. Once the people interested in it come to a rough consensus that the text is workable, try RfC to elevate to guideline, or (but that would probably be a next step) policy.
  2. Propose it on a policy talk page for insertion in that policy. I'd choose WP:NPOV, with something like "Wikipedia is neutral to the choices people make w.r.t. their identity, religion, and preferences, and reports these without bias as expressed by themselves and recorded in reliable sources ... etc..." Again, try to reach a rough consensus on the talk page on wording, and where in the policy it should go. When that is possible → RfC (with announcement here, on the BLP policy talk page etc.)
  3. There are other possibilities (e.g. in a first step see if it can be added to WP:NPOVFAQ or WP:NPOV tutorial and from there to policy), and opportunities (e.g. group forces with the recently concluded initiative at Wikipedia talk:WikiProject LGBT studies#"Homosexual" vs. "Gay" – Wikipedia policy?) --Francis Schonken (talk) 20:39, 29 June 2015 (UTC)[reply]
Note: I placed a {{update}} template at Wikipedia:WikiProject LGBT studies/Guidelines#Transgender and intersex people, which seems to be lagging much behind. Maybe start to find consensus on updating the project-level guidance first, and see whether it can taken to a higher level of guidance from there? --Francis Schonken (talk) 08:59, 1 July 2015 (UTC)[reply]
I am not sure that there is enough support for IDENTITY to promote it... so I think the first step would be a wiki-wide (heavily advertized) RFC, asking whether the community wants IDENTITY to be promoted or left as an essay. Blueboar (talk) 11:10, 1 July 2015 (UTC)[reply]
  1. WP:IDENTITY is MoS, so currently at guideline level (not essay level).
  2. RfC for promotion to a higher level is unlikely to succeed before the text is somewhat tailored to such level. It's about common sense exceptions, easily applied for guidelines (as illustrated by some of the examples mentioned in this discussion), while a policy text should be written so that it is more resilient against exceptions (that means more detail about particular circumstances and/or more axing around overarching principles – these are choices that need to be made for a policy text, and hashing out such choices, checking against BLP, NPOV, and other existing policies, etc are usually better done before a more-or-less consensus text is presented via RfC - attempting to finetune a text by means of an RfC has already proved too often to be WP:SNOW) --Francis Schonken (talk) 11:56, 1 July 2015 (UTC)[reply]
You might find WP:PROPOSAL worth reading. WhatamIdoing (talk) 18:31, 1 July 2015 (UTC)[reply]
and/or Wikipedia:How to contribute to Wikipedia guidance. --Francis Schonken (talk) 11:34, 4 July 2015 (UTC)[reply]
@Francis Schonken: The current edition has been updated by -sche to a new section (Wikipedia:WikiProject LGBT studies/Guidelines#How to write about transgender, non-binary, and intersex people), per discussion regarding the use of the term "transgendered" that the user brought up. – Zumoarirodoka (talk) 12:32, 7 July 2015 (UTC)[reply]
Yes; that's largely a different issue from the one we've been discussing here, but if we were drafting a policy on trans subjects, I guess the language I added to WP:LGBT based on discussion would be appropriate to cover in the same place. Actually, perhaps MOS:IDENTITY's guidance on names and pronouns is not the subject of enough unity to elevate it to a policy at this time, but perhaps the WP:LGBT guidance on using words like "transgendered" is uncontroversial enough and subject to enough style guides' unanimity that it would be appropriate to elevate to guideline status on some MOS subpage? -sche (talk) 18:41, 7 July 2015 (UTC)[reply]

General discussion

  • For articles where the gender is important, and where the current publicly expressed gender identity would cause unjustified confusion, I think using their publicly expressed gender identity from that historic time frame is the way to go. For articles where that is not important, I'm really not sure. So in this case, because the gender of an athlete in the Olympics is important, I would say continue to use the historic male gender identity in those articles. But if we aren't talking about an athlete, I'm not sure. Say its an article about a company that talks about the CEO. On the one hand, the CEO's public gender identity at the time they were CEO may be interesting to some people. But on the other, it is at least somewhat common for people to say their current gender identity long predates when they started publicly expressing it, and we should try to be respectful of that. It also wouldn't be nearly as confusing as in the athlete example. I don't know how this would be turned into a guideline either. Monty845 02:49, 2 June 2015 (UTC)[reply]
  • Well, gender is important for sports, as most disciplines use it to create separate categories - usually for good reason. Learning about transgender people competing in sports with a category different from their self-identified gender will be more and more common, now that it is becoming less of a taboo. It makes sense to register a specific sentence in the guideline, but it should be based on the same criteria of the current MOS:IDENTITY. If the topic is confusing to some people, the guideline could help editors deal with it in a consistent way. Diego (talk) 09:33, 2 June 2015 (UTC)[reply]
  • For a historical listing on a page of athletic events, the name seems more relevant than the gender. As except for co-ed athletic events (equestrian?), it is assumed that everyone in that particular listing is of the same sex (or identified as such at the time of the competition). I was looking for an example of a prominent cisgender athlete who changed names during their career, and hit upon Muhammad Ali. On the list of heavyweight boxing champions he is listed as Muhammad Ali (Cassius Clay) for the year 1964. I think doing this on articles referring to Jenner's athletic career - i.e., Caitlyn Jenner (Bruce Jenner) - with a footnote about the gender change, might work. Funcrunch (talk) 03:00, 2 June 2015 (UTC)[reply]
    A lot of tables don't have that kind of room. You also have to take context into it. For way more than half of Ali's boxing career he was known as Muhammad Ali, not Cassius Clay. Same with Abdul-Jabbar (Lew Alcindor). In their field they had dual names and it makes sense to choose the more prominent one in their field. Jenner in sports was only known by one name, Bruce Jenner. The sports fields should reflect that. Fyunck(click) (talk) 04:59, 3 June 2015 (UTC)[reply]
    I can tell you right now, every table involved in this case has room for it. So that's a red herring. Skyerise (talk) 12:05, 5 June 2015 (UTC)[reply]
    They wouldn't in tennis draws... I'm not as familiar with wikipedia track&field nomenclature. Fyunck(click) (talk) 17:17, 5 June 2015 (UTC)[reply]
    An interesting precedent. I hadn't thought of that angle. Good idea. --Jayron32 03:05, 2 June 2015 (UTC)[reply]
    Funcrunch has it right. When the old name is reasonably expected and perhaps needed for context, include it in parentheses. Otherwise, use current name. EvergreenFir (talk) Please {{re}} 03:18, 2 June 2015 (UTC)[reply]
  • Well, I think that might be because of Wikipedia's specific preference/obsession for the "common name" to be used, rather than the accurate name (who cares if the entire world calls it Myanmar, its official name? Common name is Burma!!! No discussion!). In the sports-reference results from 1960, he is Cassius Clay, and his sports-reference profile (based on his 1960 results) he is also Cassius Clay (with Muhammad Ali listed under "other names"). МандичкаYO 😜 03:19, 2 June 2015 (UTC)[reply]
  • Given how WP:RS are treating Myanmar in the past year or so, it is likely ripe for a rename, but that is neither here not there. MOS:IDENTITY clearly lays out an exception for gender identity, the current discussion is merely how to clarify that guideline for articles outside of the subject article itself. --Jayron32 03:29, 2 June 2015 (UTC)[reply]
Are we seriously comparing a slave state's top-down impressed archaicising spelling of "Burma", which incidentally is pronounced like the word "Burma", with the individual lives of human beings? Ogress smash! 13:19, 3 June 2015 (UTC)[reply]
    • That's a good compromise, but shouldn't the name by which the subject was known at that time come first? Epic Genius (talk) 17:03, 2 June 2015 (UTC)[reply]
  • I think gender should reflect the choice of the subject (or in all cases should strive to be neutral where it interferes with proper continuity), but the name should reflect that which the subject was known by at the time. This also raises a question regarding gender-specific achievements. Ie, if Jenner's record was for male decathalon, would we use female pronouns in these cases? - Floydian τ ¢ 03:45, 2 June 2015 (UTC)[reply]
    The guideline says "yes", if that's the person's preference. That's the aproach most respecting WP:BLP. Confusion about a woman participating in men's category could be handled by noting that Jenner is a transgender person, which IMHO is relevant in that context. Diego (talk) 12:06, 2 June 2015 (UTC)[reply]
    That Jenner came out as transgendered in 2015 is not relevant to an Olympic competition 30 years prior though. And changing the name from the 1976 events, even to add a parenthetical or footnote introduces anachronisms that, frankly, do the encyclopedia a disservice. If we view Wikipedia as a serious reference, then re-writing history is outside our purview. Resolute 18:37, 2 June 2015 (UTC)[reply]
    Ah but see trans-awareness is the new white liberal guilt of today. It's more important that we slaughter the English language in an attempt to not possibly offend someone who lived for 60 years as a male, than it is to be factually accurate and list the name and gender they were publicly identified by at that time. Political correctness be damned, until June 1st they were a male named Bruce Jenner. Today that is different, but 3 days ago they identified as a man, so 30 years ago they most certainly were a man named Bruce Jenner. Unfortunately a case like this brings out the advocates with their cause. - Floydian τ ¢ 14:37, 3 June 2015 (UTC)[reply]

* There is a precedent for using names that the athlete used at the time of their athletic achievements. Ron Atest (Metta World Peace), Mike Stanton (Giancarlo Stanton), Domanick Davis (Domanick Williams), Olivier Saint-Jean (Tariq Abdul Wahad), Lew Alcindor (Kareem Abdul Jabbar) and Cassius Clay (Muhammad Ali) did not have their records retroactively changed. — Preceding unsigned comment added by 69.69.186.3 (talk) 04:02, 2 June 2015 (UTC) [reply]

  • In my opinion, use female wherever possible except in the cases where it would be likely to lead to confusion or implicates something that is not the case. (Her former marriage, at the least. Possibly her athletic accomplishments and her appearance on the Wheaties boxes as well) In the cases where her female name is likely to lead to confusion or false implications, use Bruce Jenner (Caitlyn Jenner). AddWittyNameHere (talk) 07:42, 2 June 2015 (UTC)[reply]
  • In sentences where female pronouns would cause problems, a common guideline is to use the last name (i.e. "Jenner competed in male categories" rather than "she competed in male categories"). Using the parenthesis is a good idea when the full name is needed - it's the most informative. Diego (talk) 09:33, 2 June 2015 (UTC)[reply]
  • Yes, I was speaking mostly of her full name. Names are more likely to lead to confusion and should have a more standardized solution; for pronouns there are multiple valid ways to work around issues—by replacing the pronoun with the surname, by rearranging the sentence so it makes sense ("became a parent" v. "became a father"). Probably more ways to deal with pronoun-related issues that are neither confusing nor insensitive, but those are the two most obvious. AddWittyNameHere (talk) 17:24, 2 June 2015 (UTC)[reply]

I strongly encourage all participants in this thread to read all of the Wikipedia:Gender identity essay - and in particular Retroactivity and Common name, which is the topic at hand. It works as a FAQ for MOS:IDENTITY, dealing with the most common objections to it, and reflecting the values that were used to craft the current guideline in defense of BLPs. Would it be a good idea to post it at the lead of this discussion, above Option 1? If there are no objections, I'll post the link there. Diego (talk) 10:14, 2 June 2015 (UTC)[reply]

  • The only problem I have with that is that it makes too many presumptions on the part of the transgendered person. For some transgendered people, the act of "coming out" as one gender may be merely the revelation to the public of a gender which they have had their whole life. However, the experience of transgendered people (like all people) is diverse, and the experience of one person cannot be generalized across all people. Gender can be a fluid concept, and while for one person, the act of "revelation" may be what is happening, other people may genuinely be one gender for some phases of their life, and may genuinely be another gender for other phases of their life. It isn't for us to decide, in any one particular case, what gender means to all people at all times. Sure, for some the act is merely a public revelation of a life-long gender (as noted in the essay), but for others the situation is more complex. We're also considering, in that essay, the implicit notion that people's experience exist only on the binary state of one of two genders; or perhaps on a continuum between those two genders. Human experience cannot be reduced to a single axis on any trait; we need to be careful not to minimize the experience of those who identify as a third gender or the genderqueer. My concern with that essay is that it's advice is not inclusive of the range of human experience, and we should NOT assume that all people who "come out" as trangendered are doing so for the same reason as all others. If a person genuinely identified as a different gender at a different phase of their life, we should not minimize that experience any more than a person who identified as one gender, different from their public persona. Both experiences should be considered "valid" (insofar as it isn't any of my or your or anyone's job to determine validity for others in a situation such as this.) --Jayron32 11:03, 2 June 2015 (UTC)[reply]
  • I don't see the essay as excluding the genderqueer nor assuming a gender binary; even if many examples deal with the case of transgender persons, the main theme is that of self-identity, whichever that is. It's true that we shouldn't soehorn all experiences into a common category, but that's not what the essay is about, quite the contrary. We do need a standard on how to handle our "default" way to write, so to say, and for transgender people (the topic of this discussion) the most sensible way is well handled by the external guidelines on which our MOS:IDENTITY guideline is based.
Exceptions to the guideline may still be handled case by case. If we find evidence that one particular person doesn't consider themselves to have always been the same gender, the writing for their biography could be handled on the light of the particular expressed self-identification of that person at different times. The problem with Option 1 above is that it encourages doing this even for people who self-identify as always having been the same gender. Diego (talk) 11:23, 2 June 2015 (UTC)[reply]
I very much appreciate Jayron's commentary about transgender people having different gender identity expressions. And on that point, it is also worth noting that while the term transgender is commonly used in a restrictive sense (for cases such as Chelsea Manning or Caitlyn Jenner), it is also an umbrella term for gender variant people. Because the biology of gender (including the causes of transsexualism topic) is still so heavily debated, with so much of the debate being inconclusive, and the complexities of gender variance, I remind myself to be cautious about making gender identity automatically a matter of biology. For many transgender people, they absolutely believe that there is a genetic basis to their gender identity; for other transgender people, they don't.
On another note: What should we do in cases like this edit, where CloudKade11 changed the label of "father" to "mother" regarding Jenner? How do we know that Jenner identifies as a mother? Flyer22 (talk) 11:55, 2 June 2015 (UTC)[reply]
(edit conflict)I think, however, that we miss the basic premise of these discussions when we focus on issues like "biology" and "choice" and "genetics" and "environment" and all the rest. The implicit assumption in the above (well meaning) discussion is the same as the transphobic people use to justify their bigotry: They choose to mistreat someone based on the fact that their identity is not valid based on concepts of biology; that a person "chooses" a certain gender, and that choice therefore means that others get to impart "consequences" based on that choice, etc. The first, and again, well meaning attempt is to refute those notions by saying "no, it really does have a genetic or biological basis" or "it is not something people choose". While well meaning, that misses the point entirely. The point (and excuse the emphasis, but I am doing this for clarity, not to shout or be rude), is that people are afforded dignity for no other reason than they are people. When you find someone mistreating a person because they claim that their biology makes them one gender, and they've (in the mind of the transphobic person) chosen to disobey their biology, and you counter that with "no they haven't, their biology and not their choice makes them who they are, even for transgendered people", you've focused on the wrong issue, and ultimately do a disservice to the proper resolution of the conflict. The response is "people are afforded the same basic level of dignity no matter who they are, and that includes the same rights to self-determination and identity that are afforded to all, irrespective of all considerations". That's the end of the debate. That's the point we need to get across. When we make dignity dependent on why a person is the way they are, that opens the possibility that there will be people who don't qualify for dignity based on your debated definitions. Dignity is not optional. --Jayron32 12:19, 2 June 2015 (UTC)[reply]
Jayron32 (WP:Pinging you in case you miss this comment), I know that it's common for transphobic people to use biology against transgender people (I've seen it enough times on Wikipedia and elsewhere), and I've heard all of those types of arguments. I brought up the biology matter above because this post by Diego Moya mentions biology. Your "11:03, 2 June 2015 (UTC)" post also made me want to address biology and the fact that gender variance is complex; there are some genderqueer people, for example, who will state that they choose to be a gender and that they actively rebel against the gender binary. I simply wanted to add on to your point about not generalizing transgender people; what I meant is that it's not always simple to say what made a person transgender. Some people (including some transgender people) argue a biological basis; other people (including some transgender people) argue that it's not a biological basis, and then there are the ones that argue that it's nature and nurture (a combination of both, not one or the other). That's basically all that I was stating: Gender identity expressions do not always form the same way. Flyer22 (talk) 19:38, 2 June 2015 (UTC)[reply]
See this archived discussion at MOS talk page. BTW, when infoboxes can't properly summarize a complex situation, isn't it common practice to simply remove the problematic fact and explain it in prose? Diego (talk) 12:17, 2 June 2015 (UTC)[reply]
I think the edit should be reverted or removed entirely, and CloudKade11 notified of this discussion, since there's still a huge debate on this. Epic Genius (talk) 17:05, 2 June 2015 (UTC)[reply]
  • If anyone seriously wishes to challenge or change Wikipedia's established position on this, I would strongly suggest starting by studying the history of our articles on Chelsea Manning, Wendy Carlos, and Chaz Bono as well as the extensive discussions about the naming of each on multiple noticeboards. --Guy Macon (talk) 12:11, 2 June 2015 (UTC)[reply]
  • We really need an official FAQ that summarizes the previous conversations about the guideline, otherwise we'll be revisiting it for every new variation of its application. Diego (talk) 12:17, 2 June 2015 (UTC)[reply]
  • Well, I think the issue is that if this had been discussed before, it is not self-evident from the way the existing guidance is written at MOS:IDENTITY. The point of the discussion is not to overturn any aspect of that well-crafted guideline, it is to clarify as there is some ambiguity. The point of the discussion is to hammer out how to handle issues which did not come up in the cases like Chaz Bono or Chelsea Manning; neither of them competed in sports where their results were awarded to them under their prior names, a situation which we need to clarify for the current hot topic, but to do so in a way where we don't have to debate it again in the future. It is because this situation has not been clarified for policy's sake that the discussion is necessary. Once this matter is settled, we won't have to deal with this one. That doesn't mean some new, novel problem we hadn't thought up yet won't arise in the future that we hadn't yet considered. The process is not ever going to end; that's not a bad thing. Not because we're rehashing settled policy (which this discussion is not, MOS:IDENTITY is not under challenge), we're dealing with situations we hadn't the foresight to clarify previously. We'll have situations in the future similarly as well. This is just the way it goes. --Jayron32 12:27, 2 June 2015 (UTC)[reply]

But we have cases that cover transgender identity in the context of their previous careers, like Linda Wachowski and Danielle Bunten Berry, and which were taken into account when drafting the guideline. Current consensus is to use the latest expressed identity and gender pronouns even for the periods where the public identity was a different one (and even on articles about their careers), handling any potential confusion through careful wording.

If the goal is how to clarify the guideline on how its current wording applies in some particular cases, it cannot override its purpose - the clarification must be compatible with what we already have. Or if this discussion wants to change that existing consensus, it needs to address the arguments that lead to it, not merely ignore them nor assert that they are no longer valid. Diego (talk) 12:52, 2 June 2015 (UTC)[reply]

  • I'm not doubting whether the discussion happened before. The issue is the current state of the guideline has some ambiguity. Insofar as the ambiguity exists now, a discussion is needed now to resolve the ambiguity now. When this discussion concludes, this ambiguity will be resolved to the community's satisfaction, and the wording of the guideline will be changed to be less ambiguous. --Jayron32 13:46, 2 June 2015 (UTC)[reply]
    Any person whose gender might be questioned should be referred to by the pronouns, possessive adjectives, and gendered nouns (for example "man/woman", "waiter/waitress", "chairman/chairwoman") that reflect that person's latest expressed gender self-identification. This applies in references to any phase of that person's life, unless the subject has indicated a preference otherwise. What is ambiguous about that? The people arguing to use male pronouns in Jenner's case are arguing for a radical change in the guideline, not a clarification. If you're referring to what name should be used, then you're right, what name to use is not explicitly spelled out - although we have precedents in similar situations, and there seems to be an evolving agreement towards using both names (one of them in parentheses). Diego (talk) 16:31, 2 June 2015 (UTC)[reply]
    No, I'm with you on the pronoun issue. The deal is in articles such as the 1976 Summer Olympics; especialy on mere entries in tables, where the pronoun issue wouldn't come up at all, do we use "Caitlyn Jenner" or "Bruce Jenner" or "Caitlyn (Bruce) Jenner" or some other identifier. The ambiguity is minor, and only exists in specific historic examples, where there is not a narrative to follow to explain the situation. --Jayron32 17:52, 2 June 2015 (UTC)[reply]
    Thank you, I understand now better your request for clarification. There seem to be two different aspects to it - whether we should use the previous name, and whether we should use the assigned-at-birth pronouns (sorry for the not PC term). The latter is settled from all the long previous discussions and crafting of the guideline, and would require a very strong new consensus to overturn. The former is open to discussion, and would make for a good adition to the guideline. I think Gaijin42's suggestion below to use the previous name where either gender or the exact name are relevant to the topic (noting that the person as changed names since) may be a viable approach, and compatible with how name changes are handled in other situations. Diego (talk) 18:23, 2 June 2015 (UTC)[reply]
  • I don't believe that there are any examples of athletic records being changed when an athlete change their name. It would be quite confusing for a reader to see "Caitlyn Jenner" under 1976 Olympic Gold Medal winners. — Preceding unsigned comment added by 104.254.93.62 (talk) 13:33, 2 June 2015 (UTC)[reply]
I tend to agree with what fun crunch pointed out above-(a parenthetical ref to old name if needed)...but I would also like to know if it would be acceptable or correct to say something like;"Competing as Bruce Jenner, Caitlyn won the gold medal"?73.199.138.75 (talk) 14:57, 2 June 2015 (UTC)[reply]
Yes, that is valid by the guideline. Diego (talk) 16:54, 2 June 2015 (UTC)[reply]
I just think that there's no precedent. Keep in mind that I am solely referring to athletic records, not other aspects of Caitlyn Jenners life. I just think that we should stick to common practice. When Chad Johnson changed his name to Chad Ochocinco, Oregon State didn't update their record books to reflect the change. There are many examples of athletes changing their names, and having their records appear as the name they competed under.104.254.93.62 (talk) 15:01, 2 June 2015 (UTC)[reply]

It seems that we have to distinguish between the biological and the juridical aspects. In a strictly biological sense, gender is a component that can never be changed (the difference in regards to male and female chromosomes). For example, if the medical record is considered, an individual once born a male will always remain a male, no matter what surgical operations the individual has gone through.
Individual's name, however, is a juridical matter. When it comes to that, I think we should use whichever name in force at the particular moment (e.g. Bruce Jenner in 1976, Caitlyn Jenner in 2015). In technical terms, I think that "gender as a subjective experience" is mostly manifested through the choice of name, and by respecting this right we'll afford dignity towards these individuals the best.
In other words, individuals may choose between their "gender identity" (subjective experience), not between their gender (which is an immutable biological component). Cheers! Jayaguru-Shishya (talk) 16:03, 2 June 2015 (UTC)[reply]

Please see the arguments laid out at Really a man and Legal name, those concerns have been addressed in the current manual of style. Diego (talk) 16:35, 2 June 2015 (UTC)[reply]
  • In this case, the personal preference of this person seems to be to use male pronouns for their past and to start using female pronouns in the future. Because of that, I think that Wikipedia should likewise use male pronouns for this person's past, and female pronouns for the future. Multiple media outlets got statements from this person about their preferred pronoun usage. It is unusual that in this case we have guidance for our manual of style here.
This is supporting evidence to manage these kinds of things on a case by case basis. Reform the RfC to address cases in which there is no supplementary information. This is a poor test case for examining the issue because there is a large amount of contextual publication on this stylistic issue for this case. Blue Rasberry (talk) 18:08, 2 June 2015 (UTC)[reply]
  • I'm not considering anything. I have no horse in the race, and just want to see the text clear at MOS:IDENTITY so we can point people in the direction the community wishes. I'm open to any and all well-explained alternatives. My two ideas were only the two I came up with, I am but one person, and not that smart of one; I fully expect people to have better ideas than I. --Jayron32 19:54, 2 June 2015 (UTC)[reply]
@Jayron32: I ask because I don't wish to refactor you. Is it okay if I go ahead and add a third option then? EvergreenFir (talk) Please {{re}} 20:15, 2 June 2015 (UTC)[reply]
So long as there's an explanation of the option in the introductory text so people know, in some useful detail, what they are voting on. --Jayron32 20:20, 2 June 2015 (UTC)[reply]

Ogress, I don't really like being labelled "transphobic"[4] (I assume you were pertaining to me since you referred to my comment) just because I happen to disagree. By "immutable biological component" I was simply pertaining to the different pair of chromosomes that males and females have, and in strictly medical sense that's what defines the gender. Neither do transgender studies disagree with this, but they emphasize "gender identity" (which I correctly reflected IMO). So what you found "transphobic" is actually supported by the very transgender studies. A quick look into the literature will confirm this. Should there have been misunderstanding, I hope this will help to sort it out.
Oh boy, why won't we just start using Finnish language instead? We've got only one pronoun for 3rd person singular, "hän", both for "she" and "he". ;-) Jayaguru-Shishya (talk) 12:33, 3 June 2015 (UTC)[reply]

@Jayaguru-Shishya: First, I really think you'd benefit from reading the (not very long) really a man guidelines. It really covers a lot of ground quickly, with citation and after consensus. Also, this is not a pleasant conversation in general: people are saying very hurtful things about actual human beings, some of whom are doubtless editors here and in this very conversation, so I'm not going to dance around the subject. Second, I didn't say you were a transphobe, I said the idea was transphobic. And the idea is, in fact, transphobic and incorrect: gender is not immutable and, in a strictly medical sense, different chromosomes are not what define gender. Gender and sex are different, and even sex is far more complicated than "chromosomes": it includes sexual organs, secondary sex characteristics, hormones and other things. In fact, most people don't have any idea what their chromosomes are; do you know how often infertile couples discover that the reason they cannot have children is that one of them has the "incorrect" chromosomes for their sex and gender? The estimated percentage of intersexuals - persons whose chromosomes do not match their apparent sex - among the general population ranges from one to four percent. That's a lot of people. So let me ask you: if a transgender woman has female genitalia due to SRS, has estrogen and not testosterone in her system as a result, has female secondary characteristics like breasts, how is her sex "male"? It's not. And not a single thing about that has anything to do with her gender anyway. A transgender woman who has a fully male body in every way is still a woman. We don't check genitals in people unless we're about to engage in intercourse with them, and we definitely don't check genitals before deciding what pronouns to use. That's the remit of gender, not sex. Ogress smash! 13:07, 3 June 2015 (UTC)[reply]
Thanks for your answer, Ogress. Sorry, I got mistaken that you were calling me "transphobic", but I am glad to hear you weren't :-) Anyway, I can assure you that I am not. I must admit though, that I never distinguished between the terms "gender" and "sex", but considered those more or less synonymous. It seems I was wrong. I just checked from a Finnish-English-Finnish dictionary, and the term "gender" is defined as follows:[5]
  1. Identification as male/masculine, female/feminine or something else, and association with a (social) role or set of behavioral and cultural traits, clothing, etc typically associated with one sex. (Compare gender role, gender identity.)
  2. The sociocultural phenomenon of the division of people into various categories such as "male" and "female", with each having associated clothing, roles, stereotypes, etc.
You are right. It must be the Finnish language that's causing confusion here on my part: in Finnish the word "sukupuoli" means both "gender" and "sex", and to emphasize the English meaning of "gender" as "gender identity" (number one above), we speak about "sukupuoli-identiteetti". So that explains why I was mistakenly using those two terms as synonyms (even the word "gender" already self-includes the identity aspect".
Did that make any sense? :-) Summa summarum, the distinction I was trying to make between "gender" and "gender identity" is no longer relevant. Thanks for correcting me! Cheers! Jayaguru-Shishya (talk) 14:23, 3 June 2015 (UTC)[reply]
Jayaguru-Shishya, coming from this, well, if you read the Gender and Sex and gender distinction articles, you will see that it notes that the terms sex and gender are commonly used as synonyms. But, yes, Ogress and I (and a lot of other people) distinguish between them...and for good reason. Flyer22 (talk) 15:56, 3 June 2015 (UTC)[reply]
I don't know but according to Monash University, it's pretty much like Ogress stated above. Jayaguru-Shishya (talk) 16:54, 3 June 2015 (UTC)[reply]
According to most dictionaries, "gender" and "sex" are synonyms in English too. But because "gender" also means "gender identity" and "gender role," it is best to be extra specific in conversations in which it is relevant. The usage note at the American Heritage Dictionary explains it pretty well. Darkfrog24 (talk) 18:55, 3 June 2015 (UTC)[reply]

The bottom line here is that transgender subjects are usually forced to change their name. They deserve to be credited for all their past accomplishments under their new chosen name. It's simple enough to add footnotes explaining this along with a citation for the name change. All proposal to do otherwise essentially strip the subject of their right to be credited by the name by which they are currently designated for their past accomplishments. Crediting some accomplishments under their former name deprives them of direct credit for their accomplishments. Since it is so easy to use footnotes to clarify, those arguing against doing so seem to be expressing a deep-seated discomfort with gender change which has no place here. Skyerise (talk) 17:41, 4 June 2015 (UTC)[reply]

It may be un-related but the fight over Jenner's name is going to street signs as well. [6]. In this case changing the name would effect other people's lives from social security into to drivers licenses. - Knowledgekid87 (talk) 20:09, 7 June 2015 (UTC)[reply]

TY especially Jayron32 for comments from 11:03, 2 June 2015 and Skyerise for the compelling "They deserve to be credited for all their past accomplishments.." argument. Part of me wonders how this may relate to all the women and occasional man that change their names in marriage or just for reason of some other preference?
A would agree that biography is of more importance than biology in determination of gender as related to the self but, beyond Jenner's claim that in an earlier phase of (bio) life that s/he wore female undergarments on occasion, is there any more evidence that she previously identified as a female or that, in the context of previous situations, that he (at that time) had identified as a man. I am concerned that we may be exerting wp:crystal to view a situation in Jenner's life of which we either are not or cannot be certain. I appreciated Jayron32's comments that different trans people have very different experiences and my immediate leaning particularly with "she"/"he" issues is that this might be applied differently with different people depending on whether or not the person identified with a gender that was suggested by the approximate 2% chromosome variance that typically dictates biological sex.
As far as name usage is concerned I think I would probably favour "Caitlyn (Bruce) Jenner", "Caitlyn (as Bruce) Jenner" or "Bruce (now Caitlyn) Jenner" in the context of previous sports articles and maybe other unless there is an argument otherwise.
When Daley Thompson (British hero) won the first of his Olympic gold medals this happened in a context that he and everyone else understood that the preceding athlete was the ("American hero") by name as "Bruce Jenner". In this context I agree with other editors that a wholesale replacement of the name would be inappropriate. GregKaye 14:14, 12 June 2015 (UTC)[reply]
Uh, Greg, have you read the article or any of the interviews? Jenner has stated that her female self-identification and gender dysphoria started at a young age. And transgender women who experience gender dysphoria starting at a young age don't ever "identify as a man", they "present as a man", that is, they do their best to pretend to be their "assigned gender" in order to get by in the world. Their gender self-identification is female usually from the time they understand the distinction between male and female. Jenner has confirmed in interviews that this was the case for her. Skyerise (talk) 14:46, 12 June 2015 (UTC)[reply]
In a subject that was new to me and I had only got as far as to go through a number of news reports a long with much of the article. I was also intrigued that the Kardiashian syblings repeatedly made reference to Bruce following announcements with use of male pronoun. Reports came across as indicating support but with significant surprise. In this context I appreciate your answer to my open question above.
I am still interested in the possibility that there may be different experiences up to a level of gender dysphoria as you have described. This would fit in with views presented by Jayron32 that: "Gender can be a fluid concept, and while for one person, the act of "revelation" may be what is happening, other people may genuinely be one gender for some phases of their life". At this point I appreciate that Jenner made very some strong statements in the interview but she also said things that only went as far as to say "My brain is much more female than it is male" 4minutes55secs. She also gave approval of the use of the male pronoun at the point of the interview. The important thing for me is that we treat a person as a person and I really don't know if this some of the content here would be anything that Jenner herself would be overly concerned with. Certainly in the future she is entitled to develop and present views in any way she sees fit.
I was concerned that unnecessarily long explanations were being applied (and made quick reply) but don't feel so strongly about this now. GregKaye 14:44, 13 June 2015 (UTC)[reply]

Clarification on the meaning of this proposal

MOS:IDENTITY says:

An exception to the above is made for terms relating to gender identity. In such cases, Wikipedia favors self-designation, even when usage by reliable sources indicates otherwise. Any person whose gender might be questioned should be referred to by the pronouns, possessive adjectives, and gendered nouns (for example "man/woman", "waiter/waitress", "chairman/chairwoman") that reflect that person's latest expressed gender self-identification. This applies in references to any phase of that person's life, unless the subject has indicated a preference otherwise. Direct quotations may need to be handled as exceptions (in some cases adjusting the portion used may reduce apparent contradictions, and "[sic]" may be used where necessary).

I believe the definition of "Option 1" is to change this to:

An exception to the above is made for terms relating to gender identity. In such cases, Wikipedia favors self-designation, even when usage by reliable sources indicates otherwise. In an article whose subject is the individual person, any person whose gender might be questioned should be referred to by the pronouns, possessive adjectives, and gendered nouns (for example "man/woman", "waiter/waitress", "chairman/chairwoman") that reflect that person's latest expressed gender self-identification. This applies in references to any phase of that person's life, unless the subject has indicated a preference otherwise. Direct quotations may need to be handled as exceptions (in some cases adjusting the portion used may reduce apparent contradictions, and "[sic]" may be used where necessary). However, in articles about events involving early stages of the person's life, the gendered terms that match the gender used by most reliable sources for the appropriate phase should be used, even if no longer current.

The article Christine Jorgensen, an article about a trans woman, refers to Christine Jorgensen as she/her throughout. But an example of what option 1 says is that if there were an article about Christine Jorgensen's mother, (I'm not saying there is one; this is just a random example showing how I understand the definition of this option) the section relating to personal life and children Florence (CJ's mother) gave birth to would refer to CJ as "George" and "he". Any part of the definition of "Option 1" that I'm ignoring?? (I'm not saying I support this change; I'm merely trying to clarify what it means. Georgia guy (talk) 15:07, 2 June 2015 (UTC)[reply]

If this is what is being proposed (which is what many Supporters seem to be arguing for), it would be best to start a new proper RfC with a clearer question. The current thread is worded as a slight clarification of the guideline, but the !votes are calling for a radical restriction of its current scope. It's also unclear what is the scope of the proposed change: should it apply to just sports records? should it affect any article which is not the biography? should it apply to all content referring to the early stages of the person's life, even in the biography? People are supporting all those options which are not part of the original question. Diego (talk) 16:41, 2 June 2015 (UTC)[reply]
IMO it should only apply to portions where gender is important. competing in gendered sports, prior spouses were not involved in homosexual marriages, They did not retroactively become the mother of a child. etc This is quite a limited set of places where it matters. "Caitlin went to X elementary school" etc is fine because gender is not relevant to the vast majority of elements in a biography. At a minimum quality every place that matters with the parenthetical (presenting s a male, as Bruce, etc) but that can get very cumbersome. Gaijin42 (talk) 17:22, 2 June 2015 (UTC)[reply]
Any example?? When talking about a trans woman becoming a parent do you think we should say "She became a parent for the first time" or "She fathered her first child"?? Georgia guy (talk) 17:42, 2 June 2015 (UTC)[reply]
For that specific example, avoid gender all together and say "Jenner became a parent for the first time". But when talking about a specific interaction especially if it involves another persons actions or POV its more difficult ("Jenner was viewed as a father figure by the Kardashian girls, and tried to emulate their own Father's good traits)" or something along those lines is what I'm talking about. Jenner is entitled to their own gender identity, including retroactively (because they may have considered themselves female the entire time) but they are not entitled to retroactively change the experiences and interactions of others into ones that involved a woman. Such starts to encroach on BLP issues for the others involved. Gaijin42 (talk) 18:10, 2 June 2015 (UTC)[reply]
Yeah... that example is difficult because Jenner was their father, and now she's a woman. However, I agree that we should avoid unnecessary pronouns or even unnecessary first names. Epic Genius (talk) 21:32, 2 June 2015 (UTC)[reply]
Exactly. WP:MOS: "If a style or similar debate becomes intractable, see if a rewrite can make the issue moot."  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  16:48, 14 June 2015 (UTC)[reply]
Yep; I believe MOS:IDENTITY at one point even spelled out that rather than saying things like "he gave birth" one should go with "he became a parent", although it seems it no longer does (which is fine, it's common sense). -sche (talk) 21:34, 14 June 2015 (UTC)[reply]
It should probably continue to say something about this, since common sense is obviously very scarce on this issue right now and probably will be for the forseeable future.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:34, 16 July 2015 (UTC)[reply]
(after some digging) The wording in question was removed in diff, citing discussion. The wording had previously been discussed a lot, as in, almost non-stop from Archive 141 through Archive 149. -sche (talk) 20:22, 16 July 2015 (UTC)[reply]
@-sche: Clearly not actual consensus to do that. There seem to be five in favor of it, mostly just with "me too" comments (reminiscent of the cascade of activism that's led to the current huge debate), while multiple other editors suggest that context matters, another suggests using the biologically correct pronoun in biological contexts, and other suggest a recommendation to avoid pronouns, etc. Given the enormous amount of previous, heated discussion, it's unlikely that that handful of editors could have actually represented a consensus to delete long-accepted, common-sense advice even if that micro-consensus had been unanimous, which it definitely was not. At very least it needs to retain the advice to avoid confusing uses of pronouns, which is also one of few things this current, much more participatory discussion is converging on.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  12:20, 20 July 2015 (UTC)[reply]
@SMcCandlish: re "[only] five in favor": eh, further up this page, changes were made based on me and Trystan saying "meh, I guess" to a proposal by Francis. (I refer to the final change(s) discussed here.)
I'd be fine with re-adding language to the effect of "where possible, say 'he became a parent', not 'he gave birth'", but I agree with one of the main points that led to the previous wording being removed, namely that it's not "logically impossible" that "he gave birth" and we shouldn't use the words "logically impossible" — even prefaced by "seemingly", they unnecessarily invite controversy (indeed, so much of it that they got removed). A rationale of "minimize confusion" might be better, especially if we bear in mind that being confused/jarred is not the exclusive province of people who say they're unfamiliar with "trans-gender stuff" — many people find it jarring if a subject is misgendered.
Having said that, can you think of articles where a MOS guideline to prefer "he became a parent"-type language would have helped avoid or resolve disputes, especially disputes that wouldn't be covered by the excellent, recently-added guideline "to see if a rewrite can make the issue moot"? Given that such language has been stably absent since 2013, it'd probably be helpful to show cases where its absence has been harmful, if one is interested in proposing its restoration. -sche (talk) 21:27, 20 July 2015 (UTC)[reply]
@-sche: Agreed. Those are all salient points. Other than the "prove it" line. Common-sense style advice doesn't need internal or external "citations" (if someone runs to MOS and says "We need a rule against replacing commas with asterisks, because it's happening all over the place", that needs proof; it's the "extraordinary claims require extraordinary sourcing" principle). The only reason I ever got involved introducing language like that the first time (I don't recall if I wrote it or just supported it, but I was there) was because I ran into cases of "he gave birth", "she fathered", etc. and the usual activism-for-language-change editwar-wall came up. Long before the recent meatpuppeteering power-grab. Incidentally, I also added the "see if a rewrite can make the issue moot" wording; I'm glad you like it, but it's too new to know if it will have any effect. A large number of the arguments on this page right now are proof positive that the gender-language activism POV will absolutely use "he gave birth", etc., if permitted. This "mission" will not be swayed by general "rewrite to avoid confusion" wording at the top of a guideline page; part of the cause is to write this way on purpose, to make a point and advance the socio-linguistic agenda. Only a concrete guideline, one that other editors feel empowered to act on, will restrain this problem. As I show below, common sense has not prevailed. The relative absence of a class of attested, poor writing is evidence that the guideline against it was in fact working. Since that language's removal, all hell has been breaking loose (correlation not causation) on every detail of how we write about TG subjects. The reasonable thing to do is revert to the common-sense wording on at least that one little, obvious point, until the chaos shakes out and a proper consensus reassessment can happen.

Anyway, while searching mostly produced false positives ("he gave birth the to philosophy that..."), there are "live" cases right now, e.g. Eugenia Falleni: "he gave birth". And an especially egregious example, as if written on purpose to confuse, at Thomas Beatie: "As a man, he gave birth to all three of his children" (if you read the whole thing, it really means "while identifying as a man, but before internal gender-reassignment surgery", mixing in a point about gender identity that does not need to be in that sentence at all, since it was already stated earlier in the section that he was male-self-IDed since age 10. (The entire section is problematic, written in a "gotcha!" story-telling fashion the entire point of which seems to be the delivery of that phrase I quoted). Both of those examples are back-to-back on the same page of search results. No telling how many more there are (I fixed a number that were not about TG people, just sloppy writing). I'm skipping fantasy/sci-fi and mythological cases, since they may be valid in context. At [[Hit & Miss]: "she fathered a son"; this is repeated word-for-word about the same show at Transsexual. One other result I found had already been rewritten by someone else (not sure how much the search results lag behind the live text), demonstrating both that there are additional cases, and that other editors are concerned about it and reverting it. It's important that these are only the most obvious possible searches, the "I can't believe anyone would actually write that" gaffes. There must be hundreds of other cases, e.g. in sports (the "Caitlyn Jenner won the men's gold medal" kind of stuff). Back to "proof": I don't think I should have to go to those articles and make common-sense rewriting edits that open me to another flood of hateful invective from the usual suspects as they revert-war me, to gather "smoking gun" evidence. My own stress level aside, I'm not an undercover agent, and probably provoking conflict to obtain such a result would be a questionable-faith exercise. There's no need to produce a smoking gun from bad-actors for us to just re-add a version of the wording, minus the wording flaws you pointed out. (Sorry this is long; it's a quick brain dump; I'll compress a lot before advancing this on MOS. If I even need to do it personally. Someone else could.)  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  00:27, 21 July 2015 (UTC)[reply]

For a point of reference of (OK its just my opinion) the stupidity of this policy carried not even to its extreme, check out Talk:High jump#Caitlyn Jenner and Talk:Decathlon#Caitlyn Jenner. Trackinfo (talk) 09:16, 3 June 2015 (UTC)[reply]

A lot of people in these discussions are making statements like "Jenner was viewed as a father figure" as if that's going to make people's brains explode - it is fine as is. When reading the article, readers may discover that (for example) Caitlyn Jenner lived much of her life as a man. That's fine. It's not like it's going to cause aneurysms. No one is going to be harmed. It's a little unusual but c'mon, there's a lot of transgender people in the world. There's wayyyy too much weight being placed on speech at Wikipedia, as if what we write here at Wikipedia is going to destroy the world. Just respect people's gender and name choices like we already do with most people. There's relatively little fuss given for most other people who don't use their birth names. IMO, there's zero need to avoid pronouns or skip names - that's just going to be weird. And changing C's old name at the athletic's pages is seemingly causing people to lose their minds... guys, chill. Caitlyn Jenner won awards in men's sports. This isn't going to change anything in the sports world. OMG, was K-C a LESBIAN MARRIAGE?!?!? is first, not likely to happen ever, and second, is covered by the information in the article that Caitlyn publicly transitioned at the age of 65. This is like a drama in a teacup because Caitlyn is a woman and hence uses female pronouns. Trans folk exist and it's seriously not difficult, despite this page exploding, to just handle it. Ogress smash! 10:16, 3 June 2015 (UTC)[reply]
From a relativist point of view, "Caitlyn is a woman" is only true for some people. It's true for me, being familiar with TG people and issues, but I can't pretend that everyone in the world agrees with that, and it's not Wikipedia's job to force the world to go along with it. There's a difference between choosing, by consensus as a project, to respect Jenner's gender identity, and trying to extend that baseline consideration to every possible wording alteration people can come up with in relation to a particular group. This one-size-fits-all approach cannot work. Different TG people approach this sort of issue differently, and the facts of particular circumstances even in the same subject's life differ. From a factual standpoint certain things should not be changed, because it distorts history.

I have no problem with Jenner's article saying "Jenner won [insert award info, from when Jenner was publicly identified as male]". We get into problems of multiple kinds when this is "She won [insert same]". We run into even more problems when the article on the medal itself is changed to read: Winner of the [year] medal was Caitlyn Jenner" instead of "Bruce Jenner" text in a piped link to the Caitlyn Jenner article (or "Bruce Jenner (now Caitlyn)", or Caitlyn Jenner (then Bruce)"]. It's a falsehood from the perspective of virtually everyone but TG language reform activists. Even if I were one myself (and my usage in my personal life actually matches that of one, except where I know the TG individual in question does not her/himself agree with the now-customary usage for TG people), that fact would not change and I'd have to come to the same conclusion. A desire to see the English language change, and for the societal pressures and psychology behind particular language usages to change, doesn't mean they already have changed. Wikipedia is written in 2015 English for 2015 people, not in what we [or some subset of we] would hope is some future English for a future audience.

We all understand that you and several others here want "she" and "Caitlyn" in every single place, but this can't reasonably happen; your motivations for this change to be taken that far, and the problems that arise from it, are at odds with Wikipedia's purpose and the needs of the audience. This is turning into one of the most obvious, though not most weighty, WP:NPOV problems on the whole encyclopedia.

Anyway, I agree that the Jenner article should use "she", and consistently refer to the subject under the current name. But there's clearly not a consensus that this should extend to banning constructions like "Competing as a male, and under the name Bruce, Jenner won [insert medal here]" where this seems it best serves the readers, much less to engaging in revisionist denialism on sport -related pages and suggesting that a woman named Caitlyn won men's sports competitions. But of course I'm just some ignorant transphobe mansplainer. I couldn't possibly be a well-informed, SF Bay Area egalitarian with waaay more than average genderqueer friends, who doesn't believe logic has genitals, chromosomes, or a gender identity. Sarcasm aside, I'm of course aware that my own reasoning on this could have imperfections. But at least I'm making an effort. Most of what I'm seeing from the other side is a circular reasoning pattern of proof by assertion. You can't simply keep restating "she has a right" and "the only correct way to view this is...", without actually responding to and refuting the responses and refutations that have already been provided against your assertions. That's not an argument, it's just noise. (I'm addressing the entire "do it the TG language reform way, or else" side of the debate, not your posts especially.)  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  16:44, 14 June 2015 (UTC)[reply]

See BBC's article about Renee Richards if it helps [7] ("She was captain of the men's tennis team at Yale University" is similar to "Competing in male categories, and under the name Bruce, Jenner won [insert medal here]", which could be allowed in an article). It mentions Jenner as "Bruce Jenner [Caitlyn Jenner]". We now have the argument about high quality WP:SOURCEs supporting the same rules codified in WP:MOSIDENTITY. Diego (talk) 08:41, 28 June 2015 (UTC)[reply]
One lone example in an experimental area of language and cultural change where everyone is trying to figure out what to do, and may have activistic editors (in the "above you in the company's organization chart", real-world sense) telling you what to do, isn't really evidentiary of anything.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:33, 16 July 2015 (UTC)[reply]

Option 3 cleanup

@Jayron32 and EvergreenFir: and everyone: Option 3 says "(formerly Bruce Jenner)", which is unnecessarily ambiguous. It's unclear whether that's formerly with respect to 1976 or to present. A reader could figure it out, but we should avoid the need to figure it out if we can. The way to do that is with "(then Bruce Jenner)". I think this can be changed without affecting any existing !votes, as it's only a language improvement, not a change of concept. ―Mandruss  19:09, 3 June 2015 (UTC)[reply]

@Mandruss: My first reaction is that this is a great suggestion. While I'd prefer "then known as", I know that's too much. My thought process on that is that some trans folks would say "I've always been FOOBAR_CURRENT_NAME, people just called me FOOBAR_OLD_NAME back then". But I am probably over-thinking it. I would be fine with changing it to "then" instead of "formerly". EvergreenFir (talk) Please {{re}} 19:16, 3 June 2015 (UTC)[reply]
Unless I'm mistaken, "formerly" has the same problem, so "then" is no worse in that respect. ―Mandruss  19:20, 3 June 2015 (UTC)[reply]
I suppose it does. Just been thinking on it in general. Again, no opposition to the change. It's shorter, clearer, and addresses the issues you raised. It's a good idea. EvergreenFir (talk) Please {{re}} 19:41, 3 June 2015 (UTC)[reply]
I'm not particularly hung up on details. My support for such a notion is that the general concept is good; I'm not going to let grammar get in the way of doing the right thing. --Jayron32 00:11, 4 June 2015 (UTC)[reply]
While there are many trans folks who would say that they were always the gender with which they now identify, I seriously doubt many would say that they were always the name that they have now chosen. Funcrunch (talk) 03:28, 4 June 2015 (UTC)[reply]

 DoneMandruss  07:59, 4 June 2015 (UTC)[reply]

How sources are referring to the records matter, and what they are stating

Like I noted at Talk:Caitlyn Jenner, I follow MOS:IDENTITY; I think it's important that we follow it. That stated, when it comes to the records Jenner set, an approach to analyze is this article by espnmediazone.com regarding the ESPY Award that Jenner will be receiving. That article refers to Jenner with male pronouns when addressing the athletic records, but notes that "the decision to publicly come out as a transgender woman took a different kind of courage and acceptance of one's self. To celebrate that bravery, ESPN today announced that Jenner will be presented with the Arthur Ashe Courage Award at The 2015 ESPYS Presented by Capital One." Going by this Twitter post by Jenner, she is excited for the event and perhaps does not mind the male pronouns for a past matter. Keep in mind that when some transgender people, including transgender Wikipedia editors, were insisting that Jenner should be using female pronouns, she was using male pronouns. Whereas many transgender people cannot stand to be referred to by gender pronouns that they do not identify with, it may be that Jenner is not as offended by being referred to by the opposite pronouns, unless perhaps there is an ignorant and/or malicious intent behind it. I'm not stating that we should not follow MOS:IDENTITY; I'm simply posting this ESPY Award article for further thought on the records aspect. Flyer22 (talk) 02:38, 4 June 2015 (UTC)[reply]

I would not read too much into Jenner not correcting or addressing the ESPN article on pronoun usage, especially in a short Twitter post. Speaking from experience, correcting pronouns constantly can be very stressful, and sometimes we let misgenderings go by rather than correct them, simply out of exhaustion. Funcrunch (talk) 03:52, 4 June 2015 (UTC)[reply]
Yeah, I was not expecting her to address the matter, especially via Twitter, and blast groups that will be honoring her; I wanted to add on to the discussion about what is or isn't the appropriate way to refer to her past regarding her records, and what she might think of the matter. As has been discussed above, not all transgender people feel that they were the same gender throughout their lives or at every point in their lives. With this edit, Barte stated, "Some thoughts on the matter from the Washington Post and National Review Both reference the Wikipedia entry here, though neither notes the MOS:IDENTITY guidance." If we look at the Washington Post source, it states, "There’s no doubt that it’s insensitive for former Nickelodeon stars, news organizations and just about anyone to refuse to refer to someone by the name he or she prefers — whether that person is Malcolm X, Cary Grant, Muhammad Ali, Chelsea Manning or Jay Z. But Bell’s insensitive declaration raised an interesting point. Did Bruce Jenner or Caitlyn Jenner win those Olympic gold medals and appear on those TV shows? And if Caitlyn Jenner did, must history be rewritten? Is every source that refers to 'Bruce Jenner, record-breaking athlete' — or 'Bruce Jenner, guest star on ‘Silver Spoons — now in need of a correction? Wikipedia thought so. By Tuesday evening, the ubiquitous crowdsourced encyclopedia was redirecting its 'Bruce Jenner' page to 'Caitlyn Jenner' and using the pronoun 'she.'"
If we look at the National Review source, it states, "GLAAD addresses the challenge this way: DO avoid male pronouns and Caitlyn’s prior name, even when referring to events in her past. For example, 'Prior to her transition, Caitlyn Jenner won the gold medal in the men’s decathlon at the Summer Olympics held in Montreal in 1976.' But GLAAD also defines 'gender identity,' which is the thing at issue here, as 'one’s own internal, deeply held sense of being male or female.' That presents a problem. But the past, being common property, is not GLAAD’s to rewrite — particularly given the Left’s logical inconsistency about what has just taken place. The argument for adjusting the historical record to reflect Jenner’s present sensibilities is (at least in part) that 'Bruce' was really 'Caitlyn' all along; 'Caitlyn' did win the medals, we just didn’t know it then. Yet GLAAD and others liken pronoun changes to name changes: Nobody calls Jay Z 'Shawn Corey Carter,' ergo, they should not call Caitlyn 'Bruce.' But what 'courage' has Jenner demonstrated if his transition is not precisely that he got rid of the person Bruce for the person Caitlyn? He has not simply adopted a new name, a new identifier, but a new 'identity.' Both the identifier and the thing it identifies have changed." Because of all of this, I've changed the title of this section to How sources are referring to the records matter, and what they are stating. Flyer22 (talk) 23:06, 4 June 2015 (UTC)[reply]
Re "not all transgender people feel that they were the same gender throughout their lives or at every point in their lives" - this is true, but since you're talking about Caitlyn Jenner in particular here, it seems most prudent to stick with the MOS:IDENTITY guidelines of assuming current stated gender applies throughout the person's life unless they themselves state otherwise. Of course, unless she's stated otherwise, it is highly unlikely that Jenner identified with the name Caitlyn specifically at the time of winning her medals (and certainly not from birth), but that is why Options 3 and 4 above suggest including both names. I really don't see why so many people (not you) are resistant to respecting a person by including both their current and past names in such a manner; it isn't "rewriting history". Funcrunch (talk) 01:49, 5 June 2015 (UTC)[reply]
DHeyward, considering what you stated in this discussion, including that "Jenner has already said she doesn't mind masculine pronouns in the 'Vanity Fair' article and indeed still says 'Bruce' out of habit.", maybe you have something you want to state in this section? Flyer22 (talk) 19:06, 8 June 2015 (UTC)[reply]
I agree with ESPN. When they talk about the past historical records and there is no way to disassociate former name and their gender is relevant to history and notability, the least confusing and the most natural agreements should be used. The IOC statement is all in past tense and is simply a matter of fact regarding the Olympic record. It's not their place to confirm Jenner's transition with pronouns that reflect her gender identity when they are not in a position to do so and, as a general policy, risk outing someone that has left their deadname and past. If there is another Olympic Athlete that is not as well known but keeps their mailing address updated privately with the IOC and has told them about their transition but is otherwise private and disconnects from that past, it would be a HUGE mistake for the IOC to respond to requests about that Olympic Athlete with anything other than the historic record. Mixing pronouns that don't match the record would only elicit more questions and may even open those athletes' transition to public scrutiny, the exact opposite of their desire. It's a sure bet that there are news organizations looking for other transgender athletes, public or not, to seek comment. I would have no problem if Jenner petitioned the IOC to change its records, but short of that, they are bound by them. I expect the IOC to keep medical history of athletes as privately as possible including disqualifications as well as transgender athletes that petition to compete as their expressed gender (i.e. a transgender woman athlete that competes as a woman is a "woman" with no asterisk, "formerly known as" or parenthetical explanation of the waiver or even mention of the waiver). I also commented that I think it is wrong to highlight the transition in virtually every article about Jenner. It reeks of placing activism over a lifetime of extraordinary accomplishments. Jenner, the person, won Gold Medals for the 1976 Men's Decathlon. Her transition does not overshadow that nor is it necessary to whisper "transgender" on every page with asterisk, parenthesis, name changes and pronouns. Those that do so are not seeking to minimize harm to Jenner, rather they are seeking to exploit her for her courage to transition so publicly. We should let her be the role model and not decide which event in her life defines her. We simply don't know. ESPN is not wrong and they have undoubtedley consulted with both Jenner, the LGBT community and others to decide how approach this. They will be courageous in their choice and respectful of the people involved and to imply anything else does a huge disservice to our readers. --DHeyward (talk) 20:06, 8 June 2015 (UTC)[reply]
To me it is misleading to suggest that Jenner saying she doesn't mind being misgendered - especially at this very early state in her transition - should guide Wikipedia policy. Most trans people expect to be misgendered and misnamed repeatedly by friends and acquaintances for a period of time following transition, and even misgender and misname ourselves as we get used to using our new names and pronouns. But in an encyclopedia which is referred to by news organizations as well as individuals, we should set a higher standard, and not give the impression that an individual trans person's comfort level around pronouns should dictate how we handle gender changes. (Of course, if she specifically said that she was fine being referred to by her previous name and pronouns in Wikipedia articles and news coverage, that would be a different matter.) Funcrunch (talk) 20:11, 8 June 2015 (UTC)[reply]
The "expect to get misgendered" and "misgender and misname ourselves" aspects you brought up are very solid points, Funcrunch. I think that the "getting used to" aspect is something we should always keep in mind with regard to transgender people, their families, and the public at large; for example, it can take a significant time for a mother to use the new name and pronouns, if she ever does so or tries to do so consistently. I also keep the "getting used to" aspect in mind when considering our Wikipedia editors and the world at large. As we know, Jenner is a person who went by the name "Bruce Jenner," and by male pronouns, for a very long time; so it's natural that people will make mistakes as far as the name and gender go; it's not always a matter of transphobia. Flyer22 (talk) 01:15, 9 June 2015 (UTC)[reply]
Not to mention...there are surely still people who don't recognize the name Caitlyn Jenner, at least at first saying or first glance, but do recognize the name Bruce Jenner. Flyer22 (talk) 01:21, 9 June 2015 (UTC)[reply]
To limit this whole discussion to what contemporary sources are reporting is WP:Recentism. Most of the primary reporting of Jenner's athletic and celebrity history before 2015 are not being rewritten by the originating source. Newspapers and books don't reprint due to later developments. In Jenner's case, male pronouns are used, Bruce Jenner is the name attributed by those sources. Wikipedia should not be deviating from those sources when reporting historical incidents. To do so is rewriting history, violating WP:SOURCE. That ought to be consistent across all transgender people. We should always link to the main name article where her transition and new name are explained. Painfully, I'm sure some of these prevalent advocates will want to force the parenthetical "now Caitlyn Jenner" into every appearance of the name, we already see that or primarily its inverse occurring, but it will really clutter up the readability of many articles. Jenner's long, public notoriety makes this case more problematic, but it is confusing to any reader in any case where the wrong name and wrong pronouns are used to describe a notable historical event involving a person who transitioned at a later date. Its a consistent violation of WPSOURCE. Trackinfo (talk) 03:36, 12 June 2015 (UTC)[reply]

Old sources aren't republished, but we do rewrite our articles to keep them current with the most recent knowledge. When scientists discover an new hominid older than all others, we update the article of the previous one - maybe noting that "for X years, it was the oldest hominid known"; when it is revealed that some scientist published papers with fraudulent data, we remove them from the references - we don't accept those as if they were valid before publishing the retraction and only became invalid after that. All that "historical revisionism" argument is frankly an insulting idea; updating articles to reflect that we understand the topic best now, because of the increased knowledge, is what makes us an up-to-date resource, and thus one of the project's best characteristics.

Your best argument is that of readability, but it can't take precedence when is weighted against encyclopedic accuracy (describing all the relevant facts) and BLP (respecting a living person's identity while avoiding harm). And better yet, we don't need to confront them - we could reference both names just in the first appearance in the article, or place a footnote at each entry in a table. So that's not a reason either against options 3 and 4. Diego (talk) 08:56, 12 June 2015 (UTC)[reply]

P.S. Regarding the argument about "confusing readers" with the use of pronouns, it's worth noting that the BBC had no problems in using the female pronoun when talking about tenist Renee Richards [8] and is not ashamed of writing a sentence like "She was captain of the men's tennis team at Yale University". For what it's worth, it refers to Jenner as "Bruce Jenner [Caitlyn Jenner], who's a very famous athlete". I think we could use some good advice from the BBC editors and get those as best practices. Diego (talk) 14:52, 27 June 2015 (UTC)[reply]
Of course they are, but Renee Richards played tennis as a transgender where Caitlyn did not win the decathlon as a transgender. Today when talking about Jenner we would say she won the decathlon in 1976. I have no quarrel with that. But what does Yale University have listed as their Team Captain back then? The Olympics website uses Bruce Jenner with nothing else as winning the Decathlon. So we have to look at context. When we talk specifically about Caitlyn Jenner and what she has accomplished, we are going to say she won the Olympics but mention that it was as (Bruce Jenner) in some way. When we are simply talking 1976 Olympics we are going to use Bruce Jenner and usually use he in that context. Fyunck(click) (talk) 06:40, 28 June 2015 (UTC)[reply]
But that would be an incorrect use of the pronoun given what we know now, that Jenner was a transgender woman, even if she was hiding. A first class publication like the BBC won't make that mistake. Richards also played tennis in the male categories, and she was listed as a captain of the men's team in Yale, but BBC writes "she was captain", not "he was captain". The context has changed because we have more information about that period that was not known then, and dismissing that information as if it doesn't exist would be wrong. Of course it's OK to use the names Bruce Jenner and Richard Raskind for the period where those were the names they were using, but a clarification that we're talking about persons who later changed names is needed. Diego (talk) 08:27, 28 June 2015 (UTC)[reply]

To the closer: survey is statistically invalid

I'd like to point out that this whole survey process is pretty much invalid. Transgender people make up an estimated 2 to 5% of the population. [9]. The 2013 study The Wikipedia Gender Gap Revisited measured gender bias in survey completion and estimated that as of 2008, 84% of English Wikipedia editors were male. In the worldwide Wikipedia Editor Survey 2011 of all the Wikipedias, 91% of respondents were male. There are significant differences in the acceptance of trans people between males and females surveyed, with men being significantly less accepting than women of transgender individuals, with white males being the least accepting among males and with the widest gap between white male and white female opinions. [10] Somewhere between 58-63% of males are sports fans, while only 36-41% of woman are fans. [11]

So, 60% of the 84% male editor population is about 50% of Wikipedia editors, while 40% of the 16% female editor population is 6.4%. Even assuming the unlikely high number of 4.6% for the trans editor population, that puts the expected ratio of female+trans to male editors responding at 1 in 6. Basically, there is no possible way that the outcome can be anything but a "male sports fans" opinion, which would be in no way representative of what our readers want and would necessarily be significantly (and likely severely) skewed toward the less accepting male view of transgenderism.

Unless a better way can be found to do this, these results are completely invalid and should be ignored, leaving MOS:IDENTITY as it is, as the previous consensus was arrived at through discussion about transgender individuals who were not athletes, leading to a more balanced and more accepting result. That is, the past consensus more accurately reflects the general opinion of Wikipedia editors as the inherent biases were not exaggerated by the disproportionate attraction of sports fans to the previous discussions, resulting in the slightly less skewed ratio of ~ 1 to 5 female to male response. I could not find statistics on the acceptance of transgenderism among male sports fans, but I suspect that it is much lower than that of the general male population. Skyerise (talk) 21:20, 5 June 2015 (UTC)[reply]

100% ridiculous... AndyTheGrump (talk) 22:32, 5 June 2015 (UTC)[reply]
I thought so too. But as long as the closer stays within wiki "policy", looks at the arguments pro and con, looks at any relevant censoring policies, and checks where consensus seems to be, I think we'll be ok here at this encyclopedia. Any ridiculous bloviating will be ignored by most good closing admins. Fyunck(click) (talk) 23:10, 5 June 2015 (UTC)[reply]
(edit conflict) Even if there is systemic bias on Wikipedia and in its users, WP:CONSENSUS is important as well. I assume this will be closed by an admin (or 2) and I'm sure they'll weigh the comments here against site policy. Remember, this is not a WP:NOTAVOTE. EvergreenFir (talk) Please {{re}} 22:33, 5 June 2015 (UTC)[reply]
Yup, and the current MOS:IDENTITY guideline was developed by consensus and has been tested several times previous without any significant change to the guideline. In such a case, it is reasonable to ask two questions: 1) is there a reason why this discussion looks different? and 2) does that reason make it likely that this discussion is more or less representative than the previous ones? Skyerise (talk) 22:54, 5 June 2015 (UTC)[reply]
When the MOS:IDENTITY guideline was developed in this regard, POV pushing editors (that minority you statistically itemized above) flocked to the discussion because it was in their interest. We now have a very public conflict where interpretations of this MOS:IDENTITY causes conflicts with WP:SOURCE and offends many other individuals under WP:BLP in the process (I've tried to itemize a few in other discussions). When we are dealing with people of lesser notability, that awkward rewriting of history might be tolerable on a minor scale. Now we have a famous notable figure with a 45 year history representing as one gender but now is transgendering to another. This massive rewriting of history puts wikipedia at odds with the established, known reporting of that 45 year history in a very public way. Advocacy groups wish to use this as an example, but it is not wikipedia's job to alter facts. Trackinfo (talk) 21:08, 9 June 2015 (UTC)[reply]
MOS:IDENTITY is not the only guideline that recommends using recent sources over the ones contemporary to the facts, so advocacy is not the only reason to prefer using the most recent name. Self-published name changes and WP:MOS/Medicine-related articles recommend weighting the most recent sources when appropriate, so it's not a concern of rewriting history but of using the most accurate and updated name for the topic. Also MOS:PIPE advises us to "make sure that it is still clear what the link refers to without having to follow the link", so places that link to the Caitlyn Jenner article (or any biography where the subject has changed names) should provide some cue as for why the historic name does not match the one at the linked article. Diego (talk) 19:50, 10 June 2015 (UTC)[reply]
Almost all articles containing Jenner's name are getting bombarded (like here and here) by activists replacing Jenner's name to prove a WP:POINT (yet another guideline being violated under cover of MOS:IDENTITY) against what the source says. As these are being reverted by other editors on those grounds, there is the residual Note "Jenner changed her name due to gender transition in 2015." that has not been removed. The message is clear that Jenner has since changed identity, without altering the fact that Bruce Jenner is the name recognized for these achievements. Trackinfo (talk) 22:16, 12 June 2015 (UTC)[reply]
Trackinfo, it sounds as if you haven't actually read the specific clause of MOS:IDENTITY, or you'd know that it specifically states: "Wikipedia favors self-designation, even when usage by reliable sources indicates otherwise" Skyerise (talk) 22:21, 12 June 2015 (UTC)[reply]
I asked over at WP:AN for a neutral uninvolved admin to close this when the time comes but have yet to get a reply. - Knowledgekid87 (talk) 22:35, 5 June 2015 (UTC)[reply]
Wondering...Does anyone ever ask for a biased, fully involved admin to close a discussion? Fyunck(click) (talk) 23:15, 5 June 2015 (UTC)[reply]
LOL! Are there any admins among the !voters above? We could ask them to close the discussion... :) </tongue in cheek>. -sche (talk) 03:09, 10 June 2015 (UTC)[reply]
Thanks. That would be appropriate. Skyerise (talk) 22:36, 5 June 2015 (UTC)[reply]

We see this fairly often here. A debate comes to an answer that someone does not like and they try their best to explain why consensus is wrong. I am afraid that you will have to accept the outcome of this RFC even if you think the people involved in it are "sports fans". Chillum 22:56, 5 June 2015 (UTC)[reply]

Hmm, Chillum why do you think you are entitled to tell me what I have to accept? I always have the option of just walking away from Wikipedia. Skyerise (talk) 23:00, 5 June 2015 (UTC)[reply]
P.S. Your bee and hummingbird photos are great. Skyerise (talk) 23:04, 5 June 2015 (UTC)[reply]
Maybe something can be worked out of this proposal is passed? Re-wordingwise maybe? I just don't want it to feel like it is all or nothing, some have argued for this to be a case by case basis. - Knowledgekid87 (talk) 23:07, 5 June 2015 (UTC)[reply]
Thank you I am very proud of both of those images. You are of course right, if you find the outcome distasteful you do not have to participate. I do think you are being a bit dismissive of other people's opinions. Chillum 23:07, 5 June 2015 (UTC)[reply]
Only because many of the opinions are uninformed, put forth by people who haven't actually looked into or considered the hardships and disapproval which are a lifelong problem with trans folk, whether they choose to transition or not. Skyerise (talk) 02:10, 6 June 2015 (UTC)[reply]

::::That's not our problem. We are here to build an encyclopedia first and foremost. High quality articles is more important than trans editors being upset over pronoun usage. And let me be blunt. No group of editors has the right to speak for an entire portion of the population. If you don't like it, well no one is forcing you to stay here. Feel free to fork if you wish, but your demands are becoming disruptive.69.143.188.200 (talk) 06:53, 7 June 2015 (UTC)[reply]

Read the BLP policy. "Writing an encyclopedia" is neither our first nor foremost task around living persons; treating them with respect is. Moreover, exactly how on earth do you expect to write an encyclopedia free from hideous systemic bias if you adopt policies and make statements hideously offensive to a not-insignificant portion of the population? Encyclopedias require editors and good encyclopedias require diverse editors. And what I'm hearing here is a lot of "hey I got into the clubhouse and clearly everyone is just like me so it's fine". Ironholds (talk) 04:41, 8 June 2015 (UTC)[reply]
I have absolutely no idea how you came to comprehend wikipedia biographies in that way. Like everything else we are here to build an encyclopedia... it's our number one priority. Now, wikipedia gives us Policies and Guidelines to help us achieve that endeavor, and BLP's certainly have more strict rules to follow so we don't get sued. It's why we must source, source, source BLP's. We treat living persons with respect (as we do to dead persons too) but we also tell the truth if it is backed by sources. I'd like to say we never censor, but I know we do in certain cases, so it's best to say we rarely censor. Fyunck(click) (talk) 06:00, 8 June 2015 (UTC)[reply]
Probably by reading the policies, being around when they were drafted and working in a related field. It's not so we never get sued; are you kidding? The legal protection we have is actually stronger if the Foundation sets no content policies. It's because you should treat article subjects with a certain modicum of human decency and empathy. Again, the idea of "we are here to build an encyclopedia...it's our number one priority" - you cannot complete that priority if you are exclusionary to current and future Wikipedians. That I haven't seen you address. Ironholds (talk) 06:39, 8 June 2015 (UTC)[reply]
I read them and don't see it where it says we are not first and foremost an encyclopedia. Most were drafted before 2008 when it says you made your first non-anon edit (I was in 2006), and working in a related field I see as a non-factor here at wikipedia. So no policies and leaving us to edit as we please leaves us stronger legally? I don't buy it. I gives us the tools to stop false info from appearing for living people, or attacking them using bias. Our policies were not all set just to treat subjects with kindness. If we did that our articles might be barren indeed. We certainly need to treat subjects fairly, and with npov, but we are not exclusionary to future or current wikipedians. Everyone can edit here. Of course we have to use a certain "modicum of human decency and empathy" but we don't go overboard the other direction either and suppress pertinent facts because people don't like those facts. I don't know where this is coming from, but if it's really the way you feel I don't think we'll ever see eye to eye, but dialog is always good as it helps to see different viewpoints. Fyunck(click) (talk) 07:08, 8 June 2015 (UTC)[reply]
You're right, me being a HCI researcher into Wikipedia's collaborative workflows and a former legal monkey is of absolutely no relevance in discussions around legal liability and what makes people leave Wikipedia. Why did I even mention it? Look: the Foundation is protected from lawsuits by Section 230 of the Communications Decency Act, which absolves entities of liability if they merely acted as a publisher of defamatory content without exercising editorial control over it. When the Foundation passes rules that constrain editorial content, it weakens that protection; not fatally, but an amount. That is why they're less liable, as crazy as it sounds, without rules on defamation. And this wasn't my first account. We're absolutely exclusionary to Wikipedians! Anyone can edit, you say. As long as the people who can edit aren't appalled by a community that's okay with deadnaming trans people. Or...being massively incivil. Or any of the other things we tolerate. Your position is analogous to, to be crass, dumping sewer water in a pond and then claiming "hey, anyone can still swim in it, if you don't want to swim in it any more it's your problem, you could if you wanted to". I'm pretty amazed that you've genuinely claimed, though, that "we have to use a certain modicum of human decency and empathy" but also that offending trans people is A-OK. What does empathy and decency look like to you? Being decent about the things you think are problematic? If so, you should probably google that "empathy" word. Ironholds (talk) 17:23, 10 June 2015 (UTC)[reply]
You're amazed because I'm an amazing person. I find there's a HUGE difference between using a "certain modicum of human decency and empathy" and going overboard and suppressing facts. Timmy may not like being called a snot, but if all the sources call him a snot that fact will wend its way into an article about him. "Massively incivil?" Holy mackerel you must have some burr up your saddle to make a ridiculous statement like that about wikipedia articles and wikipedia editors. And perhaps you should research the word "modicum" while you have access to a dictionary. Fyunck(click) (talk) 18:22, 10 June 2015 (UTC)[reply]
You don't think there are tremendously offensive and rude Wikipedia editors? Huh. You should hang around certain content creators more. And this isn't about suppressing facts; this isn't about someone called Timmy being called a snot; this thread started, in your words, around "pronoun usage". The right of people to be identified in a way that adheres to the very basic, very fundamental elements of who they are as a person. If you want to convince anyone, you should start while explaining why that principle violates the maxim of "Encyclopedia first, and screw everything else!" - and defend that maxim. Not by comparing it to totally inadequate analogies like "someone calling Timmy a snot". The only thing you achieve when you compare gender identity to calling someone a snot is confirming that you don't get the scale of what we're talking about here. Ironholds (talk) 21:04, 10 June 2015 (UTC)[reply]
A couple things here. You are were talking about the wikipedia "community," not a few offensive knuckleheads. To be honest, some of the things you are saying here offend me! So you should practice what you preach. And this is about suppressing facts whatever you want to believe. Maybe not your specific viewpoint as I don't follow every single phrasing people write, but several prominent posters here. I'm a pretty courteous person and have no problems addressing people as they wish to their face, but the past is the past as far as I'm concerned and I'll follow the sources rather than rewrite history. My Timmy analogy might have been poor, but it was 100x better than your twisted sewer water analogy. Look, if Bruce wants to change to Caitlyn, that's her choice. If in referring to her we try and make sure we use she/her then that sounds perfectly reasonable to me. A "modicum" of courtesy seems called for here. Plus it can be easily sourced to boot. There are also times that we'll need to use "Caitlyn (formerly Bruce)", "Bruce (now Caitlyn)" and also simply "Bruce Jenner." It will depend on the situation, and the sourcing. The other thing.... I checked here and I never said anything with the term "pronoun usage." Do you have some nasty chip on your shoulder about me because you're confusing me with someone else? If so perhaps you should learn to read more carefully before the fangs come out. Now for me this is getting too personal and astray from the subject at hand which is whether the "survey is statistically invalid." I don't find it so at all and I found the original posting rather offensive to our editors, who for the most part are good people trying to help. Fyunck(click) (talk) 21:42, 10 June 2015 (UTC)[reply]
I'm not sure exactly what "legal monkey" means, Ironholds, but even if you were only a paralegal or law school student, not an attorney, you should know that a "right of people to be identified in a [preferred] way" cannot possibly exist in the legal system under which WP operates. Short of defamation and a few other extremely narrow exceptions, anyone can use any words they choose to refer to anyone else. You can make an ethical, social-norms, or other sort of claim, but not a legal one. Your legal training also already informed you that truth is an absolute defense to defamation, so even under the most tortured possible misinterpretation of [US] defamation law, using gender-non-neutral language not preferred by a biography subject could never be defamatory if the facts about the subject could render the gender-specific usage factual in any generally understandable sense. But no one with any legal undestanding would take seriously the idea that gender-non-neutral language could ever be the basis of a defamation claim to begin with. Since you must already know these things, given your legal background, it's unclear to me why you would make such an argument.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  16:10, 14 June 2015 (UTC)[reply]

Back to the topic at hand which was addressed to the closer about whether this "survey is statistically invalid." As I did a check it appears to me that a bit of canvassing was happening. I can't be sure because there could have been a mention of why these notifications went out, but I can't find it. So no trouble retracting if I'm wrong. I see that user Skyerise sent out bunches of notices to specific editors from June 4 to June 5 telling these individuals about this topic. Many of those are on her User:Skyerise/ATW sandbox page. Perhaps it's an equal mix of both sides of the issue, but if not it's blatant canvassing. Anyone (like an admin) want to confirm this? Fyunck(click) (talk) 22:20, 10 June 2015 (UTC)[reply]

I guess I'm a bit late to the party here, but did someone really just say that writing an encyclopedia is secondary to treating subjects with respect? I don't even know how to respond to something so misguided. -R. fiend (talk) 04:46, 15 June 2015 (UTC)[reply]

The problem is advocacy, we aren't here to break social barriers which is what some seem to want done here. If you want to make a difference than take your arguments off Wikipedia and do something to change things. As an encyclopedia though, we follow WP:RS. - Knowledgekid87 (talk) 00:58, 19 June 2015 (UTC)[reply]

Comments and sample articles

Admittedly sex-changes, especially so late in life, are tricky. I believe one should follow what the citations/sources say (not what the subject wants). At any give point, Jenner was either Bruce or Caitlyn, and referred to as either male of female accordingly by reliable sources. Cf. the FA article on Augustus, who had several different names over the course of his life and was referred to by historians by those different names; the article reflects this when describing the events of each time period. Other articles, off the top of my head, to possibly consider looking at (transgenders, gender-benders, pseudonyms) are: Wendy Carlos, Brandon Teena, George Eliot, George Sand, Mark Twain. Softlavender (talk) 01:02, 9 June 2015 (UTC)[reply]

Jennell Jaquays is another example of someone who gained fame under her former name/gender before transitioning. - Floydian τ ¢ 13:31, 10 June 2015 (UTC)[reply]
  • There's economist Deidre McCloskey, transited from Donald at age 53. The article's bibliography lists all works as by "Deidre". This certainly makes sense for reprints that use "Deidre" instead of the original "Donald". For earlier works, it may or may not be the same question as referring to Bruce or Caitlyn in the historical record. Choor monster (talk) 18:38, 23 June 2015 (UTC)[reply]
    Yes. This is another example of why we can't rewrite history, since most sources we cite are not reprints that make such editorial changes.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:29, 16 July 2015 (UTC)[reply]

Related (?) topic

Comment Can we extend this slightly? I understand that the article Hillary Rodham Clinton (the name she prefers to be known by) has been moved to Hillary Clinton. Her picture is still captioned Hillary Rodham Clinton. Can we set up a guideline to stop this sort of thing happening? 5.150.92.19 (talk) 11:14, 11 June 2015 (UTC)[reply]

It's more the other way around. WP goes by the most common name used in reliable English-language sources because this is what most people look for. The preferences of the subject lately aren't the criterion. Otherwise Cat Stevens would be at Yusuf Islam. The TG exception that's been carved out turn this on it is ear. So this question is: 1) Undo that exception, 2) extend it to everyone, 3) leave it as some weird exception that gives TD subject a special right as an article subject here that is enjoyed by no one else. Everyone one of this options will piss of a substantial number of people both on and off Wikipedia. The worst is #2, because it will impact the most readers. As for the HRC photo caption: It takes a while for all content to be cleaned up after a move.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:30, 18 June 2015 (UTC)[reply]

I just had a look at the discussion that caused this to happen and it seems that all the arguments are irrelevant. Surely if a person's name is X entering it in Wikipedia as Y fails WP:RS and WP:V. 5.150.92.19 (talk) 11:34, 11 June 2015 (UTC)[reply]

If we're going to defy WP:COMMONNAME policy to always use a transgendered subject's preferred name as the title of their article here, then we have to do that for everyone, or it's laughable bias problem. TG people are not magically "First Class citizens" with more rights than everyone else, us second class citizens.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  07:56, 15 June 2015 (UTC)[reply]
To clarify: I mean that the TG exceptionalism to COMMONNAME (and WP:MOS) puts us in the BIAS position of logically having to extend it to everyone or undoing it at least partially. I'm not actually advocating extending it to everyone. On a re-read, I realized the sarcasm wasn't clear. Anyway, I've read the requested move at Talk:Hillary Clinton or Talk:Hillary Rodham Clinton or where ever it is now. The arguments are not irrelevant under Article titles policy. And her name is both Hillary Clinton and Hillary Rodham Clinton; one's just a longer version. Anyway, the 3-party close on the HRC -> HC case was extremely well prepared and reasoned. It's exemplary. The problem isn't with that move, it's with the underlying decisionmaking tree in policy.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:30, 18 June 2015 (UTC)[reply]
SMcCandlish I think that it would be fair if we recognise in Wikipedia that, on this issue, we are actively and I personally think legitimately WP:SOAPBOXING on behalf of LGBT issues. Many of these people may face huge prejudice. In effect we are adopting a convention that, in some ways, is akin to Positive action to exert an influence in one direction while society variously exerts an opposing influence. There are a range of WP:NPOV issues that might be mentioned here perhaps including WP:RIGHTGREATWRONGS but, in many cases though not to extremes, I personally think that WP:IAR may reasonably apply. GregKaye 11:01, 18 June 2015 (UTC)[reply]
Sorta. It's more that one segment of the LGBT camp descended as a pack of WP:ACTIVISTs and changed something. I doubt it will last, but I say up top, just going back to the earlier status quo is going to make a lot of people angry. There may be some compromise somewhere.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:30, 18 June 2015 (UTC)[reply]

Name vs. Gender

This point may have been raised above, but if so, it is buried in the discussion and I could not find it. I think we need to separate the issue of "change of name" from the issue of "change of gender". There is no reason why a woman can not be named "Bruce". So... let us (for the sake of discussion) totally accept the argument that Jenner was a woman when she won all those Olympic medals... Her name was "Bruce" at the time. Once we accept that a woman can be named "Bruce", all the angst about what to call Jenner becomes irrelevant... We can treat the name change the same way we would treat any other name change... by using her "old" name in historic contexts, and her "new" name in modern contexts. Blueboar (talk) 13:06, 12 June 2015 (UTC)[reply]

Blueboar I think that both a differentiation of issues as well as a differentiation of article topics would be an advantage. Where possible I think that pronouns should be avoided totally. "Why say either she or he when "Jenner" is would be sufficient in most if not all cases. We are dealing with a person here and one who, while identifying as a female, was seemingly comfortable with the use of the male pronoun in the early June interview." This also raises the issue that different people are reported to experience self identification to a non xy chromosome based sex differently according to perhaps any number of parameters including extent and time of life. I also think that a lot depends on the way the individual person may regard themselves in retrospect.
The role played by the person is also significant and much has already been said in regard to Jenner's marriages and the ways in which these should be covered. GregKaye 10:39, 18 June 2015 (UTC)[reply]

Saying that "Jenner was a woman when she won all those Olympic medals" in the men's event is very problematic. Does that mean that she was the first woman to ever win a medal in a men's olympic event? Rreagan007 (talk) 02:35, 21 July 2015 (UTC)[reply]

Yes, and it's one of multiple reasons we can't do that.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  15:16, 22 July 2015 (UTC)[reply]

Suggestion

My sympathy goes to whoever has to close this, not only because the subject is controversial, but because it's confusing that there are multiple options, and the levels of support (or opposition) to any one of them don't at all correspond to the levels of opposition (or support) to the others. The only suggestion I can offer that might cut the Gordian knot is: when looking at the commenters who want to use the new name, and the commenters who want to use the old name, consider whether all of them are actually exclusive to the commenters who suggest using both names or not. Using both names isn't my most favoured option, but it would simultaneously "preserve the historic gender" and provide the clarity and attribution of accomplishments to the people (rather than the strings of letters) who earned them, and so potentially satisfy more people and concerns than either the "only use old name" or "only use new name" options would. -sche (talk) 15:34, 19 June 2015 (UTC)[reply]

I concur. While such an approach can't satisfy everyone, it will satisfy a lot of them, while doing no harm to reader interests, and give us something to build on instead of war about.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:26, 16 July 2015 (UTC)[reply]

The best solution for the biggest online encyclopedia, Wikipedia.

Currently, many people consider Wikipedia as a fake encyclopedia. Some of them say "Wikipedia can't be trusted, it contains all wrong information and everyone can change it". What I would like to propose is seen that on Wikipedia IPs will be always welcomed, why don't we protect all articles here permanently, as the Indonesian and others do. Or else the EDIT TAB at the top of the page must be hided. This will defend Wikipedia from vandalism and people will be trusting and caring more to Wikipedia. Otherwise all IP edits can be reviewed. Hope that everyone agrees with this perfect method.--Graspleonanymore (talk) 19:58, 21 June 2015 (UTC)[reply]

see Wikipedia:Perennial_proposals#Prohibit_anonymous_users_from_editing. Your suggestion is generally shot down because it won't actually address the issues as can be seen [12] where a registered user account inserts unsourced promotional content into an article. -- TRPoD aka The Red Pen of Doom 20:29, 21 June 2015 (UTC)[reply]
I think they are proposing that all pages use pending revisions for IP edits. Jason Quinn (talk) 12:40, 22 June 2015 (UTC)[reply]
Considering Wikipedia's grown into an amazing resource using an open model, it seems to me that you are arguing against proven successful methods in some strange bid to prevent failure. You registered your account yesterday. Why do you think you have the experience to know what the "perfect method" for Wikipedia is? If it is so easy and obvious, somebody among our many thousands of multi-year veterans would have figured out a perfect method and proposed it already. It is not so easy or obvious. As for the people who dismiss Wikipedia as having no value being it's open, consider them dinosaurs and just ignore them. Why should we change in response to people who have an inaccurate view of the world? Jason Quinn (talk) 12:40, 22 June 2015 (UTC)[reply]
Ip users contribute about 90% of edits and lots keep minor spelling and grammar in order. Could we consider a WP:SNOW for this? TheMagikCow (talk) 17:08, 22 June 2015 (UTC)[reply]
It's far fewer than 90%! Johnbod (talk) 13:22, 23 June 2015 (UTC)[reply]
It's closer to 40%. Dragons flight (talk) 02:23, 4 July 2015 (UTC)[reply]
Let's follow this to its logical conclusion and do away with pending changes for editing existing articles. Give IP editors the ability to create articles and put those articles into pending changes. At one stroke we get rid of AfC with its huge backlog and free pending changes reviewers to do something more useful - like reviewing new articles by IP editors. We don't need pending changes on existing articles because they are on watchlists and any vandalism is soon reverted, either by ClueBot or an editor. This proposal will be found at the top of this page and it needs discussion - it's been running for 31 days but so far only four people have !voted. — Preceding unsigned comment added by 164.127.144.1 (talk)
Yeah, I'd like to see some real stats on this. This probably does need to be re-examined periodically. At some point a line will probably be crossed where anons generate more mischief than positive results.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  02:03, 28 June 2015 (UTC)[reply]
I've got to support the anon here. As much of a headache as persistent vandalism is, the positives outweigh the negatives. There have been so many occasions when an IP, with poor formatting and bad spelling will post that tidbit of truth that can take fact-finding in a whole new direction. From these things that might even look like vandalism, there is truth that can be googled and sourced. Whole articles have been constructed from the path an IP has sent me on, and any editor who is conscientious about checking before pushing the vandalism button should have the same kind of story. As big as some people's egos are, we can learn things from other people. Trackinfo (talk) 04:26, 28 June 2015 (UTC)[reply]
I'm also going to support the "anonymous users" here. Vandalism is an annoyance; however even without IPs, vandals would just to take a couple seconds and register (no email verification!) There are many IPs that wish not to register for personal reasons, and many are constructive (contrary to popular belief; IPs are often presumed vandals by quite a lot). Some also see no reason to register; why would they do so if they just want to correct a grammatical error or do some quick editing? Esquivalience (alt) (talk) 02:15, 4 July 2015 (UTC)[reply]
It's not just vandalism, which implies deliberate destructiveness, it's also the disruptive editing that seems well-intentioned but is inept, and where, because of dynamic IP assignments, the proffered user warnings are apt to go unnoticed (or so it sometimes seems). I think Wikipedia could do a better job of sorting out the good from the disruptive IP edits. Dhtwiki (talk) 00:13, 5 July 2015 (UTC)[reply]
Ineptitude can go both ways. I'd like to think I'm an experienced editor, but I have had my own ineptitude corrected by anon IPs . . . today. It is amazing how fast information flows here. People are watching. We even have an effective, sometimes obnoxiously so, new article patrol. I have great faith in watched articles getting corrected. Your quality may vary depending on the watcher(s). I've seen some garbage in low traffic, poorly watched articles. Our problems come from unwatched articles. Right now that list is secret, which does to motivate the kind of diligent wikipedians we depend upon to watch, to take those articles under their wing. So who knows what is in unmonitored articles? Trackinfo (talk) 00:37, 5 July 2015 (UTC)[reply]
Experienced editors should not be inept, although they might miss things that a well-intentioned IP editor can be helpful in spotting, especially if you narrowly define ineptness as persistence in getting it wrong. Some IP addresses excel in that, and that is where the problem lies, not in IP users generally. As far as unwatched articles being a problem, I think that it's the high-traffic articles that are most prone to disruption, and where that disruption, if left unchecked, is most likely to adversely affect readers and give Wikipedia a black eye. Dhtwiki (talk) 23:11, 9 July 2015 (UTC)[reply]
As an anon user I can tell you that I would do far less cleaning up of articles if I was forced to register. I am overwhelmed with the culture of Wikipedia - all the rules, formatting, and quibbles. I just want to remove blatant vandalism and misspellings when I see it. Thanks for listening to my anon comment. (I hope I posted it right) — Preceding unsigned comment added by 70.190.222.225 (talk) 09:26, 11 July 2015 (UTC)[reply]
I am with 70.190.222.225 on this one. I first started editing Wikipedia as an unregistered user on 01 January 2006. I made a few mistakes and got into a few arguments, but it didn't take long to figure out that helpful edits like reverting obvious vandalism, correcting typos, and adding references to reliable sources where [Citation Needed] used to be pretty much never got reverted. I registered under this username on 09 June 2006 and nine and a half years later am still an active editor. I may not have ever gotten started if I had to jump through a bunch of hoops before seeing any results. Vandals, on the other hand, appear to be willing to jump trough all kinds of hoops to accomplish their vandalism. and I don't see other websites with involved registration processes having any shortage of trolls or vandals. --Guy Macon (talk) 13:46, 12 July 2015 (UTC)[reply]
I was an anonymous IP editor for four years before I created this account, and edited desultorily for four more years after that. I can see that letting people edit without registering can be an inducement to getting involved, but I don't see how continued IP editing is a necessity. If greater control of IP editing, while not doing away with it entirely, releases editors from the onerous chore of reverting disruption, that has to be weighed against the gain of attaching new people to the project, and the fact that a limited amount of disruption can be beneficial. Dhtwiki (talk) 23:17, 14 July 2015 (UTC)[reply]
I'm under the impression that editors now spend far less time engaged in "the onerous chore of reverting disruption" than ever before. WhatamIdoing (talk) 18:31, 16 July 2015 (UTC)[reply]
Re: OP's opening word "currently" – has always been true, always will be. Not a big deal. Were in the top 5 most-used websites in the world.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  15:16, 22 July 2015 (UTC)[reply]

Was "Own work" a disastrous choice for a descriptor for image uploads?

I do a lot of reviewing new draft articles for AFC, and I absolutely consistently, constantly see people uploading things like logos (especially logos), promotional photos, etc. as "Own work" to Wikimedia Commons. For a huge number of these cases, I'm pretty sure that the person didn't actually create the work, and in the few cases where the uploader does indeed own the work, I don't think they at all understand the implications of "releasing" your own logo under Creative Commons.

Is the problem that "Own work" gets constantly interpreted as "why yes, I am indeed the person who took a screenshot and then hit the upload button!"? Would we be far better of if the option was labeled something more like "I personally am the copyright holder of this work"? Sure, I bet a number of folks would just lie for the sake of convenience, but that's a problem no matter what. But I do think a large chunk of "Own work" labels are from people who simply have no idea what they're actually selecting, and/or no concept of derivative works.

I realize too that short of flashing a screen-wide animated "You must type the words I hereby release this text and images under CC version..." in huge flashing letters (and maybe not even then) we're always going to have people that don't understand the concept of releasing info to CC, but I think that the incredible vagueness of "Own Work" just exacerbates the problem. Is there any remedy to this at all, or do we just shrug and accept that a huge portion of our photos are not actually CC as Wikimedia states, but are mistakenly/illegitimately uploaded copyright works? MatthewVanitas (talk) 14:42, 3 July 2015 (UTC)[reply]

I don't know if this is a problem that can be fixed with mere terminology. Assuming that most users are using the upload wizards, the Commons upload wizard has a gigantic cartoon as the first step that explains the concept of derivative work. The English Wikipedia file upload wizard tries desperately to get users to use the Commons wizard if the user declares a free work, but if not, it still asks the user to declare that "I made this myself, from scratch, without copying or incorporating anybody else's creative work". I'm guessing that a lot of users just don't care. Regards, Orange Suede Sofa (talk) 18:23, 3 July 2015 (UTC)[reply]
As somebody who has spent a lot of work, over many years, in trying to improve the instructions we give to uploaders, I've come to the rather cynical conclusion that it doesn't really matter how we phrase these things. People will ignore them. It's not because they are difficult to understand (there's really nothing difficult to understand about "I made this myself from scratch", just as there is nothing difficult to understand about "a free replacement could be created", or "this image is the object of discussion in the article"). These things aren't difficult to understand but difficult to accept. People just won't accept anything that boils down to "sorry, no, you really can't use this image". People who come to our upload system just want to know "what do I have to do to upload this picture?" and won't take "nothing, you just can't" for an answer. People come here with their experiences of elsewhere on the internet, where nobody cares about copyright, and naturally assume that here, like elsewhere, copyright notices and licensing rules are just meaningless boilerplate that's there for form's sake and can safely ignored in practice. The only thing that would get the message of "no, we really, really mean that" across to such uploaders would be if somebody stood by to physically slap them in the face if when they proceed. Fut.Perf. 20:54, 3 July 2015 (UTC)[reply]
I believe that one of the major cable providers has a patent on physically slapping people in the face when they proceed... --Guy Macon (talk) 06:09, 4 July 2015 (UTC)[reply]
That would be a nice change from the major cable providers (in the US anyway) are usually metaphorically doing to a certain tender body part of their customers.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  07:09, 21 July 2015 (UTC)[reply]
For photographs of living people, a very large percentage of those uploaded as "Own work" are NOT photographs taken by the uploader. Particularly in evidence, for instance, are uploaders from Pakistan or India who claim photographs taken from all around the world as "Own work". These are obviously paid editors adding photos to the articles they have written and who don't know enough to provide the copyright documentation (from the photographer), or who do know to do that but would prefer to skirt the easily skirtable rules. Obviously we need to change the wording on uploaded photographs to read "I took this photograph myself" (rather than "Own work"). Softlavender (talk) 06:44, 4 July 2015 (UTC)[reply]
For whatever good it may do, I second the motion. --Thnidu (talk) 04:29, 6 July 2015 (UTC)[reply]
"I took this photograph myself" isn't clear enough. Sure I took it – right off that magazine's website! We would need something like "I physically pushed the button on the camera myself". Or maybe a pop-up window that would let people "subcategorize" the answers:
  • "Own work" – I personally pushed the button on the camera or drew this in illustration software, starting from a blank page.
  • "Own work" – I copied this all by myself from someone else's website.
  • "Own work" – I asked someone else to take this picture for me.
  • "Own work" – Somebody else made it, but I'm the person who is doing the work of uploading it.
Running a quick image search might be more practical. Then we could automatically reject things that are already on the web. WhatamIdoing (talk) 02:02, 11 July 2015 (UTC)[reply]
Rejecting a photo based on an image search assumes that editors who upload their own work do so exclusively to Wikipedia. I can guarantee that's not universally true. Regards, Orange Suede Sofa (talk) 03:20, 11 July 2015 (UTC)[reply]
Also, images from Commons get posted everywhere because they are CC released ... so of course an image that's been on Commons a few weeks can, and will probably, appear numerous places. Softlavender (talk) 03:27, 11 July 2015 (UTC)[reply]
Yes, but I'm talking about running an image search during the uploading process itself, when there will have been no "few weeks on Commons" for it to have spread all over. Also, if you publish your photo on some other website first, then it requires OTRS paperwork. The main drawback that I see is that an image search will capture public domain photos, e.g., off a US federal website – but those shouldn't be uploaded as "own work" in the first place. WhatamIdoing (talk) 18:36, 16 July 2015 (UTC)[reply]
  • Yes it was a disastrous choice! In particular, apart from some other cases discussed above, it encourages people who take photos of copyrighted things like paintings to claim the Picasso etc as "own work". I understand Future Perfect at Sunrise's cynicism, but the fact of the matter is that we don't even begin to explain what we mean, and never have, so we can't really know what would happen if we did. Johnbod (talk) 17:17, 9 July 2015 (UTC)[reply]
    +1. -sche (talk) 07:57, 12 July 2015 (UTC)[reply]
  • Definitely needs clarification. I've thought this for years.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:21, 16 July 2015 (UTC)[reply]

The description uploaders have to select in the file upload wizard here on en-wp in order to upload something as "own work" is the following: "This file is entirely my own work. I am the copyright holder. I made this myself, from scratch, without copying or incorporating anybody else's creative work, and I am willing to release it under a free license." How anybody could say that we "don't even begin to explain what we mean, and never have", is beyond me. What exactly does anybody propose could be further clarified about this (while keeping it short enough that people will actually read it)? Fut.Perf. 11:31, 16 July 2015 (UTC)[reply]

  • I would like this debate to continue to a conclusion, that as thing stand 'own work' and present explanations does not get the message across. On WP & Commons we don't like to resort to legal threat unless threats are leveled at us. Yet, it may be worth pointing out to potential unloaders that claiming ownership may have legal implications (to the up-loader) if they get it wrong. This Foundation's legal team would be wise to have an import on such a statement I think. Look in any publication and they prefer to use images from the big photo-libraries because they offer to pay for the legal cost if a client uses an image -only to then find out their getting sued by the rightful copyright owner. This gives the publisher confidence which they don't have when considering WP & WC images. For those that have been here for a long time they will remember that some up-loaders have faced legal challenges. Therefore, why not point out to potential up-loaders and underline it, that they up-load images at their own personal risk and so must not just click any box at random if they want to stay on the right side of the law. Think the Foundation's views would help because we have a policy not to offer legal advice and Jimmy would hate it if we appeared to be patronizing. Yet, why not reduce the image patrollers work-load a little, by giving potential up-loader this necessary information – and perhaps naïve up-loaders potential grief?--Aspro (talk) 21:38, 16 July 2015 (UTC)[reply]
    • May I suggest a sub-thread that proposes specific wording?  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  15:14, 22 July 2015 (UTC)[reply]

RfC: Increasing the activity requirement for retaining administrator rights

I'd like to finally start an RfC that is a follow on from this Idea Lab discussion, regarding increasing the requirements for activity for a user to retain their administrator rights. In 2011 a discussion came to the conclusion that admins who had not performed any edits or admin actions over a period of one year should be desysopped. These editors can request their tools back without a new RfA during a period up to 3 years of inactivity, after which a fresh RfA is required. The current wording of WP:INACTIVITY states that "Admin accounts which have made no edits or administrative actions for at least 12 months may be desysopped."

There has recently been concern regarding those administrators who make very few administrator actions per year - some editors feel that a higher level of activity is expected of administrators to ensure that they are up to date on Wikipedia policies and practices. Others are concerned about the lack of accountability of those administrators who only make one or two actions per year and are otherwise inactive. Another issue is the tracking of the number of administrators on Wikipedia; varying activity means that the number of admins does not accurately represent the number of admins actively carrying out administrative tasks.

Some statistics will be useful in addressing this issue, which I primarily got from this tool query (that link can take a minute or two to open/run, be patient!). There are, as of the time of this posting, 1347 users with administrator rights on the English Wikipedia. Of those, 918 (68%) have made at least one loggable admin action over the past year. 609 have made more than 10 admin actions, with the other 738 (55%) contributing a total of 1092 actions over the past year (about 0.1% of all 1,101,983 actions). Put another way, out of interest, 45% of administrators carry out 99.9% of all administrator actions.

My proposal is this: Changing the text of WP:INACTIVITY from "Admin accounts which have made no edits or administrative actions for at least 12 months may be desysopped." to "Admin accounts which have made no more than 10 administrative actions for at least 12 months may be desysopped." Sam Walton (talk) 12:34, 6 July 2015 (UTC)[reply]

Support (higher activity requirement)

  1. Support. 10 admin actions in 12 months seems about right. We need an up to date criterion that more accurately reflects and quantifies today's admin work. This would not only enable more rigorous pruning, but it might encourage some admins to be more active. At a time when en.Wiki editors and new content may well be converging on the moment when new 'promotions' may not be sufficient to meet desysoping for cause and natural attrition, to be aware of the true strength will help to plan for such a contingecy. --Kudpung กุดผึ้ง (talk) 12:37, 6 July 2015 (UTC)[reply]
  2. Support - an admin that only comes along once or twice a year to keep their status isn't really doing the job they volunteered for. I know real life happens, but even then an effort should be made. Primefac (talk) 12:38, 6 July 2015 (UTC)[reply]
  3. Support If a user who made less than 10 edit per year ran in an RfA, they would be laughed at. Why would someone who has recived these tools be held to a lower standard, where only one administrative action is required to stay as an admin. Makes no sence to me. Admistators who has been granted these tools should be held at a higher standards. I'm all for this. (tJosve05a (c) 12:41, 6 July 2015 (UTC)[reply]
  4. Absolutely support – I would have gone with 12 admin actions in 12 months (i.e. averaging to 1 per month). But regardless of whether an Admin is still editing, if they aren't using their tools more than about once per month, it's clear they don't need their tools anymore and should drop back down to "regular editor" status (plus Reviewer and Rollback and whatever) – and they'd still have one three years from that to ask to have the bit restored. This is a perfectly sensible proposal – Admin status shouldn't be a lifetime appointment: editors should have that bit for only as long as they intend to actively use them. --IJBall (contribs • talk) 12:56, 6 July 2015 (UTC)[reply]
  5. Support - You are given the tools to help the project - not to edit the project, editors do that. Spend a few minutes to work on a backlog, and done, and thanks. From the wider view, it will also help the community know when we need to make more admins to do those backlog tasks, that the current holder will, apparently, never do. Alanscottwalker (talk) 13:59, 6 July 2015 (UTC)[reply]
  6. Support Less than 1 action a month for a year doesn't seem too taxing. Why have the tools if you're going to sit around on your elbows doing sod all? Lugnuts Dick Laurent is dead 14:14, 6 July 2015 (UTC)[reply]
  7. Support ArbCom has already struck down WP:NOTCOMPULSORY for admins. The amount of activity required is not great, and if it, what do you want the tools for? Hawkeye7 (talk) 09:54, 7 July 2015 (UTC)[reply]
  8. Support This seems reasonable given that it is fairly easy to get the bit restored following removal due to inactivity. Gamaliel (talk) 23:15, 7 July 2015 (UTC)[reply]
  9. Support. We have too many hat collectors and not enough active admins. I agree with the statements made Sam Walton, and the statements made above. Adminship should be a "use it or lose it" proposition. If you're not actively using it, then you don't need it. There are many reasons to do this: security (elevated permissions on long-term inactive accounts is a bad idea), staying up-to-date with policy, accountability (making a minimal amount of admin actions per year can easily hide incompetence or bad faith), etc. It's good that people have volunteered to serve the project, but if they're incapable of serving the project, then they should step down. To retain your elevated privileges when you are not using them seems like hat collection to me. Wikipedia will welcome you back and restore your privileges once you are able to contribute again. NinjaRobotPirate (talk) 00:52, 8 July 2015 (UTC)[reply]
  10. Support, logical and sound idea. — Cirt (talk) 02:45, 10 July 2015 (UTC)[reply]
  11. Support: I decided to dip back into Admin closure of AfDs spurred by this discussion. I think that this Deletion Review says everything that needs saying --> Wikipedia:Deletion_review/Log/2015_July_10#Rhodes Bantam. --User:Ceyockey (talk to me) 15:08, 10 July 2015 (UTC) @Esquivalience:[reply]
  12. Support. Good grief we should at least be as careful as Wikidata [13], which requires at least five admin actions per any given six months. If people haven't been noticing clueless admins doing clueless or irresponsible Rip-Van-Winkle–like things after semi-retirement, lengthy (spells of) inactivity, or extremely haphazard WP participation, then I guess they haven't been paying attention, and also haven't noticed how quickly policies, guidelines, and best practices change on current-day Wikipedia (as opposed to Wikipedia in 2005). I would also greatly increase the edit-count requirement per year.Softlavender (talk) 03:41, 11 July 2015 (UTC)[reply]
  13. Support I don't see that this is going to gain traction, but I think it's a sensible thing to require of admins. I have a theory that it would rejuvenate the RFA process... but that's another story. §FreeRangeFrogcroak 18:30, 13 July 2015 (UTC)[reply]
  14. Support Adminship has become for too many a retirement award. We have a few very active admins working with a mop and too many others that forgot they were given a T-shirt for a reason. Chris Troutman (talk) 16:00, 16 July 2015 (UTC)[reply]
  15. Support Adminship is a status that entails responsible work. It's a position of trust. If an admin is not doing the work he/she signed up for, then they shouldn't have any reason to be an admin. Administrators help keep the operation of the site running smoothly, as well as granting permissions and blocking and unblocking users. Sam.gov (talk) 20:56, 16 July 2015 (UTC)[reply]
  16. Weak support I'm wary of some of the concerns expressed by the opposers—chiefly, that we don't have enough admins as is for all the work that needs doing. But the current activity requirements are quite basic, and the proposed ones still are. I don't know if there's a big problem of admins who don't do admin work, but anyone like that could use a gentle poke reminder to wield their powers for the good of the encyclopedia. Use 'em or lose 'em. Regardless of our requirements, I think we should make explicit that leeway can be appropriate. If someone experiences chronic or acute illness, or if they go do Peace Corps for a year, we should still be understanding and compassionate about real-life requirements. Admins are people too. --BDD (talk) 13:30, 17 July 2015 (UTC)[reply]

Oppose (higher activity requirement)

  1. Oppose I have a couple of concerns here. First, it's not clear to me (without several examples) why it is a problem for a sysop not to use their tools often - the question of measuring administrator activity to me speaks more of a misuse of metrics than of an issue with sysop behaviour. Second, how is "administrative actions" counted here? Surely not only logged actions would count. Third, it does not readily appear to me that low tool usage by whichever metric is a reliable predictor of one's understanding of policy, or that accountability is lacking for low frequency activity. Also, as a neutral question, how would this proposal shift the workload distribution? Jo-Jo Eumerus (talk, contributions) 12:46, 6 July 2015 (UTC)[reply]
    Based on the stats shown above, it appears it wouldn't shift the workload – it is still true that, currently, 50% of Admins do all the (logged) work. Now, it would be interesting to see if the other 50% is doing unlogged actions (and how many), but I'm not sure such stats will be readily available... --IJBall (contribs • talk) 13:07, 6 July 2015 (UTC)[reply]
  2. Oppose as being unenforceable, and per my reasoning below. The goal here, it seems, is to keep admin from gaming the system, but under current policy, once desysopped, the admin can just go to WP:BN and get the bit back, the same is true under this proposal. And how does this figure into the 3 years of inactivity? They have been active editing, lets say, so the 3 year period would never begin. It would mean that 10 years later, they could get the bit back as long as they edited some because they never went completely inactive to start the 3 year period. There are other holes I can poke, but this should be sufficient. Simply won't work, even if the proposal has good intentions. You can't piecemeal the policy, you have to rewrite the entire resysop policy to make any of this work, and that isn't trivial. Dennis Brown - 12:51, 6 July 2015 (UTC)[reply]
  3. Oppose. First, one of the most useful skills an admin can possess is knowing when to not take any action. This proposal devalues this skill and instead encourages action even when it would be better to either talk or do nothing. Second, this proposal assumes most, if not all, meaningful admin action show up in the logs. This is just not the case. An obvious example is editing of protected pages, an action routinely performed by admins working on the various sections of the Main page or monitoring Wikipedia:Main Page/Errors. Are these actions of no value to the project just because they are not explicitly logged as an admin action? --Allen3 talk 13:27, 6 July 2015 (UTC)[reply]
    While this is true, there are always a ton of admin actions that do need to be taken. There are always, for example, speedy deletion noms to be closed (mostly in the direction of deleting) and AfDs, XfDs, and RMs to be closed administratively. bd2412 T 18:54, 13 July 2015 (UTC)[reply]
  4. Oppose I'd be in favor of increasing requirements, but not of dropping general edits from the definition of activity. We don't want people taking admin actions just to meet a quota. Rhoark (talk) 14:02, 6 July 2015 (UTC)[reply]
  5. Oppose per Allen3. In addition, continuing activity requirements placed upon volunteers should be based on an ongoing expense for the organization just for keeping them on the rolls (like having to pay a medical doctor to conduct an annual physical exam of the volunteer), or the potential to do serious harm due to outdated skills (like a volunteer emergency medical technician who never bothered to pick up her Naloxone kit). Neither consideration applies to Wikipedia administrators. Jc3s5h (talk) 14:17, 6 July 2015 (UTC)[reply]
  6. Oppose We should not be desysoping people for inactivity at all in my opinion. We are volunteers after all and should not have some quota. Chillum 14:47, 6 July 2015 (UTC)[reply]
  7. Oppose I am on the fence as to whether we should be desysopping more admins for inactivity, as they are not harming the project by having the admin flag. I am opposed to the solution above because it will do absolutely nothing as Dennis points out below with his scenarios. This would require a complete rewrite to make it workable, not just a change to the one sentence. -- GB fan 15:20, 6 July 2015 (UTC)[reply]
  8. Oppose As in all responsible volunteer positions, admin work takes a toll and can lead to burnout. We want admins to be able to step back and take a tool break when they need without feeling this is the end. The last thing we need is burnt out admins making problematic usage of tools because when they are not at their best just because otherwise they lose their tools. On a side note, I always thought inactivity desysoping was because when an account comes back after that long it is hard to tell if it is the same person, or if they have changed, or if Wikipedia has changed. If the admin has not been using tools, but has been editing actively, they have not exactly lost touch of the community. They are probably aware of changes in policy and recent ArbCom cases. We also probably know if their judgement or behaviour has taken a turn for the worse. In this situation, what is the problem with a probably trustworthy admin having tools they don't use, or use rarely? Happy Squirrel (talk) 15:30, 6 July 2015 (UTC)[reply]
    Actually, one of the main reasons we desysop is security. To reduce the chance of a unused account being hacked while the admin isn't monitoring that email address. Many admin use dedicated email addresses for Wikipedia. I could think of a few PR companies that would pay a chunk of change to buy that hacked account, btw. Dennis Brown - 15:41, 6 July 2015 (UTC)[reply]
    In that case, an admin who has not used the tools, but has been editing should not be desysoped since they are not a security threat. They should be immediately aware if their account has been compromised. Happy Squirrel (talk) 20:44, 6 July 2015 (UTC)[reply]
  9. Oppose In a perfect world, no one would have to perform any administrative actions. This feels like requiring police officers to make traffic ticket quotas.--Jorm (talk) 15:37, 6 July 2015 (UTC)[reply]
  10. Oppose. The inactivity desysop was created to reduce the security risk associated with unattended admin accounts, which is reasonable. This proposal seems motivated by an entirely different animating principle, namely that admins who have low activity can't be trusted to do the right thing in the future. I don't buy into that principle at all. The core attribute of adminship is trust, and while trust can rise and fall for many reasons (some of which are not even directly connected to admin behavior), I don't believe that trust should turn on how many logged admin actions one creates. Dragons flight (talk) 16:18, 6 July 2015 (UTC)[reply]
  11. Oppose - on the face of it, I'm generally against proposals which will add to administrator attrition even a little without substantially improving the encyclopedia, and this proposal fails in that aspect. I'm also with other opposers who have pointed out that this isn't in the spirit of WP:INACTIVITY which is meant to protect the encyclopedia from genuinely abandoned accounts. Ivanvector 🍁 (talk) 16:23, 6 July 2015 (UTC)[reply]
  12. Oppose FWIW 10 actions a year is hardly "high activity". Next (as others have mentioned) this is much to much like a policeman having a ticket quota. It leads to taking an action just to take it and not considering whether the action is the right one. MarnetteD|Talk 16:30, 6 July 2015 (UTC)[reply]
  13. Oppose Per Dennis Brown, I can't see it being any use. Per Rhoark, we shouldn't be requiring quotas - even if all that's needed is to visit CSD once a year and delete the first 10, 12, or however many, things on the list without reading the articles. As to the RfA comment, quite right, we wouldn't hand out a mop to someone with 10 edits a year. But the person concerned here isn't at RfA. It only takes five mins to perform 10 deletions. Does it prove anything other than that someone has the password for the account? One action also proves that. One edit also proves it. But who has it? Peridon (talk) 16:55, 6 July 2015 (UTC)[reply]
  14. Oppose I think the current position where admins have the tool removed after going completely inactive for 12 months is about right. We should be be quite ready to remove the tools where an issue arises with that admin, but except for that an admin for makes any useful contributions should be welcomed. Also there are actions that only administrators can take that are not logged as such and as Dennis Brown says there is no way of tracking those. I do support however changing the statistic of measuring how many admins we have that are defined as "active" to make how that is measured stricter (or have a new stricter measure added), so we can measure how many significantly active admins we really have, but we should not desysop those who don't meet it. (I should declare an interest here in that I think I would have been desysopped under this proposal back in 2013, before getting sucked back in May 2014 and making thousands of logged actions this year) Davewild (talk) 19:02, 6 July 2015 (UTC)[reply]
  15. Oppose, I see no evidence that what this RFC aims to fix is a problem and this problem is serious enough to warrant further policy creep. Max Semenik (talk) 20:22, 6 July 2015 (UTC)[reply]
  16. Oppose Per Dennis and Happy Squirrel. Furthermore, in my opinion, all this will do is increase the potential burn-out for the "remaining" admins and cause us to have a net decrease in available admins in the not-too-distant future. -- Avi (talk) 20:48, 6 July 2015 (UTC)[reply]
  17. Oppose. An inactive admin has the potential to become an active admin again. Desysop them and they lose that potential for little good reason. {{Nihiltres|talk|edits}} 21:22, 6 July 2015 (UTC)[reply]
  18. Oppose, for several reasons. 1) I posted some similar statistics a couple of months ago, with the observation that the percentage of admins making no logged actions has changed very little over time (~33%) while a smaller number of admins have been accounting for a larger proportion of total admin actions. I would oppose any change with the potential to further decrease diversity in overall admin decision-making. 2) Per Allen3, who has correctly identified the importance of knowing how and when to do nothing. We should encourage people to do more nothing around here. 3) There's no evidence presented that there is currently a problem with the activity criteria, or that this proposal would solve any specific problem. Doing nothing about non-problems is just as important collectively as it is individually. You know what to do with things that ain't broke, right? COI: I was desysopped under the existing activity criteria, but it wouldn't have made any difference if this proposal had been in effect. Opabinia regalis (talk) 21:28, 6 July 2015 (UTC)[reply]
  19. Oppose - I'm for a higher requirement than one anything every 12 months, but I don't think that someone who is an active or semi-active editor should be desysopped. --B (talk) 21:33, 6 July 2015 (UTC)[reply]
  20. Oppose in its current format because IMO it is unfeasible and may deter any existing admins or put too much of a "quota" on them. However, lower the threshold and I'll see if I can support it. I agree with Dennis Brown's comment that the rule can be easily be gamed, so it's not feasible in any format, unless you change or eliminate the 3-year re-RfA requirement as well. Epic Genius (talk) 04:08, 7 July 2015 (UTC)[reply]
  21. Oppose - While I appreciate the need for administrators to be more active and up-to-date with the community, Wikipedia is not compulsory, and the spirit of that policy is that we shouldn't focus on demanding more from other editors—administrators and their toolset included. I agree with others who have said this might feel like putting a "quota" on them. In other words, the focus should be on improving the encyclopedia, not worrying about whether you've logged 10 admin things this year. That being said, the current policy of desysopping if an admin is completely separated from the project—no edits, no logged actions whatsoever—for 12 months makes sense. In the current case, we're not demanding more, we just want to make sure you're up to speed after a year-long break. Mz7 (talk) 05:43, 7 July 2015 (UTC)[reply]
  22. Oppose as per the above. We're not creating an incentive to remain active, we're just making it slightly harder to avoid going inactive. Also, the concerns about actions that would not fit into this metric (declined unblocks, for example) are worth looking at as well. UltraExactZZ Said ~ Did 16:15, 7 July 2015 (UTC)[reply]
  23. Oppose the current status quo of removing totally inactive admin accounts makes sense, but having an arbitrary quota does not. Not only does this not address any problem in particular, it unfairly discriminates against non-stereotypical admins who have the nerve to do activities which may leave them unable to access Wikipedia regularly, such as having kids, taking trips, doing missionary work, military service, etc. This would impair the diversity of the Wikipedia admin group even worse than it currently is. Andrew Lenahan - Starblind 22:47, 7 July 2015 (UTC)[reply]
  24. oppose none of the concerns listed as rationale for the change are of any actual concern. no "less active" admin has to my knowledge ever made a bad administrative action based on "old" interpretations. this is an attempt to fix a problem that doesnt exist. -- TRPoD aka The Red Pen of Doom 23:01, 7 July 2015 (UTC)[reply]
  25. Oppose Since there is no cloud, desysopping of someone that is editing can be reversed by request. What is the new activity requirement accomplishing? Dormant accounts with no activity get desysopped and in three years it requires RFA. This will do nothing to prevent an admin from simply requesting the tools back when they are desysopped. I'd rather have them game the system with one edit a year then to bog down bureaucrats with re-sysop requests when that becomes easier than the one edit per year game. In essence, this is replacing "one edit" with "one crat request" and is more burdensome. --DHeyward (talk) 23:12, 7 July 2015 (UTC)[reply]
  26. Oppose. It isn't that hard to do 10 admin actions in one year. If the purpose of this is to desysop the ones who make a few edits per year to retain adminship, how hard is it to do a deletion, block at AIV, AfD closure, [etc.] every month; or do a batch of them in a hour or so? The quota can be made higher so that there needs to be considerable activity to retain adminship; but admins may go semi-active for reasons out of their control. This change is also prone to ten times more wikilawyering and differing interpretations. Esquivalience t 00:30, 8 July 2015 (UTC)[reply]
  27. Strong Oppose. We have processes that can address the issues of an Administrator who is gaming the system to retain his or her hat. I see no reason to increase the minimum load; we already have too few mop wielders due to the fact that RfA is a brutal process that needs to be tamed a bit, and the fact that editors who have been around enough to DESERVE that mop are 'not a dime a dozen'. Administrators are people who willingly subject themselves to the magnifying glass of scrutiny in order to attain a few more buttons. They are volunteers; not employees we can just lay quotas on. I'll agree with other Oppose votes and say that there's no problem being fixed by raising the quota. Some Admins are dispute resolution masters, who may not wield their mop much. By adding a quota, we restrict those users and incentivize them to use their powers more than reason dictates they should by adding a quota. I don't care how easy it is to go out and find a vandal to bop or an article to speedily delete, they shouldn't need to do something for the sake of doing it. Melody Concertotalk 01:25, 8 July 2015 (UTC)[reply]
  28. Oppose - Desysopping admins who actively edit but perform less than 10 admin actions per year would not address any of the concerns. As an active editor, such admins would be aware of evolving policy and would be accountable. Rlendog (talk) 05:00, 9 July 2015 (UTC)[reply]
  29. Oppose - I think the proposal outlines the problem well but the proposed remedy is really a form of editcountitis. Besides, we have an admin shortage; if someone only carries out 9 useful admin actions in a year, well, every little helps. WaggersTALK 12:01, 9 July 2015 (UTC)[reply]
  30. Strong oppose - editcountitis indeed. And besides, this is a volunteer project. Every edit should count. Period. - jc37 06:42, 10 July 2015 (UTC)[reply]
  31. Oppose, solution looking for a problem. Stifle (talk) 08:44, 10 July 2015 (UTC)[reply]
  32. Oppose, per TheRedPenOfDoom and Stifle. This is most definitely a solution looking for a problem. Desysoping long-term, completely inactive accounts is one thing, but Administrator policy specifically states that an administrator is never required to use their tools. This proposal seems to go against the sentiment completely, for no reason. Things change around here, but they don't change that quickly or that dramatically. Any users who are capable of orienting themselves with adminship to begin with are definitely capable of reorienting themselves with it after a break, any time they need or want to do so. A user at this level does not simply 'forget' how to edit Wikipedia, and likewise they don't forget how to perform administrative tasks. While not a draconian proposal or anything, forcing us to meeti an arbitrary quota of administrative actions will not separate a good admin from a bad one, nor will it improve the project in any way I can forsee. Swarm we ♥ our hive 08:01, 11 July 2015 (UTC)[reply]
  33. Oppose - Nothing wrong with the policy we already have, If you're editing you're still active regardless of tool-use, Personally see no point to this. –Davey2010Talk 05:44, 12 July 2015 (UTC)[reply]
  34. Oppose We don't impose a minimum number of edits to retain a registered account, so why should we impose a minimum number of admin actions to keep the admin tools? TomStar81 (Talk) 12:27, 12 July 2015 (UTC)[reply]
  35. Oppose I worry that it will lower the quality of admin work if it provides a slight incentive to rack up admin action count. Not sure I want to see an admin that is a couple shy feeling like they have to quickly block someone or something at the end of the 12 month cycle, even if they try to be careful in what they choose I can see such pressure causing mistakes to be made. PaleAqua (talk) 08:10, 13 July 2015 (UTC)[reply]
  36. Oppose. I don't use the tools often because I focus on content and seldom see a need to use them. I don't search out admin tasks to do, but if I see something requiring attention, it is useful to be able to deal with it. Everyking (talk) 17:40, 13 July 2015 (UTC)[reply]
  37. Oppose Pretty much per PaleAqua, quotas that could pressure admins into using their tools when uncertain seems a bad idea.Bosstopher (talk) 17:49, 13 July 2015 (UTC)[reply]
  38. Oppose Dennis Brown's objections are persuasive. Neljack (talk) 01:51, 14 July 2015 (UTC)[reply]
  39. Oppose - Not convinced on the need for this and the current policy, which I supported from the start, is sufficient for dealing with abandoned admin accounts. CT Cooper · talk 07:53, 14 July 2015 (UTC)[reply]
  40. Oppose - This is a very bad idea: we do not need to impose a ticket quota on administrators as if they are patrol officers working traffic. Imposing minimum requirements on marginally active admins is not going to lead to more good admin decisions. Dirtlawyer1 (talk) 22:32, 14 July 2015 (UTC)[reply]
  41. Oppose - This is just looking for something else to police. And it breeds distrust. We're mostly competent people here, and there are already procedures in place to deal with the incompetent ones. Kingturtle = (talk) 13:27, 15 July 2015 (UTC)[reply]
  42. Oppose We elect admins to use the tools given to them when their judgment tells them to do so, not to fulfill a quota—even a small one. I simply don't see a benefit in this kind of thing. This simply gives administrators who are inactive the motivation to turn up, do ten admin actions in one blast—burn through a few CSDs or RFPPs and then disappear again. This is extra workload for crats/stewards for no real benefit. The only purported benefit I'm seeing is that if we have some idea of the actual number of active administrators, we can make efforts to recruit more administrators to make up the shortfall. But we can't. The bottleneck is RfA: there are good qualified candidates who could become fine and productive administrators, if we didn't subject them to the strange and barbaric week-long hazing ritual. The account security benefits are already provided by the existing desysop-on-extended-inactivity policy. If one wishes to rally together support for getting more administrators, simply look at metrics of admin activity and point out why the current number of active admins doesn't match the admin workload. And if getting more people to do admin work is needed, why not simply drop an email to one of those existing admins saying "hey, we miss you at Wikipedia, we really need active, smart admins working in this area and would love to see you back!" Carrots and niceness seems better than hitting people with sticks. —Tom Morris (talk) 08:07, 16 July 2015 (UTC)[reply]
  43. Oppose - I agree with the majority of the sentiments above. De-sysoping is really only necessary if the tools granted by this right are being abused, or if ones conduct is egregious.Godsy(TALKCONT) 08:14, 16 July 2015 (UTC)[reply]
  44. Oppose: We need more admins, not fewer. I agree with people wanting to see a high activity level for approving a new admin (I recent voted against a candidate partially on the basis of a paltry activity level), but everyone needs wikibreaks, and some of us bail for a year or longer doing other things in our lives, only to return to high activity levels later. This is true of admins as well as non-admins.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:19, 16 July 2015 (UTC)[reply]
  45. Oppose — Protip: admins (myself included) aren't going to magically make more time they already don't have just to meet some stupid, arbitrary requirement, and creeping up baseline activity requirements is just going to result in more people feeling disinclined to return after periods of absence just to avoid the annoyance of the bureaucracy involved with resuming. I've gone many months without activity at times (because real life gets in the freaking way of volunteering), only to finally find myself with some free time to tackle some CSDs or something. Proposals like this, while well-intentioned, are fundamentally ignorant in premise and assumptions; for, they assume people like me need prodding to stay active or some other crap like that. We don't. In fact, I basically go through withdrawals and start feeling edgy if I've been deprived of free time to put in to volunteering. The only thing you're going to accomplish by trying to force us to do more (by the cracking of a whip, it seems) is to make us leave or just not care enough to jump through the hoops any more if we fall behind. Any admin worth their weight in salt will, after any period of inactivity, check guidelines or policies to make sure whatever they're doing is "up to code" before taking action, and if they forget or something slips by, they'll happily admit "my bad" and undo something if they screwed up. It really isn't a big deal if, for example, something gets speedily deleted accidentally because of some minor CSD wording change or something, because everything has an undo button and/or a process like DRV exists to deal with out-of-process actions. What matters more is keeping people who have a history of trustworthiness around, and, failing that, keeping the porch light on so that they always feel welcome to return and pick up where they left off. Good admins—no, good volunteers—are basically like good friends: you can be apart for years and still pick right back up where you left off. --slakrtalk / 01:06, 18 July 2015 (UTC)[reply]
  46. Oppose - for the reasons stated above. Neutralitytalk 19:16, 20 July 2015 (UTC)[reply]
  47. Oppose at first glance this seems a medium price to pay for something that a few people think is sensible even if they can't come up with a good rationale for it. 1092 logged admin actions a year looks at first glance like the equivalent of losing a one pretty active admin, but longer term we have lots of admins who have the odd inactive year, so the admin actions we would lose in subsequent years are likely to be far greater. And of course not all admin actions are equal, an evening on huggle blocking vandals or a couple of hours clearing the expired prod queue would easily pass this test, occasionally closing RFCs or appointing autopatrollers would take far longer to generate ten admin actions. ϢereSpielChequers 21:39, 22 July 2015 (UTC)[reply]

Discussion (higher activity requirement)

  • That is a sticky situation, as we are learning at AE. Consensus seems to be that doing certain actions that only admin are allowed to do, ie: close an AE discussion, are indeed "admin actions" yet no log is shown of it. I would also argue that the quality of an admin isn't measured by the times you block someone, but arguably by the number of blocks you can avoid by careful mediation. The fact that you have the tools and the editors know you CAN block if needed, is sometimes helpful in an edit war, for instance. The same for ANI/AN3, an admin can lend his expertise in an official capacity without actually using the tools, in what is arguably an admin role. Much of the power of the admin bit is when you don't use it. On the opposite side, you might have admin that only use the tools on articles they themselves are interested in and editing. Moving over redirects and the like. Even though they are only serving their own interests (and ours, of course), they wouldn't be under scrutiny because they fall on the "ok" side of this measuring stick. Their contributions to the community, however, may actually be less than the admin that mentors, mediates and monitors. I'm not arguing against the logic in the proposal, but I think it would be hard to be completely fair and mistakes could happen too often, as proposed. Dennis Brown - 12:44, 6 July 2015 (UTC)[reply]
  • Couldn't most of this concern be satisfied by a "better accounting" of Admin actions? I remember this point was made in the previous discussion, and it does seem like there are "holes" in this system – "Admin-type actions" that AdminStats isn't "catching" in its count, and probably should be. --IJBall (contribs • talk) 13:01, 6 July 2015 (UTC)[reply]
  • I do not think this is a problem. First, most (if not all) of the admins who are inactive are really inactive - not that they are active in non-logged actions and not active in logged actions. Making 10 logged actions takes 5 minutes - for example, we have about 2000 broken redirects which are amenable to speedy deletion. And, if this is a real issue, i.e. an admin is active in a non-logged part but for whatever reason does not want to make logged actions - they will be perfectly capable explaining this to crats, pointing out their activity, and avoid desysopping.--Ymblanter (talk) 13:28, 6 July 2015 (UTC)[reply]
  • Per your reasoning, "most (if not all) of the admins who are inactive are really inactive", this makes the proposal an unnecessary layer of bureaucracy then. It means it is answering a question that no one is asking. I think the current policy makes sense, and it could be tweaked, but adding something like this would require rewriting the whole policy due to all the loopholes, and I'm not convinced there is any real benefit from the effort. I'm not arguing against the principle, but this proposal is unworkable, and I lack the imagination to propose a better one at this time. Dennis Brown - 14:43, 6 July 2015 (UTC)[reply]
  • Let me offer some scenarios...
Scenario 1: I quit using the tools but still do a little editing each month. One year from now, you desysop me. I go to WP:BN and ask for my tools back. Policy says I can do this as they weren't taken under a cloud and there isn't a 3 year period without edits. Proposal doesn't work.
Scenario 2: I quit using the tools but still do a little editing each month. I get the notice that I'm about to be desysoped (required), so I quickly go and make 10 admin actions so I won't be. You know, sloppy RFPP protections or close a few early deletes at AFD, no need to be good actions, just actions. Proposal doesn't work.
Scenario 3: I quit using the tools but still do a little editing each month. I get notice I'm about to be desysopped (required). I let it happen. I continue to edit some every month for years. 5 years later, I go reclaim my admin tools because there was never a 3 year period of inactivity, and policy says there MUST be 3 years with NO editor activity to force me back to RFA. Proposal doesn't work.
It isn't about being against the principle, it is that this is a completely unworkable proposal as written. The entire policy would have to be rewritten, "admin action" has to be defined, there has to be a way to search for admin actions that aren't logged, etc. Good intentions, but bad idea. Dennis Brown - 14:54, 6 July 2015 (UTC)[reply]
I think the problem you are talking about at is that of people who are not here to create content, and this proposal is not really intended to address that. Hawkeye7 (talk) 12:19, 7 July 2015 (UTC)[reply]
  • If something like this were to move forward, I would prefer something similar to what I've workshopped at Wikipedia talk:Bureaucrats#Activity requirement; allowing a longer period of time, and commenting or acting as an administrator counting as administrator activity (to recognize that many administrative acts aren't necessarily reflected in Special:Log). This could be rather difficult to determine in any automated fashion, mind (much moreso than bureaucrats, anyway). –xenotalk 20:30, 6 July 2015 (UTC)[reply]
  • The only real way to do this sort of thing would be to add a flag to edits, similar to the minor edit flag, that would label them as edits made in an administrative capacity. Actually, if used properly, that might solve quite a few problems, wouldn't it? (I should send this to VPT!) Take the current proposal. Did you close an AFD? Tag it as an Admin edit, and there's one administrative action. Decline an unblock? There's two. And so on. But until we have something like that, this proposal doesn't work. UltraExactZZ Said ~ Did 16:12, 7 July 2015 (UTC)[reply]
  • Interesting idea! It would solve a lot of problems. –xenotalk 16:23, 7 July 2015 (UTC)[reply]
  • Yes, that is an interesting proposal – I don't recall anyone suggesting this before. --IJBall (contribs • talk) 20:36, 7 July 2015 (UTC)[reply]
  • Comment This is similar with what the Commons requires where they define "active" as 6 admin actions over the previous 6 months (without a discussion). However, if there is some reason why an admin is inactive (work, illness, travel, real life), they just have to post a notice within that 6 months and they are considered active. If the definition of "inactive" is broadened, I think there should be a similar proviso where communication with an inactive admin would restart the 6 month period. People have legitimate reasons for becoming inactive.Liz Read! Talk! 20:05, 7 July 2015 (UTC)[reply]
  • II think we might want to at least ask admins who have not used the admin rights at all in the last year or so if they want to m keep it, or be removed from the active list. This really doesn't even require a policy change--anyone could do it. `DGG (at NYPL) -- reply here 00:33, 9 July 2015 (UTC)[reply]
  • I am still not quite sure why this is being discussed... why does it matter if an admin goes inactive? As far as I know, there is no limit to the number of people who become be admins... so it's not as if keeping an inactive admin on the roles is preventing someone else from becoming an admin. So what is the problem with keeping inactive admins? Blueboar (talk) 01:15, 9 July 2015 (UTC)[reply]
    @Blueboar: The general view among IT security professionals is that idle accounts pose a security threat, and obviously idle accounts with additional permissions pose more of a threat. TBH there's not much reasoning behind that view other than the fact that if someone hasn't accessed their account for a while, you can be fairly sure they haven't changed their password recently, making them more vulnerable to a brute-force attack. Also if a user isn't regularly monitoring their account they're unlikely to notice if someone else hacks into it. WaggersTALK 11:56, 9 July 2015 (UTC)[reply]
    Right: making edits but not performing any administrative actions is explicitly not a problem from an account-security perspective. Opabinia regalis (talk) 05:11, 10 July 2015 (UTC)[reply]
  • Comment I can see a clear need to remove the admin right for totally inactive accounts to prevent someone other than the original editor gaining access. In several instances I have cleaned out the home of someone who passed away, and in other cases I have found a box of some deceased or incapacitated relative's personal papers. It would seem likely that such effects would sometimes include a list of online accounts and passwords. For my own such listing, the passwords are encrypted, but I doubt that is common. Others may keep such info in some computer "password vault," but that seems hackable. As others have stated above, a stolen admin account might be of value to various parties such as PR firms. A turnoff of admin rights after perhaps a year of total inactivity would be of value, just to keep the password and account name from falling into the hands of someone else when the admin is no longer with us in one way or another. If the editor returns from an overseas military deployment, or finishes his novel or dissertation, or her new baby is old enough not to need constant care, or he recovers from the illness, then he can ask for the bit back, if he did not leave under a cloud. Imposing a work quota on unpaid volunteers is silly when there is little or no expense associated with allowing the volunteer some status. Does Wikipedia pay for insurance/bonding for the volunteer? Pay anything monetarily? Provide office space or computer equipment? Pay so much for annual credit checks or security checks? Provide health care or pension contributions? What is the annual cost of maintaining a computer file that says the volunteer editor has the admin bit? Some small fraction of a cent, perhaps? But the volunteer has contributed thousands of hours of work in most cases to achieve a record which motivates the community to grant him the bit. Eagerness to remove the bit unless the volunteer meets some arbitrary work quota seems puzzling. Edison (talk) 17:58, 10 July 2015 (UTC)[reply]
I am puzzled by your puzzlement? Sure they're volunteers - they volunteered to do something - and we accepted them because we needed it done. If adminship is a position of trust then they have breached trust because we trusted them with the tools to improve the project but they're not doing that -- they have wasted our time in granting, or in continuing to grant, them that trust. Volunteering to do something, and then not doing it, is frowned on everywhere in life. Alanscottwalker (talk) 16:10, 12 July 2015 (UTC)[reply]
If you are that angry at some volunteer who does not do a quantity of work you require, then stop paying her. How on earth does it cost you time, effort or money for some to keep the bit when they do not run around all the time blocking and deleting? Some of us are content adders and use the tools when we encounter something which needs them. How many hours a year do you devote to "continuing to grant" the admin their bit?Edison (talk) 21:11, 14 July 2015 (UTC)[reply]
That didn't make any sense at all [to me; evidently it did to someone else]. You can't "stop paying" someone that isn't paid. That's what volunteer labor is: unpaid.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:17, 16 July 2015 (UTC)[reply]
That's the point, SMcCandlish. Alan is claiming that a volunteer who is less than ideally active (at this particular point in time) is imposing some sort of cost on Alan. It sounds like he has to spend a non-trivial amount of time "continuing to grant" trust to them, or their admin bits will somehow expire. AFAICT, everyone else thinks that it's faster to "continue to grant trust" to all existing admins (elapsed time on task: 0.0 seconds) than to actually determine which admin bits should be revoked. WhatamIdoing (talk) 18:46, 16 July 2015 (UTC)[reply]
If you say so. I agree with the premise that re-extending trust takes no time investment, and I opposed this proposal, too. But "stop paying the volunteer" didn't parse. Maybe I'm being too literal and missing some joke.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  00:51, 21 July 2015 (UTC)[reply]
It does not parse because Edison and WhatamIdoing are not responding to my comment(or they are stating claims that I did not make--is it possible they don't know what volunteer means?): 1) there is no pay - admins know that going in (as do editors); 2) no one has said you have to fulfill the 10 actions in 12 months by blocking or deleting; 3) it has nothing to do with anger; 4) cost to me is not even discussed in my comment; 5) there is no 'determining which admin bits to revoke' for non-admining, they're revoked until such time you decide you want to volunteer to do those admin things again and demonstrate how you'll benefit the project with them - and then you can request it back); 6) we have editors to edit, admins are not given the tools to edit (and, at any rate, the non-active are not using them to edit apparently or they would use them, at least, less than once a month). 7) trust is earned in the doing, it's earned day-by-day - that's how trust is generally understood. Finally, redundant admins are just that, redundant -- we either don't need new admins or, hey, you volunteered to use those tools to do things that are needed, so, you know, do it. -- Alanscottwalker (talk) 22:19, 23 July 2015 (UTC) But perhaps I am missing something, serious questions: is it that important to admins that they are admins, even if they don't show a use of the tools? Is it just a status thing ("big deal") to them? Alanscottwalker (talk) 22:43, 23 July 2015 (UTC)[reply]

Protected Class and non choice characteristic defined groups

Protected Class and non choice characteristic defined groups may need greater policy support within Wikipedia content creation. Protected class is a legal definition which informs Wikimedia wide policy WP:NDP. Not all Protected classes are non choice defined groups, non choice classes include gender, race and disability, where a characteristic places an individual in a group beyond any consideration of personal choice. It is notable that WP:BIO would provide significant protection for an individual where content dealt with an issue realted to their belonging to a Protected Class, including any non choice characteristic defined group. By comparison unnamed people who are accorded membership of a non choice characteristic defined group receive no such protection despite the fact that this may allow aspersions to be cast on the group as a whole. Sources, through use of poorly defined collectivising terms such as “community” can present a story in which a whole category of people is presented as harbouring or supporting extremists or persons comitting or intending criminal acts. WP:LABEL offers some guidance, but unless a specific term is used it may not apply and WP:WEASEL provides that: “a reliable source may use similar expressions if they accurately represent the opinions of the source.” Thus while Wikimedia has protective policies on groups of people WP:NDP, and Wikipedia has protection for individuals WP:BIO as well as policies that in some part protect oppressed groups– there exists gaps in which Wikipedia content allows the collective impugning non choice defined groups. For an example see discussion at: [[14]]

Resolving this apparent lack in Wikipedia policy might perhaps be achieved by extending the relevant parts of WP:BIO to non choice characteristic defined groups. There are good reasons not apply this extension to, for example religion which although it is a Protected class, must be assumed to attach a large measure of personal choice to an individual, it would also not apply to named organisations per WP:BLPGROUP. The problem overall may be assumed to be small, however as things stand there does exist the capacity for Wikipedia to act as a propagator of discrimination on the basis gender, race, disability and illhealth with its process of content generation. --In Vitro Infidelium (talk) 11:38, 8 July 2015 (UTC)[reply]

The classifications to which WP:NDP applies have virtually nothing to do with "non choice characteristic defined groups". I cannot make sense out of this, so I cannot comment on whether this might lead to a reasonable proposal. — Arthur Rubin (talk) 09:18, 9 July 2015 (UTC)[reply]
To repeat from above - "non choice classes include gender, race and disability, where a characteristic places an individual in a group beyond any consideration of personal choice." Gender, Race and Disability are all covered by WP:NDP. None of us can chooose, at least not at birth, our gender or race and few people would regard disability in whether acquired childhood or aduthood as a 'choice'. What matters in policy terms is whether the protections of WP:NDP, together with WP:BIO should have some application to WP content which deals with members of non choice classes, where content may otherwise promote discrimination against such a class, both individually and collectively. This is surely not a difficult to grasp concept ? --In Vitro Infidelium (talk) 13:41, 9 July 2015 (UTC)[reply]
Thinking over Jewishness, Apostasy in Islam, neurodiversity, autogynephilia, paraphilia, Rachel Dolezal, race, etc... I foresee absolutely massive shitstorms being the result of defining official policy on whether different group identifications are voluntary or not. Rhoark (talk) 16:45, 9 July 2015 (UTC)[reply]
Wikimedia's nonsdiscrimination policy has nothing whatsoever to do with the content of Wikipedia articles. It's talking about the conduct of the Foundation, whom they hire and so on. The protected class notion is specifically from United States law (of special relevance to WP because of the location of most of the servers), but US law has the First Amendment, which protects content. So there is no legal issue related to "protected classes", and the remaining points have to do with WMF policy, which In Vitro Infidelium has misinterpreted. --Trovatore (talk) 17:05, 9 July 2015 (UTC)[reply]
Yep. WMF policy is not about WP article content, with is determined by reliable sources (and where malfeasance in editing makes that temporarily untrue we already have policies that steer the community to fixing those cases).  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:16, 16 July 2015 (UTC)[reply]
  • Note: This thread overlaps with #Adoption of a non-discrimination policy, below.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:16, 16 July 2015 (UTC)[reply]
  • Oppose: Thought this over (in relation to the related thread and the "essay"/debate page it's spawned). I have to occur with Arthur Rubin that isn't really cogent, and with Rhoark that this is a "shitstorm" factory (even aside from the fact that WP editor interaction has nothing to do with WMF's internal employee policies). The entire notion that all innate qualifies of someone are somehow special and immune to criticism is a non-starter. Lots of people appear to be congenitally stupid or douchebaggy, but this doesn't even anyone a magical right to be moron or flaming jerk as an editor, nor to have articles about them stripped of RS'able coverage of their encyclopedically relevant blunders or asshattery. Some legal systems, and some international accords of varying levels of ratification (and near-zero enforcement) treat certain characteristics (sex, ethnicity, etc.) as thing to not persecute people for. But WP has a far broader set of policies against persecuting people. Finally, the bureaucratic/legal concept of "protected class with non-choice characteristics" simply isn't relevant to WP, within with bounds of legal expression (i.e. short of libel, incitement, privacy law violations, etc.) There is no "lack in Wikipedia policy" to "resolve" here. That someone thinks there's an "apparent" one is an individual perception problem.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  04:15, 21 July 2015 (UTC)[reply]

Adoption of a non-discrimination policy

According to Roger Davies, discussions relating to an open Arbcom case considered the possibility of recommending that the community adopt a policy similar to the WMF's non-discrimination policy. His comment is here and it would seem that the ArbCom are unlikely to pursue that line at least in the present case. I know that there have been numerous attempts to micro-manage/enforce various notions of civility on en-WP, which usually hit the stumbling block of subjectivity, but has there ever been a formal proposal to implement something along the lines of non-discrimination? If yes, what came of it? - Sitush (talk) 14:15, 11 July 2015 (UTC)[reply]

Hey Sitush There was a discussion in 2009 to adopt something similar. It died because, I suspect, it was too complicated and too gold-plated. The failed proposal is here; the adoption discussion, such as it was, took place on its talk page.  Roger Davies talk 06:53, 12 July 2015 (UTC)[reply]
The 2009 proposal is practically laughable, with bits like "Wikipedia's discrimination policy should supersede any other Wikipedia policy" (identifying in particular notability) and trying to use "dignity" as a justification for censoring images of genitalia (not expressing an opinion on them, just noting the folly of trying to purge them as "discrimination").
That said: I like the idea of a non-discrimination policy. The question here is what practical effect one would have, given that it is mostly covered by civility and in theory already existent through the WMF's policy (the WMF's policy is reiterated at Wikipedia:Non discrimination policy). What do we add? As Roger Davies already noted (in Sitush's link), the risk is that we generate a big pile of fodder for wikilawyering. That, plus the usual issues with policy creep{{Nihiltres|talk|edits}} 15:55, 15 July 2015 (UTC)[reply]
Thanks for the link, Roger. Nihiltres, yes, the 2009 thing does seem at least naive and, yes, the scope for wikilawyering might be huge even if a less naive attempt were made now. I guess the devil would be in the detail. - Sitush (talk) 07:36, 16 July 2015 (UTC)[reply]
The amount of resistance met even trying to address basic sexism and other bias issues on WP is higher than one might expect, so that would be a stumbling block to adoption of such a policy here (even one not based on subjective stuff like "dignity"). The libertarian-right stream that wends its way through the dominant "US West Coast privileged white male nerd" editing bloc that dominates WP (and of which I'm a statistical member if not an ideological one, nor sharing the ideology of their main, left-wing oppoents, being a "classical liberal" myself) tends to see all bias-, minority-, gender-, and culture-related concerns as "just a bunch of p.c. 'microagreesions' crap" by WP:ACTIVISTs looking to soapbox and POV-push in campaigns to right WP:GREATWRONGS. To their partial credit, they not actually wrong about this in every single case (cf. the tendentiousness and meatpuppetry that has been going on in efforts to get WP to essentially rewrite history just make transgendered bio subjects happier), just usually wrong. Tthere's a frequent inability of that mindset to distinguish between 1) socio-political agendas that push writing that isn't actually better (largely external forces trying to affect our content in the course of remaking the world), 2) inappropriate behavior in furtherance of genuinely better writing (an internal ends-justify-the-means issue), and 3) genuinely better writing that accounts for real societal mores and which isn't pursued tendentiously (this is not actually a problem of any kind).

This cognitive dissonance is an impediment to making progress on the general WP:BIAS and WP:GENDERGAP problems, because it falsely equates anyone who raises a legitimate sexist language concern (as an example) with kooks who want to change English to use made-up gender-neutral pronouns like zie and hisr, or refer to woman doctors as "doctresses" (or contrariwise to totally erase -ess from the language), etc. Even the community consensus changing over time to now accept simple things like using diacritics correctly in Latin-script names in which they belong has met resistance from this same ideology, and there's a strong current of jingoism, linguistic prescriptivism, and other forms of traditionalism in this thinking and approach.

Even aside from this "new traditionalism" trend, it really would be difficult to craft an anti-discrimination policy in a way that it couldn't be abused as "a wikilawyer's charter", as you put it in the post of yours quoted at the link provided by the OP. Between reasonable concerns and unreasonable resistance there doesn't seem to be much room for such a policy to evolve. If it did, it would have to start, at least, as something about editors' behavior towards other editors, the way the WMF policy is about internal behavior, and not address the content of public-facing edits.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  10:50, 16 July 2015 (UTC)[reply]

  • Someone started an RFC on WP:HARASSMENT but I hope discussion will be moved here. I'm very happy to see this started here. Thank you Sitush. EvergreenFir (talk) Please {{re}} 20:50, 16 July 2015 (UTC)[reply]
  • Howdy Sitush. Any attempts to create a Discrimnation policy on Wikipedia, will fail. It's impossible for anyone to be completely certain about another Wikipedian's RL identity & thus such a policy wouldn't succeed. In fact such a policy would create divisions in the community. GoodDay (talk) 13:14, 17 July 2015 (UTC)[reply]
    @GoodDay: "Impossible to be completely certain", sure, but if people reveal or imply some personal feature (e.g. gender), that's enough for jerks to potentially discriminate over. The real concern here is how to balance a non-discrimination policy with wikilawyering. {{Nihiltres|talk|edits}} 16:07, 17 July 2015 (UTC)[reply]
  • Worse yet; instead of letting either of the relevant discussions on this inform the plan, or the one at WT:HARASSMENT do so, they've simply gone and created the page at WP:Sexual harassment. Check out its talk page. Here's a quote from the would-be policy's proponent: 'Sexually harassment casues more harm than other forms of harassment. It's a more serious offense. ... There's a wide body of literature that makes it clear that sexual harassment is particularly harmful and serious.' I couldn't make this stuff up.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  06:54, 21 July 2015 (UTC)[reply]
  • And still getting worse. Now it's WP:POVFORKed and WP:FORUMSHOPped to Wikipedia:Sexual harassment policy. It's time for some administrative action to put a stop to this.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  16:50, 22 July 2015 (UTC)[reply]
    I've merged these last two (into WP:Sexual harassment), and redirected WP:Sexual harassment policy to WP:Harassment, the actual policy.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  17:10, 22 July 2015 (UTC)[reply]

Moving modules

I propose the following:

  • Only administrators can move modules
  • When a module is moved, its documentation subpage is automatically moved as well
  • The "suppress redirect" option is automatically selected when moving modules; see also Wikipedia:Village pump (technical)/Archive 127#Module redirects?
  • All instances of {{#invoke:M|f}}, where M is the old name and f is a function, will have to be fixed to {{#invoke:N|f}}, where N is the new name

GeoffreyT2000 (talk) 15:01, 11 July 2015 (UTC)[reply]

  • Templateeditors should also be able to move modules, obviously, when this is feasible. Part of the development process is progressively moving code around to do increasingly complex and efficient things, and this need not be held up by WP:BUREAUCRACY. It sounds like you are making technical proposals, in the second and third bullet points, for what the software should do, but this isn't WP:VPTECH. The last point is just general cleanup we should do anyway, but it's something that would have to be done automatically and instantly during the move process, by the software, or it would not be possible to move modules without breaking all the templates and pages that use them. There's a way around this problem, highlighted at the very discussion you already cited. :-)

    Counter-proposal:

    • Only templateeditor users (which includes administrators) can move modules.
    • If the module was already used in any non-test pages, then in a text editor prepare the code return require('Module:N'), where N is the name to which the module will be moved; this will be used to create the functional, invocable equivalent of a redirect from the old to the new name. Do likewise for any Module:M/X submodules.
    • Then move the module from the old Module:M pagename to the new Module:N location. Do not use the "suppress redirect" option during the move if the module was used in non-test pages.
    • Immediately save the "Lua redirect" code from your text editor to the old Module:M location, as its sole content (i.e. replacing the #REDIRECT [[Module:N]] {{R from move}} material in it), so that the invocations of the module are not broken for more than a few seconds. Do likewise for any submoduless.
    • All instances of {{#invoke:M|...}} in templates or other pages are then to be updated to the {{#invoke:N|...}} module name, and corresponding require('Module:N') changes made to any other Lua modules that require the module that has been moved. In the interim, the redirects from Module talk:M and Module:M/doc to their new locations help people find the new location of the module.
    • The "Lua redirect" may then be deleted or sent to WP:MFD for deletion.
    • It will be proposed at WP:VPTECH that a warning about moving modules will appear automatically for Special:Move when the namespace is Module:, either pointing to where these instructions are documenting them, or including them directly.
Note that by not suppressing redirects, we preserve a history of the move at the original location, and create redirects for the talk and /doc pages. Do suppress it for code that is still in development, so we con't create redirs no one could need.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  09:22, 15 July 2015 (UTC)[reply]
  • This all seems unnecessarily bureaucratic. gerrit:146608 will fix this the right way. Jackmcbarn (talk) 17:44, 16 July 2015 (UTC)[reply]
    • Fine be me if they get it right. But I've learned not to hold my breath waiting for such changes, even obvious ones sometimes take several years to make it through the dev process. Several of the bugs I opened 6-8 years were still open last I looked a few months ago. Anyway, my version describes a way to do it, now, without causing problems, while the original does not. Anyone competent to be moving these things around already knows what I wrote up there; I just didn't want to see the not-practical version to go unchallenged. PS: Neither version is "bureaucratic". Technical specificity to avoid breakage isn't "bureaucracy"; that's not what the word means. The only bureacracy point, barely, in either proposal is the permission level (and mine's the less bureaucratic, since it permits many, many more editors to do this if they're competent, instead of only admins (i.e., a bureaucracy).

RfC: Notability and directory issues for lists

Please see here for input on notability and directory issues for lists!

Thanks! Mootros (talk) 15:08, 11 July 2015 (UTC)[reply]

Having looked at it, I think that topical RfC is quite symptomatic of a more general problem. While it needs to be settled on its own terms it is context, the central problem is the inability of many editors to distinguish between WP:Notability (whether a topic has enough reliable-source coverage to be kept as a stand-alone article) and encyclopedic relevance (whether something can be mentioned at all in an article). This problem is endemic to discussions of list content and their inclusion criteria, and it needs to be resolved site-wide. The simplest and most direct solution is for the list-related guideline to directly advise against using the word "notable" or any derivative of it in list inclusion criteria, so people stop confusing the two concepts. That's probably a discussion to have at WT:LIST, though it could also be had here (I just don't think it'll do much at the article talk page linked by the OP).  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  10:54, 16 July 2015 (UTC)[reply]
It is not a problem limited to lists. "Notable" is used on including content in articles which otherwise meet notability as well, or with sources at times. I'll comment at that discussion. Jo-Jo Eumerus (talk, contributions) 11:36, 16 July 2015 (UTC)[reply]
Fair enough. The points about using the word for list inclusion criteria apply to content in other article types.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  15:11, 22 July 2015 (UTC)[reply]

Formatted ANI Discussions

WP:ANI can be rather chaotic and highly disorganized. The more heated the dispute the longer it ends up being and the more disorganized it can be. This makes ANI manipulatable. The longer the discussion there is and the longer it goes on the more chance the issue being brought forward is ignored. Simply put people get too tired to bother with it. I propose that we adopt a policy enforced format for ANI discussions. I was thinking something along the lines of the format used by Arbcom. See WP:RFAR. In addition I think it would be beneficial if this policy encouraged (but not required) brevity where possible.-Serialjoepsycho- (talk) 10:07, 12 July 2015 (UTC)[reply]

  • Opposed: I think the idea is overkill... many (most?) ANI discussions are actually settled fairly quickly... and adopting a "mandated" format would actually make such quick settlements harder to achieve. More over, a mandated format can be gamed because "procedure was not followed". Would some ANI deliberations perhaps benefit from an "Arb-Com like" format?... sure. Would all benefit from an enforced format? No.
What I would suggest is a two stage solution... keep the current ANI discussion as step one... but if that does not resolve the issue, then go to a more formalized "Arb-com like" format. Blueboar (talk) 10:46, 12 July 2015 (UTC)[reply]
  • Oppose: WP:RfC/U was closed with the understanding that ANI would become the proper place to have the sort of discussions that were at RfC/U. Such discussion were rare at RfC/U and are rare here, but any attempt to limit ANI so that it can no longer fulfill that role needs to contain a proposal for a new place where such discussions are allowed. --Guy Macon (talk) 13:59, 12 July 2015 (UTC)[reply]
  • Comment I agree that most are handled fairly quickly. It might be that less than 20% are long and tedious. I agree that setting up a means that could be used to get a procedural close would be a poor idea. I did not consider that when proposing this. I'll move this to the ideas lab so perhaps a more workable solution could be discussed. Perhaps some sort of ANI clearinghouse, where the discussions that meet a certain criteria and would benefit from an "Arb-Com like" format could be moved to.-Serialjoepsycho- (talk) 18:41, 12 July 2015 (UTC)[reply]
  • Oppose for the same reason Guy Macon raises, as well as for WP:BUREAUCRACY reasons. We don't need another rule muzzling people for the sake of "process" and to make it more easy for editors who spend too much time in noticeboard WP:DRAMA factories to pass judgement on others. What is being proposed here is already used at WP:AE, basically, and it doesn't work well. It leads to too much "Judge Dredd" action taken without sufficient review of the facts. This can result in cases of people being restricted for things they did not really do because they're not allowed to adequately defend themselves, and occasionally to cases of no action being taken about actual bad-faith editing because you can be punished for providing sufficient evidence to make the case. I've also had admins at AE literally delete the evidence I presented because it had exceeded their arbitrary length limits, and then proceed to take serious-consequence actions based on the evidence still left in the page, as if the evidence they'd deleted themselves had never been presented. Usually, this kind of enforced discussion formatting and content limitation just gives an advantage to a complainant trying to make someone else look bad, because it takes approximately twice as much material to simultaneously defend against the accusation (party B's diffs about party B) and show why the complainant has unclean hands (party B's diffs about party A), and doing so effectively doubles the number of claims to examine. Over time, this effect increases "wiki-litigiousness": Whoever is first to make an accusation is more likely to get what they want, as long as they can carefully construct a claim that looks damning on its face, and will require a lot of diffs and explanation to disprove, since it makes both any defense and any examination of the complainant's own involvement in the matter less likely to be thorough. The last thing we need is yet another kangaroo court that trains people how to be WP:WIKILAWYERs. Finally, many semi-noobs end up at ANI for some "schooling"; a WP:RFARB-styled legalistic approach is difficult even for long-term users to figure out, so imposing it on ANI would be giving another wikilawyering advantage to those with with the most practice at generating drama on noticeboards.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  07:30, 15 July 2015 (UTC)[reply]
  • Comment: The ArbCom Request format wouldn't work because ANIs need to have threaded discussions. What needs to happen at ANI is more eyes, and more people willing to closely examine all of the points of evidence. Right now it's not so much that threads get long, it's that threads get ignored. I'm appalied that ANI sometimes seems like a ghost town or an echo chamber, with only the most belligerent of parties' threads (either the filer, or the subject) getting much involvement or investigation/traction. (Sometimes this is a result of a poorly filed ANI.) What works best at ANI is when all parties, or at least those parties participating who have an organizational bent, work to keep the organization in bounds, within consensus. I like to add subheaders (especially "Proposal: _____"), or sidebars, to focus discussions, so that ten discussions/topics aren't happening at once in the same space. Also, sometimes judicious hatting of irrelevant digressions helps a lot. I think awareness of the problem and the intention to solve it is key. Of course the resolution sometimes depends on how uninvolved and neutral the person attempting some organization can be. Of course the one thing that makes some ANIs so lengthy is the endless back-and forth of people who have had grievances against each other for years. I think if more admins got involved and reminded people to stick neutrally to the point, it would help. That brings up the point I made at the beginning: Admins seem to be conspicuous by their absence on ANI these days. Some legitimate threads don't get closed before the bot eats them, not even when there's a consensus of numerous editors. We need more admin eyes on ANI. Softlavender (talk) 09:02, 15 July 2015 (UTC)[reply]
    • I concur with all of that. If more of us spent a little time in ANI, then the workload would be lower, and the influence of people who treat it like their own personal entertainment medium would be greatly reduced. I'm not sure how much that broader participation will fix, though, given the declining admin pool in numbers, and the declining willingness of remaining admins to get involved in controversies that may generate ill-will toward them individually. I'm not sure how much longer this can go on. Our adminship system is clearly failing, in multiple ways (and many have been predicting this for 5, 8, even 10 years). All organizations have lifecycles, and if the needs of each phase of them are not adjusted to, it can cause any organization to fail. If these needs are met, an organization can continue through multiple iterations of the cycle indefinitely.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:13, 16 July 2015 (UTC)[reply]
  • Oppose: Would send it the way of the (unworkable and justifiably staked-through-the-heart RFC/U) Cas Liber (talk · contribs) 23:51, 18 July 2015 (UTC)[reply]

Preventing Wikipedia from being used by scammers and theives

Hello Community,

This is my first post at Wikipedia. Which means I have a bit of passion about this topic. Recently I was scammed via my iPhone and a Wikipedia page was referenced to help build legitimacy and aid in the scam.

The back story...

As I surfed the web on my iPhone I hit a site, that was placed by the scammers, which generated a perpetual pop up window telling me my iPhone was hacked and that I should immediately call Apple support. I did. While talking with the "technician" I was asked if he could run tests on my computer. I allowed this "technician" access and they ran "a test". Once ran, the "technician" reported that I had received the Koobface virus. At that time the "technician" took me to the Wikipedia page: https://en.wikipedia.org/wiki/Koobface At this page he reviewed the danger of the virus with me which solidified their scam in my mind. They then recommended an "Authorized Vendor" to cure the problem and shared the web page to: http://www.squaretechno.com/ again to solidify the scam.

I later got concerned I was being scammed and hung up. After doing research I confirmed that I was scammed by a real Apple Technician confirming this is not a process that Apple supports and by reading community pages warning about such scams. Example: https://discussions.apple.com/thread/7070529?q=Square%20Techno There are many more. And in many of these posts the victim reports being shown the Wikipedia page I submitted above.

My suggestion is to mark pages, like above, that are being or have the potential to be used in scams. Curious if there is a way to place an asterix or icon on such page warning the visitor that the page has been referenced as used in recent scam activities. I believe the content on the page to be true, the warning is about the information being used to build legitimacy in the scam being presented.

How cool would it be to prevent scammers leveraging this community and the information in Wikipedia to aid in their scams? How cool would it be if the "technician" saw a big warning on the above page the next time the "technician" took one of their proposed victims to such page?

Thank you for reviewing.

/ss "Kongeegen" — Preceding unsigned comment added by Kongeegen (talk • contribs) 18:33, 15 July 2015 (UTC)[reply]

They would just use another page. We are here to build an encyclopedia and I don't think anything we can do will stop some people from falling for scams. Chillum 18:38, 15 July 2015 (UTC)[reply]
Legitimate customer support services do not make unsolicited calls, emails, or pop-up ads. If people keep falling for those, it doesn't matter what Wikipedia does. None of the real problem lies with us. Ian.thomson (talk) 18:59, 15 July 2015 (UTC)[reply]
The only thing I could begin to imagine helping would be a banner across every article saying "unsolicited phone calls, emails, or pop-up ads are never legitimate sources of technical support, income, real estate, or medicine; always (call/email/visit) the official (tech support/store/company) (number/email/address) and not one that unsolicited messages give you" but that's something people should know anyway. Not saying you deserved what you got, but please post that quoted bit about unsolicited messages on Facebook so your friends know better. Ian.thomson (talk) 19:09, 15 July 2015 (UTC)[reply]
Wikipedia can, in articles on online scams, document how sources tell us they work. But WP repurposing itself as a scam alert systems isn't our "job" and wouldn't work; as Chillum says, they'll just use a different page. It would probably take then just a few minutes to adjust some scripts. There are loads of websites out there about how to avoid falling for scams of this sort. And the bad guys will invent new ones, and a new batch of people will fall for those, until they're widely know to be tricks. That's just how the world works. Always has. In this particular kind of case just realize that it's essentially physically impossible for some remote website to analyze problems on your computer and alert you about them. Don't even fall for those "Your Flash plugin is outdated! Click here to download the new version!" things. Some browsers, like Chrome/Chromium may themselves prompt you to update outdated plugins, but random websites don't, unless they're trying to screw you over.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:04, 16 July 2015 (UTC)[reply]
Kongeegen, it sounds like you might be interested in reading about Technical support scams. I'm glad that you didn't fall for it in the end. WhatamIdoing (talk) 18:53, 16 July 2015 (UTC)[reply]

Updating nonfree content policy to reflect the existence of the draft namespace

The primary nonfree content policy and guideline (WP:NFC, WP:NFCC have not been updated to reflect the creation of the draft namespace. Moreover, despite express policy language limiting nonfree images to articlespace, practice tolerates use of nonfree images in userspace and sandbox drafts. I believe we should modify the nonfree content policy, consistent with the WMF Licensing Resolution, to

1. Authorize the display of nonfree content in the draft namespace

2. Create standards to limit the time drafts may display nonfree content, and encourage editors to save drafts with linked images -- eg, [[:Filename.ext]] -- rather than displayed images

3. Sunset the toleration of nonfree images in userspace and sandbox drafts (my suggestion is December 31, 2015), and establishing a standard practice for addressing violations (eg, moving page to draftspace, suppressing display of images, etc)

I don't believe this is terribly controversial or difficult, and hope the essential text can be quickly developed and sent to RFC, assuming the concept is accepted in principle. The Big Bad Wolfowitz (aka Hullaballoo) (talk) 00:51, 16 July 2015 (UTC)[reply]

  • Makes sense to me. I like the idea of moving moribund userspace drafts to draftspace (with human intervention, not automatically - if a user subpage isn't actually an article draft and is using non-free images, they should just be disabled). But anyway, the basic principle that the spirit of "allow non-free in articles" implicitly means "allow non-free when drafting those articles", is sensible.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  11:07, 16 July 2015 (UTC)[reply]
  • I could favor this, with some cautions and reservations. "encourage editors to save drafts with linked images" does not work unless WP:NFCC #7 "One-article minimum" is interpreted to include linked items from drafts as "use", and this is made explicit. I don't see the need for "Create standards to limit the time drafts may display nonfree content" but if that need is felt, then make the limit at least the 6 months allowed before an unedited draft is considered stale -- I would prefer a year. DES (talk) 16:08, 16 July 2015 (UTC)[reply]
  • I agree with the first two suggestions, but think that allowed use in drafts should include userspace/sandbox drafts. I believe that works in progress are protected by fair use law and that amending our non-free content guidelines to allow use in the draftspace is fine. I would prefer a one-year limit (and no less than six months) to the time the fair use image is allowed outside the article namespace and that there should be a guideline that specifies the draft must be a potential article that is being worked on...not an article that appears to be created just to host non-free images or is not something that the author intends to turn into an article or section of an article. There should be a bot to alert the persons working on the draft a reasonable length of time before the images are deleted (since some users are not very active on WP at times). I think a template on the article in the draftspace (at top, something like "This draft article contains non-free images which will be deleted in X days unless...") or message on the user's talk page (article is in username/sandbox) as well as, of course, a deletion template on the file page. I think one month is a preferable length of time to add these, as it allows users which aren't very active a descent length of time to finish the drafts. AHeneen (talk) 22:22, 16 July 2015 (UTC)[reply]

Sexual harassment policy

I've created a proposal here: Wikipedia:Sexual_harassment

Should there be a sexual harassment policy on wikipedia? What form should this policy take? Please feel free to completely rewrite the proposed policy if needed. --ScWizard (talk) 23:15, 16 July 2015 (UTC)[reply]

You may not have noticed it, given your extremely sporadic contribution history, but please note the section above re: non-discrimination policy. I do realise that some might argue the two are not the same but there is also a RfC knocking about somewhere, which is referred to in that thread by someone else. - Sitush (talk) 23:34, 16 July 2015 (UTC)[reply]
They're related but separate I'd say. --ScWizard (talk) 23:37, 16 July 2015 (UTC)[reply]
We already have WP:NPA and WP:CIVIL... we don't allow harassment of any kind. So I am not sure a specific Sexual harassment policy is needed. Blueboar (talk) 03:02, 17 July 2015 (UTC)[reply]
The trouble is that WP:NPA and WP:CIVIL are frequently ignored and treated with contempt, even by those like admins who are charged with enforcing them. How would any new policy be treated any different?Nigel Ish (talk) 07:36, 17 July 2015 (UTC)[reply]
Just no. You're conflating two things that should be separate. Editor interactions are what are within the boundaries of community policy and norms. The actions you outlined are Office Actions and law Enforcement. It's absolutely silly to require reporting to WMF when it's clearly something that can be report to law enforcement. I wouldn't jeopardize a prosecution if my clear choice was a LE report. It's sort of like a requirement to inform the diocese about child molesting by priests. It might happen but they are not required to. Certainly the WMF isn't going to let the community set Office Action policy either nor will they allow editors to advertise legal action they have taken against other members per WP:NLT. This is misguided and it's the WMF Office Action that needs review. --DHeyward (talk) 08:19, 17 July 2015 (UTC)[reply]

RfC on whether calling an event "murder" presumes the perpetrator is a "murderer".

See Wikipedia talk:WikiProject Crime and Criminal Biography#Request for Comment: Does "murder" presume "murderer"? Or don't. InedibleHulk (talk) 16:19, July 17, 2015 (UTC)

Why only one FA nomination at a time?

The Featured Article nomination rules say: "An editor is allowed to be the sole nominator of only one article at a time; however, two nominations may be allowed if the editor is a co-nominator on at least one of them.". Could someone please explain why this rule was instituted? What's the problem with allowing editors to nominate multiple articles at any given time? Thanks. Leptictidium (mt) 21:19, 17 July 2015 (UTC)[reply]

It was decided here, along with the mandatory two week break after failed nominations to deter people playing shoot-till-you-win, and you're very unlikely to get consensus to change either. The problem was certain editors had a tendency to play "throw all the darts and see what sticks", in the hope that one would slip through; this made FAC unmanageably large. If you have a good reason to nominate more than one at once, the delegates will usually allow it if you ask. – iridescent 23:10, 17 July 2015 (UTC)[reply]
No, they never do. Hawkeye7 (talk) 11:06, 18 July 2015 (UTC)[reply]
"Never" is pushing it a bit, given that I had two running simultaneously last month and the world did not come to an end. As of 11 June, the delegates' stated position was "It's not uncommon for us to permit a second solo nom when the first is obviously fairly close to promotion". – iridescent 23:20, 18 July 2015 (UTC)[reply]
The other exception is joint nominations, which I think is a good thing - i.e. if this encourages editors to work together on broader, larger articles with the payoff that they might have two running at once. Hence I have a joint nom and solo nom up at the moment. Good to see you again Leptictidium (feel free to translate any mushroom articles to/from Catalan :)). Cas Liber (talk · contribs) 23:49, 18 July 2015 (UTC)[reply]

Awards and nominations-type tables for athletes

Those infoboxes can get very crowded with all the various awards etc. that sportspeople have accumulated over their long careers. It got me thinknig of how we could use the "awards and nominations" model to create similar article lists for atheletes which concisely show everything they have accomplished in their field.

Thoughts?--Coin945 (talk) 18:36, 20 July 2015 (UTC)[reply]

Yeah, just copy that format wholesale. Heh. Seriously, was there something about the one format that doesn't translate well to the other?  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  00:45, 21 July 2015 (UTC)[reply]
Well sportpeople dont really win awards do they? Medals yes. Titles yes. But awards and nominations? I'm not sure. And how would it work for sportspeople who have had a career in other media like film/TV? It would confuse the heck out of me working out how to arrange it all.--Coin945 (talk) 18:21, 21 July 2015 (UTC)[reply]
Track and field already has {{AchievementTable}} for this purpose (see e.g. Paula Radcliffe#Achievements or James Kwalia#Achievements); but I'm not sure how easily that table could be adopted by other sports. Sideways713 (talk) 14:50, 22 July 2015 (UTC)[reply]
Eh, we do not need a VP discussion to come to the conclusion "Yes, table fields and parameter names need to be changed to make sense." Seriously. I thought you were asking if the overall layout of the table needed adjusting.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  15:08, 22 July 2015 (UTC)[reply]

Requesting closing statements for archived discussions

I just cleaned out a bit of WP:ANRFC. If you haven't been over there in a while, it had about 75 "requests for closure", and about 65 of them were posted by the same editor. I removed eight "requests" from him that were made for already-archived discussions. (More of them have probably been archived since he requested closure, but these eight were already archived at the time he posted his request.) I guess he wants someone to go back into the archives and add a closing statement, which is pointless:

  • Almost nobody watches the archives, so nobody will read the closing statement even if one is added.
  • Generally speaking, editing an archive is a Bad Idea, and editing it to make it look like some closing statement was relevant and accepted at the time is a doubly bad idea. Nobody reading the archives later is likely to check the history to see when that closing statement was added. If the close is wrong or materially deficient, then nobody has had a fair opportunity to object to it.
  • If the participants in the discussion stopped talking about it long enough for it to get archived uncontested, then it's a safe bet that they don't need some WP:NAC to come round and write down what the NAC believes the consensus is.

Here is my proposal: Let's amend both WP:RFC and WP:TPG to say that closing statements should neither be requested for, nor added to, discussions that have been archived.

(I'll post notes at RFC and TPG about this in a bit.) What do you think? WhatamIdoing (talk) 15:57, 21 July 2015 (UTC)[reply]

? Some RfC's are (automatically) archived, some even before an RfC (template) has run its normal time. What I've seen closers do, is bring the RfC section back to the talk page, and close it. What's the problem with that? --Francis Schonken (talk) 16:05, 21 July 2015 (UTC)[reply]
  1. Some NACs are directly editing the archive pages instead of bringing it back to the talk page, where editors might see the closing statement.
  2. What's the point of adding a closing statement on 20 July, to a discussion that ended on 24 June (because even proponents figured out by then that there was no consensus for their proposal) and was archived without complaint or apparent regret on 2 July? If none of the 20+ people involved in that discussion felt the need to continue that discussion during those 18 days that it was in the archives, or to keep talking about it at all after 24 June, and none of the 20+ participants felt the need to request a closing statement, then why should we encourage (or even permit) someone to edit the archives to add a pointless and potentially misleading closing statement? WhatamIdoing (talk) 18:01, 21 July 2015 (UTC)[reply]
Re. #1 I totally agree, that's not the way to do this (although for "no consensus" formal closures there's maybe not too much reason to bring it back to the active page either). But I totally disagree with your solution: the recommendation should be to do it like it should be done, not to avoid closers doing their closing properly. Also, I'd rather have a non-admin closer helping out with the backlog (and making some errors in the process), than the backlog growing and in the end a clever guy saying, well let's cut the backlog by impeding the inflow...
Re. #2 Here also, the encouragement would be to keep the backlog at WP:ANRFC down, not to avoid people asking for closure. I've recently added a WP:ANRFC request for an RfC that was archived months ago, and I got the thoughtful attention of a closer. So where's the problem? --Francis Schonken (talk) 18:16, 21 July 2015 (UTC)[reply]
I disagree with the original comment that closing statements should neither be requested nor added to discussions that have been archived. Sometimes the discussion has been archived because the archival bot parameters are too quick to archive, and there was consensus in the first two weeks of the 30-day discussion period, and then contributions stopped, or sometimes the discussion has been archived because the RFC bot pulled the tag after 30 days, so that contributions stopped, and then the RFC waited for a closer for a long time. Formal closure is still a good idea in those cases, because there might have been a consensus to do something. I agree that, if there is a consensus to do something, the RFC should be moved back from the archive talk page to the active talk page. A rule that archived RFCs should not be closed, however, is the wrong answer. Closing the RFC, even if it was archived, is a better answer. Robert McClenon (talk) 18:30, 21 July 2015 (UTC)[reply]
I agree with Francis Schonken and Robert McClenon that close requests for archived discussions should be permitted per my comments here. I also agree with their comments that "no consensus" closes of archived discussions probably don't need to be moved back to the main talk page. Specifically, these are good rules of thumb:
  1. Robert McClenon's comment "I agree that, if there is a consensus to do something, the RFC should be moved back from the archive talk page to the active talk page."
  2. Francisc Schonken's comment "although for 'no consensus' formal closures there's maybe not too much reason to bring it back to the active page either".
Cunard (talk) 05:57, 22 July 2015 (UTC)[reply]
For those who didn't click the links, Robert McClenon, of course, is the editor who just added closing statements to the archives, and Cunard is the editor who lists about 90% of all expired RFCs at ANRFC, including all eight of the archived ones. It is not exactly surprising that they believe they are being useful by requesting and closing long-dead discussions; if they thought that it was inappropriate or a waste of time, then they wouldn't be doing it in the first place. WhatamIdoing (talk) 22:17, 22 July 2015 (UTC)[reply]

I agree with User:WhatamIdoing that such discussions shouldn't be "closed" by merely editing a talkpage archive subpage. If such a discussion still needs closure, restore it to the talk page, and close it there - thus giving it a new timestamp for the bots, as well as an edit for watchlists. - jc37 11:37, 22 July 2015 (UTC)[reply]

Default: Just unarchive and close; the archiver bot will re-archive it later. It's perfectly legitimate to unarchive a discussion that hasn't concluded; we are not servants of bots, they serve us. If someone manually archived it without comment, do the same. If someone manually archived it with an edit summary that the discussion is closed, moot, stale, etc., edit the archive and close the archive with their summary and attribution and a note that you refactored, since it was just a sloppy attempt to close it originally (if their close was questionable, that's not your problem; anyone who cares to challenge it has a process for doing so). It is not true that no one reads archives; we refer to them all the time, so properly closing an archived discussion that shouldn't be unarchived but which wasn't closed with the right tagging and summary serves the interests of the community.

It also isn't true that there's no point to adding a closing statement to a month old (or whatever) discussion. Many participants in discussions are not semi-pro arguers, but say their piece and move on, and are not going to be aware that a discussion did not close and got archived while still open. It's very frustrating to come back to an issue you participated in trying to resolve, only to find that no one bothered to close it simply out of backlog or apathy or oversight (in the "missed it" sense). There are no legitimate grounds on which to argue that it "can't" be unarchived or closed or both, per WP:COMMONSENSE and WP:NOT#BUREAUCRACY and WP:IAR and WP:BOLD and WP:LAWYER and the spirit of WP:CONSENSUS. I've been unarchiving non-ancient archived discussions that needed resolution for over 8 years, and only one person has ever reverted me; they even accepted my explanation when I clarified. I'm OK with the idea that if the close is going to be "no consensus" (or equivalent, e.g. "not moved" at WP:RM) then unarchival is not necessary to close; but I prefer it be unarchived because it hits people's watchlists. And I also disagree with the idea that closing statements should not be requested for discussions that have been archived. They should probably be requested more often, because a) it will result in less rehash, strife, and editor burn-out by obviating repeat discussions, and 2) the very fact that it got archived means commentary had stopped, means it was ripe for closure.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  15:00, 22 July 2015 (UTC)[reply]

I agree that it's perfectly legitimate to unarchive a recent discussion if you have an interest in continuing it. (For old discussions, WP:TPG recommends starting a new one instead of reviving months- or years-old ones. TPG's recommendation is consistent with the policy that WP:Consensus can change.)
But the question here is not whether you want to continue an occasional discussion; a quick trip through your contributions shows that you've done this once in the last three years, when a bot archived the discussion while you were typing. That's perfectly reasonable and desirable, but not what I'm talking about.
The question is more like this:
Given that the person making the request for closure has no interest whatsoever in continuing the discussion or what the outcome is, and is merely making the request out of habit;
given that the person writing the closing statement has no interest whatsoever in continuing the discussion, and probably also has neither any interest in or knowledge about the subject;
given that the discussion is already archived, and that nobody interested in the discussion has tried to prevent or reverse this archiving;
given that, as a general rule of thumb, most of our editors with any experience can figure out the result of most discussions (i.e., more than 50% of discussions) without outside assistance, especially from a non-admin who probably has neither knowledge or interest in the subject matter;
given that nobody interested in the specific discussion has expressed any confusion about the result of the discussion or requested any assistance with understanding the outcome;
given that there is no clear reason to un-archive the discussion merely to add a closing statement (neither any IAR-style reason nor any justification that would pass muster under the TPG guideline); and
given that nobody is likely to notice someone adding a closing statement to the archives –
given all this, is there any actual, practical, non-bureaucratic value in either requesting or adding that closing statement? Mightn't it be just a little less bureaucratic to wait until there is evidence that someone actually wants or needs the help of a closing statement for the discussion in question?
Or maybe this will be a more useful question: if the closing statement is so unimportant, or the result so obvious, that it's not worth un-archiving the discussion so that other people will read what you're adding, should you add the closing statement at all? WhatamIdoing (talk) 22:17, 22 July 2015 (UTC)[reply]

@Cunard: of course not every RfC "needs" formal closure. Is there a selection on which RfC's you think most in need of formal closure? Alternatively, did you ever think suggesting it as a bot job to get RfC's listed at ANRFC once the RfC tag is removed (usually by bot)? E.g. the time spent listing them manually might be used also to close a few you're not involved in (or do you only list the ones you can't close)? Indiscriminate listing of expired RfC's may of course have a negative effect that those most in need of attention (often also the ones most difficult to close with walls of text and uncountable ramifications) get snowed in by those where participants came to live with the "apparent" outcome and moved on? Sorry for the many questions, but backlog is a problem (as correctly indicated by WhatamIdoing), and I see this discussion here as an opportunity to develop a strategy on how to deal with that. --Francis Schonken (talk) 09:12, 23 July 2015 (UTC)[reply]

WP:RFC says that most (i.e., >50%) of discussions don't require closing statements; WP:ANRFC says that "many" shouldn't be listed there (and, if memory serves, used to say "most"). I and other editors have suggested that closing statements for most RFCs (e.g., these) are unnecessary. They did not need to be listed, they did not need to be closed, and the closing statements provide no value to anyone who might read them. They are wastes of time – which would be fine, if some volunteer really wanted to waste his time (or open himself to derogatory speculation about planning for an unsuccessful RFA run by doing a bunch of pointless makework). But they are also damaging to the WP:Be bold and WP:Consensus can change ethos: when we provide closing statements for discussions with perfectly obvious results, we are telling new people that WP:NOTBURO is unimportant words on paper, and we are telling experienced editors that we are concerned that they are either too stupid or too tendentious to figure out what the consensus is. And, as you say, filling up ANRFC with unimportant requests for closure prevents people from finding the ones that would actually benefit from it. Indiscriminate (by bot) or nearly indiscriminate (what we have now) listing kills the signal:noise ratio for that page. I suspect that it also has the effect of making some admins feel discouraged, because it's yet another "backlog", albeit an artificial one, that makes their efforts seem futile.
I believe that these proposals have been considered in the past:
  • not listing requests that you personally don't care about;
  • asking participants whether they to list it;
  • asking participants whether they would object to listing it; and now
  • not requesting a close for already archived discussions or adding closing statements to the archives.
WhatamIdoing (talk) 15:59, 23 July 2015 (UTC)[reply]
I'd like to hear Cunard's rationale why they picked the ones they picked for listing at ANRFC, and whether we can come to some agreement here.
I'm a directly interested party here, because I've got one listed that won't go away (even when archived...) unless closed formally. When I see all the others listed (I had a glance this morning whether there were some others I could help close but can't find one that would accept NAC closure and for which I'm not completely unfamiliar with the topic area) seems like kinda desperate. I think an understanding is best so that this doesn't go WP:COSMETICBOT or whatever way we don't want this to go. --Francis Schonken (talk) 16:28, 23 July 2015 (UTC)[reply]
FWIW, I agree that Cunard is fishing too many of these RfC's out of the waste bin and spamming WP:ANRFC with them. I will also make a mental note about unarchiving any RfC's that still need closures and closure statements but have been archived. That said, I disagree with the idea that all RfC's that have been archived shouldn't be closed at that point, or that all of the RfC's that Cunard has been spamming to WP:ANRFC don't belong there. I think, in conclusion, I'd like to ask Cunard to be more careful in choosing which RfC's to post up to WP:ANRFC, and not to dump 80 RfC's (many of which aren't even "formal" RfC's and/or which don't need "formal closes") there all at once. --IJBall (contribs • talk) 20:37, 23 July 2015 (UTC)[reply]

Perhaps it might be a good idea to write some guidance describing cases when a request for closure is or isn't appropriate? I'm only aware of WP:CLOSE#Which_discussions_need_to_be_closed, which is quite vague. I'd also like to put in an argument for not de-archiving discussions, especially if the issue is contentious - a few days between the closure and post-closure discussion can make the procedure seem more measured and reduce the feeling of immediacy from editors who feel strongly about the issue. My feeling is to say that there's WP:NODEADLINE, and if nobody ever checks, then the RfC question is probably no longer an important issue. Sunrise (talk) 00:06, 24 July 2015 (UTC)[reply]

  • WhatamIdoing has raised this issue repeatedly. Two previous discussions are Wikipedia talk:Administrators' noticeboard/Requests for closure/Archive 1#Cunard is still adding dozens of requests (July 2014) and Wikipedia:Administrators' noticeboard/Archive268#Severe backlog at WP:ANRFC (January 2015). In both discussions, I explained my closure requests in detail.

    I think Scott summarized it very well at Wikipedia talk:Administrators' noticeboard/Requests for closure/Archive 1#Too many discussions being added:

    Lack of resolution to ongoing debates is a continuing issue on this project. If there are too many things listed here, it's because there are too many things left unfinished. It's a reflection of reality. As Cunard points out in his admirable response in the "September 2013" link above, not having a formal closure can also lead to misinterpretations (or deliberate ignorance) of consensus by persons in disputes, and not provide a recourse for editors attempting to enforce consensus. Having an accepted closure to point to will be immensely useful in many subsequent debates. We should encourage these. Making them is tough work, and I think that's what's putting editors off doing it, not seeing the number that need to be done.

    Robert McClenon, one of RfC's dedicated and hard-working closers, explained why formal closure of even seemingly "consensus is clear discussions" is helpful at Wikipedia:Administrators' noticeboard/Archive268#Benefits of Formal Closure:

    I have closed several RFCs where I thought that consensus was clear, but that required follow-up for either of two reasons. Either one of the posters ignored the consensus, in spite of the formal closure stating the consensus, or one of the posters objected to the close and requested that I re-open the RFC to allow them to insert a statement. When there was move-warring against consensus or edit-warring against consensus, formal closure put the enforcing administrator on firmer ground in enforcing consensus. Formal closure establishes what the consensus is, unless reviewed. Otherwise the resulting WP:ANI thread would itself have had to establish consensus before warning or blocking, causing drama on a drama board. In cases where I have been asked to re-open a closure, I have instead asked for closure review. Without closure and closure review, the most likely result would have been edit-warring.

    The recent backlog is because I did not update the closure requests list for around four weeks. (In the past, I updated it every two or three weeks.) In the past when a large number of requests has been added, the backlog has returned to a reasonable number within two weeks. Cunard (talk) 03:51, 24 July 2015 (UTC)[reply]

RfC: On Software Notability.

There is currently a RfC on the topic of software notability at Wikipedia talk:Notability (software)#RfC: On Software Notability.. Interested editors are requested to comment. :) ηoian ‡orever ηew ‡rontiers 09:16, 22 July 2015 (UTC)[reply]

New essay on petty demands

I decline to single out who inspired this lately, but I'd been thinking of writing this for years: WP:You can search, too.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  14:46, 22 July 2015 (UTC)[reply]

Good essay. Thanks!- MrX 14:48, 22 July 2015 (UTC)[reply]

Wikipedia's "Manual of Style/Text formatting" should allow boldfacing of "row headings"

Row headings are the first words at the start of items in a list format, usually ending in a period; for instance the names of people who are the subject of the paragraph. Boldfacing of row headings is common in publishing. It's user friendly for the same reason that the boldfacing of standalone headings is helpful. It helps the reader grasp the outline of the material, and helps the re-reader navigate it more easily; it provides readers with visual "handholds" in a blank wall of normal text.

Wikipedia's "Manual of Style/Text formatting" neither recommends nor proscribes boldfacing for row headings. It seems unaware of their common use. It ought to be revised to allow them in a list format (after an *). RogerKni (talk) 15:33, 22 July 2015 (UTC) PS: I recently lost over a dozen row-heading boldfaces to a Wikipedia monitor who is following the guidelines in the "Manual of Style/Text formatting," hence my proposed change to that manual. RogerKni (talk) 15:57, 22 July 2015 (UTC)[reply]

@RogerKni: Just propose it at WT:MOS; this isn't really a WP-wide policy matter, just a "tweak MOS to match actual practice" matter. But actual practice is narrower than you suggest. This style is used in particular to boldface list items like * '''Tiger salamander''' (''Ambystoma tigrinum''), North America, [other details], where the words to be boldfaced do have the character of an inline heading. Not for things like * At 2014 board meeting, elected new Executive Director Cris Allston, and passed resolution to .... So, you'd need to draft a specific, well-thought-out wording to add to the guideline. See also MOS:GLOSSARIES. When you want this effect, and would like the entries one one line and their descriptive text on the next, template-formatted glossary list structure will do all of that for you automatically. PS: It's already common practice to boldface entries of sort illustrated in the salamander example, and all of WP knows that, so there isn't really a necessity to add it to MOS. If it's added (I think it should be), a short version should appear in MOS proper, if at all, a short version at MOS:BOLD, and the detailed version at MOS:LIST since this only applies to list content.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  16:33, 22 July 2015 (UTC)[reply]

@SMcCandlish: :@Melonkelon: :@Herostratus:Thanks for your help, SMcCandlish, with suggesting where to submit this. I propose to submit the following text (down to the long dashed line):

Wikipedia’s “Manual of Style/Text formatting” currently does not explicitly permit the boldfacing of inline headings. Under Boldface, at https://en.wikipedia.org/wiki/Wikipedia:Manual_of_Style/Text_formatting#boldface, under == Boldface ==, then under === Other uses ===, the advice reads (all is quoted material until the dashed line):

Use boldface in the remainder of the article only in a few special cases:

  • To identify terms in the first couple of paragraphs of an article, or at the beginning of a section of an article, which are the targets of redirects to the article or section (e.g. sub-topics of the article's topic, rather than the synonyms as already boldfaced per the above). (See Wikipedia:Redirect § What needs to be done on pages that are targets of redirects? for examples and further details.)
  • Mathematical objects traditionally written in boldface such as vectors and the rational number symbols Q and Z.
  • In some citation formats, for the volume number of a journal or other multi-volume works.

As a result, a STiki Barnstar of Bronz Merit-winner who has been keeping tabs on my edits in a particular article (“Patterson-Gimlin film”) has deleted the boldfacing of over a dozen inline headings, including some that pre-existed my editing. When I protested, he cited the aforesaid Manual via “MOS:BOLD”.

However, lower down on the same page in the Manual, the boldfacing of inline headings is employed; I quote:

Italic type (text like this) should be used for the following types of names and titles, or abbreviations thereof:

  • Major works of art and artifice, such as albums, books, video games, films, musicals, operas, symphonies, paintings, sculptures, newspapers, journals, magazines, epic poems, plays, television programs, radio shows. Medium of publication or presentation is not a factor; a video feature only released on video tape, disc or the Internet is considered a "film" for these purposes, and so on. (See WP:Manual of Style/Titles § Italics for details.)
  • Court case names: FCC v. Pacifica. (Case citation or law report information is presented in normal font)

In addition to the fact of exiting common use, documented above, boldfacing of row headings is common in publishing. It's user-friendly for the same reason that the boldfacing of standalone headings is helpful. It helps the reader grasp the outline of the material, and helps the re-reader navigate it more easily; it provides readers with visual "handholds" in a blank wall of normal text. (These advantages can be seen in a second instance of the Manual's use of a boldfaced inline heading style, at the end of its References section.)

The deleter of my boldfacings is acting in good faith, and he has a good case as the Manual is currently worded. And furthermore, even if he were to agree to undo his deletions, which I think he may have hinted at in his latest comment, another person could come along and justifiably delete them again, based on the Manual’s wording. So that wording should be expanded. Here’s what I suggest as a new second item in the Manual’s list above. Improvements welcome:

“* As an inline heading, also known as a row heading, in a list format (preceded by an *), which should come at the beginning of the text and have the concise characteristics of higher-level, own-line headings, rather than of discursive text.”


Is the use of <code> . . . </code> necessary? I hope not.

BTW, you wrote, “PS: It's already common practice to boldface entries of sort illustrated in the salamander example, and all of WP knows that, so there isn't really a necessity to add it to MOS.”

But it’s not true that “all of WP knows that,” because, as I had written above: “I recently lost over a dozen row-heading boldfaces to a Wikipedia monitor (the otherwise-excellent Melonkelon) who is following the guidelines in the "Manual of Style/Text formatting," hence my proposed change to that manual.” So there is a necessity to revise the manual. RogerKni (talk) 09:21, 23 July 2015 (UTC)[reply]

Centralization of sexual harassment policy proposals

 – Pointer to relevant discussion elsewhere.

This discussion has been centralized at Wikipedia talk:Harassment#Sexual harassment policy, and listed at WP:CENT The two competing drafts have been merged into Wikipedia:Sexual harassment.  — SMcCandlish ¢ ≽ʌⱷ҅ʌ≼  17:58, 22 July 2015 (UTC)[reply]

A-Class article assessment

Hello, so I am unsure where best to propose this. For quite some time we have been using WP:1.0 classification scale. Overall, this has been successful however one item has been under used. That would be A-Class article assessment.

For those who do not know, A class articles rank between Good articles (GA) and Featured articles (FA) of which both has a well defined process namely GAC) and (FAC) whereas A class has none. This leads to a considerable amount of confusion among its use and quite often A-class is entirely skipped where articles are promoted to featured from good article or lower. Furthermore there does not even appear to be an A-class title template.

Please take a look at D21 road (Croatia)'s talk page as an example. It is the ONLY A-class article in Category:A-Class Highways articles, and was promoted to A-class by a user for no discernible reason as such as the case with possibly all A-class tagging. Also mind that the promotion was only applied for Wikipedia:WikiProject Highways while as far as WikiProject Croatia is concerned it is still just a GA. This is by no means an original story. I understand two Wikiprojects, namely WikiProject Military History and WikiProject Tropical cyclones has a more structured use for this, but every other wikiproject seemingly does not.

My question to the community is should we abolish A-class article assessment and stick to whats left (Stub, Start, C-class, B-class, GA, FA) which seems to be doing just fine as we are for-going A-class entirely. The reason I ask this of the community is because we are working on a system to triage assessment using Artificial Intelligence. Under use of A-class makes it very difficult to model even for Artificial Intelligence which is very good at identifying stub, start, good article and featured at the moment due to their structured nature.

As a second phase for this we ought to establish more structure for C class and B class as the algorithm is able to predicts one or the other but human assessment does not seem to have a standard. We need to define what it means to be a C class or B class.

-- A Certain White Cat chi? 18:08, 22 July 2015 (UTC)

There are three projects that have active A-class assessment programs, and they've all been active a long time: see WP:HWY/ACR, WP:MHR, and WT:TROP. Theoretically, A-class could be used in many ways, but each of those three projects makes close connections between A-class and the WP:FAC process. In what way would it be useful to abolish these three review processes? Btw, 3 wikiprojects (last time I checked) have a B+ review, intended (AFAIK) to prep articles for WP:GAN. - Dank (push to talk) 19:32, 22 July 2015 (UTC)[reply]
There are two considerations we ought to make. Firstly do we want a site-wide standard of our assessment metric? We have means to enforce this with AI induced system that recommends humans to re-assess. Secondly A class assessment undermines community consensus in the sense that both GA and FA have site-wide accepted criteria where as A class does not. My question is does the A class assessment bring anything useful? A class articles are more or less featured candidates, just like good articles. I would certainly find B+ more useful than A class or even B class being a process like Good article and Featured article. What makes an article B class and not C is quite unclear to me at the moment. -- A Certain White Cat chi? 19:59, 22 July 2015 (UTC)
A point of fact - the D21 road article underwent an A-class review here. Parsecboy (talk) 19:53, 22 July 2015 (UTC)[reply]
Thank you for the link, it was unclear to me just by looking at the talk page. I will however ask what does A class bring that GA or FAC doesn't? I am not trying to be dense, I just do not see it. -- A Certain White Cat chi? 20:01, 22 July 2015 (UTC)
A-Class is, generally speaking, a more rigorous review than GA (since it involves multiple reviewers rather than a single one, and is usually done within communities of subject-matter editors rather than arbitrary reviewers). The difference between A-Class and FA is more subtle, but primarily has to do with a focus on content versus presentation; FA tends, on the whole, to pay more attention to matters of stylistic compliance. Kirill [talk] 20:25, 22 July 2015 (UTC)[reply]
But A class ranks above GA. So it is overruling community standard in essence. I would support a better quality standard for GA if you feel it is inadequate. As for Wikiproject Military, perhaps they can perform a "seal of approval" in place of A class which would be an independent classification outside of the "standard" assessment scale. An article can be GA and this special assessment by Wikiproject Military. -- A Certain White Cat chi? 21:58, 22 July 2015 (UTC)
I think we're going round in circles -- the "special assessment by Wikiproject Military" is A-Class Review. As to your previous point, it would be overruling GA if when an article reached A-Class in one project it automatically applied to all projects but it doesn't (although some projects do accept A-Class assessments from other projects, e.g. WP:Ships and WP:Aviation both accept WP:Military History A-Class assessments). Cheers, Ian Rose (talk) 02:36, 23 July 2015 (UTC)[reply]
This is pretty much a perennial proposal. Personally, I would support abolishing it as redundant to GA, but I do know MILHIST uses it as another stepping stone toward FA. So mostly, I just ignore it. Resolute 19:38, 22 July 2015 (UTC)[reply]
As Dank points out above, the current A-Class processes are inherently project-specific reviews, and are no different from any of the other project-specific classes used in individual projects' implementation of the assessment system. I don't have a particularly strong opinion on whether A-Class should be considered one of the "standard" classes, or whether it should be something adopted by individual projects on an opt-in basis, but certainly I can see no reason why we would want to dismantle assessment processes that have been producing valuable results for years merely because other projects haven't implemented something similar. Kirill [talk] 19:55, 22 July 2015 (UTC)[reply]
See, that does not make it less problematic. In the case of Cold War a single wikiproject decided on behalf of other wikiprojects that this article was to be promoted from good article to a class. I do not believe each had a process to follow or perhaps such separate processes would conflict each other. I am merely proposing we migrate away from it just so we can aim for a Wikipedia wide article quality assessment. I never claimed a-class assessment to be useless.
We can have multi-assessment if you like where the article would officially be a "good article" and wikiproject would have whatever it's own assessment metric it desires. It is just as easy for the AI algorithm to treat A-class as if it were Good Article for its purposes (or outright ignore its existence). However such confusing labeling would be confusing and hence generally unhelpful to the reader. Our readers are familiar with good article and featured article assessments but they do not know what A class even means. Is that better than featured since assessments start with C then B then... Does it go to A?
-- A Certain White Cat chi? 20:07, 22 July 2015 (UTC)
The "multi-assessment" scheme you propose is essentially how things work at the moment. There's no requirement that all projects assign the same assessment level to a particular article; there's nothing preventing one project from rating an article as A-Class and another rating it as GA-Class, for example. (Note that, in practice, smaller and less active projects tend to accept the ratings assigned by larger and more active projects at face value, but this is a matter of consensus and agreement between individual projects, rather than actually policy.)
As a more general point, I'm unconvinced that our readers are particularly savvy in terms of even FA and GA ratings, much less any other elements of the assessment scheme. Further, while I'm broadly sympathetic to the idea that some sort of technology-assisted re-assessment can help improve the overall article assessment system, I would not support dismantling existing, functional assessment mechanisms in favor of a future system that remains entirely hypothetical at this point. Kirill [talk] 20:22, 22 July 2015 (UTC)[reply]
  • Both GA and FA creates a small icon on the top right corner of the article where as A-class does not (we just keep GA icon until FA). So it isn't a matter of savyness, it is a matter of familiarity.
  • The "future system" you mentioned already is in function (m:Objective Revision Evaluation Service), mind that it is in development so it is not a finished product but even our preliminary BETA results are exciting. What we do is we take some of the existing quality assessments by humans to train machine learning classifiers and attempt to see if we can predict the actual class. Mind that often the human tagging is outdated so you have a start class that wasn't re-assessed in a while.
  • So for current version of the Cold War article ores returns GA (%33) and FA (%49), we indeed have a level of uncertainty. Possibly it is time to seriously talk about a FAC for that article though it isn't that close yet. Fact is it is somewhere between GA and FA, leaning towards FA. We exist to serve the communities needs. As for the D21 road (Croatia) ores returns GA (%55) or FA (27%), so perhaps this article has a long way to go before it becomes featured. We offer a method to triage attention to articles pointing the ones closer to promotion for human review. What is astounding to me is that the system to determine GA and FA article quality is so consistent that we get pretty good predictions. Props to the entire community for making that an awesome process.
  • If community demands predictions for A-class we will certainly honor that and we will NEVER force any Wikiproject to use our system. We only serve at the pleasure of the wikiproject requesting our service. We also do NOT want to create more work for Wikiprojects. Our predictions for A class has been more incorrect than correct since A class articles look too much like either good articles or featured articles and overall lack site-wide consistency in quality but also because we lack enough samples to train the system. Hence our accuracy cannot increase much for A class.
-- A Certain White Cat chi? 21:51, 22 July 2015 (UTC)
I don't see the fact that the predictions aren't consistent as a problem, actually; as has been mentioned, there are only a few projects that heavily use A-Class, and all of those rely on fundamentally non-automated review processes to assign that rating. In fact, I would go so far as to suggest that your tool should simply ignore A-Class entirely, and predict based just on GA and FA ratings. Those of us who work with A-Class can always examine articles that land between those if we're looking for potential A-Class candidates. Kirill [talk] 00:43, 23 July 2015 (UTC)[reply]
We should in that case eliminate unused A-class from wikiprojects that do not use it then unless and until they develop a process for it. The idea here isn't to replace you, the idea here is to suggest to you that a GA has been improved over time and perhaps it is time to re-asses it. Indeed you can manage it however you like. Mine was merely a suggestion that would achieve the exact same thing while the template displayed GA and a separate template displayed A class (or an extra parameter which would override the appearance while other parameters would be enough for bot process). It would be helpful to have the assessments template to be as simple as possible. I am more concerned with that. -- A Certain White Cat chi? 01:25, 23 July 2015 (UTC)
A-class is the best assessment that we have. It is far more rigorous review than GA. It involves multiple reviewers rather than a single one, and is done within communities of subject-matter editors rather than arbitrary reviewers, which promotes greater consistency. It includes image and source reviews. A-class MilHist articles are close to FA. Often cases they exceed it. I am totally opposed to the abolition of A-class. A-class is far better than FA because there is no limit on the number of articles that can promoted to A-class, which is why most A-class articles can never reach FA. It is a vital part of our mechanism for producing quality articles. If a well-defined process is required, then other projects are free to adopt the MilHist one, which works well. Hawkeye7 (talk) 22:10, 22 July 2015 (UTC)[reply]
A class is below FA class. I would think it would be better we improved GA itself. Perhaps make GA meet the MilHist A-class standards and demote existing GA to something like an intermediary B+ (which would be reassessed as GA if it qualifies). We have always raised the bar in quality where we demoted even FA articles. My hope here is to reach to a standard scale that everyone can agree. -- A Certain White Cat chi? 22:27, 22 July 2015 (UTC)
Yes, A class is below FA. But there are limits as to how many articles can be nominated for FA. For the purpose of automated assessment, it is equivalent to FA. Hawkeye7 (talk) 02:17, 23 July 2015 (UTC)[reply]
I don't think increasing the threshold for GA promotion—at least in terms of making it a multi-reviewer process—is viable. GA was originally developed precisely to provide a light-weight, single-reviewer alternative to other review processes; even if we were to raise the bar for GAs, it would simply result in a new process having to be created to fill the need for a light-weight review. Kirill [talk] 00:43, 23 July 2015 (UTC)[reply]
Yes, hence B+ ranking below GA and above B. -- A Certain White Cat chi? 01:25, 23 July 2015 (UTC)
Well I think it's far simpler to leave GA as it is, and leave the A-Class to be used by those projects that choose to employ it. Cheers, Ian Rose (talk) 03:03, 23 July 2015 (UTC)[reply]
  • @Kirill Lokshin:, @Ian Rose: thank you for your insightful feedback. I was unaware this Wikiprojecy used subject matter experts (SME) to insure quality and I would certainly not want that to go to waste. However, I think it would be safe to remove if from wikiprojects that have no use for it. Would that be fair? A-class would be an opt-in only where opt-in would have a criteria such as having subject matter experts etc as Wikiproject Military History has. A-Class feels weird to me as it overrides community decision and that should only be granted to wikiprojects that has an actual process that improves quality.
  • I am not trying to disrupt an existing and working system. I just want the WP1.0 rating system to follow a certain site-wide standard so we follow a quality standard that does not get any less than a certain level. A-class is an anomaly in that rating system. From the above discussion, it sounds to me like Wikiprojects use A-class in a manner more or less independent of GA, FA ratings. Commons has a few different assessments as well. For instance there is Featured pictures but also Quality images and Valued images where the three are independent of each other with different criteria. The idea here is to segregate the A-class process so that it stands on its own with SME assessment and community cannot overrule said experts with a FA process (and really vice versa for GA). This is kind of what I meant by "Seal of Approval" which would use the A-class process. Being "Featured" would be a community quality level and SME assessment would be independent of it. We would want people to seek both FA and this new standard. Would this be a better direction?
-- A Certain White Cat chi? 08:47, 23 July 2015 (UTC)
  • Sure, it's just that I've always seen FA as a community-based assessment while A-Class is project-specific (in other words I think what you suggest is already the case), and assumed that A-class was purely opt-in anyway and didn't need removing from Wikiprojects that didn't use it -- but perhaps I've missed something. I guess we need to know the exact nut-and-bolts of what's being proposed because I'm still a bit unclear on it. Cheers, Ian Rose (talk) 09:10, 23 July 2015 (UTC)[reply]
  • @Ian Rose:, we are slowly building consensus I think. There is a reason why I posted a link to relevant wikiprojects. Initially I did not understand the point or purpose of A-class however this is more clear to me now. I suppose the current state I have in my mind is to segregate SME driven A class from community driven GA and FA. Perhaps with this an article may have two title templates. Should we discuss this angle? I want to investigate what kind of a change would be more relevant and agreeable for you. -- A Certain White Cat chi? 14:55, 23 July 2015 (UTC)
Just popping in to support what the other Milhist coords and others have said above. If you think it would be useful to removed A-Class from other Wikiprojects for your purposes, that's up to them, but Milhist's A-Class review system is tried and true, provides SME input and scrutiny, and at the very least, three sets of eyes to look over not only the military aspects of the article, but also identify areas where the more generic WP standards need to be improved. FA is a very tight bottleneck, I always have half a dozen articles I would like to nominate, but the one at a time rule means I usually get two or three to A-Class before I get one cleared through FA. I agree that our A-Class far exceeds GA, and that is evidenced by the amount of comments newly promoted GAs get when they are nominated for A-Class review. Cheers, Peacemaker67 (crack... thump) 14:03, 23 July 2015 (UTC)[reply]
  • I would also advocate to keep the A-class review rating (at least on Milhist) per Peacemaker.--Tomandjerry211 (alt) (talk) 15:07, 23 July 2015 (UTC)[reply]
    • I do not suggest removing it either, but segregating it as A-class involves SMEs where as GA and FA does not. As a reader I would be more interested in looking at articles that are both FA and A-class since that means not only is the articles style and etc are in like with FA criteria but also its content has been verified and improved by SMEs. The two are different. In this system a FA that wasn't promoted to A-class would be nominateable for SME review. -- A Certain White Cat chi? 17:24, 23 July 2015 (UTC)
  • Just noting here that an article that is promoted to A-class does not loose it's {{good article}} status, and (for articles I've been involved with) are still assessed as GA-class for projects other than the one doing the review (note that all the national road wikiprojects share WP:HWY/ACR). And A-class is actually quite linked in with the 1.0 assessments - for the HWY/roads projects at least, A-class nominees are already GAs, and are usually put through ACR as preparation before a FAC nomination. A-class fits in between GA and FA. - Evad37 [talk] 17:04, 23 July 2015 (UTC)[reply]
    • But that is self contradictory, in WP 1.0 rating you are either a GA or A-class. I am saying it can be both but I feel we really need to segregate the two processes for this to work as intended. In terms of operation it would change very little, we may just add another template perhaps... -- A Certain White Cat chi? 17:24, 23 July 2015 (UTC)
      • Hi, this is also responding to your reply to me at 14:55, above. An article can only be GA or A for the same project, but it can be both GA and A overall. That is if you put an article through GAN, all project ratings are set to GA and you get the little GA icon at the top of the article, as well as "A good article from Wikipedia" if you have article assessments turned on in your Preferences. If you then take it through say MilHist ACR, the rating for MilHist and associated projects (e.g. Ships or Aviation) will be A, but not any others, so the article as a whole will be both GA and A and at the top you'll still see the GA icon but you'll also see "An A-class article from Wikipedia ... Also a good article". Then if you go through FAC with it, all ratings will change to FA, the icon will change to the FA bronze star, and you'll see "A featured article from Wikipedia" at the top. So I think A-Class, though a project- rather than community-based system, does slot in quite logically -- I even wrote a little thesis on it (complete with diagram!) for the monthly MilHist newsletter a few years ago. Cheers, Ian Rose (talk) 22:11, 23 July 2015 (UTC)[reply]
        • Or to put it another way, a Good Article (one that has passed a GA review, but not yet an FAC) is not necessarily a GA-class article (an article assessed with |class=GA in a projects banner) - for the projects using an ACR process, a Good Article can be assessed as A-class for that project (but for other projects it would still be GA-class). - Evad37 [talk] 01:04, 24 July 2015 (UTC)[reply]
          • Yes, I think so. Cheers, Ian Rose (talk) 01:14, 24 July 2015 (UTC)[reply]
            • Ergo, in principle neither one of you would object segregating A class out of the WP1.0 scale then? -- A Certain White Cat chi? 02:11, 24 July 2015 (UTC)
              • What's the point of doing that, though? It would inflate the numbers of GA-class articles in the projetcts' statistics, which wouldn't then show the A-class articles. Note also that the purpose of article assessments is, per WP:COUNCIL/AFAQ, to allow a WikiProject to monitor the quality of and prioritise work on its articles, and to allow Wikipedia 1.0 to prepare static releases. Neither of these purposes require an article to have a single quality rating across all projects – for any assessment level. For WP1.0, the bot takes the best rating as the rating of the article (per WP:1.0/A); and for wikiprojects, see the FAQ "Are these ratings official? Not really; these ratings are meant primarily for the internal use of the project, and usually do not imply any official standing within Wikipedia as a whole" (WP:COUNCIL/AFAQ). - Evad37 [talk] 02:16, 24 July 2015 (UTC)[reply]
              • Actually, can you explain what you mean by segregating A class out of the WP1.0 scale – I may be misinterpreting it. - Evad37 [talk] 02:36, 24 July 2015 (UTC)[reply]
                • @Evad37: basically it means we will stop treating A-class as something in between GA and FA and instead treat it as an independent metric. Hence WP:COUNCIL/AFAQ would not have an A-class column like it does now and instead would denote A-class as some independent metric determined by SMEs. We can functionally achieve this in certain ways such as using an additional parameter or an additional template where this would be designed to solely handle A class assessments in no way influencing GA/FA assessment and vice versa. This way getting your favorite article FA would be nice but then you would also seek A class from SMEs. We may perhaps call it something different than "A class" if SMEs do not quite like the name. Perhaps something like Quality Article or Informative Article - still achieving the same thing as A class, SME verification of content. Mind that this would also make SME involvement more prominent making the reader more confident of the contents completeness. As for your other point, the only thing official in this site is remarks made by WMF board of directors and their representatives (staff) so I wouldn't worry too much about "official" too much. Legally speaking we are all just informally maintaining this website. -- A Certain White Cat chi? 03:09, 24 July 2015 (UTC)

RM at WP:SAL

Please see: Wikipedia talk:Manual of Style/Stand-alone lists#Requested move 23 July 2015. thanks... Blueboar (talk) 11:48, 23 July 2015 (UTC)[reply]

Editors offering 'donations' to get their pet article published

I recognise that it is often an expression of exasperation, along the lines of "How do I get my awful piece of COI junk accepted? Must I make a donation to Wikipedia in order to do so?" but I also see this as a highly offensive behaviour. It offends me as an editor because it implies that my editorial judgement at WP:AFC (where I review reasonably actively) can be bought, and it offends me as a Wikipedian because it implies that Wikipedia can be bought. This takes the concept of paid editing, playable to some, unpalatable to others, to an extreme I find deeply unpleasant

This means I do not feel disposed to treat this lightly.

We do not treat legal threats lightly, even throwaway ones, and I wonder if we ought to treat offers of corruption, even throwaway ones, the same way.

What I am hoping for is a discussion about the formulation of a simple policy or guideline that allows editors and those issuing the silly words alike to understand that it is unacceptable behaviour and how they should proceed. This might included a suitable single issue notice or warning able to be issued by (eg) Twinkle. Fiddle Faddle 12:42, 23 July 2015 (UTC)[reply]

I hear that you feel offended by this action but, as an uninvolved party, I don't see anything disrespectful in the example you gave. It's difficult to talk in hypotheticals but I see neither an offer nor a threat in the quote above. Asking if Wikipedia publishes articles in return for donations isn't implying that your "editorial judgement" can be bought, it's asking about the process involved. It's a straightforward question with a simple answer; no. Should we not just educate the newbie and move on? I don't think we can warn people for asking how Wikipedia works- surely it's already opaque enough without making general enquiries an offense? Perhaps there is more to the situation than you feel you can post here? Djonesuk (talk) 22:56, 23 July 2015 (UTC)[reply]
It's not entirely easy to explain the issue because it can sound bizarre. What concerns me is that Wikipedia is devalued unless we have a standard response. That response is something that I consider, at present, would be best enshrined in a guideline. I don't want to upset further someone who is expressing frustration, and yet, in parallel with that I feel the need to refer them somewhere, not just to me as a "kind uncle explaining to a child" (a poor metaphor, but you get my drift, I hope). In the past few days I have encountered two certainly, perhaps more, folk making the rhetoric offer of a donation to get their drafts accepted. I had not encountered it before, though I have reviewed quite a few drafts. The cluster may have made it seem to be more of an issue than it is. Even so I am leaning towards a formal guideline to refer to. Fiddle Faddle 23:13, 23 July 2015 (UTC)[reply]

Leave a Reply