Posts

Posted on

Don’t mention the war

This article originally appeared on Geek Feminism.

Over at Livejournal, angelbob is gathering anecdata:

A friend recently said… that as a woman working in technology, she wouldn’t recommend that other women enter the field. She’s a system administrator… I’m not going to repeat her reasons here. Rather, I’d be very curious whether other women working in technical fields, especially system administration and/or programming, felt the same way. Anybody care to comment?

I find this is a bit of an elephant in the room in “women in technology” discussions, and so I (bravely! like John Tierney, no doubt) want to talk about it. It probably applies to “women in science” discussions and so on, I just don’t follow them as much.

There are women, quite a few in fact, in technology careers who suggest other women don’t enter them. They usually find this is a unpopular opinion in the harming the community direction. Often some of their major critics are other women, especially women who are running recruitment and outreach for the field. The argument generally goes like this: the major thing that will fix sexism in this field is more women! So if we stay silent and take the sexism bad with the geeky good for long enough, sexism will solve itself. By encouraging women to stay out, you are basically furthering sexism in this field. QED.

Let’s pick this apart. First, purely as a practical matter, even in the forthcoming geek feminist utopia, some women will be talented programmers or engineers or mathematicians but will choose to spend most or all of their life in a different field. The human endeavour is not a zero sum game, we have not “lost” someone when she becomes a nurse or a musician.

Second, we don’t want to be denying women’s experiences. If a geek career was hard, unpleasant and not ultimately worth it for her, she should say this, and if it was related to her being a woman, it makes sense to recommend against it for other women. It’s hard to hear this if you are among the women who passionately love their geek work and want to share the good news, but those of us who are more in the advocate line surely do not want to spread the message that if women so much as hear negative experiences about geekdom they’ll all flee. If women’s interest in geekdom comes at the expense of lying to them and denying other women’s negative experiences, then the cause of women in geek careers isn’t worth it. Women can listen to passionate detractors, passionate advocates and people somewhere in between, consider their own experiences, and make up their own minds.

And lastly, women do not in fact bear the responsibility of ending geekdom’s sexism, and even if we did, we couldn’t. It is, in fact, ultimately down to the most powerful people to bear the bulk of the burden for changing the social environment. Having a field become 50 or 75% women has some effect on the stereotype effect, but it is not a magic de-sexist-itising measure.

How about you? If you left a geekdom or a geek career, or are a passionate critic of it (and aren’t we all, since pretty much any criticism is subject to the tone argument) have you been told not to discourage women, or that you are undermining the work of advocate women?

Posted on

The latest essentialism go-round: do we dare to discuss?

This article originally appeared on Geek Feminism.

Showing up on our Linkspam radar this week is John Tierney’s article for The New York Times, Daring to Discuss Women in Science, which is another round of “I am going to challenge the groupthink and be the one person who dares to make gender essentialist arguments about women in technical fields [well, me and that army over there]”. It argues from a finding among very high performing high school students, the top 0.01 percent of the population as sorted by the SAT and ACT standardised tests in the US, from which the researchers concluded that there’s distinct gender differences among students with that sort of performance.

Tierney writes:

The boy-girl ratio has also remained fairly constant, at about three to one, at the right tail of the ACT tests of both math and science reasoning. Among the 19 students who got a perfect score on the ACT science test in the past two decades, 18 were boys.

Meanwhile, the seventh-grade girls outnumbered the boys at the right tail of tests measuring verbal reasoning and writing ability. The Duke researchers report in Intelligence, “Our data clearly show that there are sex differences in cognitive abilities in the extreme right tail, with some favoring males and some favoring females.”

