This document is a log of all code of conduct incidents occurring in Kubernetes community spaces. Information is anonymized to protect those involved in incidents.
- Incident report: An incident report is a description of an action, event or public statement the reporter feels violates the Code of Conduct. For more information, see Incident Reports.
- Conduct action: A conduct action is any action (restorative or punitive) taken by the Code of Conduct Committee or another body empowered by them (such as a direct action by Slack admins).
Data collection period: January 1, 2022 - June 30, 2022
Incident report counts
| Received Via | This Period | Delta vs Prior Period |
|---|---|---|
| conduct@kubernetes.org | 3 | -5 |
| Slack admins | 61 | +5 |
| GitHub admins | X1 | X1 |
| Linux Foundation event staff | 5 | +4 |
| Other avenues | N/A | N/A |
Total incidents reported: 69
Total conduct incidents Incident reports determined to be CoC violations and which resulted in conduct action
| Action By | Restorative Action This Period | Delta vs Prior Period | Punitive Action This Period | Delta vs Prior Period |
|---|---|---|---|---|
| Code of Conduct Committee | 0 | -1 | 0 | N/A |
| Slack Admins | 37 | +2 | 14 | +5 |
| GitHub Admins | X1 | X1 | X1 | X1 |
| Linux Foundation Staff | 4 | X2 | 0 | X2 |
| Other avenues | N/A | N/A | N/A | N/A |
Total incidents which resulted in conduct action: 41
Footnotes: 1 Due to a full turnover of the code of conduct committee staff, the collection of data for this report was delayed. As such, the data rention window for GitHub had passed. In the future, we will take steps to prevent this from happening.
2 This data was not available in the previous transparency report, therefore there is no delta to report.