What Keeps Me at Mozilla

Doing good is part of our code.

A friend of mine is considering an offer to work at Mozilla and asked the question “what keeps me at Mozilla?” Below is my response to them.

(Note: As a couple of colleagues have indicated in the comments, this list is very-US centric. Benefits and even ability to work for Mozilla varies by your country of citizenship/residency.)

  • Near total flexibility in working environment. I can work at home, or from our Portland space, or any of the many Mozilla offices.
  • Ability to travel and go to conferences. Different teams have different policies about this, but over the last year I have been able to go to the conferences I’ve wanted to. Plus I can book travel to the MTV/SF offices whenever I feel like I need actual face-time.
  • Good salary and benefits. I don’t know exactly how Mozilla salaries compare to other Bay Area companies, but compared to Portland they are awesome. Last year I was able to pay off my student loan debt, save 10% of my salary AND buy a house. The health insurance is pretty good (not perfect; e.g. we don’t have complete coverage for trans folks yet). Paid time-off is plentiful as well (by US standards, anyway). And, having a flexible work environment means you can use for PTO for actual vacation as opposed to running errands or going to medical appointments.
  • Relative freedom in selecting your tools. You pick your hardware and operating system. You have root on your own machine. You can request a new laptop at least every two years (some people seem to get them sooner). There are gadgets like tablets, Android and now Firefox OS phones. If you need something to get your job done, you will get it.
  • Significant choice regarding what projects you work on. That’s not to say you can work on whatever you want according to whim alone. There is oversight, and your projects need to fit within Mozilla’s high-level goals. But within your functional team, you often have a great amount of say in what you spend your day-t0-day time doing. And, if you get in a position where you’re not doing what you really want to be, there are avenues for changing that.
  • Ability to work for mission-driven, open source oriented organization. Jobs at such organizations are rare because such organizations are few in number. At Mozilla, you have the honor of working for a project that has a ton of world-wide visibility and impact. We are working on initiatives that really matter, such as keeping the web open and bringing that open web to as much as the globe as possible (with Firefox OS).
  • You will work with brilliant, driven folks. These folks far outnumber the assholes. And it’s not just employees you’ll be working with. You will become part of a global army of awesome volunteer contributors.

If that’s piqued your interest, head on over to our Careers website and see if any of the open listings interest you. Got questions? I’m happy to answer them.

Oh, and to any co-workers who are reading, free free to add your own responses to ‘what keeps you at Mozilla’ by leaving a comment.

(Photo of Firefox billboard courtesy of Fligtar.)

Taking a Break

I’m taking a break from all social media and any unnecessary communication channels. I have a lot to do before I take vacation starting Friday until 2 January and I just don’t have it in me right now to participate in the non-stop, mostly-knee jerk discussion about violence and gun policy, among other topics. By and larege, my participation in recent dialogs hasn’t felt productive and I’m feeling more and more disconnected from the folks I interact with. That tells me it’s time to take a timeout.

After I tweet/share this blog post, I’m logging out of Twitter and Facebook. I have turned off email notifications for those services. I’ve left all non-essential IRC channels. However, I’m more than happy to interact with you all one-on-one. If you need to get a hold of me, feel free to:

  • send me an email (put level of urgency in the subject line)
  • give me a call
  • query me on Freenode or Mozilla IRC
  • send me a gChat

 

 

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.

Joining the Technical Evangelism Team at Mozilla

I’m happy to announce that next Monday, 5 November will be my first day working full-time as a technical project manager and evangelist on the Technical Evangelism team within Mozilla’s Developer Engagement group, lead by Stormy Peters.

I joined Mozilla 13 months ago as a Web Product Engineer on the Web Productions team. During that time I helped guide the successful launches of Firefox Live, Firefox Flicks, the Legacy Firefox Startpage, a re-vamped Mozilla Careers and De Todos Para Todos. I’m going to miss working day-to-day with my awesome colleagues on this team!

