Clarifying Notes and Statements
The Fedora Code of Conduct (CoC) outlines our shared values and standards. However, applying these high-level principles to specific situations requires clarity. The Fedora Code of Conduct and its associated documents are “living documents.” They will change over time as the Fedora community changes. This supplemental document serves as an extension of the main policy, to provide additional background and clarification to the Fedora CoC. It ensures that enforcement is consistent and that community members understand how the Fedora CoC applies to real-world scenarios, including event visibility and the protections afforded to those who report violations.
Visibility and Awareness
A Code of Conduct is only effective if the community is aware of it and understands the reporting procedures. To ensure this transparency, the following standards apply to all Fedora operations:
-
Digital Presence: The Fedora Code of Conduct and its associated documents must be linked in the footer of all major Fedora websites and, where possible, in other project communications.
-
Event Prominence: All events must prominently display the Fedora Code of Conduct. Organizers must publish event-specific notes, including designated points of contact.
-
In-Person Reporting: If an event supports in-person reporting, the specific process for doing so must be clearly and prominently displayed.
-
Physical Signage: In-person events organized by Fedora must provide physical copies of the Fedora Code of Conduct or display clear signage regarding it for attendees.
-
Online Events: Virtual events must display a link to the Fedora Code of Conduct prominently on the event home page.
-
Registration Acknowledgement: Where the platform allows, online events should require attendees to agree to abide by the Fedora Code of Conduct as a mandatory step in the registration process.
Why was the word “contributor” from the Contributor Covenant adapted 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.
Rationale for Retaliation Clause (v2.1)
This update codifies a zero-tolerance stance on retaliation to ensure community members feel safe and empowered to report concerns without fear of negative consequences. Any confirmed act of retaliation is considered a serious, standalone violation of the Fedora CoC and will be met with appropriate corrective action. The new section explicitly extends protections to reporters, witnesses, and Fedora Code of Conduct Committee members acting in good faith. Additionally, it distinguishes between unsubstantiated good-faith claims and malicious false reporting, establishing the latter as a violation to preserve the integrity of the enforcement process.
As of version 2.1, the Fedora Code of Conduct Committee has explicitly codified our stance on retaliation to close a critical gap in community safety. It was determined that for the Fedora CoC to be truly effective, reporters must feel empowered to come forward without fear of professional or social backlash. Silence caused by fear of retribution undermines the health of the entire project.
Want to help? Learn how to contribute to Fedora Docs ›