Main menu:

Site search

Feeds

Categories

December 2014
S M T W T F S
« Sep    
 123456
78910111213
14151617181920
21222324252627
28293031  

Archive

The Ada Initiative Has My Back

Bess at PuppetConf 2013
The Ada Initiative has my back. In the past several years they have been a transformative force in the open source software community and in the lives of women I know and care about. To show our support, Andromeda Yelton, Chris Bourg, Mark Matienzo and I have pledged to match up to $5120 of donations to the Ada Initiative made through this link before Tuesday September 16. That seems like a lot of money, right? Well, here’s my story about how the Ada Initiative helped me when I needed it most.

Donation button
Donate to the Ada Initiative





Thanks to the Ada Initiative, having a conference code of conduct has become an established best practice, and it is changing conference culture for the better. I’m so proud of the many library conferences and organizations who have adopted Code of Conduct policies this year. However, just because a conference has a policy in place doesn’t mean there won’t be any problems. I’d like to share something that happened to me this year, the way the Ada Initiative helped me and the conference in question deal with it, and how things have since improved.

I gave a talk at code4lib a few years ago called “Vampires vs Werewolves: Ending the War Between Developers and Sysadmins with Puppet“. The talk was well received enough that it became a little bit of a meme, and last year PuppetConf asked me if I’d give an updated version of it for PuppetConf 2013.

It was exciting to participate in such a huge conference. PuppetConf is well funded and professionally managed. They have a code of conduct in place, friendly and helpful staffers, and high quality content. I was having a great time up until right before my talk.

Unfortunately, the talk before mine was titled “Nobody Has to Die Today: Keeping the Peace With the Other Meat Sacks.” I watched this talk on the video monitor from backstage, while getting hooked up to a lapel microphone, already a little nervous about facing such a large audience.

The speaker was a large heavily muscled man who was shouting more than speaking into the microphone. He was shouting about violence, and about how many people get murdered in the workplace. He particularly mentioned the fact that murder is the number one cause of death for women in the workplace. I felt my blood running cold. My body felt flooded with fear, and I wanted to run. He went on to discuss the many ways he personally had hurt people, through his work as a bouncer, in martial arts, or just because someone made him angry. At this point I was literally shaking. I have been on the receiving end of violence. I have known people who have been murdered. I know people, especially women, who have been hospitalized with the kinds of injuries he was graphically describing having inflicted. In spite of the small print disclaimer on his slides that this presentation was not encouraging violence, it was doing precisely that. If you don’t communicate technical requirements in the way he specifies, apparently, you will get what’s coming to you and you will deserve it.

The conference staff backstage were horrified. Some high profile people in the audience were walking out. It was clear that I was upset (I was trying not to hyperventilate at this point) and someone kept asking me if I wanted to file a code of conduct complaint. The thought of this made my panic even worse. I could easily picture filing a complaint and then paying for it with my life, when this guy found out and beat me to death in the parking lot after the conference. I said I did not want to file a complaint. I tried to take deep breaths and to not break down crying. I was determined to give my talk in spite of my shaky emotional state.

And I did. I delivered my presentation, which went surprisingly well, except for the fact that in the video I am swaying back and forth. I don’t usually do that when I speak, and I read it as the outward manifestation of how upset I was.

Afterwards, I thought for a long time about writing to the conference with my concerns. I started to do so several times, but I always chickened out. It was too easy for me to picture this guy learning my name and coming after me. Before you dismiss me as paranoid please consider the stories of Anita Sarkeesian and Kathy Sierra. Women in technology face worse than sexist jokes. We face assault. We face death threats. If you defend the status quo, understand what you are defending.

It wasn’t until this year’s PuppetConf call for proposals that I complained. The conference had liked my talk last year, and invited me to submit another talk this year. I wrote to decline, and told them why. I also sent a copy of my letter to Valerie Aurora, asking for the advice of the Ada Initiative.

I am very pleased to say that PuppetConf took my concerns seriously. Working with the Ada Initiative, they strengthened their code of conduct, put more screening measures in place for presentations, and improved training for conference staff on how to deal with problematic situations. PuppetLabs is an example of a company that is doing things right. They have specific outreach programs to get more women involved in the Puppet community and they are pursuing similar strategies to encourage participation from underrepresented racial groups. I feel good about the fact that I’m sending members of my staff to PuppetConf 2014, and at this point I would gladly speak at the conference again.

