Setting intention

From Open Source Bridge Wiki
Jump to: navigation, search

Links for Supporting diversity with a new approach to software

Who needs it the most? Teams that want to build software for people or communities who are usually marginalized

Who else benefits? Any team that wants to build better software

It won’t just happen. If creating software that works better for everybody is something you want to do, make it an explicit goal - and commit to it publicly.

High-level recommendations

  • State your commitment publicly with a Diversity Statement or an equivalent. (See links below for examples)
  • Code of conduct (for the development team and for the community) and process for reporting and dealing with issues
  • Approach it in an intersectional way
  • Recruit a team that’s diverse in multiple dimensions
  • Foster an culture of inclusion and equity
  • Seek out and recruit diverse users, community leaders, and beta testers
  • Work to improve diversity and inclusion in technology and society (not just your project)
  • Be aware of how existing societal power vectors affect software - and look for ways to counter them

Open Source Bridge Sessions

Opening Up The Current Open Source Blueprint, Stephanie Morillo (2015)

Building mentoring into an open source community that welcomes and values new contributors, Cathy Theys (2015)

From the Inside Out: How Self-Talk Affects Your Community, Kat Toomajian (2015)

Catalyzing Diversity: Practical Advice for Navigating Minority STEM Communities to Open Up Open Source, Alberto Roca and Shauna Gordon-McKeon (2015)

Explicit Invitations: Passion is Not Enough for True Diversity, Lukas Blakk (2014)

Badging and Beyond: Rubrics and Building a Culture of Recognition as Community Building Strategies, Larissa Shapiro (2014)


Diversity statements: Dreamwidth and Django (although see this HBR article on Unintended Consequences of Diversity Statements as a caveat)

Codes of conduct (for the development team and community) and process for reporting and dealing with issues: As Sage Sharp's Evolving Code of Conduct Language on Otter Tech highlights, "best practices" for codes of conduct are constantly evolving, so please don't assume the language and framing in any of these is ideal by today's standards!

See also Christie Koehler's Adopting a code of conduct is an adaptive challenge not a technical one.

5 tips every open source project manager should consider, Safia Abdalla on

My Disability Matters' Respect and Inclusion Pledge

Disrupting the Startup Brogrammer Culture, Lynne d. Johnson, Shireen Mitchell, Nicole Sanchez, and Amy Vernon at Women Who Tech telesummit

Geek Feminism’s HOW TO recruit and retain women in tech workplaces for best practices on this front.

Being an Effective Ally to Women and Non-Binary People, Toria Gibbs and Ian Malpass of Etsy

Facilitating for Diversity and Inclusion on the Digital Library Foundation's wiki

Racial Equity Tools has a wealth of resources supporting individuals and groups working to achieve racial equity

List of Resources for Recruiting and Retaining Women in Tech, Chaya Cooper

Project Include has recommendations on culture, “employee lifecycle” (which could be adapted for open source projects), metrics, and more.

Imagining Radical Queer Futures through Tech by Morgen Bromfell (at SF Alterconf 2016) discusses the need for the radical imagination in the context of the survival of marginalized communities