I support the Ada Initiative because biology doesn’t explain: why there aren’t more women in computer science, why I don’t have more women colleagues who hack on databases, or why we don’t have more women contributing to open source projects.

You can support the Ada Initiative, too.

I wrote a few years ago about how I thought we might best get more women involved. Four years later, my tl;dr version is: make friends with women. Imagine if every male developer could name 10 women that they considered friends among their colleagues. People they trusted, hacked with and built new companies with.

But grassroots efforts alone can’t solve the lack of women’s involvement.

My story of involvement with open source and computing starts with friends who shared the fun with me in college. They invited me to Marathon parties, late night hacking sessions with new processors, pranking coworkers whose system images weren’t quite as secure as they’d advertised…

I love free and open source culture, IT security culture and all the people that I’ve met over the past 13 years. My life is so incredibly enriched and joyful as a result of the people who share what they learn with me.

Despite my love, there’s trouble in paradise. We could be better. And one thing I wish for is more women in my open source communities.

Over the years, I’ve been part of efforts to increase the number of women involved in the projects I’ve founded – Open Source Bridge (more than 50% managed by women, >30% speakers women), Legion of Tech (1/3 of the original board members were women), and Code-N-Splode (all women’s programming and speaker development group).

Now, I’m an advisor to the Ada Initiative. I’ve watched over the last year as Mary and Val have worked to focus their mission and identify exactly what they think will encourage women. They have to balance their experiences and the resistance to cultural change endemic to businesses, organizations and the loose organizations around open source.

It’s fucking hard work. And they’re doing a great job.

Ada Initiative is the organization I wish would have existed 13 years ago. It’s the voice of experience and a catalyst for change that we need inside our communities. It’s a place for women to go for advice and help when things go right — or when things go wrong.

So, what can you do?

The Ada Initiative needs money. They need corporate support. They need individual contributions.

If you, or your company, can contribute and keep the Ada Initiative going for another year, contribute today. Mary and Val have done the hard work of getting started. Now they need your help to keep going.

Image courtesy of Sarah Novotny

I got in about 1pm to She’s Geeky, an unconference about women who self-identify as geeks.

I’m here on a mission: to find developers who want to move to Portland! Emma, Urban Airship, Puppet Labs, About Us and BankSimple are all hiring (and BankSimple is even interested in remote hires).

My favorite conference session yesterday was about leadership and management, the difference between the two, and how to work with managers. We had an amazing discussion, with @noisegirl, Allison Randal, and Ursula Kallio leading a lot of the discussion. Topics ranged from how to carve out time for individual contribution when you take on a management role, to dealing with insane micromanagement to exploring the limits of change in an organization.

Another discussion I participated in was “Startup. Now what?” We talked about the issues each woman faced in starting her own business, and I asked a lot of questions.

I also attended a talk about the commerce department’s Privacy Green Paper. I hadn’t heard of it before, but the response being formulated is here: http://wiki.idcommons.net/Privacy_Green_Paper_Response

The main gist of the discussion was about encouraging congress to think carefully about the legislation and the business environment created (or stifled) by new data regulations. The contention is that activity data stored in “personal data stores” (PDS) is inherently of value — we already know this because our data is bought and sold without our consent or knowledge currently. So, why not create a system where businesses can do this, but with the consent and knowledge of consumers? I’d probably say “citizens” there instead of consumers, but you know. Whatever.

I’m not sure I fully understand the issues yet. I tried at one point to draw a link between PDS and “owning your own logs.“, but that didn’t seem to resonate. Kaliya said something about respecting definitions, so I think that I still don’t quite understand what defines a PDS.

Or, put another way, I am having a hard time understanding the distinction, because the freedom issues seem to be very much the same.

I tweeted a bit about my thoughts on APIs related to PDS, and here’s one conversation that tumbled out of it:

Uploaded with Skitch!

Anyway, much to think about from the first day, and I’m excited to see what discussions unfold today!