As upsetting as this incident was, this is a story with a happy ending. Because the Ada Initiative exists, both PuppetConf and I had someone to go to for guidance in how to improve the situation. Honestly, I still feel a little afraid about writing this post. But I also believe that nothing gets better until people take the risk of speaking out publicly. I am choosing to take that risk, in order to better communicate about why this work matters.

The Ada Initiative continues to do great things. You can read their 2014 progress report here. I am particularly excited about the Ally Skills workshop that will be offered at the Digital Library Federation Forum on October 29. Today, librarians are showing our love for the Ada Initiative. Watch for blog and social media posts from friends in library land who will be sharing more stories about why the Ada Initiative matters, and follow the action on twitter under the hashtag #libs4ada. Join us in supporting the Ada Initiative’s mission and donate today!

Donation button

The Courage of Misha and Amy

I continue to be blown away by the courage in the face of bigotry displayed by the We Do Campaign. Watch the new video they’ve just released (embedded here) and contrast the self-righteous Bible quoting at the beginning with the quiet dignity and brave commitment to the path of love shown by Misha and Amy.

And then go give the Campaign for Southern Equality a few dollars.

Please also join our Mad4Equality March Madness tournament, which is raising money for the Campaign for Southern Equality and the Trevor Project.

Chris Bourg, a wonderful colleague of mine at Stanford, wrote a great blog post about Mad4Equality, in which she calls me out:

And I’m calling out Bess Sadler right now to put up another $25 against my bet that my Blue Devils will dance longer than her Tarheels. Go Cardinal, Go Blue Devils!

I accept. And I also back a similar bet that Stanford’s Nerd City Kids will dance longer than any other team anyone cares to name.

#mad4equality

Earlier this year, the Campaign for Southern Equality released some powerfully emotional videos (see above) in which same-sex couples across the South walked up to counters where they knew they would be denied marriage licenses and asked for marriage licenses anyway. Simple acts of courage like this can make an enormous difference in changing culture. Furthermore, I am convinced that we need to fight for marriage equality in the south if we want to achieve it everywhere else. Why support CSE?

Across the South, LGBT people lack basic legal protections, face robust opposition to our rights and have limited resources for advocacy. LGBT people in our region are also at an elevated risk of poverty. Beyond this, the South receives less than five percent of the total annual funding that goes to LGBT organizations nationally. Factors like this contribute to the commonly held belief that the South is “unwinnable” when it comes to LGBT rights.

But we hold a different view. First, we believe there is a pressing need for advocacy, legal and crisis response services for LGBT people in the South. Second, we believe that LGBT people and allies in the South are uniquely positioned to accelerate winning full equality on the federal level by directly resisting discriminatory laws and systems. Third, we believe that every person – including those conflicted about or opposed to LGBT rights – can become an ally.

As a result, we’re taking a new approach, building upon a rich legacy of civil rights organizing in the South and working in close partnership with other LGBT and civil rights groups.

I grew up in Chapel Hill, North Carolina, where Tar Heel basketball is taken pretty seriously. I have long since moved away, but March Madness always makes me homesick. This year, I dedicate my homesickness to improving my home’s culture.

I am proud to team up with my friend Chris Bourg (“the Feral Librarian”) and the Butch Wonders blog to host a March Madness tournament, proceeds to benefit the Campaign for Southern Equality

The basic details are described at Announcing … Mad for Equality! We are planning on a $10 per bracket entry fee, with 1/3 of the pot going to the winner(s), 1/3 to Campaign for Southern Equality, and 1/3 to another LGBT equality charity to be determined by popular vote. So — head over to Butch Wonders and nominate your favorite charity. We will also be tweeting about the contest on the hashtag #mad4equality.

You can also donate directly to the Campaign for Southern equality at http://www.southernequality.org/donate/.

Why we don’t speak up

Oh, Internet. There is never a shortage of anonymous cowards willing to say horrible things in secret. And this is not good for discourse, because only some of us get to receive emails like this on a regular basis:

I think the most accurate conclusion that can be drawn from all this complaining of late is that women actually are inferior.

I know that, because you have a vagina, you probably have lots of dudes tripping over themselves to tell you how great you are! But, to the rest of us who do not play that game, you just look dumb.

