From ec4ce17e24c19f986a61605681be23391bd98de4 Mon Sep 17 00:00:00 2001 From: Favour Chibueze Date: Tue, 5 Nov 2024 16:13:47 +0000 Subject: [PATCH 1/4] added code of conduct breaches --- docs/index.rst | 8 ++ .../code_of_conduct_breaches.rst | 76 +++++++++++++++++++ 2 files changed, 84 insertions(+) create mode 100644 docs/policies/code_of_conduct/code_of_conduct_breaches.rst diff --git a/docs/index.rst b/docs/index.rst index 08486bb6..69559430 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -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 diff --git a/docs/policies/code_of_conduct/code_of_conduct_breaches.rst b/docs/policies/code_of_conduct/code_of_conduct_breaches.rst new file mode 100644 index 00000000..246158ed --- /dev/null +++ b/docs/policies/code_of_conduct/code_of_conduct_breaches.rst @@ -0,0 +1,76 @@ +.. vale on + +Code of Conduct Breaches +######################## + +.. 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 | ++--------------+----------------------------------------------------+------------------------------------+ \ No newline at end of file From 4dcc6e361e119455d8d20a764f09381d267c4311 Mon Sep 17 00:00:00 2001 From: Favour Chibueze Date: Tue, 5 Nov 2024 16:28:15 +0000 Subject: [PATCH 2/4] Add Use of Community Tools & Resources --- docs/index.rst | 2 +- .../code_of_conduct_breaches.rst | 76 ------------------- .../code_of_conduct/tools_and_resources.rst | 71 +++++++++++++++++ 3 files changed, 72 insertions(+), 77 deletions(-) delete mode 100644 docs/policies/code_of_conduct/code_of_conduct_breaches.rst create mode 100644 docs/policies/code_of_conduct/tools_and_resources.rst diff --git a/docs/index.rst b/docs/index.rst index 69559430..64ee0d48 100644 --- a/docs/index.rst +++ b/docs/index.rst @@ -28,7 +28,7 @@ The vision is that it grows over time as the teams and governance structure evol :caption: Policies :hidden: - policies/code_of_conduct/code_of_conduct_breaches + policies/code_of_conduct/tools_and_resources .. toctree:: diff --git a/docs/policies/code_of_conduct/code_of_conduct_breaches.rst b/docs/policies/code_of_conduct/code_of_conduct_breaches.rst deleted file mode 100644 index 246158ed..00000000 --- a/docs/policies/code_of_conduct/code_of_conduct_breaches.rst +++ /dev/null @@ -1,76 +0,0 @@ -.. vale on - -Code of Conduct Breaches -######################## - -.. 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 | -+--------------+----------------------------------------------------+------------------------------------+ \ No newline at end of file diff --git a/docs/policies/code_of_conduct/tools_and_resources.rst b/docs/policies/code_of_conduct/tools_and_resources.rst new file mode 100644 index 00000000..9f8df32b --- /dev/null +++ b/docs/policies/code_of_conduct/tools_and_resources.rst @@ -0,0 +1,71 @@ +Use of Community Tools & Resources +################################## + +Why do we need this policy? +*************************** + +Each contributor might be granted an access to one or more tools or resources provided and or operated by the Mautic Community to fulfill their responsibilities as contributor. This policy aims to reduce the security and business risks and to let users know how they are permitted to use the tools and resources, and what happens if they are misused. + +Who does this policy apply to? +****************************** + +This policy applies to all contributors. It applies no matter where the tool or resource use takes place. It applies to use of tools and resources (as defined below) on any device. + +Tools and resources +******************* + +The Mautic Community uses different tools and software, including, but not limited to, desktop software, web-based software, web applications, cloud-based services like mail, storage platform, real time communication services (i.e. Gmail, GSuite, Slack, Jitsi etc.). + +The Mautic Community encourages its contributors to use provided tools whenever appropriate. For instance allowed usage includes: communicate with other contributors (i.e. through email, instant messaging or videoconferences), work/collaborate with other teams and stakeholders on project materials (i.e. team documents, project documents, collaborated folders). + +Unauthorized use +**************** + +Any of the project tools (i.e. email account, software license, chat system) shall not be used for personal reasons and for non-project related activities. This includes but is not limited to advertising products or services in email signatures, soliciting business, and conducting any business not directly relating to your role within the Mautic project. Any usage of the tools that is not related to the project may affect the services availability for the other project users and activities, so it shall be considered as unallowed and unauthorized. + +Security +******** + +Used inappropriately, tools (especially online) can be source of security problems for the Mautic Community. Users shall not: + +- Open email/messaging attachments from unknown sources as they might contain a virus, trojan, spyware or any other kind of malware. +- Disable security or malware prevention software or features, as they are essential to protect from security issues, threats, frauds. +- Send and or disclose confidential data of the Mautic Community. +- Access another user’s account (i.e. email account, service profile, messaging account, etc.). + +Inappropriate Contents/Usage +**************************** + +Any of the tools and resources, including but not limited to communication systems (i.e. Email, Slack, Chat), must not be used to send or store inappropriate content or materials. It is important to understand that viewing, storing or distributing inappropriate content via the Mautic Community's tools is not acceptable under any circumstances. + +Users shall not: + +- Write or send emails or messages that might be defamatory or incur liability for the Mautic Community. +- Create or distribute any inappropriate content or material through any of the provided tools. Inappropriate content includes: pornography, racial or religious slurs, gender-specific comments, information encouraging criminal skills or terrorism, or materials relating to cults, gambling and illegal drugs. This definition of inappropriate content or material also covers any text, images or other media that could reasonably offend someone on the basis of race, age, sex, religious or political beliefs, national origin, disability, sexual orientation, or any other characteristic protected by law. +- Use tools for any illegal or criminal activities. +- Send offensive or harassing emails, messages or materials to others. +- Create or distribute messages or materials that could damage the Mautic Community’s image or reputation. + +Any user who receives or detects messages or materials they consider to be inappropriate should report this to the Community Manager or Project Lead. + +Copyright +********* + +The Mautic Community respects and operates within copyright laws. Users may not use their Mautic email to share any copyrighted software, media or materials owned by third parties, unless permitted by that third party. + +Contributors must not use the tools and resources available to them in order to perform any tasks that may involve breach of copyright law. + +Users should keep in mind that the copyright on letters, files and other documents attached to emails/messages may be owned by the email sender, or by a third party. Forwarding such materials on to other people may breach this copyright. + +Termination +*********** + +Any access to the tools and resources (including email, chat and services accounts) shall be revoked or removed if the user is no longer an active contributor to the project or is subject to sanctions as a result of improper conduct. + +Policy Enforcement +****************** + +The tools and resources are provided for legitimate business use. The Mautic Community therefore reserves the right to investigate the usage of provided tools upon violation report or suspicious usage detection. Any such investigation will be carried out by the Community Manager and/or Project Lead. + +Any breaches of this policy might result in a disciplinary action, up to the deactivation of the user account in any of the tools and resources and removal from the Community. + From 7b4dacb92ebfce989ddfc94d26c2bb5848684628 Mon Sep 17 00:00:00 2001 From: Favour Chibueze Date: Fri, 29 Nov 2024 20:08:10 +0000 Subject: [PATCH 3/4] fix vale --- .../code_of_conduct/tools_and_resources.rst | 24 +++++++++---------- 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/docs/policies/code_of_conduct/tools_and_resources.rst b/docs/policies/code_of_conduct/tools_and_resources.rst index 9f8df32b..016e4d57 100644 --- a/docs/policies/code_of_conduct/tools_and_resources.rst +++ b/docs/policies/code_of_conduct/tools_and_resources.rst @@ -1,10 +1,10 @@ Use of Community Tools & Resources ################################## -Why do we need this policy? -*************************** +What is the purpose of this policy? +*********************************** -Each contributor might be granted an access to one or more tools or resources provided and or operated by the Mautic Community to fulfill their responsibilities as contributor. This policy aims to reduce the security and business risks and to let users know how they are permitted to use the tools and resources, and what happens if they are misused. +Each contributor might receive access to one or more tools or resources managed by the Mautic Community to carry out their responsibilities. This policy aims to reduce the security and business risks and to let users know how they're permitted to use the tools and resources, and what happens if they're misused. Who does this policy apply to? ****************************** @@ -14,14 +14,14 @@ This policy applies to all contributors. It applies no matter where the tool or Tools and resources ******************* -The Mautic Community uses different tools and software, including, but not limited to, desktop software, web-based software, web applications, cloud-based services like mail, storage platform, real time communication services (i.e. Gmail, GSuite, Slack, Jitsi etc.). +The Mautic Community uses different tools and software, including, but not limited to, desktop software, web-based software, web applications, cloud-based services like mail, storage platform, real time communication services (i.e GMail, G Suite, Slack, Jitsi etc.). -The Mautic Community encourages its contributors to use provided tools whenever appropriate. For instance allowed usage includes: communicate with other contributors (i.e. through email, instant messaging or videoconferences), work/collaborate with other teams and stakeholders on project materials (i.e. team documents, project documents, collaborated folders). +The Mautic Community encourages its contributors to use provided tools whenever appropriate. For instance allowed usage includes: communicate with other contributors (i.e through email, instant messaging or video conferences), work/collaborate with other teams and stakeholders on project materials (i.e team documents, project documents, collaborated folders). Unauthorized use **************** -Any of the project tools (i.e. email account, software license, chat system) shall not be used for personal reasons and for non-project related activities. This includes but is not limited to advertising products or services in email signatures, soliciting business, and conducting any business not directly relating to your role within the Mautic project. Any usage of the tools that is not related to the project may affect the services availability for the other project users and activities, so it shall be considered as unallowed and unauthorized. +Any of the project tools (that is email account, software license, chat system) shall not be used for personal reasons and for non-project related activities. This includes but is not limited to advertising products or services in email signatures, soliciting business, and conducting any business not directly relating to your role within the Mautic project. Any usage of the tools that is not related to the project may affect the services availability for the other project users and activities, so it shall be considered as disallowed and unauthorized. Security ******** @@ -29,14 +29,14 @@ Security Used inappropriately, tools (especially online) can be source of security problems for the Mautic Community. Users shall not: - Open email/messaging attachments from unknown sources as they might contain a virus, trojan, spyware or any other kind of malware. -- Disable security or malware prevention software or features, as they are essential to protect from security issues, threats, frauds. +- Disable security or malware prevention software or features, as they're essential to protect from security issues, threats, frauds. - Send and or disclose confidential data of the Mautic Community. -- Access another user’s account (i.e. email account, service profile, messaging account, etc.). +- Access another user’s account (that is email account, service profile, messaging account, etc.). Inappropriate Contents/Usage **************************** -Any of the tools and resources, including but not limited to communication systems (i.e. Email, Slack, Chat), must not be used to send or store inappropriate content or materials. It is important to understand that viewing, storing or distributing inappropriate content via the Mautic Community's tools is not acceptable under any circumstances. +Any of the tools and resources, including but not limited to communication systems (that is Email, Slack, Chat), must not be used to send or store inappropriate content or materials. It is important to understand that viewing, storing or distributing inappropriate content via the Mautic Community's tools is not acceptable under any circumstances. Users shall not: @@ -53,7 +53,7 @@ Copyright The Mautic Community respects and operates within copyright laws. Users may not use their Mautic email to share any copyrighted software, media or materials owned by third parties, unless permitted by that third party. -Contributors must not use the tools and resources available to them in order to perform any tasks that may involve breach of copyright law. +Contributors must not use the tools and resources available to them to perform any tasks that may involve breach of copyright law. Users should keep in mind that the copyright on letters, files and other documents attached to emails/messages may be owned by the email sender, or by a third party. Forwarding such materials on to other people may breach this copyright. @@ -62,10 +62,10 @@ Termination Any access to the tools and resources (including email, chat and services accounts) shall be revoked or removed if the user is no longer an active contributor to the project or is subject to sanctions as a result of improper conduct. -Policy Enforcement +Policy enforcement ****************** -The tools and resources are provided for legitimate business use. The Mautic Community therefore reserves the right to investigate the usage of provided tools upon violation report or suspicious usage detection. Any such investigation will be carried out by the Community Manager and/or Project Lead. +The tools and resources support legitimate business use. The Mautic Community therefore reserves the right to investigate the usage of provided tools upon violation report or suspicious usage detection. The Community Manager and/or Project Lead will carry out any such investigation. Any breaches of this policy might result in a disciplinary action, up to the deactivation of the user account in any of the tools and resources and removal from the Community. From b1dd67806f4900b8bd1818c63886cccac76f0ff6 Mon Sep 17 00:00:00 2001 From: Favour Chibueze Date: Fri, 29 Nov 2024 20:22:48 +0000 Subject: [PATCH 4/4] fix vale errors --- .../code_of_conduct/tools_and_resources.rst | 24 ++++++++++++------- 1 file changed, 15 insertions(+), 9 deletions(-) diff --git a/docs/policies/code_of_conduct/tools_and_resources.rst b/docs/policies/code_of_conduct/tools_and_resources.rst index 016e4d57..326ae7f6 100644 --- a/docs/policies/code_of_conduct/tools_and_resources.rst +++ b/docs/policies/code_of_conduct/tools_and_resources.rst @@ -1,42 +1,48 @@ +.. vale off + Use of Community Tools & Resources ################################## What is the purpose of this policy? *********************************** +.. vale on + Each contributor might receive access to one or more tools or resources managed by the Mautic Community to carry out their responsibilities. This policy aims to reduce the security and business risks and to let users know how they're permitted to use the tools and resources, and what happens if they're misused. Who does this policy apply to? ****************************** -This policy applies to all contributors. It applies no matter where the tool or resource use takes place. It applies to use of tools and resources (as defined below) on any device. +This policy applies to all contributors. It applies no matter where the tool or resource use takes place. It applies to use of tools and resources as defined below on any device. Tools and resources ******************* -The Mautic Community uses different tools and software, including, but not limited to, desktop software, web-based software, web applications, cloud-based services like mail, storage platform, real time communication services (i.e GMail, G Suite, Slack, Jitsi etc.). +The Mautic Community uses different tools and software, including, but not limited to, desktop software, web-based software, web applications, cloud-based services like mail, storage platform, real time communication services, i.e GMail, G Suite, Slack, Jitsi etc. -The Mautic Community encourages its contributors to use provided tools whenever appropriate. For instance allowed usage includes: communicate with other contributors (i.e through email, instant messaging or video conferences), work/collaborate with other teams and stakeholders on project materials (i.e team documents, project documents, collaborated folders). +The Mautic Community encourages its contributors to use provided tools whenever appropriate. For instance allowed usage includes: communicate with other contributors, i.e through email, instant messaging or video conferences, work/collaborate with other teams and stakeholders on project materials, i.e team documents, project documents, collaborated folders. Unauthorized use **************** -Any of the project tools (that is email account, software license, chat system) shall not be used for personal reasons and for non-project related activities. This includes but is not limited to advertising products or services in email signatures, soliciting business, and conducting any business not directly relating to your role within the Mautic project. Any usage of the tools that is not related to the project may affect the services availability for the other project users and activities, so it shall be considered as disallowed and unauthorized. + +Contributors must not use project tools such as email accounts, software licenses, or chat systems for personal purposes or non-project-related activities. This includes but is not limited to advertising products or services in email signatures, soliciting business, and conducting any business not directly relating to your role within the Mautic project. Any usage of the tools that is not related to the project may affect the services availability for the other project users and activities, so it shall be considered as disallowed and unauthorized. Security ******** -Used inappropriately, tools (especially online) can be source of security problems for the Mautic Community. Users shall not: +Used inappropriately, tools especially online can be source of security problems for the Mautic Community. Users shall not: - Open email/messaging attachments from unknown sources as they might contain a virus, trojan, spyware or any other kind of malware. - Disable security or malware prevention software or features, as they're essential to protect from security issues, threats, frauds. - Send and or disclose confidential data of the Mautic Community. -- Access another user’s account (that is email account, service profile, messaging account, etc.). +- Access another user’s account (i.e email account, service profile, messaging account, etc.). Inappropriate Contents/Usage **************************** -Any of the tools and resources, including but not limited to communication systems (that is Email, Slack, Chat), must not be used to send or store inappropriate content or materials. It is important to understand that viewing, storing or distributing inappropriate content via the Mautic Community's tools is not acceptable under any circumstances. + +Contributors must not use any tools or resources, including communication systems such as Email, Slack, and Chat, to send or store inappropriate content or materials. It is important to understand that viewing, storing or distributing inappropriate content via the Mautic Community's tools is not acceptable under any circumstances. Users shall not: @@ -60,12 +66,12 @@ Users should keep in mind that the copyright on letters, files and other documen Termination *********** -Any access to the tools and resources (including email, chat and services accounts) shall be revoked or removed if the user is no longer an active contributor to the project or is subject to sanctions as a result of improper conduct. +Any access to the tools and resources including email, chat and services accounts shall be revoked or removed if the user is no longer an active contributor to the project or is subject to sanctions as a result of improper conduct. Policy enforcement ****************** -The tools and resources support legitimate business use. The Mautic Community therefore reserves the right to investigate the usage of provided tools upon violation report or suspicious usage detection. The Community Manager and/or Project Lead will carry out any such investigation. +The tools and resources support legitimate business use. The Mautic Community therefore reserves the right to investigate the usage of provided tools upon violation report or suspicious usage detection. The Community Manager and/or Project Lead carries out any such investigation. Any breaches of this policy might result in a disciplinary action, up to the deactivation of the user account in any of the tools and resources and removal from the Community.