What follows is one of the articles I wrote for The Encyclopedia of Gender and Information Technology. It was accepted pending revision, but I decided to withdraw it. The deadline was just about to pass, and I suppose I could have asked for an extension, but the changes the reviewer requested ended up requiring more research on the history of women in computing than I have time to do, unfortunately (must spend time on dissertation only!). Plus, this is much more of a nonacademic position paper than an objective, informative academic encyclopedia article. I wrote two other articles for the encyclopedia anyway, which is probably enough. So, enjoy. Maybe you'll learn something you didn't know before; I hope so. Not being a software developer myself, I'm sure I'm wrong about some of the technical matters I discuss here, and I'd appreciate any corrections.
UPDATE: See also the playlist I created on this topic. It contains a few sources I found since writing this.
UPDATE: There's a thread at Linux Weekly News about an article in NewsForge titled "Getting in touch with the feminine side of open source."
UPDATE: Máirín has a thoughtful response you should read.
Introduction: Proprietary and Open Source Software
The software most people use every day – common applications like Microsoft® Word®, Adobe® PhotoShop®, and the like – is proprietary. That is to say, we pay for the use of it, and suppliers pay programmers to write the source code. Consumers purchase the software, install it, and use it. While consumers can use the software applications, because they are only sold the executable files, they cannot view or alter the source code. This means they cannot write new modules or tinker with existing features; for example, consumers can't make changes to a proprietary word processing program's bulleted list feature to add a new style of bullet or write a module that would make the program recognize a given file format it does not currently recognize. In proprietary software applications, the code is under traditional copyright, and because the corporations only sell the executable program file(s), the user cannot view or build upon the source code. Instead, the user must wait for the next version of the program, hope the company has added the features she wants, and pay for the upgrade. Programmers who work for software corporations must sign confidentiality documents agreeing not to share the source code with any unauthorized personnel.