I received this email and I took a few deep breaths. I recognized that I was feeling shame. Time to unpack that feeling! Among many other reasons, I am feeling shame because we aren’t supposed to say the word “vagina.” That is one of the words I (and you, and all of us) have been conditioned to feel shame around, because we view women’s bodies as shameful. This leads to the kind of thinking that classified “pregnancy” under the heading of “disease” in the Dewey Decimal system. [1] More personally in my own life, it leads to a society where some of us can’t really get medical care because we have medical issues concerning parts of our bodies that everyone is trained not to acknowledge. So when this anonymous coward sent me this nice little message, one of the things he’s trying to do here is re-assert the patriarchy. It’s a dog whistle to the conditioning he knows I’ve received. I feel sorry for the women in his life, I’m sure he finds lots of little ways of letting them know how valueless he believes them to be.

Many people get harassed on the internet, but for some of us it carries extra baggage or vulnerability. It is one of the very real reasons why many women (and queers, and ethnic minorities, and any kind of “othered” group, especially one whose members have been conditioned by violence) sometimes fear to speak up when they witness unacceptable behavior. I have reached a point in my life when I am done accepting it quietly. The consequences of ignoring this kind of behavior are too high. The Workplace Bullying Institute has a great summary of some of the effects of bullying. I am convinced, and they show some compelling evidence, that bullying is a form of violence. This is what happens to an employee who experiences regular workplace bullying:

  • You feel like throwing up the night before the start of your work week
  • Your frustrated family demands that you to stop obsessing about work at home
  • Your doctor asks what could be causing your skyrocketing blood pressure and recent health problems, and tells you to change jobs
  • You feel too ashamed of being controlled by another person at work to tell your spouse or partner
  • All your paid time off is used for “mental health breaks” from the misery
  • Days off are spent exhausted and lifeless, your desire to do anything is gone
  • Your favorite activities and fun with family are no longer appealing or enjoyable
  • You begin to believe that you provoked the workplace cruelty

I want more diversity in the open culture movement, and I do not want the people we recruit to feel like that. Those of us who are here already, please join me in making your harassment public, when it is safe for you to do so, so that we can have a more useful community-wide dialogue on the issue.

[1] See The Power to Name by Hope Olson for many other examples of how library classification systems have repeated societal biases

Creating a Commons

This is the text of my talk from code4lib 2013. My slides are here. Video is here.

Hi, I’m Bess Sadler, and I work at Stanford University Library. I build open source software for libraries, and it’s pretty important to me. This is not my first code4lib, I’ve been around for awhile.

—-

We lost a member of our community this year. Aaron Swartz spoke at code4lib in Portland in 2008. His work on Open Library was inspiring to many of us, including me. He was a library hacker in the very best sense, and he brought a sense of ethics to his work that affected me deeply. I am glad to have known him, and I am grateful for his contributions.

In addition to his work with bibliographic data, Aaron also helped to design the creative commons licenses.

—-

I love the creative commons licenses. In case you haven’t encountered them before, let me explain that they say the same thing in three vocabularies: Machine readable, human readable, and lawyer readable.

I’d like to suggest that successful community developed software projects, and technology communities like code4lib, should adopt the same strategy.
____

Machine readable means cool uris, and unit test coverage, continuous integration, and semantic markup.

—-

It means building software that’s easy to integrate, and is able to accept code contributions without breaking. I won’t spend much time on this because it has already been well covered at this conference, and in books like Practices of an Agile Developer and Producing Open Source Software. I will just say that shared engineering practices become more and more important the larger and more distributed your development team becomes, and it is an investment that’s worth making.

—-

And lawyer readable, well, we’re not lawyers, so I don’t want to spend a whole lot of time on legal contracts, except to say, yes, you really do need to figure out your governance and legal structure if you want to collaborate across institutions for very long. And it’s a very good idea to get anyone who is contributing code to your project to sign a contributor license agreement. It goes a long way toward establishing a clear legal standing for any code that is produced.

Being lawyer readable can make your life a lot easier, and can make a big difference in whether your software project attracts new adopters and committers. In fact, it might determine whether their employment contract allows them to participate at all.

