December 13, 2011
This article was contributed by Valerie Aurora (formerly Henson)
The Ada Initiative is a
non-profit dedicated to increasing the participation of women in open
technology and culture. In other words, we want more women in open
source, Wikipedia, and the rest of our brave new Internet world. A
lot of people agree with that goal - at least that's what
our first
Ada Initiative survey told us. (Note that the Ada Initiative has
absolutely nothing to do with the Ada programming language, other than
sharing a namesake. Your author wrote Ada 95 for a living once and
sincerely hopes to never touch another "bondage-and-discipline"
language again.)
LWN readers might remember us from
our launch announcement
back in February, as well as our first "Seed 100" fundraising
campaign.
This article is an update on what Ada Initiative has done since its
founding, what we're doing next, and what you can do to help.
Accomplishments this year
The most surprising and visible change in open tech/culture
communities over the last year was
the widespread
adoption of some form of code of conduct or anti-harassment policy
by over
30 conferences and organizations. (The exact number is hard to
determine since some organizations adopted the policy for all their
events and put on dozens of events per year.) Many major Linux and
open source conferences have a policy: all Linux Foundation events,
including Plumbers, LinuxCon, and Kernel Summit, linux.conf.au, all
Ubuntu Developer Summits, several PyCons, OSBridge, all O'Reilly
conferences (pledged), and many more. The idea that everyone should
be able to attend a conference without expecting to be harassed or
threatened is spreading to fan, science-fiction, and open culture
events as well. Given
the level of controversy a
year ago, this shows a strong change in public opinion across a
broad swath of the open technology and culture community.
We ran two surveys this year. First was the Ada Initiative Census
(part
1 and
part
2), with over 2800 responses (about 1600 from women). We ran this
survey to find out what people thought about women in open technology
and culture, which communities had more women than others, and if people felt that having more
women was a good goal or not. A lot of people had told us that they
wanted more women in open tech/culture, and that they felt many
communities weren't very welcoming of women, but it was good to get
statistical confirmation from several thousand people.
Our second survey asked attendees of the Grace Hopper Celebration
(mainly young women in university computer science programs) about
their attitudes towards careers in open source. It was an extremely
simple and open-ended survey, nonetheless two common themes appeared:
most believed you couldn't get paid to write open source software or
that it paid much less than closed source, and that the
"personalities" and culture of open source were intimidating and
unpleasant. This is important information to know so that efforts to
recruit new college graduates into open source jobs can be successful.
We also achieved our goal of being the "go-to" organization for advice
on how to
respond
to incidents of harassment in a way that says women are a welcome
and valued part of the community. Often it's merely an issue of
raising awareness: Most people simply don't know that harassment and
bad behavior is happening. If you're a famous, well-known,
influential member of the open source community, you're likely to be
treated very well, and if you do run into any obnoxiousness, you have
a lot of friends willing to come to your aid quickly. You won't have
much of an idea of how newcomers are treated, or people who look
different from you, or don't have as many friends as you, unless you
go looking for their stories. One place to find these stories is on
the "
Timeline
of sexist incidents in geek communities" maintained on the Geek
Feminism wiki.
We organized our
first AdaCamp
for January 14, 2012, in Melbourne, Australia (the Saturday
before linux.conf.au 2012 in nearby
Ballarat). AdaCamp is a small invitation-only unconference bringing
together a variety of people to collaborate on ways to increase the
participation of women in open technology and culture. We have people
from open source, but are making a strong effort to bring in people
from Wikipedia, fan culture, and other
areas. Applications
are currently open; if you know someone who should attend,
encourage them to apply! For our North American AdaCampers, our next
AdaCamp is tentatively planned to coincide with Wikimania in
Washington D.C. in July.
We wrote a first draft of Ada's Advice, a guide to useful resources
for people who want to help women in open tech/culture, organized by
the role of the person looking for advice: parent of a young daughter,
employer looking to hire more women, women in open tech/culture
themselves. I'm constantly trying to find that link to that one
article that I vaguely remember being somewhere
on the Geek Feminism Wiki and
failing; this is my solution. We are also planning to write short summaries
of books and longer articles, as well as some original content and
updating older content (such as
generalizing HOWTO
Encourage Women in Linux to open tech/culture overall). We think
that people shouldn't have to read ten books before they can start
helping women effectively.
Ada's Careers is a project in the planning stage. This is our answer
to the abandoned job postings mailing list - you know, the one you
create after recruiters keep trying to post jobs to your development
mailing list and then no one ever reads again? Well, we want to
create a career development community: a place where women hang out
all the time because it helps them at all stages of their careers, not
just when they are looking for a new job. Finally, we'll have an
answer to "Where do I put my job posting where qualified women will
read it?"
Another project we'd like to run is First Patch Week. Often,
experience writing open source is a prerequisite to getting a job in
open source. At the same time, women face extra barriers to getting
that unpaid experience, starting with local user group meetings
that are often uncomfortable for women to attend, to
IRC servers where users perceived to be female are 25 times more
likely [PDF] to get a nasty private message than those percieved to be
male. We want
to partner with an open source company to donate a week of their
programmers' time to mentor women through the process of creating and
submitting their first patch to an open source project. This will be
an expensive and time-consuming project to run the first time, but
will get easier as we repeat it, and will have a major, direct effect
on the number of women available and qualified to be hired by open
source companies.
We have some other project ideas but these are the ones we're most
likely to do soon. What project do you want to see finished next?
Leave us a comment telling us what your favorite is.
The not-so-fun stuff: Paperwork and government regulations
I'm a kernel programmer by training, so it's not that surprising that
I found myself comparing the process of incorporating a
U.S. non-profit with booting a kernel. You have to bootstrap from a
couple of people with an idea for a non-profit to a legally registered
corporation with strict oversight by a board of directors, with every
step along the way properly authorized and recorded. It may not be
the best analogy to explain how to found a non-profit, since most
people don't know how the boot process works either, but since
this is an article for LWN I can get away with it.
The non-profit/boot analogy goes thus: (1) file articles of
incorporation (BIOS) and bylaws (bootloader), (2) take "action by
incorporator" to appoint the board of directors (secondary
bootloader), (3) board votes for standard "startup" motions (kernel
initialization), then (4) board meets regularly to vote on new
motions, elect new board members, and delegate tasks (servicing
interrupts, running processes).
The "articles of incorporation" are paperwork you send to a state
government declaring that you are a non-profit corporation. The
articles of incorporation describe the ground rules of the corporation
and don't change. The bylaws, which can change, are filed at the same
time as the articles of incorporation and describe how the corporation
is governed - stuff like how the board of directors is elected.
To me, the most obscure part of the bootstrapping process was the
"action by incorporator." Sure, the bylaws say how your board of
directors elects new directors, but how do you get your board in the
first place? What happens is that the person who filed the articles
of incorporation (me, in this case) writes down who they appoint to the
board of directors, states they relinquish all rights as incorporator,
and then signs and dates the document. Presto, the corporation now
has a board of directors in complete control.
From there on out, everything is governed by votes by the board of
directors. The board usually delegates a lot of stuff to the officers
so it doesn't have to meet every time the hosting bill has to be paid.
There is an initial set of standard motions that most corporations
pass that is similar to kernel initialization, allowing the officers
to do things like hire lawyers and buy liability insurance. After
that, the board meets routinely and as-needed (which is like responding to
timer ticks or servicing interrupts) to vote on
new motions. We even have an equivalent of AppArmor or SELinux: We
have to make detailed yearly reports to the U.S. tax service on our
finances and management, beginning with filing an incredibly complex
and expensive application for tax-exempt status.
The annoying stuff: Fundraising
Fundraising is a lot like funding a startup except that no one gets rich.
We began in classic self-funded startup fashion: For 7 months we lived
on our savings and part-time consulting work. We also
had angel
funders who trusted us enough to give us money on faith: Linux
Australia, Puppet Labs, and the Ceph division of DreamHost. Next we
raised a round of "seed funding": 100 donors of $512 or more in our
Seed
100 round (actually, 103 because we couldn't close the drive fast
enough). We've nearly used up our startup capital and have started our
first
general fundraising drive, open
to both
small individual donors
and large corporate
donors. If you like the work we're doing, and want to see things
like Ada's Advice and First Patch Week become a reality, please donate
now and tell your friends about us too!
We're still debating the long-term funding model for the Ada
Initiative. Should companies who benefit financially from open source
and open culture fund most of the Ada Initiative? Should we rely on
lots of small individual donors like Wikimedia? Should we sell
t-shirts? Tell us what you think in the comments!
(
Log in to post comments)