Tagged: Open Source

Open Source Day at Grace Hopper: Core Team Members Wanted

The Open Source Day event (2012 overview) is part of the annual Grace Hopper Celebration of Women in Computing conference (GHC). This year I am co-chairing the Open Source Day (OSD) with Alice Bonhomme-Biais, who has been involved with OSD at GHC championing the Google Crisis Response project

The purpose of the Open Source Day is twofold:

  1. To give Grace Hopper attendees the opportunity to learn what open source is, how to contribute to open source projects and to make their first contribution!
  2. To help open source projects become more friendly to new and novice contributors.

We accomplish this by inviting a dozen or so open source projects (usually with a humanitarian focus) to join the Open Source Day and connect with contributors (GHC attendees, mostly college students). In the months prior to OSD, we work with participating organizations to prepare their projects for new contributors and during the event we facilitate this on-boarding process.

Soon, we’ll be asking organizations to apply to be a part of the Open Source Day.

Right now we need to assemble our core team. If you’re interested helping to make OSD a success this year, please do the following no later than Friday, 29 March:

  1. Read through the list of core team roles.
  2. Take note of the time commitment and general responsibilities and make sure you’re comfortable with them.
  3. Contact me to let me know that you’d like to be on the committee. If a particular role interests you, let me know that too. DEADLINE: Friday, 29 March (but the sooner the better).

Once we’ve heard from everyone, we’ll meet as a group to solidify the roles and select a weekly meeting time.

For those of you who participated last year, you might  recall that organization leaders were a part of the core planning team.  We have decided to change that this year to let org leaders focus on  getting their project ready for the event. Instead, each org leader will be assigned an org coordinator (part of the core team) as a point of  contact with the core team. We’ve made this change in order to make our  weekly planning meetings run more efficiently and to create a meeting  space where org leaders can discuss the issues most relevant to them.

A Moment of Reflection on Firefox’s Birthday

8 years ago today, Mozilla released Firefox 1.0. I remember when this happened. I was 23 and working for a small technology publisher in San Francisco. Even now, I can feel the excitement I felt then at having a viable open source alternative to Internet Explorer. I was an early Firefox Affiliate and I installing it on every computer I could get access to, including all the ones at work.

Never in my wildest dreams did I think then that I’d be fortunate enough to make my living in open source, let alone working for Mozilla. Mozilla isn’t a perfect organization, and it’s been a stressful first year for me, but I’m still proud to call myself a Mozillian and look forward to being here for a long while. At least long enough so see us successfully launch FirefoxOS and hire some more women and queer people (especially in technical roles).

What about you? Where were you when Firefox 1.0 launched?

Oh, and If you’re curious about this history of the Mozilla Project, including key releases, check out this timeline.

Death Threats in Open Source Are not Occurring in a Vacuum

Individuals who make death threats start with less egregious behavior and systematically test the boundaries of the communities in which they exist. When they get away with small violations, they often move on to larger ones. They watch what others are able to get away with, too. The pattern of behavior is common among abusers. If you’re an abuse survivor, you know this implicitly.

The open source community consistently condones the type of behavior that can escalate to death threats. The “free as in freedom” philosophy has created a haven for privileged individuals to act without accountability. Harassment, discrimination and exclusion of women, queer and trans people, racial minorities and other individuals from marginalized groups are commonplace. This is not okay. Not only is it morally wrong to exclude people in this manner, but communities thrive on diversity and stagnate without it. Open source is no different, and we have largely been failing to address this issue.

If you’re not actively working to make your community welcoming to a diverse set of individuals, you are part of the problem. If you are a white, straight cis man and you look around at your community and the majority of what you see are straight, white, cis men, then you are part of the problem. If your project or community does not have a code of conduct and you are not actively providing meaningful enforcement of those standards, then you are part of the problem. If you are not holding your technical leaders accountable for their behavior that is harming the community, then you are part of the problem.

We can no longer operate under the fantasy that maintaining healthy open source communities is solely a matter of technical skill or competence. As Matthew Garrett recently stated:

No matter how technically competent a community leader is, no matter how much code review they perform or how much mentorship they provide, if they’re expressing unacceptable social opinions then they’re diminishing the community. People I know and respect have left technical communities simply because people in positions of responsibility have engaged in this kind of behaviour without it causing them any problems.