However, I’m also excited about what I’ll be working during the next year because I’ll be contributing to programs directly related to the launch of FirefoxOS. This includes the early adopter hardware program, and programs to engage developers in writing HTML5 apps for FirefoxOS.

If you love technical project management, consider applying for my previous role. Got questions about that or how you can get involved in FirefoxOS? Drop me a line.

 

Please Join Me in Supporting the Ada Initiative

The Ada Initiative is a not for profit organization with the goal of supporting women in open technology and culture. The organization is currently fundraising for operating expenses through March of next year. They are very close to reaching their goal, but need your help! I’m a recurring supporter of the organization, and have just made another donation in solidarity with Sumana and Leonard’s generous offer of a $10,000 matching donation towards this goal.

If you want women to increase women’s participation in open source and you want women to feel welcome and safe doing so, please consider a contribution. Your money will be used for many awesome programs, including: imposter syndrome training, career development resources, supporting women in submitting their first patches, resources for conference organizers, and much more.

Tech Podcasts Hosted by Women?

Last week I asked on Twitter/Facebook:

What are some tech/FLOSS podcasts that aren’t hosted exclusively by dudes?

I received very few responses.

Among them were two already on my radar: The two programs that Gina Trapani co-hosts, In Beta and This Week in Google, as well as yayQuery with Rebecca Murphey.

A person responded with two I didn’t already know about: Nixie Does Linux and Our SQL co-hosted by Sheeri Cabral.

I know women are underrepresented in tech, but there has to be some others. If you know of any, please leave a comment and let me know!

For a couple of years now, I’ve wanted to start a podcast and realizing the lack of ones co-hosted by women motivates me that much more. Problem is, I have no idea where to start. Oh, and no time. That means I need your help! if you’re interested in helping, please contact me.

 

Strategies for Facilitating Better Meetings

As part of my work with Mozilla and Stumptown Syndicate, I attend a lot of meetings and many of those I am responsible for facilitating.

I think most people consider meetings to be necessary evils. Meetings are often time-consuming, inefficient and take us away from real work we need to be doing, and yet they seem unavoidable. It’s probably true that we can’t get away with eliminating meetings all together. Sometimes you just have to get everyone in a “room” together to hash out some issue.

However, I think we can work towards having more efficient meetings and below are some strategies I’ve learned for doing so.

Designate a Facilitator

The facilitator is usually the “driver” of the meeting. She helps the group understand and achieve their objective(s), assists the group in following the agenda and staying on schedule. The facilitator should ensure that notes are taken. Often, but not always, the facilitator is the person who initiates and schedules the meetings (by sending out the meeting invite).

Have a Clear, Obtainable Objective

Before the meeting (ideally when the meeting is scheduled), an objective (or set of objectives) for the meeting should be drafted and communicated to the entire group. The objective should follow SMART criteria: specific, measurable, attainable, relevant and time-bound. If you are meeting to make a series of decisions, state what specific decisions need to be made.

Create and Distribute an Agenda

Having an agenda is essential for keeping a meeting focused and timely. Whenever possible, circulate the agenda ahead of time so attendees can: a) determine the important of their presence at the meeting and prioritize their schedule accordingly, and b) prepare for the meeting.

In agendas I draft, I always include the following:

(Descriptive) Meeting Title & Date

== Objective ==
== Attendees ==
== Agenda / Notes ==
== Action Items ==

Did you note my use of wiki syntax? Not a coincidence! If you’re using a wiki in your organization, writing notes and agendas in wiki syntax makes recording of agendas and meeting notes that much easier (more on this in a bit).

Make Sure You Really Need a Meeting

It sounds simple, but before you schedule a meeting, ask yourself if you really need one. Can you clearly state your objective and draft an agenda? If not, you may not be prepared to have a meeting. Would an email work instead? A quick IRC conversation?

Include Compete Participation Instructions

Include complete participation instructions every time, even for regular meetings with regular participants. The reason for this is that you want as few barriers to attending your meeting and being on time for it as possible. If someone has to go looking for information on how to participate in the meeting, there is a chance that they will be late or that they won’t attend at all.

