Category: Tech community

Posted on

Your women's networking event; mothers need to plan

This post is inspired by a specific event, but I have contacted the organisers privately with a specific complaint/suggestion, so I’m not posting this publicly to slam them, or naming them here. But I think the ideas are more generally useful.

If you run career networking events for women (or anyone! but it’s more obvious if they’re targeted at women) you need to make it possible for mothers to attend them. Not all women are mothers, but a substantial fraction are.

How can you do this? Well, childcare for children from 0 to 12 or so would be awesome, but I realise it’s expensive and logistically difficult (certified safe space, insurance, qualified carers in the right ratios…). Here’s something that isn’t: specific advance publicity. That is, publicity that announces date, time (start and finish, or at least finish of the formal bit, eg “6pm to 8pm with socialising until whenever!”) and location. Because here’s what a mother will have to do:

  • there’s good odds a mother needs to be sure someone else will care for her child during your event. That someone else might be a co-parent who has a life of their own to plan, or it might be a non-household member (same) or a paid carer who needs to be booked (and budgeted for!) in advance
  • if your event is on a day when she does care, she will probably need to dress especially for your event
  • if your event is on a day when she does care, she will probably have to travel especially for your event

The appropriate minimum notice period is at least a week.

As a bonus, this is also helpful to part-time workers, unemployed people and students, all of whom all have to dress especially and travel in order to attend most networking events, and busy people, for that matter, and people who work in casual-dress jobs.

A slight tangent, but something else I wish networking events did: be more specific about the catering. So many go from, say, 6pm to 9pm and specify something about a “light meal”, which in the extreme can constitute a couple of spring rolls per person. I’m a long-term breastfeeder, at the height of production I’ve had to eat something like five substantial meals in a day. Even before I was pregnant, I ate good sized dinners. I understand that your event likely won’t have a full sit-down meal, but I’d much rather get info like “light snacks will be provided, there’s a food court at $address if you want to eat beforehand” than “our sponsors are catering a meal! awesome $sponsor!” when it turns out I will need to leave early (in tears, because noise and hunger overwhelm me) and buy a whole second meal at 9pm.

Posted on

Some resources for people who want to be allies

This article originally appeared on Geek Feminism.

This is a 101 post and all of the links here are fairly well known to ‘net feminists, but Noirin being assaulted has caused newcomers to wonder what they can do to help create a safer environment for women and others at risk of assault.

Newcomers: we welcome your help! Here’s some things you could look at.

The Con Anti-Harassment Project: is a grass-roots campaign designed to help make conventions safer for everyone. Our aims are to encourage fandom, geek community and other non-business conventions to establish, articulate and act upon anti-harassment policies, especially sexual harassment policies, and to encourage mutual respect among con-goers, guests and staff. They have a lot of material, see particularly their tips for conferences/conventions who want to create a policy and their FAQ. If you aren’t an organiser, you could make a point of requesting an enforced policy from conferences you attend, and thanking those that have them.

Check out the The Open Source Women Back Each Other Up Project & Gentlemen’s Auxiliary which is more informal: you can share stories of harassment, assault and successful backing each other up, organise meetups at cons you attend, and purchase gear.

Make it not okay, really not okay around you to say the kinds of things people said to and about Noirin. You, presumably, believe* that women can attend conferences and go to bars and have fun and have male friends and consensually touch people and have a romantic/sexual history and have photos of themselves online and be a feminist and have the absolute right to refuse consent to intimate social situations, to touching and to sexual activity. You, presumably, also believe people you personally despise, or aren’t your idea of fun, or who hold opinions you disagree with, or who have hurt you in some fashion, have the absolute right to refuse consent in the same way. You presumably believe that sexualised approaches to people, and sexualised interactions with them are harassment unless they are welcome. If you believe those, and you are around people who don’t, don’t let them believe that they are with allies, if and when you have the power for that to be safe.

Valerie Aurora points out also that if you attend events where harassment and assaults are happening and the event organisers and atmosphere are ignoring or contributing to the problem, stop going if you can. Support spaces that are doing better.

