i3.github.io/docs/conduct-reporting.html at main · i3/i3.github.io · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
<!DOCTYPE html>
<html lang="en">
    <head>
        <meta charset="utf-8">
        <title>Code of Conduct: Reporting Guide — i3: improved tiling X11 window manager</title>
        <link rel="icon" type="image/x-icon" href="/favicon.ico">
        <link rel="stylesheet" href="/css/style.css">
        <meta name="viewport" content="width=device-width, initial-scale=1">
        <meta name="description" content="i3 is a tiling window manager with clean, readable and documented code, featuring extended Xinerama support, usage of libxcb instead of xlib and several improvements over wmii">
        <meta name="author" content="i3 developers">
	<link href="https://fosstodon.org/@i3wm" rel="me">

    </head>
    <body>
        <header>
            <a class="logo" href="/">
                <img src="/img/logo.svg" alt="i3 WM logo" />
            </a>
            <nav>
              <ul>
                <li><a href="/docs/">Docs</a></li>

                <li><a href="/screenshots/">Screens</a></li>

                <li><a href="https://github.com/i3/i3/discussions">FAQ</a></li>

                <li><a href="/contact">Contact</a></li>

                <li><a href="https://github.com/i3/i3/issues">Bugs</a></li>

                </ul>
            </nav>
        </header>
        <main>

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


        </main>
        <footer>
            © 2009-present Michael Stapelberg,
            <a href="/impress.html">Impressum</a>,
            <a href="https://github.com/i3/i3.github.io">Source</a>
        </footer>
    </body>
</html>