| |
@@ -1,16 +0,0 @@
|
| |
- include::ROOT:partial$attributes.adoc[]
|
| |
-
|
| |
- = Code of Conduct response policy
|
| |
-
|
| |
- Once a ticket notifying us of a Code of Conduct issue has been filed, the {team_name} will respond with an initial contact message within one week.
|
| |
- That will come with a request for response, and further action will come within a week of the {team_name}'s initial response.
|
| |
-
|
| |
- ({team_name} IRC meeting, 2018-05-23)
|
| |
-
|
| |
- Teams within Fedora have the freedom to decide what is on- and off-topic for their fora (IRC channel, mailing list, Telegram channel, et cetera).
|
| |
- Moderators may ban participants for repeatedly engaging in off-topic discussion in contributor channels, however they must file a ticket with the {team_name}'s https://pagure.io/CoC/issues[Code of Conduct issue tracker] to report the ban.
|
| |
- Bans for being off-topic in one channel may not be extended to other channels unless the behavior is displayed in that channel as well.
|
| |
- In this case, each ban should be treated as a separate issue with its own ticket.
|
| |
- Community members who wish to appeal the ban may file a link:{team_issue_tracker}/issues[ticket with the {team_name}].
|
| |
-
|
| |
- The xref:fca.adoc[FCA] is empowered to take action on Code of Conduct reports with an additional +1 from another core {team_name} member or the xref:dei:roles:council-advisor.adoc[DEI Advisor] and report back to {team_name}.
|
| |
jflory7
commented 4 months ago
This commit removes a policy that was not updated along with the new Fedora Code of Conduct in 2021. This policy documents an incorrect and outdated process from 2018 that is no longer observed. It is misleading and communicates wrong information. Therefore, it should just be removed instead of going through the Council Policy Change Policy.
The removed page now redirects to the current Fedora Code of Conduct page for anyone who bookmarked the previous URL.