GNOME's Code of Conduct is our community’s shared standard of behavior for participants in GNOME. This is the Code of Conduct Committee's periodic summary report of its activities from May 2025 to October 2025.
The current members of the CoC Committee are:
- Anisa Kuci
- Carlos Garnacho
- Christopher Davis
- Federico Mena Quintero
- Michael Downey
- Rosanna Yuen
All the members of the CoC Committee have completed Code of Conduct Incident Response training provided by Otter Tech, and are professionally trained to handle incident reports in GNOME community events.
The committee has an email address that can be used to send reports: conduct@gnome.org as well as a website for report submission: https://conduct.gnome.org/
Reports
Since May 2025, the committee has received reports on a total of 25 possible incidents. Many of these were not actionable; all the incidents listed here were resolved during the reporting period.
- Report on a conspiracy theory, closed as not actionable.
- Report that was not actionable.
- Report about a blog post; not a CoC violation and not actionable.
- Report about interactions in GitLab; not a CoC violation and not actionable.
- Report about a blog post; not a CoC violation and not actionable.
- Question about an Export Control Classification Number (ECCN) for GDM; redirected to discourse.gnome.org.
- Report about a reply in GitLab; not a CoC violation; pointed out resources about unpaid/volunteer work in open source.
- Report about a reply in GitLab; not a CoC violation but using language against the community guidelines; sent a reminder to the reported person to use non-violent communication.
- Two reports about a GNOME Shell extension; recommended actions to take to the extension reviewers.
- Report about another GNOME Shell extension; recommended actions to take to the extension reviewers.
- Multiple reports about a post on planet.gnome.org; removed the post from the feed and its site.
- Report with a fake attribution; closed as not actionable.
- Report with threats; closed as not actionable.
- Report with a fake attribution; closed as not actionable.
- Report that was not actionable.
- Support request; advised reporter to direct their question to the infrastructure team.
- Report closed due to not being actionable; gave the reporter advice on how to deal with their issue.
- Report about a reply in GitLab; reminded both the reporter and reported person how to communicate appropriately.
- Report during GUADEC about an incident during the conference; in-person reminder to the reported individual to mind their behavior.
- Report about a long-standing GitLab interaction; sent a request for a behavior change to the reported person.
- Report on a conspiracy theory, closed as not actionable.
- Report about a Mastodon post, closed as it is not a CoC violation.
- Report closed due to not being actionable, and not a CoC violation.
- Report closed due to not being actionable, and not a CoC violation.
- Report closed due to not being actionable, and not a CoC violation.
Meetings of the CoC committee
The CoC committee has two meetings each month for general updates, and weekly ad-hoc meetings when they receive reports. There are also in-person meetings during GNOME events.
Ways to contact the CoC committee
- https://conduct.gnome.org - contains the GNOME Code of Conduct and a reporting form.
- conduct@gnome.org - incident reports, questions, etc.