Community

Gleo community code of conduct

This community code of conduct covers every space Gleo runs: replies on X, events, code repositories and calls. It also explains how to report a problem.

Last updated October 6, 2026

We want people of every background and level of experience to feel able to ask questions, disagree and contribute. That only works if everyone treats each other with respect. This code applies to the Gleo team and to everyone who takes part in our spaces.

Reviewing and contributing to code

Review the work, not the person. Explain why a change is needed, assume the author acted in good faith, and accept that maintainers make the final call on what is merged. Credit others for their ideas and code.

Everyone is welcome

We welcome contributors regardless of age, body, disability, ethnicity, gender identity and expression, experience, nationality, appearance, race, religion or sexual orientation. Use plain language and be patient with people working in a second language.

Behaviour we do not accept

  • Harassment, insults, threats or personal attacks.
  • Sexual language or imagery, and unwelcome attention.
  • Publishing someone's private information without permission.
  • Promoting scams, fake contract addresses or impersonating the team.
  • Repeatedly derailing discussions after being asked to stop.

How to report a problem

Send a direct message to @gleo on X. Include what happened, where, and links or screenshots if you have them. You will get a reply, and you can stay anonymous to the person you are reporting.

Keeping reports confidential

Reports are seen only by the people handling them. We do not share the reporter's identity without consent.

What the team will do

The team will review every report and respond in proportion: a private note, a temporary mute, or removal from our spaces. We may remove comments, code or other contributions that break this code.

Where this code applies

This code applies in all Gleo spaces and when someone represents Gleo elsewhere, for example at an event or in an official account.

Where these rules come from

This code draws on common practice in open-source communities, rewritten for Gleo.

Looking for somewhere to start? See the Gleo community channels, the upcoming Gleo events or the answers to common questions.