Gender inclusiveness in software companies is receiving a lot of attention these days, but it overlooks a potentially critical factor: the software itself. Research into how individual differences cluster by gender shows that men and women often work differently with software for problem solving, such as when trying to contribute to OSS communities.
So you need to find out whether and to what extent gender biases exist in the open source tools that your project uses, the tools you develop, or how your project site itself is structured, and you need to discover how to fix it. Anita Sarma outlines a field-tested method based on five facets of statistical gender differences in preferred cognitive styles and presents what the method reveals about open source software tools and infrastructure—namely that the tools themselves are deeply implicated in gender disparities in OSS communities. Along the way, you’ll learn concrete ways in which the OSS community can get involved in removing gender biases from software that OSS produces, facilitating newcomer onboarding and building inclusive communities.
Anita Sarma is an associate professor at Oregon State University. Previously, she was an assistant professor at University of Nebraska, Lincoln; a postdoctoral scholar at Carnegie Mellon University; and a doctoral student at University of California, Irvine. Through this journey, her passion has been on helping humans make better software and work together. A major part of her research focuses on increasing gender inclusivity in OSS. Her work has been funded through the National Science Foundation (NSF) and Air Force (AFOSR), and she’s the recipient of the NSF CAREER award. She’s authored and coauthored over 50 peer-reviewed journal and conference publications, and her work has been recognized through several Best Paper Awards (ESEM, CHI (2), ICGSE, ICSME).
©2019, O'Reilly Media, Inc. • (800) 889-8969 or (707) 827-7019 • Monday-Friday 7:30am-5pm PT • All trademarks and registered trademarks appearing on oreilly.com are the property of their respective owners. • email@example.com