You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This updates wording in a few sections of our new incident-process
docs, adds a link to our new Slack channel in the README, and adds some
descriptions and a link to the incident-process doc to the README.
Signed-off-by: Aeva Black <[email protected]>
Please email [email protected] to initiate an incident report. **_Please do not make reports via our public slack channel._**
36
+
37
+
Our [Incident Report Handling Procedures](incident-process.md) describes how we handle reports while protecting the safety and confidentiality of all involved parties.
38
+
31
39
## Terms
32
40
33
41
The members and their terms are as follows:
@@ -43,7 +51,7 @@ The members and their terms are as follows:
43
51
- Celeste Horgan (CNCF)
44
52
- Tim Pepper (VMware)
45
53
46
-
Please see the [bootstrapping document](./bootstrapping-process.md) for more information on how members are picked, their responsibilities, and how the committee will initially function.
54
+
Please see the [bootstrapping document](./bootstrapping-process.md)and [election process guidelines](election.md)for more information on how members are pickedand their responsibilities.
47
55
48
56
## Emeritus Committee Members
49
57
@@ -54,5 +62,4 @@ The Code of Conduct Committee sincerely thanks our emeritus committee members fo
54
62
- Carolyn Van Slyck (Microsoft)
55
63
- Paris Pittman (Apple)
56
64
57
-
_More information on conflict resolution process to come in the near future. For now, any Code of Conduct or Code of Conduct Committee concerns can be directed to <[email protected]>_.
Copy file name to clipboardExpand all lines: committee-code-of-conduct/incident-process.md
+32-19Lines changed: 32 additions & 19 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -13,6 +13,20 @@ This document outlines the Code of Conduct Committee's workflow when receiving a
13
13
14
14
## When and Where does the Kubernetes Code of Conduct apply?
15
15
16
+
The Code of Conduct applies between all community members when interacting about Kubernetes. This primarily addresses official spaces, but if conduct-related issues are affecting our community in unofficial spaces in ways that are likely also affect interpersonal interactions in _official_ spaces, we may be asked to become involved.
17
+
18
+
### What are the boundaries of the Kubernetes community?
19
+
20
+
There are no hard boundaries of the community, but common places we are asked to extend guidance to are:
21
+
22
+
- Official Kubernetes communication channels
23
+
- Kubernetes events and meetups
24
+
- Media and web presences
25
+
- Social media
26
+
- In some cases, where individual social media messages are not related to Kubernetes but have been reported to the Code of Conduct Committee and are making project members feel unsafe or unwelcome, we might choose to act.
27
+
28
+
## Incident Reports
29
+
16
30
### What is an incident report?
17
31
18
32
An **incident report** is a description of an event, interaction, or public statement submitted to the Kubernetes Code of Conduct Committee, which the reporter feels violates the [Kubernetes Code of Conduct](https://kubernetes.io/community/code-of-conduct/).
@@ -29,16 +43,6 @@ The Code of Conduct Committee accepts reports from everyone who interacts with t
29
43
30
44
At times we encourage community members to email us if an incident is ongoing and we have not been contacted.
31
45
32
-
### What are the boundaries of the Kubernetes community?
33
-
34
-
There are no hard boundaries of the community, but common places we are asked to extend guidance to are:
35
-
36
-
- Official Kubernetes communication channels
37
-
- Kubernetes events
38
-
- Media and web presences
39
-
- Social media
40
-
- In some cases, where individual social media messages are not related to Kubernetes but have been reported to the Code of Conduct Committee and are making project members feel unsafe or unwelcome, we might choose to act.
41
-
42
46
### Where do private incident reports happen?
43
47
44
48
The Code of Conduct Committee's primary means of contact is our email address, [email protected].
@@ -47,6 +51,10 @@ We can also be reached via Slack direct messages to individual committee members
47
51
48
52
### How is the privacy of a report protected?
49
53
54
+
All incident-related discussions happen in private spaces between current Code of Conduct Committee members, and all members agree when joining the Committee to maintain the confidentiality of incidents to the extent permitted by law.
55
+
56
+
Where incidents relate to _unintentionally_ or _non-consensually_ publicly-visible content or messages, we may, or may request others to, delete that content to help preserve the privacy of involved parties.
57
+
50
58
### Why does this process exist?
51
59
52
60
The reporting process exists to provide the community with mechanisms to keep people safe, and to ensure that poor behavior, regardless of who the initator is, is not accepted.
@@ -59,17 +67,22 @@ The Code of Conduct Committee has unilateral power to address harms as needed an
59
67
60
68
The Code of Conduct Committee responds to all emails in a timely manner, usually within a few days.
61
69
70
+
When an email is received, it is reviewed for severity. Based on our training, the initial member(s) to review the report and determine severity and urgency. When necessary, we may alert other members and call for an urgent meeting, but in most cases, we discuss asynchronously and develop a response plan.
71
+
72
+
We maintain a triage rotation schedule so that there are at least two people watching for incoming reports. This allows us to meet our SLA to the community.
73
+
62
74
### Recusal
63
75
64
-
Before beginning investigation on an incident, members can recuse (or refuse to pass judgement on) an incident if they feel a relationship with someone in the incident may hinder impartiality or create a perception of impropriety with respect to individuals involved in the reported incident. Code of Conduct Committee Members might recuse for the following reasons:
76
+
Before beginning investigation on an incident, members can recuse from (or refuse to pass judgement on) an incident if they feel a relationship with someone in the incident may hinder impartiality or create a perception of impropriety with respect to individuals involved in the reported incident. Some examples of reasons a Code of Conduct Committee member might recuse themselves are:
65
77
66
-
- Direct reporting relationships, or company work relationships
78
+
- Direct reporting relationships, or company work relationships that would cause the investigation to appear inappropriate
67
79
- Close working relationships in the Kubernetes community, for example co-leading a SIG with the reporter or someone else mentioned in the report
68
80
69
-
70
81
If all members of the Code of Conduct Committee felt the need to recuse themselves from an incident, the incident would be handled by our thid party mediator.
71
82
72
-
### Reaching out to involved parties
83
+
To reduce the likelihood of recusals, our [election](election.md) process stipulates that we may never have a majority of the Committee from a single employer.
84
+
85
+
### Building a plan
73
86
74
87
The Code of Conduct Committee will privately discuss the incident report, and may or may not decide that we need more information prior to determining whether to take any action.
75
88
@@ -80,12 +93,12 @@ We consider the following at this stage:
80
93
- Is there a public record of the incident which we can review, such as a chat log or video recording?
81
94
- Are there any privacy or safety considerations that we must take into account? For example, if we reach out to an individual named in the report, could this jeapordize the safety of the reporter or other individuals?
82
95
96
+
### Reaching out to involved parties
97
+
83
98
It is our intention to put as little emotional labor on those who have been harmed as possible, and to protect the safety (both physical and emotional) of all community members. We labor to be supportive and non-judgemental and to make the reporting process as safe and low anxiety as possible.
84
99
85
100
In all instances these clarifying discussions are confidential.
86
101
87
-
88
-
89
102
## Incident response workflow
90
103
91
104
### Reconvening the Committee
@@ -110,11 +123,11 @@ In general, the committee strives for unanimous consensus before taking an actio
110
123
111
124
For example, we may choose to do nothing, to issue a private warning, to offer coaching, to recommend organizational changes, or to ban someone from a community platform.
112
125
113
-
114
126
### Taking Actions and Communicating our Recommendations
115
127
116
128
When we have decided on a course of action, we do the following:
117
129
118
130
- We clearly communicate our decision to those who need to hear it, without violating the confidentiality of those who requested it during an investigative process (if one was undertaken).
119
-
- If and only if it is needed, we work with other leadership bodies (e.g., Steering Committee and the Linux Foundation) to issue a public statement.
120
-
131
+
- If and only if it is needed, we work with other leadership bodies (e.g., Steering Committee and the Linux Foundation)
132
+
- This may be necessary if the incident extends to other communities or event spaces, particularly if we feel there is elevated risk of harm to members of those communities
133
+
- In rare cases, we might find it necessary to issue a public statement, either jointly or separately
0 commit comments