I’m very excited to announce that the Badg.us website has fully transitioned over to Community IT Ops infrastructure!
Badg.us is a site where anyone can create a series of Open Badges to recognize skills, achievements and interests. This platform is available for free and intended to provide an easy option for issuing interoperable badges that align with the Open Badges metadata standard.
This took a lot of effort from the team but I specifically want to acknowledge Edmund Wong.
We are leveraging our HP Cloud OpenStack infrastructure as best as we can, including HP’s DBaaS and LBaaS. This allowed us to focus on the website & app and let the “cloud” handle the rest of the infrastructure. Edmund documented our setup, should you want to spin up your own version of Badg.us.
One of the core tenants of Community IT Ops is education. In fact, the Mission Statement even says so:
How we do it
Teaching and education are core to our mission and values. We mentor and teach today’s skills and help put those skills to practical use by hosting and running production sites and services. We use OpenBadges to acknowledge skills and accomplishments.
I’m extremely excited – and happy – that this is the first service that Community IT Ops stood up.
A big thanks to everyone involved.
ps. Maybe you want to get involved?
[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.
ReMo structure (draft)
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:
- 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?