Our Code Of Conduct
The point of our CoC and IS is to an attempt to send a clear message to marginalized groups that your presence is welcome and that we are thinking of your safety and comfort.
Harassment is any unwelcome or hostile behavior towards another person for any reason. This includes, but is not limited to, offensive verbal comments related to personal characteristics or choices, sexual images or comments, deliberate intimidation, bullying, stalking, body shaming, following, harassing photography or recording, sustained disruption of discussion or events, nonconsensual publication of private comments, inappropriate physical contact, physical and verbal intimidation, or unwelcome sexual attention. Conduct need not be intentional to be harassment.
Thursday Network will not tolerate such behavior!
Photography is encouraged, but other participants must be given a reasonable chance to opt out from being photographed. If they object to the taking of their photograph, comply with their request. It is inappropriate to take photographs in contexts where people have a reasonable expectation of privacy (in bathrooms or where participants are resting).
We ask that you avoid displaying, distributing or distracting other participants with illegal, pirated, or explicit content while on the premises.
We also ask that you avoid recruiting for your startup, company, job, or organization...except during the shout-outs portion of our event.
Participants asked to stop any harassing behavior are expected to comply immediately. As this is a hackathon, we like to explicitly note that the hacks created at our hackathon are equally subject to the anti-harassment policy.
Sponsors and partners are also subject to the anti-harassment policy. In particular, sponsors should not use sexualized images, activities, or other material. Sponsor representatives (including volunteers) should not use sexualized clothing/uniforms/costumes, or otherwise create a sexualized environment.
If you are being harassed, notice that someone else is being harassed, or have any other concerns, please contact a member of hackathon staff immediately.
Hackathon staff will be happy to help participants contact any local security or local law enforcement, provide escorts, or otherwise assist those experiencing harassment to feel safe for the duration of the hackathon. We value your attendance.
If a participant engages in harassing behavior, the hackathon organizers may take any action they deem appropriate. This includes warning the offender, expulsion from the hackathon with no refund (if applicable), or reporting their behavior to local law enforcement.
We expect participants to follow these rules at hackathon and workshop venues and hackathon-related social events.
Our Inclusivity Statement
We encourage everyone to participate and are committed to building a community for all. Although we will fail at times, we seek to treat everyone both as fairly and equally as possible. Whenever a participant has made a mistake, we expect them to take responsibility for it while also providing support through positive reinforcement.
Although this list cannot be exhaustive, we explicitly honor diversity in age, gender, gender identity or expression, culture, ethnicity, language, national origin, political beliefs, profession, race, religion, sexual orientation, socioeconomic status, and technical ability. We will not tolerate discrimination based on any of the protected characteristics above, including participants with disabilities. There is no one true hacker.
Our Principles Of Positivity
Respect the Opinions and Abilities of Others
Code for DC is designed as a place for people all of different skill levels and approaches to meet and work together toward common goals. As a result, we do not expect that everybody will share the same opinion. However, we do expect that disagreement is done respectfully.
Additionally, we expect that members will educate others respectfully. To this end, do not assume anybody else’s level of expertise or knowledge. Do not belittle a lack of information, or insist on unnecessary precision. We are all learning, so afford others—as well as yourself—room to grow.
Keep Your Team Open
Except for instances where it would significantly impede productivity, there is always room on a Code for DC project for one more person. Unless doing so would be counter-productive to the goals of the project, anybody who is interested in a project is allowed to join it.
While this document exists primarily to prevent certain bad behavior, we also believe that our community members should work towards a higher standard. To that end, we strongly encourage the following conduct, though they are considered aspirational rather than necessary.
Build With, Not For
Work to ensure that the community is well-represented in all stages of development. Seek out those who are under-represented, and remove barriers to access. Listen as much—or more—than you speak, and give full consideration to all ideas, even if they seem improbable at first.
Empower, Experiment, and Find a Way for Everybody to Contribute
When more people share their knowledge and skills, they give a project a greater chance to succeed. When somebody shows up with an unusual skill, look for ways to fit them into the team rather than reasons why it wouldn’t work. Experiment with new approaches, and don’t be afraid to try something that might not work.