This is our Code of Conduct. It’s a working document, and you can fork/comment/suggest changes to it on GitHub.
We think that it’s important for every community to have a clear statement of how people are expected to behave within its borders, across all spaces and platforms. We’ve had a version of this internally since early on in the project. We’re sharing this now as we prepare to launch our own community space, which have their own Community Guidelines based on this code. We will also adapt this for in-person events that we run.
Please read it. What did we miss? What would you add? Let us know on GitHub, email us at email@example.com or Tweet at us: @coralproject
The Coral Project Code of Conduct
Last updated 3/1/2017
We expect everyone contributing to The Coral Project to follow this code of conduct. That means the team, contractors we employ, contributors, as well as anyone posting to our public or internal-facing channels.
We created it not because we anticipate any unacceptable behavior, but because we believe that articulating our values and obligations to one another reinforces the already exceptional level of respect among the team, and because having a code provides us with clear avenues to correct our culture should it ever stray from that course.
We make this code public in the hopes of contributing to the ongoing conversation about inclusion in the tech, design, and media communities and encourage other teams to fork it and make it their own.
We commit to enforce and evolve this code over the duration of the project.
Be supportive of each other. Offer to help if you see someone struggling or otherwise in need of assistance (taking care not to be patronizing or disrespectful). If someone approaches you looking for help, be generous with your time; if you’re under a deadline, direct them to someone else who may be of assistance. Go out of your way to include people in team jokes or memes, recognizing that we want to build an environment free of cliques.
Be collaborative. Involve your colleagues in brainstorms, sketching sessions, code reviews, planning documents, and the like. It’s not only okay to ask for help or feedback often, it’s unacceptable not to do so
Be generous and kind in both giving and accepting critique. Critique is a natural and important part of our culture. Good critiques are kind, respectful, clear, and constructive, focused on goals and requirements rather than personal preferences. You are expected to give and receive criticism with grace.
Be humane. Be polite and friendly in all forms of communication, especially remote communication, where opportunities for misunderstanding are greater. Use sarcasm carefully. Tone is hard to decipher online; make judicious use of emoji to aid in communication.
Respect people’s boundaries.
Do not make it personal.
We are committed to providing a welcoming and safe environment for people of all races, gender identities, gender expressions, sexual orientations, physical abilities, physical appearances, socioeconomic backgrounds, nationalities, ages, religions, and beliefs.
We expect that you will refrain from demeaning, discriminatory, or harassing behavior and speech.
Harassment includes, but is not limited to: deliberate intimidation; stalking; unwanted photography or recording; sustained or willful disruption of talks or other events; inappropriate physical contact; use of sexual or discriminatory imagery, comments, or jokes; and unwelcome sexual attention.
Furthermore, any behavior or language which is unwelcoming—whether or not it rises to the level of harassment—is also strongly discouraged. Much exclusionary behavior takes the form of microaggressions—subtle put-downs which may be unconsciously delivered. Regardless of intent, microaggressions can have a significant negative impact on victims and have no place on our team.
Other inappropriate behavior:
- Copyright infringement
- Impersonation of someone else
- Violating someone’s privacy
If you feel that someone has harassed you or otherwise treated you or someone else inappropriately, please alert the project lead at firstname.lastname@example.org
Reporting a problem
These guidelines are ambitious, and we’re not always going to succeed in meeting them. When something goes wrong—whether it’s a microaggression or an instance of harassment—there are a number of things you can do to address the situation. Depending on your comfort level and the severity of the situation, here are some suggestions:
Address it directly. If you’re comfortable bringing up the incident with the person who instigated it, pull them aside to discuss how it affected you. Be sure to approach these conversations in a forgiving spirit: an angry or tense conversation will not do either of you any good. If you’re unsure how to go about that, try discussing with your manager or with the people and culture team first—they might have some advice about how to make this conversation happen.
If you’re too frustrated to have a direct conversation, there are a number of alternate routes you can take.
Talk to a peer or mentor. Your colleagues are likely to have personal and professional experience on which to draw that could be of use to you. If you have someone you’re comfortable approaching, reach out and discuss the situation with them. They may be able to advise on how they would handle it, or direct you to someone who can. The flip side of this, of course, is that you should also be available when your colleagues reach out to you.
Talk to Andrew or David. We will work with you to help you figure out how to ensure that any conflict with a colleague doesn’t interfere with your work, in confidence if you would prefer.
Talk to Chris Lawrence. Chris oversees the project. He can be contacted at email@example.com
If you feel you have been unfairly accused of violating this code of conduct, you should contact Chris at the above email address with a concise description of your grievance.
We welcome your feedback on this and every other aspect of what we do as The Coral Project, and we thank you for working with us to make it a safe, enjoyable, and friendly experience for everyone involved in the project and what we do.
Above text is licensed CC BY-SA 4.0, adapted from the SRCCON code of conduct, FreeBSD’s code of conduct, Vox Media’s product team code of conduct, and Medium’s code of conduct.