Finally, because I couldn’t find this written up in one place in a bite-sized way, don’t tell people what they have to or should do about abuse or assault or harassment. Abuse, assault and harassment are about withholding power from someone, about denying them self-determination. They need, and have a right to, the power to decide how to respond. It may be appropriate, if you are a witness or a good friend or an event organiser or the person on the spot or otherwise one of the people most likely to be able to help them, to offer them help in getting home, finding a shelter, getting some money, finding a crisis counsellor, going to the police, getting ongoing counselling, speaking out, overcoming fear of the next event, getting the hell out, now or in the future, as seems appropriate at that moment. And then let them decide whether they want to do that or anything else, and whether they want your help. (A reference in forming this thinking was Karen Healey’s Snakes in the grass. tigtog also pointed me at unusualmusic’s linkspam: Why didn’t you call the police? Part One.)

* If you do not believe the things in that paragraph we don’t really need to know why not.

Posted on

Noirin’s hell of a time

This article originally appeared on Geek Feminism.

Warning: this post discusses sexual assault and links to both a survivor account and to hostile comments.

Noirin Shirley’s post A hell of a time in which she describes her sexual assault at ApacheCon on the 4th November and names her attacker is starting to show up in our Linkspam suggestions and so on.

We’ve seen it.

This post has been widely linked by tech news sites, including (trigger warnings for comments at all of these places) Reddit, Hacker News and Gawker and while some respondents have been sympathetic to or angry for Noirin, there’s a lot of victim blaming in the usual ways: “don’t ruin his life over one mistake”, “don’t go to bars”, “asking for it”.

I think this is hard for us to write about, as several of us (including me) know Noirin either online or in person. We want to acknowledge what happened to her and how she responded (go Noirin!) but the ferociousness of the don’t-speak-out wasn’t-that-bad this-is-how-human-sexuality-works get-over-it this-isn’t-news deserved-it has hit us all hard. It feels like we’ve been working our teaspoons super hard for ages, and someone built another dam and filled it up.

And we are just onlookers.

Noirin: sorry about what happened to you, both the assault and the response.

Surely I don’t really need to say this: comments will be moderated. Leaving anti-speaking-out or compulsory-police-reporting or pro-sexual-assault or I’m-not-necessarily-talking-about-this-situation-but-here’s-a-hypothetical-where-the-alleged-attacker-gets-hurt comment here is a waste of your time.

Update: if you have links to share, please place a warning if that link, or any comments it is allowing, are victim-blaming.

Posted on

When you are the expert in the room

This article originally appeared on Geek Feminism.

This is an Ask a Geek Feminist question:

This a “what should we do” question, but a fairly specific one.

Recent discussions, particularly Restore meritocracy in CS using an obscure functional language , have left me thinking “this still doesn’t say what it would be helpful for people like me (white male with computing experience starting early) to actually do about it”. Just saying to avoid the viewpoint that this reflects enthusiasm or innate ability isn’t very specific, but the discussion seemed to finish around that point.

The answers will probably be different in different contexts. For example, how about in class? The best I can think of is “don’t be eager to answer the lecturer’s questions to the class, but let someone else go first”. Would that help? Is that enough, in that context? But if you give the lecturer the impression you’re not knowledgeable, but then do well in the written exam, you can invite suspicion of cheating in the exam (this definitely happens). Or should you even make deliberate wrong answers, to lower your apparent expertise? I’d find that horribly condescending if I knew someone was doing it towards me.

And in a professional context, if you know the answer to a colleague’s question (or on a mailing list, to any question), but you hold back on it to let someone else answer, you’re holding back the asker from getting on with whatever raised the question. But is that less important than letting others answer? (I suspect it depends on the group or list concerned.)

And a branch of that one, relevant in my present job, in which part of my role in the team is specifically to be the experienced programmer who can answer people’s questions, how is it best to handle that?

And in a seminar, should you hold back in a discussion if you have advanced ideas, so as not to scare the less confident? But then, you’re not making your best technical contribution.

