Remembering Telsa Gwynne

Telsa Gwynne, whom I knew through my time in the LinuxChix community between 2000 and around 2007, died this week:

Telsa is the direct inspiration for the entire 15 years of content on this website, especially the personal diary. Before joining LinuxChix, I first knew Telsa through her online diary (its archival title, “This was a diary, once”, is painful to read now), which I heard about through someone who read Alan Cox’s diary, and I was struck by how striking daily life could be in written form. Telsa’s diary was full of personality and snark, and singlehandedly inspired me to begin writing about my life online too.

I thought of her as a net celebrity, although not in the usual way of “married to Alan Cox”, but as “writer of one of my favourite websites”. I was therefore a little bit shy about directly interacting with her when I initially joined the LinuxChix lists in 2000, but I first met her in person in 2001 at linux.conf.au when she and Malcolm Tredinnick were hanging around debriefing and complaining about CVS, on which he was teaching a tutorial that year which Telsa later wrote up. She was grumpy and kind and normal, even if she did know CVS.

Andrew saw her again at LCA in 2003, but I didn’t go and I think I only met her one more time, in Wales in 2004 when we visited their house and due to poor planning with trains, ended up staying the night. Telsa and Alan were kind hosts and we enjoyed Telsa’s huge knowledge of local history as we walked all around Swansea.

Telsa’s final diary entry in 2006 says she “plain[ly] and simpl[y] los[t] interest in running to stand still just to understand how to use anything mechanical.” However hard she worked for it, I remember her as profoundly technically knowledgeable and an excellent teacher. A great deal of my initial learning about both CSS and character encodings came from her, and she was well known as a high level user of DocBook. A friend shared one of her posts to a private LinuxChix technical list today, walking through the differences between library packages and -devel packages in Linux distributions, and their implications for compiling software.

I hadn’t been in contact with Telsa since she or I variously withdrew from our common online communities, so since 2007 or before. I kept an eye on the very occasional updates to her website, and was pleased to think that she had found a more satisfying life outside her Free Software community volunteering. I still find this a happy thought.

Telsa was also a critical inspiration to me as an activist: in the early 2000s (and still) it was hugely controversial to either believe that open source communities could still work if they were more civil (the entire LinuxChix project was partly an experiment with that), and even more so to insist that they should be. Telsa is the earliest person I can think of who stood up in an open source development community and asked it to change its norms in the direction of civility. I don’t know how heavily her online harassment experiences played a part in her departing Free Software and some online communities — I hope it wasn’t a large part — but I’m sorry it happened and I’m angry.

Telsa was a brilliant and kind and strong person, and I am sorrier than I can say that we will never be in contact again. To Alan, Debbie and others who loved her: my profound sympathies for the loss of an amazing person.

Other memorials:

Telsa online:

Creative Commons License
Remembering Telsa Gwynne by Mary Gardiner is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

End of year question template: the year in threes

This entry is part 1 of 13 in the series Year in threes

The end of the Gregorian calendar year is an increasingly significant time for me, with both of my children born in January, as well as, sadly, having had three of my four grandparents die in the last months of different years. And as the children get older, the school year forces itself back on our notice to go with the long standing summer traditions of our household. (Which are, for reference, Christmas and the Boxing Day test. I’m trying to get the solstice to sneak in there.)

And so I’ve always enjoyed Julia’s end of year reflections (see 2014’s version) but I’ve never found the question set resonated, and increasingly less so as I get older. (Did anyone close to you give birth in 2014? Me, but I don’t think the question envisages that answer.)

So I thought I’d come up with my own set that I can do each year. They’re broad to the point of banality, but I want to leave room for answers. Here they are, by all means use them if they suit you too.

Three moments of YEAR.

Three meals of YEAR.

Three photos of YEAR.

Three pleasures of YEAR.

Three news stories from YEAR.

Three sensations from YEAR.

Three sadnesses of YEAR.

Three plans* for YEAR+1.

Three hopes for YEAR+1.

* Not resolutions, but plans. Things I don’t need to resolve to do because they’re already in progress.

As a side-note, my Internet archeology is not good enough to find the source of the questions that Julia uses. The earliest year I can find them being used is 2004 (here and here) and then not again until 2007, and then just a few people each year until in 2011 it either got a lot more popular or Google has indexed it better. Anyone got a source earlier than December 2004?

End of year question template: the year in threes by Mary Gardiner is marked CC0 1.0

Handling harassment incidents swiftly and safely

This article was written by me and originally published on the Ada Initiative’s website. It is republished here according to the terms of its Creative Commons licence.

As anti-harassment policies become more widespread at open technology and culture events, different ways of handling harassment incidents are emerging. We advocate a swift process in which final decisions are made by a small group of empowered decision makers, whose focus is on the safety of the people attending the event.

Open technology and culture communities, which often make decisions in a very public way, can be tempted to also have a very public and very legalistic harassment handling process, a judicial model, but we advocate against this. It prioritises other values, such as transparency and due process, over that of safety. Alternatively, because many members of such communities find ostracism very hurtful and frightening, sometimes they develop a caretaker model, where they give harassers lots of second chances and lots of social coaching, and focus on the potential for a harasser to redeem themselves and re-join the community.

