Code of Conduct

= Page: Code of conduct for technical spaces =

This is a code of conduct for Wikimedia technical spaces. 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).

Principles
In the interest of fostering an open and welcoming community, we are committed to making participation in Wikimedia technical projects a respectful and harassment-free experience for everyone, regardless of gender, gender identity and expression, sex, sexual orientation, disability, neuroatypicality, physical appearance, body size, race, ethnicity, national origin, age, political affiliation, or religion.

Technical skills and community status make no difference to the right to be respected and the obligation to respect others. Newcomers and other contributors with limited experience in our community deserve a welcoming attitude and constructive feedback. Prolific contributions and technical expertise are not a justification for lower standards of behavior.

Unacceptable behavior
Harassment and other types of inappropriate behavior are unacceptable in all public and private Wikimedia technical spaces. Examples include but are not limited to:


 * Personal attacks, violence, threats of violence, or deliberate intimidation.
 * Offensive, derogatory, or discriminatory comments.
 * Gratuitous or off-topic use of sexual language or imagery.
 * Inappropriate or unwanted attention, touching, or physical contact (sexual or otherwise).
 * Inappropriate or unwanted public or private communication, following, or any form of stalking.
 * Unwanted photography or recording.
 * Disclosure of a person's identity or other private information without their consent.
 * Publication of non-harassing private communication
 * Trolling, for example by sustained disruption, interruption, or blocking of community collaboration.

Our open source community acknowledges the presence of systemic inequity and oppression and prioritizes marginalized people’s safety over privileged people's comfort. We do not consider the following to be violations of this policy:
 * Efforts to include or improve the experience of members of underrepresented groups in our technical communities
 * Discussing imbalances in different groups' representation or trends in whose voices are listened to in a given discussion, project, or leadership team
 * Reasonable communication of boundaries, such as “leave me alone,” “go away,” or “I’m not discussing this with you”
 * Refusal to explain or debate social justice concepts
 * Criticism of racist, sexist, cissexist, or otherwise oppressive behavior or assumptions

When evaluating situations that involve heated conflict, we consider persistent patterns of interaction, whose boundaries have been crossed and how frequently, who benefits from a position of privilege, and who belongs to groups which tend to be marginalized. We also assert that no marginalized status excuses a pattern of abusive behavior or harassment.

Report a problem

 * In case of threat of harm and other urgent situations, notify appropriate law enforcement first (if possible) and email the Wikimedia Foundation via emergency@undefinedwikimedia.org (more information).

Victims and observers of unacceptable behavior are encouraged to follow any of these steps:


 * 1) Ask abusers to stop, making them aware of this Code of Conduct.
 * 2) Report the problem to the administrators, maintainers, or designated contacts of the space or project where the problem is happening.
 * 3) Report the problem directly to the Code of Conduct Committee via techconduct@undefinedwikimedia.org. You can also send a report to the Committee if you reported it elsewhere earlier but were not satisfied with the response.

In your report please include: Project administrators and maintainers have the right and are expected to take action on any communication or contribution that violates this code of conduct.
 * Your contact information, so we can get in touch with you if we need to follow up.
 * Names (legal names, nicknames, or pseudonyms) of any individuals involved. If there were other witnesses besides you, please try to include them as well.
 * When and where the incident occurred. Please be as specific as possible.
 * Your account of what occurred. If there is a publicly available record (e.g. a mailing list archive or a public IRC logger) please include a link. Screenshots or diffs can be useful in case something is edited or deleted before action is taken.
 * Any extra context you believe existed for the incident.
 * If you believe this incident is ongoing.
 * Any other information you believe we should have.

Committee members, administrators, project maintainers, and designated contacts are obligated to process all reports with confidentiality. In some cases we may determine that a public statement will need to be made. If that is the case, the identities of all victims and reporters will remain confidential unless those individuals instruct us otherwise.

Go to Code of conduct for technical spaces/Cases to learn about how reports are processed.

Attribution and re-use
This Code of Conduct is adapted from the Contributor Covenant (revision 49054013), the jQuery Code of Conduct (revision 91777886), the Open Code of Conduct (v1.0), and the Citizen Code of Conduct, along with the WMF Friendly space policy. Text from the Contributor Covenant and the jQuery Code of Conduct is used under the MIT License. The text from the Open Code of Conduct is used under a Creative Commons Attribution license. The text from the Citizen Code of Conduct is used under a Creative Commons Share-alike Attribution license. The overall text is under MediaWiki.org's standard license (CC BY-SA 3.0).

We value each other's contributions and each contributor's commitment to making our technical spaces friendly spaces for everyone. We encourage other projects to adopt and adapt this code of conduct regardless of whether they use Wikimedia technical infrastructure.