The most extreme suggestion I’ve seen (only once, I think) is that geeky men should get out of computing altogether, to make it more comfortable for others to get in. In which case, a big source of potential mentors would be lost.

And do the same suggestions apply to female experts?

So, I’m stumped on this and can’t contribute any significant answers, but I hope the questions are useful for discussion.

There was some discussion among the cob-loggers about whether and how to answer this question. But there was always lots of confusion about this on the LinuxChix lists while I was subscribed (I haven’t been for a few years now), men who genuinely wanted to in some way to address gender issues in computing but the only strength they saW in themselves was their expertise, and when it was suggested to them that displaying this at every opportunity was at best annoying and at worst harmful they were completely at a loss. So I think an answer is genuinely useful.

Important note: this answer is aimed at privileged people (in this context, generally men with a good technical background) hoping to check their privilege and keep it on a short leash. If you are a woman reading this, it’s entirely possible the reverse applies to you in geeky environments: you might be wanting to learn how to have more confidence in your expertise and how to inspire confidence in others. Some of these techniques might be useful to you at some times when you want to help others learn, but this answer isn’t really intended for you.

Important note 2: from here on, “you” refers to the general you, the person who want to encourage/support/etc women but is struggling to see how to do it without being dishonest about your own abilities, not necessarily “you” the person who asked this specific question. I’ve seen this a lot, so I want to try and address it in general. I’m generally going to assume that the relative expertise of the question asker is in fact a correct assessment but you should question whether you are really the expert or whether you’re partly benefiting from structural assumptions that you are.

Let me start by stating that there are at best misguided versions of this question: people who say “I want to share my expertise with women who want to get into computing! But now I’m not supposed to be intimidating. Fine then, I’ll take my expertise and go home. See how you like that, women in computing! Ahahahaha!” Don’t be one of those people. Your participation in technical and geeky groups, especially groups for learners, isn’t solely about you. If you insist on either being the top dog expert or going home… go home.

My beta reader for this suggested that much of the question is based around the assumption that in order to help build people up, you have to drag yourself down. There’s two problems with this: one is that this sort of thing isn’t a zero sum game, and the other is that not all women (or outsiders in general) are also beginners. They may be intimidated in spite of substantial ability and experience. So in many cases your role is less to try and hide your own excessive light under a bushel, and more to support the discovery of what’s already there.

When you’re the expert at work

In terms of your workplace, an approach I like is one that some activist groups make explicit: if you are the only person who knows how to do something that the organisation needs, you should make it your top priority to train at least one other person to do it. You could do some of the following:

  • presumably part of your role as designated expert, or something that you can make part of your role, is keeping a sort of list (mental or physical) of areas of expertise other programmers have, and referring questions to the other experts.
  • if something should be documented, ask the person who consults you if she can document it as she learns it. Then you can refer future questioners to that documentation, or get them to improve it. And you can credit its authors when you point people to it. And by having people teach others and write for others, you are turning them into experts.
  • if something should be automated (for example, you are consulting on a fiddly manual process) ask the person who consults you if she can automate it as she learns it.
  • when you get too busy (and this sounds like the sort of role where you are constantly in more demand than you can satisfy) decide that someone else needs to be the expert on some subset of the organisations knowledge base, and come up with some kind of handover process in collaboration with her, so that she is confident in being able to handle that set of problems and people know to go to her without even involving you.
  • consider that your own expertise is unlikely to be all-encompassing. If there’s a task that takes you half a day and a colleague half an hour, ask her for her help with it. (No need to go on and on about how she’s the expert here yay for her, just get her help.)

Note that those aren’t specific to women colleagues despite my choice of pronoun. The idea is to change the environment such that expertise is being built everywhere, not to go out of your way to make women into experts, unless you are in an environment specifically focussed on women (like LinuxChix is).

Similarly, in teaching roles, it is important to know when someone is thinking out loud on their way to the answer and when they are genuinely stumped and starting to get too frustrated to make progress. In the former case, just let them think and give them some time to put those thoughts into action.