At Code-n-Splode last night, we first heard Christie Koehler give a great talk on CodeIgniter, the one PHP web framework endorsed by Rasmus Lerdorf, original author of PHP. She went over the pros/cons, details of how you go about installing and then using CodeIgniter, and then showed a very detailed example from her recent work. I hope she posts the slides soon – they were great. (If you want to see our tweets – per Gabrielle’s suggestion, we’re tagging with #cns now.)

After the talk (nearly 9pm!) we all went over to the Green Dragon for our #afterhours chat. Audrey led off by explaining the recent controversy she’d written about, and the Ruby/Rails community response to her posts.

Some of the things she shared I was shocked by – specifically some very personal attacks in comments that she’d decided to save (in Skitch), but remove from her posts. Her standard was: “is this something that would cause my mom to stop reading.” And, if the comment met that standard, she archived and removed it.

I learned about threads in the local ruby community about the topic of women’s participation, and some very positive comments on Hacker News and Digg, and _why’s posts that seem to be expanding perceptions and opening people’s minds to ways that may ultimately be more inclusive of women and minorities.

All told, we had 15 people at the meeting, 13 of which were women. Our first Code-n-Splode meetings started with about five people. Our largest meeting (thanks to the clever, rocket-building Sarah Sharp) had somewhere around 30 people.

Among the many things that the Code-n-Splode crew discussed last night was “what made portland different”. And I thought I’d let you in on our secret.

We ask women to participate.

When we have code sprints for Calagator, Open Source Bridge or we have the Agile development meetups dedicated to coding – there are always women there. From what I understand, having women show up regularly to code sprints is unusual in other cities.

When I am responsible for these meetups, I contact the people that I want to attend directly – and I ask them to come. This is a mix of women and men (I no longer have to explicitly think about inviting women, because so many are already in the community). But when I was first asking people, I *did* have to contact women who were just dipping a toe into the community — to convince them that yes, joining us would be fun, educational and sometimes good for their careers.

When I first started attending user groups regularly about nine years ago, I often was the only woman. Now, it is extremely rare for me to be the only one. Particularly in groups that span multiple technologies (Web Innovators, Open Source Bridge, Extreme/Agile developers, Functional programming, and BarCampPortland come to mind) or are largely social opportunities for geeks to mix (Lunch 2.0, Beer and Blog). More geeky women (and women that I don’t already know) seem to attend these types of events.

I don’t think there is a single magic formula for transforming your city’s geek scene. But I think it is worth asking questions of the Portland tech community leaders, finding out how our groups work and trying out our techniques in your home town.

Taking a break while digging a ditch

When you have a community, and you notice that there’s an imperfect distribution in participation, what do you do?

How do you increase participation of a particular minority group? What should your goal be?

For example, if you have an open source project, and you need more programmers to contribute — what do you do? What I’ve observed is that the project advertises explicitly – they say, “Hey, we’d like more developers – interested?”

The leaders of the project call up their good friends, and ask those people to help out. Then they present at conferences, saying “Hey, look at our cool project. Want to join us?” They talk to individuals, they talk to groups. They say the same thing, “We’d really like you to join us. So, why don’t you download our code, ask me some questions, and contribute!”

Bottom line: they network, and they find the people that they are looking for.

So, I think this model works equally well for getting more women involved in open source projects. You say to your group of friends, “Hey, I’d like more women contributing to my open source project. Do you know any?” You go to conferences, and you say explicitly, “Hey you – would you like to participate in my project? What are you interested in? Can I help you find a project that is of interest to you?” You go to user groups, and you talk to the women who show up and find ways to keep them engaged in the group, and in the code.

All the hand-wringing over this problem that starts with “I don’t know what to do” can be solved by simply asking people to be involved. Politely, insistently and like you’re bringing them the best party you’ve thrown all year.

Invite them explicitly, rather than falling back on a “if we build it, they will come” mind-set. Sure, a laid-back approach works when you have a popular project, or the choice to contribute is easy. But otherwise, we need to ask for greater participation.

Take a moment, ask yourself — how many women do you know that write code? How many women do you know that contribute to open source in other ways? What can you do to expand your open source circle so that you invite at least one woman into our community? More than one? Maybe half a dozen?

Change yourself, and the whole community will change with you.

Fact is, open source software contribution is still kind of difficult. There are so many barriers to entry that community managers from huge corporations and extremely large open source projects are willing to meet with a group of five people at a 2000-person conference to explain the culture, the potential pitfalls, and the tremendous benefits of getting involved. And those same people are so convinced of the importance of this one-at-a-time contact, that they tell potential contributors, “If you have any questions, email me directly, and I will help you.”

We love our communities and the ideas that drive free and open source software so much that we want to talk to anyone who is interested. We think that it is worth it to convince people, one at a time, to contribute.

The same logic applies to getting women involved. The change won’t happen in a day. We convince people, one at a time, that what we work on – what we believe so much in – is worth contributing to.

And then, one person at a time, we will make it so that women are 50% of open source community.

(image courtesy of diamondmountain via Creative Commons license)

Update: Fixed the etherboot wiki link.

I attended the Google Summer of Code Mentor Summit this past weekend on behalf of PostgreSQL. We met at the Google campus in Mountain View.

This event was an unconference and so, none of the sessions were determined in advance.

Some of the highlights were:

• Leslie Hawthorn and Chris DiBona went into some detail with the whole group about the selection process for GSOC. This session made me feel as though PostgreSQL had relatively good chances for being accepted again next year. Google, however, does not pre-announce projects/products, so there is no sure thing about our (or any other project’s) involvement.
• I met MusicBrainz guys and was pleased to receive many bars of chocolate they requested to be distributed to SFPUG and PDXPUG members as thanks for making an great database.
• Attended three sessions concerning recruitment and retention of students. This is a topic that many people were interested in, but that few people feel they have a proper strategy for.

I also led a session on recruitment and retention of students to open source projects. Some of the ideas that came out of that and the related sessions were:

• Determine what makes you personally need to be part of Postgres (joy of learning, scratching a technical itch, making a tool for your job, fame). Find out which of those things your student also needs or wants and try to give that or help your student achieve that thing.
• Have a clearly defined method for students to keep journals. Several projects simply used MediaWiki and templates.
• Use git (or other distributed revision control), and have students commit early and often to a branch that mentors have access to.
• The Etherboot project has a great system: http://etherboot.org/wiki/soc/2008/start
• Hold weekly meetings over IRC. These can be brief, but help get students accustomed to your project’s culture and way of doing things.
• Ask the student: “are you on track?”, ask the mentor: “do you think the student is on track?” on a weekly basis
• If you want students to stick around, find incremental responsibilities to assign that are driven by their enthusiasm.
• Interview on the phone all your students ahead of time, not just the ones you think might be a problem.
• Require a phone number on the application for the student.
• Require a secondary contact so that if the student “disappears” there’s a backup person to contact. (and contact that person BEFORE SoC starts)

I made good connections with members of Git, Parrot, WorldForge, Ruby and many other community leaders. I was particularly impressed by the ideas and stories from the current Debian project leader, Steve McIntyre and Gentoo council member Donnie Berkholz. Donnie recommended some books about recruitment that I plan to read and review in the next few weeks.

The issue of mailing list moderation and the number of people required to keep mailing lists functioning properly came up frequently. If you know a moderator for a Postgres mailing list, please consider thanking them for doing a very tedious, extremely important and often thankless job.

I also spent some time discussing with Leslie Hawthorn and Cat Allman how to increase the total number of women mentors and students next year. Leslie and I shared some ideas and I offered to help implement them next year. One thing the crowd asked for was explicit training on how to recruit and manage female students. Realistically, this information will apply to all students, and I hope this training helps us recruit more students overall.

I thought the conference went quite well. I hope PostgreSQL is accepted next year, and that one of our mentors is able to attend this conference. And, if you go, be sure to register for the hotel early, and stay at the Wild Palms.

Heard of geekspeakr.com? Brenda Wallace is created a place to store the names and interesting details of women speakers for conferences.

I took a snapshot of the tag cloud so far:

Yay for PostgreSQL being the only database represented! So far!

[ I was working on a blog post about the Women In Open Source roundtable I ran, and then Brenda Wallace tweeted: "it seems reasonably easy 2 get women involved in opensource documentation, ui design, and even management. Why is it hard 2 get women coding?" Here's my longer response, mostly with ideas I got from the roundtable. ]

I ran a panel discussion about Women in Open Source at the PostgreSQL Conference East (last weekend). I talked about all the conference events that I’d seen in the last 1-2 years specific to women, and a pair of researchers talked about communication patterns among women on the KDE women’s list. Then we had a 2 hour discussion with the 10 people in attendance.

Three issues that stuck with me from the discussion were:

* Mentoring: Women do not often receive the same type of mentorship that men receive. This has two important consequences: women don’t feel as connected to the community (don’t learn cultural norms, don’t receive favors, don’t get as much praise or reward for work), and women don’t see clear pathways to greater responsibility or prestige (roles are not obvious unless you’re “in the know”, few role models).

* Self-efficacy: Women consistently rate themselves as far less capable than they prove themselves to be. Example: survey of Computer Science undergrads showed that women rated their preparedness at an average of 0%, while men rated their knowledge and prep around 60-70% — even though GRADES proved that the women had just as much ability/knowledge (these 0% folks were getting As and Bs in courses). The UMD researchers said that self-efficacy has been strongly correlated with success in achieving goals.

* Quality of Life: some coding jobs are low prestige, require superhuman hours and aren’t friendly to women (or men) with children. We didn’t have any research to back this up, but there was a lot of speculation that women 25-45 would not be excited to come back to programming after having children because of the life/work balance problems.

Some or all of these issues can probably be linked to the experience of other minority groups.

As far as “what we can do” — I think we need to work environments more humane and accepting of people who have children. There’s a bit of anti-child culture in some high tech circles, and my personal feeling is that this will continue to turn women away.

I also think we need more mentorship! Women need to mentor women, and men need to mentor women. I think training a group of men on how to mentor women would be greatly beneficial — especially if those men-mentors got some kind of seal of approval at the end of their mentorship bootcamp.

There’s always a tension when men mentor women, and maybe if it was a little more organized and some rules were set — like no using the mentorship program as a personal dating service — it might work better than the ad hoc mentorship stuff we have right now.

Less formal than GSOC, but more formal than just contacting people on a mailing list.

Sunday’s keynote at SCaLE was given by Stormy Peters. She talked about open source, business contributions and the social and financial economies driving development.

Three of her research questions were:

• What is the initial motivation that encourages people to contribute?
• How do companies pay for open source contributions? (and what’s the effect?)
• How do companies change projects when they join?

Her conclusion was that the developer community needs to teach businesses how to do things right for the community. We can’t wait for businesses to figure it out on their own. The call to action was a good one, but it seemed to leave some audience members scratching their heads. One audience member asked, “How do we do that?”

A few interesting figures she mentioned:

• 1/3 of all developers believe that software should be free
• Average number of open source projects a developer works on: 5
• 40% of open source developers are paid to contribute
• 10-20% are paid but their bosses don’t know it – that probably was a joke

One quote that stuck with me was: “Typically people have been divided between left and right brain [professions].” I don’t agree. I think you only have to look briefly at the history of science to see that creativity (“right brain”) and reason (“left brain”) have often gone together.

The developer community just like many others – regular people who want to be useful, and inspired by their work. Creativity may not be asked for in a person’s work. But people invent, dream and create regardless of whether their profession requires it.

Thanks to one of Audrey’s RSS feeds, I read Women in Computer Science – An Endangered Species of a New Kind? this afternoon. About the same time, I received email from a professor at UMD who is helping organize PostgreSQL Conference East. She would like to hold a Women in Open Source Focus Group session during the conference, and we’re looking for participants.

Over the last year, I’ve read many times that computer science enrollment for women is down, and more generally, for the sciences. The author of the endanger species post says that she’s going to do some more research to confirm or deny that trend.

I just picked up a book Why Aren’t More Women in Science, with eds. Stephen J. Ceci and Wendy M. Williams. I’ll be writing more about the individual articles over the next couple weeks. I found it referenced among some blog entries about the lack of diversity at technology-related conferences.

On the “things might get better” front: I think that we’re starting to achieve a critical mass of women who code and also have free time to devote to trying to solve these problems. Of course men can work on it too, but there’s unquestionable value in having a group of women leading efforts. DevChix is certainly one of those groups. Those of us in Code ‘N’ Splode are trying to get off the ground and eventually provide leadership as well.

The Women in Open Source track at SCALE is coming up next Friday. I know a few of the people presenting, and I’m hoping to make some more connections on behalf of PostgreSQL.

Lack of diversity in conferences – economic, ethnic and gender; presenters and attendees – is something I’d like to change. My shot over the bow is this focus group for women in open source during the PostgreSQL conference in College Park, MD, March 29-30. There are some PhD candidates and professors doing research on this topic there! Anyone interested in joining us, please contact me.

To Sir, with Love: How To Get More Women Involved in Open Source

I think we IT folks share a passion for fixing things. We solve problems other people find impossible every day. Just a small amount of that energy directed toward encouraging women to join in openly would go a long way.