Newer
Older
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
# CCoC Enforcement Guidelines
_Last updated 2023-10-12 by [@ajhalili2006](https://mau.dev/ajhalili2006)_
This living document applies to both squad members, community maintainers in open-source projects,
and moderators in chatrooms (particularly our Zulip Cloud organization).
## General
We follow the general advice on the version of Contributor Convenant our current code of
conduct were adopted, alongside Mozilla's diversity and inclusion guidelines, with some
adjustments specific to our community and internal spaces.
## Application of [Consequence Ladder]
[Consequence Ladder]: https://github.com/mozilla/inclusion/blob/master/code-of-conduct-enforcement/consequence-ladder.md
### Recommendations
They're not treated as violations, although we'll log the case as informational
internally.
### Warning (either simple or formal)
Either the mod team, the project leadership or the squad leads should privately
provide a written warning regarding the violation, along with clarity of violation
and consequences of continued behavior. This should be apply to ALL ladders of
enforcement.
If this is their first formal warning, evaluate their access to internal/sensitive content
within Recap Time Squad and consider temporarily revoking their NDA access.
### Mandatory Cool-off Period
This is somewhere between an formal warning and a temporary ban within the Community CoC,
but in this case, we require the violator to take mandatory time-off/cool-off, ranging from
a few weeks to 3-6 months on case-by-case basis.
If this level of enforcement is used the second time, revoke dev/maintainer/moderator access
if any, including temporarily suspending Staff SSO account access. For the third time, block
or deactivate their accounts, alongside thier NDA access, during the extended ban.
### Area-Specific and Permanent Bans
```{admonition} Bans and blocks should be only used as last resort.
:class: warning
While it is still possible to appeal an moderation action involving bans, once the squad leads upheld
the ban decision, it is cannot be reversed unless the ban was happened in bad faith or human error.
```
Depending on the situtation, we may scope the ban to specific project/community areas
at our discretation.
## Enforcement on Fediverse
Enforcing the community code of conduct on the fediverse is different due to
the federated nature of the network, but we'll try to