When you’re the expert in class

Some of the question about classroom behaviour does seem a little excessively fearful. I guess there might be some classes that are structured as lectures and a final exam, but all my classes at university involved submitted assignments throughout the course in which you can demonstrate knowledge without taking up class time. A class in which people must ask questions to demonstrate their knowledge, as opposed to asking questions because they need the answer sounds like it must be terribly tedious for everyone involved. And they must be awfully small classes, or really long ones, if everyone who doesn’t regularly participate but still does well in the class is then investigated for cheating. In general, if you are required to demonstrate expertise solely in order to pass, see if you can do so in a way that isn’t public.

In terms of being part of classes or seminars, it is situation dependent. Is the class or seminar or discussion a bit introductory for you? Perhaps you should absent yourself or remain silent while the others get the hang of things, or at least wait for one-on-one approaches from other students for help rather than taking up teaching time demonstrating your knowledge. Is it genuinely challenging for you too? Well, make it visible that you’re being challenged. Be that wonderful person who asks the lecturer half way through the class “uh, I don’t think I really understood that first set of hypotheses, can we slow up?” when everyone else thought it was just them. Throw a few ideas against the wall before you think you have the answer. If someone else has a good idea, give them space to express it, thank them, and then see if you can extend it, especially in a collaborative way with the original proposer. Watch the tendency to try and set up a you-and-me-the-smart-ones dynamic with the teacher by speaking up only when you’re totally confident.

It may help periodically to actually try and measure (by making notes of who speaks when, assuming you can do it subtly) whether you are the most talkative person in the class. If you are, take a break from talking: it’s unlikely your ideas are so uniformly superior as to need that much airtime, and if they are, perhaps you need a more advanced class.

My beta reader also suggests that if you find a classroom is centred around you and other confident students and generally being a little self-congratulatory and that other students are floundering and suffering, that perhaps you should have a word to the teacher about how you feel the classroom environment is letting most of the students down.

When you’re the expert in a women-centred geek forum

In situations like mailing lists, at least places like LinuxChix which have a specific mission to be encouraging and a good place for learning, here’s some tips:

  • Have a look at the average turnaround time of the discussion. Is it common for someone to wait 24 hours to have a question answered? Well, people asking for help are probably aware that they may need to wait 24 hours (unless of course they say something like “ARGH HELP NOW DON’T DELAY FIRE FIRE FIRE IN THE THEATRE”). So make that your delay. Wait 24 hours (say), and see if they got a decent answer yet. If not, then post.
  • Very important: before you post an answer, read the other answers. It’s a common problem to have a self-appointed expert insist on re-explaining the whole thing from scratch, rather than seeing that Suzy already sorted out Jane’s compile error, so you just need to help Jane work out how to get the info she needs out of the core dump.
  • If an answer worked, but is missing a nuance, or isn’t precisely how you would have done it, consider carefully if you need to point that out. Is it actually harmful in the long run to do it the other suggested way or is it a matter of taste? Is this a good time and place to evangelise on matters of taste? It usually isn’t.

Note that none of this is denying your interest, expertise or talent: it’s not about pretending not to have it, it’s about genuinely putting it at the service of other people, and about developing similar expertise in other people.

I think it’s also important to interrogate your motivations in being the expert in women-centred groups. All of these approaches are not uncommon in tech groups with a lot of women:

  • assumptions that you, a man, must surely be the only expert in such-and-such who is part of the group, because, really, how likely is a woman to be a such-and-such expert? (There were certainly subscribers to the LinuxChix lists who believed that this was true of all of Linux systems administration, to the constant chagrin of women members who had spent 20 years in the field.)
  • assumptions that women geeks, unlike men geeks, will properly acknowledge you and respect you for your expertise, finally, the admiration you deserve!
  • the good ol’ not having enough women in your social circle thing, and being there to make friends.

The last one is tricky: here’s my take. Nothing wrong with having friends or wanting more! But, when you aren’t in a social group, attend to the mission of the group first, and the socialising a distant second.