Again, this is covered in the books I just recommended, and the apache software foundation also maintains an excellent guide to getting your open source software project on firm legal footing. Again, this is an investment in your project and your community that is worth making. I too love under the radar software that we develop and share informally. I don’t want to lose the spirit of informal collaboration that code4lib does so well. But we must recognize that we live in a larger context, one where major lawsuits have happened because of unclear code provenance. Be smart and protect yourself.


Machine readable, lawyer readable, these are important. But what I really want to talk about today is being human readable.

When we build software, what are we building? Software code, certainly, but we are also building ways of doing things, a group of people who know how to work together, and the traditions they create. In other words, a culture. In other words, a commons.

How many people here went over to the fedora4lib house this week? Fedora4lib is a team of software engineers from several institutions, who arrived in Chicago early, rented a house together, and have been collaboratively creating the next version of fedora. They had a couple of open house events this week, which were really fun.

When I got over there Chris Beer had just baked cookies. This is definitely my idea of developer happiness. I talked to the developers, and the feedback I heard was that not only had they been productive and produced something that all of these institutions can benefit from, they felt closer as a team, they communicated better.

Hydra, in addition to being a digital repository solution, is a community. In fact, increasingly, this seems like our primary identity. What we are finding is that the ability to collaborate on common solutions is more important than any single project. This gives us resiliency, and room to experiment. I think having a community makes us feel safe enough to take risks, and sharing work frees up our time to innovate. By trusting each other, and cultivating in each other a willingness to experiment, we get to try cool experiments like fedora4lib. And I think we’ve hit on something worth doing again.

This intentional focus on hydra as a community has been a successful strategy. You might have noticed from the talks this year, quite a few institutions have been joining the hydra community, and it seems to be working out well for them. In fact, we realized recently that the limiting factor on our growth was our ability to hire and train people to build and run these repositories.

That’s one of the reasons I’ve been spending some time this year teaching for RailsBridge in San Francisco. I am thinking about how to teach digital library concepts to people who are new to programming, or new to libraries, or both. Partly this is to help meet the hiring and training needs of hydra institutions, but it’s also because I believe that building and maintaining library software is vitally important work and it’s too big a job to leave to a small group of people. We are creating the future of libraries here. I feel like the stakes are pretty high. I want the solutions we develop to be inclusive, and I am deeply worried about the fact that only 2% of open source software developers are women. I want to do something about that, and teaching seems like a way I can make a contribution.

But when I think about what it is I’d really like to teach people who are new to coding for libraries, what I come up with isn’t about technology so much as it is about adopting a problem solving mindset, something I am starting to think of as “hacker epistemology.” Epistemology, if you’re not familiar with the term, refers to the question of how we decide what’s true, how we construct knowledge. For example, someone might have an epistemology of received knowledge. That person would decide what was true based on what an authority figure told them was true. Here in code4lib, many of us have more of what I think of as a hacker epistemology, this magic combination of collaborative knowledge building, combined with a disregard for the mental traps of conventional thinking. We like to take things apart and see how they work. Sometimes we listen to what authority figures tell us, but we easily discard received knowledge if we gather evidence that contradicts it. I think it’s this attitude that has made code4lib so successful. We value rough consensus and working code. The truth is what works.

—–

I was very sorry to miss code4lib last year. I hear that Dan Chudnov delivered an outstanding keynote. I am sorry I missed it, but happy that I got to hear a little about it last night. If I understand Dan’s message, he was saying that it’s important for us to grow code4lib to accommodate all of the people who want to join us and contribute to our work. I couldn’t agree more. This year, we have more people here than ever before. We have taken major steps forward in making code4lib more open and welcoming for newcomers. Now I want to take a few more steps in the direction of building inclusive community.

I love code4lib, and I make extensive use of it, so it seems only natural to me to want to improve it. Step one in hacking a system is trying to understand the system, and looking for places where it might be possible to make a change. One way I hacked code4lib this year was by requesting that we adopt a code of conduct.

Having a code of conduct is becoming a recognized best practice in the open source community, and a proven way to attract a more diverse audience for conferences and communities of all kinds. I am pleased to say that we did adopt a code of conduct, and we join great organizations like the Linux Foundation and the O’Reilly conferences, in taking this step. As of January 9, the django software foundation will only sponsor events with a published code of conduct, and more and more open source projects are following suit. After code4lib adopted our code of conduct, CurateCamp adopted a similar statement. I find all of this very encouraging.