But neither of these models prioritise safety from harassment.

Consider an alternative model: harassment in the workplace. In a well-organised workplace that ensured your freedom from harassment — a situation which we know is also all too rare, but which we can aspire to, especially since our events are workplaces for many of us — an empowered decision maker such as your manager or an HR representative would make a decision based on your report that harassment had occurred and other relevant information as judged by them, and act as required order to keep your workplace safe for you.

A well-organised workplace would not appoint itself your harasser’s anti-harassment coach, have harassment reports heard by a jury of your peers, publish the details of your report widely, have an appeals process several levels deep, or offer fired staff members the opportunity to have their firing reviewed by management after some time has passed.

Like in a well-organised workplace, we advocate a management model of handling harassment complaints to make events safer: reasonably quick and final decisions made by a small group of empowered decision makers, together with communication not aimed at transparency for its own sake, but at giving people the information they need to keep themselves safe.

The management model of harassment handling is that:

  1. you have a public harassment policy that clearly states that harassment is unacceptable, and gives examples of unacceptable behaviour
  2. you have a clear reporting avenue publicised with the policy
  3. you have an empowered decision maker, or a small group of decision makers, who will act on reports
  4. reports of harassment are conveyed to those decision makers when reported
  5. they consider those reports, gather any additional information they need to make a decision — which could include conduct in other venues and other information that a very legalistic model might not allow — and they decide what action would make the event safer
  6. they communicate with people who need to know the outcome (eg, with the harasser if they need to change their behaviour, avoid any people or places, or leave the event; volunteers or security if they need to enforce any boundaries)
  7. they provide enough information to the victim of the harassment, and when needed to other attendees, to let them make well-informed decisions about their own safety

Further reading

Creative Commons License
Handling harassment incidents swiftly and safely
by the Ada Initiative is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Based on a work at https://adainitiative.org/2014/07/23/handling-harassment-incidents-swiftly-and-safely/.

The Ada Initiative founders on funding activism for women in open source

This article was co-written by me and Valerie Aurora. It was originally published in Model View Culture and was later published on the Ada Initiative blog. It is republished here according to the terms of its Creative Commons licence.

In December 2010, Valerie Aurora, then a leading Linux filesystems developer, announced that she was leaving software development to work on women in open source software activism full time. Behind the scenes, she asked several other geek feminist activists to join her to work on women in open source activism full time. “I don’t know what the world-wide economic capacity for paid activists [for women in open source] is, but let’s find out together!” she wrote.

In 2010, the smart money said that the world-wide economic capacity for paid activists for women in open source was well under one person. And only Mary Gardiner, then an unpaid computer science PhD student looking to leave academia, took Valerie up on the offer.

Thus began our long journey towards answering the question: “How does an activist get paid?

This article chronicles our own painful and sometimes expensive learning experiences around funding diversity in tech work, as well as advice and techniques from several other successful full-time diversity in tech activists and fundraising experts: Ashe Dryden, diversity advocate and consultant; Kellie Brownell, CiviCRM implementer at Giant Rabbit and former Ada Initiative fundraising consultant; Frances Hocutt, founding president of the Seattle Attic feminist hackerspace; and Emily May, executive director of Hollaback!.

Paying Activists and Funding Complications

The question we struggled with initially was why activism, and feminist activism in open source software in particular, should be a paid job at all. Thanks to the work of people including Kate Losse, today the tech community is increasingly aware that this kind of community-building labor is valuable and should be compensated. But in 2010, all we knew is that volunteer activism was not working. Women in open source software were working for free, burning themselves out while fighting for rights as simple as basic physical safety – let alone equal pay, equal treatment and a non-sexist culture.

And yet the expectation that women in open source should be unpaid activists was so high that in 2009, Emma Jane Westby formulated the “Unicorn Law,” which states: “If you are a woman in Open Source, you will eventually give a talk about being a woman in Open Source.” In October 2011, Skud — herself an activist and target of harassment — adapted Arlie Hochschild’s term “the second shift” to describe this phenomenon. But after ten years, and tens of thousands of hours of difficult, draining work, the percentage of women in open source software was still in the low single digits.

Valerie’s insight — radical, at the time — was that we needed full-time paid activists working on the problem in order to make any progress. We founded the Ada Initiative with the principle of paying fair market wages to anyone doing work for us more than a few hours a week. In 2010, this was a moonshot. In 2014, it’s increasingly how things are done. More and more diversity in technology initiatives are becoming paid activities, and a growing proportion of the technology industry recognizes this labour as something worth paying for.

For all this progress, relatively few “pre-fabricated” diversity in tech jobs exist, and the ones that do exist tend to be co-opted by corporations to narrowly focus on recruiting and, in effect, marketing. Many existing large diversity-in-tech non-profits are primarily corporate-funded and therefore end up compelled to do recruiting and marketing for for-profit tech corporations. An employee of a for-profit corporation who wants to advocate for significant cultural change as part of their job is stuck in an additional catch-22: they can’t criticize their competitors, because it looks like a conflict of interest, and they also can’t criticize their own employer, because that’s a great way to get fired.