Posted on

The lamb roast roundup: Mums and censorship

This article originally appeared on Hoyden About Town.

Feminist criticism of the “It’s Time to Tell Mum” anti-filtering campaign has shown up on several blogs:

ZDNet Australia writer Josh Taylor picked up the story and contacted myself and Geordie Guy, vice-chair of EFA’s board, for comment in his article EFA apologises for ‘sexist’ anti-filter site.

[Geordie] Guy told ZDNet Australia the responses he received to his blog forced him to delete the entry.

“A couple of the comments that came in response to that were really abusive and I didn’t want to start or continue a fight, which is why the article was removed,” he said.

“We sincerely regret that the campaign offended some people,” Guy said, explaining that his personal musings on the blog were superseded by the apology from the EFA board. He said it was inevitable that the different approach to the censorship debate — and getting a comedian involved — would offend a few people.

“Needless to say, we didn’t set out to upset anyone and we don’t think mums are stupid — we think some mums are being treated as such by the government, who is playing on their fears without giving them the full story,” he said.

The EFA though have explicitly disclaimed any apparent apology in their own blog:

So contrary to reports elsewhere, like [Taylor’s piece], we aren’t apologising for the campaign – we’re happy with the way it turned out. Of course, we’d rather nobody was offended, and sincerely regret it. But offending nobody is only possible without any risk-taking, and a risk-free campaign is unlikely to break any new ground.

I’ve also transcribed the the Akmal Saleh video that’s part of the “It’s Time to Tell Mum” campaign.

Continue reading “The lamb roast roundup: Mums and censorship”

Posted on

So simple, even your mother will be opposed

This article originally appeared on Hoyden About Town.

My four month old has explained a lot of things to me. To date it’s been things like “it’s been four months and you still can’t tell the difference between tired and hungry? HERE LET ME SHOW YOU.”

But I confess that I was surprised last night by his cogent explanation of reasons to oppose the Federal government’s proposed Internet filtering scheme, thanks to Electronic Frontiers Australia’s It’s Time to Tell Mum campaign, which enabled him to simply explain things like even mums want an internet connection that’s faster, cheaper and more secure, if mums begin to rely on the filter to keep their children safe, rather than monitoring their children’s internet use themselves, children will actually be less safe than before the filter was in place.

And I have to thank him, and Electronic Frontiers Australia, because that was a lot clearer than the confused mother-logic authored by some mummy bloggers I know around these parts.

Seriously, is there some kind of bingo card for “getting mothers involved” yet? Here some squares to get you started, thanks to “It’s Time to Tell Mum”: mothers are late technology adopters, mothers are uninterested in technology and toys for their own sake, mothers are solely responsible for the moral welfare of children, (which is lucky because) mothers are pretty much only interested in the moral welfare of children, (which is also lucky because) fathers and co-parents might as well not exist. Any more?

See also discussion in the previous Open Thread.

Posted on

Is requiring Open Source experience sexist?

This article originally appeared on Geek Feminism.

Code Anthem’s Don’t Judge a Developer by Open Source (via Meg in the Open Thread) argues that companies that rely on Open Source coding contributions as a hiring criterion are both demanding a lot of their hiree’s free time and are sexist:

Open source is a culture. There are plenty of smart and passionate developers out there who are not part of that culture. And certainly there are plenty of dumb and curmudgeonly developers out there participating in open source…. There are there smarter ways to spend your time. The stereotypical open source developer works for a bumbling corporate during the day, doing dull work (but necessary to make money) and then comes home to work on his passion, OpenOKHRWUJ Framework…

Requiring open source contributions is sexist… Open source is dominated by men even more so than the programming community as a whole… it’s irresponsible to require your new hire developers to come from a male-oriented pool. Alas”¦ “Underrepresentation breeds underrepresentation”.