Here’s a roundup of feminist/women-in-science-o-sphere responses, many via SKM at Shakesville:

  • Anna N., 3 Problems With The “Women In Science” Debate: If boys and girls, men and women had truly equal opportunities, we might be able to conclude something about their “innate abilities” ”” or at least stop worrying about gender inequality in various fields. But we’re still very far from that point. Tierney finds fault with programs to eliminate bias at the university level, and says, female scientists fare as well as, if not better than, their male counterparts in receiving academic promotions and research grants. But girls may be implicitly or explicitly discouraged from pursuing science long before they actually become scientists…
  • Caroline Simard, “Daring to Discuss Women in Science:” A Response to John Tierney: The problem with the biology argument that “boys are just more likely to be born good at math and science” isn’t that it’s not “politically correct” — it’s that it assumes that we can take away the power of societal influences, which have much more solid evidence than the biology hypothesis. Tierney makes the point himself in his article…
  • Christina Agapakis, Adventures of Women in Science: The irony here being that this article is a very clear example of some of the social biases women in science face every day, just one of the countless attacks and indignities that make it that much harder for women to get up and go to lab every day, to achieve great things in math and science.
  • Janet D. Stemwedel, John Tierney thinks he’s being daring: On the general subject of claims for which there does not does not exist relevant empirical evidence, are there any published studies (or any research projects currently underway) to explore the connection Tierney, Summers, et al. seem to assume between being in the extreme right tail of laboratory measures of mathematical and scientific aptitude (like the math section of the Scholastic Aptitude Test) and having the chops to to get a doctorate in science or to win tenure at a top university?
  • SKM, Daring to Discuss Women and… *Yawn*, which also includes several links from the Larry Summers debate and earlier: For that matter, I think the “daring” idea that women are innately inferior to men at various Important Things–and indeed the preposterous notion that the idea is “daring” to begin with–has been answered quite competently in the past
  • Gretchen Keller, Women in Science: 2+2=?: …one of my least favorite, yet thought-provoking questions is “How does it feel to be a woman in science?”. Usually I reply that it feels the same as it does for a man: frustrating, time-consuming, invigorating and mostly like a bird flying repeatedly into a window desperately hoping that one of these times that pane of glass will turn into thin air.
  • Amy E. Slaton, Erring on the Side of…Exclusion: I know, I know: sarcasm is petty and unattractive. So before I lose any remaining credibility, let me defer to Troy Duster’s brilliant historical discussion of biological understandings of intellectual capacity. For almost 20 years, editions of his book, Backdoor to Eugenics, have laid out the very worrisome political and cultural implications of our pursuit of biological bases for intellectual and behavioral differences.
  • Clara Raubertas, “daring” to draw unscientific conclusions from statistics: Of course, his conclusions aren’t very scientific. Here are a few of the unfounded assumptions he has to make to draw the conclusions he draws… The assumption that science is so hard that it’s really only suited for people with extremely high scores (in the top fraction of a percent among a group of students who are already in the top fraction of a percent among their peers)
  • Melissa, The never-ending discussion: biology or bias?: What I find most frustrating is that there are myriads of studies, and everyone can cite their favorite study to support their viewpoint ”” be it that bias is the dominant factor keeping women out of sciences or that biology accounts for the paucity of women… I found what may currently be the best, though still imperfect, antidote to the never-ending, go-nowhere discussion of this topic, namely Stephen Ceci and Wendy William’s book, The Mathematics of Sex: How biology and society conspire to limit talented women and girls.
  • FemaleScienceProfessor, But I Don’t Want to Write about John Tierney Again: Thanks for all the e-mails and comments with links to the New York Times commentary by John Tierney, but what he wrote is just more of the same of what he’s written before: i.e., many women don’t want to be scientists or engineers, others can’t because they aren’t as good at math as the guys. Oh yeah, and Larry Summers made some reasonable statements in a speech that was misunderstood by hysterical females.
  • Hannah (in reply to FemaleScienceProfessor), Daring to Discuss: While I do understand this fear, how else are we going to convince the scientific establishment, many of whom likely share Tierney’s views, that gender bias is real and actually does keep women from succeeding in science careers? Clearly, just waiting for the old guard to pass on isn’t working, because I’ve met plenty of young male scientists who are just as biased as the old ones: they just hide it better.
Posted on

larch: migrating mail between IMAP accounts