Thus, full-time diversity activists who want to do effective, controversial, culture-changing work must often work out how to pay themselves, rather than taking existing jobs at tech companies or diversity in tech non-profits.

What follows is a survey of some of the most popular funding sources: corporate sponsorship, individual donations, and consulting and training.

But first…

Why you shouldn’t try them all

Often activists will reach for every funding opportunity they can: individual fundraising campaign, yes! Government grants, yes! Selling stickers, yes! Sucking up to wealthy potential donors at lavish one-on-one dinners, absolutely! But it is crucial to pick just two or three funding sources and concentrate on them.

Raising money in any form takes time, practice, dedication, and skill. Pursuing too many forms of funding will just mean that you’re bad at all of them. Some diversification of funding sources is often recommended, but the base requirement is a reliable funding source.

An activist’s choice will depend both on their mission and who they are able to reach. The Wikimedia Foundation is focusing exclusively on small donors from all over the world giving an average of $25 each and giving up pursuing most grants or large donors, in part because small donors are inherently diversified. However, the Wikimedia Foundation can use Wikipedia, one of the world’s most-read websites, as a fundraising platform, a rare advantage. No diversity in tech activists will have such a large pool of potential donors! Each individual and organization needs to assess which sources of funding are compatible with their mission, and of those sources, which they can access.

Corporate Sponsorship

The Ada Initiative, like many diversity in tech groups, initially planned on getting most of our funding from technology-related corporations. Our focus was on women in open technology and culture, which includes open source software, Wikipedia-related projects, open data, and similar areas. Our logic was charmingly naïve: since corporations reaped most of the benefit of open tech/culture, they should pay most of the cost of increasing the percentage of women in their talent pool because fairness. Also, corporations tend to have a lot of money.

Major corporate sponsorship for diversity in tech work comes in several common forms: conference sponsorships, grants for specific projects, fellowships employing a specific person for a few months, and completely unrestricted grants (our favorite). Corporate donors are attractive because, compared to the typical activist, many have effectively infinite amounts of money.

However, corporate sponsorship has clear downsides for many diversity in tech activists. The sponsor’s goal tends to be making sure the corporate sponsor has access to a diverse hiring pool. Most companies therefore prefer to support events and education initiatives that serve as recruitment opportunities in the short or medium term.

Corporate sponsorship is also often very cautious. They are looking to associate their name with a popular message, and groups who do not yet have a history of successful programs may have trouble accessing corporate donations. Organizations intending to rely on corporate donations may have to bootstrap with other funds or volunteer labor while building a history of success.

The main exception to these rules, in our experience, is smaller privately-held companies whose owners account only to themselves for how the company’s money is spent. They tend to be less conservative and more risk-tolerant than publicly owned companies. In the Ada Initiative’s case, these kinds of corporate donors were crucial to our success and included Puppet Labs, Dreamhost, Dreamwidth, and Inktank.

Early on, our philosophy at Ada Initiative was to accept any no-strings-attached corporate sponsorship as long as the company’s business model wasn’t fundamentally anathema to our mission. But since many corporations — and corporate management — are complicit in discrimination and harassment of women in tech, much of the effective work to support women in tech involves criticizing the status quo and has the potential to offend the very corporations who sponsor us. We gradually came to realize that every corporate sponsorship has an invisible condition: unspoken internalized pressure to avoid any actions that might cause that corporation to stop donating to us.

We had another motivation for our initial corporate-funded model: guilt. We felt guilty asking individual people to support our work but no such compunction when it came to corporations. We suspect this kind of guilt plagues many activists; we tend to want to help others, not ask others to help us. Our guilt about asking individuals to support our work instead of corporations drove us to end our first fundraiser early, resulting in the loss of tens of thousands of dollars from eager donors and forcing us to start another, less-efficient fundraising campaign only 5 months later. Reframing how we viewed asking individual people for donations took three years, a career counselor, a therapist, several books, and a perceptive fundraising consultant, Kellie Brownell.

So let’s talk about…

Individual Donations

Since mid-2011, the bedrock of the Ada Initiative’s funding has come from a few hundred individuals within the technology community. Being accountable to donors who are primarily interested in culture change even when it has no direct benefit to themselves allows us to take on more radical programs. This includes work that is not directly connected with hiring or careers, or that is connected with gift and alternative economies like media fandom with little direct connection to corporate profits.

Perhaps the most compelling reason to adopt an individual donor funding model is that donors often become advocates for diversity in tech themselves. Kellie Brownell, our former fundraising consultant, says, “While fundraising at the Electronic Frontier Foundation, I kept noticing that our donors were the first to take action when we asked for help.” Many an Ada Initiative donor has gone on to successfully advocate for an anti-harassment policy or a diversity scholarship in their community. We also receive many thank-you notes from people too shy, too burned out, or too busy to be advocates themselves, who are relieved that they can take action in some way by donating. Individual donors create a virtuous circle where fundraising supports our mission, and our mission increases our fundraising.