Things to consider including in your meeting invite:

  • date and time (including in UTC)
  • physical location (if there is one) and any special access instructions
  • conference/video call information, including complete dial-in number, room number and any required access codes
  • key instructions for using the conference/vidyo call system (e.g. how to mute yourself)
  • direct links to on-line meeting systems
  • if software is required to participate in the meeting, instructions on how to obtain and install it

Don’t assume that participants will have any of the above info readily accessible, even if they have attended your meetings before.

Here’s text that I put at the bottom of every Mozilla meeting invite (some info has been faked, so please don’t use for a real Mozilla meeting):

==============================================================
Connection Details: 

Vidyo 9597 (ckoehler).

+1 650 903 0800, x92 (or +1 800 707 2533, password 000) 
Then 99597 

•1 to mute if you’re dialed in (nb: it makes an audible beep) 

Direct room link: 

https://v.mozilla.com/flex.html?roomdirect.html&key=1234567890

==============================================================

Note: If you’re a Mozillian and you want non-employees to join your Vidyo meeting, be sure to include the direct link.

Be Mindful of Participants’ Time

Because people’s time is precious, we should be mindful when requesting and utilizing it. There are several aspects to being mindful of your participants’ time:

  • Make sure each participant is really required at the meeting. Each of your participants should have an integral role in obtaining the objective of your meeting. If they don’t, add them as an optional attendee or don’t invite them at all.
  • Be aware of the timezone for each of your participants. When working with a global organization it’s often not possible to find a time that’s convenient for everyone. But you should have some awareness of who is being inconvenienced when, and try to distribute that burden. For example, don’t  schedule every meeting for times that are convenient only for those in Pacific time.
  • Start on-time and end on-time. Most people have multiple meetings per day, and have other things they need to do at certain times. Don’t make others late by conducting a meeting that exceeds its scheduled time. Better yet, strive to end a few minutes early! Most everyone appreciates a few unexpected minutes between commitments to stretch their legs, use the restroom and get some water or coffee. Likewise, be respectful of those who arrive on-time for a meeting by starting on-time. A meeting that starts at the scheduled time is that much more likely to end by the scheduled time.

Take Notes

One of the most important things you can do during a meeting is to ensure that good notes are taken. Taking notes has the following benefits:

  • helps to keep participants focused and on-track during the meeting
  • provides a clear record of what was discussed and decided during the meeting, for reference both by those who attended the meeting and those who were not able to do so

I find it works well for the group to take notes together in the same etherpad I have used for the agenda.  Notes do not have to be a word for word recounting of what was said in the meeting, but should include a summary of the discussion points, questions raised and answers given.

You don’t need to create perfect notes while the meeting is happening. Just record the important information and be prepared to edit afterward.

Follow-Up

A good meeting is not complete until you’ve distributed and recorded the revised meeting notes (or minutes), with key decisions and action items clearly indicated.

The complete agenda and note-taking process looks like this:

  • create and circulate an agenda in advance of the meeting
  • use etherpad (or another collaborative editing tool) whenever possible
  • take notes, with the group’s assistance, in the same document you used for the agenda
  • edit the notes after the meeting is complete, making sure to call out key decisions and action items
  • distribute the edited notes to everyone you invited to the meeting (not just those who actually attended)
  • record the notes in an accessible location (on a public wiki, on your organization’s intranet, etc.)

When I distribute meeting notes, I usually do so via email, with a link to the edited notes and action items included in the actual body of the email.

Your Strategies?

What strategies do you have for running better meetings? Let me know by leaving a comment.

Advice to Women Seeking Careers in Technology

Note: This post is inspired by this question submitted to Quora.

There are many benefits to a career in technology:

  • wages and compensation are high compared to other industries (even accounting for the wage gap between men and women)
  • many tech jobs offer flexible schedules and working environments
  • the work can be intellectually challenging and fulfilling

Here are some bits of advice I’d give to women considering a career in technology, or to those just beginning one.

Practice building confidence and be mindful about not selling yourself short.

