From d0414bda32bf59015fccb853fff04c61436aafc8 Mon Sep 17 00:00:00 2001 From: Justin W. Wheeler Date: Feb 15 2025 04:25:15 +0000 Subject: 📝🚚 docs(code-of-conduct): Initial commit This commit migrates all content related to the Fedora Code of Conduct into a new Antora module. This segments it off from the rest of the Fedora Project docs and also sets up in the future to have reviewer groups on Forgejo that are automatically tagged for review on specific Antora modules. It also provides improved discoverability of the Fedora CoC source material. I used Antora page aliases to handle redirects from the previous URL paths. ref: https://pagure.io/Fedora-Council/council-docs/pull-request/242 Signed-off-by: Justin W. Wheeler --- diff --git a/project/antora.yml b/project/antora.yml index ee5ac6e..3314f28 100644 --- a/project/antora.yml +++ b/project/antora.yml @@ -14,3 +14,4 @@ start_page: ROOT:index.adoc # This lists all the menu definitions of your component. nav: - modules/ROOT/nav.adoc + - modules/code-of-conduct/nav.adoc diff --git a/project/modules/ROOT/nav.adoc b/project/modules/ROOT/nav.adoc index 14696d7..559045f 100644 --- a/project/modules/ROOT/nav.adoc +++ b/project/modules/ROOT/nav.adoc @@ -4,9 +4,6 @@ * xref:brand.adoc[Brand] * xref:initiatives.adoc[Current Initiatives] * xref:communications.adoc[Project Communications] -* xref:code-of-conduct.adoc[Code of Conduct] -** xref:coc-committee.adoc[Committee] -** xref:coc-clarifying.adoc[Clarifying Notes and Statements] * xref:help.adoc[Getting Help] * xref:join.adoc[Get Involved] * xref:sponsor.adoc[Sponsoring] diff --git a/project/modules/ROOT/pages/coc-clarifying.adoc b/project/modules/ROOT/pages/coc-clarifying.adoc deleted file mode 100644 index 7ec8a9a..0000000 --- a/project/modules/ROOT/pages/coc-clarifying.adoc +++ /dev/null @@ -1,32 +0,0 @@ -= Clarifying Notes and Statements - -== Clarifications - -The Code of Conduct and its associated documents are “living documents.” -They will change over time as the Fedora community changes. This supplemental document exists to provide additional background and clarification to the Code of Conduct. -All changes to the Code of Conduct and associated documents will be tracked with change information and date of change details in a Change History document maintained by the FCAIC. - -== Awareness - -A Code of Conduct is only effective if people know about it and know how to report an incident when needed. -This Code of Conduct and its associated documents will be linked in the footer of all major Fedora Websites and where possible in other project communications. - -All events will prominently display our Code of Conduct and publish any additional event specific notes, such as points of contact. -If an event allows in-person reporting (see the Reporting Details and Response Process documents for more information), the process for doing this must be prominently displayed. - -In person events organized by Fedora must make physical copies of the Code of Conduct available for attendees or make signage about it. -Online events must have a link to the Code of Conduct prominently displayed on the event home page. -If the platform allows, online events should ask for attendees to agree to abide by the Code of Conduct as part of the event registration. - -== Who is the Code of Conduct Committee - -To be worked out. -Right now, the Code of Conduct Committee consists of the FPL and the FCAIC, but this is not sustainable. -We need a larger body, which will include Fedora community members selected by the Fedora Council. - -== Why was the word “contributor” from the Contributor Covenant removed when it was adapted for Fedora? - -We need a code of conduct that speaks to everyone who interacts with our community. -Many of us may understand the word “contributor” to encompass everyone from a mailing list participant, forum poster, bug reporter, documentarian, designer, developer, etc., but not everyone understands it this way. -Additionally, many of our events are attended by users. -Speaking about the community is a more clear definition of the individuals covered in this Code. diff --git a/project/modules/ROOT/pages/coc-committee.adoc b/project/modules/ROOT/pages/coc-committee.adoc deleted file mode 100644 index 48b6436..0000000 --- a/project/modules/ROOT/pages/coc-committee.adoc +++ /dev/null @@ -1,91 +0,0 @@ -= Fedora Code of Conduct Committee - -== Who is the Fedora Code of Conduct Committee? - -The Code of Conduct Committee consists of the Fedora Project Leader, the Fedora Community Architect, and Fedora community members. -Members of the Code of Conduct Committee will be provided with incident response training and guidelines around Fedora’s xref:code-of-conduct.adoc[Code of Conduct]. - -== Responsibilities of the Fedora Code of Conduct Committee - -The Fedora Code of Conduct Committee will: - -* Accept, acknowledge, and investigate reports of possible violations of the Code of Conduct from community members and/or moderators. -This will include communications with people who submit reports, reported persons, witnesses, and Red Hat Legal, as appropriate. -This will also involve communications with other members of the Committee by text or video call to deliberate and resolve reports. -Additional details about the reporting and response processes are documented on the xref:code-of-conduct.adoc#_reporting_and_enforcement[Reporting Process Information page]. -* In cases where a Code of Conduct violation has occurred, determine what action should be taken by the Fedora Project. -These will typically take the form of remedial guidance, a set of consequences for the reported person, and/or possible recommendations for new policies or rules for the Fedora Project. -* Accept and acknowledge requests for clarifications about the Code of Conduct, and provide a response once any necessary communications and deliberations are complete. -* Make reporting as appropriate about incidents, including an annual report summarizing incidents over the last year. -* This report will be statistical in nature to illustrate the process is functioning. -Past reports can be found under the https://communityblog.fedoraproject.org/tag/code-of-conduct/[Code of Conduct tag] on the Community Blog - -The current Code of Conduct Committee is comprised of: - -* Matthew Miller (Fedora Project Leader) -* Justin W. Flory (Fedora Community Architect) -* Marie Nordin (community member) -* Dorka Volavkova (community member) -* Jona Azizaj (DEI Advisor) -* David Cantrell (Fedora Council & FESCo member) - -== Adding or Removing Members to the Code of Conduct Committee - -The Fedora Project Leader and Fedora Community Architect are members of the Code of Conduct Committee, regardless of who holds these roles. -Ideally, the Committee should have at least three members at all times, and no more than seven. -The Fedora Council will be notified of all changes in membership to the Fedora Conduct Committee. -Adding and removing members to the Committee will happen from time to time for a variety of reasons, including, but not limited to: - -* Particular Community members’ interest in maintenance of Fedora community health -* A Committee member no longer has the time or desire to maintain Committee responsibilities -* A Committee member fails to uphold the Code of Conduct Committee Commitments -* Disengagement or absence in Committee activities lasting beyond one Fedora Linux release cycle (i.e. ≥4 months) - -=== Adding a Member to the Code of Conduct Committee - -To add a member to the Fedora Code of Conduct Committee: - -* Current members of the Code of Conduct Committee or the Fedora Council identifies a prospective member and obtains interest in and commitment to participation, then files an issue proposing the member’s nomination. -* The Code of Conduct Committee reviews the nomination to determine eligibility. -Suitability will be determined by evaluation of the nominee’s behavior and track record of interactions in the Fedora community. -* If the nomination is accepted, the Committee invites the nominee to join the Code of Conduct Committee in a formal communication. -This invitation must include the xref:#commitments[Code of Conduct Committee Commitments] that members must agree to follow to ensure Fedora’s Code of Conduct is managed fairly and in a confidential manner. -* If the nomination is rejected, the Committee sends a notification of the rejection. -A rejected nominee will be eligible for renomination after two release cycles. -* Upon acceptance of the invitation and acknowledgement and agreement to the xref:#commitments[Code of Conduct Committee Commitments], Fedora will provide the new member with Code of Conduct incident management training. -* Addition of the new member to Code of Conduct incident tracker and documentation. - -=== Removing a Member from the Code of Conduct Committee - -The process to remove a member of the Fedora Code of Conduct Committee is notice from: - -* The member to the Committee that they intend to step down, or -* The Committee to the member that they have been removed, and why they have been removed. - -Followed by removal of the individual from the CoC incident tracker and documentation. - -[#commitments] -== Fedora Code of Conduct Committee Commitments - -Members of the Fedora Code of Conduct Committee involved in investigating reports and making recommendations for resolution of Code of Conduct violations are required to uphold the following principles, ensuring that bias, lack of confidentiality and conflicts of interest do not impact the outcome of a Code of Conduct determination. - -**I agree to adhere to the Fedora Code of Conduct, in both letter and spirit, and acknowledge that violating the Code could result in removal from the Committee.** - -**I agree to keep the process, any facts I learn, and any evidence I review confidential, and agree to discuss them only with individuals who are part of the process** -(e.g. Fedora Code of Conduct Committee members, Red Hat Legal, or other designated individuals). - -**I will recuse myself if I cannot be fair and impartial in an individual case, due to my personal involvement with the parties involved.** -If I have questions about recusal, I will consult the Fedora Community Architect and/or the Fedora Project Leader. - -**I agree that I will review Code of Conduct reports, conduct investigations, and make recommendations fairly and impartially.** - -**I will review the reports and deliberate only in confidential sessions, with the outcome to be shared only with the parties and others as determined on a need-to-know basis.** -(e.g. system administrators, moderators, or project leads.) - -**I will respect the process and outcome, recognizing that the Committee decision is the product of the Code of Conduct Committee, even if I do not personally agree, my recommendations are rejected, or I am part of the minority.** - -Please respond with acknowledgement that you have reviewed these commitments and agree to follow them in your role as a member of the Fedora Code of Conduct Committee. - -== History - -The Committee structure was https://pagure.io/Fedora-Council/tickets/issue/442[approved by the Fedora Council] in April 2023. diff --git a/project/modules/ROOT/pages/code-of-conduct.adoc b/project/modules/ROOT/pages/code-of-conduct.adoc deleted file mode 100644 index c532438..0000000 --- a/project/modules/ROOT/pages/code-of-conduct.adoc +++ /dev/null @@ -1,115 +0,0 @@ -= Code of Conduct -:page-aliases: council::policy/coc-response-policy.adoc - -== Fedora Community Code of Conduct - -The Fedora Code of Conduct is a set of guidelines that explains how our community behaves and what we value to members and outsiders. -The Code of Conduct is a living document and will be updated when and if it is deemed necessary. - -The Code of Conduct is not “code” in the sense of being an algorithm or a computer program. -The Code of Conduct is not “blindly and algorithmically” executed but is instead enforced by humans making real decisions based on all of the available information and using all available context. - -The Code of Conduct does not seek to restrict speech or penalize non-native speakers of English. -Instead the Code of Conduct spells out the kinds of behaviors we, as a community, find to be acceptable or unacceptable. -The Code of Conduct is, in many ways, the outward embodiment of the Friends component of Fedora’s Foundations. - -== Our Pledge - -In the interest of fostering an open and welcoming environment, we as the Fedora community pledge to collaborate in a respectful and constructive manner, and welcome everyone willing to join us in that pledge. -We welcome individuals regardless of ability, age, background, body size, education, ethnicity, family status, gender identity and expression, geographic location, level of experience, marital status, nationality, national origin, native language, personal appearance, race and/or ethnicity, religion, sexual identity and orientation, socioeconomic status, or any other dimension of diversity. - -Our channels, mailing lists, and posts should focus on Fedora and on free and open source software and content. -We pledge to make participation in our project and our community a harassment-free experience for everyone. -We pledge to avoid personal attacks on others, and to avoid inflammatory language and speech that perpetuates discrimination. -Furthermore, we pledge to not use the Fedora Project and its platforms as a basis to engage in personal campaigns against other organizations or individuals. - -== Our Standards - -Examples of behavior that contributes to creating a positive environment include: - -* Using welcoming and inclusive language -* Being kind to others -* Behaving with civility -* Being respectful of differing viewpoints and experiences -* Gracefully accepting constructive criticism -* Focusing on what is best for the community -* Showing empathy towards other community members - -Examples of unacceptable behavior include: - -* The use of sexualized language or imagery and unwelcome sexual attention or advances -* Initiating controversy for controversy’s sake (repeatedly asking disingenuous questions under a guise of sincerity) -* Saying insulting/derogatory comments and making personal attacks. -* Repeatedly instigating conflict, and baiting people into arguments -* Public or private harassment -* Publishing someone else’s private information, such as a physical or electronic address, without explicit permission -* Deliberate intimidation, stalking, or following -* Violent threats or language directed against another person -* Sexist, racist, homophobic, transphobic, ableist, or exclusionary statements, even if they were meant as jokes -* Excessive swearing -* Unwelcome physical contact -* Sustained disruption of talks or other events -* Other conduct which could reasonably be considered inappropriate in a professional setting even if the conduct may be legal under the laws of some jurisdiction. - -== Our Responsibilities - -The Fedora Council is committed to enforcing this Code of Conduct in a fair and impartial manner so that Fedora community members are able to participate in the Fedora Project and its associated activities in a safe and respectful environment. -To achieve this, the Council has delegated responsibility to a xref:coc-committee.adoc[Code of Conduct Committee] for clarifying and interpreting the standards of acceptable behavior, responding to and investigating reports of behavior that is not aligned to this Code of Conduct and determining appropriate and fair corrective action in response. -The Committee will perform these functions along with the Red Hat Legal team, as appropriate. - -Within their respective areas of participation Fedora Community members have the right in their sole discretion and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. -Those Fedora Community members are expected to exercise these rights in alignment with the Code of Conduct. - -== Scope - -This Code of Conduct applies in all online and offline project spaces and in all online and offline spaces where an individual is representing the project, its community, or is acting as a community member. - -Examples of acting as a community member include: - -* Posting to a Fedora mailing list, -* Filing a bug with Fedora, -* Participating in an official Fedora communication channel, such as IRC or telegram -* Contributing to the Fedora Project in any form -* Using an official project email address -* Posting via an official social media account -* Acting as an appointed representative at an online or offline event -* Speaking for Fedora or its subprojects at a public event or online video -* Working in a Fedora or related booth or table at an event -* Participating in a Fedora or related technical meetup -* Serving as an elected or appointed leader in Fedora, including being a member of the Fedora Council - -== Reporting and Enforcement - -Instances of behavior inconsistent with this code may be reported by contacting the Fedora project by filing a private Fedora Code of Conduct ticket at https://pagure.io/CoC/new_issue. -If the incident occurs at an event, the local event staff should be contacted in addition to opening a ticket. - -Individuals without access to https://pagure.io/CoC/new_issue may send an email to the following address: codeofconduct@fedoraproject.org. -This email will be converted into a private Code of Conduct ticket by the xref:coc-committee.adoc[Code of Conduct Committee]. - -All reports will be kept confidential. -When we discuss incidents with anyone we will anonymize details as much as we can. -This means that the identities of all involved parties will remain confidential unless those individuals instruct us otherwise or we are required to make disclosures under the law. Additionally, in some cases we may need to disclose this information to other parties at Red Hat. -Fedora is not a separate legal entity and therefore has to comply with all requirements imposed upon Red Hat. - -Upon our review/investigation of the reported incident, we will determine what action is appropriate based on this Code and its clarifying statements. -An incident review will include communication with the reporter and the individual being reported, and an opportunity for both parties to provide an account of the incident. - -All complaints will be reviewed and will result in a response. -Failure to follow this Code may result in actions including, but not limited to, warnings, temporary suspension, and in extreme circumstances, banning from the Fedora Project. -Please note, while we take all concerns/reported incidents raised seriously, we will use our discretion to determine when and how to follow up on reported incidents. - -== Attribution & License - -This Code of Conduct is an edited form of the Contributor Covenant, version 1.4 along with material from the PyCon Code of Conduct and others. -The process of dealing with reports is inspired by ideas from the Mozilla CPG Incident Process. -This Code of Conduct is licensed under the https://creativecommons.org/licenses/by/4.0/[Creative Commons Attribution 4.0 International (CC BY)] license. - -Additional material is drawn from many sources, including: - -* http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports -* http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy_resources -* https://www.ashedryden.com/blog/codes-of-conduct-101-faq -* http://safetyfirstpdx.org/training/code_of_conduct/TemplateIncidentResponseGuide.pdf -* https://www.washingtonpost.com/opinions/how-my-restaurant-successfully-dealt-with-harassment-from-customers/2018/03/29/3d9d00b8-221a-11e8-badd-7c9f29a55815_story.html -* https://www.shrm.org/hr-today/news/hr-magazine/Pages/1214-workplace-investigations.aspx -* https://www.eeoc.gov/policy/docs/harassment.html diff --git a/project/modules/code-of-conduct/nav.adoc b/project/modules/code-of-conduct/nav.adoc new file mode 100644 index 0000000..26a0c78 --- /dev/null +++ b/project/modules/code-of-conduct/nav.adoc @@ -0,0 +1,3 @@ +* xref:index.adoc[Code of Conduct] +** xref:clarifying-statements.adoc[Clarifying Notes and Statements] +** xref:committee.adoc[Committee] diff --git a/project/modules/code-of-conduct/pages/clarifying-statements.adoc b/project/modules/code-of-conduct/pages/clarifying-statements.adoc new file mode 100644 index 0000000..4e326c6 --- /dev/null +++ b/project/modules/code-of-conduct/pages/clarifying-statements.adoc @@ -0,0 +1,33 @@ += Clarifying Notes and Statements +:page-aliases: project::coc-clarifying.adoc + +== Clarifications + +The Code of Conduct and its associated documents are “living documents.” +They will change over time as the Fedora community changes. This supplemental document exists to provide additional background and clarification to the Code of Conduct. +All changes to the Code of Conduct and associated documents will be tracked with change information and date of change details in a Change History document maintained by the FCAIC. + +== Awareness + +A Code of Conduct is only effective if people know about it and know how to report an incident when needed. +This Code of Conduct and its associated documents will be linked in the footer of all major Fedora Websites and where possible in other project communications. + +All events will prominently display our Code of Conduct and publish any additional event specific notes, such as points of contact. +If an event allows in-person reporting (see the Reporting Details and Response Process documents for more information), the process for doing this must be prominently displayed. + +In person events organized by Fedora must make physical copies of the Code of Conduct available for attendees or make signage about it. +Online events must have a link to the Code of Conduct prominently displayed on the event home page. +If the platform allows, online events should ask for attendees to agree to abide by the Code of Conduct as part of the event registration. + +== Who is the Code of Conduct Committee + +To be worked out. +Right now, the Code of Conduct Committee consists of the FPL and the FCAIC, but this is not sustainable. +We need a larger body, which will include Fedora community members selected by the Fedora Council. + +== Why was the word “contributor” from the Contributor Covenant removed when it was adapted for Fedora? + +We need a code of conduct that speaks to everyone who interacts with our community. +Many of us may understand the word “contributor” to encompass everyone from a mailing list participant, forum poster, bug reporter, documentarian, designer, developer, etc., but not everyone understands it this way. +Additionally, many of our events are attended by users. +Speaking about the community is a more clear definition of the individuals covered in this Code. diff --git a/project/modules/code-of-conduct/pages/committee.adoc b/project/modules/code-of-conduct/pages/committee.adoc new file mode 100644 index 0000000..36b87d4 --- /dev/null +++ b/project/modules/code-of-conduct/pages/committee.adoc @@ -0,0 +1,92 @@ += Fedora Code of Conduct Committee +:page-aliases: project::coc-committee.adoc + +== Who is the Fedora Code of Conduct Committee? + +The Code of Conduct Committee consists of the Fedora Project Leader, the Fedora Community Architect, and Fedora community members. +Members of the Code of Conduct Committee will be provided with incident response training and guidelines around Fedora’s xref:code-of-conduct.adoc[Code of Conduct]. + +== Responsibilities of the Fedora Code of Conduct Committee + +The Fedora Code of Conduct Committee will: + +* Accept, acknowledge, and investigate reports of possible violations of the Code of Conduct from community members and/or moderators. +This will include communications with people who submit reports, reported persons, witnesses, and Red Hat Legal, as appropriate. +This will also involve communications with other members of the Committee by text or video call to deliberate and resolve reports. +Additional details about the reporting and response processes are documented on the xref:code-of-conduct.adoc#_reporting_and_enforcement[Reporting Process Information page]. +* In cases where a Code of Conduct violation has occurred, determine what action should be taken by the Fedora Project. +These will typically take the form of remedial guidance, a set of consequences for the reported person, and/or possible recommendations for new policies or rules for the Fedora Project. +* Accept and acknowledge requests for clarifications about the Code of Conduct, and provide a response once any necessary communications and deliberations are complete. +* Make reporting as appropriate about incidents, including an annual report summarizing incidents over the last year. +* This report will be statistical in nature to illustrate the process is functioning. +Past reports can be found under the https://communityblog.fedoraproject.org/tag/code-of-conduct/[Code of Conduct tag] on the Community Blog + +The current Code of Conduct Committee is comprised of: + +* Matthew Miller (Fedora Project Leader) +* Justin W. Flory (Fedora Community Architect) +* Marie Nordin (community member) +* Dorka Volavkova (community member) +* Jona Azizaj (DEI Advisor) +* David Cantrell (Fedora Council & FESCo member) + +== Adding or Removing Members to the Code of Conduct Committee + +The Fedora Project Leader and Fedora Community Architect are members of the Code of Conduct Committee, regardless of who holds these roles. +Ideally, the Committee should have at least three members at all times, and no more than seven. +The Fedora Council will be notified of all changes in membership to the Fedora Conduct Committee. +Adding and removing members to the Committee will happen from time to time for a variety of reasons, including, but not limited to: + +* Particular Community members’ interest in maintenance of Fedora community health +* A Committee member no longer has the time or desire to maintain Committee responsibilities +* A Committee member fails to uphold the Code of Conduct Committee Commitments +* Disengagement or absence in Committee activities lasting beyond one Fedora Linux release cycle (i.e. ≥4 months) + +=== Adding a Member to the Code of Conduct Committee + +To add a member to the Fedora Code of Conduct Committee: + +* Current members of the Code of Conduct Committee or the Fedora Council identifies a prospective member and obtains interest in and commitment to participation, then files an issue proposing the member’s nomination. +* The Code of Conduct Committee reviews the nomination to determine eligibility. +Suitability will be determined by evaluation of the nominee’s behavior and track record of interactions in the Fedora community. +* If the nomination is accepted, the Committee invites the nominee to join the Code of Conduct Committee in a formal communication. +This invitation must include the xref:#commitments[Code of Conduct Committee Commitments] that members must agree to follow to ensure Fedora’s Code of Conduct is managed fairly and in a confidential manner. +* If the nomination is rejected, the Committee sends a notification of the rejection. +A rejected nominee will be eligible for renomination after two release cycles. +* Upon acceptance of the invitation and acknowledgement and agreement to the xref:#commitments[Code of Conduct Committee Commitments], Fedora will provide the new member with Code of Conduct incident management training. +* Addition of the new member to Code of Conduct incident tracker and documentation. + +=== Removing a Member from the Code of Conduct Committee + +The process to remove a member of the Fedora Code of Conduct Committee is notice from: + +* The member to the Committee that they intend to step down, or +* The Committee to the member that they have been removed, and why they have been removed. + +Followed by removal of the individual from the CoC incident tracker and documentation. + +[#commitments] +== Fedora Code of Conduct Committee Commitments + +Members of the Fedora Code of Conduct Committee involved in investigating reports and making recommendations for resolution of Code of Conduct violations are required to uphold the following principles, ensuring that bias, lack of confidentiality and conflicts of interest do not impact the outcome of a Code of Conduct determination. + +**I agree to adhere to the Fedora Code of Conduct, in both letter and spirit, and acknowledge that violating the Code could result in removal from the Committee.** + +**I agree to keep the process, any facts I learn, and any evidence I review confidential, and agree to discuss them only with individuals who are part of the process** +(e.g. Fedora Code of Conduct Committee members, Red Hat Legal, or other designated individuals). + +**I will recuse myself if I cannot be fair and impartial in an individual case, due to my personal involvement with the parties involved.** +If I have questions about recusal, I will consult the Fedora Community Architect and/or the Fedora Project Leader. + +**I agree that I will review Code of Conduct reports, conduct investigations, and make recommendations fairly and impartially.** + +**I will review the reports and deliberate only in confidential sessions, with the outcome to be shared only with the parties and others as determined on a need-to-know basis.** +(e.g. system administrators, moderators, or project leads.) + +**I will respect the process and outcome, recognizing that the Committee decision is the product of the Code of Conduct Committee, even if I do not personally agree, my recommendations are rejected, or I am part of the minority.** + +Please respond with acknowledgement that you have reviewed these commitments and agree to follow them in your role as a member of the Fedora Code of Conduct Committee. + +== History + +The Committee structure was https://pagure.io/Fedora-Council/tickets/issue/442[approved by the Fedora Council] in April 2023. diff --git a/project/modules/code-of-conduct/pages/index.adoc b/project/modules/code-of-conduct/pages/index.adoc new file mode 100644 index 0000000..c532438 --- /dev/null +++ b/project/modules/code-of-conduct/pages/index.adoc @@ -0,0 +1,115 @@ += Code of Conduct +:page-aliases: council::policy/coc-response-policy.adoc + +== Fedora Community Code of Conduct + +The Fedora Code of Conduct is a set of guidelines that explains how our community behaves and what we value to members and outsiders. +The Code of Conduct is a living document and will be updated when and if it is deemed necessary. + +The Code of Conduct is not “code” in the sense of being an algorithm or a computer program. +The Code of Conduct is not “blindly and algorithmically” executed but is instead enforced by humans making real decisions based on all of the available information and using all available context. + +The Code of Conduct does not seek to restrict speech or penalize non-native speakers of English. +Instead the Code of Conduct spells out the kinds of behaviors we, as a community, find to be acceptable or unacceptable. +The Code of Conduct is, in many ways, the outward embodiment of the Friends component of Fedora’s Foundations. + +== Our Pledge + +In the interest of fostering an open and welcoming environment, we as the Fedora community pledge to collaborate in a respectful and constructive manner, and welcome everyone willing to join us in that pledge. +We welcome individuals regardless of ability, age, background, body size, education, ethnicity, family status, gender identity and expression, geographic location, level of experience, marital status, nationality, national origin, native language, personal appearance, race and/or ethnicity, religion, sexual identity and orientation, socioeconomic status, or any other dimension of diversity. + +Our channels, mailing lists, and posts should focus on Fedora and on free and open source software and content. +We pledge to make participation in our project and our community a harassment-free experience for everyone. +We pledge to avoid personal attacks on others, and to avoid inflammatory language and speech that perpetuates discrimination. +Furthermore, we pledge to not use the Fedora Project and its platforms as a basis to engage in personal campaigns against other organizations or individuals. + +== Our Standards + +Examples of behavior that contributes to creating a positive environment include: + +* Using welcoming and inclusive language +* Being kind to others +* Behaving with civility +* Being respectful of differing viewpoints and experiences +* Gracefully accepting constructive criticism +* Focusing on what is best for the community +* Showing empathy towards other community members + +Examples of unacceptable behavior include: + +* The use of sexualized language or imagery and unwelcome sexual attention or advances +* Initiating controversy for controversy’s sake (repeatedly asking disingenuous questions under a guise of sincerity) +* Saying insulting/derogatory comments and making personal attacks. +* Repeatedly instigating conflict, and baiting people into arguments +* Public or private harassment +* Publishing someone else’s private information, such as a physical or electronic address, without explicit permission +* Deliberate intimidation, stalking, or following +* Violent threats or language directed against another person +* Sexist, racist, homophobic, transphobic, ableist, or exclusionary statements, even if they were meant as jokes +* Excessive swearing +* Unwelcome physical contact +* Sustained disruption of talks or other events +* Other conduct which could reasonably be considered inappropriate in a professional setting even if the conduct may be legal under the laws of some jurisdiction. + +== Our Responsibilities + +The Fedora Council is committed to enforcing this Code of Conduct in a fair and impartial manner so that Fedora community members are able to participate in the Fedora Project and its associated activities in a safe and respectful environment. +To achieve this, the Council has delegated responsibility to a xref:coc-committee.adoc[Code of Conduct Committee] for clarifying and interpreting the standards of acceptable behavior, responding to and investigating reports of behavior that is not aligned to this Code of Conduct and determining appropriate and fair corrective action in response. +The Committee will perform these functions along with the Red Hat Legal team, as appropriate. + +Within their respective areas of participation Fedora Community members have the right in their sole discretion and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct. +Those Fedora Community members are expected to exercise these rights in alignment with the Code of Conduct. + +== Scope + +This Code of Conduct applies in all online and offline project spaces and in all online and offline spaces where an individual is representing the project, its community, or is acting as a community member. + +Examples of acting as a community member include: + +* Posting to a Fedora mailing list, +* Filing a bug with Fedora, +* Participating in an official Fedora communication channel, such as IRC or telegram +* Contributing to the Fedora Project in any form +* Using an official project email address +* Posting via an official social media account +* Acting as an appointed representative at an online or offline event +* Speaking for Fedora or its subprojects at a public event or online video +* Working in a Fedora or related booth or table at an event +* Participating in a Fedora or related technical meetup +* Serving as an elected or appointed leader in Fedora, including being a member of the Fedora Council + +== Reporting and Enforcement + +Instances of behavior inconsistent with this code may be reported by contacting the Fedora project by filing a private Fedora Code of Conduct ticket at https://pagure.io/CoC/new_issue. +If the incident occurs at an event, the local event staff should be contacted in addition to opening a ticket. + +Individuals without access to https://pagure.io/CoC/new_issue may send an email to the following address: codeofconduct@fedoraproject.org. +This email will be converted into a private Code of Conduct ticket by the xref:coc-committee.adoc[Code of Conduct Committee]. + +All reports will be kept confidential. +When we discuss incidents with anyone we will anonymize details as much as we can. +This means that the identities of all involved parties will remain confidential unless those individuals instruct us otherwise or we are required to make disclosures under the law. Additionally, in some cases we may need to disclose this information to other parties at Red Hat. +Fedora is not a separate legal entity and therefore has to comply with all requirements imposed upon Red Hat. + +Upon our review/investigation of the reported incident, we will determine what action is appropriate based on this Code and its clarifying statements. +An incident review will include communication with the reporter and the individual being reported, and an opportunity for both parties to provide an account of the incident. + +All complaints will be reviewed and will result in a response. +Failure to follow this Code may result in actions including, but not limited to, warnings, temporary suspension, and in extreme circumstances, banning from the Fedora Project. +Please note, while we take all concerns/reported incidents raised seriously, we will use our discretion to determine when and how to follow up on reported incidents. + +== Attribution & License + +This Code of Conduct is an edited form of the Contributor Covenant, version 1.4 along with material from the PyCon Code of Conduct and others. +The process of dealing with reports is inspired by ideas from the Mozilla CPG Incident Process. +This Code of Conduct is licensed under the https://creativecommons.org/licenses/by/4.0/[Creative Commons Attribution 4.0 International (CC BY)] license. + +Additional material is drawn from many sources, including: + +* http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Responding_to_reports +* http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy_resources +* https://www.ashedryden.com/blog/codes-of-conduct-101-faq +* http://safetyfirstpdx.org/training/code_of_conduct/TemplateIncidentResponseGuide.pdf +* https://www.washingtonpost.com/opinions/how-my-restaurant-successfully-dealt-with-harassment-from-customers/2018/03/29/3d9d00b8-221a-11e8-badd-7c9f29a55815_story.html +* https://www.shrm.org/hr-today/news/hr-magazine/Pages/1214-workplace-investigations.aspx +* https://www.eeoc.gov/policy/docs/harassment.html