I recently had to move several gigabytes of email (not my own, work-related) into Google Apps (Gmail). As best I can tell, the way most people do this is that they grit their teeth and they open up a graphical email client and drag folders one-by-one. It’s a one-off job for most people.

There were a couple of reasons I didn’t want to do that. One is that I was on my parents’ DSL connection at the time and pushing gigabytes of data through someone’s DSL is a violation of good guest principles, at least in Australia. The other is that we have over 500 folders in the account I’m talking about: that’s a lot of mouse pain.

Anyway, here’s your answer, if you are in the same position as me. After substantial searching, at least for this kind of tool, I came across larch, which is a Ruby command-line tool for IMAP-to-IMAP moves, most tested on Gmail and essentially designed for the “move my mail archives into Gmail” use-case. It’s much more mature than most of the one-off scripts people have thrown up on the ‘net. It certainly seemed robust over this volume of mail, although I did have to run it a couple of times to get past a few errors (it does not re-copy already copied mail, so re-runs are fast). It deserves more search juice.

If you wanted to keep two accounts permanently in sync, offlineimap would be the tool of choice, although the manual still seems to regard IMAP-to-IMAP syncing as not as robustly tested as its core mode of operation, which is IMAP-to-Maildir.

Creative Commons License
larch: migrating mail between IMAP accounts by Mary Gardiner is licensed under a Creative Commons Attribution 4.0 International License.

Posted on

Viewing attachments when using mutt remotely

Yes, that’s right, I’m still in the dark ages and do not yet use Gmail for my email. Even though it has IMAP and everything. I still use Mutt.

I almost always use Mutt locally, using offlineimap to sync IMAP folders to local maildirs. This means I don’t usually have the problem of being unable to view non-text attachments. However, for the next little while I’ll be using Mutt on a remote connection.

Don Marti has one solution to this, which assumes that you are accessing the server with Mutt on it via SSH (probably true) and are easily able to create a tunnel to your local machine, which is trivial if you are using a commandline ssh client, but while you can do it with PuTTY I figured it was just annoying enough that I might not bother. (And I doubt you can do it at all with those web-based SSH clients.)

My alternative assumes instead that you have a webserver on the remote machine that has mutt on it. It then just copies the attachment to a web-accessible directory, and tells you the URL where you’ll be able to find the attachment. It’s thus a very trivial script (and I doubt very much it’s the only one out there), but perhaps using mine might save you fifteen minutes over coming up with your own, so here it is:

copy-to-dir.sh (in a bzr git repo)

Sample output is along these lines when you try to view an attachment in Mutt:

View attachment SOMEPDF.pdf at http://example.com/~user/SOMEPDF.pdf Press any key to continue, and delete viewable attachment

