This commit represents a notable change to the Fedora Code of Conduct,
including new language that describes our stance against retaliation and
defining protections for reporters and participants, and addressing the
issue of false reports.
The work in making this update began in September 2024 by Marie Nordin
(@riecatnor) who first raised this as an issue and identifying an
industry trend towards including language about retaliation in a Code
of Conduct. A proposal was made and went through several rounds of
revision. The revision represented in this commit was signed off by Red
Hat Legal (Richard Fontana) in January 2026.
Upon merging to the `main` branch, the Fedora Code of Conduct v2.1 comes
into effect and will be used as guiding reference for future tickets by
the Fedora Code of Conduct Committee.
CC, CoC Committee: @jspaleta@jonatoni@dcantrell@ankursinha@chris
CC, Council: @bookwar@churchyard@t0xic0der@amoloney@ryanlerch@pboy@pbokoc@nimbinatus
Fixes CoC#345.
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit makes the identity of a Fedora Code of Conduct more explicit
and clear, different from just "any" Code of Conduct. This will be
important for versioning of future changes to the Fedora Code of Conduct
document, to give the document a more firm identity and tracked changes.
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit makes several minor changes to the Fedora Code of Conduct
document behind-the-scenes. The changes are as described as follows:
- Description: Adds a SEO-friendly description for the page, summarizing
the page and its contents. This will appear when linked online, e.g.
on social media websites or chat rooms.
- Authors: Add original authors, co-authors, and communities of
reference involved in the drafting of the Fedora CoC.
- Specifically version the current draft by Marie Nordin as v2.0, last
updated in May 2021. This will be important, as we will start to
version future changes to the Code of Conduct going forward, for
maximum awareness and transparency for changes.
- Anchors: Add section anchors to headers, to make them more static and
less likely to change over time. This will break old links… but I
think it is better to be explicit and use SEO-friendly header anchors
as a standard going further.
All of these changes do not represent content or interpretative changes
to the Fedora Code of Conduct or the behavior we expect people to hold
themselves accountable to. Therefore, I am making these changes
unilaterally and pushing directly to `main`.
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
This commit addresses feedback that came up in a Fedora Discussion topic
about whether Telegram groups are official or unofficial. The Code of
Conduct was written at a time when we were only beginning to use Matrix
more formally in the project. Since the time that the Code of Conduct
was published, we have now shifted completely to Fedora Discussion and
Fedora Chat/Matrix as our official chat platforms, as verified by the
Communications page.
It might be more wise to link out to the Communications page in the
Project docs, but for now, this commit addresses an important
clarification about where the Code of Conduct is more rigidly applied
and where it is more challenging to enforce.
ref: https://discussion.fedoraproject.org/t/the-status-of-the-telegram-groups-within-the-project/172185/13
Signed-off-by: Justin Wheeler <jwheel@redhat.com>
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 <jwf@redhat.com>
2025-02-14 23:25:15 -05:00
Renamed from project/modules/ROOT/pages/code-of-conduct.adoc (Browse further)