It’s well known that women routinely under-assess their own skills as well as their value to their workplace or organization. Watch for this in yourself and work on ways to build your own confidence and self-assessment abilities.

Build and utilize a support network.

I can’t stress the importantance of having a network of people you can reach out to when things get tough (which they will, because that’s life). But don’t wait until you’re down in the dumps to reach out. Find a group of people you connect well with and make consistent connections with them. Don’t be afraid to attend women-only events and groups if you find that’s where you feel most comfortable.

Know that you will encounter sexism, racism and other misbehavior.

The tech industry is full of very privileged individuals and you will undoubtedly encounter sexist, racist and other kinds of bad behavior. No matter how trivial this behavior seems know that you are under no obligation to brush it off or grow a thicker skin. Know that you can talk about the bad behavior you encounter. If you don’t feel comfortable doing this publicly, utilize your support network.

Avail yourself of feminist and other anti-oppressionist resources.

Start with geekfeminism.org and microaggressions.com.

Learn to negotiate and ask for what you are worth.

This is a corollary to “not selling yourself short” and includes salary as well as desired job position. I know of companies who will offer the harder to fill, less prestigious positions to women first simply because they are more likely to accept them (even when they would prefer the more prestigious position). Read Ask For It for some good tips on negotiation in the workplace.

Know that work environments can vary significantly.

Workplace culture and environment can vary drastically from company to company. Don’t forget that when you’re interviewing, you’re interviewing the company in addition to them interviewing you. Ask them about their anti-harassment policies and what they do to facilitate women achieving in tech. If you think they could be doing better, consider letting them know.

Be a life-long learner.

Tech is a rapidly changing field where practice makes all the difference. Find a mentor. Be a mentor. Read code and write code. Go to user/meetup groups. Teach others. Practice. Build.

Fellow tech women who have been around a while now: What tips would you offer? Leave ‘em in the comments!

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.

My First Internet Death Threat (Trigger Warning)

Trigger warning: Violence against women, homophobia and fat-shaming.

Friday morning I woke up to find I’d received my first internet death threat. It was in response to my blog post about accountability. I’m posting the contents of the entire message below so that others have an idea of the kind garbage others and I have to endure when we choose to speak on social justice issues.

Unfortunately, the commenter was used an IP anonymizer, so there is no way to determine their identity. Is it a colleague or a total stranger? There’s no way to know.

Here’s the comment. Consider the trigger warning above before you decide whether or not to read on.

Jesus stop whining you stupid dyke. No one gives a shit what you think, and if you keep attention whoring like this you’re going to end up with your fat throat slit if one of us can manage to find a knife deep enough to penetrate your layers of blubber.

Point is, you’re just a useless, loudmouthed lesbian. Personally, I think you should consider leaving Mozilla or better yet do the world (and your parents) a favor and kill yourself already. You’re worthless fat waste of space and posting this garbage does nothing to promote Mozilla’s image. Grab an ounce of self-worth and delete your shitty blog, cunt.

I’ve known for a long time that those who speak out about anti-oppression and other social justice issues receive death threats. I now know first-hand how unsettling it is to be on the receiving end of such threats. It’s made me re-think my habit of checking email first thing in the morning before I’m fully awake an functional. What it hasn’t done is discouraged me from talking about these issues. If anything, being the target of such speech is just a reminder about how important it is for those of us in marginalized groups to be visible and to be heard when we feel we are able to do so.

Update 8 October 12:19: A couple of people have asked me to post the email headers and IP address of the person who left the comment. Unfortunately, it was left as a comment via WordPress so I don’t have email headers. What I do have is the IP address and reverse lookup as captured by Apache and WordPress software: IP: 31.172.30.1, tor18.anonymizer.ccc.de. It’s my understanding that there is no way to track the identity of someone who has used Tor, but I’m happy to share my Apache logs with anyone who thinks they might be able to get some more info from them. Also, the person gave the email address “kelly.rutherford@gmail.com,” but I assume that is not their own because why use Tor and then give your real email?