In order to use it, you need to:

  1. copy the script to the remote machine where you use mutt;
  2. make it executable;
  3. edit it to set the OUTPUTDIR and VIEWINGDIR variables to something that works for your setup;
  4. set up a custom mailcap file much like the one Don Marti gives, that is, put something like this in your ~/.mutt-mailcap:
     text/*; PATH-TO-SCRIPT/copy-to-dir.sh %s application/*; PATH-TO-SCRIPT/copy-to-dir.sh %s image/*; PATH-TO-SCRIPT/copy-to-dir.sh %s audio/*; PATH-TO-SCRIPT/copy-to-dir.sh %s
  5. set mailcap_path = ~/.mutt-mailcap in your ~/.muttrc file.

Something like this probably could work for Pine and other text-based email clients used remotely too, but I’m not sure how because I don’t use them. And if someone wants to document this in a way that assumes less pre-existing knowledge, go ahead.

Also, making your attachments web-accessible means that they are, well, web-accessible. I’ve set up a HTTP Auth-protected directory using https for this, you should think about your own setup too.

Creative Commons License
Viewing attachments when using mutt remotely by Mary Gardiner is licensed under a Creative Commons Attribution 4.0 International License.

Posted on

Many roads, one surname

This article originally appeared on Hoyden About Town.

In yesterday’s SMH Catherine Deveny asked Why do (don’t go there) most children(don’t go there) still end up with (don’t go there, don’t go there, don’t go there!) their father’s surname?

She’s fairly clearly talking about a certain, already small and reportedly shrinking, milieu, that of heterosexual couples forming a nuclear family where the male and female partners have different surnames. She’s particularly talking about legally married couples, because in that case there is a socially visible ‘choice’ available to the female partner to use her birth surname or adopt her husband’s surname, or, I think even more rarely, some combination thereof. (Deveny has discussed women’s own decision here and it made it to Hoyden in 2007.)

Of course, we’re already in problematic territory here, in our last surname discussion WildlyParenthetical had a great comment in which she wrote:

[A structural analysis of surname choice as a feminist decision] assumes to know, in advance, the entire significance of a choice. In fact, it says that the entire (feminist) significance is given by its capitulation or resistance to a particular dimension of patriarchy…

… it can erase the heteronormativity of the issue to begin with… it can erase a colonialist, imperialist and racist history… it can erase the moments in which one has been disowned, or a survivor of violence, the moments where the very nuclear family structure enforced by surnames has been the cause of great damage…

Here I am under the microscope though. I had a son last month, my own first child and the first child of my long term heterosexual relationship. Moreover, his father and I are legally married. I’m white and of largely British Isles descent: this surname tradition is my cultural heritage. And I use my birth surname both socially and professionally, as does he: of course, my choice to do so is marked, and his isn’t.

My son? His surname is the same as mine, rather than his father’s.

While I was pregnant, we worked over this problem a lot, because I was very struck by the comment of zuzu’s that tigtog brought to our attention: You may feel you have great reasons for choosing the option which just happens to be what the patriarchy has greased the rails for you to do rather than taking the harder path of going against tradition. But having good reasons doesn’t mean that you’re not adding your own grease to those rails… Deveny observes much the same, that there are many many many reasons, but very much one likely outcome.

I come with a great big helping of privilege, and I’ve greased plenty of rails already and figured that the punishment I’d take for thinking about adding a teeny smidge of friction here was small, but it still took a great deal of energy to reach this decision. It took a great deal more for me than for my husband of course. I considered a lot of options: the children using the surname of the same-sex parent, inventing a new family name entirely, and so on.

I’ve ended up liking using my surname because it’s a distorted mirror of the usual decision. There’s very few objections to it that don’t also apply to the most common decision. Input from others vastly tended to focus more on what he and his family would lose than what mine would gain. Neither of us has brothers: sisters are so unreliable when it comes transmitting surnames! Several people took it out to cousins: I have more male cousins with my surname than he has with his. Trouble he might have dealing with travel or school documentation were raised more often than trouble I might have.

I am not kidding myself that this was Big Activism for me, it was low risk to my safety, my relationships, my right to parent my son. And I’m much more pleased to share a surname with him than my husband is sorry not to. (Of course, if he becomes very sorry, he can always change his name…) In some ways though, that makes me extra glad with the decision to do the, or at least an, unusual thing.

Posted on

Ethics of Free Software community research

Most of this entry is exactly a year old today and it’s just sat around in draft form all that time. Since I posted something similar on Geek Feminism about research into women in tech and similar topics, I thought I’d get it out there.

In January 2009 a researcher named Anne Chin of Monash University Law emailed the chat list for the linux.conf.au 2009 conference asking for research subjects to be interviewed about licencing and Open Source software. There were several responses criticising her use of HTML email and Microsoft Word attachments. I’ll leave the specifics of this alone except that people should be (and probably are) aware that this is almost always an unknowing violation of community norms.

I did, though, think about making some notes on research ethics and Free Software research. A bit about my background: I am not a specialist in ethics. I’m somewhat familiar with ethics applications to work with human subjects, but not from the perspective of evaluating them. I’ve made them, and I’ve been a subject in a study that had made them.

For people who haven’t seen this process, the ethical questions arising from using human subjects in your research in general covers the question of whether the good likely to arise from the outcomes of the study outweighs the harm done to the subjects, together with issues of consent to that harm. (There are many philosophical assumptions underlying this ethical framework, I don’t intend to treat them here.) Researchers in universities, hospitals, schools and research institutes usually have to present their experimental designs to an ethics committee who will determine this question for them and approve their experiment. Researchers who work across several of these (eg, a PhD student who wants to interview schoolchildren) will need to do several ethics applications, a notable chore when the forms and guidelines aren’t standardised and occasionally directly conflict. Researchers working for private commercial entities may or may not have a similar requirement. Researchers who use animals also have to have ethical reviews, these are done by animal ethics committees, which are usually separate.

At my university, essentially any part of your research that involves measuring or recording another person’s response to a research question and using it to help answer that question needs a human ethics application.

The good/harm balance may include very serious dilemmas: is there a health risk to subjects? how will the researcher manage the conflict between maintaining subject confidentiality and research integrity and the good of her subjects or the requirements of the law if she uncovers, say, episodes of abuse or violence? But it also involves less immediately obvious and serious ethical questions. Is this study a giant waste of subjects’ time? is considered a question of ethics by ethics committees, and is in fact the most serious problem for linguistics research, since there’s very seldom an outcome of particular interest to the subjects themselves.

The study in which I took part a few years back was towards the serious end actually: it was a study into the psychological profiles of people who have an immediate family member who had cancer as a child and involved both questionnaires and a phone interview with a psychologist. Both because the study explored memories of the illness and because the profiling included evaluating depressive episodes, suicidal ideation and so on, it came with a detailed consent form and with information about a counselling service that had been informed of the study and was prepared to work with its subjects.

In the case of the Free Software community the ethical questions are often more towards the waste of time? end of the spectrum than the more immediately serious end. It’s important to understand that this isn’t necessarily the case though. Here are some more cutting ethical problems:

  • getting findings that expose your subjects and/or their employers to intellectual property claims; or
  • revealing that your subjects are breaching employment contracts in some way (generally also related to IP) and thus exposing them to job loss and possible civil action.

Getting ethics approval to carry out workplace studies can be fairly hard precisely due to problems like these. But in the rest of this post I will treat the waste of time problem.

Firstly the basics: are your subjects going to be identifiable in your final reports or to the general public? If not, who will know who they are? Can a subject opt to have their responses removed from the study? When and how? All this should be explained at the start. (Usually if an ethics committee has been involved, there’s a consent form.) If doing a survey look into survey design, in order to construct non-leading questions and such.

Now, for specifics. Most of them arise from this principle: there are a lot of researchers working, in various ways, on the Free Software community, possibly making it a slightly over-studied group if anything. This places the onus on the individual researcher to demonstrate to the community that their project is worthwhile and that they’re going to do what they say. Thus:

  1. demonstrate some familiarity with the background. Depending on your research level this could mean anything from demonstrating a knowledge of existing anthropological work on Free Software (say, if the research project is for your anthropology PhD) down to at least understanding the essential concepts and core history (say, a project at high school level). This can be demonstrated by research design, eg asking sensible well-informed questions, but actually mostly requires a bigger time investment: making appearances in the community, either virtually or physically, ideally for a little time before asking the community to help you get your PhD/A-grade/pass.
  2. don’t get the community to design your experiment for you. Have a specific goal, more specific than get people to write me lengthy essays about Free Software, and get ideas from that and write about them. In the general case, the ask people incredibly vague stuff and hope they say something interesting technique fails the waste-of-time test.
  3. give your results back to the community. The most common problem with the various surveys, interviews and questionnaires sent to the Free Software community is that responding to them is like shouting into a black hole. It is not unheard of, of course, to see the thesis or essay or roundup that comes out of these, but it is unusual, relative to the number of requests. Most of the time the researcher promptly disappears. Researchers should come to the Free Software community with an explanation of when and where they will make the results of the study available. They should explain the aims in advance unless this would compromise the results. (On that note: Anne Chin is giving a linux.conf.au talk this year.)

Creative Commons License
Mary’s helpful guide to soliciting research participation on the ‘net by Mary Gardiner is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Posted on

University colleges: nurturing a rape culture

This article originally appeared on Hoyden About Town.

Warning: this post has graphic quotes from and links to mainstream media accounts of rape culture and imagery, and sexual violence.

One of the profoundly disturbing aspects of rape culture discussions—and this won’t surprise readers here—is the way that they reveal the confident assumption that there are rapists, who are evil and other and unresponsive to any form of social control, and then there are the rest of us, who can be exposed to any number of conflicting messages about rape—sexy rape, not-rape rape, that-type-of-girl rape, he’s-such-a-good-fellow rape—and emerge with our anti-rape moral compass intact.

There is no single place in my own experiences that taught me that this is wrong more thoroughly and dramatically than university residential college.

Continue reading “University colleges: nurturing a rape culture”

Posted on

Conference recordings and harassment

This article originally appeared on Geek Feminism.

The problem

At technical and other geek conferences and events it’s becoming increasingly common to either video talks by default, or in some cases to refuse to allow any speaker to opt out of being recorded while still being allowed to give their talk. I have been told a couple of stories of harassment related to conference videos, as follows (all individuals are women, some have been anonymised, none are me):

S gave a talk at a professional conference and related the following experience in chat:

S: linkedin pm I just got: “wow- you’re alot more younger and attractive than I imagined!.Thanks for showing your picture!”
S: I don’t like photographs and don’t let my likeness out much online. But a professional talk I gave a couple weeks ago was videoed (with my knowledge and consent). This was the result.

C gave a talk at a technical conference and a recorded version was also published with her consent. She subsequently received an anonymous email with a list of time offsets for the video and sexual commentary on her appearance at those time offsets.

Geekfeminism contributors also shared stories:

  • Leigh, in reply to S’s story:

    I got one of those on Facebook a few weeks back, from someone I know in the local Linux community, saying I was “so hot” and asking if I was giving any more talks this summer. This is someone I know only professionally, and not even well at that.

    I replied with a link to Juliet’s ‘and she’s cute too!’ blog post…

  • Skud has received several messages with offensive commentary on her appearance based on videos and photographs of her talks. A couple of events have recorded her without first obtaining her consent; in one case, she spoke to the photographer afterwards and asked for the video not to be published.

See also the Wiscon troll incident.

What to do about it

Based on these stories, there are several concerns about recording conference talks that conference organisers should be thinking about when planning to record talks:

  1. Consent to recordings must be obtained from all speakers, in advance.
  2. Have an optional, opt-in, recording scheme for talks. As these stories demonstrate, people have had harassment experiences, some very creepy and cruel, related to being recorded, or have reason to fear them. People may well decide that they’d prefer not to be recorded for this, or other, reasons. If your conference has a “if you don’t want to be recorded, withdraw your talk” policy, you will exclude those people from speaking.
  3. It’s not feasible to get attendee consent, but in your conference handouts, warn attendees that their questions and possibly other conversation may be recorded during talks.

Possible alternatives to making recordings of speakers include publishing slides only, or making a slidecast of their slides and the audio of the talk. (Note that the latter can also be considerably more useful than visuals of the speaker.)

Separately, some women (in particular) intensely dislike the paparazzi atmosphere that some geek events have, in which everyone can be photographed at any time. In your event’s code of conduct, consider addressing the question of whether photographers should seek consent from individual subjects to either photography or to publication of photographs.

What’s your experience with event recording, especially video and photography? Can you think of any other ways in which recording is problematic, or other guidelines for event organisers to help with these problems?

Note to commenters: the “you should be flattered” discussion will not take place in this post. Thank you.

Posted on

Why we document

This article originally appeared on Geek Feminism.

A comment over on the Geek Feminism wiki asked whether we aren’t damaging the community by documenting sexism. I don’t want to get too 101 on our fine blog, but I do want to talk about why I consider our pretty long list of sexist incidents in geekdom a success.

My first geek feminist forum, and still the one I participated longest in and therefore in many ways most influential on me, was LinuxChix. Things I learned over there included the reasons why having men dominate conversations can be anti-feminist, via the discussion around the document now available as behaviour in technical forums, which was originally a response by Valerie Aurora to a problem where the LinuxChix techtalk list was seeing fewer and fewer posts by women and was generally perceived as scary and hardcore.

We also had a long-standing problem articulating what it was that led to the extreme gender imbalance in Free Software development and many of its user communities. I can’t speak for the community, but what I remember feeling about those discussions was a major unease. There was sexism in computing and in Free Software… probably? Some women had stories, some women didn’t. There was social, peer and societal pressure on young women considering science and technical careers or even on developing those skills… probably? Again, some women had stories, some didn’t.

Had you asked me in 2003 for troublesome incidents in Free Software””are we doing anything wrong, or is this a problem we’ve inherited from other people who did things wrong, or is this just a thing about women, that they don’t like to be too nerdy in their spare time?””I don’t know that I would have been able to give you examples of anyone doing anything much wrong. A few unfortunate comments about cooking and babies at LUGs, perhaps. Things started to change my awareness slowly. Valerie’s 2002 HOWTO Encourage Women in Linux dug up some incidents at LUGs. In 2005 LinuxChix itself got some attention from (trigger warning) the troll Skud posted about. I was personally present at a sexualised presentation, the Acme::Playmate presentation at the Open Source Developers Conference in 2006. And in 2007, very soon after I had seen Kathy Sierra keynote linux.conf.au 2007, she was scared out of her work writing about technology by (trigger warning) online harrassment and for the first time, I personally saw the Internet explode over the issue of active, virulent sexism against women in technology.

I do not in fact find writing the wiki documentation of incidents in geekdom very satisfying. The comment linked at the beginning of the post compared the descriptions to a rope tying geekdom to the past. Sometimes being known as a wiki editor and pursued around IRC with endless links to yet another anonymous commenter or well-known developer advising women to shut up and take it and write some damned code anyway is like a rope tying me to the bottom of the ocean.

But what makes it worth it for me is that when people are scratching their heads over why women would avoid such a revolutionarily free environment like Free Software development, did maybe something bad actually happen, that women have answers. It’s not the only answer, there’s still all that social, peer and societal pressure, the shorter leisure hours, and so on, after all. And there’s no level of harrassment or cruelty that won’t find someone, plenty of someones, prepared to immediately argue that it’s really no big deal, what are you doing here, giving up? Letting them win? But now if when I’m asked about whether geek women have problems and why there aren’t more of us, I’m not left fumbling to explain it even to myself.

I don’t know what the Mary of 1999 (my watershed geek year wasn’t 1998, in fact) would have done if she’d come across that page in more or less the condition the wiki comment described, “the girl entering the community without any predispositions”, the woman vulnerable to being misled into thinking that geekdom is full of scoundrels (or, we might argue, not entirely misled). Maybe she would have run, I can’t say for sure that she wouldn’t have. But what woman is without baggage? In 1999 as a teenage girl with hair flowing down to my waist (I tell you what, short hair has cut my street harrassment down nearly as much as it cut my grooming routine down) I walked down the street to the steady beat of rape threats from passing vehicles. At least I would have found that geek women were talking about it and had got together and got each other’s back.

Posted on

“Girl stuff” in Free Software

This article originally appeared on Geek Feminism.

This is an edited repost of a blog entry of mine from February 2009.

In January 2009 I gave a talk at the LinuxChix miniconf held as part of linux.conf.au 2009. It was titled ‘Starting Your Free Software Adventure’ and used women developers and community leaders as examples. The idea was to show people what the first steps look like. I conducted (extremely short) email interviews of several women involved in Free Software or Culture or their communities, including Kristen Carlson Accardi, Brenda Wallace and Terri Oda among others.

One thing stood out and kept coming up all week: Terri mentioning that she had resisted at times working on things perceived as ‘girl stuff’. In Free Software this includes but is not limited to documentation, usability research, community management and (somewhat unusually for wider society) sometimes management in general. The audience immediately hit on it, and it swirled around me all week.

This is a perennial problem for professional women: software development is by no means unique in having developed a hierarchy that goes from high status roles disproportionately occupied by and associated with men to somewhat lower status roles disproportionately occupied by and associated with women. (In the case of software, disproportionately occupied by women still means male dominated of course, at least in the English-speaking world.) It’s difficult to disentangle the extent to which women and/or their mentors and teachers self-select for the lower status roles (and I would hardly argue that the self-selection occurs in a vacuum either) versus the extent to which they are more or less barred from high status roles versus the extent to which the association is actually flipped and professions and jobs within them have become low status because women started doing them. Other well-known examples, are, for example, the concentration of women in biological sciences as opposed to, say, physics, the different specialisation choices of male and female medical doctors and surgeons, and so on. Sometimes, as in the war between sciences, the status of a field is somewhere between a joke and real, to the extent that those can be differentiated, but often it isn’t: there’s a correlation between the male to female ratio of a medical specialty and its pay.

In all of these cases, a woman who is conscious of this problem tends to face a choice. Do the ‘girl stuff’, or not? (Of course, ideally one rejects the dichotomy, but no individual woman is responsible for constructing it.) And some, although I don’t know what proportion, of women feel guilty about their choice, especially if they do choose to do girl stuff. Just go ahead and imagine your own scare quotes from now on, by the way.

It also gets messy in various other ways. There’s the extent to which a woman who doesn’t do girl stuff is invested in maintaining the status of her boy stuff role and also the aforementioned vicious cycle where if women are doing something, it will come to be seen as not particularly hard or noteworthy.

Most concretely, I usually see this tension bubble away underneath outreach programmes promoting computing careers (you know what, I have my own status issues and I still resist calling it IT) to women. There’s the people who want to go for yeah we all know coding is populated by weirdos, and male weirdos at that, luckily you don’t have to be a geek and you don’t have to code, phew! I tend to hear about that one only once my outreach friends have gotten involved and staged a coup, admittedly. There’s the there’s so many opportunities in computing, and yes, coding is one of them and its fulfilling and it’s something you can do, but dammit, coders get all the cred and attention and dammit can we talk about something else? Women who admin/write/test/manage rock! And there’s you know, women coders don’t exactly rule the world yet, and furthermore isn’t all this oh-yes-you-could-code-I-guess-and-that’s-a-fine-thing but look! something for folks with people skills! talk basically a soft version of ew coding that’s for boys, also, last I checked, math is hard?

I observe again that there’s no right answer here in the real world right now. Women doing girl stuff have good reasons to feel dissatisfied that their hard-won skills are underpaid and under-respected, women doing boy stuff (scare quotes! please insert!) want other women to know that there’s fun to be had over here, thank you.

One crucial point in my thoughts about this I stumbled on only after the conversation Brianna Laugher recounts, over Indian food on the Friday night (the location of all major conference breakthroughs worldwide). She said”Š”””Šparaphrased”Š”””Šthat she didn’t feel that she should have a problem or be criticised for doing what she is good at, or what’s so desperately needed in her communities, and have to be just another coder in order to be fully respected. And I said that while this was certainly true, women also need to have the opportunity, to give themselves the opportunity, to be selfish: if we want to code, or do something else we are currently either bad at or not notably good at, or for that matter which we are good at but in which we’d have competitors, we should consider doing that, rather than automatically looking for and filling the space that is most obviously empty. However women are justifiably reluctant to enter places where they aren’t obviously welcomed, and what better way to be welcomed than to do work that needs doing and not become just another person doing the coding free-for-all and delaying external validation for potentially quite a long time?

I have no answers. Just the perennial question of distinguishing what other people want, what other people claim they want, the genuine satisfaction of being of service to someone, and the genuine satisfaction of knowing you’ve done a good job of something hard. Where do you like to stand on that?