Diversity in tech organizations are increasingly bootstrapped with a crowdfunding campaign. Diversity advocate and consultant Ashe Dryden raised $20,000 in July 2013; Trans*H4CK raised $6,000 beginning in May 2013; feminist hackerspaces Double Union and Seattle Attic raised $15,000 and $11,000 respectively in November 2013; and in March 2014 Lesbians Who Tech raised $29,000 for a summit in San Francisco and $20,000 for a summit in New York.

Crowdfunding, with its constant outreach and rewards is an excellent way to interest donors and community members in an organization, but Dryden cautions that “[it was and] still is a considerably larger amount of work on top of the other work I’m doing.” At the extreme, the work required to publicise a fundraising drive and then fulfill rewards can risk exhausting the funds raised! It may also only work a limited number of times. Emily May, executive director of anti-street harassment non-profit Hollaback!, says “80% of our donors are young[…] They are incentivized to give by new exciting initiatives, but there are only so many ‘new exciting initiatives’ that [we] can launch without overwhelming our capacity.”

Activists are beginning to be able to raise enough money to pay themselves from many very small regular donations. Dryden’s funding now comes primarily from Gittip, a service that allows people to make anonymous weekly donations directly to her. She is the top Gittip recipient with an income of $750 a week, and is not the only diversity in tech activist among Gittip’s top receivers. Others include Lynn Cyrin, a trans woman of color working on a guide to class mobility and CallbackWomen, working to increase women’s representation at conferences.

Dryden says, “Community funding is great because it means I’m working directly for the community. I often tell people that the community is my employer, so I’m working directly for them, instead of what would look best for a company. It also means that I can be impartial in critiquing what’s wrong with the industry without worrying about financial ramifications either through my employer’s view not aligning with mine or people attempting to get me fired for my views, which many other activists and advocates have experienced.” Dryden’s model is beginning to approach what Sue Gardner, the outgoing executive director of the Wikimedia Foundation and an Ada Initiative board member, identifies as the future of non-profit funding: small donations from a large number of donors, requiring relatively little fundraising effort from the organisation compared to traditional models.

Every individual donor population is unique. In Dryden’s case, anonymous donors make small weekly donations on the order of $5. In the Ada Initiative’s case, we tend to have donors with high-paying technology jobs (or who own technology companies themselves) with generous bonuses, stock grants, and programs that match employee donations to non-profits. Kellie Brownell explains how we grew our individual donor base: “We adapted fundraising practices from individual major giving, for example, (1) thanking donors quickly, (2) asking what motivated them to give, and (3) reporting back later what we did with their money. Major giving practices are highly personal and aim to help donors grow in their understanding of an organization’s mission and why this mission matters to them. Once a fundraising team becomes good at doing both these things, you can develop this model further by giving donors opportunities to participate in the process.”

Relying on individual donors has downsides. Recruiting the initial slate of donors can take months of full-time work, and reminding them to give again takes more work (which is one reason why non-profits tend to prefer automatic recurring donations). Individual donors may also attempt to redirect the person or organization’s work towards less controversial programs. Dryden explains that the anonymity of her donors, which is not an option for most non-profit corporations, “removes the pressure to fit my message into what I think my larger funders would agree with, which protects the integrity of my work.”

Membership

A variant of individual donations is the membership model of funding, where funders pay membership fees instead of donating, and in return receive benefits from the organization such as access to private events, training or spaces. It often comes with input into the activist group’s governance, usually as the right to vote for or stand for the governing committee.

This model is most successful where activists are primarily working to provide ongoing benefits to a small group of people; for example, feminist hackerspaces (a.k.a., community workshops), which exist for the benefit of local women and others who are not welcomed in existing hackerspaces. Frances Hocutt, founding president of the Seattle Attic feminist hackerspace, says “We aim for members to fund the bulk of our operations because we want our community to be able to continue even if donations drop off. We are trying to build a community that is sustainable and can be self-supporting if need be.”

For organizations like the Ada Initiative, which aims to benefit a very large group of people and provide resources widely and freely, the membership model is less suitable as we have little additional benefit to offer members. Hocutt also observes that it is not ideal when activists are trying to benefit people who can’t afford membership fees: “We believe that ability to pay dues has nothing to do with a person’s ability to contribute to the creativity and energy of the Attic community, and we want to remove barriers that keep some of us from doing that.” Seattle Attic offers the ability for donors to donate memberships for people who can’t afford one, and a transport subsidy to members who don’t have access to transport.

Consulting and training

Counterintuitively, one way to raise money from donors without giving them undue influence is to provide consulting and training directly to them for a fee. This makes the terms of the relationship very clear; they receive a specific tangible benefit in return for their fee, rather than there being an unspoken expectation of a long term PR or recruiting boost.

In addition to her Gittip income, Ashe Dryden funds her work by consulting for corporations looking for help improving diversity in their organization. The Ada Initiative’s training programs include the Allies Workshop, which teaches men simple, everyday techniques to fight sexism in their workplace and open tech/culture communities. The Allies Workshop is a fairly challenging and confrontational program, as it teaches people to directly confront sexism and harassment without being transphobic, homophobic, racist, ablist, or classist. By offering it as a corporate training program on a voluntary attendance basis only, we attracted companies with employees who were ready to take personal action to support our existing strategy.