Want to lessen the number of death threats that women (and others) in open source receive? Adopt a strong code of conduct and enforce it. Do not allow misogynist, sexist, racist, homophobic, etc. comments or behavior, no matter how trivial they feel to you. Don’t ask people like me to explain to you ad nauseam why a fellow community member saying “we don’t want you around” is a threat. Don’t argue when we say that a co-worker  who advocates against universal marriage is advocating legislative violence. Instead, hold those who make these statements accountable.

In other words, reducing and eliminating death threats in the open source community starts with being intolerant of microagressions.

O’Reilly Open Source Award

O'Reilly Open Source Award

Last Friday I was presented with an O’Reilly Open Source Award. The award recognizes  “individual contributors who have demonstrated exceptional leadership, creativity, and collaboration in the development of Open Source Software.” Wikipedia has a list of previous winners.

Not only did I get the very awesome sharpie-enscribed lightbulb award you see above, but I also received my very own Eggbot! The Eggbot is an open source CNC artbot and was used to create the awards.

I’m honored to be recognized by O’Reilly for my work getting people involved in in Open Source through events like BarCamp Portland and Open Source Bridge via my governance of Stumptown Syndicate.

However, these efforts are by no means singular. The projects I’m involved in are successful because of the awesome people that choose to volunteer their time to help make them a reality. I would have liked to be able to recognize a dozen or more people on stage with me last Friday. Thank you Audrey Eschright, Reid Beels, Jim Eastman, Kirsten Comandich, Amy Farrell, Chris McCraw, Igal Koshevoy, and Melissa Chavez for working with me on these projects year after year. And, thank you to my lovely wife Sherri Montgomery for supporting my work and joining in herself.

If you’re curious what Edd and Sarah said about me, check out the video here:

I feel as if my work in open source and free culture is just beginning. There is so much more to do. If you’d like to join me, get in touch!

 

Still No Code of Conduct at Mozilla

It’s been nearly four months since events at Mozilla lead several of us to call for adoption of a code of conduct. And yet we do not have one.

I can’t tell if progress is stalled, or if we’re just not hearing of updates. The last post to mozilla.governance on the topic occurred in early May. What’s going on? Why does this appear to be a non-priority for our leadership?

Regardless of the reasons, four months is a long time to wait for something that was long overdue to begin with. It’s a long time to wait to have reassurance from my community that I, and others like me, are welcome, and that discriminatory behavior against us will not be tolerated.

Codes of Conduct and Censorship in Technical Communities

Over the past several months I’ve been thinking a lot about anti-harassment policies, codes of conduct, when censorship is harmful and when it is appropriate. During this time I’ve seen a number of comments about how codes of conduct simply aren’t necessary, how they will be used as instruments of unnecessary censorship, and how some people have been bullied into adopting them.

You know what? I’m rather tired of seeing these comments over and over again and of having to argue that it’s necessary for communities to adopt a code of conduct.

Being open, welcoming and safe to all, including gender, sexual and racial minorities, is not the default state of our technical communities (particularly in open source). This is a sad truth, but a truth nonetheless. And, it’s one that people continue to dispute despite overwhelming evidence. All one has to do is to look at the dearth of members from minority populations who participate in open source. Or head over to Geek Feminism and read through the list of incidents.

If communities want to change the status quo they need to be proactive. One way of doing that is to adopt a policy outlining expected conduct.

We decided to adopt such a policy for this year’s Open Source Bridge. It’s something we put considerable effort towards. We created a draft, revised it several times, shared it with a range of community members and revised it again. We made sure to publish it prior to our CFP close so all prospective speakers would know what we expected of all participants.

In the process of writing the code of conduct we realized the following was important to us:

  • emphasize the positive as well as negative behavior, focusing on the idea of open source citizenship
  • give organizers the flexibility to deal with situations according to their best judgement
  • emphasize the grassroots nature of open source bridge by having the same policy apply to everyone involved (speakers, attendees, etc.)
  • give participants a sense of agency around their experience at the conference

Focus on Citizenship

As we discussed what sort of policy to adopt it became clear to us the we wanted something more than an anti-harassment policy. Having zero-tolerance for harassing behavior at conferences is of course important, but we realized that we wanted more than just an explicit catalog of prohibited actions. We wanted a document that emphasized the idea of open source citizenship. We wanted to focus on recognizing positive as well as negative behavior.

Give Organizers Flexibility

