CCoC Enforcement Guidelines#
Last updated 2023-10-12 by @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.
Scope#
Any activity performed using a @crew.recaptime.eu.org email address must follow the
Code of Conduct as published for kernel.org, just as any individual using a corporate
email account must follow the specific rules of that corporation. Additional policies
may apply, including the
Application of Consequence Ladder#
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, as documented in Mozilla’s.
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[1].
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#
Bans and blocks should be only used as last resort.
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 first before we proactively expand the scope of the ban (as the violation progresses).
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 moderate as much as we can. See this appendix section in the community code of conduct for details.