As with the membership model, providing consulting or training in return for a fee may compromise the ability of an organization to benefit the public.

“I would love a stronger earned income revenue stream, but our values of making it free to launch a Hollaback! in [any] community conflict with that,” reports Emily May, whose organization’s funding is primarily foundations (65%) and government (20%). In order to combat this effect, the Ada Initiative makes our training materials available publicly, and offers cheap and free spots at public training sessions, as well as offering training using the same materials to fee-paying clients.

Incorporation and funding

The Ada Initiative is incorporated as a 501(c)3 not-for-profit in the United States with tax-exempt status. This has some immense practical benefits in exempting us from corporate income taxes and allowing us to receive tax-deductible donations in the US.

Incorporating in some form — non-profit, B-corp, limited liability company, etc. — is not a requirement for funding diversity in tech work. We were astonished to discover how much money people would give us with the ink barely dry on our mail-order certificate of incorporation from the State of Delaware. In retrospect, we realized people were initially donating to Mary Gardiner and Valerie Aurora, not the Ada Initiative, Inc. In the tech sector, people are frequently willing to give hundreds or thousands of dollars to individuals as long as they personally trust the recipient, with or without the incentive of tax deductions or certification by some charity-related authority (e.g., the U.S. Internal Revenue Service).

The decision of whether or not to create a 501(c)3 requires weighing significant trade-offs. Preparing our application for tax-exempt status and then following various accounting and reporting rules to retain it take an astonishingly high proportion of our time — our 2012 taxation filing consumed approximately a month of staff time. In the U.S., non-profit incorporation is most suited to an organization that, like the Ada Initiative, intends to grow into a larger multi-person effort. We deliberately created an organization that would allow our projects to be continued by other activists if and when we burned out and move on to easier jobs (like writing operating systems software or leading a computational research lab).

To The Moon!

In 2010, Valerie described paying one activist to work on issues facing women in open technology and culture as a “moonshot”. In the short time since, so many activists have found that the work they do or the resources they need both should be paid for and can be paid for. The Ada Initiative, Black Girls Code, Seattle Attic, Double Union, Trans*H4ck, Lesbians Who Tech and others have joined older organizations such as the Anita Borg Institute and the Level Playing Field Institute. More are appearing every month. They are joined by community-funded individual activists such as Ashe Dryden and Lynn Cyrin.

Diversity in tech activists are using a wide variety of strategies: corporate sponsorship, yearly fundraising campaigns, monthly or even weekly small donors, foundation grants, conference sponsorships, and many more. The technology and culture around giving are changing so quickly that funding strategies that were completely impractical three years ago can now fund a full-time activist or an entire non-profit with several paid employees. Conventional fundraising experts, raised on a diet of buying email lists and snail mail appeals, are hard-pressed to keep up with these massive changes. We recommend that diversity in tech activists learn fundraising techniques from each other in addition to learning established fundraising best practices. In many ways, diversity in tech activists are outstripping received fundraising wisdom.

We can’t imagine what diversity in tech activism will look like in another four years, but we’d love to see reliance on corporate donations fall back to simply being one of many options for activists to consider. We hope that people who have benefited from the technology industry continue to give back by supporting diversity in tech activism, by joining diversity activist communities and by donating to individuals and organizations working towards a diverse and equitable tech workforce.

[Disclosure: former Model View Culture editor Amelia Greenhall and Valerie Aurora, one of the authors of this article, both serve on the board of Double Union in a volunteer capacity.]

Creative Commons License
The Ada Initiative founders on funding activism for women in open source by the Ada Initiative is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
Based on a work at https://adainitiative.org/2014/06/10/the-ada-initiative-founders-on-funding-activism-for-women-in-open-source-from-model-view-culture/.

Remembering Malcolm Tredinnick

I flew home from the US yesterday and when I arrived in Sydney I got a message from my husband saying that Malcolm Tredinnick had died. According to this piece by Simon Dulhunty, he was found on Monday to died at home in Sydney, possibly after a seizure, while I was at PyCon 2013.

Malcolm Tredinnick speaking to an audience
Malcolm Tredinnick speaking at DjangoCon 2008 (by Sebastian Hilling CC BY-NC)

I’ve known Malcolm slightly since my first linux.conf.au in Sydney 2001. In late 2004 I interviewed for a job at CommSecure (since closed) where he was then working, having been a lead developer of and continuing to maintain and develop a real-time data delivery system for the Hong Kong stock exchange. (The eventual end of that contract was the reason CommSecure later closed.) He was also my boss for about half of 2005 until I left to begin my PhD in early 2006.

I still caught up with him at technical events, the last long conversation I remember with him was at PyCon AU 2011 where my husband Andrew and I had a very Malcolm conversation with Malcolm, which roved over the paperwork hassles of having no fixed address (Malcolm travelled a lot and went through periods where he housesat or lived in serviced apartments for a while), the Australasian chess community, and some gentle mutual trolling between him and Andrew over narrative testing.

