Code of Conduct
A code of conduct sets a clear expectation that everyone at the event; attendees, speakers, sponsors, and organizers, is responsible for maintaining a respectful environment. It’s not a formality. It’s what makes the meetup a place where people feel safe showing up.
What to include
At minimum, a code of conduct should cover:
- Who it applies to (everyone: attendees, speakers, sponsors)
- What behavior is prohibited (harassment, intimidation, unwelcome recording, offensive comments based on gender, race,
- disability, religion, and similar characteristics)
- How to report a violation (a person to contact, an email address, or both)
- What happens when the code is violated (organizers can ask someone to leave and ban them from future events)
The Contributor Covenant is a well-established starting point that many tech communities use. The RubyMX Code of Conduct is another reference.
Communicating it
A code of conduct only works if people know it exists. RubyMX communicates it in two ways:
- During registration: attendees agree to the code of conduct when they get their ticket
- At the start of every event: the host reads the code of conduct aloud and explains who to contact if something happens
Both matter. The registration mention sets the expectation in advance. The in-person reading makes it real for the room and tells people where to go for help.
Make sure volunteers know who the point of contact is. Attendees who need to report something should be able to reach someone immediately, not just an email address.
Enforcement
If someone violates the code of conduct, organizers have the authority to ask them to leave and to ban them from future events. That’s the full range: a private conversation at the low end, removal and a permanent ban at the high end.
As organizer, you won’t always know what happened until someone tells you. Take reports seriously and act on them. The people who report something are usually more afraid of not being believed than they are of the person they’re reporting.