I have loved and supported Electronic Frontiers Australia (EFA) for many, many years. The love affair began back in uni, and coincided with my discovery of open source software. The power of freedom (as in speech) was heady and strong back in those days. Today, in many ways, it still is. Right now the fight is not so much against the big software companies though (although that's still up there), but the Australian government.
Senator Conroy has been banging on about introducing an internet filter for years now. I won't go into detail. If you're reading this blog, then it's a safe bet that you already know all about it. There are a lot of arguments against the filter, but they all revolve around one main tenet: freedom.
Which is where the EFA comes into it. They've really gotten onto the bandwagon, and have been perhaps the single most outspoken group against the filter (with the possible exception of Mark Newton). They have provided information for both the informed and uninformed public; organised and undertaken online and other forms of protest; collected, collated, and reported statistics and data; arranged means for interested groups to get together, talk, plan, and rant. And they've created 'campaigns' around the filter to both raise awareness of the issues, and inform the public on methods to avoid the filter becoming law. I've loved every minute of it.
But, for the first time ever, EFA has struck a sour note with me. And I'm not alone in feeling a little cheesed off, either. It's about the EFA's latest campaign, which has been dubbed the "Time to tell Mum" campaign. The basic premise is a comedy sketch featuring Akmal Saleh (who I've never liked all that much, mostly because he only seems to have one joke that he uses over and over again. But that's neither here nor there). Akmal, in his vaguely humorous way, tells us that we need to tell our Mums about the internet filter. This is because Mum's "love gossip" and "care about their families". He never really gives a good reason for this directly, but EFA themselves note that "[EFA] hope this campaign will reach some new people, and further highlight the myths about Conroy's Filter".
As with most things, the comments fall into two broad camps: Those who find the campaign sexist, and those that think that anyone opposing the filter is good people, and the feminists should just get over it already.
Do you want to know a secret? I'm not in either camp. I can see the issue with the sexist language. I can see how it enforces gender stereotypes, and how it is really just not helping. Hey, I'm a feminist from way back, and I'd be lying if I said I couldn't see that side of the argument with extreme clarity. I also, for what it's worth, completely support anyone who has the guts to stand up and yell about it. I strongly suggest you read "Goodbye Electronic Frontiers Australia" over at the Witty Title Pending blog for a great review of the feminist issues that have come up.
But, I can also see this from EFA's perspective. I can appreciate that they are trying to target a wider audience, an audience of people who care about their children and their families, and who are going to spread the word among the traditionally conservative-voting older generation. But it was disingenuous of EFA to target "Mums" specifically, when what they really mean is "older people who are less tech-savvy and interested in 'family' issues". But then, worse crimes have been committed in the quest for a catchy soundbite, I guess.
Therein lies the rub, then. EFA have fallen afoul of their privilege, like so many men before them (the EFA board is made up of all men and one woman. The executive is completely male. I'm not certain of racial background, and so won't make comment on that matter). They have played into gender and social stereotypes. But they're not the first. They certainly won't be the last.
EFA have made comment on how successful the campaign has been. It's gotten people talking, it has (by their own account) gotten the word out to people (Just Mums? Or others as well?) who didn't otherwise know about it. It generated some controversy and got people blogging about it, talking about it, discussing it. Those who liked it shared it around because it was funny (to them). Those who didn't, shared it around to show people how outraged they were.
Privilege is a queer beast. If you have it, you can't see it, and are almost completely unable to understand it. If you don't have it, it stares you in the face everywhere you turn. We all have privilege in one form or another. I'm female, but I have privilege in terms of being white, wealthy (in world terms, anyway), employed, educated, and in my 20's (for a little while longer, anyway). This makes it hard for me to see some things to which my privilege blinds me, but makes me very aware of those places where I'm under-privileged. EFA and their ad company FNUKY really just acted within stereotypes and privileges that they probably don't even recognise they have. They have created an ad that they - within their privilege - saw as amusing and fresh. They imagined that using a comedian and a few gags about Mums and gossip and how they care about their families but know nothing about technology would hold the public's interest, get the message across, and hopefully go viral. And, to their credit, the grand majority of the population (recalling that even though 51% of the world's population possess a vagina does not automatically make 51% of the population feminists) agreed with them. That makes for one successful marketing campaign.
Advertising uses all sorts of social, sexual, and racial stereotypes to get the message across. The very fact that marketing uses 'target groups' (read: "stereotypes") to create campaigns shows this. Take a look at Sociological Images one day to get a glimpse into how advertising campaigns are created and digested by the consuming public. You'll never look at a billboard the same way again. And while past practise does not make this particular wrong right, it does make it difficult to get very worked up over it, from my perspective anyway. The ad agency were doing what ad agencies do: create ads that appeal to a mass market. EFA were not evil by signing off on it, they were just blinded by privilege and unable to see how the campaign would play off amongst a minority of that market. The offense in this case, then, is not within EFA alone, but in the entire marketing and advertising machine, and in society that continues to mindlessly consume what that machine serves up to them.
For all intents and purposes, EFA would be best to make a proper apology (not a fauxpology like the one they have already given), and promise to do better next time. (For more information on what constitutes 'good' and 'bad' apologies, check out the Geek Feminism Wiki article on the subject). They won't, though, for a number of reasons. First, because they are still sitting in their little bubble of privilege and don't understand the issues the feminist left have taken with the campaign. Secondly, because the old marketing adage still holds true, especially on the internet: "All publicity is good publicity".
There's more to social media than Facebook
I quit Facebook on the weekend. For real. For good. And you know what?
Nothing happened.
Well, Facebook gave me a guilt-trip, but other than that, nothing happened.
No one called me in a panic, asking where I was, and what I was doing.
I didn't get an email pleading for me to come back to Facebook, and help them find red gems, or a lost cow, or a home for some virtual furry pet.
I didn't have a notice breathlessly exclaiming that someone had tagged me in a photo, or in a post.
No one sent me a message about all my friends who were having birthdays this week, or who had just 'changed their relationship status', or who were feeling lonely and unloved and needed me to 'reconnect with them'.
Instead, I went outside for a while. I read a book. And then I came back inside and updated my Twitter account instead.
You see, there's a lot of self-proclaimed "Social MediaDouchebags Experts" out there, and they're all in a lather about Facebook, and telling you how to set up a fan page, and put a 'like' button on your blog and all that. Most of them know Twitter exists as well, but many of them downplay it. It's not the latest big thing right now.
Unfortunately for the so-called "experts", they've found themselves behind the eight-ball again. What is the next big thing is quitting Facebook. All the cool kids are doing it, as the rash of stories from Crikey (and Gizmodo), Wired, Boing Boing, TechCrunch, Read Write Web, and the the EFF would indicate. And they're just the ones I've come across myself.
Mark Zuckerberg, once the poster child of the Social Media Billionaire's club (the generation that came after the dotcom kids), is learning something that every Web 2.0 entrepreneur must learn. When you give something to the public that they want, they'll embrace it. But start taking too much from them, and they'll drop you faster than you can say "Where's the delete button?".
What this all means is that there's a huge amount of commentary around now, ranging from "what does a perfect social network look like?" to "I want to quit Facebook, but I don't know what to do with myself now". Well, there's some simple answers. First of all, a better Facebook will come along (and the smart money is on these guys if you ask me. You heard it here first). Secondly, you don't need to wait for the next Big New Shiny Thing to take off. Go sign up at any of the squillion or more other social media sites, and work out what else is out there. There's more to social media than Facebook. Get out of your comfort zone, and explore.
Nothing happened.
Well, Facebook gave me a guilt-trip, but other than that, nothing happened.
No one called me in a panic, asking where I was, and what I was doing.
I didn't get an email pleading for me to come back to Facebook, and help them find red gems, or a lost cow, or a home for some virtual furry pet.
I didn't have a notice breathlessly exclaiming that someone had tagged me in a photo, or in a post.
No one sent me a message about all my friends who were having birthdays this week, or who had just 'changed their relationship status', or who were feeling lonely and unloved and needed me to 'reconnect with them'.
Instead, I went outside for a while. I read a book. And then I came back inside and updated my Twitter account instead.
You see, there's a lot of self-proclaimed "Social Media
Unfortunately for the so-called "experts", they've found themselves behind the eight-ball again. What is the next big thing is quitting Facebook. All the cool kids are doing it, as the rash of stories from Crikey (and Gizmodo), Wired, Boing Boing, TechCrunch, Read Write Web, and the the EFF would indicate. And they're just the ones I've come across myself.
Mark Zuckerberg, once the poster child of the Social Media Billionaire's club (the generation that came after the dotcom kids), is learning something that every Web 2.0 entrepreneur must learn. When you give something to the public that they want, they'll embrace it. But start taking too much from them, and they'll drop you faster than you can say "Where's the delete button?".
What this all means is that there's a huge amount of commentary around now, ranging from "what does a perfect social network look like?" to "I want to quit Facebook, but I don't know what to do with myself now". Well, there's some simple answers. First of all, a better Facebook will come along (and the smart money is on these guys if you ask me. You heard it here first). Secondly, you don't need to wait for the next Big New Shiny Thing to take off. Go sign up at any of the squillion or more other social media sites, and work out what else is out there. There's more to social media than Facebook. Get out of your comfort zone, and explore.
Lest We Forget ... But who have we already forgotten?
As ANZAC day approaches, and my bugling duties are again requested, I thought it would be apt to draw attention to the post I wrote on the topic this time last year. The last paragraph mentions this:
When you stand up and say "Lest we forget" this ANZAC day, please think of those who history has already forgotten. There were around 500 Australian Aboriginals and Torres Straight Islanders who served in World War I, and around 5,000 serving in World War II. Aboriginal and Islander men and women have served in every major conflict that Australia has ever been involved in. Many of them never came home.
Those who did return were refused pensions, land grants, and other benefits offered to white servicemen, and were barred from entry into the Returned Serviceman's League (RSL). They were denied the recognition, honour, and respect that their mates in the trenches received. And now, over sixty years since the end of World War II, we are still refusing to give them that honour.
This ANZAC day, spend two minutes in silence for those who history have forgotten, Lest We Forget also. If you are in Canberra, please consider attending the the Aboriginal and Torres Strait Islander commemorative ceremony after the dawn service at the War Memorial.
The information for this post was drawn mostly from The Anzac Day legend & Coloured Digger Anzac march
The image is part of the The Coloured Digger set, uploaded to flickr by Findo and is shared under a Creative Commons Licence.
Information about the various services (including the Aboriginal and Torres Straight Islander commemorative ceremony) can be found on the Australian War Memorial website.
The AWM website does not include directions to the Aboriginal Memorial Plaque. Directions can be found here, or on the The Anzac Day legend & Coloured Digger Anzac march.
I won't make comment on how far removed the plaque is from the memorial itself. I'll allow these links to speak to that.
This ANZAC day I'd like to remind you all to think about not just the white Australians (and all the members of other nationalities) that have died during war, but to remember the original owners of this land who died in other, non-glorified, and unremembered battles.
When you stand up and say "Lest we forget" this ANZAC day, please think of those who history has already forgotten. There were around 500 Australian Aboriginals and Torres Straight Islanders who served in World War I, and around 5,000 serving in World War II. Aboriginal and Islander men and women have served in every major conflict that Australia has ever been involved in. Many of them never came home.
Those who did return were refused pensions, land grants, and other benefits offered to white servicemen, and were barred from entry into the Returned Serviceman's League (RSL). They were denied the recognition, honour, and respect that their mates in the trenches received. And now, over sixty years since the end of World War II, we are still refusing to give them that honour.
This ANZAC day, spend two minutes in silence for those who history have forgotten, Lest We Forget also. If you are in Canberra, please consider attending the the Aboriginal and Torres Strait Islander commemorative ceremony after the dawn service at the War Memorial.
-=oOo=-
The information for this post was drawn mostly from The Anzac Day legend & Coloured Digger Anzac march
The image is part of the The Coloured Digger set, uploaded to flickr by Findo and is shared under a Creative Commons Licence.
Information about the various services (including the Aboriginal and Torres Straight Islander commemorative ceremony) can be found on the Australian War Memorial website.
The AWM website does not include directions to the Aboriginal Memorial Plaque. Directions can be found here, or on the The Anzac Day legend & Coloured Digger Anzac march.
I won't make comment on how far removed the plaque is from the memorial itself. I'll allow these links to speak to that.
-=oOo=-
Lest We Forget.
FOSS Training
I was privileged enough to be able to attend linux.conf.au in Wellington in January. While there, I caught Bob Edwards' and Andrew Tridgell's talk on "Teaching FOSS at Universities" (video of which can be found here). It intrigued me.
Open source software development is very different to developing software in a more traditional, closed source environment. The aim of the course is to teach students how to go about working within the open source community. It covers the practical aspects of checking out code from a repository, submitting patches, and undergoing code approvals and reviews. It also looks at some of the less tangible aspects, like what's accepted and expected within the community, the motivation behind project development, and governance. The course also goes into some detail about documentation.
Documentation for open source projects is not quite the known quantity that it can be in many proprietary software environments. I once had a developer I was working with describe it as "we live in the Wild West out here", and - at least to an extent - he makes a good point. While writing for an open source project may not be as wild and exciting as that sentence makes it sound, it can sometimes be unpredictable and, at times, incredibly frustrating. Frequently, a book has been written and reviewed in preparation for a release, only to find at the last minute that a feature has been pulled from the version, a component has suddenly been renamed, or the graphical interface has had some kind of redesign. All of these things happen to open source writers on a regular basis, and frequently the only solution is to pull an all-nighter, get the changes in, and have the document released on schedule. And that's only if you were lucky enough to find out about the change with enough time to spare before release!
So how does a writer plan for and write a documentation suite when there's so much unknown in a project? The answer is - perhaps ironically - to plan ahead. You can't plan for every contingency, nor should you. But if you have a plan of any description, you're going to be better off when things start to go wrong. Pin down the details as best you can as far ahead as possible. But don't leave it there, continue to review and adapt your plan. Keep your ear to the ground, and constantly tweak your schedule and your book to suit. If something comes up in a mailing list about a feature you've never heard of, don't be afraid to ask the question - "Does this need to be documented? Will it be in the next version? Where can I get more source information?". Another trick is to make sure you build in 'wiggle room' to your schedule, in case you suddenly discover a new chapter that needs adding, or a whole section that needs to be changed. If you're consistently a few days or a week ahead of schedule, then even a substantial change should not throw you too far off balance.
Just like a ballet dancer, technical writers need to be disciplined, structured, and organised. But you also need to have grace, poise, tact, and - most importantly - flexibility.
Thanks to Bob and Tridge, I'll be lecturing the 2010 FOSS course students at the Australian National University later this week. I'll also be contributing the textbook that is being developed for the course. True to form, it is being built by and for the open source community, using open source tools (including Publican which has been developed in-house by some of my esteemed colleagues). Watch this space for more information.
Open source software development is very different to developing software in a more traditional, closed source environment. The aim of the course is to teach students how to go about working within the open source community. It covers the practical aspects of checking out code from a repository, submitting patches, and undergoing code approvals and reviews. It also looks at some of the less tangible aspects, like what's accepted and expected within the community, the motivation behind project development, and governance. The course also goes into some detail about documentation.
So how does a writer plan for and write a documentation suite when there's so much unknown in a project? The answer is - perhaps ironically - to plan ahead. You can't plan for every contingency, nor should you. But if you have a plan of any description, you're going to be better off when things start to go wrong. Pin down the details as best you can as far ahead as possible. But don't leave it there, continue to review and adapt your plan. Keep your ear to the ground, and constantly tweak your schedule and your book to suit. If something comes up in a mailing list about a feature you've never heard of, don't be afraid to ask the question - "Does this need to be documented? Will it be in the next version? Where can I get more source information?". Another trick is to make sure you build in 'wiggle room' to your schedule, in case you suddenly discover a new chapter that needs adding, or a whole section that needs to be changed. If you're consistently a few days or a week ahead of schedule, then even a substantial change should not throw you too far off balance.
Just like a ballet dancer, technical writers need to be disciplined, structured, and organised. But you also need to have grace, poise, tact, and - most importantly - flexibility.
Thanks to Bob and Tridge, I'll be lecturing the 2010 FOSS course students at the Australian National University later this week. I'll also be contributing the textbook that is being developed for the course. True to form, it is being built by and for the open source community, using open source tools (including Publican which has been developed in-house by some of my esteemed colleagues). Watch this space for more information.
Cross-posted to FOSS Docs
Ada Lovelace Day 2010: Unicorns
Often, when a woman joins an all-male technical environment, they will look at her strangely. They might try and pretend that she's a bloke, that she's just 'one of the boys'. They might ignore her. They might make a few distasteful jokes and then get on with the job. But mostly, what happens is that a woman is noticed. She'll be whispered about, she'll feel eyes watching her, she will notice her work being held to scrutiny. There might be a few gentle put-downs, all in the name of 'humour' ("can't you take a joke?"), and there might be some bolder individuals who will make life uncomfortable. But, generally, the overwhelming sense is that of being different.
Imagine, if you will, that you were at work, and suddenly, a unicorn walked in. How would you react? Now imagine the unicorn is that woman.
This situation has given rise to what is now known as the Unicorn Law. It was created by Emma Jane Hogbin. Emma Jane is a Canadian technical writer, and one day I will write an Ada Lovelace Day post about her. Not this year, though (sorry Emma Jane!).
This year, I want to nominate my fellow LinuxChix unicorns in Australia and New Zealand:
Aeriana
Brianna Laugher
Claudine Chionh
Donna Benjamin
Jacinta Richardson
Joh Clarke
Mary Gardiner
Melissa Draper
Pia Waugh
Sara Falamaki
Every one of these women know what it's like to walk into a room and be stared at as though you were a complete novelty. Every one of these women now what it's like to be held to a higher standard than your male counterparts for the same recognition and acceptance. Every single one of these women have been asked "are you here with your boyfriend?" (and worse!). Every single one of these women amaze me, inspire me, and support me, every single day.
Ada Lovelace day is about remembering where we've come from, but it's also to remind us about where we're going. The women of the Australia and New Zealand LinuxChix chapters remind me every single day why I get up and continue fighting. Thank you.
(The Unicorn/RoboTux image used above was created by Lisa at pixellab and is shared under a Creative Commons licence)
Imagine, if you will, that you were at work, and suddenly, a unicorn walked in. How would you react? Now imagine the unicorn is that woman.
This situation has given rise to what is now known as the Unicorn Law. It was created by Emma Jane Hogbin. Emma Jane is a Canadian technical writer, and one day I will write an Ada Lovelace Day post about her. Not this year, though (sorry Emma Jane!).
Aeriana
Brianna Laugher
Claudine Chionh
Donna Benjamin
Jacinta Richardson
Joh Clarke
Mary Gardiner
Melissa Draper
Pia Waugh
Sara Falamaki
Every one of these women know what it's like to walk into a room and be stared at as though you were a complete novelty. Every one of these women now what it's like to be held to a higher standard than your male counterparts for the same recognition and acceptance. Every single one of these women have been asked "are you here with your boyfriend?" (and worse!). Every single one of these women amaze me, inspire me, and support me, every single day.
Ada Lovelace day is about remembering where we've come from, but it's also to remind us about where we're going. The women of the Australia and New Zealand LinuxChix chapters remind me every single day why I get up and continue fighting. Thank you.
(The Unicorn/RoboTux image used above was created by Lisa at pixellab and is shared under a Creative Commons licence)
Barbie's Next Career: Blogger Barbie?
The geek feminist establishment has spent so much time hating Barbie, that now it's a little hard to know what to think about the new Computer Engineer Barbie. I predict it's going to be yet another polarising factor, actually. There'll be those who think that Barbie is just mocking what we have tried so hard to achieve. And then there'll be those who'll think that this might actually help prove to little girls that a computing career is a possibility. The comments to this BBC article would indicate so, anyway.
When I was in high school in rural Queensland, there was the obligatory "what do you want to do when you leave school" conversations that had to be had in the run-up to matriculation. For whatever reason - and I don't really know whether to blame the school faculty, the rural sensibilities, or my own strange teenaged assumptions - I came to the conclusion that careers fell into one of two categories. You either did an apprenticeship, or you went to uni. The only apprenticeships I was aware of as being available for girls (all the boys were going to be fitters and turners, and I didn't even know what a fitter and turner was, let alone want to be one) were hairdressing apprenticeships. I didn't want to be a hairdresser. So I decided I'd better go to uni. How I chose my degree is another whole story, that might be best suited for another blog post, but suffice it to say that it took me six years and a lot of money (thanks HECS!) to finally graduate with something that I was proud to have, and that has eventually gotten me into a career I'm particularly fond of.
I spent most of high school flitting between the library for lunch-time sessions of Advanced Dungeons & Dragons, and the computer lab for marathon BASIC programming competitions with my friends. Christmas holidays were spent at my parent's old IBM compatible trying not be eaten by a grue. Yet the concept of studying computing was completely foreign to me. I loved making things do stuff, I loved destructing things to find out how they worked, I loved creating stories, and then having 2d10 decide the next plot twist for me. If something went wrong I wanted to know why it went wrong. Quite a lot of the time I broke things just so I could try to fix them (and that hasn't really changed much, I pulled apart my Roomba the other day). It wasn't until I got to uni and made friends in the computing lab there (you know who you are!) that I discovered that IT degrees even existed, I think.

