svn commit: r51417 - head/en_US.ISO8859-1/htdocs/internal
Benedict Reuschling <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.cvs.doc |
|---|---|
| Message-ID | <[email protected]> |
Author: bcr
Date: Mon Feb 12 20:43:11 2018
New Revision: 51417
URL: https://svnweb.freebsd.org/changeset/doc/51417
Log:
Announce the new Code of Conduct for the Project.
A lot of work by many people went into making this new code better than
the one we had, including: Valerie Aurora, Anne Dickison, Warner Losh,
Colin Percival, Benno Rice, Devin Teske, and Robert Watson.
Approved by: core@
Modified:
head/en_US.ISO8859-1/htdocs/internal/code-of-conduct.xml
Modified: head/en_US.ISO8859-1/htdocs/internal/code-of-conduct.xml
==============================================================================
--- head/en_US.ISO8859-1/htdocs/internal/code-of-conduct.xml Mon Feb 12 17:51:01 2018 (r51416)
+++ head/en_US.ISO8859-1/htdocs/internal/code-of-conduct.xml Mon Feb 12 20:43:11 2018 (r51417)
@@ -8,142 +8,260 @@
<head>
<title>&title;</title>
- <cvs:keyword xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
- </head>
+ <cvs:keyword
+ xmlns:cvs="http://www.FreeBSD.org/XML/CVS">$FreeBSD$</cvs:keyword>
+ </head>
<body class="navinclude.docs">
- <h2>Introduction</h2>
+ <h2>&os; Code of Conduct</h2>
- <p>We expect everyone involved with the &os; project to follow
- this Code of Conduct. This not only includes developers and
- contributors to &os; but also anyone posting to &os; mailing
- lists or using the &os; Forums or chatting on &os; specific IRC
- channels, or otherwise interacting with the &os; community.</p>
+ <p>The &os; Project is inclusive. We want the &os; Project
+ to be a venue where people of all backgrounds can work together
+ to make the best operating system, built by a strong community.
+ These values extend beyond just development to all aspects of
+ the Project. All those given recognition as members of the
+ Project in whatever form are seen as ambassadors of the
+ Project.</p>
- <p>Each individual's behavior is primarily a matter for their
- personal conscience. Even so, there are limits whose breach
- will not be tolerated. This page explains what is normally
- expected of &os; community members, and what is absolutely
- required.</p>
+ <p>Diversity is a huge strength and is critical to the long term
+ success of the Project. To that end we have a few ground rules
+ that we ask people to adhere to. This code applies equally to
+ everyone representing the &os; Project in any way, from new
+ members, to committers, to the core team itself. These rules
+ are intended to ensure a safe, harassment-free environment for
+ all and to ensure that everyone feels welcome both working
+ within, and interacting with, the Project.</p>
- <h2>Interpersonal Interaction</h2>
+ <p>This document is not an exhaustive list of things that you
+ should not do. Rather, consider it a guide to make it easier to
+ enrich all of us and the technical communities in which we
+ participate.</p>
+ <p>This code of conduct applies to all spaces used by the &os;
+ Project, including our mailing lists, IRC channels, and social
+ media, both online and off. Anyone who is found to violate this
+ code of conduct may be sanctioned or expelled from &os;
+ Project controlled spaces at the discretion of the &os; Code
+ of Conduct Committee.</p>
+
+ <p>Some &os; Project spaces may have additional rules in place,
+ which will be made clearly available to participants.
+ Participants are responsible for knowing and abiding by these
+ rules. Harassment includes but is not limited to:</p>
+
<ul>
- <li>Keep it civil.</li>
- <li>Be tolerant.</li>
- <li>Remember that you are in public and that your actions
- determine the public perception of the project.</li>
- <li>Do not make it personal. Do not take it personally.</li>
- </ul>
+ <li>Comments that reinforce systemic oppression related to
+ gender, gender identity and expression, sexual orientation,
+ disability, mental illness, neurodiversity, physical
+ appearance, body size, age, race, or religion.</li>
- <p>Always strive to present a civil and courteous demeanour in
- your dealings with other project members; moreso when dealing
- with third parties from outside the project. Avoid foul or
- abusive language: remember that cultural standards differ, and
- that what may seem to you to be a very mild statement can be
- deeply shocking to another. Avoid contentious topics (unless
- directly technically relevant). These things all have their
- places, but not here, where they are out of context.</p>
+ <li>Unwelcome comments regarding a person's lifestyle choices
+ and practices, including those related to food, health,
+ parenting, drugs, and employment.</li>
- <p>Try not to take offense where no offense was intended. Not
- everyone speaks or writes English fluently. Not everyone can
- express themselves clearly. Give people the benefit of the
- doubt. Even if the intent was to provoke, do not rise to
- it.</p>
+ <li>Deliberate misgendering.</li>
- <p>Conflict is inevitable, but unseemly conduct is not. If you
- must disagree forcefully, do so within the appropriate technical
- discussion group and in a manner that will be acceptable to your
- audience. Stay focused on the topic at hand. Heated
- arguments have a way of dragging in bystanders and mutating
- until the original point is lost.</p>
+ <li>Deliberate use of "dead" or rejected names.</li>
- <p>Stick to the facts. Anyone may disagree with you: this does
- not give you a license to descend into personal insults. If
- your arguments cannot stand up in their own right, then either
- admit defeat gracefully or formulate better arguments.</p>
+ <li>Gratuitous or off-topic sexual images or behaviour in spaces
+ where they're not appropriate.</li>
- <h2>What Will Not Be Tolerated</h2>
+ <li>Physical contact and simulated physical contact (e.g.,
+ textual descriptions like "*hug*" or
+ "*backrub*") without consent or after a request
+ to stop.</li>
- <p>The following will not be tolerated, and can result in
- expulsion from the community</p>
+ <li>Threats of violence.</li>
+ <li>Incitement of violence towards any individual, including
+ encouraging a person to commit suicide or to engage in
+ self-harm.</li>
+
+ <li>Deliberate intimidation.</li>
+
+ <li>Stalking or following.</li>
+
+ <li>Harassing photography or recording, including logging online
+ activity for harassment purposes.</li>
+
+ <li>Sustained disruption of discussion.</li>
+
+ <li>Unwelcome sexual attention.</li>
+
+ <li>Pattern of inappropriate social contact, such as
+ requesting/assuming inappropriate levels of intimacy with
+ others.</li>
+
+ <li>Continued one-on-one communication after requests to
+ cease.</li>
+
+ <li>Deliberate "outing" of any private aspect of a
+ person's identity without their consent except as necessary to
+ protect vulnerable people from intentional abuse.</li>
+
+ <li>Publication of non-harassing private communication without
+ consent.</li>
+
+ <li>Publication of non-harassing private communication with
+ consent but in a way that intentionally misrepresents the
+ communication (e.g., removes context that changes the
+ meaning).</li>
+
+ <li>Knowingly making harmful false claims about a person.</li>
+ </ul>
+
+ <h2>Reporting Instructions</h2>
+
+ <p>If you believe someone is violating the code of conduct we ask
+ that you report it to the &os; Code of Conduct Committee by
+ emailing <a
+ href="mailto:[email protected]">[email protected]</a>.</p>
+
+ <p>All reports will be kept confidential whenever possible. We
+ strive to protect the identity and safety of reporters. In some
+ cases we may need to make a public statement of some form, in
+ which case we will use the minimum of details and identifying
+ information necessary to protect our community. In rare cases,
+ we may need to identify some of the people involved to comply
+ with the law or protect other potential victims. In these
+ cases, we will consult with the reporter to find out what their
+ wishes are and take them into account in our final decision. In
+ all cases, we will not directly or indirectly identify reporters
+ without their consent unless we see no other option.</p>
+
+ <p>If you believe anyone is in physical danger, please notify
+ appropriate law enforcement first. In your report please
+ include:</p>
+
<ul>
- <li>Discrimination based on gender, race, nationality,
- sexuality, religion, age or physical disability.</li>
- <li>Bullying or systematic harassment.</li>
- <li>Incitement to or condoning of any of these.</li>
+ <li>Your name and contact info (so we can get in touch with you
+ if we need to follow up)</li>
+
+ <li>Names (real, nicknames, and/or pseudonyms) of any
+ individuals involved. If there were other witnesses besides
+ you, please try to include them as well.</li>
+
+ <li>When and where the incident occurred. Please be as specific
+ as possible.</li>
+
+ <li>Your account of what occurred. If there is a publicly
+ available record (e.g. a mailing list archive, tweet, or a
+ public IRC logger) please include a link and/or screen
+ shots.</li>
+
+ <li>Any extra context you believe relevant for the
+ incident.</li>
+
+ <li>If you believe this incident is ongoing.</li>
+
+ <li>Any other information you believe we should have.</li>
</ul>
- <p>There can be no place
- within the &os; Community for discriminatory speech or action.
- We do not believe anyone should be treated any differently based
- on who they are, where they are from, where their ancestors were
- from, what they look like, what gender they identify as, who
- they choose to sleep with, how old they are, their physical
- capabilities or what sort of religious beliefs they may hold.
- What matters is the contribution they are able to make to the
- project, and only that.</p>
+ <h2>What happens after you file a report?</h2>
- <p>There is no place within the &os; Community for
- behavior intended to intimidate or persecute other members of
- the community. No one should have any cause to fear involvement
- with the &os; project.</p>
+ <p>You will receive an email from the &os; Code of Conduct
+ Committee acknowledging receipt of your report within 48
+ hours.</p>
- <p>We will not tolerate any member of the community, either
- publicly or privately, giving aid or encouragement to any
- third party to behave in such a way towards any members of
- the &os; community.</p>
+ <p>The committee will meet as quickly as possible to review the
+ incident and determine:</p>
- <p>Core will remove any and all access to &os; resources or
- privileges for whatever period it deems fit, up to and including
- a permanent ban where it rules that a transgression has
- happened.</p>
+ <ul>
+ <li>Whether an investigation is needed, including interviewing
+ additional parties or witnesses;</li>
- <h2>In Case of Conflict</h2>
+ <li>What appears to have happened and;</li>
+ <li>Whether the behavior constitutes a Code of Conduct
+ violation.</li>
+ </ul>
+
+ <p>If a member of the &os; Code of Conduct Committee is one of
+ the individuals included in the report they will recuse
+ themselves from handling the report.</p>
+
+ <p>Once the working group has a complete account of the events
+ they will make a decision as to how to respond. Actions taken
+ may include:</p>
+
<ul>
- <li>If contested, back out your changes first, then argue your
- case.</li>
- <li>Ask for review.</li>
- <li>Seek approval from maintainers.</li>
- <li>When no mutually satisfactory resolution can be achieved,
- defer to security-officer, doceng, portmgr, or core</li>
+ <li>Nothing (for example, if we determine that no violation
+ occurred).</li>
+
+ <li>If determined to be solely technical in nature or if it
+ falls outside the scope of the Code of Conduct, forwarding the
+ incident to the &os; Core Team</li>
+
+ <li>A private reprimand from the working group to the
+ individual(s) involved.</li>
+
+ <li>A public reprimand.</li>
+
+ <li>An imposed vacation from &os; Project controlled spaces
+ (e.g. asking someone to "take a week off" from a
+ mailing list or IRC).</li>
+
+ <li>A permanent or temporary ban from some or all &os;
+ Project controlled spaces (events, meetings, mailing lists,
+ IRC, etc.)</li>
+
+ <li>A request for a public or private apology.</li>
+
+ <li>A request to engage in mediation and/or an accountability
+ plan.</li>
</ul>
- <p>If there are a sustained set of objections to a change you
- have made, be graceful and revert what you have done.
- Objections are hardly likely to be raised for trivial reasons,
- and commits can always be re-applied. The potential loss of
- reputation for the project from shipping bad code is
- permanent.</p>
+ <p>We will do our best to respond within one week to the person
+ who filed the report with either a resolution or an explanation
+ of why the situation is not yet resolved.</p>
- <p>Seeking review beforehand is the best way to avoid
- misunderstanding. It is not just good practice for improving
- code quality: it facilitates putting opposing technical
- arguments clearly and reasonably.</p>
+ <p>Once we have determined our final action, we will contact the
+ original reporter to let them know what action (if any) we will
+ be taking. We will take into account feedback from the reporter
+ on the appropriateness of our response, but we do not guarantee
+ we will act on it.</p>
- <p>It is strongly encouraged that you consult maintainers before
- making changes in their particular areas, although in many areas
- some teams have given blanket approval for certain types of
- change. For instance, various types of sweeping updates to the
- ports are permitted without reference to individual port
- maintainers. It is the duty of committers and maintainers to
- keep up-to-date with such standards and practices, and abide by
- them. Getting maintainer approval for any change, even if not
- strictly required, is never a bad thing, and certainly
- courteous.</p>
+ <p>Finally, the committee will make a report on the situation to
+ the &os; Core Team. The Core Team may choose to issue a
+ public report of the incident.</p>
- <p>If you cannot agree, who should you turn to for arbitration?
- Core itself is directly responsible for the base system, but has
- delegated control over ports, documentation, release engineering
- and security related functions to sub-committees. Operational
- control of &os; cluster servers, user accounts, e-mail, various
- web-based and other services have been similarly devolved to <a
- href="../administration.html">specific teams</a>. These teams
- are the first line of resort when disputes cannot be resolved and
- require mediation. Failing that, a decision by core will be
- final.</p>
+ <h2>Appeals</h2>
+
+ <p>Only permanent resolutions (such as bans) may be appealed. To
+ appeal a decision of the CoC Committee, contact the &os; Core
+ Team at <a href="mailto:[email protected]">[email protected]</a>
+ with your appeal and the Core Team will review the case.</p>
+
+ <h2>Glossary</h2>
+
+ <dl>
+ <dt>Systemic oppression:</dt>
+
+ <dd>
+ <p>The ways in which history, culture, ideology, public
+ policies, institutional practices, and personal behaviors
+ and beliefs interact to maintain a hierarchy — based
+ on race, class, gender, sexuality, and/or other group
+ identities — that allows the privileges associated
+ with the dominant group and the disadvantages associated
+ with the oppressed, targeted, or marginalized group to
+ endure and adapt over time. (Derived from Aspen Institute,
+ via Open Source Leadership)</p></dd>
+
+ <dt>Dead names:</dt>
+
+ <dd>
+ <p>A name assigned to a person at birth which they no longer
+ identify with. Most often used to refer to the assigned
+ name of a trans person who has publicly identified
+ themselves under a new name. Deliberately using a dead name
+ is an act of hostility.</p></dd></dl>
+
+ <h2>Attribution</h2>
+
+ <p>This Code of Conduct is based on the example policy from the <a
+ href="http://geekfeminism.wikia.com/wiki/Community_anti-harassment">Geek
+ Feminism wiki</a>.</p>
</body>
</html>
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/svn-doc-all
To unsubscribe, send any mail to "[email protected]"