Talk:Code of Conduct/Archive 4

Progress overview
Many parts of the Code of Conduct have reached their final state (see this page and the archive for discussion and consensus votes). There are still several steps left, organised by section here:


 * Page: Code of Conduct
 * This section is finalized.


 * Page: Code of Conduct/Cases
 * This section is finalized.


 * Page: Code of Conduct/Committee
 * Meeting the Legal and HR requirements regarding confidentiality. There is a draft for this, and there is an ongoing discussion on this page.
 * After these sections are done, the "Page: Code of Conduct/Committee" section will be almost done.


 * Page: Code of Conduct/Amendments
 * Discussed at Talk:Code_of_Conduct/Draft


 * After all sections are in their final (draft) state, there will be a call for consensus on the final proposal.

Suggested addition: Date of enactment
While legally it is clear that this contract does not apply retroactively, to protect former contributors who cease their participation when these terms come into effect IMHO it is useful to add the date of enactment to the second sentence in the form of:

"It applies both within physical spaces, such as Wikimedia technical events and Wikimedia technical presentations in other events, and virtual spaces (MediaWiki.org, wikitech.wikimedia.org, Phabricator, Gerrit, technical mailing lists, technical IRC channels, and Etherpad) since 2016-mm-dd."

This reminds potential harassers that there is no basis for communication with former contributors, and if that doesn't stop them it spares victims from proving to law enforcement that they did not consent to any special agreements between them and the harasser.


 * --Tim&#160;Landscheidt 23:11, 31 March 2016 (UTC)


 * In what way does this "code" become a contract, especially in consideration that there is no exchange of property, at least for unpaid volunteers? --Fæ (talk) 17:39, 1 April 2016 (UTC)


 * A contract is the congruence of multiple declarations of intent. The consideration of this contract is not monetary or some property, but that other parties refrain from exercising their freedom of speech and submit themselves to the Committee.  --Tim&#160;Landscheidt 19:12, 1 April 2016 (UTC)
 * No, I think this is off-beam. I doubt it would be called a "contract" under UK law or US law (which requires a meaningful exchange of property to be enforced in court, otherwise it's just puffery about waiving legal rights to a "Committee" of unelected and unqualified amateurs), or represent the sort of proof for law enforcement you seem to be expecting. Adding a "date of enactment" appears to be wrapping an on-wiki guide in legalistic language that would be more likely to mislead contributors being harassed into thinking these are legal documents providing protection, or that the proposed committee has some sort of legal basis for authority. They are not and they are not intended to be "legal".
 * If they were, then it would be sensible to advise anyone setting up an account to consult an attorney before agreeing to a complex and open-ended "contract" that is likely to be amended or extended without official notice, and all accounts would have to be non-anonymous for the "contract" to be enforceable against identifiable individuals. --Fæ (talk) 12:21, 2 April 2016 (UTC)


 * If someone has questions about what they are agreeing to, I'd certainly advise to consult an attorney because if someone proposes to you a complex agreement it usually reflects their interests, not yours. But my concern are not the remaining contributors, but the ones who have left and may still be hit because at a glance this draft makes it sound as if all contributors to Wikimedia projects always consented to it, and that is not the case.  --Tim&#160;Landscheidt 18:06, 2 April 2016 (UTC)


 * It is clear that this is a WMF project -- it has been worked on almost entirely by WMF staff, it has been drawn up using WMF consultants whose report has not been revealed to the community, and it is linked to WMF team goals at T90908. It will presumably be implemented by WMF authority, on the basis that access to WMF servers, services and funds will require compliance with WMF rules, policies, terms and conditions.  I have asked for clarification on whether the community will be invited to discuss the Code before it is formally promulgated, and whether they will be asked to approve it, but no-one seems willing to say that either of those will happen.  As with the overlapping Event Ban policy, I think we may expect that, once completed to the satisfaction of WMF staff, it will simply be brought into force without further ado.  Rogol Domedonfors (talk) 21:19, 2 April 2016 (UTC)


 * Matthew has described the approval process on : "When the last section is completed and approved on the talk page, the Code of Conduct will become policy and no longer be marked as a draft." --Tim&#160;Landscheidt 22:13, 2 April 2016 (UTC)


 * Thanks for pointing that out -- I am a little surprised that the question I asked here about the next steps should have been answered elsewhere, on a list I don't subscribe to, without at least a cross-reference on this page. But I suppose that WMF staff are very busy, and at least the answer is now public.  I dispute the wording community approval through the discussions on each section in that email: for the reasons I outlined already in this thread, and from my own experiences, this Code has not been approved by the community in any real sense.  It has been developed almost entirely by WMF staff, with minor input from non-staff volunteers, with parts of the discussion hidden from community view, and approved by WMF staff.  It is a WMF policy, imposed on the community by WMF action.  Why trouble to disguise that fact?  Rogol Domedonfors (talk) 11:18, 3 April 2016 (UTC)
 * Sorry, you're right. I intended to post that here as well, but I forgot.  I've now posted it on Phabricator as well:

We’ve gotten good participation as we’ve worked on sections of the Code of Conduct over the past few months, and have made considerable improvements to the draft based on your feedback.

Given that, and the community approval through the discussions on each section, the best approach is to proceed by approving section-by-section until the last section is done.

So, please continue to improve the Code of Conduct by participating now and as future sections are discussed. When the last section is completed and approved on the talk page, the Code of Conduct will become policy and no longer be marked as a draft.
 * Mattflaschen-WMF (talk) 21:25, 4 April 2016 (UTC)
 * Regarding your other statement, your characterization of this as a WMF policy is not accurate. Anyone can see for themselves how this draft has changed extensively over a period of months due to both volunteer and staff involvement.  This started at a public meeting at the Wikimania Hackathon, and everyone has had continuous opportunities to participate since then.  Ultimately, people (especially volunteers) are going to work on the projects they want to and have time to work on.  Trying to dismiss the process due to a claimed lack of volunteers does not reflect that reality of how communities operate. Mattflaschen-WMF (talk) 21:28, 5 April 2016 (UTC)


 * I do not see what else you can call it. The volunteer involvement has been small; almost all the discussion and wording has come from WMF staff; two of the top three non-staff by contribution count are explicitly repudiating the claim of volunteer consensus in this very thread; almost all the declarations of consensus have been made by WMF staff members on the basis of discussions overwhelmingly involving other WMF staff members; some discussions were taken off this page to Phabricator without notification here; some of the input has been from WMF consultants commissioned by and reporting to WMF staff in a report not yet seen by volunteers; some of the input has been mandated by WMG Legal; the code will be overseen by a WMF team as final authority; promulgating the Code is a formal WMF team goal on Phabricator.  To say that is a WMF policy rather than a community consensus is not to "dismiss the process", it is to describe it.  You may wish it were otherwise, but to adopt your own wording, to call this a community consensus does not reflect reality.  Rogol Domedonfors (talk) 21:12, 6 April 2016 (UTC)


 * Rogol Domedonfors, the ownership of a policy is defined by who is invited to participate, not by the percentage of people that decide to participate. If we would have been after a WMF policy, we would have taken a very different approach and, say, after a review period of 30 days, we would have enacted it. Yet here we are, progressing at community speed, inviting the technical communities to participate in every new section, in every new decision, seeking community consensus as reasonably as we can. Besides, as I have said before, most of the topics being discussed are not WMF related. The definition of what constitutes unacceptable behavior (the most discussed topic by far) does not depend on whether you are volunteer or staff.
 * The fact is that the Wikimedia technical community is the only one where the percentage of WMF employees is a lot higher. While WMF employees can be community members of en.wiki etc only in their personal volunteer capacity (since we are explictly discouraged to edit articles from our WMF accounts), WMF employees working on technical projects are community members at Wikimedia tech in their full right, they may become (and frequently become) admins, maintainers, and organizers of other community activities. WMF employees working in tech projects also spend plenty of time in online & offline Wikimedia technical spaces, and therefore they are clear users of this CoC, either as potential offenders or potential victims. Therefore, would you agree that the participation in this discussion of WMF employees working in Wikimedia technical spaces is at least as relevant as the participation of volunteers who are rarely active in Phabricator, Gerrit, technical mailing lists as wikitech-l, technical events, or here at mediawiki.org?--Qgil-WMF (talk) 05:43, 7 April 2016 (UTC)
 * You've gone off on a tangent here, but I note that you made a list in your question which is different to the CoC scope, I presume you had your reasons for doing so. The CoC includes "technical IRC channels, and Etherpad" and any event where "Wikimedia technical presentations" might be given (I presume this means given by WMF employees). Though there is a link on the word IRC, I do not believe for one minute that the intention is to limit the CoC to MediaWiki IRC channels, and Etherpad is widely used for almost any meeting or discussion. If you include those applicable spaces, then no, you cannot claim that WMF employees are the majority of participants and therefore must dominate the decision to implement this CoC and be obliged to comply with a WMF appointed Committee's decisions of who to ban or put on a secret list (this from the latest event ban document). --Fæ (talk) 09:08, 8 April 2016 (UTC)
 * I'm not claiming that "WMF employees are the majority of participants and therefore must dominate the decision to implement this CoC". I'm just saying that WMF employees working on technical projects are regular users of Wikimedia technical spaces, regular members of the Wikimedia technical community, and therefore their opinions count just as much, regardless of affiliation.
 * Look, I'm the first one willing to have a higher participation of technical volunteers, WMDE tech members, and people with other affiliations. I actually spend a significant amount of time asking them directly. However, what else can we do to increase this participation, in addition to all what we are doing already? We cannot pull their tongues or fingers. We cannot blame the WMF employees stepping by their own initiative for participating either. Reading some of the comments it sounds as if we are discriminating or censoring the participation of non-WMF people in this process. It is not the case, quite the opposite.--Qgil-WMF (talk) 10:08, 8 April 2016 (UTC)
 * It seems rather late to ask that question. If you go back in the archive to 19 September 2015, you will find that I requested "could the owner of the stakeholder list and the communications plans for those stakeholders post links to them" .  A member of WMF staff responded "I think the current tactics drafting here and pinging wikitech-l is good enough until we have a version of the draft we are happy about. Then we can make the big call, knowing that more ideas will come, more criticism will come, and more edits are likely to come."   The requested communications plan was never published, but presumably the person who posted that response had one in mind.  It was around that time that the involvement by WMF staff accelerated and fairly soon non-staff contributers were explicitly stating that they were feeling overwhelmed.  There is no question of "blame" here, merely a recognition that, whatever the original aspirations, the Code as it stands is in practice a creation of WMF staff and will be imposed and supported by the authority of the WMF.  What's so bad about that?  Rogol Domedonfors (talk) 21:09, 8 April 2016 (UTC)
 * Re "I presume this means given by WMF employees", that is not correct. Everything in the intro and "Unacceptable behavior" sections of the draft applies to both staff and volunteers, without exception.  So it does not matter who is giving the presentation.  Regarding, "I do not believe for one minute that the intention is to limit the CoC to MediaWiki IRC channels", as the text says, it applies to technical IRC channels.  So there are some channels connected to the Wikimedia movement that would not be covered, but technical channels like #wikimedia-dev, #mediawiki-parsoid, etc. etc. would clearly be covered. Mattflaschen-WMF (talk) 04:21, 10 April 2016 (UTC)
 * Please provide a link to the definitive list of IRC channels this CoC applies to. At the moment "etc. etc." seems to be whatever a WMF employee would like it to be and may or may not include project channels, OTRS channels, admin channels, any channel with "Wikimedia" in it, etc. etc. --Fæ (talk) 18:02, 10 April 2016 (UTC)
 * ✅ --Qgil-WMF (talk) 08:42, 19 April 2016 (UTC)
 * Sorry, not really done. In defining technical mailing lists, you have linked to a section with several subsections. This includes lists like wikimedia-medicine and wikidata-tech. As far as I am aware the users of those lists have no interest in applying this CoC and therefore being governed by a committee that they have not voted for.
 * I presume that for the many IRC channels listed in IRC/Channels#MediaWiki_and_technical, the channel notices will be changed so that anyone joining those channels is aware that this CoC applies to their behaviour in those IRC channels and any text that may be interuptive or offensive might result in a global ban if the Committee thinks it's appropriate?
 * Lastly, what about Etherpad? Surely this CoC can only apply to when Etherpad is being used to support relevant events or discussions. If someone wants to use Etherpad to rant about something to one of their mates, why would anyone care or for that matter know? Unless the WMF keeps logs of every etherpad discussion after it is deleted, a general policy cannot apply to every Etherpad instance. --Fæ (talk) 11:46, 5 May 2016 (UTC)
 * This specific discussion is going too far away from the subject of this section. If you want to continue it, please create a new section. If a Wikimedia list is technical, then it is a Wikimedia technical space. That is a simple principle. How to reach these mailing lists is being discussed in another section. Adding notices in Wikimedia technical IRC channels explaining that they are covered by the CoC is a good idea. https://etherpad.wikimedia.org/ being within the scope of this CoC means that if soemone is being harassed through this medium in the context of Wikimedia technical work, that action can be reported.--Qgil-WMF (talk) 08:51, 9 May 2016 (UTC)
 * Etherpad is one of the virtual spaces listed, so all activity on the Wikimedia Etherpad is covered, in all contexts (including the one Quim mentioned). Mattflaschen-WMF (talk) 20:39, 1 June 2016 (UTC)

"marginalized" and "underrepresented"
Can we get any clarity on how it would be determined whether a group is "marginalized" and/or "underrepresented"? And, for that matter, what counts as a "group"? Yaron Koren (talk) 16:46, 12 April 2016 (UTC)


 * since you shepherded this text into the Code of Conduct, surely you can shed some light on the meaning of these words? Yaron Koren (talk) 17:40, 18 April 2016 (UTC)


 * I don't think this is a place to discuss Social Theory. If a report of discrimination is presented and the reporter or anyone else declares that a reason for discrimination is being the relation of the alleged victim with (name a marginalized or otherwise underrepresented group here), then the Committee will study the accusation. I have added an entry to the FAQ.--Qgil-WMF (talk) 09:17, 2 May 2016 (UTC)


 * I don't think this is a theoretical discussion - the current code of conduct specifies that any group-specific outreach program is either encouraged (is the group is marginalized or underrepresented) or banned (if it's anything else). So how do we know which it will be? Yaron Koren (talk) 13:21, 2 May 2016 (UTC)


 * Can you provide a realistic example where the current wording gets in the way of solving a problem?--Qgil-WMF (talk) 13:28, 2 May 2016 (UTC)


 * Sure. There have already been three theoretical cases brought up of MediaWiki-related outreach efforts where it's not clear whether the WMF would encourage or penalize such efforts:
 * For Hungarian speakers in Hungary
 * For evangelical Christians in the United States
 * At an all-boys school in the United Kingdom. Yaron Koren (talk) 13:53, 2 May 2016 (UTC)


 * Outreach efforts to targeted groups are always allowed. In the case of marginalized and otherwise underrepresented groups, they are even encouraged. The three examples you have provided would clearly be compatible with the Code of Conduct.--Qgil-WMF (talk) 14:11, 2 May 2016 (UTC)
 * That is not what the CoC says (and it was not added to it, despite explicit requests). It says discrimination is forbidden but "targeted outreach to [marginalized and otherwise underrepresented] groups is allowed and encouraged". --Tgr (WMF) (talk) 15:45, 2 May 2016 (UTC)
 * The CoC says that discrimination is unacceptable behavior. Organizing a workshop for Hungarian speakers in Hungary is not discrimination, and the CoC doesn't suggest so. Organizing a workshop where someone is not accepted for being Hungarian, that is discrimination.--Qgil-WMF (talk) 17:30, 2 May 2016 (UTC)


 * What about the other two examples? Yaron Koren (talk) 17:59, 2 May 2016 (UTC)
 * It is not discrimination to organize a workshop for evangelical Christians, it is not discrimination to organize a workshop at an all-boys school... The Wikimedia movement is organizing workshops targeted to specific audiences all the time. Discrimination is usually detected not through who is invited, but who is excluded and why.--Qgil-WMF (talk) 18:45, 2 May 2016 (UTC)