I remember desperately wanting (and eventually getting) a Peaches 'n' Cream Barbie for my birthday one year when I was little. Perhaps if I'd been given computer engineer Barbie instead, my story would be different? I'm not sure, but it's my daughter's birthday soon, and I guess it can't hurt ...
------
News just in: you can pre-order Computer Engineer Barbie on the Mattel site, for delivery in December. Just in time for Christmas!
------
Update: ... but only if you live in the US. Bugger.
When I was in high school in rural Queensland, there was the obligatory "what do you want to do when you leave school" conversations that had to be had in the run-up to matriculation. For whatever reason - and I don't really know whether to blame the school faculty, the rural sensibilities, or my own strange teenaged assumptions - I came to the conclusion that careers fell into one of two categories. You either did an apprenticeship, or you went to uni. The only apprenticeships I was aware of as being available for girls (all the boys were going to be fitters and turners, and I didn't even know what a fitter and turner was, let alone want to be one) were hairdressing apprenticeships. I didn't want to be a hairdresser. So I decided I'd better go to uni. How I chose my degree is another whole story, that might be best suited for another blog post, but suffice it to say that it took me six years and a lot of money (thanks HECS!) to finally graduate with something that I was proud to have, and that has eventually gotten me into a career I'm particularly fond of.
I may not have gone where I intended to go, but I think I have ended up where I needed to be.
-- Douglas Adams "The Long Dark Tea-Time of the Soul"