What I will remember most about Malcolm is that he was a teacher at heart. I never personally had this relationship with him, but I knew several people at CommSecure and elsewhere who Malcolm had tutored or mentored in programming, often over a very long period of time. Elsewhere I know he had taught mathematics (long before I knew him, he very nearly completed a PhD in mathematics when his area suddenly became fashionable and about 50 years of work was done in 6 months by incoming mathematicians) and chess. I will also remember his dry and sadonic approach to nearly everything (for a very recent example, Malcolm gives useful parenting advice), combined with “really, how hard could it be?” used both straightforwardly and distinctly otherwise. Goodbye Malcolm.

Update, funeral plans: Ray Loyzaga who was Malcolm’s close friend, and long-time founder-CEO of CommSecure, has announced that Malcolm’s funeral will be at 2:30pm Thursday April 4, at Camellia Chapel, Macquarie Park Cemetary, North Ryde, Sydney.

Other memorials:

Malcolm online:

Creative Commons License
Remembering Malcolm Tredinnick by Mary Gardiner is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License.

How to do more writing, by someone who has never made any such resolution

Jonathan Lange asked on Google+ for ideas about keeping a “write more” resolution. I took over his comment section, and in the spirit of taking some of my own advice, here’s a synthesis of what I said there. Since not writing as much as I feel I ought is never a problem I’ve had, this advice is in the delightful genre of someone who has never needed the advice simply making some up and giving it to you anyway! Enjoy my half-baked ideas.

Re-use your writing. A lot of people I know spend an enormous amount of time on crafting lengthy, tightly argued emails. These count, and you can make them feel like they count by editing them for a sufficiently general audience and publishing them on your blog. This is one I actually do do: several of my Geek Feminism pieces originated in annoyed private emails I sent to close friends, or in IRC rants.

Accountability and incentives. This is like all of the “how to exercise more” advice: make it public, make it social. Make a public commitment, make a shared commitment with a fellow writer. Have a competition, one-sided or not (“I will write more blog entries than N will this year”?). Deadlines and someone who will be personally disappointed in you can be an excellent motivator (as long as it doesn’t tip you over into an avoidance cycle), and for writing there’s a whole profession which involves, in part, holding people to deadlines and being disappointed if they fail to meet them: so, find an editor.

Unfortunately, in order to get an editor one generally needs to pitch (leaving aside the whole question of finding an agent, especially when it comes to fiction), which means writing, so you will have to be motivated to do some writing before you can partially outsource your motivation to editors and deadlines.

Becoming a freelancer seems like a big effort in order to fulfil a personal goal to “write more”, but part of the attraction is that you can pitch to places that have a ready-made audience, which means that you have outsourced any implicit “write more in places people will read it and find it useful” goal; you don’t need to put an equal or greater amount of work into building an audience for your writing.

Specific goals. This assists with accountability. What does writing more mean? A certain wordcount? A certain number of blog entries? A certain number of pitches sent out? A certain number of pitches converted to published articles? All of these are more artificial but easier to keep accounts of than “write more”.

Spend money. Enrol in a course or similar. This adds deadlines too, typically.

Creative Commons License
How to do more writing, by someone who has never made any such resolution by Mary Gardiner is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

Ada Lovelace Day: Marita Cheng, Robogals founder

Today, October 16, is Ada Lovelace Day: write or record a story about a woman in science, technology, mathematics or engineering (STEM) whose achievements you admire.
This is a slightly updated version of a profile that has appeared on Geek Feminism and Hoyden About Town.
Marita Cheng was named as the Young Australian of the Year winner at the beginning of the year. She’s been involved in volunteering since she was a high school student, and in 2008, early in her undergraduate studies (mechatronic engineering and computer science at the University of Melbourne) she founded Robogals, which is an engineering and computing outreach group, in which women university students run robotics workshops for high school age girls.

Marita, while still in the final year of her undergraduate degree, is also an entrepreneur and has been previously awarded for her work as founder of Robogals, including winning the Anita Borg Change Agent award in 2011. In 2012 she travelled to several countries with the aid of the Nancy Fairfax Churchill Fellowship to study “strategies used to most effectively engage female schoolgirls in science, engineering and technology.”

While I have heard of Robogals, I hadn’t heard of Marita specifically before she became Young Australian of the Year. One of the fascinating things about starting the Ada Initiative is slowly discovering all the other amazing women who work in technology career outreach and related endeavours. But it’s a little embarrassing, judging from her bio, to have not heard Marita Cheng’s name before the beginning of the year!

