[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.]
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.
Advisory BoardLeadership Council (~ ReMo council)
- Core group of Community SysAdmin Mentors (~ Mozilla Reps)
- Community IT/SysAdmin/Ops volunteers (~ Mozilla contributors)
Rebooting Community IT with CSA
- What impact does this group want to have on open source projects and public benefit organizations?
- How do we become a force multiplier for your organization?
- What are our 9-12 month goals and objectives?
- How do we do it?
- How do we work with your existing IT Operations as partners?
And ask one more:
- How do we create the CSA to support organizations like Mozilla or Creative Commons, for example?