Handling reports
Reports will receive immediate attention from the Code of Conduct Committee. The Committee will maintain a private log, which is used as described below.

After the initial outcome, the reporter will be notified. The initial outcome must always be logged, even if action is deferred or declined. Both the notification and logging must be done regardless of whether the initial response is by a single member or the group.
 * For a simple case (e.g. a first offense or a minor violation in a single space), a single committee member can take one of these actions on their own:
 * Defer to the space itself.
 * Issue a public or private reprimand directly.
 * Decide not to take action.
 * More complex cases may require the Committee to investigate, eventually contacting any individuals involved and/or related administrators or project maintainers. The Committee must get consent from the reporter before revealing any confidential information (including the reporter's identity). The full Committee can always overrule a response by an individual member.
 * In case of even more complicated or urgent matters, or if the Committee is unable to reach consensus, the report can be transferred to the Wikimedia Foundation Developer Relations team.

After being notified of the outcome, the reporter or alleged offender may raise objections to the resolution. These will be considered by the committee, which may alter the outcome. If the outcome is altered, the new outcome will be logged. When the committee begins enforcing a decision, that is also logged.

Responses and resolutions
Possible responses by the full committee to a reported breach of the Code of Conduct may include:
 * Taking no further action, if the committee determines no violation occurred.
 * Defer to the space involved (e.g. MediaWiki.org admins in the case of an incident on MediaWiki.org, or event organizers for a hackathon), if they seem best-equipped to handle it.
 * A private reprimand from the committee to the individual(s) involved. In this case, the group chair will deliver that reprimand to the individual(s) over email, copying the group.
 * A public reprimand. In this case, the group chair will deliver that reprimand in the same venue that the violation occurred (e.g. in IRC for an IRC violation; email for an email violation). The group may choose to publish this message elsewhere for posterity.
 * An imposed break (e.g. asking someone to "take a week off" from a technical mailing list or technical IRC channel). The group chair will communicate this imposed break to the individual(s). They'll be asked to take this break voluntarily, but if they don't agree then a temporary ban may be imposed to enforce this break.
 * A temporary or permanent ban from some or all Wikimedia technical spaces. The group will maintain records of all such bans so that they may be reviewed in the future, extended to new Wikimedia technical forums, or otherwise maintained.
 * A request for a public or private apology. The chair will deliver this request.
 * Project maintainers who do not follow the Code of Conduct may be removed from their positions of responsibility, temporarily or permanently.

Appealing a resolution
Only resolutions (such as bans) that last 3 months or longer may be appealed by the reported offender. Reported victims can always appeal. To appeal a decision of the committee, the reported offender or reported victim may contact the Developer Relations team at developer-relations@undefinedwikimedia.org and they will review the case. Until an appeal is resolved, the prior resolution remains fully in effect.

= Page: Code of conduct for technical spaces/Committee =

The Code of Conduct Committee is a team of five trusted individuals with diverse affiliations responsible for general enforcement of the Code of conduct for Wikimedia technical spaces. Committee members are in charge of processing complaints, discussing with the parties affected, agreeing on resolutions, and following up on their enforcement. At the committee's discretion, it can also delegate complex issues to the Wikimedia Foundation's Developer Relations team, transferring the responsibility of their resolution.

The Committee determines its own procedures, subject to the duty to act fairly.

Diversity
Diversity among Committee members is encouraged, as a way to promote fairness and independence in their decisions. Members need not be formally part of any organization, and the Committee cannot have all members affiliated to the same employer. Members are expected to have complementary participation in different technical spaces, to assure a good knowledge of our community.

Confidentiality
Committee members and anyone else joining the Committee's deliberations on a case may not disclose private information, except when required by procedures of the Code of Conduct or the Law.

Conflict of interest
Members of the committee must not participate in a decision if doing so would place them in a conflict of interest.

Self-nomination of candidates
The nomination period for new members of the Committee lasts one month. During the first two weeks, people can self-nominate and discuss the candidates. During the remainder of the month, only discussion is permitted. Feedback about candidates can be provided publicly, or privately to the group choosing the next committee.

In their nomination, candidates must commit to comply with the full Code of Conduct, and they can include an initial statement. All candidates must identify to the Wikimedia Foundation.

Selection of new members
The initial Committee is selected by the Developer Relations team after the first nomination period, and remains without changes during one year. From that point, the Committee elects their new members by a majority vote every six months. Up to four committee members can be re-elected.

After a new Committee is chosen, they elect a chair.

Resignation and suspension
Committee members can resign at any time. A member not meeting their obligations can be suspended by agreement of the other four members. In case of a vacancy, the Committee should choose a new member as soon as possible.