From: Michael Stapelberg Date: Sun, 12 Feb 2017 20:52:21 +0000 (-0800) Subject: document code of conduct (#31) X-Git-Url: https://git.sur5r.net/?a=commitdiff_plain;h=3feebee760e87b9abb2301333ba93ea73507acf3;p=i3%2Fi3.github.io document code of conduct (#31) fixes https://github.com/i3/i3/issues/2676 --- diff --git a/conduct-faq.html b/conduct-faq.html new file mode 100644 index 0000000..8bdec04 --- /dev/null +++ b/conduct-faq.html @@ -0,0 +1,74 @@ +--- +layout: default +title: "Code of Conduct: FAQ" +--- + +
+ +

Code of Conduct: FAQ

+ +

+Largely taken from django. Thanks! +

+ +

+This FAQ attempts to address common questions and concerns around the i3 +community's Code of Conduct. If you still have +questions after reading it, please feel free to contact us at conduct AT i3wm DOT org. +

+ +

Why have you adopted a Code of Conduct?

+ +

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.

+ +

We know that the i3 community is open, friendly, and welcoming. We want to + make sure everyone else knows it too.

+ +

What does it mean to "adopt" a Code of Conduct?

+ +

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.

+ +

However, we do expect that people will abide by the spirit and words of the CoC + when in "official" i3 spaces.

+ +

In practice, this means mailing lists (i3-discuss), the i3 IRC channel + (#i3), 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.

+ +

What happens if someone violates the Code of Conduct?

+ +

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 + Reporting Guidelines

+ +

Why do we need a Code of Conduct? Everyone knows not to be a jerk.

+ +

Sadly, not everyone knows this.

+ +

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.

+ +

This is censorship! I have the right to say whatever I want!

+ +

You do -- in your space. If you'd like to hang out in our 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.

+ +
diff --git a/conduct-reporting.html b/conduct-reporting.html new file mode 100644 index 0000000..73a715d --- /dev/null +++ b/conduct-reporting.html @@ -0,0 +1,78 @@ +--- +layout: default +title: "Code of Conduct: Reporting Guide" +--- + +
+ +

Code of Conduct: Reporting Guide

+ +

+Largely taken from django. Thanks! +

+ +

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. +All reports will be kept confidential. 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.

+ +

If you believe anyone is in physical danger, please notify appropriate +law enforcement first. If you are unsure what law enforcement agency is +appropriate, please include this in your report and we will attempt to notify +them.

+ +

In your report please include: +

+

+ +

What happens after you file a report?

+ +

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).

+ +

The working group will immediately meet to review the incident and determine: +

+

+ +

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.

+ +

Once the working group has a complete account of the events they will make a +decision as to how to response. Responses may include: +

+

+ +

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.

+ +

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.

+ +
diff --git a/conduct.html b/conduct.html new file mode 100644 index 0000000..9a48fec --- /dev/null +++ b/conduct.html @@ -0,0 +1,99 @@ +--- +layout: default +title: Code of Conduct +--- + +
+ +

Code of Conduct

+ +

+Largely taken from django. Thanks! +

+ +

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.

+ +

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.

+ +

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.

+ +

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.

+ +

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 +Reporting Guidelines

+ + + +

Original text courtesy of the + +Speak Up! project.

+ +

Questions?

+

+If you have questions, please see the Code of Conduct FAQ. If +that doesn't answer your questions, feel free to contact us at conduct AT i3wm DOT org. +

+ +
diff --git a/docs/index.html b/docs/index.html index 5e79ddd..12c23d7 100644 --- a/docs/index.html +++ b/docs/index.html @@ -20,6 +20,11 @@ suggestions please let us know! Introduction and reference. Read this!

+

+Code of Conduct
+Outlines acceptable behavior within the i3 projects. +

+

Layout saving/restoring
Explains how to save a layout and restore it in a new i3 session.