Rebooting Community IT, Part 3

[After Part 1 & Part 2 I thought I was done. But the more I reflected on what Community IT could be I realized there’s a Part 3 where I’ll share some of the thinking we came up with that resulted in a Draft Proposal.]

The CSA

This past January I started working with my former colleague @thunder (currently at Creative Commons) and my friend and then current colleague @solarce (Mozilla Webops) on what it would be like to have an organization comprised of volunteer SysAdmins who would lend their time to help manage infrastructure & systems for open source and public benefit organizations. Not too unlike the Open Source Lab but extending to not just open source projects but organizations like Creative Commons or Mozilla.

We called this Community SysAdmins or CSA.

Some of the thinking that went into the January draft was based on our collective experiences at Mozilla, especially around organizational governance – modules and module owners, for example.

My thoughts around this continued and I began to think more about reasons why Community IT within Mozilla hadn’t taken off. Or why it had taken off very slowly.

I started to see a model where it could work and it was not unlike the Mozilla Reps model.

ReMo structure (draft)

ReMo structure (draft)

  • CSA Advisory Board Leadership Council (~ ReMo council)
  • Core group of Community SysAdmin Mentors (~ Mozilla Reps)
  • Community IT/SysAdmin/Ops volunteers (~ Mozilla contributors)

Rebooting Community IT with CSA

As we start thinking about what it means to Reboot Community IT, I want to share the draft CSA proposal we created and re-ask these modified five questions I asked in Part 2:

  1. What impact does this group want to have on open source projects and public benefit organizations?
  2. How do we become a force multiplier for your organization?
  3. What are our 9-12 month goals and objectives?
  4. How do we do it?
  5. How do we work with your existing IT Operations as partners?

And ask one more:

  1. How do we create the CSA to support organizations like Mozilla or Creative Commons, for example?

Continue reading

Rebooting Community IT, Part 2

[This is Part 2. In Part 1 I wrote about where we started from and where we are today. In this post I’ll share where I want us to go.]

From 2011 to 2013, Mozilla IT’s impact on the Mozilla Community lead to Air Mozilla and Community Website/Email Hosting.

CSAimageThe holy grail was something more. Something where volunteer contributors were running or helping run websites and working with Mozilla IT Operations.

Something where there is a “talented group of volunteer SysAdmins who want to devote some of their time to help the open source and open communities with non-profit organizations that work to create open source and a better, open Web.”

[I blatantly lifted that off communitysysadmins.org – an effort I started with a small cohort of people early in 2013.]

Mozilla & Community IT Operations
There hasn’t ever been a Community IT Operations anything at Mozilla.

Throughout my tenure at Mozilla we’d occasionally spin up servers or services that would be managed by someone in the community. We’d even support whole projects that were related to Mozilla but largely independent projects (Camino & SeaMonkey, for instance).

But unfortunately this felt very ad-hoc. These where difficult to support within Mozilla IT Operations.

What’s Next?
With my Mozilla contributor hat on, I want to build a new movement.

I want to start with a focus on Mozilla and build a Community IT / SysAdmin / Operations movement.

And I know we can do it.

We will be fierce. No one will build into the Internet the kinds of things we want to build.

Community IT Operations Kick Off Meeting
I want to invite you to join my movement and our kick off meeting. We’re still sorting out then when (scheduling is hard – check out this Doodle to help me find a time).

In the mean time, think about how you’d answer these questions:

  • What impact does this group want to have on the Mozilla project?
  • How do we become a force multiplier for Mozilla?
  • What are our 9-12 month goals and objectives?
  • How do we do it?
  • How do we work with Mozilla IT Operations as partners?

Join communityit@mozilla.org and watch https://wiki.mozilla.org/IT/Community for updates.

Join me?

We will be fierce. No one will build into the Internet the kinds of things we want to build.