We aspire to create a culture where people work joyfully, communicate openly about things that matter, and provide great services for the American people and the world. We would like our team and our communities (including government and private sector colleagues) to reflect the diversity of America. We want to foster diversity of all kinds—not just the classes protected in law. Diversity fosters innovation. Diverse teams are creative teams. We need a diversity of perspective to create solutions for the real and urgent challenges we face.
This is the DevProgress Code of Conduct. We expect everyone who works at DevProgress, attends DevProgress events and meetings, or participates in online forums or other virtual collaboration to follow this code of conduct. This applies to all of our methods of communication: chatrooms, hackathons, events, commit messages, email, and both formal and informal conversation.
Consider what you can do to encourage and support others. Make room for quieter voices to contribute. Offer support and enthusiasm for great ideas. Leverage the low cost of experimentation to support your colleagues' ideas, and take care to acknowledge the original source, not just the most recent or loudest contributor. When someone offers something unexpected, look for ways you can contribute and collaborate. Share your knowledge and skills. Prioritize access for and input from those who are traditionally excluded from the civic process.
Create boundaries to your own behavior and consider how you can create safe space that helps prevent unacceptable behavior by others. We do not seek to list all cases of unacceptable behavior, but provide examples to help guide our community in thinking through how to respond when we experience these types of behavior, whether directed at ourselves or others.
If you are unsure if something is appropriate behavior, it probably isn’t. Each person you interact with can define where that line is for them. Impact matters more than intent. Ensuring that your behavior does not have a negative impact is your responsibility. Problems happen when we assume that our way of thinking or behaving is the norm or ok with everyone. This is particularly problematic when we are in a position of power or privilege.
Here are a few examples of unacceptable behavior:
-
Negative or offensive remarks based on race, religion, color, sex (with or without sexual conduct and including pregnancy and sexual orientation involving transgender status/gender identity, and sex-stereotyping), national origin, age, disability (physical or mental), genetic information, sexual orientation, gender identity, parental status, marital status, and political affiliation as well as gender expression, mental illness, socioeconomic status or background, neuro(a)typicality, physical appearance, body size, or clothing. Consider that calling attention to differences can feel alienating.
-
Touching people without their affirmative consent.
-
Sustained disruption of meetings, talks, or discussions, including chatrooms.
-
Patronizing language or behavior.
-
Aggressive and micro-aggressive behavior, such as unconstructive criticism, providing corrections that do not improve the conversation (sometimes referred to as "well actually"s), repeatedly interrupting or talking over someone else, feigning surprise at someone’s lack of knowledge or awareness about a topic, or subtle prejudice (for example, comments like “That’s so easy my grandmother could do it.”).
-
Referring to people in a way that misidentifies their gender and/or rejects the validity of their gender identity; for instance by using incorrect pronouns or forms of address (misgendering).
-
Retaliating against anyone who files a formal complaint that someone has violated these codes or laws.
DevProgress is greatly appreciative of the multiple sources that we drew from to build this Code of Conduct, including:
- 18F Code of Conduct official Code of Conduct of 18F (a digital delivery team within the General Services Administration).
- Bridge Foundry Code of Conduct used for RailsBridge, and other related workshops and open source projects
- Open Hatch Project Codes of Conduct
- Yes and Yes Yes Code of Conduct
- Ada Initiative: HOWTO design a code of conduct for your community
- PyLadies Code of Conduct
- Hacker School User's Manual: The Environment
- Geek Feminism Code of Conduct
- Geek Feminism Wiki: Codes of Conduct Evaluations
- Python Code of Conduct
- Code for America Code of Conduct
- Laws enforced by the Equal Employment Opportunity Commission
- Types of Discrimination prohibited by law
- New and proposed regulations
If you or someone you know feels that DevProgress should be made aware of any violations of this code of conduct, there are a number of ways you can get in touch with the project. All reports will be taken seriously, and identities protected.
- Send an email to [email protected]
- Send an email directly to the DevProgress Open Source Community Mananger.
- PM the Open Source Community Manager (Currently @decause) and ask for an invite to our private slack channel for incident response.