Other people on this talk page have written the opposite - that yes, these are examples of discrimination. One of them is Neil P. Quinn (here) - who interestingly enough is the author of the current anti-discrimination text in the code of conduct. How do we know whom to believe? And maybe just as importantly, perhaps the fact that there's this kind of disagreement and misunderstanding of the meaning suggests that the current wording needs work? Yaron Koren (talk) 19:14, 2 May 2016 (UTC)


 * I think you are misreading Neil's statement. He wrote: "It would only allow closed programs for them if they were marginalized" (emphasis mine). As Qgil noted, it's not about who are invited, it's about who you are excludin -- hence the qualification closed. Valhallasw (talk) 20:13, 2 May 2016 (UTC)


 * ... and this is where I insist that discussions based on theoretical and statistically unlikely scenarios lead to nowhere, because this is not math but social relationships. In a real world scenario someone would organize such workshop for evangelical Christians and someone would report a case of discrimination. If the Evangelical Church of X is organizing a MediaWiki workshop in their church facilities to their congregation, that in itself is not discrimination. If someone was interested in participating but was not accepted for not belonging to that congregation, then we have a possible case of discrimination. If someone from that congregation was not accepted for being black / gay, etc, then this is a clear case of discrimination.
 * But... in my humble opinion this discussion is basically akin to bikeshedding. In all these years of MediaWiki, how many workshops targeted to a specific social group can you count?--Qgil-WMF (talk) 19:59, 2 May 2016 (UTC)


 * I wouldn't call this "bikeshedding", since the text of the code of conduct is the subject of discussion here. Probably "nitpicking" would have been the better word. But to answer that - I don't like binding text where the best defense for it is "don't worry, it doesn't matter". If the concept of "marginalized" and "underrepresented" groups is so unlikely to become an issue that these words don't even need to be defined, why have them there in the first place? Why does a technical community need to get into (as you rightly called it) "social theory" at all? You can't have it both ways - either this wording matters or it doesn't. Yaron Koren (talk) 21:15, 2 May 2016 (UTC)


 * The wording of the draft matters, because discrimination against marginalized and otherwise underrepresented groups exists in our societies and it is sadly not difficult to find. But this is not what this section is about. The scenarios presented here are about outreach to non-marginalized and non-underrepresented groups, and whether they constitute discrimination, to which I have replied that no, by default these don't constitute discrimination. If your main interest is to prevent harassment and to defend victims of discrimination, this reply should be good enough to agree and move forward. Or at least I fail to see how following your line of argument helps defending better potential victims of discrimination.--Qgil-WMF (talk) 22:28, 2 May 2016 (UTC)


 * My main interest is in making sure that volunteers don't get penalized due to unclear or poorly-thought-out rules. (Looking at the comments made on this page by non-WMF employees, it appears that I'm not the only one with this interest.) A few points: evangelical Christians are a highly-underrepresented group, in my opinion, though others may disagree. That's part of why I brought up that example: there's ambiguity even about a seemingly straightforward concept like underrepresentation; and given that the policy now is apparently not to define these words at all, that may continue to be a problem. Second, as I noted before, your interpretation of the text disagrees with those of others; which I think brings up the real chance that the "moderation committee" or whatever they're called will also disagree with you. Less ambiguous wording would fix that problem. Yaron Koren (talk) 00:38, 3 May 2016 (UTC)
 * I disagree. I think that less ambiguous wording would only contribute to wiki-lawyering. We all know what discrimination looks like; there's no reason to argue about absurd examples that are never going to happen (like evangelical Christians). I'm sure the Committee can find a reasonable interpretation when and if the time comes. Kaldari (talk) 00:44, 3 May 2016 (UTC)


 * I'm not sure if you mean that discrimination against evangelical Christians is an absurd concept, or an outreach program to them is; I'm guessing the latter. But fine, let's say it's an absurd example. And let's say the boys'-school hackathon is, too (I don't think it is). How about this one, then: the Google Summer of Code. It's an outreach program that only accepts college students, which is in a sense doubly discriminatory, because you not only have to be a certain age, you have to be paying for college, which in many cases is a significant financial outlay. I think one would be hard-pressed to describe college students as either marginalized or underrepresented. (Though again, these are undefined terms, so who knows.) I'd be interested to hear your response to that. Yaron Koren (talk) 13:36, 3 May 2016 (UTC)
 * The current draft, under "inappropriate behavior", has one bullet point which says "Discrimination (unless required by law), particularly against marginalized and otherwise underrepresented groups. Targeted outreach to such groups is allowed and encouraged." It does not disallow outreach programs in general and it does not disallow outreach programs that are not targeting such groups. Hence I'm afraid I cannot follow the Summer of Code example being brought up. --AKlapper (WMF) (talk) 14:36, 3 May 2016 (UTC)


 * The bullet point disallows discrimination, except for two cases (legal requirement and targeted outreach to, etc.). GSoC discriminates, and is not (as far as I know) covered by either of those cases. Ergo, the bullet point disallows GSoC. Am I wrong? Yaron Koren (talk) 15:03, 3 May 2016 (UTC)
 * Ah, that's clearer, thanks! There can be general (unfocused) outreach and there can be focused outreach by defining a target group based on exclusive criteria (e.g. being a student). I don't consider the latter discrimination per se, as you could also participate in Wikimedia's technical spaces without having to take part in Google's SoC (with its eligibility criteria). If the eligibility criteria of a specific outreach program make someone feel discriminated, the person could bring it up to the organizers of that outreach program (Google in case of Summer of Code) or is free to run their own outreach program with different eligibility criteria. --AKlapper (WMF) (talk) 16:13, 3 May 2016 (UTC)
 * This is simplistic. An LGBT event that was publicised as LGBT only, a Women's editathon restricted to women, or a BEM event where "non-minorities" could not take part, are all highly problematic and could easily lead to later claims of discrimination that would be hard to defend as "targeted outreach". Having events focused on minority group interests without stopping any collegiate individual from contributing is what normally goes on, and hardly anyone can disagree with that approach, but each of the three examples has been suggested in the past for targeted editathons or virtual discussion, and for all I know might have happened under the control of a local chapter. --Fæ (talk) 16:30, 3 May 2016 (UTC)
 * Fæ - you make a good point; it's another way in which the sloppiness of the current wording can lead to problems later on. As I noted before, it's not only the words "underrepresented" and "marginalized" that are poorly defined here, but also "outreach".
 * AKlapper - if outreach is never discrimination, why are the words "to such groups" in there? Yaron Koren (talk) 17:14, 3 May 2016 (UTC)
 * I personally do not know why the words "to such groups" are in there, sorry. --AKlapper (WMF) (talk) 19:34, 3 May 2016 (UTC)
 * GSOC does not discriminate. GSOC has no restrictions based on maximum age (there is an 18+ restriction which I believe is for legal reasons) or financial ability.  Someone of any age can be a college student at any level.  GSOC allows college students at any level, and it is relatively common to have older students at e.g. the PhD level.  In some countries, you can go to college without paying out of pocket.  In others, you do need to pay out of pocket.  Some people can not afford to buy or access a computer, which makes it impossible for them to become software engineers.  No one would say GSOC discriminates against them.  The ability to financially access college is a similar barrier in some places, but neither are discrimination on GSOC's part. Mattflaschen-WMF (talk) 20:05, 1 June 2016 (UTC)
 * It's not discrimination because, in some countries, college is free? What about the countries where college is expensive? Yaron Koren (talk) 21:11, 1 June 2016 (UTC)
 * You claimed Google Summer of Code is "an outreach program that only accepts college students, which is in a sense doubly discriminatory, because you not only have to be a certain age, you have to be paying for college". As I pointed out, both statements are false.  There is no restriction requiring you to be young ("a certain age") or to be paying your way through school (and some GSOC students don't pay their way through school).  As my analogy about access to a computer (which you did not respond to) shows, there are sometimes implicit barriers due to finances.  But those barriers are not put in place by Google. If Google actually wanted to discriminate against poor people as you claimed, they could limit the program to countries without universal free college, meaning fewer poor people could participate.  They don't.  It's clear they actually want to reach out to students and give them an opportunity to supplement their education with involvement in open source.  I've explained myself.  Don't expect an endless back-and-forth about this with me.  Mattflaschen-WMF (talk) 23:16, 1 June 2016 (UTC)
 * It would be appreciated if you don't defame other participants in this discussion. Yaron did not say that you need to be young to take part in GSoC.  Additionally, your definition of discrimination would require perpetrators to have (publicly shown) malice.  This is the exact scenario victims of discrimination and harassment fear: The perpetrator claims: "But I only had good intentions!" and is let off the hook.  --Tim&#160;Landscheidt 00:00, 2 June 2016 (UTC)
 * Accusing me of defamation is outrageous. I defamed no one.  Yaron said, "which is in a sense doubly discriminatory, because you not only have to be a certain age" and I characterized that quote accurately.  I said "GSOC does not discriminate", not that it unintentionally discriminates.  Google is essentially (ignoring distinctions of stipends vs. W-2 which are not the main point) hiring college students to work on open source.  Claiming that GSOC discriminates because not everyone can access college means that e.g. a hospital that only hires doctors who graduated medical school also discriminates.  That's just not what the word 'discrimination' means in this context. Mattflaschen-WMF (talk) 00:14, 2 June 2016 (UTC)
 * I never said Google wants to discriminate against poor people. (The discrimination that does occur is unintentional.) Anyway, your analogy is not that strong because going to medical school is a widely-understood qualification for being a doctor, whereas going to college is rather ancillary to being a programmer. Your laptop analogy is a little better, though the cost in time and money to get a laptop is hardly comparable to going to college. Yaron Koren (talk) 01:49, 2 June 2016 (UTC)
 * You implied that Yaron claimed that GSoC required participants to be young, and that is obviously untrue as can be seen above. Bearing false witness while knowing that the allegation is false is called "verleumden" in German, and several dictionaries translate that to "defame".  --Tim&#160;Landscheidt 18:29, 15 June 2016 (UTC)

If you find a case of discrimination in Wikimedia's participation in Google Summer of Code, please report it. In all these years I don't recall any problem of this kind.--Qgil-WMF (talk) 19:36, 3 May 2016 (UTC)


 * It discriminates against non-college students. Should that be reported? Yaron Koren (talk) 19:52, 3 May 2016 (UTC)
 * "Google Summer of Code is a global program focused on bringing more student developers into open source software development." It's an outreach activity that helps bringing people related to underrepresented groups in our developer community. Wikimedia's participation in this program hasn't been questioned by anybody for reasons of discrimination in all these years. I don't see any real problem posed by your question.--Qgil-WMF (talk) 20:31, 3 May 2016 (UTC)
 * I'm glad that no one has questioned it, but that's irrelevant: it seems like it would be banned by the current wording, unless I'm missing something. Yaron Koren (talk) 20:42, 3 May 2016 (UTC)
 * Yes, you are missing the basic point about the goal of this CoC being "fostering an open and welcoming community" and "making participation in Wikimedia technical projects a respectful and harassment-free experience for everyone". Under this perspective your examples about GSoC and other hypothetical outreach activities pose no real doubts. This section feels exhausted and there is so much work to do.--Qgil-WMF (talk) 21:57, 3 May 2016 (UTC)
 * If WMF's participation in GSoC has not been questioned in the past and this Code of Conduct draft prohibits it, that is a solid indicator that these rules do not not change the status quo. If the here repeatedly implied "solution" is that in those cases the Code of Conduct will not be enforced, this directly contravenes the stated goal that it applies to everyone equally.  It also raises the fear that this Code of Conduct will be used for harassment in that it will be enforced for some "offenders" and waived for others depending on which groups they belong to.  --Tim&#160;Landscheidt 22:29, 3 May 2016 (UTC)
 * I do not see how Summer of Code would be banned by the current wording or how the current wording would prohibit Summer of Code. I disagree that an outreach program "discriminates" just by being targeted outreach. Also see my previous comments in this thread. --AKlapper (WMF) (talk) 07:20, 4 May 2016 (UTC)
 * Yaron, Tim, you are basing your argumentations in false dilemmas. The fact is that Wikimedia's participation in GSoC has made our community more open, welcoming, and diverse. It is also a fact that GSoC has explicit rules of conduct which fit with our goal of making participation in Wikimedia technical projects a respectful and harassment-free experience for everyone. If what you care about is conduct problems in Wikimedia technical spaces, then there is no conduct problem with GSoC and our other developer outreach activities. I have left a summary at Code_of_Conduct/Draft/FAQ.--Qgil-WMF (talk) 07:28, 4 May 2016 (UTC)
 * Qgil - you'll get no argument from me that GSoC is a great program, but it's totally irrelevant to the discussion at hand, which is whether the anti-discrimination clause in the CoC would ban GSoC. Perhaps you're missing the main point, which is that this isn't intended as a criticism of GSoC, but rather of that section of the CoC, which, through sloppy wording, could possibly end up (among other things) accidentally ending our participation in a popular program.
 * AKlapper - as noted before, the presence of the phrase "to such groups" seems to directly contradict your interpretation of the wording. Yaron Koren (talk) 13:40, 4 May 2016 (UTC)
 * I'm glad that we agree that GSoC is a great program. It is a very relevant aspect to this discussion, actually. Andre and I (both former GSoC co-organizers, and both handling conduct reports in our WMF Technical Collaboration roles) don't see how the CoC wording would motivate a CoC committee to "possibly end up (among other things) accidentally ending our participation in a popular program". That section of the CoC has been reviewed twice, and that exact line has been reviewed and discussed and approved. Let's move on. The CoC is a living document, if any sentence in it proves to be problematic with real cases, we will be able to contest it and amend it. Discussing hypothetical cases like a crazy committee banning Wikimedia's participation in GSoC on the grounds of discrimination to non-college students is not the best use of our time.--Qgil-WMF (talk) 09:22, 5 May 2016 (UTC)
 * It wouldn't take a "crazy" committee, just a committee that didn't apply en:WP:IAR to the text of the CoC and didn't accept "college students" as being a group that is somehow marginalized or underrepresented. It's a very similar situation to the recent news about Oklahoma's "forcible oral sodomy" law, where the court had to rule in a way no one liked because that's the way the law was written. Anomie (talk) 13:28, 5 May 2016 (UTC)
 * Yes, exactly. Qgil - the wording was lightly reviewed and hastily approved; now it's being reviewed with more scrutiny, and the consensus seems to be turning against it. Yaron Koren (talk) 13:43, 5 May 2016 (UTC)
 * No, I'm not, and writing your own FAQs to prove your arguments does not work. College students are not a marginalized or underrepresented group in the MediaWiki community (or even in many general populaces), not least because (IIRC) a college degree is mandatory for many (all?) WMF developer jobs.  This suggests on the other hand that   are underrepresented, and discriminating against them should be forbidden.
 * Also, your sentence: "The CoC is a living document, if any sentence in it proves to be problematic with real cases, we will be able to contest it and amend it." reflects exactly the "flexible" approach that in daily life forms the basis for discrimination and harassment. What makes GSoC a "great program" that is more important than non-discrimination other than that it introduces more people to the MediaWiki community who are like the ones already there?  What are the values that the Code of Conduct is trying to convey?
 * Finally, "let's move on" is IMHO not an acceptable attitude when discussing discrimination and harassment. It suggests to participants that they should be silent so that a sense of consensus can be pretended where it does not exist.  I am very thankful to Yaron and others that they continue to point out the flaws of this draft against a much more resourceful opposition.  --Tim&#160;Landscheidt 01:01, 6 May 2016 (UTC)
 * Thanks for the summary Tim. By the way, as this CoC is going to be bulldozed through regardless of whatever unpaid volunteers have to say about it, I'll be putting my name forward to sit on the Committee. I'll be happy to fully comply with the Committee's self-governance, but would be there to provide a viewpoint from someone not happy with the processes that created it or granted it significant authority over community members. --Fæ (talk) 11:28, 6 May 2016 (UTC)


 * I do not think there was ever a clear answer to the original question at the top of the thread how it would be determined whether a group is "marginalized" and/or "underrepresented"? This is not a matter of Social Theory, but a simple practical question.  If a complaint is laid against someone and the issue of whether one of the parties involved is or is not a member of a marginalised or underrepresented group, or whether a group they belong to is or is not marginalised or underrepresented, who is responsible for deciding that issue?  Is it the person claiming membership of the group in question?  Is it an individual member of the Committee acting ad hoc?  Is it the Committee acting ad hoc?  Is it the DevRel team?  Is it a community consenus after discussion in some forum, and if so, where?  Are such decisions, once made by whoever is authorised to make them, determined for all time, or just for the purposes of a specific case?  Is there a mechanism for making decisions before complaints are laid, or are these decisions to be purely reactive?  The Code as drafted appears to be silent on these matters, and yet the answers will be needed in order to resolve any cases brought under this heading.  Rogol Domedonfors (talk) 15:19, 6 May 2016 (UTC)
 * I'd say this is covered by Code of Conduct/Draft. Are there specific aspects missing? --AKlapper (WMF) (talk) 09:57, 9 May 2016 (UTC)
 * Yes. The specific aspect missing is an answer to the question I posed, namely, who gets to say whether a given group is or is not marginalised and/or underrepresented.  Rogol Domedonfors (talk) 10:16, 9 May 2016 (UTC)
 * "Reports sent to techconduct@undefinedwikimedia.org are handled by the Code of Conduct Committee". Therefore, it is ultimately the Committee who decides whether discrimination against marginalized and otherwise underrepresented groups plays a role in a report.--Qgil-WMF (talk) 12:26, 10 May 2016 (UTC)
 * You're just restating the problem here - obviously, if anything is poorly defined in the code of conduct, the committee would have to decide what it means. But leaving it up to the committee to define various words seems like an awful idea: it makes more work for them, and it's undemocratic, in that it puts in the hands of a few people decisions that should rightfully be up to the whole community. Yaron Koren (talk) 14:18, 10 May 2016 (UTC)
 * Quite so. The proposition that the decision on whether a group is M/U is made by the Committee because they are the people who handle the complaint is bad logic, and not improved by the patronisingly terse way it is expressed.  Having the Committee make the decision is a plausible option but by no means the only one: the proposal that the decision be in the hands of the community and that the Committee follow a decision already made by someone else is no less plausible.  My point is that the choice as to who makes the decision needs to be discussed explicitly, and so far that had not happened.   Rogol Domedonfors (talk) 17:27, 10 May 2016 (UTC)
 * Rogol, you asked for an explicit answer to the question 'who gets to say whether a given group is or is not marginalised and/or underrepresented.' and you got an explicit answer. Calling that 'bad logic' is not conductive to a healthy debate. Valhallasw (talk) 20:06, 10 May 2016 (UTC)
 * The response was in the form, not of an explicit statement, but of an apparently logical argument suggesting that the answer to the question could be deduced from the text of the Code. The apparent logic of the argument was flawed, so that the response was neither explicit, nor an answer.  Terse, patronising non-answers are, I suggest, less conducive to healthy debate than robust identification of logical fallacies.  Rogol Domedonfors (talk) 21:20, 10 May 2016 (UTC)
 * The current draft counts more than my opinions, and this is why my replies are based on the draft whenever possible. According to the draft, reports sent to the Committee are confidential, and it is the task of the Committee to resolve them "eventually contacting any individuals involved and/or related administrators or project maintainers." If someone has a better answer, please share it.
 * For what is worth, I don't see how confidential reports of harassment combine well with public community discussions. I also don't take for granted that democratic processes and open community discussions are the perfect solution to deal with problems affecting specifically marginalized and underrepresented groups, and there is a thick historic record sustaining this reasoning.
 * But what is more important: again, what realistic problem are you trying to solve? Could you suggest a plausible example where the current draft would be troublesome? An example starting with a report submitted to the Committee, having a relation with a marginalized or underrepresented group that you could choose (say a transgender developer, or whatever you prefer). What problems would the current draft cause, and what alternative solutions do you propose?--Qgil-WMF (talk) 09:31, 11 May 2016 (UTC)
 * This question is frankly, a diversion. Either the Code assigns authority to some entity to determine the question of which groups are M/U or it does not.  If it does so explicitly, quote the line of the Code that assigns that authority.  If it does so implicitly, by necessary implication, make a valid logical argument.  If it does not at all, which I judge to be the case, then the issue remains in doubt.  I think that Qgil-WMF holds the position that it is implicit that the Committee has that authority, and I think his logic is faulty.  Discussing fictional scenarios will not resolve that.  As to why resolving this issue is important, the Code refers to this category of groups but without explaining which they are or who decides which they are.  The Committee will need that information to resolve complaints involving those cases.  One possible complaint might ask for additional sanctions in a case of discrimination because the complainant is a member of an M/U group; the subject of the complaint denies that the group is M/U.  Another might be that a person is excluded from an event which is targetted at a particular group.  The organisers claim that it is permitted as being outreach to a targetted M/U group; the complainant denies that the target group is M/U.   Where will they go for the information they need to resolve those complaints?  Who determines whether a group is M/U?  Is there an official list somewhere of such groups?  Of course not.  If the consensus is, that this must be a matter for the Committee's own judgement ad hoc without any guidance from the Community or anyone else, then they are left with responsibility but not authority, an untenable position.  It is very likely that anyone sanctioned under these provisions will wish to appeal, and may well do so on the grounds that the Committee's decision on the issue of whether a group is M/U was incorrect.  In such cases should the DevRel team be authorised to overrule the Committee or should they regard themselves as bound to follow the Committe's decision on this specific issue?  It seems to me important that the Committee should know what authority they have, and that the importance of that knowledge is sufficiently obvious from the broad classes of question I mention without diverting the discussion onto the fictional details of fictional scenarios as has already happened above.  Rogol Domedonfors (talk) 12:19, 11 May 2016 (UTC)
 * I agree with Rogol that these frequent protestations of "it doesn't matter what the wording is, it's never going to come up anyway" are a diversion - if some wording can't be defended on theoretical grounds, chances are that there's something wrong with the wording. But there are real-life use cases. At the risk of going down another rabbit hole: let's say someone lodges a complaint that they were discriminated against because they're Samoan. The committee finds that this was indeed the case, and then has to decide on the punishment - which, according to the CoC, has to be harsher if Samoans are a marginalized or underrepresented group. What should the committee do? Yaron Koren (talk) 15:31, 11 May 2016 (UTC)
 * "which, according to the CoC, has to be harsher" You lost me here Yaron. Why would the punishment be required to be harsher within a case of unacceptable behavior pertaining to discrimination than say a case pertaining to unwanted physical contact? I'm reading over the draft and I think I missed something. Honest question. :) Ckoerner (talk) 14:24, 12 May 2016 (UTC)
 * I meant harsher than if the group were not marginalized or underrepresented. Yaron Koren (talk) 15:10, 12 May 2016 (UTC)
 * Perhaps it will help if I make explicit what I believe some people see as implicit in the Code.
 * The status of a group as marginalised or under-represented for the purposes of a complaint under this Code will be determined by the Committee in its absolute discretion. The Committee need not publish their decision or if they do publish it need not publish the reasons for it.  Such decisions will be made ad hoc and the Committee will not be bound to follow precedent: these decisions are not subject to appeal.
 * It may help to focus the discussion if I make it clear that I personally do not endorse this statement, nor do I necessarily believe that it is what the drafters of the Code intended, I merely claim that it is a good interpretation of the position the Code as currently drafted will entail. If it is indeed the position intended by the drafters, and if it commands consensus, perhaps it would be as well to write it explicitly into the text of the Code for future reference.  Rogol Domedonfors (talk) 21:32, 13 May 2016 (UTC)

Confidentiality
Some people will recall the prior requirement that WMF Legal raised earlier. I've updated the draft to handle this. Trust and Safety also required an additional change here, which only addresses the most serious of serious matters, where they are already involved today. Mattflaschen-WMF (talk) 20:28, 13 April 2016 (UTC)
 * I don't think we should accept a code with this in it. -- Krenair (talk &bull; contribs) 20:46, 13 April 2016 (UTC)


 * We did not reach consensus on this issue, to say the least. The full discussion is here: Talk:Code_of_Conduct/Draft/Archive_1 and Talk:Code_of_Conduct/Draft/Archive_1. dumped the conclusion on us, but unfortunately did not elaborate on the WMFs position in the further discussion. Quoting myself:
 * "Why can't we just ask the victim whether they are OK with it? See Geek Feminism: Responding to reports and 'Why didn't you report it'. If the report is always sent to HR, it is very likely it will dissuade people from responding -- WMF HR is not generally seen as a neutral entity, and many people will assume HR and Legal will act to reduce liabilities for the Foundation rather than trying to solve the issue at hand, which triggers all the fears listed in the 'Why didn't you report it' post. Valhallasw (talk) 14:39, 1 September 2015 (UTC)"


 * Valhallasw (talk) 21:28, 13 April 2016 (UTC)
 * This does not appear thought out. What does "the Law" mean, just U.S. Law, or UK Law because the accused or accuser live in the UK and the UK has much stricter laws for on-line harassment? How can "the Law" apply to an international Committee of mixed WMF employees and unpaid volunteers as opposed to applying to the WMF (which seems far more likely) yet the Committee is under no particular obligation to behave as if it were under contract to the WMF? There are too many questions here for this to be understood by the people who are mandated to comply with it, just reading the words added. The longer this document becomes, the more holes seem to be fundamentally written into it. --Fæ (talk) 21:31, 13 April 2016 (UTC)


 * Just noting here that Ms. Baranetsky no longer works for the Wikimedia Foundation. It looks like she left in January 2016. --MZMcBride (talk) 03:42, 14 April 2016 (UTC)


 * Looking at the archive linked to above reminds me why I came to the conclusion last September that there was no point in my continuing to contribute to this discussion. I made these points in September and there was no response to them from WMF Legal.  It transpired that a member of WMF staff, in the course of reorganising the discussions, had taken it upon himself to tell WMF Legal that no response was required at that stage (nor, it would seem at any subsequent stage either).  However, whether or not the WMF Legal have considered these points, and whether or not they choose to share their reliberations with the community, the fact remains that this Code has been determined almost entirely by WMF staff and their confidential consultants, parts of it have been dictated directly by the WMF corporately, and it will be imposed on the volunteer community by WMF fiat.  If it transpires that the Code is legally defective, and exposes volunteers to legal risk due from issues of conflict of law that might have been, but were not, foreseen, then the WMF corporately will be responsible.  In a way that's reassuring.  How the WMF will react when (not if, but when) something goes amiss, and whether they will accept the consequences of their actions and inactions, remains to be seen.  Rogol Domedonfors (talk) 20:43, 14 April 2016 (UTC)


 * Hi all. We took another look at this section of the policy and wanted to clarify a previous statement made by WMF Legal. Given the participation by WMF employees and contractors in the technical community, it is likely for them to be a part of the Committee. Accordingly, we do think HR has an interest in knowing about the conduct of WMF staff, both if they are victims as well as if they are harassing others. The employees may in some instances be obligated to report allegations against or by staff to HR, so a policy prohibiting this would preempt WMF employee participation. We understand the concern that such a requirement holds the risk of deterring reporting with every exception to confidentiality. However, the HR team would be better positioned to act on the complaint and respond to any wrongdoing. Additionally, we hope that through actions like supporting this Code of Conduct policy, we will gain the trust of the community that we are dedicated to creating safe spaces for people on Wikimedia sites and are not interested in retaliating against good-faith complainants. Also, we want to apologize for the delay in responding to this discussion. As was mentioned above, Victoria Baranetsky left the Foundation shortly after posting her message and missed the discussion. Thank you for your patience here. MBrar (WMF) (talk) 23:50, 22 April 2016 (UTC)
 * What was the answer to my point of last September, repeated here, about potentially conflicting legal requirements in other jurisdictions? Have they been considered; is WMF Legal satisfied that these issues have been resolved; and what is that resolution?  Rogol Domedonfors (talk) 21:32, 24 April 2016 (UTC)
 * Hi We understand this is a concern. Unfortunately, it’s one that’s difficult to respond to because the answer to what law applies to a given case can vary a lot. For example, some places apply the law of wherever an incident happened, while others apply the law of where the people involved lived, and others apply law if they think their state has a “significant interest” in the case. Because this is not a policy that applies strictly to the Wikimedia Foundation (since the committee will be run by volunteers) one can’t rely on using U.S. law because of the Foundation’s location either. Volunteers will need to ensure they follow the laws that are applicable to them, which most often means the place where you live. While we are not aware of any jurisdiction with any mandatory reporting requirements for a position like this, there might be some out there, so we understand why this provision is written as it is. We do want to emphasize that this isn’t a new issue. Arbcom, admins, and others who help keep the projects running all occasionally face this question, but the projects have been very successful over many years with systems of community management in place. Volunteers understand the laws in their jurisdiction, just as they do in relation to copyright and similar issues when they engage in editing the Wikimedia projects.
 * I realise it is complicated, which is why I suggested seven months ago that the issue be looked into by the Legal team. As I understand it, the volunteers are expected to abide by the requirements of the Code and to obey the laws of their own jurisdiction (of course).  So far I have seen no discussion of what WMF Legal, or staff, want to happen when these requirements are incomptible, and what support they will give to volunteers in that event.  It seems likely that the answer is none.  There was a discussion of this last September and it seems that no progress has been made and that the issue remains unresolved.  Rogol Domedonfors (talk) 05:33, 28 April 2016 (UTC)
 * If this was true, it would prohibit other companies' employees in the same jurisdiction as WMF from contributing as well as they are not named in the proposed amendment. But in reality, WMF employees happily contribute to other software projects and attend (or even organize) in-person conferences where no such reporting obligations exist or are forbidden by local law, so this does not seem to be preempting WMF employee participation.  --Tim&#160;Landscheidt 10:48, 28 April 2016 (UTC)
 * I'm still quite unhappy with this. I understand the WMF has a legal obligation to prevent harassment by employees, and has an obligation to protect employees from harassment. At the same time, WMF HR and Legal have an obligation to protect the WMF itself. These goals and the goals of someone who has been harassed do not necessarily align. I believe in the good intentions of the WMF, but I'd rather not base policy on my current beliefs on other peoples' intentions.
 * To move this forward, I would like to suggest a possible solution: Make the non-WMF members of the committee the initial point of contact for complaints involving WMF employees (or even for all complaints -- other issues can then be forwarded to WMF members). These members have no legal obligation to report to HR and Legal, and can therefore advise the victim to escalate the issue to WMF HR/Legal, but cannot (and will not) force this. Valhallasw (talk) 10:31, 27 April 2016 (UTC)
 * An alternative is . Nemo 13:14, 10 May 2016 (UTC)


 * Hi all, I just want to clarify a few things from MBrar's comments. The complexity with these kind of international law issues isn't one that we can research and answer. One might be able to come up with several legal doctrines that could apply, but without more details about the facts of a specific case, it's simply an impossible to answer question. I really want to emphasize that this isn't a new issue though. Any activity on the Internet, or any activity at all that can reach multiple people in different places can create the risk of different laws applying. If someone lives in a place that has particularly strict laws, it's possible that it could create a conflict with this code of conduct and that person might have to withdraw from the committee to obey the law. But we're not aware of any such requirements or restrictions. If something does happen, either due to an unusual law or a misunderstanding, we have the Legal Fees Assistance Program that could help because we do want to support users who are providing their time to help manage the projects. -Jrogers (WMF) (talk) 20:40, 28 April 2016 (UTC)


 * In general, I think we can give a vote of confidence to this process as defined in the draft, and be open for improvements if specific problems arise. I also think we can give a vote of confidence to the first Committee to polish processes based on their actual experiences. Otherwise we can discuss the perfect theoretical scenario forever, presumably none of us having run into these types of legal/process situations before. I'm not talking about this section about confidentiality only, but in general for all our remaining discussions about this draft. We work on open wikis and free software, and we are used to the notion of release and improve based on practice. Ultimately what will prevail is the good criteria of a competent and trusted Committee.--Qgil-WMF (talk) 09:00, 29 April 2016 (UTC)
 * I do not know exactly who we refers to in this vote of confidence. I do not regard this Code has having the confidence of anyone but a handful of members of the WMF staff.  If the intention of this assertion is to declare the Code finished, then it is a WMF staff policy imposed on the volunteer community by WMF authority.   Rogol Domedonfors (talk) 21:17, 1 May 2016 (UTC)
 * If I understand you correctly, this was brought up already and you received a reply in https://www.mediawiki.org/w/index.php?title=Talk%3ACode_of_Conduct%2FDraft&type=revision&diff=2093859&oldid=2093338 --AKlapper (WMF) (talk) 06:42, 2 May 2016 (UTC)
 * Indeed, and the way you frame your response supports my point. There are two classes of people, WMF staff and volunteers, to whom this Code will apply, and the proposed Code treats them differently, at the insistence of WMF Legal.  The majority of contributors to the Code are members of staff and the consensus among them appears to be that they approve the Code and a senior member of staff is taking it upon himself to declare the Code agreed.  The minority of contributors are volunteers and the weight of opinion among them is that they are not happy with the process by which the Code is being implemented.  Your response is that when a volunteer expresses an opinion they have been "answered" by a member of staff: the clear implication being that a point is settled once a member of staff has given their opinion on the subject, and that the member of staff's opinion is somehow binding.  This does not look like a discussion among equals seeking to develop a consensus -- it looks like a mere volunteer raising a point which is then dismissed by the authority of a staff member, a one-way conversation in which volunteers propose and staff members dispose.  This is why I call the Code a WMF Staff Policy -- it is a policy which for all practical purposes has been developed by WMF staff members as a formal WMF team goal and which will be imposed on volunteers by the authority of the WMF acting through a WMF approved committee backed by a WMF Staff team.  It seems important to staff members not to accept this view and I do not understand why.  Why the reluctance to admit that the Code is imposed by WMF authority and accept the consequences of doing so, for better or worse?  Why the effort to make it appear, against the evidence, that this is a consensus across both classes of the community?  Rogol Domedonfors (talk) 09:10, 2 May 2016 (UTC)
 * I do not see how my personal response implied "that the member of staff's opinion is somehow binding" - my sole intention was pointing to a previous comment that looked like a potential answer to your question, without me necessarily endorsing anything. If you think that it "does not look like a discussion among equals", what is your proposal to get more equality and involvement? --AKlapper (WMF) (talk) 09:43, 2 May 2016 (UTC)
 * I made various suggestions for wider involvement several months ago. They were not taken up and it is too late to rectify the situation, which is regrettable.  I note that you do not dispute my assessment of the present status of this Code.  Rogol Domedonfors (talk) 16:28, 2 May 2016 (UTC)
 * If you have specific past comments you're referring to, feel free to explicitly point to them for the sake of a focused discussion. Regarding your last sentence, I note that I neither dispute nor endorse your assessment. --AKlapper (WMF) (talk) 12:40, 3 May 2016 (UTC)
 * The comments are in the archived pages and the links are in an earlier posting in this thread, if you wish to look at the history. There seems little point in revisiting them as the work here has taken a different track over the last eight months or so: I have already said that I see no point in trying to rewind those discussions and I can hardly suppose that anyone else does either.  The irony of a staff member apparently giving permission to a volunteer to do something in the context of a discussion about whether or not they should be regarded as equals is not lost on me.  Rogol Domedonfors (talk) 07:45, 5 May 2016 (UTC)
 * Let's keep this section on-topic, please. I have created and you can continue this discussion there. Thank you.--Qgil-WMF (talk) 09:47, 5 May 2016 (UTC)


 * I just want to get back to the original point about WMF reducing its own liabilities; I understand the concern, and, beyond what legal has already pointed out about this (and the fact that this is not a new requirement in any space, including WMF projects) -- I just wanted to raise the point that this is in addition to the committee's own handling of the report, and this concept is crucial. If a WMF employee is involved in a report, WMF HR and Legal will be notified - but that notification does not impact the work of the committee, who will still follow the process as usual and decide on whatever steps necessary with the people involved. If, for example, a report is discussed in the committee and the committee then decides to ban a person for a week from some mailing lists, then they will do that, whether the person is an employee of the WMF or not. The only difference is that if that person is a WMF employee, WMF HR and Legal should know about it.
 * That, however, also makes sense. As employees, the WMF technical spaces is our expected workplace; if we misbehave, or if we get banned, or if we were subjected to any wrongdoing or harassment, it is quite logical for our workplace HR and Legal to be aware of it. There are employment and labor laws, for example, that, while the community is not obligated to follow, WMF HR is obligated to follow when it comes to people who are its employees. This is not only an expected (and not new) term and request to have, it makes total sense given the status of the people involved. And it does not influence or change the process by which the committee decides what to do with a case. It simply says to additionally notify those two bodies, who are, quite clearly and practically, responsible for their employees' workplace conduct, and providing a safe workplace environment. MSchottlender-WMF (talk) 23:48, 20 May 2016 (UTC)
 * As I wrote above, this does not make sense. If there were any such legal requirements, they would apply to all employers, yet the proposal only mentions one, so there do not seem to be any such legal requirements.  If a WMF employee is banned from his workspace by a third party or harassed there and this should be reported to WMF HR, this obligation can (and should be) be made part of the contracts between WMF and its employees.
 * In addition, I would be very surprised if the committee would not be biased by this difference that you pointed out: If a volunteer is the alleged offender, for example banning them would have little effect on them and can be handed out freely. WMF employees on the other hand would be unable to fulfill their contractual obligations and – as was repeatedly asserted during the ED mobbing – could face unemployment or deportation as a consequence.  --Tim&#160;Landscheidt 02:43, 21 May 2016 (UTC)

There seem to be multiple discussions here in parallel: I would like to suggest to split the discussion into those topics explicitly, even though they (at least partially) affect the same text in the proposal. Valhallasw (talk) 14:25, 22 May 2016 (UTC)
 * 1) The legal requirement of employers to act in case of harassment,
 * 2) The freedom of the CoC to make decisions without interference from WMF HR/Legal,
 * 3) Whether the committee needs to/will take into account the effect of their decisions on employment etc. of the offender,
 * 4) The chilling effect of requiring reports to be forwarded WMF HR/Legal, and finally
 * 5) Potential legal issues for members of the committee


 * I support the idea of splitting discussions. As this section is today (including links to previous discussions), I barely know where to start in order to have an opinion, and I bet any newcomers to this specific discussion will feel the same x 10. If someone has the knowledge and the time, it would be good to start new sections for each of the discussions that remain open, suggesting a specific change to the current draft. From there, digesting information and seeking consensus (or at least isolating the hardest nuts to crack) should be simpler.--Qgil-WMF (talk) 06:18, 2 June 2016 (UTC)
 * Splitting per request of Valhallasw and Qgil-WMF. Mattflaschen-WMF (talk) 19:03, 15 June 2016 (UTC)

