Archives

Code of Conduct

Proposed CRASH Space Code of Conduct

This code of conduct under review for vote by the board at the December meeting. There is alternate language also under consideration.

  • http://geekfeminism.wikia.com/wiki/Conference_anti-harassment/Policy
  • https://adainitiative.org/2014/02/18/howto-design-a-code-of-conduct-for-your-community/

Our mission is to create a welcoming environment for the community to expand their technical, scientific, and artistic skills through individual projects, social collaboration, and education.  As a result, we put “BE AWESOME” as our #1 House Rule.

Sometimes, however, “BE AWESOME” is not specific enough to encourage the diversity and multiple points of view that strengthen our community and projects. Therefore, we would like to make it clear that we at CRASH Space are dedicated to providing a safe and encouraging environment for everyone, regardless of gender, sexual orientation, disability, physical appearance, body size, race, or religion.  Our goal is to treat others with respect in all of our workshops, classes, events, talks, presentations, and projects.

What it Means to Be Awesome:

  1. We treat others as they would like to be treated, acting from an assumption of mutual respect and good will.
  2. We clarify misunderstandings, apologize for harm caused, and assume ignorance before malice.
  3. We offer our sincere help and support to those who request it. We remember what it’s like to be a beginner, and therefore offer the kind of help that benefits the learner, not our egos.
  4. We allow others to speak without interruption, and resist the urge to “Well, actually…”
  5. We encourage a diverse technical community where each person is welcome to choose their own tools, programming languages and techniques without fear of insult or judgement.
  6. We welcome and encourage diversity, and work diligently to keep subtle -isms out of our communication with each other.
  7. We work to create an environment free of microagressions, which can be detrimental to the growth of diversity in our space.
  8. We ask permission from others. We accept “no”s without arguing, and say “yes” when we mean yes.
  9. We stand up and watch out for each other. Maintaining a respectful and safe community is everybody’s responsibility.

Remember: We all make mistakes. If you get called out on something: apologize, learn from it, and be better next time. That is the awesome thing to do.

Code of Confidentiality

If a member or visitor of CRASH Space raises a concern relating to actions covered by this policy in good faith, there will be no retaliation for bringing forward their concern. Threatening or taking action against a member for invoking this policy and/or for participating in any related investigation will be considered a violation of this policy.

All concerns relating to harassment, including sexual harassment, will be dealt with as confidentially as possible. A member’s identity or the circumstances regarding any concern or complaint will not be disclosed unless disclosure is necessary for the purposes of legal investigation or disciplinary action.

In the Event of Conflict

We believe that when both parties are attempting to act with respect and good will, many conflicts can be resolved without escalation.

If conflict arises with another member, remember to assume ignorance before malice, and first attempt to address it with them directly. Request that they stop the problematic behavior and see if you can resolve the situation with them via honest and open communication. If this is not possible, ask a neutral party to mediate.

In the Event of Extreme Conflict

If you feel that direct communication is unsafe or otherwise inappropriate, or if the steps above have failed to resolve the situation, please escalate to a CRASH Space officer or board member privately, or via email at board@crashspace.org. The board will take appropriate action as soon as is reasonably possible.

The board shall keep records of all such incidents brought to its attention and the actions taken in response.

Policy Enforcement

Depending on the severity of the situation, actions taken in response to violations of this policy may include:

  • a verbal or written warning
  • temporary suspension of access to the workshop
  • termination of membership without refund of dues
  • the involvement of law enforcement

We believe in our community, and hope to never need to take the actions mentioned above.

Acknowledgments

Much of the information above is influenced by or borrowed from the many awesome spaces who have paved the way for safer, happier hackerspaces:

Ada Initiative | Double Union | Hacker School | hacklab.to | Seattle Attic