00:00:20.640
So, sorry. I just got sick the last night and this morning, so if there's a lot of coughing or excessive water drinking, that is why. My name is Ashe. I'm a programmer, and most people here probably know me because of my diversity advocacy work that I do in the Ruby community. I've been a programmer for about the past 13 years, 11 of which have been in open source communities. For the past four or five years, I've been pretty solidly planted in the Ruby community.
00:00:30.480
A lot of my work kind of revolves around what we can do better as a Ruby community, what I've learned from other communities, and the good things that we have, which we can export to other places. So I’m Ashe Dryden pretty much everywhere on the Internet. Feel free to ask me questions later if you’d like. I'm very lucky that the Internet is actually my employer, which is a really weird thing to say. A bunch of anonymous strangers basically pay my salary so I can do this work. One of the companies that stepped up to sponsor a lot of my work this year is Bendy Works, which is a Rails and Ruby consultancy in Madison. They gave me a bunch of these cute little software craftsmanship notebooks, so come and talk to me later, and I’ll give you one.
00:01:06.159
The reason that I do this is that I really like solving hard problems. That's probably the reason I became a programmer in the first place. After being a programmer for so long, I can tell you that the hardest problems are always the people problems. It's the issues that people bring when they write software and the problems that arise when they try to work together to write software. A lot of my work lately has focused on this. So why do I do this? Well, I love open source software. I love the ability for anybody to come in and create something amazing and be able to share it with many others. I love that we can collaborate around the world on a tiny bit of code. I think that's really cool; that's something that a lot of people in other professions do not get to experience.
00:01:56.439
I also believe that the software we write today is a reflection of the people who wrote it. The more diverse the perspectives of the individuals involved, the better our software will be. My work specifically focuses on getting more different kinds of people to come to our events, to work at our companies, and to contribute to our software. So what does open source look like now? Unfortunately, it is largely homogeneous. The vast majority of the people contributing to open source look very similar; they come from very similar backgrounds.
00:02:48.159
It's important to remember that we are not the only ones using our software. There are experts coming to the table, using our programs, but also governments, schools, and students who are brand new to writing or using software. We need to keep that in mind while we're developing it. As I mentioned, the community is quite homogeneous. Specifically, only 1.5% of open source contributors are women. This is an extremely low number, especially considering that about 20% to 24% of our community is made up of women. We should expect to see at least 10 times this number of women contributing to our software.
00:03:58.560
As for other marginalized groups—people of color, LGBTQ individuals, people who do not speak English as a first language, and people with disabilities—we currently have no idea what their representation looks like. The groups are small enough and the funding is often so specific to women that we just don't gather data on these other characteristics. We're not polling people to discover what the representation is like for these groups. So, why is it so low? There are several factors that contribute to this, which I will briefly touch on. I have a blog post in the resources if you want to dig deeper into each of these.
00:05:09.320
The first factor is time, which is probably the hardest one because it’s not something we can provide to others. Many people from marginalized communities have significantly less time to contribute to open source software. When they go home, they are much more likely to be engaged in unpaid labor, whether it be taking care of family members, running errands, or handling medical concerns. All of these responsibilities limit their available time to contribute to software projects. We also face the issue of pay inequality, which is something most people are familiar with. Women in the software industry earn about 80% of what men do, which is a significant disparity.
00:05:51.919
It's slightly better than the U.S. average but not by much. When considering race, women of color earn about 55% of what white men do, indicating a stark difference in the time and money available to these individuals. For many, achieving similar levels of pay often requires working multiple jobs or applying different strategies to make ends meet. The reality is that many aren't interested in a 50% raise simply because they don't have any spare time to contribute under current circumstances.
00:06:02.400
Additionally, very few people are actually compensated for their contributions to open source. While some companies have become visible for paying individuals to work on open source projects, whether part-time or full-time, the availability of such jobs is extremely limited and often requires significant qualifications and experience that can exclude marginalized individuals from accessing these opportunities.
00:06:27.120
This contributes to a situation where individuals may not have the time they need during their employment to engage in open source work. Getting involved in open source can be a powerful way for people to feel linked to a greater purpose and create work that they can be proud of, yet individuals from marginalized backgrounds may face additional obstacles that inhibit this connection.
00:06:54.080
Moreover, treatment within communities can also influence participation. Dismissive behaviors or belittling comments in issue queues, along with harassment in communication platforms like IRC, contribute to an atmosphere of unwelcomeness where individuals feel unsafe or unwanted. Such environments discourage people from spending their free time contributing when they perceive that they will be treated poorly.
00:08:02.359
A common reaction I encounter when asking individuals why they don’t contribute is fear of being the only female programmer publicly engaged in a project and subsequently attacked. This concern is not unreasonable given the negative treatment many women receive online. It creates an additional barrier to entry for many people who consider contributing but fear the implications of their identities being scrutinized by others.
00:09:03.760
So, what can we do about this? How many people in this room contribute to open source right now? Whether through writing code, testing, documentation, or organizing meetups, please raise your hands. A good number of you are involved, and this shows that these issues can be addressed by anyone who has a job, sits in this room, enjoys going to conferences, or cares about the open source movement. It's important that as more people come into open source, we maintain a cohesive culture—something that can be tricky with many newcomers joining over time.
00:10:59.680
To encourage contributions, it’s essential to make it clear that you want people to engage in your projects. It may seem obvious, but many people who haven’t participated before don’t know what you’re looking for. Adding a contributor file to your project can outline how to contribute and what kind of input is needed—this low barrier can assist those who feel uncertain about how to participate.
00:11:59.760
Labeling issues in your queue as beginner-friendly can help those who may feel intimidated. It’s crucial to reserve simple issues for those who are new to the project. For documentation, get eyes on it from beginners; the best documentation often comes from those without prior context. Encouraging these individuals to provide feedback can help gauge how accessible your resources are.
00:13:04.480
Be vulnerable and share your own experiences of feeling scared or uncertain. High-profile contributors being open about not having all the answers can empower others. Displaying your own struggles can help build a more supportive atmosphere for newcomers. Remind them that everyone starts somewhere and that it’s okay to feel intimidated. Everyone gains from this openness.
00:14:10.240
It’s not just about patience; it’s also about making sure that all participants feel safe. Many projects have successfully implemented codes of conduct, which set behavioral expectations and create guidelines for reporting issues. Everyone should familiarize themselves with these codes. It’s vital that they can approach someone about an issue and feel assured that it will be handled respectfully and promptly.
00:15:45.760
Fostering an environment of safety leads to increased participation. Paying attention to the help provided is necessary as well. We need to ensure that individuals feel comfortable asking for assistance and that questions are addressed without defensiveness. It’s also essential to be inviting; welcoming newcomers instead of berating them for making simple inquiries can create a more inclusive environment.
00:16:55.040
Supporting those who contribute—whether through volunteering or monetary contributions—is equally important. Many individuals cannot participate in open source due to their time constraints or financial limitations. Companies should specify in job postings that they support contributions to open source projects. Highlighting this alongside job benefits indicates to candidates that engagement in open source work is valued.
00:18:55.840
To further assist, sponsoring programs that help individuals contribute, like Rails Girls and RailsBridge, can be immensely beneficial. These initiatives provide support and mentorship, helping individuals connect with their communities. Moreover, consider donating to organizations committed to engaging newcomers in open source initiatives.
00:19:58.080
In conclusion, I hope that these resources can further inform your efforts in fostering inclusive open source contributions. The first is a deeper dive into the challenges that hinder contributions. The second is about creating clear guidelines for contributions known as contributor documentation. The last two resources are codes of conduct that facilitate respectful engagement within open source projects. Thank you very much!