We also wanted the document to be flexible enough to allow organizers to utilize their best judgement in dealing with situations. We didn’t want to create a situation where we had to deal with behavior that is clearly problematic but that we failed to identify and elucidate ahead of time in our code of conduct. We knew we couldn’t list everything that could potentially go wrong. Along those same lines, we didn’t want to be in the position of having to kick someone out of the conference for less problematic or correctable behavior or for violating our code of conduct simply because we were unskillful in our wording.

Highlight our Grassroots Effort

Open Source Bridge is a grassroots event, organized entirely with volunteers. It’s important to me that those who are involved with our event: the speakers, the attendees, the participants and volunteers know how important they are in making OSBridge a successful event. Each of those roles is just as important as the other and we wanted this equality to be clear in our code of conduct. This is why we have one code of conduct that it applies to everyone. Each person has the same set of responsibilities to make OSBridge a positive event for all involved, including themselves.

Empower our Participants

We wanted participants to feel that our code of conduct gave them a sense of agency and empowerment about their experience. Don’t like something you see? You have a right and a responsibility to say something about it. Don’t like how your colleague is being treated? Let us know. We wanted to encourage folks to come talk to us about any issues that arose and included very clear way to contact us to do so.

The Result

The end result is something I’m very proud of and I think time will demonstrate it is has made our entire community better for everyone (not just previously marginalized groups). We even created a generic version, the Citizen Code of Conduct that we’ve made available for others communities to adopt and adapt as needed to meet their specific needs.

Is it perfect? No, it’s not. We’ve already identified somethings we want to make better. We want to want to clarify what we mean about participating actively and authentically. We also want to add something about contacting organizers to resolve any questions participants may have about their content/behavior being objectionable.

The code of conduct is a work in progress and we’ll keep iterating on it as we get feedback from our community.

On Censorship and Freedom of Expression

So now that we’ve adopted a code of conduct, does that mean that we’re going to use it to arbitrarily censor ideas and people we don’t like from the community? No, it doesn’t. I think if we started to engage in this sort of abuse people we would be called to task about it by our community.

Having a code of conduct does, however, mean that we’re going to take seriously and investigate any reports we receive of content and/or behavior that violates it. And, yes, since we don’t have a list of explicit rules, we’ll use our best judgement to determine how to handles any incidents that arise. This is no different than every other decision you already trust us with when you decide to participate in the conference.

Not everyone will agree with the calls that we make, and I’m okay with that. I’m also okay with using our power as conference organizers to potentially censor content or behavior that is harmful to a subset of our community.

I’ll say it again in another way: I don’t believe that censorship is in and of itself a bad thing because freedom of expression is not an unlimited right. From Wikipedia: “the right to freedom of speech is not absolute in any country and the right is commonly subject to limitations, such as on libel, slander, obscenity, incitement to commit a crime, etc.”

Yes, censorship has been using by those in power for hundreds of years as tools of oppression and tyranny. But censorship also prevents harm from being done to vulnerable populations.

We censor children’s access to pornography so that they have less of a chance to witness sexual material before they are ready for it. We censor hate speech. We censor certain incitements to violence and crime. We (hopefully) self-censor too, for a lot of good reasons: so that we don’t hit our kids or tell our co-workers to go fuck themselves when we’re having a bad day.

Part of being a mature and responsible adult is knowing when freedom of expression should be limited and censorship is appropriate, and when it is an abuse of power wielded for selfish means or ulterior motives.

As conference organizers we hold that our participant’s right of expression carries with it certain responsibilities. We therefore we ask everyone to abide by a code of conduct and reserve the right to enforce certain restrictions on speech and expression if it becomes necessary.

Moreover, there is a huge difference between government censoring disagreements, which is what protections around free speech are really about, and a community deciding standards are required for participation. The latter is what we’re doing with our code of conduct.

Will some feel disenfranchised?

I recognize that some feel disenfranchised when communities adopt a code of conducts.

They are unwilling to accept that codes of conduct are unnecessary. They take it personally and resent being told how to act like a grown up. They think themselves feminists and above scrutiny. They think there’s nothing wrong with including overtly sexualized material in a technical presentation. They think it’s perfectly okay to name a software package “upskirt” or “pantyshot.” They say we’ve taken political correctness too far and by doing so have removed all fun out of going to conferences. They claim we engage in witch hunts against perfectly respectable members of our community.

And everyone is entitled to their thoughts and opinions.

And we are entitled as a community to exclude a few in order to welcome the many that have been marginalized time and time again.

So, if you feel excluded by our code of conduct, I encourage you to examine your own privilege and behavior and see if you can’t open your heart to what we’re trying to do.