Further reading:

  • Marita Cheng’s website
  • Life is turbocharged for Robogals founder (a profile this past weekend)
  • Creative Commons License
    Ada Lovelace Day: Marita Cheng, Robogals founder by Mary Gardiner is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

    Ada Lovelace Day: Else Shepherd, leading Australian electrical engineer

    Today, October 16, is Ada Lovelace Day: write or record a story about a woman in science, technology, mathematics or engineering (STEM) whose achievements you admire.

    Else Shepherd is an Australian electrical engineer specialising in communications equipment. She has co-founded multiple Australian engineering companies, including Mosaic Information Technology, a custom modems company, and Microwave & Materials Designs, developing microwave filters for mobile phones. She was appointed as the chairman of Powerlink, the state government-owned corporation maintaining Queensland’s high voltage electricity grid, in 1994, and has been a board member of the National Electricity Market Management Company (now known as the Australian Energy Market Operator).

    Shepherd won Engineers Australia’s Peter Nicol Russell Memorial Medal in 2007, their most prestigious award, recognising an engineer with over 20 years of substantial contributions to professional engineering in Australia. As best I can tell, she is the only woman Peter Nicol Russell medallist. She is also a Member of the Order of Australia since 2003, and was the University of Queensland Alumnus of the Year in 2009. She is also a pianist and choral director.

    Shepherd has talked about her experience as a woman in electrical engineering with University of Queensland publications. She and one other woman graduated in 1965, the university’s first women graduates in electrical engineering. She was unable to attend Institution of Engineers meetings in the 1960s, because they were held at the local Men’s Club. She continues to promote workplace flexibility, having used part-time work during parts of her career to care for her two children.

    Further reading:

    Creative Commons License
    Ada Lovelace Day: Else Shepherd, leading Australian electrical engineer by Mary Gardiner is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

    Harassment report at your conference: what do you do???

    This article was written by me and originally published on the Ada Initiative’s website. It is republished here according to the terms of its Creative Commons licence.

    The Ada Initiative’s anti-harassment work and other anti-harassment initiatives have resulted in many conferences adopting anti-harassment policies.

    The Ada Initiative are not enforcers of individual conferences’ policies: this is the responsibility of conference staff, and conferences do not usually inform us of reports, nor do we expect them to. Harassment within a community is that community’s responsibility. However, in some cases when Ada Initiative staff have attended a conference, we have been asked to advise conference staff on responses. We’ve learned several useful techniques for making sure that the conference follows through quickly on its commitment to anti-harassment. We’ve drawn our experiences together into a wiki page: Responding to harassment reports.

    Our first tip is, of course, to have a policy. Harassment incidents at geek conferences — including open technology and culture conferences — are widespread. If harassment is reported at your conference and you do not have a policy, it is difficult to reach consensus among conference staff that harassment is not welcome, let alone that you should respond to it, or about how you should respond. The result is that people who are worried about harassment, or who have experienced it at your event or other events, will not feel or be safe at your event. Your policy should be in place before your conference. The Ada Initiative and Geek Feminism volunteers have prepared substantial resources on how to put a policy in place.

    You should also pre-prepare some emergency contacts, for incidents that you can’t handle. Conference volunteers and staff are rarely able to solely respond to and properly help with physical safety threats, illness or people in crisis. We suggest preparing a handout with contacts for emergency services, venue security, local medical and mental health facilities and crisis hotlines for mental illness, sexual assault, and physical violence. Make this info available in your conference materials so that attendees do not have to come to you, but have copies to hand in case they do.

    Having a staff member whose key responsibility is to assist attendees in difficulty (rather than routine conference chores) can assist in a fast response, see the Duty officer wiki page.

    Unfortunately, having a policy does not mean harassment won’t occur at your event. Once an incident is reported, you need to respond rapidly to reports. As the wiki page discusses in more detail you should:

    1. get a written report where possible, or have the staff member who received it write down what they were told
    2. have a staff member collate these reports in case of multiple incidents of harassment by one person, so that you can respond to the pattern rather than one instance
    3. have a staff member discuss the incident with the alleged harasser
    4. convene a meeting as soon as reasonably practical to decide on a response
    5. decide on a response and communicate it to the complainant and the harasser as soon as possible
    6. provide the harasser with an avenue of appeal if one is available but insist that they abide by any sanctions in the meantime
    7. communicate the incident and response briefly to the community, either attending the conference or reading your blog etc, to allow them to see that the policy is enforced
    8. remind the attendees and community where the policy is found and invite them to review it

    We welcome additional improvements to our detailed guide on how to respond to harassment reports. If you would like to discuss the suggestions, please do so on the wiki’s talk page.

    Creative Commons License
    Harassment report at your conference: what do you do???
    by the Ada Initiative is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.
    Based on a work at https://adainitiative.org/2012/10/04/harassment-report-at-your-conference-what-do-you-do/.

    Mary’s helpful guide to soliciting research participation on the ‘net

    This article originally appeared on Hoyden About Town.

    In my years on the ‘net, I’ve seen any number of people want to interview others or get them to take surveys for everything from a short high school or undergraduate paper through to graduate research projects and books. And they so seldom manage to meet basic ethical guidelines for making sure they aren’t wasting their participants’ time at best or endangering them at worst. Hence this article.

    In addition, this article may help research participants better assess requests: are researchers telling you what you need to know? Have they considered your interests as well as their desire to Find Something Out At All Costs?

    Full disclosure: I am not a research ethics expert, I am simply a researcher helping you get the basics right. Please seek expert advice if you have any doubt about the safety or integrity of your research.

    Why do I need to do this stuff?

    Because you’re so often asking people sensitive stuff, that’s why!

    Look, I have some sympathy for the “it’s just questions about something-seemingly-small!” myself. I ask people questions about their linguistic intuitions. “Which sentence reads better to you, A or B?” There’s nothing less fun than completing a 31 page ethics application to get approval to ask people about which sentences read better.

    But look, all research, at best, takes up people’s time. You owe people something for that. In addition, quite a lot of the research people are recruiting for on the ‘net wants to get into harassment of women, political affiliations, sexual experiences, why people write slash. That kind of stuff? That kind of stuff in the wrong hands loses people jobs and relationships. You owe people serious, well thought out harm mitigation for that.

    So, ethical research recruitment lets people know what they’re getting into, whether it is a boring half hour sharing linguistic intuitions, or sharing potentially damaging information with a reseracher.

    The bare minimum

    All researchers asking for participation should share this information:

    • Who are you?
    • Who do you work for or who commissioned this work, if not yourself?
    • How can I get in contact with you, and how can I get in contact with who you are working for?
    • What is the purpose of the research?
    • What is the status of the research? Is this sheer curiosity that made you whip up a survey in five minutes, or a pilot study, or the main game?
    • What kind of effort do you want from me? (Interviews versus surveys. Five minutes versus many hours. You get the idea. Tell me upfront what my time investment is.)
    • When you’re done, where can I see the results?
    • Will the results be made public and in what form? (A peer-reviewed article? A PhD thesis? A pop science book? On your blog?)

    Some of this might be the sort of thing you want to put on a webpage you can link to, so you can leave short advertisements like “Hi, I’m looking for help with X, and thought readers here might want to help because of Y, if you need to know more, please see LINK.”

    You;d be amazed how many people miss the “When you’re done, where can I see the results?” step. Even if they’re asking people for 20 hours of interviews or something like that. For anything but the most trivial investment of time, letting people read your results is the minimum reward required.

    Also, results being made public can often be good: the subject’s work is contributing to the sum of human knowledge! So don’t consider this necessarily a bad thing in and of itself.

    Institutional research

    If you are doing research at the postgraduate, postdoctoral or faculty level, research using human subjects (and other animal subjects for that matter, but you aren’t likely to be recruiting them on blogs) requires ethics approval by an institution-level ethics committee in most institutions.

    So, when soliciting participants for research that has ethics approval, provide the following info:

    • All the bare minimums plus
    • A statement citing your ethics approval in whatever manner is usual. Your committee probably has boilerplate. Typically this will name the institution, give a reference number for your experiment and provide contact details for the ethics committee.
    • If your ethics committee approved a recruitment advertisement, use it! If it’s long put it at the other end of a link if that’s OK with them.
    • If your ethics approval requires that you disclose a bunch of things, also state them or place them at your info link if allowed.

    If your institutional research didn’t require ethics approval (some institutions might, for example, have a blanket policy covering low-risk things like linguistic intuition questionnaires) find whatever boilerplate they let you use instead, if there is any or say something sensible along the lines of “This questionnaire comes under the XYZ University Low Risk Experimentation Policy [link].”

    Basically, if you are doing research on behalf of an employer state either that you have ethics approval, or if not, why not (eg, your institution has no committee).

    No committee but doing something sensitive?

    If you’re doing sensitive work outside the oversight of ethics committees, here’s the start of your checklist!

    • All the bare minimums plus
    • Are respondents going to be anonymised in your personal/researcher copy of the data? Are you stripping any associated names, IP addresses, email addresses and similar? If not, what are you keeping and why?
    • How are you storing the researcher copy of the data?
    • Who has access to the researcher copy of the data? (Yourself? Your boss? All of your boss’s present and future employees? The Internet?)
    • When do you plan to delete the researcher copy of the data, if ever?
    • Are respondents going to be anonymised in the published results? If not, what identifying information will you publish and why?
    • Can a respondent withdraw their participation and be deleted from your data or transcripts? How do they do it? How long do they have to do so?

    There are all kinds of other factors that ethics committees would get you to look at, basically, what capacity for harm does your research have? How are you mitigating that harm? What risk to your participants is left?

    Risks include: physical health risks; mental health risks (more common with online data gathering, eg, triggering questions); exposing people to relationship disruption or breakdown, or abuse (by, eg, asking them to discuss infidelity); exposing people to criminal prosecution (eg by asking them to discuss illegal drug use); exposing people to civil liability (eg by getting them to discuss breach of contract), exposing them to job loss; denying them the best treatment or resources (by, eg, giving preferential treatment to patients or students or employees who agree to take part in the research, thus harming others); and coercing participation in general. And there’s one question that frankly stands out to me as a member of the apparently rare species Lady on the ‘Net, which is “are you studying an over-studied population and if so, what benefit does this extra research have for them, as opposed to for you?”

    One of the most obvious mitigation strategies is anonymity of your subjects in reports, and eventual data destruction of any private identifying data. But as you can see from the examples related to coerced participation, it isn’t the only strategy you might need. List your possible harms, list your mitigations, let the potential subjects decide if the research is worth it to them.

    Related

    I wrote a similar post focussed on software development a few years back, in that case mainly focussed on “prove to your subjects that their participation is not a waste of their time.”

    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.