--- /dev/null
+---
+layout: default
+title: "Code of Conduct: FAQ"
+---
+
+<div id="content">
+
+<h2>Code of Conduct: FAQ</h2>
+
+<p>
+Largely taken from <a href="https://www.djangoproject.com/conduct/faq/">django</a>. Thanks!
+</p>
+
+<p>
+This FAQ attempts to address common questions and concerns around the i3
+community's <a href="/conduct">Code of Conduct</a>. If you still have
+questions after reading it, please feel free to contact us at conduct AT i3wm DOT org.
+</p>
+
+<h3 id="why-adopt">Why have you adopted a Code of Conduct?</h3>
+
+ <p>We think the i3 community is awesome. If you're familiar with the i3
+ community, you'll probably notice that the Code basically matches what
+ we already do. Think of this as documentation: we're taking implicit
+ expectations about behavior and making them explicit.</p>
+
+ <p>We know that the i3 community is open, friendly, and welcoming. We want to
+ make sure everyone else knows it too.</p>
+
+<h3 id="what-does-it-mean">What does it mean to "adopt" a Code of Conduct?</h3>
+
+ <p>For the most part, we don't think it means large changes. We think that the text
+ does a really good job describing the way the i3 community already conducts
+ itself. We expect that most people will simply continue to behave in the
+ awesome way they have for years.</p>
+
+ <p>However, we do expect that people will abide by the spirit and words of the CoC
+ when in "official" i3 spaces.</p>
+
+ <p>In practice, this means mailing lists (i3-discuss), the i3 IRC channel
+ (<tt>#i3</tt>), bug tracking and code review tools. In addition, violations
+ of this code outside these spaces may affect a person's ability to
+ participate within them.</p>
+
+<h3 id="violations">What happens if someone violates the Code of Conduct?</h3>
+
+ <p>Our intent is that the anyone in the community can stand up for this code,
+ and direct people who're unaware to this document. If that doesn't work,
+ or if you need more help, you can contact conduct AT i3wm DOT org.
+ For more details please see our
+ <a href="/conduct-reporting">Reporting Guidelines</a></p>
+
+<h3 id="why-do-we-need">Why do we need a Code of Conduct? Everyone knows not to be a jerk.</h3>
+
+ <p>Sadly, not everyone knows this.</p>
+
+ <p>However, even if everyone was kind, everyone was compassionate, and everyone was
+ familiar with codes of conduct it would still be incumbent upon our community to
+ publish our own. Maintaining a code of conduct forces us to consider and
+ articulate what kind of community we want to be, and serves as a constant
+ reminder to put our best foot forward. But most importantly, it serves as a
+ signpost to people looking to join our community that we feel these values are
+ important.</p>
+
+<h3 id="free-speech">This is censorship! I have the right to say whatever I want!</h3>
+
+ <p>You do -- in <em>your</em> space. If you'd like to hang out in <em>our</em> spaces (as
+ clarified above), we have some simple guidelines to follow. If you want to, for
+ example, form a group where i3 is discussed using language inappropriate for
+ general channels then nobody's stopping you. We respect your right to establish
+ whatever codes of conduct you want in the spaces that belong to you. Please
+ honor this Code of Conduct in our spaces.</p>
+
+</div>
--- /dev/null
+---
+layout: default
+title: "Code of Conduct: Reporting Guide"
+---
+
+<div id="content">
+
+<h2>Code of Conduct: Reporting Guide</h2>
+
+<p>
+Largely taken from <a href="https://www.djangoproject.com/conduct/reporting/">django</a>. Thanks!
+</p>
+
+<p>If you believe someone is violating the code of conduct we ask that you report
+it to the i3 core contributors by emailing conduct AT i3wm DOT org.
+<strong>All reports will be kept confidential.</strong> In some cases we may
+determine that a public statement will need to be made. If that's the case, the
+identities of all victims and reporters will remain confidential unless those
+individuals instruct us otherwise.</p>
+
+<p><strong>If you believe anyone is in physical danger, please notify appropriate
+law enforcement first.</strong> If you are unsure what law enforcement agency is
+appropriate, please include this in your report and we will attempt to notify
+them.</p>
+
+<p>In your report please include:
+<ul>
+ <li>Your contact info (so we can get in touch with you if we need to follow up)</li>
+ <li>Names (real, nicknames, 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 or a public IRC logger) please include a link.</li>
+ <li>Any extra context you believe existed 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>
+
+<h3>What happens after you file a report?</h3>
+
+<p>You will receive an email from the i3 core contributors
+acknowledging receipt immediately. We promise to acknowledge receipt within 24
+hours (and will aim for much quicker than that).</p>
+
+<p>The working group will immediately meet to review the incident and determine:
+<ul>
+ <li>What happened.</li>
+ <li>Whether this event constitutes a code of conduct violation.</li>
+ <li>Who the bad actor was.</li>
+ <li>Whether this is an ongoing situation, or if there is a threat to anyone's physical safety.</li>
+</ul>
+</p>
+
+<p>If this is determined to be an ongoing incident or a threat to physical safety,
+the working groups' immediate priority will be to protect everyone involved.
+This means we may delay an "official" response until we believe that the
+situation has ended and that everyone is physically safe.</p>
+
+<p>Once the working group has a complete account of the events they will make a
+decision as to how to response. Responses may include:
+<ul>
+ <li>Nothing (if we determine no violation occurred).</li>
+ <li>A private reprimand from the working group to the individual(s) involved.</li>
+ <li>A public reprimand.</li>
+ <li>An imposed vacation (i.e. asking someone to "take a week off" from a mailing list or IRC).</li>
+ <li>A permanent or temporary ban from some or all i3 spaces (mailing lists, IRC, etc.)</li>
+ <li>A request for a public or private apology.</li>
+</ul>
+</p>
+
+<p>We'll 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>Once we've determined our final action, we'll contact the original reporter to
+let them know what action (if any) we'll be taking. We'll take into account
+feedback from the reporter on the appropriateness of our response, but we don't
+guarantee we'll act on it.</p>
+
+</div>
--- /dev/null
+---
+layout: default
+title: Code of Conduct
+---
+
+<div id="content">
+
+<h2>Code of Conduct</h2>
+
+<p>
+Largely taken from <a href="https://www.djangoproject.com/conduct/">django</a>. Thanks!
+</p>
+
+<p>Like the technical community as a whole, the i3 team and community is made up
+of a mixture of professionals and volunteers from all over the world, working on
+every aspect of the mission - including mentorship, teaching, and connecting
+people.</p>
+
+<p>Diversity is one of our huge strengths, but it can also lead to communication
+issues and unhappiness. To that end, we have a few ground rules that we ask
+people to adhere to. This code applies equally to founders, mentors and those
+seeking help and guidance.</p>
+
+<p>This isn’t an exhaustive list of things that you can’t do. Rather, take it in
+the spirit in which it’s intended - 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 managed by the i3 project. This
+includes IRC, the mailing lists, the issue tracker, and any other forums
+created by the project team which the community uses for communication. In
+addition, violations of this code outside these spaces may affect a person's
+ability to participate within them.</p>
+
+<p>If you believe someone is violating the code of conduct, we ask that you
+report it by emailing conduct AT i3wm DOT org.
+For more details please see our
+<a href="/conduct-reporting">Reporting Guidelines</a></p>
+
+<ul class="simple">
+ <li><strong>Be friendly and patient.</strong></li>
+
+ <li><strong>Be welcoming.</strong> We strive to be a community that welcomes
+ and supports people of all backgrounds and identities. This includes, but
+ is not limited to members of any race, ethnicity, culture, national origin,
+ colour, immigration status, social and economic class, educational level, sex,
+ sexual orientation, gender identity and expression, age, size, family status,
+ political belief, religion, and mental and physical ability.</li>
+
+ <li><strong>Be considerate.</strong> Your work will be used by other people, and you in turn will
+ depend on the work of others. Any decision you take will affect users and
+ colleagues, and you should take those consequences into account when making
+ decisions. Remember that we're a world-wide community, so you might not be
+ communicating in someone else's primary language.</li>
+
+ <li><strong>Be respectful.</strong> Not all of us will agree all the time, but disagreement is no
+ excuse for poor behavior and poor manners. We might all experience some
+ frustration now and then, but we cannot allow that frustration to turn into a
+ personal attack. It’s important to remember that a community where people feel
+ uncomfortable or threatened is not a productive one. Members of the i3
+ community should be respectful when dealing with other members as well as with
+ people outside the i3 community.</li>
+
+ <li><strong>Be careful in the words that you choose.</strong> We are a community of professionals,
+ and we conduct ourselves professionally. Be kind to others. Do not insult or
+ put down other participants. Harassment and other exclusionary behavior
+ aren't acceptable. This includes, but is not limited to:
+ <ul>
+ <li>Violent threats or language directed against another person.</li>
+ <li>Discriminatory jokes and language.</li>
+ <li>Posting sexually explicit or violent material.</li>
+ <li>Posting (or threatening to post) other people's personally identifying information ("doxing").</li>
+ <li>Personal insults, especially those using racist or sexist terms.</li>
+ <li>Unwelcome sexual attention.</li>
+ <li>Advocating for, or encouraging, any of the above behavior.</li>
+ <li>Repeated harassment of others. In general, if someone asks you to stop, then stop.</li>
+ </ul>
+ </li>
+
+ <li><strong>When we disagree, try to understand why.</strong> Disagreements, both social and
+ technical, happen all the time and i3 is no exception. It is important that
+ we resolve disagreements and differing views constructively. Remember that we’re
+ different. The strength of i3 comes from its varied community, people from a
+ wide range of backgrounds. Different people have different perspectives on
+ issues. Being unable to understand why someone holds a viewpoint doesn’t mean
+ that they’re wrong. Don’t forget that it is human to err and blaming each other
+ doesn’t get us anywhere. Instead, focus on helping to resolve issues and learning from mistakes.</li>
+</ul>
+
+<p>Original text courtesy of the
+<a href="http://web.archive.org/web/20141109123859/http://speakup.io/coc.html">
+Speak Up! project</a>.</p>
+
+<h2>Questions?</h2>
+<p>
+If you have questions, please see <a href="/conduct-faq">the Code of Conduct FAQ</a>. If
+that doesn't answer your questions, feel free to contact us at conduct AT i3wm DOT org.
+</p>
+
+</div>
Introduction and reference. Read this!
</p>
+<p>
+<a href="/conduct"><strong>Code of Conduct</strong></a><br>
+Outlines acceptable behavior within the i3 projects.
+</p>
+
<p>
<a href="/docs/layout-saving.html"><strong>Layout saving/restoring</strong></a><br>
Explains how to save a layout and restore it in a new i3 session.
projects / i3 / i3.github.io / commitdiff