Thursday, November 17. 2011

IT and Community

Mozilla's IT team is pivoting to a more community-focused approach. Our director of IT, mrz, has been writing extensively about it over the last few weeks.

As you can imagine, the difficult part of this is to balance security with accessibility. We'd like to be open, but we can't give the keys to the kingdom out to anyone who promises to help. The approach we're taking is to treat volunteers as we would part-time employees - post positions, interview, and then supervise to gain trust. This is a fairly common model, actually, for any organization with volunteers and a need for security. Youth programs, for example, generally do an interview and background check with new volunteers, and those volunteers will be paired with senior volunteers or staff for a while.

However, it's a bit cumbersome, both for Mozilla and for potential volunteers. We must design entire positions - ongoing tasks or roles that a volunteer can work on for an extended period of time - and then select a limited number of volunteers to fill those roles. For potential volunteers, an application and interview can mean a long time (weeks?) before they get to do anything hands-on. It also carries the risk that we'd have to turn a qualified volunteer away due to lack of suitable positions.

So what to do?

We need a more fluid way of interacting with potential contributors. Since our bug database is public, we can begin by simply tagging a few bugs that are appropriate for newcomers -- things that don't require sensitive access and are well-encapsulated so they can be completed without extensive knowledge of Mozilla's infrastructure.

Here's the list.

It's a bit short right now. There are a few things that may help:

  • We can get better about identifying appropriate tasks and projects and making bugs out of them.
  • We can identify a means of giving limited or sandboxed access to a new volunteer.
  • Consumers of Mozilla's IT resources can begin tagging bugs, where Mozilla can provide the resources and volunteers can do the heavy lifting - got any ideas?


No Trackbacks

Display comments as (Linear | Threaded)

*If you have a bugzilla account, you should be able to add the "good-first-bug" search to your footer; see

#1 Dustin J. Mitchell on 2011-11-17 07:19 (Reply)

*This is great. Being more clear about opportunities people can take on should make it easier for people to get started.

One thought about your bug list -- have you thought of also marking these as mentored bugs? This will show new contributors that there are people available who will help with any problems they have working through a task. More about that at

And to help people find the right bug from them, Josh Matthews has put together a demo that offers a way to search through open mentored bugs based on certain criteria.

If this looks like it would be helpful for IT bugs, let me know.

#2 David Boswell on 2011-11-29 00:00 (Reply)

*Yes, that looks quite helpful!

I'll let the IT folks know about the [mentor=..] tag, and see if we can add those as necessary/possible.


#2.1 Dustin J. Mitchell on 2011-11-29 00:25 (Reply)

Add Comment

To prevent automated Bots from commentspamming, please enter the string you see in the image below in the appropriate input box. Your comment will only be submitted if the strings match. Please ensure that your browser supports and accepts cookies, or your comment cannot be verified correctly.

Markdown format allowed


The postings on this site are my own and don't necessarily represent the opinions of my employer, or anyone else.