WMF is requesting that complaints involving WMF staff be forwarded to the Talent and Culture team which handles human resources responsibilities on behalf of the Foundation. WMF has a legal obligation as an employer to investigate complaints of harassment involving staff and, where appropriate, to take corrective action. In order to protect WMF staff members who make complaints and participate in investigations, U.S. laws also prohibit retaliation and WMF has a specific non-retaliation policy. The T&C team recognizes that the CoC is intended for individuals participating in technical spaces and that the CoC will be enforced by the CoC Committee. While the CoC Committee may be both the initial and primary point of contact for incidents occurring in technical spaces, the T&C team must also be alerted about incidents involving staff in order to take necessary steps to comply with U.S. and California employment laws. --ALewis (WMF) (talk) 17:16, 15 June 2016 (UTC)
 * As I have written multiple times, if this was true, it would prohibit other companies' employees in the same jurisdiction as WMF from contributing as well as they are not named in the proposed amendment. But in reality, WMF employees happily contribute to other software projects and attend (or even organize) in-person conferences where no such reporting obligations exist or are forbidden by local law, so this does not seem to be requested by WMF.  --Tim&#160;Landscheidt 18:19, 15 June 2016 (UTC)
 * The above is in regards to this change to the draft. Mattflaschen-WMF (talk) 19:03, 15 June 2016 (UTC)
 * I agree with Tim. While you can certainly request it, it's our decision. All employers of technical contributors should get the same rights over this area or none of them should, and I'm leaning towards the latter. I'll be removing the problematic text from the draft shortly, I cannot support the draft in it's current form, especially with this. -- Krenair (talk &bull; contribs) 19:40, 15 June 2016 (UTC)
 * Apparently after I posted this some people accidentally misunderstood me or it was perceived differently to how I intended (this is my fault, I wasn't very clear) - I feel the need to clarify that I do not oppose the idea of a CoC, nor am I trying to weaken it or make it impossible to enforce. The idea is good and I will support it if we can get the implementation and language fair. My position in this particular part of the document is that if we grant some employers of our contributors rights to view their cases, we need to do the same for all such employers, not just specific ones and not just affiliated ones. -- Krenair (talk &bull; contribs) 19:23, 23 June 2016 (UTC)
 * The difference is that WMF and users of Wikimedia projects such as Phabricator and MediaWiki.org, agreed to the Terms of Use (which includes the Privacy Policy). That means WMF mostly lets the communities self-manage, but imposes certain key requirements.  One of these is given in Privacy policy: "We, or particular users with certain administrative rights as described below, may need to share your personal information if it is reasonably believed to be necessary to enforce or investigate potential violations of our Terms of Use, this Privacy Policy, or any Foundation or user community-based policies."  WMF HR policies are "Foundation [...] policies".  There is no analogous policy that all MediaWiki developers agreed to with, e.g. a hypothetical FooCorp that contributes to MediaWiki. Mattflaschen-WMF (talk) 02:34, 6 July 2016 (UTC)"
 * You are missing the point. Of course WMF has the legal and technical means to require whatever it wants.  But there is no logic to posit that WMF is legally required to be informed about alleged incidents with its staff, and other companies in the same jurisdiction would not be required in the same way, and even more WMF's staff has actively organized and participated in events where no such requirement was in place, demonstrating that it does not seem to be required (or WMF has violated the law in the past).  --Tim&#160;Landscheidt 09:00, 6 July 2016 (UTC)

Legal requirement of employers to act in case of harassment
See ALewis's comment above. Mattflaschen-WMF (talk) 19:03, 15 June 2016 (UTC)

Freedom of the Code of Conduct Committee
For this point, regardless of whether the committee makes any disclosures to the WMF, it would be able to act freely. The CoC committee gets to determine how it wants to respond to issues that come to it in technical spaces and will not be consulting with WMF Legal or HR about what to do. -Jrogers (WMF) (talk) 20:50, 17 June 2016 (UTC)

Committee taking into account employment?
There is nothing in the Code of Conduct requiring that the Committee take this into account. This goes for all employers. Mattflaschen-WMF (talk) 19:03, 15 June 2016 (UTC)

Potential legal issues for members
See my comment above. We are not aware of any jurisdictions where being a member of the CoC committee would create legal problems for members. It's not a risk that can be 100% eliminated, but we have the Legal Fees Assistance Program in part to account for some sort of strange occurrence that could arise from people doing their best to help support the projects in an administrative or functionary role like this one. -Jrogers (WMF) (talk) 20:54, 17 June 2016 (UTC)

Reporter's consent
I see the draft currently has wording that "the Committee must get consent from the reporter before revealing any confidential information (including the reporter's identity) as part of the investigation." So if the committee has confidential information about someone other than the reporter, such as a witness to the event, it has to ask the reporter but not the person the confidential information is actually about? Anomie (talk) 13:20, 16 June 2016 (UTC)
 * This is a good point. I've added some wording to try to take that into account. Mattflaschen-WMF (talk) 12:43, 23 June 2016 (UTC)

Renewed addition of section on HR reporting
In, Mattflaschen-WMF added the same text that was added earlier. It would be very helpful if WMF Legal could take a more active part in this dicussion, which then hopefully leads to a text that both has community consensus and is OK with WMF legal at the same time. Valhallasw (talk) 14:50, 31 July 2016 (UTC)

Suggested rewording
Starting from the essential principle the reporter is in control, the following is my suggestion. I've tried to come up with a phrasing that takes into account that: (names have been randomly generated) Some of the committee's members have the obligation to report harassment to their HR or Legal departments. For example, WMF employees are required to report harassment involving WMF employees (either as victim or as harasser) to HR. The techconduct@wikimedia.org email address is handled by Khorshid Nosek, who has no reporting obligations, except in the case of immediate danger or child protection issues. If your report would trigger reporting obligations, Khorshid Nosek will discuss these with you before forwarding the case to other members of the committee. If you decide to not share your case with the rest of the committee, you will still be provided with assistance and support, but the committee will be unable to take further action.
 * WMF employees are required to report to HR/Legal,
 * This is likely to also be the case for other companies,
 * This is problematic because it forces the issue out of the reporters' hands (see e.g. )
 * There should be a way to provide support to victims without this being an issue.
 * (The link was very confusing to me. Those who want a quick and clear recap can read the Forbes article instead. Knowing the jargon is also needed. Nemo 19:39, 7 August 2016 (UTC))

The members of the committee and their reporting obligations are listed below:

There are two more points that need to be incorporated: but I think those should be elsewhere (not under 'confidentiality'). Valhallasw (talk) 19:02, 7 August 2016 (UTC)
 * WMF has no say in the outcome of the committee,
 * the committee may take employment into account, but is not required to.

When will this code of conduct be implemented?
I have seen this draft go on for months so I was just wondering if there as a plan to actually implement it and when. Reguyla (talk) 18:55, 16 April 2016 (UTC)
 * Your question is answered a few sections above, under Talk:Code_of_Conduct/Draft. Yes, the plan is to implement it. No, there is no definitive timeline. No, that is not a problem. Valhallasw (talk) 19:46, 16 April 2016 (UTC)
 * Thanks, hopefully sooner rather than later because urrently there are a lot of serious conduct issues with the ops on IRC that need to be addressed. Until the WMF acknowledges that at least some of the WMF's conduct standards apply at the IRC channels, the problems are going to continue. Not that I think anyone will do anything about the ops conduct there, but I am hopeful. Reguyla (talk) 23:48, 16 April 2016 (UTC)
 * For anyone curious, this complaint seems to be related to Wikimedia Forum. Anomie (talk) 13:34, 18 April 2016 (UTC)
 * It has more to do with the attitude that the ops on IRC can do whatever they want.


 * These ops are the first things some potential editors see when learning about our sites. For example, RD and a couple others recently ran off a Smithsonian employee who had come to IRC to learn about the sites. They were then accused of being me and blocked because they lived in the DC area and used Verizon like millions of other people. Because anyone who lives in the DC area and uses Verizon must be me presumably. The pettiness, retaliation and lying by admins and ops on IRC and even on wiki needs to be dealt with by the WMF. The WMF needs to start establishing that admins are accountable to policy just as editors are and this code of conduct will help that as long as the WMF is actually interested in improving the environment of the sites that is. Because the current community processes have completely failed. Otherwise, quite frankly, unless the WMF is going to deal with this problem, it's only going to get worse and the sites are going continue to decline in participation and reputation as they have been. Reguyla (talk) 14:37, 18 April 2016 (UTC)
 * While this CoC is being approved, and myself keep receiving and processing complaints about conduct in Wikimedia technical spaces. You can reach to us privately. PS: let me insist on the "Wikimedia technical spaces" part, which is the scope of this CoC.--Qgil-WMF (talk) 08:30, 19 April 2016 (UTC)
 * I understand and it's good to know you are taking questions and inquiries about ongoing problems. No offense to you guys because your intentions seem pure here but I have seen nothing from the WMF to make me believe that they/you will do anything about these problems. Maybe your hands are tied, I don't really know, but the signs of the problems are all over the place. I have advocated reform myself for the last 4 years and that led to a retaliatory ban to shut me up on EnWP and IRC, so although you may say that you are available and open to notifications of problems, I'm not really seeing much action on the problems. Including getting this code of conduct implemented. Good luck! Reguyla (talk) 16:48, 19 April 2016 (UTC)

"Yes, the plan is to implement it. No, there is no definitive timeline. No, that is not a problem." Still not a problem? Quadroutibleurpes (talk) 17:08, 14 June 2016 (UTC)
 * Congratulations to your first edit on mediawiki.org and thanks for your interest in the code of conduct draft! To answer your question: The answer remains the same (No, still not a problem) and I don't see how repeating an already answered question helps finalizing the code of conduct. --Malyacko (talk) 18:08, 14 June 2016 (UTC)
 * Thank you. A question (eg is this late or very late) may have different answers in April and June.  Pointing out rate (or lack) of progress may help completion by reminding contributors that in the real world harassment is taking place and people are suffering.  So glad to hear this is still not a problem.  Quadroutibleurpes (talk) 19:20, 14 June 2016 (UTC)
 * I've sent out the last call email for Code of Conduct/Cases (giving people a final opportunity to raise any issues). This section is (like the CoC) moving towards completion. Mattflaschen-WMF (talk) 01:22, 15 June 2016 (UTC)

Tracking current reports
I have mentioned that and I receive reports related to conduct on a regular basis, since we joined the WMF (2012), and we do our best handling them. Today I have created an internal document to start tracking new reports and our activity around them. As of now only Andre and I have access to this document. I don't expect this doc to cause any relevant changes in the way we are handling these reports, but at least we will be able to provide anonymized data. I'm thinking of our quarterly reviews as a good time and place to provide this information, under .--Qgil-WMF (talk) 09:12, 21 April 2016 (UTC)


 * Related, just for the record: Talk:Code_of_Conduct/Draft/Archive_2.--Qgil-WMF (talk) 10:36, 22 April 2016 (UTC)
 * If possible may I also recommend some kind of report that mentions the remedial action. I know that the WMF has been periodically global banning a few people a year in the last couple years but it might be good for people to see what other actions might be done and how often. Another possibility would be to create a WMF staff action wiki like the one the Arbcom uses to track case info. Of course it would have to be restricted to certain staff but it would give continuity of problems. Reguyla (talk) 01:56, 27 April 2016 (UTC)
 * Yes adding a summary of actions taken is a good idea. I'm personally inclined not to create a formal structure around this provisional internal document. I'd rather wait to the CoC to be enacted, the Committee to be created, and then let them decide how to move forward.--Qgil-WMF (talk) 09:51, 27 April 2016 (UTC)
 * Well I hope the new CoC doesn't turn out to be another Arbcom. Reguyla (talk) 19:20, 27 April 2016 (UTC)

is being added to the document, since she is a Technical Collaboration team member and also the main contact for Friendly space policy.--Qgil-WMF (talk) 07:05, 18 May 2016 (UTC)

Wider participation, still
A continuation of Talk:Code_of_Conduct/Draft/Archive_2.

Let's check what is being done and what could be done to increase the promotion of this CoC discussion, with the aim of widening the participation especially from volunteers. Space by space (feel free to edit the list below adding relevant data):
 * Physical spaces
 * Started at Wikimania Hackathon 2015 (https://etherpad.wikimedia.org/p/Wikimania-2015-Code-of-Conduct) [added by Matt]
 * There was a session at the Wikimedia Developer Summit 2016. (https://etherpad.wikimedia.org/p/WikiDev16-CodeofConduct)
 * There was not a session at the Wikimedia Hackathon 2016. Moriel and I discussed briefly about organizing one, but we decided not to because sessions are not the core activity of the hackathon. On retrospective, perhaps we should have scheduled a session.
 * Wikimania Hackathon 2016, we still have time to organize a session.
 * Not 100% physical, but we could organize a Tech talk.
 * Online spaces
 * MediaWiki.org, wikitech.wikimedia.org: there were suggestions about a sitenotice, let's discuss. Sitenotice or watchlist notice, one of both could work.
 * Phabricator is not equipped with a tool to broadcast a message to everybody. We can add a note in the homepage.
 * Gerrit is not designed at all to broadcast messages, but it can be assumed that all Gerrit users can be found in in other technical channels.
 * Technical mailing lists, Matt has been sending requests for feedback and updates to several lists (latest list of lists is wikitech-l, engineering, design, wiki-research-l, analytics, hackathonorganizers). We could discuss a one-time message to all the lists, with a request to the admins of each list to pay attention to wikitech-l or wherever source we decide to forward other communications they find interesting for their audiences.
 * Technical IRC channels, this is a bit tricky, but we could post a one-time comment in each channel, pointing to the source page, with the same request to the admins of the channel.
 * Etherpad is not designed for broadcasting messages at all. Etherpad users can be found in other spaces.

Let's start discussing the sitenotice idea. From all the options is the one that would bring more attention for lesser effort.--Qgil-WMF (talk) 09:46, 5 May 2016 (UTC)


 * What message do you envisage being conveyed in these channels, and to whom? Will it be an invitation to enthusiasts to participate and potentially restart the drafting process from scratch; an invitation to all interested to make minor or cosmetic changes only; an open call to the tire community to approve or disapprove without further changes; or a one-way announcement to the world at large that the policy is now finished and will shortly be in effect?  The message and its intended audience will surely help to determine the channels you choose.  Rogol Domedonfors (talk) 10:31, 5 May 2016 (UTC)


 * I would wait to the next request for comments, and then I would post a short intro about the CoC draft and an invitation for everybody to participate.--Qgil-WMF (talk) 08:40, 9 May 2016 (UTC)

A one off comment in IRC channels is not sufficient. To be noticed all channels where the CoC is going to be enforced will need their channel notices changed to advise everyone who logs in. A good grace time is at least a month.

For Etherpad, advising regular Wikimedians is insufficient as the tool is used by all sorts of people, such as GLAM professionals who may hardly ever log in to a Wikimedia project. Etherpad will need to be changed so that there is an advisory notice before use. Presumably global bans for harassment on etherpad will be meaningless for anonymous accounts with no Wikimedia project associated accounts.

I suggest that any notice avoid inviting volunteers to comment. At this late stage it is virtually impossible for volunteers to get anything non-trivial changed. --Fæ (talk) 09:20, 9 May 2016 (UTC)
 * Adding notices to IRC channels sounds like a good idea. Of course we have to invite participants to comment. That is the point of aiming for wider participation. While Page: Code of Conduct has gone through extensive review and it is unlikely that completely new ideas and major changes will arrive at this point, the other two pages "Cases" and "Committee" haven't gone through systematic review yet, and may still be changed or extended in fundamental ways.
 * Introducing an advisory notice in etherpads is a good idea, within the possibilities of Etherpad. It is possible to customize the default text of new etherpads. We can specify a sentence clarifying that the Code of Conduct for Wikimedia technical spaces is applicable to etherpads used for Wikimedia technical activities. Do you mean to do this once the CoC is enacted or also before, as part of this campaign for wider participation? Whether reports of harassment via Etherpad will be meaningless or meaningful, that will depend on the reports and their context. It is not something that we should address in this section.--Qgil-WMF (talk) 10:16, 9 May 2016 (UTC)
 * Perhaps you should try a break from "managing" this CoC and closing down discussion that does not follow the workflow that you have imposed without any consensus. As an example, two consultants were paid to provide professional advice, please provide a link to it rather than suppressing questions about it. If necessary you can create yet another section on this talk page to post the advice received. Thanks --Fæ (talk) 20:48, 9 May 2016 (UTC)


 * I think we must applaud the WMF staff for deciding to open up a wider discussion. It seems rather likely that there will be a rehash of the arguments here over social justice, and a concomitant delay in the finalisation of the text, but at least when the dust is settled the Code will have a plausible element of community consensus,  I wonder what the proposed timeline is now?  Rogol Domedonfors (talk) 21:26, 9 May 2016 (UTC)


 * As Qgil-WMF said, just as there was extensive review and then changes before the "Unacceptable behavior" section was finalized, there will be an opportunity for changes before the remaining sections are finalized. That does not mean we're going to go back to the beginning and re-open "Unacceptable behavior" or the other sections in "Page: Code of Conduct".


 * Regarding future publicity:
 * I'll lead a Wikimania Hackathon session about this. Hackathon says, "(more information coming soon about the schedule and how to sign up to lead a session, presentation or discussion)".  I've watched the page, so I can sign up when it opens (a ping when it opens would also be helpful).
 * This is scheduled: T137760. Mattflaschen-WMF (talk) 00:26, 14 June 2016 (UTC)
 * Regarding Quim's question of watchlist vs. site notice, I suggest a watchlist notice on MediaWiki.org and wikitech.wikimedia.org. Since we're also notifying people in other places (like mailing lists), I don't know that it needs to display on every page.  Making it slightly less prominent means we can use it for longer.  A temporary site notice may be appropriate after it's approved.
 * AKlapper (WMF), since you are bug wrangler, what do you think about putting it in the Phabricator home page as Quim suggested? If you think it's a good idea, could you do this?
 * There are a lot of IRC channels, but I think it's something the channel operators should consider.
 * Regarding Etherpad, it would be a good idea to add a footer link to the Terms of Use (and later the Code of Conduct, once it's approved). Filed as T136744.  As I said elsewhere, the Code of Conduct applies to all Etherpads.  There is no limit in the text depending on what the Etherpad is used for.


 * As far as what message to use, for now I suggest what I just posted via email and Phabricator (with whatever formatting):
 * Please participate in the discussion about how the Code of Conduct should be amended: https://www.mediawiki.org/wiki/Talk:Code_of_Conduct/Draft#Changing_the_Code_once_enacted
 * We can update this message as we move onto other things. Mattflaschen-WMF (talk) 23:38, 1 June 2016 (UTC)


 * I think we should make these extended calls for feedback when there are sections ready to be approved, as opposed to more open ended questions like today.
 * I am not aware of a process to use the watchlist notice in mw.o. I have asked in Project:Current_issues. Once we agree on an approach there, we can probably do just the same at wikitech.w.o.
 * Do we have a way to check what are the technical mailing lists with more subscribers? Posting to all of them every time we have a section for review is too much, but maybe we can increase the potential audience significantly by adding a couple of lists to the current group. For instance, comes to mind because it might cover many people that are not following other channels.--Qgil-WMF (talk) 09:15, 2 June 2016 (UTC)
 * Mailing list admins can tell you the number of subscribers for their mailing list as that's shown in the Mailman UI. (I can also imagine that someone with shell access could run some script across all lists.) http://korma.wmflabs.org/browser/mls-repos.html graphically shows posted messages and authors for those 42 mailing lists covered. --AKlapper (WMF) (talk) 09:35, 2 June 2016 (UTC)
 * Notifying people earlier of the ongoing work helps. That way, they can see how the section is developing, rather than coming in during the final approval period and saying, "I like the overall section, but I have to oppose because I really don't like XYZ".  If enough people do the latter, it may not get approved, and then we have to change the text and have a separate discussion for the changed text.  It's better to get people involved earlier.  That said, we don't want to be too intrusive, so e.g. I don't think there should be a SiteNotice about this at the top of MediaWiki.org pages at all times (it probably makes sense for limited important periods).
 * Thanks for the suggestion regarding labs-l. I have added it to my list of lists. Mattflaschen-WMF (talk) 14:19, 14 June 2016 (UTC)
 * I added a CoC text panel (W749) to the Phabricator frontpage. --AKlapper (WMF) (talk) 09:29, 2 June 2016 (UTC)

Changing the Code once enacted
In the course of another discussion, the assertion was made "The CoC is a living document, if any sentence in it proves to be problematic in real cases, we will be able to contest it and amend it." It is not clear to me that this is correct, since the Code as written has no provision for changes. It is also not clear who "we" refers to in this assertion: is it anyone discussing it at this page, the Committee, the DevRel team, the WMF Board, ... . So who has this ultimate authority over the Code and how will they exercise it? Rogol Domedonfors (talk) 05:23, 6 May 2016 (UTC)
 * I agree with you that the amendment process is something that needs to be spelled out. It's one of the things I've been thinking about. Mattflaschen-WMF (talk) 01:04, 11 May 2016 (UTC)
 * As people have noted, over time, it may be necessary to amend the Code of Conduct, in response to lessons learned or changing circumstances. It might be necessary to clarify certain points or improve procedures.


 * I think the Code of Conduct should be fairly stable, so there are not frequent changes, but amendments should be allowed. To make this possible, a super-majority (4/5) of the Committee could approve changes. Community members could suggest ideas at any time for Committee discussion.


 * What do people think? Mattflaschen-WMF (talk) 21:41, 1 June 2016 (UTC)


 * +1 to your suggestion of having a super-majority vote of the committee to approve changes. It might make sense to have a suggestion drop-box page on which people can leave proposed amendments (or send them to the committee email if they want to be anonymous) which are then evaluated on a monthly/bi-monthly basis by the committee to avoid over-burdening committee members' time. -- NKohli (WMF) (talk) 09:11, 2 June 2016 (UTC)
 * I agree. There definitely need to be formal or informal ways of suggesting amendments to the Committee. Mattflaschen-WMF (talk) 14:02, 14 June 2016 (UTC)
 * --Qgil-WMF (talk) 09:17, 2 June 2016 (UTC)
 * It seems reasonable; we'd probably want a two-week notice for community participation, like with elections. A somewhat related topic: if the committee somehow goes astray (makes weird decisions, or rewrites its own code in weird ways), would somebody have authority to replace them? --Tgr (WMF) (talk) 09:49, 2 June 2016 (UTC)
 * We can cross that bridge when we come to it. However, it is safe to say that the WMF Board would certainly have that authority. Mattflaschen-WMF (talk) 14:38, 14 June 2016 (UTC)


 * I think there are two different 'classes' of amendments. One is in, for example, the reporting steps or the handling of cases. Those are, essentially, internal to the committee, and I think it's reasonable that the committee can change these parts. However, I don't think it's reasonable to let the committee change all parts of the CoC -- that would essentially mean the committee can overrule all the consensus building that has happened here. I would therefore prefer a process where amendments are proposed and voted on on the CoC talk page. Valhallasw (talk) 10:13, 2 June 2016 (UTC)


 * I think I largely agree with Valhallasw. The authority of this code of conduct (if it has any) derives from the community, not from the committee, as I understand it. This means that the initial code of conduct would be community-endorsed presumably, but then any subsequent version of the code of conduct would be subject to the whims of whoever's currently sitting on this committee? And, of course, the committee could decide to simply do away with or dramatically alter the amendments process.
 * It seems like a valid concern that this talk page has become too insular and overloaded with Wikimedia Foundation staff. I imagine a similar concern spreads to whatever committee is formed. --MZMcBride (talk) 02:29, 3 June 2016 (UTC)
 * Agreed that we shouldn't allow the committee to amend the code. -- Krenair (talk &bull; contribs) 02:50, 3 June 2016 (UTC)
 * Might make sense to combine both approaches- have a community discussion for the amendments with a 4/5 veto option for the board or something similar the other way round. I assume amendments should be exceptional, therefore a complex process (not complicated though) should be okay. Either way, I support having a clear, transparent process that is defined before the CoC is applied. --Frimelle (talk) 12:54, 3 June 2016 (UTC)

New proposal for amendments
Many good ideas have been presented, and here is a proposal that tries to accommodate all the concerns raised. Maybe it is too detailed for the CoC draft? Anyway, I think this could work well, and the wording for the draft could be simplified if needed:


 * The draft proposed has been moved to Code_of_Conduct/Draft.

Please discuss.--Qgil-WMF (talk) 20:50, 14 June 2016 (UTC)
 * Several people commented above asking for more community involvement. I think this addresses this pretty well.  Suggested changes:
 * "changes made don't affect its essence and efficacy" -> "changes made are not expected to reduce its effectiveness". Increased effectiveness would be a good thing.
 * 'willing' -> 'wishing'
 * Define "qualified majority", or just say that there has to be consensus, and two or more Committee members together can veto.
 * Instead of "They can be proposed again after one year" (which almost encourages that), "Promoters should not perennially submit the same amendment after it has been rejected." or "If a rejected amendment is proposed less than a year later, it may be rejected." Do we need to spell this out explicitly?  Regarding length, I think we should not put this on the main Code of Conduct page.  None of the other two pages fit either, so I suggest Code of Conduct/Amendments (but still drafted here, like the other three pages). Mattflaschen-WMF (talk) 00:45, 15 June 2016 (UTC)
 * Thank you Mattflaschen-WMF, points taken. I think agreement within the Committee is just part of the definition of consensus. Wikimedia's usual practices don't require unanimity for consensus, and therefore I don't think that unanimity in the Committee should be required either. If one Committee member objects to a change but the rest of Committee members and the overall participation in the discussion agrees, that could be still called consensus. Two or more members of the Committee disagreeing to a change is a different story, that doesn't look like consensus, and when that happens it is probably better to be conservative and keep the writing of the CoC. Having the process for amending the CoC in its own page makes sense, yes. As soon as this discussion shows a basic agreement, I will move the proposal above to the Draft page for better editing and discussion.--Qgil-WMF (talk) 07:04, 15 June 2016 (UTC)


 * The new formulation ("A proposal is accepted and integrated to the Code of Conduct by the Committee when its discussion reaches consensus and no more than one Committee member opposes to it.") suggests it is accepted if the Committee's discussion reaches consensus (i.e. the committee agrees), rather than requiring community consensus. I suggest formulating it as "A proposal is accepted and integrated to the Code of Conduct by the Committee when the community reaches consensus and no more than one Committee member opposes to it.".
 * Valhallasw (talk) 16:28, 15 June 2016 (UTC)


 * Ah, good point. My intended meaning was "the community" meaning you are proposing. Change made.--Qgil-WMF (talk) 17:44, 15 June 2016 (UTC)

I have moved the draft proposal to Code_of_Conduct/Draft.--Qgil-WMF (talk) 08:17, 16 June 2016 (UTC)

Technical Collaboration instead of Developer Relations
The Code of Conduct draft includes some mentions to WMF's Developer Relations team. This is a proposal to change Developer Relations for the Technical Collaboration team. Last January we combined Developer Relations and Community Liaisons into the Technical Collaboration team. Even if Developer Relations continues to exist as a virtual team, I think it would be better to reference to Technical Collaboration, a WMF team in the full sense of the term. This would also mean getting the community liaisons involved, which would in fact reflect better the composition of Wikimedia technical spaces, formed not only by developers but also by other contributors with technical interests.

Note that the relation between the Developer Relations or any other WMF team with the CoC is still open to discussion. This proposal is only about the renaming to Technical Collaboration in the current draft.--Qgil-WMF (talk) 08:53, 10 May 2016 (UTC)
 * --AKlapper (WMF) (talk) 11:09, 10 May 2016 (UTC)

One week, no opposition, ✅.--Qgil-WMF (talk) 07:01, 18 May 2016 (UTC)

Hi Qgil-WMF. Where is "The first Committee will be chosen by the Wikimedia Foundation’s Technical Collaboration team." being discussed? --MZMcBride (talk) 13:23, 3 June 2016 (UTC)
 * The idea came in this discussion. I you or someone else have an alternative proposal, please create a new section and share it.--Qgil-WMF (talk) 14:56, 3 June 2016 (UTC)
 * Okay. I've started below. --MZMcBride (talk) 17:07, 3 June 2016 (UTC)

Over, out or off?
Six months after asking, still only bothering electrons. WMF Staff have no plans to implement Code. Is that a good thing? I am Mister Thrapostibongles (talk) 21:33, 16 May 2016 (UTC)
 * What is the point you're trying to make? Valhallasw (talk) 08:10, 17 May 2016 (UTC)
 * Point is clear. Talk starts July 2015.  January 2016: "Anything happening in the real world?  Anywhere away from this page?  Any future to this project?  Anyone responsible?"  May 2016: Still nothing.  Talk talk but no action.  WMF staff clearly not going to finish this code.  Ever.  Why not?  I am Mister Thrapostibongles (talk) 18:09, 17 May 2016 (UTC)
 * I don't understand why you think the code is never going to be finished (or why you specifically expect 'WMF staff' to finish it). You have received an extensive reply to your earlier comment on the time it takes to write the code, and in the last four months, there have been more than a few changes, something I would consider 'action'. Are you worried that the code of conduct will never actually become policy? If so, why? Do you have any suggestions to improve that? Valhallasw (talk) 07:24, 18 May 2016 (UTC)
 * As Valhallasw notes, many of Qgil-WMF's comments at your previous section are still relevant. I am still facilitating this process (see T90908).  I've just followed up on the section about the amendment process, offering a suggestion.  In addition to this, other volunteers and staff are still participating. Mattflaschen-WMF (talk) 22:14, 1 June 2016 (UTC)

What happens next?
There appears to have been little activity here this month, and indeed not much since this question was raised back in March. I assume that means that there is some kind of agreement among the authors that the Code is in an acceptable state. It seems that the only reasonable way forward is that it be publicised as it stands to the various stakeholders without further delay, asking for a simple consensus as to whether or not it should be adopted as it stands: that is, without the option of amendment at this stage. I also suggest that any further delay, in the absence of pressing reasons, be taken as an explicit acknowledgement that this proposed project has foundered, that further work on it is neither wanted nor needed, that all previous work on it has been wasted, and that the entire project has been an abject failure. Rogol Domedonfors (talk) 16:14, 29 May 2016 (UTC)
 * You asked about the next steps seven weeks ago in "Suggested addition: Date of enactment" and received answers. Did I miss any new points being made? The pace of the Code of Conduct drafting has been covered in the thread "Nine months" above. As you request "publicising (...) without further delay", could you elaborate which reasons you see for a sudden urgency and why you'd like to freeze the current draft and disallow providing more feedback? Furthermore, "any further delay" implies that there has been "delay" which would require some time schedule I'm not aware of (do you have a link?), and looking at https://www.mediawiki.org/w/index.php?title=Code_of_Conduct/Draft&action=history I don't share your personal impression that work has been "foundered". --AKlapper (WMF) (talk) 19:15, 29 May 2016 (UTC)
 * You make my point for me. Do you really regard the length of time it has taken to get to this stage as laudable?  To answer your question -- no, no new points have been made -- that is to say, no one has been willing to accept responsibility for delivery of this Code, nor has any timeline been proposed for delivery, and that is lamentable.  Of course you are not aware of a time schedule, because there isn't one, as I think you know perfectly well, and by now there ought to be.  To be perfectly explicit, the reason I suggest freezing the Code now and moving on is to move on from this leisurely polishing of minor details towards an implementation in the real world where so many of our volunteers live.  Do you believe that the Code is in an acceptble state for promulgation, or do you, or anyone else, believe that there is significant extra work that needs doing on this Code that requires significant further time to accomplish?  If so, please say what you think needs doing and how long you think it needs to carry out.  If not, why would you wish to obstruct the implementation of the Code?  Rogol Domedonfors (talk) 20:24, 29 May 2016 (UTC)
 * I don't see how things would be more "laudable" if anyone was rushing here; to the contrary. Regarding taking responsibility and a time schedule: That was covered above in "Nine months", "Suggested addition: Date of enactment", and to some extent also in "Over, out or off?". If I get it right, your actual question is "Could anyone clarify what is left to do here to get out of draft status?" --AKlapper (WMF) (talk) 20:54, 29 May 2016 (UTC)
 * You do not get it right. I am not asking for clarification, I am asserting an proposition -- that the Code is sufficiently mature to be worth promulgating -- and suggesting a course of action -- that it be promulgated as it stands.  If you disagree with that assertion, or that proposed action, please give your reasons.    Rogol Domedonfors (talk) 21:07, 29 May 2016 (UTC)
 * The CoC draft is not complete yet. The Cases and Committee pages still need to go through review. The review of these pages is what happens next.--Qgil-WMF (talk) 13:56, 30 May 2016 (UTC)
 * Your comment is written in such a way as to suggest that you have the authority to declare whether or not the draft is complete or ready to be published, and to declare what further steps need to be done. As far as I can see, you have as much or as little authority to make these pronouncements as anyone else unless and until you can achieve a consenus behind them.  If you think you have some form of authority in this area, please remind the rest of us where your authority derives from; what the scope and extent of that authority is; to whom you regard yourself as accountable for the exercise of tht autrhority nd the success or failure of this project; and explain in detail what plans you have for further work on the Code, preferably with the timeline that you expect to be held accountable for.  If you do not claim any special authority, please recast your pronouncement in such a way as to make it clearly an expression of your opinion and suggested course of action supported with reasoned argument, and suggest what criteria, in your opinion, would show the Code as being in a fit state to publish; then see if there is consensus for what your proposals, which appear to me to be in effect a policy of indefinitely protracted delay.  I remind you that the intention behind starting this work so many months ago was to achieve something: it is not clear to me that the current process is likely to achieve anything beyond an endless discussion.  Rogol Domedonfors (talk) 16:40, 30 May 2016 (UTC)
 * I'm just repeating what Matt said some weeks ago, which is the process I proposed and we have been following. It is a simple answer to your question, and I don't know why you make it complicated.--Qgil-WMF (talk) 17:24, 30 May 2016 (UTC)
 * The discussion last August which you refer to does not, as far as I can tell, give you or anyone else the authority to declare the Code finished or unfinished. What question do you think I have asked to which you believe the answer is so simple?  I have made some proposals, which you seemingly prefer to contradict rather than discuss, and some requests, which you have not met.  Rogol Domedonfors (talk) 18:41, 30 May 2016 (UTC)
 * Rogol, in your contributions on this page, you make valid points, but your contribution style does disservice to those points. Instead of trying to see if there is consensus to bring the current CoC to a vote (which is a completely reasonable thing to do), you make a statement, and when people respond to that statement, they are attacked: First you ask 'do you, or anyone else, believe that there is significant extra work that needs doing on this Code that requires significant further time to accomplish', and when Quim responds 'Yes, to do X, Y and Z', your response is 'And who are you to say so?'. Please stop with these unproductive attacks, and, if you believe that 'the only reasonable way forward is that it be publicised as it stands to the various stakeholders without further delay', please poll for consensus, to see if others agree with you. Valhallasw (talk) 18:09, 30 May 2016 (UTC)
 * Thank you for your views. You missed out the part where I asked "please say what you think needs doing and how long you think it needs to carry out".  So far no-one appears to be willing to answer that: what we do get are members of staff responding in a manner which suggests that they have the authority to decide issues by declaration rather than by discussion.  I actually put forward a proposal looking for consensus which was contradicted by a flat assertion from a member of WMF staff on no basis that I can see other than an implicit assertion of authority.
 * Let me re-iterate that the object of this entire exercise has been to deliver something, namely a code that will help make technical working spaces less damaging to participants and and more productive of good work. The longer the process is spun out, the more that objective goes unrealised.  Yet no-one, even those who regard themselves as authorised to manage this process, are willing to accept responsibility for managing the process in an effective and efficient manner -- which to my mind would include having a timeline, and sticking to it, and a stakeholder mapping with a communication plan which is actually being implemented.  Rogol Domedonfors (talk) 18:39, 30 May 2016 (UTC)
 * I don't agree with your statement "what we do get are members of staff responding in a manner which suggests that they have the authority to decide issues by declaration rather than by discussion.". Instead, I see Andre asking for clarification, and Quim answering (or at least: trying to answer) your question 'what happens next'. The answer might not touch on everything you asked, but I read it as a good faith attempt to answer your question. In other words, it's their contribution to the discussion, not an authoritative statement.
 * Nonetheless, I agree that it's problematic that the CoC takes so long. I also agree that it would be helpful to have a clear overview of the steps that need to be taken. I'm not sure if adding an explicit timeline to that is necessarily helpful: consensus building takes time, and the discussion points that are left are not the easiest ones. Valhallasw (talk) 19:15, 30 May 2016 (UTC)
 * Valhallasw, the steps I can think of right now are:
 * Meeting the Legal and HR requirements regarding the Confidentiality section. There is a draft for this, and there has been discussion regarding it.
 * There are some possible improvements that could be made to "Handling reports" and "Responses and resolutions", partly based on ideas from Ashe. In her (and my) opinion, the real issue is not whether it's simple or complex, but the initial response and later response.  Once "Handling reports"/"Responses and resolutions" are done, there could be a last call for finishing "Page: Code of Conduct/Cases", then it can be considered for approval.
 * Last call sent for this. Mattflaschen-WMF (talk) 01:22, 15 June 2016 (UTC)
 * There is the in-progress discussion regarding how the Code of Conduct will be amended once it's a policy.
 * An NDA to ensure the Committee members take their Confidentiality requirements seriously. After that and the Confidentiality section is done, I think the "Page: Code of Conduct/Committee" section will be almost done. Mattflaschen-WMF (talk) 00:19, 2 June 2016 (UTC)


 * On further consideration, I can see no plausibly productive outcome from my continuing to participate in this discussion. The Code either will or will not be finished, and it either will or will not be effective.  I have expressed my views and they clearly are unwelcome: there is nothing I can do now to promote a positive outcome.  I leave it to those who regard themselves as managing the process to take the credit and blame.  Rogol Domedonfors (talk) 19:05, 30 May 2016 (UTC)

Inspire Campaign on addressing harassment
The new Inspire Campaign makes a call for ideas to address harassment in Wikimedia. Some of these ideas will turn into projects that will request and eventually receive grants for their development. It is interesting to see this CoC effort fitting in a wider trend. There is no direct relation between this CoC and that campaign. I am sharing the news here because people watching this page might be interested.--Qgil-WMF (talk) 09:12, 1 June 2016 (UTC)

Diversity of affiliations in the Committee
Code_of_Conduct/Draft says "the Committee cannot have all members affiliated to the same employer". Diversity of the Committee is intrinsically valuable for its credibility and efficiency. More diversity means more perspectives and more flexibility to deal with potential conflicts of interest. Therefore, I propose this change to the draft: "the Committee cannot have all a majority of members affiliated to the same employer".--Qgil-WMF (talk) 09:23, 2 June 2016 (UTC)
 * Sure. --MZMcBride (talk) 02:33, 3 June 2016 (UTC)
 * Why is this even a debate when the CoC is supposed to be nearly done? The committee has no credibility if a voting majority have the same interest. --Fæ (talk) 09:16, 3 June 2016 (UTC)
 * I disagree with this, for the reasons I stated earlier. We should aim for a Committee that is qualified, diverse (in many ways, e.g. ethnic, gender diversity but also diversity of experience), and represents the MediaWiki developer community.  These are somewhat conflicting goals, since our community is not as diverse as it could be.  However, I don't support an arbitrary restriction like this.  Given the composition of the community, it could be reasonable at times for a majority of people to be employed by e.g. the WMF.  It is unrepresentative to forbid that, and could make it more difficult to achieve other diversity goals. Mattflaschen-WMF (talk) 14:34, 14 June 2016 (UTC)
 * I'm also not saying there should be a majority of people from the same employer. We should leave it up to the group selecting the Committee.  It depends on various factors, including the community, who is interested, qualifications, etc. Mattflaschen-WMF (talk) 14:35, 14 June 2016 (UTC)

Comment period for selection of new members
The current text says: ''The group doing the selection ... will then publish their candidate slate on-wiki.The community can provide feedback on these candidates... The feedback period will be two weeks for candidates who are not currently on the Committee, and one week for candidates being considered for re-selection. The group choosing the Committee will then either officially appoint the slate as members, or update the candidate slate in response to concerns raised.''

The shorter comment period for standing members seems impractical. The candidates will surely be presented together; they will have to be approved together (as approving them at different times would mean they have to agree to serve on the committee without knowing whom they will serve with; a bad idea). So there will be two weeks between publishing and approving the list of candidates (unless all of them are standing members, which is not a situation that should be encouraged). Will comments just be rejected in the second week for candidates who stand for reelection? Making the comment period uniformly two weeks seems less awkward to me. --Tgr (WMF) (talk) 09:58, 2 June 2016 (UTC)


 * This seems hypothetical. The WMF selects and appoints the committee in a closed process, unpaid volunteers have no say. A different process might apply if the WMF appointed committee wants it to, and still exists in a year from now [when the committee is first set up]. Even then, with the CoC as written, the earliest that all members are appointed with transparency will be in 2018. --Fæ (talk) 14:43, 3 June 2016 (UTC)


 * Code_of_Conduct/Draft applies to "The group doing the selection", and therefore it also applies to the WMF Technical Collaboration team when bootstrapping the first Committee, all according to the current draft.--Qgil-WMF (talk) 15:03, 3 June 2016 (UTC)
 * Under the draft, "The first Committee will be chosen by the Wikimedia Foundation’s Technical Collaboration team. Subsequent members of the Committee will be chosen by the current Committee." and "The initial Committee remains without changes for one year. From that point, the Committee elects their new members by a majority vote every six months". The community also provides feedback.  I don't know where you get 2018.  First of all, even the first Committee will be appointed with transparency (see Code of Conduct/Draft).  There is no significance at all to the date 2018.  If the first Committee is appointed in 2016 (which is certainly the goal), a new Committee will be appointed in 2017. Mattflaschen-WMF (talk) 15:15, 14 June 2016 (UTC)
 * There is no need to reject comments. There are two ways the different time period can come into play:
 * Perhaps only one member is up for re-selection right now (people can resign at any time, so it may end up one member gets elected offset from the others).
 * If say, one member is up for re-selection, and another seat is being replaced (a member is leaving), the discussion period for the new candidate can just be started a week earlier than the discussion period for the re-elected candidate.
 * That said, I don't feel that this difference in time periods is essential. Mattflaschen-WMF (talk) 14:59, 14 June 2016 (UTC)

Improvement of handling reports and responses sections
, you wrote 'There are some possible improvements that could be made to "Handling reports" and "Responses and resolutions", partly based on ideas from Ashe. In her (and my) opinion, the real issue is not whether it's simple or complex, but the initial response and later response.' above, but I can't find a section where these changes are being discussed. Did I miss that section? If not, can you add the proposal under this header? Valhallasw (talk) 11:48, 2 June 2016 (UTC)
 * I've updated the draft text for this. Mattflaschen-WMF (talk) 22:26, 11 June 2016 (UTC)

Committee membership
The current draft reads: "The first Committee will be chosen by the Wikimedia Foundation’s Technical Collaboration team."

Is there any consensus for this line? Looking at Talk:Code of Conduct/Draft/Archive 1, there doesn't seem to be agreement that the committee will be chosen by an arbitrary Wikimedia Foundation team. Many of the comments in past discussions seemed to point to nominations/elections of some kind, as I understand it. Am I missing something? --MZMcBride (talk) 17:06, 3 June 2016 (UTC)


 * On the presumption that the current text has no consensus, it was just palatable to WMF insiders, do you think that a fully open election of volunteers for the committee would be the way forward? --Fæ (talk) 17:12, 3 June 2016 (UTC)


 * Nominations and elections are certainly worth considering. I'm not sure I'm fully caught up on the backstory regarding this sentence and past related discussions. Maybe elections were deemed untenable. It feels weird to have a Wikimedia Foundation team pick the committee. --MZMcBride (talk) 23:34, 5 June 2016 (UTC)
 * Open community elections were not deemed untenable by anyone. An "appointed" committee using secret criteria and behind-closed-doors discussion is plainly unsatisfactory in terms of governance.
 * The process for creating this document is run on a type of majority vote process rather than consensus building. As the majority taking part are WMF employees and the process is directed by a WMF employee, every choice has been that of whatever a majority of WMF employees prefer. If you look through the archive of this talk page, you can see the pile-on effect which has rapidly rubbished counter-views from the small number of unpaid volunteers contributing.
 * If the committee is "hand picked" by self-appointed WMF employees, it loses credibility in terms of meaningful independence from the WMF. In the scenario where a WMF employee is claiming harassment, or has been alleged to be harassing, the current CoC simply will not work, as the committee will be unable to act independently, access evidence, or take action without first offering WMF HR or WMF Legal a political veto. --Fæ (talk) 05:12, 6 June 2016 (UTC)
 * This is incorrect. There has been a lot of consensus-building here (it's happening right now).  The Committee will be appointed in accordance with the policy.  There is nothing (in the draft, or in the Confidentiality text I added) giving WMF HR or WMF Legal a veto of any kind.  The Committee can and must apply the Code of Conduct to all members of the community, staff and volunteer. Mattflaschen-WMF (talk) 16:15, 14 June 2016 (UTC)


 * As far as I remember, this is the first time that sentence has been highlighted since it was discussed and included in the draft. It is good to discuss it. My opinion is that direct elections are not the best option to form this Committee and renovate it. The main priority of the Committee is to work well as a team of qualified contributors. Direct elections don't guarantee that as good as a managed process with nominations and public review. By design, direct elections favor majorities, popularity, and systemic biases. A managed and publicly reviewed process can favour a more diverse composition of the Committee, better prepared to deal with cases of harassment and disrespect from multiple perspectives.
 * A different question is whether this managed and publicly reviewed process to create the first Committee should be handled by the WMF Technical Collaboration team. What would be the alternatives? There was some discussion about involving the Architecture Committee but, long story short, they prefer to limit their scope to technical governance.
 * I don't agree with the argument that a WMF selected committee would undermine the independence of such Committee in cases against WMF employees (and your mention to WMF HR or Legal veto puzzles me completely, but belongs to a different discussion). Our interest is the opposite, to have a qualified and respected Committee able to deal with problems of harassment and disrespect autonomously, directly backed by the technical community. My team has dealt with cases involving WMF employees, including cases resolved against them. If no better alternative is found, I think this team would be qualified to receive nominations, propose and select a first Committee.--Qgil-WMF (talk) 09:39, 6 June 2016 (UTC)
 * At no point has it been demonstrated or agreed that an open community election for candidates is undesirable, or would give a bad result. If a candidate were put forward that the WMF does not feel appropriate, that can be discussed publicly or you could email the candidate with your concerns, just like anyone else can.
 * What exactly is the WMF scared of happening here, so that the WMF must "manage" (i.e. have absolute control of) every step of this process and avoid meaningful governance and transparency? --Fæ (talk) 17:26, 6 June 2016 (UTC)
 * I recall the criticism the latest round of community-selected board member elections received for selecting three white males from Europe and the US rather than candidates with more gender, racial, or geographical diversity (e.g. w:en:Wikipedia:Wikipedia Signpost/2015-06-03/News and notes). Such a result would probably be detrimental to trust in this committee among the groups the having of a CoC is intended to reassure. Anomie (talk) 13:25, 7 June 2016 (UTC)
 * That seems a tangent, rather than a good reason to rely on group of self appointed WMF employees to appoint Committee members and reject candidates without any open process or vote. If you wish to explain why this Committee should have some diversity criteria built in, I suggest another thread. For example you may wish to require that a proportion of members of the committee must represent certain minority groups so that it does not end up being all Europeans and Americans, all native English speakers or all heterosexual men. Such pre-agreed criteria would work perfectly well in an open vote. --Fæ (talk) 16:40, 7 June 2016 (UTC)
 * I don't think quotas as you propose would be all that great of a way to ensure diversity, as it just makes it more likely that an unsuitable person would be elected because they're the only candidate who fit the quota. BTW, why do you assume that the WMF team appointing the initial committee would appoint only themselves? Anomie (talk) 13:05, 8 June 2016 (UTC)
 * "self appointed WMF employees to appoint Committee members" does not assume they only appoint themselves. I also mentioned "require", not "quota", there are various ways of handling this without appointing unsuitable people. This is a tangent, please create a new thread if you want to expand on it. --Fæ (talk) 15:18, 8 June 2016 (UTC)


 * My concern with direct elections for Committee members have nothing to do with the WMF. Elections might be an appropriate tool to decide one winner representing the values and interests of a majority, but here we are talking about forming a team that must work efficiently together in order to protect victims of harassment (frequently not represented by majorities). Here are some flaws of the election model:
 * It takes a certain attitude to run for election. Some people that could be competent Committee members don't have that attitude and would resist to present themselves as candidates. Meanwhile, other people will have such attitude and will have the possibility to run for election even if they are potentially not a good fit to work in this Committee. A managed and publicly reviewed process eases the invitation and involvement of a wider variety of competent profiles.
 * Elections favor majorities by design, and majorities can be obtained through factors that are not directly related to the qualifications of a person to be a competent Committee member (popularity among the major constituencies of the electorate, reputation in areas different than the Committee has to deal with, communication style...). A managed and publicly reviewed process can focus better on the selection of Committee members based on their skills and merits directly related to their future work at the Committee.
 * While the winner of an election might have many merits accumulated to convince so many voters, that probability is reduced for the following candidates that get a seat with less votes, especially if the amount of candidates and the amount of voters is relatively small, as it is likely to be the case in our context. What if there were six candidates and the fifth seat was won with a dozen of votes? Since a managed and publicly reviewed process has better chances to find more candidates fitting more directly with the task, the possibility of forming a team of five competent members is higher.
 * Elections represent a competition of rivals by design, but the purpose of the exercise is to create a team that has to work together. While in an election the guarantee that rival candidates will become good partners is random at best, in a managed and publicly reviewed process the selection can focus on building a team of complementary and collaborative members since the beginning.
 * Elections are more exposed to abuse than a managed and publicly reviewed process. With the size of our community and the likely amount of candidates in an election, it would not be impossible (or maybe even difficult) for a determined candidate supported by a determined group to get a seat and use it to disrupt the Committee and the CoC itself.
 * There are many examples in real life about elections bringing these dysfunctional results when used to form teams that must work together. When a group needs to form a team, it is more usual to nominate someone to come up with a proposal, review it and either approve it or request changes for a next round.--Qgil-WMF (talk) 21:15, 7 June 2016 (UTC)
 * Certainly, these are the sorts of arguments one can use against any type of open election, and puts forward reasons to mistrust the community of volunteers. I find it enlightening that the WMF appears to fear a "determined group" mysteriously manipulating an election. Sorry, if there is a sufficiently active minority to support a candidate, using your unelected power of veto to stop them having any representation is overly authoritarian.
 * As for the reasoning, to paraphrase, "we can't have an open process as only the WMF are skilful enough to select candidates who will be suitable to work together", that seems arrogant. Looking at extremely well documented recent history, the WMF has an appalling record for appointing successful teams and retaining management that can work together for any serious length of time. It's actually an argument to avoid having the WMF control the selection process.
 * If the WMF is unable to trust the community then this CoC can be reduced to just putting you in charge and demanding volunteers follow your orders or get banned. Why don't you step back and stop acting like state police and let the community attempt to help improve your governance, public reputation and the experience of users who need help with harassment? --Fæ (talk) 07:46, 8 June 2016 (UTC)
 * Isn't the current situation that the WMF is de facto in charge? And the team that's de facto in charge is trying to give up that being in charge to the new committee? Anomie (talk) 13:05, 8 June 2016 (UTC)
 * Right now it's not really any more in charge of this wiki than other wikimedia-hosted wiki, and it's certainly not in charge of the IRC channels. -- Krenair (talk &bull; contribs) 15:23, 8 June 2016 (UTC)
 * If the WMF controls who can sit on the committee, or have the final say on the committee's processes, then that is not giving up any control, it's just having volunteers do work for you instead of paying employees. --Fæ (talk) 15:22, 8 June 2016 (UTC)
 * Fæ, the priority of this draft is to define a way to create a Committee that can serve well the purpose of this Code of Conduct. I have provided a detailed reasoning about why I believe a direct election is not the right tool for this purpose, and I think it is a valid reasoning from a volunteers' point of view. Your priority is to prevent control, censorship, and other forms of abuse from the WMF. I agree with this priority. I just disagree with your analysis about why the process currently proposed would allow that abuse.
 * "WMF" in this discussion means Andre Klapper, Rachel Farrand, and Quim Gil, the people who actually would run this process. We have a public record of years of work supporting the technical community, including the management of various community proposals and selection processes. Whatever evil machinations you fear about the WMF selecting a CoC Committee, they would be done by us.
 * We would share publicly the reasoning of our selections when proposing the members of the first Committee. If candidates declined would want us to explain or discuss our reasons with them, we would respond as well. We don't have anything to hide, we just want to select the best team possible for the task.
 * We would present the proposed Committee for community review. If our selection is partially or totally rejected, then we would take note of the criticism and we would work on a next proposal.
 * Once the Committee is nominated, their members have to commit to fairness and confidentiality regardless of their affiliation and how they have been selected. The hypothesis that a Committee nominated by a WMF team would be less independent implies that those Committee members would breach the CoC itself or would act unfairly, which are reasons to report them and substitute them.
 * Fae, you keep spreading fear about the WMF using this CoC for community control and censorship. Could you provide specific examples of how would that work in practice? At least in this section, could you explain with examples how a Committee selected through the managed process proposed could be used by the WMF for control, censorship, or other ways of abuse?--Qgil-WMF (talk) 11:15, 9 June 2016 (UTC)
 * My doubts come from personal experience of actual tactics of marginalization and threats used by members of the WMF in the past to make risks go away, not because I'm a conspiracy loon, but because I used to think this would never happen and I turned out to wrong to presume that the WMF would only behave in collegiate ways.
 * If a member of WMF legal intervenes, and says to a committee member, something like "I need you to drop this case, leave it to us", then as all committee members were required to sign a contract with the WMF with the potential for the extremely well funded legal department to pursue them personally using unspecified and unlimited "legal remedies" and "monetary damages", basically any case that the WMF board or legal feels might damage the reputation, or pose any other sort of risk to the WMF, can be instantly suppressed and the committee left unable to discuss it in any way in public, or even each other without fear of personal damage.
 * If WMF HR intervenes, they carry the same weight as legal. This would make any case that involved a WMF employee as a party to the case either impossible for the Committee to handle, or WMF HR may ask the committee to, say, suppress factual evidence from being shared with some parties to the case, or the public. This may easily happen if HR feels that the evidence may give a party grounds to later pursue the WMF for damages, or evidence that could be grounds for a civil case that they prefer never happens.
 * The WMF is able to strategically introduce delays by using an effective veto, say by asking the committee to wait while they do their own legal related investigation. Once evidence that the committee may have asked for passes the 90-day mark, any that relates to private information stored on WMF servers is deleted and will no longer be considered evidence. Any committee member or WMF employee that finds a way of getting hold of this data after the 90 days, will (and should) fall foul of their contract, unless one of the parties has had the foresite and is rich enough to speedily subpoena the WMF for the information, and it succeeded rather than being ignored by the WMF or responded to with a deliberately partial or unhelpfully literal release against an imprecise subpoena. This scenario would be an easy way to introduce doubt and lead to "assuming good faith" in the absence of critical evidence, especially were a WMF employee, wealthy partner organization, or an employee for an organization that a WMF board member has an interest in, were somehow embarrassingly involved in anonymous/pseudonymous harassment (or potentially a harassed party).
 * Perhaps you prefer to believe that such cold strategic ways of handling harassment have never happened within the WMF, but you have neither experienced the WMF for quite as long as I have, nor are a lawyer on a six figure salary who makes these choices, directed to robustly defend the WMF from all risks without worrying what happens to non-WMF parties who do not pay your fees. --Fæ (talk) 13:03, 9 June 2016 (UTC)


 * Whether WMF HR/Legal can intervene in cases is an important question, but it has no bearing on how the committee is chosen. Do you expect HR/Legal to somehow influence the choice of members on the committee through Andre/Rachel/Quim? Valhallasw (talk) 12:25, 11 June 2016 (UTC)
 * I thought about not responding as this seems weirdly obvious. However to avoid doubt - a key function of HR and Legal, is to ensure that employment contracts and policies guarantee that the WMF avoids exposure to risk, including reputational risk, and to ensure that employees comply with the policies those departments dictate. So yes, they "somehow influence" all employees and their contracts fully ensure compliance, especially when there is conflict. --Fæ (talk) 17:26, 12 June 2016 (UTC)
 * Fæ, I don't see how the WMF could drop, suppress, or veto cases, suppress factual evidence, and/or pursue Committee members... and get away with it without a whistleblowing from Committee members, reporters, witnesses, or any other community members related to the people involved in a case. But for the sake of exploring pros and cons of the different models proposed to select the first Committee, even if that would be possible, why do you think that such horrible scenarios would be possible with a committee selected in a managed and publicly reviewed process but not with a committee voted in a direct election?--Qgil-WMF (talk) 19:27, 12 June 2016 (UTC)
 * The WMF concept of whistleblowing only applies when the law is being broken and it only applies to employees. In any other circumstances, neither employees nor volunteers that signed a contract with the WMF have any protection from whatever senior management feel are actions needed to remove them from public or private discussion in order to eliminate a perceived risk.
 * I find this repeated challenge from yourself odd. In particular I have already explained the "how". It seems extremely obvious that a committee where a handful of unelected WMF employees can secretly black-ball anyone with views that they or the wider WMF may not like for unspecified reasons, such as someone like me that no doubt is seen as "undesirable" by WMF legal for blowing the whistle in public about the ethics of a trustee which resulted in a resignation after press attention, then there is no chance that the committee will represent anything but pro-WMF and pro-status-quo viewpoints.
 * By the way, my presumption is that you are using paid employee time to keep on asking questions and finding reasons to avoid making this CoC more volunteer-centric. Keep in mind that I'm not.
 * P.S. for the third time of asking, could you please demonstrate that you trust in having a joint consensus with volunteers and WMF employees by publishing the paid consultants advice about this CoC that WMF employees have been privileged to read, but volunteers like myself have not. It is a poor precedent in a discussion where transparency and ethics have become key points of contention. Thanks --Fæ (talk) 00:25, 13 June 2016 (UTC)


 * The main question is how to form a functional committee. I agree with Qgil that direct elections (i.e. the five people with the most votes form the committee) is not necessarily the best way to do so, for the reasons he and Anomie outlined above. However, a complete lack of community oversight is also not something that appeals to me -- see the earlier discussion on Talk:Code_of_Conduct/Draft/Archive_2.
 * I think a reasonable compromise could be to vote on a committee rather than on members: the technical collaboration team would build a proposed committee, and the community can then vote on whether that group becomes the committee. If others would be interested, they could formulate a counter-proposal, which would be voted on in the same way. Valhallasw (talk) 11:55, 8 June 2016 (UTC)
 * Would that vote be for the initial committee only, or would a vote be needed every time the committee wants to change its membership? Anomie (talk) 13:05, 8 June 2016 (UTC)
 * Code_of_Conduct/Draft defines a review period of two weeks for the community. Following the draft, if one or more proposed Committee members are considered problematic by one or many community members, people can send us their feedback and we will have to react on the specific complaints. In contrast, a vote would bring a Yes (all Committee candidates are confirmed) or a No (all Committee members must be changed?) and no indication about reasonings or hints for a better selection. Those details would need to come from feedback anyway, so why not focus on the feedback in the first place.
 * In fact, valid concerns about a Committee member could be overridden by a majority vote that would need to be accepted regardless. In a managed process, one email with valid concerns could be more effective, and if our reaction to feedback is not good enough, we are clearly accountable, and the likely outcomes is an escalation to community protests and lack of credibility of the Committee and the CoC before its inauguration.
 * Even from a purely logistical point of view, it is not clear at all how such vote would be organized. How are requirements for participation and identification of voters considered in a community spread across several tools and spaces with no single unified login?
 * I think it is simpler to trust a group of individuals (Andre, Rachel, Quim or another set of people) to facilitate this process, be ready to change initial candidates as a response to sensible feedback, and understand that an incompetent or unfair Committee will not have much chances to survive anyway. Note also that the most likely problem we will encounter is not which candidates to choose, but finding people willing to volunteer for this delicate role at all.--Qgil-WMF (talk) 12:58, 9 June 2016 (UTC)
 * You are replacing an open vote with your unelected network of WMF employee friends. Regardless of how many times you explain that you are nice and unbiased, you have to understand how terrible that looks to non-WMF insiders.
 * To draw a parallel fantasy scenario, if Jimmy Wales were to pick three of his close personal friends and insist that this unelected group have the final say in choosing who could be the next WMF board of trustees (i.e. a "managed" process), or control how the $100m Wikimedia Endowment fund could be used, because they were jolly nice and ethical people he trusts, do you think that would work out well, and that the community of unpaid volunteers that give their time to create project content would feel this was the best ethical approach and delivered good governance? --Fæ (talk) 23:14, 9 June 2016 (UTC)
 * Wouldn't it be more like if Jimmy Wales had picked three of his close personal friends to decide who would be the first WMF board of trustees back in 2003? Anomie (talk) 14:34, 10 June 2016 (UTC)
 * Only if Jimmy's three friends were still picking and choosing who could be a trustee in 2016. The effective veto by unelected WMF employees does not vanish after the first round. --Fæ (talk) 17:27, 12 June 2016 (UTC)
 * Where do you see language that says the WMF can veto candidates after the first committee is appointed? Anomie (talk) 13:23, 13 June 2016 (UTC)
 * It does not state that, the committee relies on a "majority vote", though it's not actually clear who is doing the voting, nor does it explain what the 'slate' is (presumably a public list). It reads as though the previous committee is voting on the next one, which presumably is not how this will work, but it's hard to interpret it. There is also no provision for public comment, the only option is private email, which seems unnecessary if there is to be any community engagement on-wiki, rather that it all happening off-wiki. The selection section is a minefield of what it does not state, rather than what it does. --Fæ (talk) 21:32, 13 June 2016 (UTC)
 * I think you're presuming a bit too much, as written it seems that the old committee voting on the new committee is exactly how it's intended to work. I suspect that only providing for private comments is intended to avoid it feeling like members have to go through a gauntlet of criticism (like enwiki's RfA process), never mind that people will likely comment publicly on the post's talk page anyway, but you'd have to ask Qgil or whoever drafted that bit to really know. And, as you were so fond of saying earlier, start a new section if you want to discuss that. Anomie (talk) 14:25, 14 June 2016 (UTC)
 * I was unsure as it's a weirdly cliquey system to apply. After a couple of iterations it would become old committee members appointing people they happen to know, or be existing friends with. Certainly as there is no criteria set down, and no requirement to do anything publicly, or even answer questions about the process, then I don't see how one could expect it not to be challenged due to perceived bias or cronyism. I fail to understand why anyone would want a committee selection process like that in preference to an open vote, even if it were geared by changeable or arbitrary eligibility criteria. --Fæ (talk) 16:02, 14 June 2016 (UTC)
 * There are basic criteria in the Code of Conduct/Draft. I expect as the Committee continues, they will develop more criteria on how to choose members.  The candidate slate will be published on-wiki.  Given that people have taken time to answer your questions here, I can't understand why you think people won't answer legitimate questions.  The text has a clear process (techconductcandidates@wikimedia.org, etc.) to ensure people don't only think of candidates they know.  Selection of the members is not the kind of process that is conducive to a vote.  This is about skills that are difficult to assess based on how well known a person is, or what they have done technically.  Anomie is correct about the reason I proposed this process.  People are likely to comment informally wherever they want (the Code of Conduct applies, though).  They should not expect Technical Collaboration or Committees to engage in blow-by-blow public debate on each candidate, though.  If people have concerns, they should make them known via the email address.  Mattflaschen-WMF (talk) 23:51, 14 June 2016 (UTC)
 * I think these aspects are mostly clear, and show there is no WMF veto of candidates chosen by the Committee: "Subsequent members of the Committee will be chosen by the current Committee.", "the Committee elects their new members by a majority vote every six months". I have clarified 'slate', one of the issues you raised above. If you find the text unclear, suggestions on how to clarify it are welcome. Mattflaschen-WMF (talk) 23:51, 14 June 2016 (UTC)


 * I'm not entirely sure what the best course of action would be in the case where one member of the committee changes. I'm inclined to suggest voting on the entire committee again (because the question is whether the new committee as a whole is a suitable committee).
 * "In contrast, a vote would bring a Yes (all Committee candidates are confirmed) or a No (all Committee members must be changed?) and no indication about reasonings or hints for a better selection. Those details would need to come from feedback anyway, so why not focus on the feedback in the first place." -- I don't understand why this would be an either/or situation. I'm envisioning a system where there first is a feedback round, then a full committee is proposed, and the full committee is voted on.
 * The question of 'who is allowed to vote' is a valid one, but one we already have to answer when it comes to voting on the CoC itself (and when it comes to voting on changes to the CoC)
 * Valhallasw (talk) 12:33, 11 June 2016 (UTC)

Referrals to second, separate group?
The current draft includes:


 * At the Committee's discretion, it can also delegate complex issues to the Wikimedia Foundation's Technical Collaboration team, transferring the responsibility of their resolution.

Introduced in this edit after this discussion.

I'm not sure the previous discussion reached consensus for the inclusion of this provision. --MZMcBride (talk) 23:47, 5 June 2016 (UTC)


 * I left this comment after adding that sentence, which didn't receive any response. As far as I remember this topic has been mentioned a couple of times but this is the first time that it has been highlighted for discussion. If someone wants to challenge the current text, I think the relevant questions are:
 * Do you agree or disagree that a Committee assumed to be formed mainly by volunteer should be able to delegate especially complex cases to a second body?
 * If you agree, do you have a proposal alternative to this team?
 * Note that is also related to the process for appeals. Do you think there should be a second body for appeals, and if so, who should that be?--Qgil-WMF (talk) 09:55, 6 June 2016 (UTC)


 * Disagree. The Committee must be ultimately responsible if this is to mean anything. If the committee needs to pull in experts or independent reviewers then it can do so. If you can think of scenarios where this becomes (legally) impossible, then set out those scenarios explicitly so we can discuss whether it makes any sense for the WMF to be a default rather the the police or the victim's/alleged harasser's lawyers. The rest of this is a tangent, if you want to discuss appeals then create another section. --Fæ (talk) 21:11, 6 June 2016 (UTC)

Following on Fæ's comment above, I agree that we can remove the escalation path to Technical Collaboration and leave all resolutions to the Committee, allowing them to seek additional support if they need it. The Committee is being defined in this CoC as a body to be trusted and to be given flexibility to make good decisions. Therefore, I propose these changes to the draft:

--Qgil-WMF (talk) 20:14, 7 June 2016 (UTC)
 * "Complex cases may require the Committee to investigate within the margins of confidentiality, eventually contacting any individuals involved and/or related administrators or project maintainers. They may also request support from experts and reviewers external to the Committee and unrelated to the case."
 * " In case of very complicated or urgent matters, or if the Committee is unable to reach consensus, the report can be transferred to the Wikimedia Foundation Technical Collaboration team. "
 * " At the Committee's discretion, it can also delegate complex issues to the Wikimedia Foundation's Technical Collaboration team, transferring the responsibility of their resolution. "


 * Sounds good.
 * Valhallasw (talk) 12:34, 11 June 2016 (UTC)
 * I support Qgil-WMF's proposal. However, I disagree with MZMcBride's characterization of the draft process.  The process we've basically been following is:
 * Someone adds text they think is a good idea.
 * It either stays or it is reverted.
 * If someone reverts it, or thinks it should be reverted, they should explain why and preferably suggest an alternative solution.
 * This is resolved through (sometimes quite extensive) discussion and text changes as appropriate.
 * The text of the section is approved later by a consensus discussion.
 * All the text is being approved section-by-section. However, implying it has to be approved by consensus before even going in the draft is wrong and gets the ordering backwards (until the text of that section is approved, it's just a draft).  Furthermore, discussions like this which say, "I'm not sure the previous discussion reached consensus", without even touching the merits (there is nothing in the OP of this section about whether the quoted text is a good or bad idea) are not as constructive as they could be.  Wikipedia:Don't revert due solely to "no consensus" is just an essay (and even if it was a policy it wouldn't apply here), but it essentially explains what I mean. Mattflaschen-WMF (talk) 16:07, 14 June 2016 (UTC)

✅ There is consensus about this change.--Qgil-WMF (talk) 20:06, 14 June 2016 (UTC)
 * There's still a few references to 'appeals body'. -- Krenair (talk &bull; contribs) 01:48, 15 June 2016 (UTC)
 * I mentioned above that this change was somewhat related to the process for appealing a resolution. Fæ suggested not to mix both topics and encouraged to create a new section if anyone wanted to discuss appeals. Appealing a resolution is part of the Cases page, and Matt just launched a call for feedback for that page. Therefore, if someone wants to propose changes to the appeals process, the time is now and the place is a new section.--Qgil-WMF (talk) 06:25, 15 June 2016 (UTC)
 * Yes, this change is not regarding the appeals process. Basically, the old text said that if the Committee didn't want to (or could not) make a decision, they could pass it to Technical Collaboration.  Now, the Committee can seek support/advice, but the Committee has to make a decision.  The appeals text is unchanged. Mattflaschen-WMF (talk) 18:14, 15 June 2016 (UTC)
 * Okay, maybe I misunderstood. -- Krenair (talk &bull; contribs) 19:09, 23 June 2016 (UTC)

How to announce the call for approval of the Cases page
In Wider participation, still we have discussed several ideas to increase the reach of CoC announcements through technical spaces. In this section we are organizing the announcement of the call for approval of the Cases page, expected to start as soon as the current call for feedback for the Cases page is settled, and points still requesting consensus (if any) have been identified.

Online spaces
 * MediaWiki.org: a sitenotice for logged-in users only is being discussed.
 * wikitech.wikimedia.org: we could just mirror what we decide for mw.o
 * Phabricator: the panel in the homepage should be updated.
 * Technical mailing lists: distributing a message to all the lists is a daunting task, but as a good enough approach we could
 * select the main mailing lists where we will post directly (latest list of lists is wikitech-l, engineering, design, wiki-research-l, analytics, hackathonorganizers, labs-l)
 * collect the email addresses of all the administrators of technical mailing lists and send them a common email with the information and a request to forward to their lists
 * Technical IRC channels, we could select a short list of popular and diverse channels and add a note in the channel topic. Should we do the same for all channels? The own users of the channels could decide when to remove those notices.

Physical spaces --Qgil-WMF (talk) 07:40, 15 June 2016 (UTC)
 * Code of Conduct session at Wikimania Hackathon 2016 on Thursday, 23 June, 13:00.
 * Video recording is a possibility, but availability of video equipment is still unclear.
 * I added labs-l, since that was in the most recent email. If people think we should have more lists, there are two possible approaches:
 * Email the list directly. It will go the moderation queue if I'm not subscribed, and the owner can decide whether to approve it.
 * Email list-l-owner@lists.wikimedia.org (varies by list) as suggested above.
 * I think the first will be more likely to actually get a message to the list, since they just need to approve, rather than draft something. For technical IRC channels, what about #mediawiki, #mediawiki-i18n, #wikimedia-tech, #wikimedia-dev, #wikimedia-labs, #wikimedia-design, #wikimedia-operations, and #wikimedia-releng?  Other people could add it to additional channels, but I think that covers the main areas. Mattflaschen-WMF (talk) 18:34, 15 June 2016 (UTC)

Removing the limitation of 3 months for appeals
After re-reading the Cases page, the only point that I found where an alternative was proposed but the discussion was not resolved is the limitation to appeal only after three months. I still believe that it is better to remove this limitation. If this flexibility is abused in practice, then we can think how to prevent such abuse, and propose a solution as an amendment of the CoC. The specific change proposed is to remove "Only resolutions (such as bans) that last 3 months or longer may be appealed by people who were sanctioned."--Qgil-WMF (talk) 09:21, 17 June 2016 (UTC)
 * I still don't think it's necessary that every low-level decision can be appealed to an entirely separate group. There is already a provision for re-consideration by the same Committee ("the reporter or any people sanctioned may raise objections to the resolution. [...]").  As a further compromise (since some people thought 3-month was too long a cut-off), I would support changing it to 1-month. Mattflaschen-WMF (talk) 20:10, 17 June 2016 (UTC)
 * OK to set a minimum filter, then. What about "Only resolutions (such as bans) that last 3 months or longer more than one week may be appealed by people who were sanctioned." Above in the draft there is a mention to asking someone to "take a week off" as a possible resolution. Looking at the type of cases reported in our technical spaces, that week off looks like a possible limit between minor incidents and grave ones. Most of the hot situations we seen in our technical spaces cool down within a week. Being banned in one channel during one week is bad in several ways, but it is not the end of the world. Due to "racing conditions", appeals to sanctions of one week or less would be probably resolved after the sanction has passed anyway. This proposal about "more than one week" would leave most appeals to longer sanctions (major problems) and also to reported offenders who have gone through their sanction but still want to defend their disagreement for the record and for similar situations in the future (smaller yet unsolved problems).--Qgil-WMF (talk) 09:11, 18 June 2016 (UTC)
 * I agree with this proposal, I also think there should be clarity about whether you have to wait for the whole amount of time for a sanction to expire before appealing or whether you can appeal as soon as it is active. I would also request clarity over whether things like permission removals (server access, +2, etc.) can be appealed and when. -- Krenair (talk &bull; contribs) 19:15, 23 June 2016 (UTC)
 * Actually, re-reading the text I suppose permission removals that are temporary for more than the time limit would be appealable and permanent ones would always be appealable? Am I understanding this correctly? -- Krenair (talk &bull; contribs) 19:16, 23 June 2016 (UTC)
 * Yes, any sanctions lasting more than the time limit could be appealed. I think the appeals could be submitted as soon as the sanction is enforced. I hope this doesn't raise an expectation that resolutions on appeals will be announced at the same speed. Appeals are expected to be based on complex situations, and forming a good judgement on them will require time.--Qgil-WMF (talk) 07:50, 24 June 2016 (UTC)
 * Yes, it's only based on the time period, not what the resolution is. Also, regarding, "whether you have to wait for the whole amount of time for a sanction to expire before appealing", they do not have to wait.  This is why it says, "Until an appeal is resolved, the prior resolution remains fully in effect.".  In other words, if someone is e.g. banned for a year, they can appeal, but they remain banned unless and until the appeal is resolved in their favor.  If they had to wait a year to appeal, that sentence would not make sense. Mattflaschen-WMF (talk) 19:02, 29 June 2016 (UTC)
 * I support the "one week" version as a compromise. Mattflaschen-WMF (talk) 20:39, 29 June 2016 (UTC)

Suggested change to "discrimination" item
In the current text, one of the examples listed of "Unacceptable behavior" is:

Discrimination (unless required by law), particularly against marginalized and otherwise underrepresented groups. Targeted outreach to such groups is allowed and encouraged.

I propose to change this to the following:

Discrimination, except when required by law, or for the purpose of outreach.

The initial wording was already voted on in March, but I think there are a few things that are clear now that weren't back then:
 * No one, apparently, has any idea what "marginalized and otherwise underrepresented groups" really means - that is, what the criteria are by which a particular group would be determined to be marginalized or underrepresented.
 * The current text sets up a strange dichotomy where all discrimination is either encouraged or banned.
 * Under the most straightforward reading of the current text, the Google Summer of Code and Outreachy would both be banned, since they both discriminate against non-college students. Unless one considers college students to be among the marginalized or underrepresented, this would be considered unacceptable outreach. (And if you think discrimination against non-students doesn't count as discrimination in the first place, imagine someone turning down a contributor's patch because the contributor is not in college. Would that be alright?) Yaron Koren (talk) 19:53, 28 June 2016 (UTC)

as proposer. Yaron Koren (talk) 19:54, 28 June 2016 (UTC)
 * Consensus not reached. There was not consensus to make the change. People cited both issues with the text change and procedural issues. Mattflaschen-WMF (talk) 03:17, 6 July 2016 (UTC)
 * Comment Marginalized group, Underrepresented_group, Group. Ok ok, I jest Yaron. Here's how I see it. Excluding a group of people by intent is unacceptable. That intent part is particularly vital. Google Summer of Code, in its stated goals and purpose, does not intentionally set out to exclude people as part of its efforts. An individual or group that purposefully singles out and attempts to prevent participation - they are discriminating. CKoerner (WMF) (talk) 20:15, 28 June 2016 (UTC)
 * I don't see how GSoC could be any more intentional in its discrimination... I'm guessing that by "intent" you really mean "malice". In either case, you seem to be reading something into the current wording that's just not there. Yaron Koren (talk) 21:04, 28 June 2016 (UTC)
 * And here we go again: Discrimination is deemed to be acceptable behaviour unless one is so abysmally dumb to admit to it. Just feigning ignorance allows one to happily continue on a path of exclusion.  --Tim&#160;Landscheidt 02:41, 29 June 2016 (UTC)
 * I note that the current draft doesn't actually mention intent. Anomie (talk) 13:56, 29 June 2016 (UTC)


 * The Unacceptable behavior section has gone through extensive review, and for the sake of progress in the completion of the draft, we have no intention to go back and reopen it. Your objection to "particularly against marginalized and otherwise underrepresented groups" was discussed even further, twice, also extensively, without agreement. The FAQ explains why we are mentioning explicitly these groups and why there is no risk of GSoC being considered by the Committee to be a discriminatory activity. As far as I recall, other hypothetical examples of abuse based on this sentence were refuted as well. The promoters of this CoC do not see a scenario where this sentence could be used unfairly against community members, or against the principles of the CoC. If reality proves that this sentence is problematic, or if new ideas are brought by the Committee or anyone else, they will be able to use the amendment process to change it.--Qgil-WMF (talk) 06:38, 29 June 2016 (UTC)
 * Your FAQ doesn't really say why GSoC wouldn't be considered discriminating against non-college-students, or why college students should be considered a marginalized or underrepresented group. It just says "GSoC itself is not a program promoting harassment and disrespect". Couldn't a FAQ equally well say that a hypothetical WMLiSFSoC "itself is not a program promoting harassment and disrespect"?
 * As for "without agreement", it seems that the disagreement in large part came from you personally. Perhaps the principle behind w:WP:INVOLVED should be applied here. Anomie (talk) 13:55, 29 June 2016 (UTC)
 * I remain unsure who "we" is in "we have no intention to go back and reopen it"; I presume this excludes me, and anyone that foolishly asks questions that Qgil does not like the look of.
 * This remains a can of worms. After my experience this week of having a project administrator actively using a free speech argument to defend the example usage of "retard" to describe other editors, I doubt that there is any common understanding of how discrimination will be understood by the wider Wikimedia community. As the process for this CoC does not ask them, the end result is likely to seem academic, compared to where we are as a community and what is routinely accepted and argued to be acceptable. --Fæ (talk) 16:13, 29 June 2016 (UTC)
 * This section has been completed, this specific text has been discussed quite throughly, and this would not improve the text. The emphasis in the original regarding "marginalized and otherwise underrepresented groups" is intentional.  We don't want to exclude anyone (see the Principles section), and we realize that outreach to underrepresented groups (like Outreachy) is necessary to expand the community.  Your proposed change takes away the point that we don't need to do outreach to every possible group. The text "marginalized and otherwise underrepresented groups" uses the plain meaning, just as e.g. "private communication" does.  People have explained the meaning in great detail, and neither phrase needs an inline definition.  I already explained why GSOC is not discriminatory.  The reason why Outreachy does not violate this clause is self-explanatory (it is an outreach program specifically targetting under-represented groups).
 * I further note that you have started this section without notifying the mailing lists as I always do, so I had to do that. Mattflaschen-WMF (talk) 18:21, 29 June 2016 (UTC)
 * When did anyone explain the meaning in great detail? Yaron Koren (talk) 02:46, 30 June 2016 (UTC)
 * This sentence (and its precursor sentences) have been discussed and explained repeatedly, down to specific individual examples: Here, etc., etc.. Mattflaschen-WMF (talk) 08:08, 1 July 2016 (UTC)
 * I think only the first of those is relevant, as far as defining "marginalized and/or underrepresented". Neil Quinn wrote that, in order for a group to be considered marginalized/underrepresented, evidence has to be provided that the group faces "systematic barriers to entering similar groups [to the WMF], like open-source software projects, free-culture movements, or San Francisco-based tech companies." So is that the answer? Yaron Koren (talk) 14:02, 1 July 2016 (UTC)
 * The text of the CoC is the controlling text. I think Neil gave a very reasonable explanation of that text, particularly regarding 'marginalized'. Mattflaschen-WMF (talk) 01:59, 6 July 2016 (UTC)
 * In other words, his explanation was reasonable but useless, since there's nothing official or binding about it? Okay... I don't know why you brought it up, then. Yaron Koren (talk) 04:10, 6 July 2016 (UTC)
 * Also, your characterization of Outreachy is incorrect. "Unlike Google Summer of Code, Outreachy is open to non-students and non-coders, so you should just apply for Outreachy internship if you are either not a student or not a coder." Mattflaschen-WMF (talk) 03:33, 6 July 2016 (UTC)
 * Ah, I didn't know that. Yaron Koren (talk) 04:11, 6 July 2016 (UTC)
 * I think it's useful to keep the particular intentions of the wording as-is. The proposed change makes this text less grounded in the problems we're trying to address. Milimetric (WMF) (talk) 18:52, 29 June 2016 (UTC)
 * comment I find Yaron's argument mildly more compelling, but honestly I have trouble caring either way. Bawolff (talk) 19:03, 29 June 2016 (UTC)
 * Comment The problematic part here seems to be that the outreach clause is limited to "marginalized and otherwise underrepresented groups", which implicitly disallows all other kinds of targeted outreach. That doesn't seem to be anyone's actual intent here. What if we just remove the limiting clause from the current wording? "Discrimination (unless required by law), particularly against marginalized and otherwise underrepresented groups. Targeted outreach to such groups is allowed and encouraged." Anomie (talk) 19:57, 29 June 2016 (UTC)
 * This was discussed before, at length. The original sentence was changed based on the discussion that ensued, and consensus was reached. "We" are the people working on this document - who reached consensus. After lengthy conversation, adjustments, and discussions, the text was approved by clear consensus. While there was some opposition, there was clearly more support, and so it was approved. There is no requirement that it be unanimous, and that is not a realistic expectation in this case.
 * This isn't a matter of misunderstanding, or a matter of "top-down" decision, and anyone reading the previous discussions can see that. In fact, the text was adjusted from the 'original' version following the lengthy discussion, so it's not like opposing voices were ignored.
 * Waiting a while after consensus was reached to challenge this section as if there was no "true" consensus, as if there were no true deliberations or considerations for the points you are (again) making is unfair at best, and disruptive at worst. It did not take us 5 minutes of casual dismissal 'why not' to accept this text. It took months to approve the "Unacceptable behavior" section, and quite a large portion of time dedicated to the "marginalized" text itself.
 * I see absolutely no reason to reopen an issue that was agreed upon by consensus, so we can entertain the few who have repetitively expressed their opposition, when consensus has been clearly against them. MSchottlender-WMF (talk) 20:10, 29 June 2016 (UTC)
 * Well, a lot of the "support" votes seemed to come from people who hadn't thought through the wording - like the people who didn't believe that, under the current wording, every kind of outreach was either banned or encouraged, with no middle ground. I thought that, with clarification of the problems, some people might change their minds, but evidently that's not the case. Yaron Koren (talk) 02:46, 30 June 2016 (UTC)
 * AGomez (WMF) (talk) 20:33, 29 June 2016 (UTC)
 * The discussion was opened and closed before. This also very much feels like unnecessary nitpicking in order to make the decision process harder. It can be amended if it proves to be unrealistic. (Which it isn't in my eyes.) Frimelle (talk) 20:42, 29 June 2016 (UTC)
 * I guess you're not assuming good faith! Oh well. Yaron Koren (talk) 02:46, 30 June 2016 (UTC)
 * The proposed text appears to define targeted outreach as discrimination. Gamaliel (talk) 20:51, 29 June 2016 (UTC)
 * It is discriminatory, by definition - otherwise it wouldn't be "targeted". Yaron Koren (talk) 02:46, 30 June 2016 (UTC)
 * Aaron (talk) 22:17, 29 June 2016 (UTC)
 * I think the existing wording, while not perfect, gives a clearer idea of the intent of the guideline. Kaldari (talk) 14:01, 30 June 2016 (UTC)
 * What do you see as the weaknesses of the current wording? Maybe there's some room for compromise? Yaron Koren (talk) 15:00, 30 June 2016 (UTC)

Is targeted outreach to non-underrepresented groups allowed?
I'm extracting this sub-thread because it seems the only one where there is some chance of having a productive discussion. The current wording implies that targeted outreach is discrimination and as such forbidden, except when it is aimed at underrepresented groups. (cf. the cooperative principle - when the speaker says "Targeted outreach to such groups is allowed and encouraged", the listener will rightfully expect that "to such groups" is included in the sentence because it is relevant, ie. leaving it off would make the sentence false). This is clearly nonsense - GSoC is targeted outreach aimed at a non-underrepresented group and everyone is supportive of it, to the extent that it has been even added to the FAQ (although the FAQ answer is a prime example of a straw man fallacy). Anomie's suggestion is the minimal required change to fix this - is there any reason to oppose that? --Tgr (WMF) (talk) 23:02, 30 June 2016 (UTC)
 * Consensus not reached. There was not consensus to make the change.  Again (see above), people cited both the text and procedural reasons. Mattflaschen-WMF (talk) 02:36, 12 July 2016 (UTC)


 * Natural language is more ambiguous than computer language and at least to me the current wording doesn't imply that "targeted outreach is discrimination and as such forbidden, except when it is aimed at underrepresented groups". However, if the small change proposed by Anomie (which doesn't bring any change to the intended meaning) makes the sentence clearer and we can finally settle this point, then I support the change:


 * "Discrimination (unless required by law), particularly against marginalized and otherwise underrepresented groups. Targeted outreach to such groups is allowed and encouraged."
 * --Qgil-WMF (talk) 06:17, 1 July 2016 (UTC)
 * I've specifically referred to a concept of philosophy of natural language in my somewhat desperate attempt to argue for something that I find obvious, so I don't think making rhetorical points about computer language is helpful. (Another, probably easier to read Wikipedia article on the same topic is implicature.) A last try: consider the sentence "Students must wear appropriate attire at all times. Skirts longer than three inches above the knee are acceptable." which has a similar structure. On a computer language level, this doesn't say whether shorter skirts are acceptable or not, but an actual human would assume that it's being implied that they aren't. This is because of the cooperative principle: listeners expect that the talker is cooperating with them to get the meaning across, by only saying things that are relevant. When that relevance is not spelled out, the listener is left to figure out how "Targeted outreach to such groups is allowed and encouraged" is relevant to discrimination being forbidden, and the obvious assumption is that targeted outreach to such groups is the only thing that's allowed and encouraged.
 * In any case, I hope that even if the phrasing would only imply to some readers that GSoC-like outreach efforts are forbidden and would not imply anything of that sort to some others, that would still not be considered a good outcome. Several people have pointed out above that they find the phrasing confusing; I would hope that the suspicion of only "nitpicking in order to make the decision process harder" does not extend to all of us.
 * Sure, leaving the text as it is won't cause any outreach programs to be rejected; a reasonable committee will ignore errors in the CoC (and if we end up with an unreasonable committee, we'll have bigger problems). It alienates people though when it's impossible to get obvious and easily fixable problems fixed (I note that this same problem was raised and ignored multiple times well before the section in question had been finalized); and it detracts from the authority of the CoC when it has to be contradicted by its own FAQ. --Tgr (WMF) (talk) 11:45, 1 July 2016 (UTC)
 * I don't think it would actually require an unreasonable committee, just one that was unwilling to ignore the plain meaning of the CoC. It reminds me of requiring . Anomie (talk) 13:45, 1 July 2016 (UTC)
 * As I explained above, GSOC does not discriminate. Therefore, they do not need any kind of "allowed and encouraged" clarification or exemption. Mattflaschen-WMF (talk) 00:37, 6 July 2016 (UTC)
 * I agree with your point about the cooperative principle, and your interpretation of the text. As I said, the emphasis is intentional, and that it does mean that discriminatory targeted outreach exclusively designed to increase participation of over-represented and non-marginalized groups is forbidden. Mattflaschen-WMF (talk) 01:30, 6 July 2016 (UTC)
 * See my comment above. This section is finalized and the emphasis in the current sentence is intentional. Mattflaschen-WMF (talk) 08:22, 1 July 2016 (UTC)
 * I'm ok with your strong oppose, for the same reasons explained in my previous comment. Moving on with the draft is more important than getting stuck with details on sections reviewed. I don't think the current sentence is problematic in practical terms. I don't think the current sentence will change a bit the participation of Wikimedia in outreach programs.--Qgil-WMF (talk) 08:45, 1 July 2016 (UTC)
 * I understand the wish to finally get this thing done and into force, and I acknowledge that I'm the chicken here and Matt is the pig (for whom reestablishing consensus on a new phrasing is surely a significant amount of work, and possibly a precedent for having to reopen discussions on other parts). Maybe we could consider all discussion about already finalized sections as part of the amendment process, to be approved or rejected three months after the CoC is enacted?
 * Yes. Addressing nice-to-have but non-blocking issues (particularly in finalized sections) in the amendment process makes perfect sense.  Personally, I do not support these two proposals, but I could support a better proposal on this topic made at the proper time.  Similarly, if unforeseen serious issues arise, they can and will be addressed by the amendment process. Mattflaschen-WMF (talk) 01:30, 6 July 2016 (UTC)
 * As for the emphasis being intentional, it seems the current text fails to communicate that intention clearly. If the intention is to say that outreach is generally OK but outreach to underrepresented groups is especially great, then a better phrasing would be "Discrimination (unless required by law), particularly against marginalized and otherwise underrepresented groups. Targeted outreach to such groups is allowed and encouraged."
 * Otherwise, I hope someone can explain what the intention is. --Tgr (WMF) (talk) 11:45, 1 July 2016 (UTC)
 * The repeated attempts at discussion of this issue show that your intentional emphasis on marginalized and underrepresented groups is not having the desired result in communicating the intended meaning of the statement as a whole. Tgr has done an excellent job in explaining exactly why it's failing. I'm going to be blunt here: "this has already been finalized" is a horrible reason for opposing fixing a clearly identified problem and is exactly the sort of thing that gives ammunition to those who attempt to assert that the WMF is trying to force things through without considering any other viewpoints. Anomie (talk) 13:45, 1 July 2016 (UTC)
 * I disagree. I think people agree on the meaning of the sentence.  As Tgr said, "the obvious assumption is that targeted outreach to such groups is the only thing that's allowed and encouraged."  I agree and that is how I think people generally interpret it.  If there were a serious problem, I would support re-opening the section to fix it.  There is no problem.  We agree on what the text means, and I support that meaning.  Anyone who says, "the WMF is trying to force things through without considering any other viewpoints." is 100% wrong.  People have worked on this text carefully and patiently.   The original version of this text was "Discrimination against marginalized and otherwise underrepresented groups".  That triggered a vigorous discussion, and you can see how the text has changed since then.  There was no attempt to ram through the original text.  Instead, people addressed the issues (thanks to suggestions from Neil and others), and the new compromise text was approved by consensus.  People are trying to change the text again, but:
 * The current text already is the compromise text.
 * There is no additional problem with this bullet point that needs to be solved before the CoC is approved.
 * Mattflaschen-WMF (talk) 01:50, 6 July 2016 (UTC)
 * If you really think people all agree with your reading of the sentence, then I don't think there's a point in my continuing to respond to you here since it seems that you're only seeing what you want to see. Anomie (talk) 03:06, 6 July 2016 (UTC)


 * - we're now in the unusual position where the two main movers behind this CoC, Qgil and Mattflaschen, disagree completely about the meaning of these words (Qgil thinks all targeted outreach would be allowed, Mattflaschen thinks much of it would be banned), but they both agree that the wording is great as it is. It appears to me now that this ambiguity has become a feature, not a bug: given that the meaning is not spelled out, Qgil, Mattflaschen and other supporters of the current wording can interpret the text either way, and thus avoid a potentially painful argument about targeted outreach. What I think they're missing is that not dealing with it now just means that the argument will get postponed to the future, when the stakes will be a lot higher. That doesn't seem fair to anyone. Yaron Koren (talk) 16:42, 1 July 2016 (UTC)
 * What doesn't seem fair to me is to keep reopening a discussion. Talk:Code_of_Conduct/Draft/Archive_2 shows that the initial proposal (from Matt) already went to several iterations until it got several Support, two Oppose from Yaron and Tgr (who keep opposing) and one Meh from Anomie (who keeps trying to find a better point of consensus, thank you). Yaron's proposal above got several Oppose, confirming a general will to keep that sentence in the draft as is. Please let continue the discussion about the draft, let the CoC and the Committee be created, and then, if you think this sentence is still problematic, propose and amendment when the first window for amendments opens. If you share the goal of having a CoC approved and enforced, this shouldn't be a plan too difficult to agree to.--Qgil-WMF (talk) 16:53, 1 July 2016 (UTC)
 * I don't know what you mean by "keep reopening" - it's only been reopened once. It's also strange that you're so against this three-word removal, given that less than 24 hours ago you thought it was a good idea. Yaron Koren (talk) 17:23, 1 July 2016 (UTC)
 * Here's the problem here the way I see it: This isn't so much an issue of compromising over new text, as it is an issue of bypassing the proper process and silencing people who participated before. In previous discussions, we went over (quite at length) almost every bit of this sentence. The original text was different, in fact, and while we were discussing the new text, compromises already happened. That is, there were (roughly) two sides for this argument of clarity and "forcefulness" of the emphasis of marginalized groups - a side that wanted to go even more clearly and make the text stronger, and a side that wanted to de-emphasize and reduce the focus on marginalized groups. There were valid, lengthy, and very comprehensive discussions that lead to a compromise on the text. Both sides seemed to consider the new version not ideal, because both sides compromised.
 * What we seem to be doing now is reopening this discussion and discussing how to push this text towards one of the argument-sides that originally participated in the compromise. Doing that means we are essentially overriding the voices who participated in the previous discussion, who wanted the compromise to go the other way.
 * This is why this discussion should close now. Not because of the claims themselves (which, again, we've gone through), not because the text is perfect as-is, not because there may be room for improvement. All of these may be true -- but the process of consensus (that is not new to RFCs and to policy in Wikimedia projects) has run the course to produce a compromise that resulted in consensus. Reopening this now and arguing to push this further into one side of the view on this is not compromising. It's taking advantage of time passed and good rhetoric to override the voices who wanted this text stronger, who argued for weeks on this, and who may not be participating anymore because they consider the text closed and done for this draft, by proper consensus.
 * This is an outrageous act of bypassing consensus, and bypassing the process that we have had for an entire year over this document. MSchottlender-WMF (talk) 19:37, 2 July 2016 (UTC)
 * I certainly understand your objections, but I think you're overstating the case. It hasn't been a year in this case - the anti-discrimination stuff was introduced in February, the current wording was introduced in March, and the vote happened a few weeks after that. And the potential conflict with GSoC (and Outreachy, but that's a trickier one) wasn't brought up until June, after the vote. I also don't think the discussion was all that comprehensive - besides the GSoC thing, there's the even more basic fact that no one seems to know for sure whether the current wording would ban some forms of outreach. (I'm curious to hear your opinion on that, by the way.) More generally, you make it sound like the discussion was a clear pro/con debate on the issues, but I remember it being a lot more scattershot than that - various objections and attempts at clarification being brought up, followed by a vote full of gauzy sentiments like the "need to serve all of humanity". I have no way to know if most of the people voting even read the previous discussion - most of them certainly weren't involved in it.
 * On a more basic level: you seem to agree that the current wording is not perfect - actually, there seems to be surprising unanimity about that. What sort of amendment process would you support, that *didn't* silence the voices of those who have already voted for this? Yaron Koren (talk) 13:26, 3 July 2016 (UTC)
 * Regarding "And the potential conflict with GSoC (and Outreachy, but that's a trickier one) wasn't brought up until June, after the vote.", that is not correct. The point about Outreachy was brought up by Neil in February, and we solved it completely through the new wording. There is no conflict with GSOC, as I've explained already. Mattflaschen-WMF (talk) 02:19, 6 July 2016 (UTC)
 * No, he was talking about Outreachy's discrimination against men, not GSoC's discrimination against non-college students. Yaron Koren (talk) 03:58, 6 July 2016 (UTC)


 * A compromise suggests that groups agree on one meaning. In this case, it seems that, although multiple groups agree on the text, they don't agree on the meaning. That's not a compromise, that's miscommunication. Valhallasw (talk) 14:57, 3 July 2016 (UTC)
 * To clarify, I believe there is a general agreement on what 'Discrimination (unless required by law), particularly against marginalized and otherwise underrepresented groups.', means, but I don't believe this is the case for 'Targeted outreach to such groups is allowed and encouraged.'. While the former was indeed discussed in length, with a compromise reached, this is not the case for the latter sentence. Valhallasw (talk) 15:13, 3 July 2016 (UTC)
 * , to clarify my position. I agree with the meaning that Matt has specified. Targeted outreach to marginalized and otherwise underrepresented groups is allowed and encouraged. GSoC and Outreachy both fit here. Targeted outreach to the opposite would be totally out of place (imagine a MediaWiki workshop at the WMF offices where only white males could participate, or a Wikimedia Hackathon in Jerusalem for Jews only). Then we have events where the target is defined by the location: a hackathon in the Roorkee University campus will probably be filled with Roorkee University members because non-members require a permission to access, a meetup in Ramallah will probably have no Israeli participants because they require a special permission to visit that city. These are restrictions imposed by the location, and what matters is that the organizers are open to accept requests from other audiences as long as they have a possibility to attend.
 * As you can see, I am using real examples to show that the current text works. Something I have been missing in this entire discussion are more real(istic) examples based on past or current activities, in Wikimedia or elsewhere. Every time a realistic scenario was mentioned (i.e. a hackathon in a boys-only school) we didn't have any difficulty deducing whether such activity would be affected or not by this CoC.--Qgil-WMF (talk) 06:47, 6 July 2016 (UTC)
 * Your examples show that you do not understand what discrimination means. When Wikimania was held in Alexandria, so-called homosexual potential attendees were assured that they were welcome, yet if they were arrested in Egypt and sentenced to several years in prison, well, bad luck.  This is discrimination by proxy, and just because it is more PR-friendly does not mean it is right.  --Tim&#160;Landscheidt 09:11, 6 July 2016 (UTC)
 * I think I do understand discrimination, but I don't understand how your comment applies specifically to the CoC draft.--Qgil-WMF (talk) 10:10, 6 July 2016 (UTC)
 * just to clarify, are you now saying that GSoC targets marginalized and otherwise underrepresented group(s)? Yaron Koren (talk) 13:56, 6 July 2016 (UTC)
 * GSOC does not discriminate to begin with (as I've explained elsewhere). Thus, it doesn't need an exemption from the discrimination clause, and the answer to your question is irrelevant. Mattflaschen-WMF (talk) 02:12, 12 July 2016 (UTC)
 * I thought your explanation was (no offense) weak logically - you said that it's not discriminatory because Google is simply "hiring college students", but there's no obvious reason why it should be only college students who are getting hired. (To be fair, your explanation is still stronger than the one Qgil put forth in the FAQ.) In any case, I'd still like to hear Qgil's answer to my question - since, in this thread, he seems to offer a third explanation altogether. (The justifications keep changing, but somehow the prescription remains the same.) Yaron Koren (talk) 02:37, 12 July 2016 (UTC)
 * In other words, I'm allowed to organise a meeting at a coffee shop on the Roorkee campus, but I'm not allowed to organise a meeting at a coffee shop off-campus while only allowing Roorkee students to attend? Valhallasw (talk) 08:25, 6 July 2016 (UTC)
 * Why would you do that? If someone else would show up at the coffee shop saying "I'm a Python ninja and I love Wikipedia, can I join?", would you tell them "Well, let's see, can you show me your Roorkee university student pass, please?".--Qgil-WMF (talk) 08:29, 6 July 2016 (UTC)
 * Yet that is exactly what happens when you organise a meeting on-campus. Except it wouldn't be the organiser doing it, but campus security. Valhallasw (talk) 08:33, 6 July 2016 (UTC)
 * MMm... you lost me. What is your desired scenario here and why the current draft would be a problem for it?--Qgil-WMF (talk) 10:02, 6 July 2016 (UTC)
 * I think what it comes down to is this: If someone does organize a meeting at an off-campus coffee shop for Roorkee students only (checking ID cards or whatever), despite it being a strange thing to do, do you believe that would be allowed by the code of conduct or prohibited? Assuming your answer is "prohibited", Valhallasw asks why it's prohibited in that situation but it's not prohibited if the identical restriction is instead implemented by holding the event in a location where an external party (in this example, Roorkee university campus security) restricts access to students only.
 * I have a different question, again assuming your answer is "prohibited": given that you now support Matt's position and Matt's reasoning for how GSoC is not discriminatory is because anyone could theoretically enroll in a college, never mind lack of time, funds, or academic ability, why would restricting an off-campus event to only Roorkee students be discriminatory when anyone could theoretically enroll in Roorkee university if they wanted to attend? Anomie (talk) 14:04, 6 July 2016 (UTC)

Finalize "Cases" section?
Should the "Cases" section (current version) be considered done? Mattflaschen-WMF (talk) 02:52, 12 July 2016 (UTC)
 * As NKohli (WMF) said, this is about "Page: Code of Conduct/Cases", which is made up of "Handling reports", "Responses and resolutions", and "Appealing a resolution". Mattflaschen-WMF (talk) 05:39, 18 July 2016 (UTC)
 * Consensus reached. There was clear consensus to adopt this text.  Mattflaschen-WMF (talk) 21:07, 26 July 2016 (UTC)


 * as proposer. This is a practical, well-documented process, and we came to a compromise on appeals. Mattflaschen-WMF (talk) 02:52, 12 July 2016 (UTC)
 * : I remain unconvinced that expanding the "Arbitration Committee" model is prudent. --MZMcBride (talk) 03:06, 12 July 2016 (UTC)
 * --AKlapper (WMF) (talk) 06:59, 12 July 2016 (UTC)
 * Valhallasw (talk) 09:49, 12 July 2016 (UTC)
 * Ckoerner (talk) 14:55, 12 July 2016 (UTC)

I have no idea what section this vote (or is it a !vote?) relates to, or if it is a section now retitled as something other than "Cases" or how it may be an expansion of the Arbcom model. Perhaps someone should explain more clearly what is being supported or opposed? --Fæ (talk) 17:58, 12 July 2016 (UTC)
 * Better link. Namely "Handling reports", "Responses and resolutions" and "Appealing a resolution" topics. -- NKohli (WMF) (talk) 12:37, 13 July 2016 (UTC)
 * Thanks, that makes more sense than the general link. --Fæ (talk) 13:17, 13 July 2016 (UTC)


 * Ladsgroup (talk) 08:11, 13 July 2016 (UTC)
 * -- NKohli (WMF) (talk) 12:37, 13 July 2016 (UTC)
 * I'm unclear how the general commitment to confidentiality can be assured for parties to cases, if emails are going through a generic address managed on OTRS. OTRS has no guarantee of confidentiality for files stored on the database and the WMF will take no responsibility for failure to maintain its security. There are references to private information giving the impression that Committee makes a commitment to ensure information from correspondents will stay private, but the same systems for correspondence or checkuser records have a long history from technical failure to deliberate misuse. There is a narrow definition that "private" excludes any information that might have been made public anywhere, and a common part of harassment is to target personal lives of volunteers by doxxing them. By definition anything already doxxed, or information about a person's life that they feel is private but may be a matter of publicly data-minable records (home phone numbers, employment records, family details and addresses, hacked or leaked private photos, etc.) are not covered by any policy, nor covered by an understanding of good-conduct for cases (as this has not been written). Either a realistic disclaimer should be made hand-in-hand with an explanation of the intended good practice, or alternative secure systems should apply for any information that parties feel must stay private. --Fæ (talk) 13:17, 13 July 2016 (UTC)
 * Hey Fæ, Using OTRS was discussed and OTRS was determined to not be a suitable technical solution. CKoerner (WMF) (talk) 14:41, 13 July 2016 (UTC)
 * Thanks for pointing this out, it seems to confirm my concerns. Let's take a moment to explain why the process followed behind this is not satisfactory. The discussion you point to was non-conclusive and boils down to two WMF employees briefly kicking it around in Sept/Nov 2015 and choosing to defer any decision to the committee when it is formed. The second link is to Phabricator where Qgil makes the decision that OTRS is unsuitable based on "several causal conversations" [sic] which are undocumented. This decision is nowhere referenced on the CoC draft discussion pages, nor is the implied action on the Committee noted anywhere that before they can start work they will have to make up and agree a solution to keeping private records confidential in a way that the WMF has no current system for, and could realistically take months rather than weeks to sort out. The way this was discussed makes it impossible for a humble volunteer like myself to know this ever occurred, even though it is possible to link to public records, not a way to ensure that interested community members can stay informed or inform themselves. --Fæ (talk) 16:12, 13 July 2016 (UTC)


 * Seems well thought out, and clearly defined. AGomez (WMF) (talk) 17:55, 19 July 2016 (UTC)
 * MSchottlender-WMF (talk) 22:19, 19 July 2016 (UTC)
 * this text. As for the concerns around privacy and OTRS, at this stage I think it's enough to say that emails sent to the committee should be secured and leave it up to the committee itself how that requirement is fulfilled. -Roan Kattouw (WMF) (talk) 00:52, 20 July 2016 (UTC)
 * I agree. The Committee must respect confidentiality.  But as far as tools for the email, the Committee should seek advice, then make the final decision.  This is consistent with the draft text (in the "Page: Code of Conduct/Committee" section), which states, "The Committee determines its own procedures, subject to the duty to act fairly.". Mattflaschen-WMF (talk) 01:43, 20 July 2016 (UTC)
 * Frimelle (talk) 21:20, 20 July 2016 (UTC)

Decision by 1 person?
The current proposal states that "If all members of the Committee disqualify themselves, the case will be handled by the appeals body." The implication is that if all but 1 members disqualify themselves the one remaining member gets to decide the issue, though I would have thought the quorum would be more than one. This isn't a good design, better to have a minimum of three for this sort of thing. WereSpielChequers (talk) 07:48, 12 July 2016 (UTC)
 * I disagree. Judges often make decisions by themselves, and there is always the option of appeal. Valhallasw (talk) 09:46, 12 July 2016 (UTC)
 * As Fae has said below, Judges are or should be professional legal people who are well qualified as judges. Where you are using less well trained people such as magistrates the UK at least has panels of three. But to answer your specific comment re the right of appeal, that should be for where people think the decision was wrong. You don't want to design a system where people can reasonably appeal because a decision was taken by only one or two people. WereSpielChequers (talk) 08:14, 14 July 2016 (UTC)
 * People are allowed to appeal for any reason, irrespective of how many committee members are taking part in the decision. The alternative is no decision from the committee, which means the case lands at the appeals body immediately. I think it's more reasonable to let the one or two remaining committe members make a decision instead, and having the concerned parties appeal if the decision is not to their liking. Valhallasw (talk) 11:09, 14 July 2016 (UTC)
 * It's a basic governance problem. Committee members are not British style judges, nor French style examining magistrates who are supported by a massive amount of training and independent governance systems. Any Committee member (by definition unpaid and unqualified volunteers) left in such a position should decline the responsibility as both unfair for parties to a case and unreliable in terms of outcome. --Fæ (talk) 13:22, 13 July 2016 (UTC)

Finished/non-finished sections
/, given that there is no interest in improving finalized sections, which sections are considered finalized, and which ones are not? Please update the header of this page accordingly. Valhallasw (talk) 09:28, 12 July 2016 (UTC)
 * Done, thanks for the reminder. Mattflaschen-WMF (talk) 05:34, 18 July 2016 (UTC)

Definition of offensive
Hi, I know I am coming to this very late, but I'd like to suggest that it is vitally important that this document define more specifically the word "offensive". I originally made this comment on the Friendly space policies talk page, this is a revised version.

"Offensive" is a highly subjective term. One person's stated opinion on a controversial topic might be some other person's offensive statement. And (correct me if I'm wrong) I'd guess that a significant percentage of complaints, in general, are of "offensive comments" made by others.

If the term is left undefined, then it's open to interpretation, and the likely outcome will be to suppress speech and stifle honest debate, because participants will tend to err on the side of caution, and not voice opinions. Also, others might misuse the policy to punish those they disagree with.

Let me throw out a couple of examples (these are just meant to be examples -- please don't be offended by the meta-discussion.) These are things that might be said in good faith by one person during a conversation, that some other person might take offense to.

1. "I think people overreacted to Larry Summers, when he suggested that differences in variability of some characteristics between men and women might help to explain the underrepresentation of women in top-tier universities."

2. "There aren't really any lesbians. Studies have shown that female sexuality is much more malleable than men's."

The second one is from a talk by Milo Yiannopoulos. I won't write others, but Google "tells lesbian she doesn't exist" to get more examples further down the "offensive scale". And then, of course, there are even more explosively controversial topics related to race, for example, where people might have honest disagreements about what should be considered offensive.

The Wikimedia community prides itself on being open, and an essential part of "open" is the free exchange of ideas.

I looked through past discussions, and I didn't find anything about this. The closest thing I found was a comment by Fæ in Archive 1 on 22 September 2015: "I would hope that if there is no intent to cause distress, that this would be quickly identified as a communication or cultural gap issue," but it was never addressed. And, I don't think the definition should hinge on intent. Clearly, if the speaker didn't intend a comment to be offensive, then that should be considered in the disposition of the complaint. But what's needed is a threshold for determining that a complaint has merit. The default standard would probably be that if any person takes offense, then the comment is, by definition, offensive. I'm suggesting that that is too open to abuse, and that some complaints should be deemed frivolous.

Another editor, in a different thread, linked to this Todo CoC, and, as a point of reference, I find it even more problematic. They specify harrassment to include "Offensive comments related to gender, gender identity and expression, sexual orientation, disability, ...". I don't see any value in listing a bunch of sub-topics. That doesn't come any closer to clarifying where the line is. Klortho (talk) 23:38, 17 July 2016 (UTC)
 * As you suggest, this is is very late. In fact, the community has already finalized the section you are discussing, and is now discussing other sections.   However, I will note that I do not personally agree with the "default standard" you propose, and that the Committee has the discretion both to determine which comments are offensive, and to determine the proper response.  The Cases section is also clear that they can decide to take no action if none is appropriate. Mattflaschen-WMF (talk) 06:02, 18 July 2016 (UTC)
 * Respectfully, I think that misses the point. I probably didn't express it succinctly enough. By leaving it undefined in the policy, you create uncertainty in any attendee (or potential attendee). It's that uncertainty itself that acts as a powerful damper on free expression. It's a well-known trick employed by repressive regimes: ambiguity in the law, coupled with selective prosecution. After a few incidents that might be perceived as unfair (even if there was no intent to be unfair) people quickly learn to censor their own speech to avoid any possibility that they'll be next. Klortho (talk) 06:23, 18 July 2016 (UTC)
 * Well, this hasn't gotten much response. I had a chat with a friend offline, and he indicated that the kind of speech in my examples would almost certainly be within bounds (not offensive), that the codes of conduct is really more about personal abuse, threatening words, and that sort of thing. So, if that's the general understanding, then I'm reassured. But nevertheless, maybe in a later revision, I'd like to urge that the more specifically you can define these concepts, the better it would be for everyone. In addition to allowing participants to feel safer expressing ideas, it would also mean that victims of harassment could feel more confident making a complaint, arbitrators would have some objective guidelines, and there would be less basis for people to claim capricious enforcement. Klortho (talk) 03:51, 22 July 2016 (UTC)


 * I'm mentioned above, so a quick chip-in, unfortunately another negative viewpoint as that's all I have left. I no longer believe in the arbitrary process being managed exclusively by a few WMF employees being called "consensus". The procedure for "managing" the creation of this document was made up one day by a WMF employee and is not based on any existing consensus building processes by Wikimedia volunteer communities, nor has been positively agreed with the community. The idea that valid concerns about the lack of definition underpinning this code cannot be discussed as that bit of the document is frozen is unhelpful. At a minimum remaining issues should be logged for later action and review rather than forgotten in talk page archives, guaranteeing that they will never be revisited due to the massive investment of time any single volunteer now needs to keep on revisiting and nagging to get noticed or heard. The lack of a basic understanding of what is or is not offensive is fundamental to how the committee can accept cases. With no boundaries established, these flaws in the foundation of this code are likely to cause later cases to unravel and the committee to lose itself in logical flaws and meaningless tautologies.
 * As an example of the weakness of the flawed "consensus" process, I have now raised five times that no volunteers have seen the expert review of the draft commissioned at the start of 2016. This seriously undermines the claim that there is an open consensus here. No explanation of why secrecy is needed for the expert review has been given, instead volunteers are met with a silence that is hard to see as anything other than hostile, given the months this has persisted. Thanks --Fæ (talk) 05:47, 29 July 2016 (UTC)
 * On this latter point, I have created T141791 to summarize the advice requested and provided by experts when drafting the Code of Conduct. The only reason for the "secrecy" has been lack of time.--Qgil-WMF (talk) 17:27, 1 August 2016 (UTC)

Officials (staff, contractors, interns, fellows, board)
I am missing an important point saying something like "unless explixitely stated(*), WMF officials (staff, contractors, interns, fellows, board) are supposed to follow the same rules, procedures, processes, guidelines etc. as non-officials (volunteers)".

(*) Sure that in certain cases officials should have veto or any other kind of exception from common processes, hence this formulation.

Unfortunately I've seen (and yet more unfortunately even experienced) many times that certain officials were not following common processes and when being notified or corrected they either ignored it (in better case) or even behaved like they are superior to "ordinary" users and do not have to follow such processes and felt offended by being told they are not supposed to, or (in the worst case) offended those who corrected them and/or used some power given by being an official.

Being discouraged from further contributing by the superior behavior of officials is the worst what can happen to volunteers, so let's prevent it.

(Feel free to rephrase the point using better terms, but keeping the sense, please.)

— Danny B. 20:25, 28 July 2016 (UTC)


 * The CoC applies to all participants in Wikimedia technical spaces. The Principles section says "Technical skills and community status make no difference to the right to be respected and the obligation to respect others. (...) Prolific contributions and technical expertise are not a justification for lower standards of behavior."--Qgil-WMF (talk) 17:02, 1 August 2016 (UTC)
 * My suggestion was actually not about respecting each other (which is already covered, as you pointed out), but about following common defined processes. If there is some defined process, it is not acceptable that official doesn't respect it, evades it or even acts against it.
 * Community status can obviously be interpreted as only something like admin/bureaucrat/steward/checkuser/etc... I would encourage to find formulation which would explicitly or implicitly cover officials as well.
 * — Danny B. 20:37, 1 August 2016 (UTC)

Summary of conduct reports handled in April-June 2016
As mentioned in earlier discussions, last quarter the Technical Collaboration team started to document reports related to conduct that we have handled. We included a summary in the [Community Engagement quarterly review slides (page 24). Pasted here for convenience:

13 incidents handled, related to --Qgil-WMF (talk) 06:52, 2 August 2016 (UTC)
 * Friendly Space Policy
 * Phabricator Etiquette
 * Offensive, derogatory, or discriminatory comments.
 * Gratuitous or off-topic use of sexual language or imagery
 * Inappropriate or unwanted public or private communication, following, or any form of stalking.
 * Unwanted photography or recording.
 * Harming the discussion or community with methods such as sustained disruption, interruption, or blocking of community collaboration (i.e. trolling).


 * If the intention of posting the nature of the conduct reports is to give an insight for development of the Code of Conduct, it would be useful to give some context as to what words or actions were counted as "offensive" or "derogatory" or "discriminatory", especially the latter. Similarly I doubt that the phrases "phabricator etiquette" or "interruption" means much to anyone without links to specific definitions, so more specific explanations of what it was that needed WMF staff interventions would be helpful for the definitions used in this CoC. --Fæ (talk) 07:17, 15 August 2016 (UTC)
 * The Phabricator etiquette is at Bug management/Phabricator etiquette. Mattflaschen-WMF (talk) 20:06, 15 August 2016 (UTC)

Advice provided by consultants Valerie Aurora and Ashe Dryden
In January 2016 two consultants were retained to advise on the drafting of the Code of Conduct. Despite several requests for more transparency of the advice delivered under this contract, including an email to the WMF CFO, the advice has been kept confidential to employees only and questions about this ignored by WMF employees as can be seen in this talk page archives. The amount or time spent on consultancy remains undisclosed.

Rather than keeping the discussion on this talk page, an action was taken on Phabricator on 1 August 2016, refer to T141791. The reply there was "Fae has requested this information several times. We haven't addressed his request so far basically because producing this summary takes time, and we have been busy. By creating this task, we are making clear that this request is in our backlog.". It seems incongruous that this document is being managed to be finalized, yet unpaid volunteers have yet to see any of the advice given over the last 8 months because "we have been busy". It should be noted that there is no offer to simply publish the advice itself, but a summary of it.

As volunteers are busy and in practice fewer are available to contribute to this document than the number of WMF employees, I hope to see that the advice is published and sufficient time is given for volunteers without the same access as WMF employees to read the professional advice provided (which would have been on previous versions of drafts of this document), and ask questions about it. As we are approaching 9 months of advice, I propose that at least a 3 month window is assured for this purpose after publication of the advice summary. --Fæ (talk) 07:12, 15 August 2016 (UTC)