| |
@@ -0,0 +1,88 @@
|
| |
+ = 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 and Code of Conduct Specialist at Red Hat’s Open Source Program Office)
|
| |
+
|
| |
+ == 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.
|
| |
bcotton
commented a year ago
As approved in https://pagure.io/Fedora-Council/tickets/issue/442