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 October 2025 to June 2026.
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 October 2025, the committee has received reports on a total of 17 possible incidents. Several of these were not actionable; all the incidents listed here were resolved during the reporting period. There is currently a total of 7 incidents in process.
- We were made aware of concerns regarding online comments made on social media by a GNOME Foundation member. Upon review, we found these comments to fall outside the scope of the Code of Conduct in this instance.
- Report about messages sent to a Telegram channel. Contacted the reported person about the inappropriate nature of the messages.
- Report about unfriendliness to newcomers in a localisation team. Asked the team lead to write down documentation on their procedures.
- Question about clarification on the CoC's text; replied suitably since the question was not actually about the CoC's contents.
- Tech support request; redirected to discourse.gnome.org.
- Malicious question; closed without reply.
- Report about homophobia; removed privileges for the reported person.
- Report about a Mastodon post which was subsequently removed. Reminded the reported person that Mastodon posts in the context of GNOME are also under the scope of the Code of Conduct.
- Report about two Mastodon posts which were subsequently removed. Reminded the reported people that Mastodon posts in the context of GNOME are also under the scope of the Code of Conduct.
- Report about a TWIG submission, not actionable as there is no violation of the CoC.
- Report unrelated to GNOME; notified the reporter and closed as non-actionable.
- Report about an interaction in gitlab.gnome.org. Reminded the reported person about how to politely deal with disagreement.
- Tech support request; already solved.
- Report about suspicious activity in Matrix; not actionable other than to keep an eye out for the reported person.
- Report about a person exhibiting bad behavior outside of the scope of the CoC. We will keep an eye on it.
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.
The website repository, and the Code of Conduct itself and the committee's procedures, are kept at https://gitlab.gnome.org/Teams/Conduct/gnome-code-of-conduct
The Code of Conduct Committee is happy to receive questions about the CoC itself and its procedures, and we will gladly assist you. Please use the communications channels listed above.