I remember desperately wanting (and eventually getting) a Peaches 'n' Cream Barbie for my birthday one year when I was little. Perhaps if I'd been given computer engineer Barbie instead, my story would be different? I'm not sure, but it's my daughter's birthday soon, and I guess it can't hurt ...
------
News just in: you can pre-order Computer Engineer Barbie on the Mattel site, for delivery in December. Just in time for Christmas!
------
Update: ... but only if you live in the US. Bugger.
LinuxCon - Boston - August 10-12 2010
I've just put in my application to speak at LinuxCon in Boston in August. Their speaker lineup is pretty impressive, so it would be an incredible honour to be selected.
For posterity, here is the abstract I've submitted:
This talk is a look into why documentation is so important to open source projects. It explains how to create documentation that will empower your users, guide them through the often daunting learning curve of using new software, and in the process make your project look fantastic. Beautiful technical documentation might sound like an unrealistic fairy tale, but it can make the difference between a successful project, and a wildly successful one.
The talk is aimed at anyone who is involved in creating open source software, and who doesn't know how best to approach the documentation process. No specific technical expertise is required.
And the bio:
Lana Brindley writes technical documentation for Red Hat. She works from her home near Canberra, Australia and is currently getting her hands dirty on middleware documentation. She is hopelessly loquacious, and enjoys writing presentations and speaking in her spare time for fun. She's also been known to wear a red fedora in public.
Lana has been writing technical documentation for open source projects for nearly three years. She has been speaking about Linux generally and technical writing specifically for the same period of time, although her fascination with these topics dates back over a decade. Most recently, she spoke at linux.conf.au in Wellington, New Zealand, the Canberra Linux Users Group, Girl Geek Dinners Sydney and Canberra, and a clutch of computer user groups.
~oOo~
Update: I did actually get accepted to speak. Unfortunately, work have declined to fund me to get over there. Never mind. Next year!
Subscribe to:
Posts (Atom)