I have a comment in moderation there in which I say that I think the stereotype is incorrect: that Open Source developers in my experience are either university students or other young people with a lot of free time, or they’re paid Open Source developers. (I know hobbyist Open Source coders with unrelated dev or other full-time jobs too, yes, but not nearly so many and their contributions are for obvious reasons usually not as significant. If nothing else, this group has a really high incidence of typing injuries.)

But that’s a side-note: I think the core point of the post stands. Open Source is very male-dominated, is known for being unpleasantly sexist, and is also a subculture whose norms (even where neutral as regards sexism) don’t fit everyone. Requiring these norms feeds right into the problem talked about in Being Inclusive vs Not Being Exclusive:

People who come from underprivileged minorities are usually very experienced in the art of being excluded. Sometimes it’s overt – “we don’t like your kind” – but many times it’s subtle. They’re told that they’re “not quite right”, or they “don’t have the right look”, or “don’t have the right experience”, or just aren’t told anything. At the same time, they are surrounded by all sorts of imagery and communique about how they don’t quite belong, about how they have to change themselves to fit in, about how they are undesirable. They do not see a lot of examples they can relate to; even the ones that come close tend to stick out for being “Exotic”, being a token. They already have a lot of barriers against them and are already of the mind that they’ll more likely be rejected than accepted.

If you insist on a lot of experience in a particular male-dominated sub-culture as a prerequisite for a job, that reads as “we prefer [a subset of] men, basically, or at least people willing to work hard to minimise all the ways in which they aren’t [part of the subset of] men” even if you didn’t intend it to and even if you didn’t want it to.

Code Anthem isn’t, as far as I can tell, thinking about Open Source paid jobs in that post, but they of course have this problem magnified. It seems vastly reasonable on the face of it: hiring existing Open Source contributors, ideally people from your very own community, means you hire people who are well-versed in the particular mode of development you do, in particular, the use of text-based mediums for communicating among a distributed team. Since Open Source (or more to the point Free Software) projects are at least sometimes associated with particular non-commercial goals and philosophies agreement with those seems desirable. But since most long-term Open Source developers need to be paid for it, it strongly feeds into this cycle of long-term Open Source developers continuing to be male and of a particular kind of culture, and continuing to overtly or subtly signal that that’s who is welcome in Open Source development.

Possible other posts of interest:

  • Terri’s Want more women in open source? Try paying them.
  • Dorothea Salo’s Sexism and group formation:

    A woman can be an honorary guy, sure, with all the perquisites and privileges pertaining to that status””as long as she never lets anything disturb the guy façade.

    It’s good to be an honorary guy, don’t get me wrong. Guys are fun to be around. Guys know stuff. Guys help out other guys. Guys trust other guys. And in my experience, they don’t treat honorary guys any differently from how they treat regular guys. It’s really great to be an honorary guy.

    The only problem is that part of the way that guys distinguish themselves from not-guys is by contrasting themselves with women.

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.)
Posted on

Names, glorious names

This article originally appeared on Geek Feminism.

Some time back, I wrote:

We [on the LinuxChix lists] 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… There was sexism in computing and in Free Software”¦ probably? Some women had stories, some women didn’t.

Now we have our long list of incidents, but I want to highlight another list which I’m happier about, our list of women in FLOSS. Back in the olden days, say 1999 or 2000 or so, LinuxChix tried to make a similar list. The Wayback Machine tells us it got to ten names, and I recall a significant amount of head scratching going into that. Now we have a list of women that is no doubt badly incomplete, probably uncompletable, but nevertheless something like ten times the length.

Today, instead of scratching our heads about what women could possibly deliver a keynote presentation at a technical conference, we started listing women who have done so, and I suspect that list too is fated to remain drastically incomplete no matter how actively it is updated. This is an inexpressibly happy thing for me: too many women to name! Thank you geek feminist flowering of 2008/2009!

Are there recent sources of geek feminist inspiration the Internet has tossed your way? Any treasure troves of women doing things you hadn’t heard about before? (Recall, we define geekdom broadly here, there’s no need to limit yourself to tech.) Who are you a mad fan of right now?

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?