Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

added code of conduct breaches #252

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

added code of conduct breaches #252

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 8 additions & 0 deletions docs/index.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,14 @@ The vision is that it grows over time as the teams and governance structure evol

about/what_is_mautic

.. toctree::
:maxdepth: 2
:caption: Policies
:hidden:

policies/code_of_conduct/code_of_conduct_breaches


.. toctree::
:maxdepth: 2
:caption: Teams
Expand Down
76 changes: 76 additions & 0 deletions docs/policies/code_of_conduct/code_of_conduct_breaches.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,76 @@
.. vale on

Code of Conduct Breaches

Check warning on line 3 in docs/policies/code_of_conduct/code_of_conduct_breaches.rst

View workflow job for this annotation

GitHub Actions / prose 

[vale] reported by reviewdog 🐶
[Google.Headings] 'Code of Conduct Breaches' should use sentence-style capitalization.

Raw Output:
{"message": "[Google.Headings] 'Code of Conduct Breaches' should use sentence-style capitalization.", "location": {"path": "docs/policies/code_of_conduct/code_of_conduct_breaches.rst", "range": {"start": {"line": 3, "column": 1}}}, "severity": "WARNING"}
########################

.. vale off

Why do we need this policy?
***************************

Having a Code of Conduct is important - it allows us to define how we expect people to behave in our community. We need to have an agreed workflow and process that will be followed in the event of a breach by a Community member of the Code of Conduct.

Who does this policy apply to?
******************************

This policy applies to every member of the Mautic Community and every contributor of the Project.

Submitting a report
*******************

Pursuant the Mautic Code of Conduct (CoC), any individual may submit an incident report to the Community Manager or Project Lead. They will review the incident and propose recommended actions and/or sanctions. Where appropriate, cases may be escalated to the Community Council.

Incident processing
*******************

- An incident report is received by Community Manager or Product Lead (receiving party) and shared with the Community Council within 24 hours of receipt.
- The incident report is shared by the receiving party with the reported person (who has committed the breach) and they are given 7 days to submit a response
- The incident report will be reviewed and discussed at the next available Council Meeting after the 7 days have elapsed or a response is received, whichever is sooner. Should the incident be of a serious matter and requires immediate action, the Community Council may call a Special Council Meeting to discuss it.
- The Community Council shall propose sanctions according to those laid out in this Policy.
- The Community Council shall notify all involved parties in accordance with this Policy.

Proposed sanctions
******************

+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Occurrence | Sanction |
+=============+=======================================================================================================================================================================================================================================================================================================================================================================================================================================================================================================+
| 1st offence | Warning to the offender. Apology to offended within 7 days required. Nature of apology to be determined by the nature of offence. If the offence was committed in public (i.e at an event or publicly on the internet) , a public apology will be required. If the offence happened in a team or more private setting, an apology to all people who witnessed the offence will be sufficient.* Should apology be refused by the offender, sanction will be escalated to second offence automatically. |
+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|2nd offence | 3 month ban. |
+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
|3rd offence | 6 month ban |
+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 4th offence | 12 month ban |
+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+
| 5th offence | Lifetime Ban by full Community Council vote |
+-------------+-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------+

Terms of a ban
**************

The inflicted ban shall be considered as “Full Ban” from the project including, but not limited to, access and privileges to any and all Mautic Channels, Forums, Websites, Systems, Events, and Activities (including speaking at events, in blog posts and on social media on behalf of the Mautic Community or Project).

End of ban
**********

After the Ban period, the user will be reinstated as a registered user, without any administrative or leadership rights or privileges. The ban will remain on the record of the offender for a period of 18 months from the end of the ban. The ban will then be removed from the offender’s record and levels of recommended sanctions will reset to those of 1st Offence.

Other sanctions
***************

The Community Council might consider other types or duration of sanctions according to the severity of the violation.

Communications
**************

The Community Council shall notify all the interested parties (offender and offended) upon any action taken in relation to the Code of Conduct incident reported. When a ban is implemented, the name of the banned person and the effective dates of the ban will be published on the Mautic Community website for the reference of the community at large to ensure no speaking or other engagements are made with the offender during the period of their ban.

Active sanctions
****************

+--------------+----------------------------------------------------+------------------------------------+
| Person | Conduct | Sanction |
+==============+====================================================+====================================+
| Yosu Cadilla | Repeated personal attacks following formal warning | Permanent ban enacted June 6, 2023 |
+--------------+----------------------------------------------------+------------------------------------+
Loading