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?


DRAFT: Community Sysadmins Proposal

I excerpted a bit from the Google Doc and have embedded the rest below. I would love feedback. I would love help. I need help.

Overview

communitysysadmins.org is an organization dedicated to connecting talented systems administrators who want to devote some of their time to help the open source and web open communities with open source and open web non-profit organizations.

Goals

  1. Harness the volunteer ops/sysadmin talent in the (dev)ops community in an organized, trusted, and scalable framework.
  2. Promote the goals of the greater open source and open web ecosystem by providing needed, skilled operations/systems administration services and experience to deserving non-profit organizations.
  3. Helping build and enhance the opsschool.org curriculum and promote the use of OpenBadges as a source of certifications of skills.

Draft Google Doc