In most ways, right now at least, you can’t. We’re too closed. It’s like I said in my first blog post,
IT is generally closed. Mozilla is not. There’s a incredible disconnect there. How do we leverage the expertise of the Community in running some of the busiest websites in the world?
In my travels over the past year I’ve met a number of passionate volunteers with IT skills who are looking for different ways to volunteer and contribute to Mozilla. In the past two months, that list has exploded.
I’ve talked about how we want to reboot Air Mozilla, how we want to open video and make it possible for more people to tell the Mozilla story in video.
But Mozilla IT is still closed.
Help me change it?
I want to illustrate what we want to do.Watch this to see how we want to pivot to open.
Good question. I think I need your help to figure this out. It’s going to feel weird and uncomfortable for us. Of all the steps we set out to do nearly two months ago, this has been the most challenging. There are so many processes to work out.
- What sort of agreement should volunteer Mozilla IT sign? A code of conduct? There are some parts of the infrastructure that must remain secure and secret even as we strive to be open.
- How do we build the trust necessary to give someone root access?
- How do we on-board new Mozilla IT volunteers? Does everyone get root access on day one? Is there some graduated process? What is it?
- Do we host onsite (or remote) training events to teach you about our tools and processes?
Today, as a code contributor, we ask you to sign a Committer’s Agreement. It’s a simple document that shows you understand what it means to contribute code to Mozilla and understand our legal requirements.
As part of Mozilla IT, you’ll have access to some pretty mission critical systems. I invite you to take a look at the Mozilla IT Agreement and share your feedback with us. It’s meant to be a lightweight agreement similar to the Committer’s Agreement.
Want to get involved?
We’re doing a lot of this thinking out in the open at https://wiki.mozilla.org/IT/CommunitySysadmin and I invite you to join and participate -
- Read the Mozilla IT Agreement.
- Read Dustin’s blog post and how we’re trying to identify bugs you can start working on.
- Join the Mozilla Community Directory @ https://mozillians.org/ (Read this blog post if you forgot why it’s important!).
- Join the conversation on the Community IT mailing list. Help us answer these questions.
- Join the IRC channel, irc://irc.mozilla.org/it
- Actually get involved. Do IT. We have a number of positions we’re looking for you to help in:
Preparing for 2012
I want to reiterate two of my goals I mentioned in my first post nearly two months ago.
My own personal goals by the end of 2012 are:
- to have 5-10 volunteer Community Sysadmins actively helping run Mozilla’s network and servers.
- to have a vibrant Community IT group…
I made the comment that it felt like the most ambitious thing we’ve done. It probably still is but in two months we’ve shifted our way of thinking, took Air Mozilla Mobile on the road and have a long list of things you need from us.
2012 will be fun.