And… I get it, not everyone thinks it’s necessary, just like not everyone wants to sign a contributor license agreement. But having a readable consensus statement about our values, and a positive affirmation that this is a safe space, really does improve the quality of our commons.

I didn’t ask for a code of conduct because of anything egregious that had happened in code4lib, but because it’s a good idea organizationally, and because I wanted us to make an explicit statement about inclusiveness. Unfortunately, we as a community do not get to start from an assumption that this is a safe and welcoming space. Sexual harassment and assault have been rampant problems in the technology world, including the world of open source software. This has been true for a long time, but thanks to courageous community members who are willing to speak publicly, who make themselves vulnerable to further attacks by refusing to remain silent, these incidents are being discussed and we as a community have an opportunity to fix this critical bug in our culture.

If we don’t define our own parameters, we are accepting the default. And the default is terrible. We can do much better than that, and we have to let people know we want to try.

Another way I hacked code4lib this year was by submitting more than one talk. For those of you new to our speaker selection process, people can submit as many talk proposals as they want, but they can only give one. We periodically discuss changing this policy, but I’d like to request that we keep it. And, I’d like to invite people to use this policy the way I do. It is important to me to have women on this stage. I want diversity of all kinds, for example I would also like to see more public libraries represented in code4lib, but given that librarianship is a majority female profession, but the tech side is majority male, I am particularly concerned with hearing from more women at this conference.

— We are all impostors.

And here, this is my final hack for this year:

Who here has ever felt like there are some astonishingly smart people in code4lib? Who has ever felt afraid they couldn’t keep up? Raise your hand.

I feel like that a lot. I think all of us do. And if we just acknowledge that truth, we go a long way toward disarming that intimidation factor.

I was talking with a friend of mine this week about these issues. He is someone who I think of as an ultimate code4lib insider. He gives talks, teaches workshops, and writes amazing software. And yet he confessed to me this week that he often feels, especially at code4lib, that he is surrounded by people who are smarter than he is, and he can sometimes feel like he’s faking it. He told me that the way he deals with that is to bolster himself, to put on his game face, to go into the world armored with masculinity and emotional invulnerability. “Do you think,” he asked me, “it might make a difference to our ability to be inclusive, if I stopped doing that? If I just admitted that I don’t know what I’m doing sometimes?” I had to try really hard not to reach out and hug him. “Yes,” I said, “I think that would make a huge difference. We should all do that.”

This makes me think of what researcher Brene Brown has to say about vulnerability.

Vulnerability is not weakness. Vulnerability is the courage to show up and allow ourselves to be seen. To try, even when we have no guarantee of success.

When we make our code public, when we allow others to find our weak spots and help us strengthen them, that is vulnerability that leads to strength. And when we acknowledge our own emotional vulnerability, the fact that many of us feel lost and overwhelmed, by technology, by work, by life, then we allow others to acknowledge those things too, and we create a context where we can support each other.

So those are my attempts at hacking on this community to make it fit my needs better. But clearly, this task is too big for me to accomplish alone. I’d like us to set up a system for accepting bug reports on our commons. The code of conduct we just adopted is our current working document for how we have decided to do that. The process can, undoubtedly, be improved further, and I encourage us all to think about how to do that.

My request of you, of us, is that we put on our hacker mindset when we file and receive these bug reports. For example, this week I received a bug report that the original title of my talk, “How to be an effective evangelist for your open source project,” was a little alienating to some here for reasons that, I admit, were invisible to me until a friend explained that, as someone who identifies as Jewish, he often feels made invisible by Christian metaphors. He didn’t like to bring it up, but he trusted me enough to let me know that that word bothered him. Because we were having a conversation where we were explicitly trying to be honest with each other without hurting each other, instead of getting defensive I was able to stay present, stay vulnerable, and accept his bug report. And I changed it. And now my presentation is better and I feel closer to my friend. This is a good system.

This community is so special to me. I joined the code4lib irc channel when I was in library school, back in 2003, before there was a conference. This community has been a source of strength to me, a place where I have made wonderful friends and developed my own skills far beyond what I once thought I was capable of. I am so happy to see the ways that we have grown, and eager to see what we’ll do next.

Thank you, code4lib, for another great year.