On Wed, Jan 12, 2011 at 6:21 AM, Sebastian Dziallas <sebast...@when.com> wrote: > Subject line says it all. :) Seriously, Mel and I have been talking > about this more and more in Doha, since we're pretty sure that > there'll be a higher amount of requests coming in starting in March > (when we push strongly for further POSSEs, but also work on an open > textbook related talk at EduComm), and I figured I'd just give it a > jumpstart. > > I created a wiki page for an Infrastructure Team here: > http://teachingopensource.org/index.php/Infrastructure_Team > > So. I know there's been previous conversations about this (and, as a > disclaimer, I know that I won't have the time to lead this) and I'd > like to ask people to put their names there if they are interested in > working on this. Basically, what's the latest state here? > > -s
While I tend to lean towards ctyler and Karlie, and make sure that as much of POSSE/TOS that can happen in the Open Source communities in question does. I think that it makes sense to have a group dedicated to infrastructure. However, if I was a person looking to volunteer (which I suppose I am) here's what I'd be interested in knowing: 1. What is the scope right now of what needs to be supported. (eg, server with wiki, mailing lists, etc) 2. How deep does that scope of responsibility run? (are people going to come to the sysadmin team for wiki problems that aren't infrastructure related - or perhaps better stated, how much of the applications are they expected to own.) 3. That you acknowledge that expanding scope might mean you need to find an owner for the expansion. If it were me trying to set this up, I'd be looking for 1-3 sysadmins to act as leads. Ideally they'd have experience dealing with F/LOSS infrastructure groups previously, and they'd also ideally have some experience with larger infrastructures typically found in the corporate world. They should know puppet (or chef, cfengine, bconfig2, etc), nagios, etc. and they should spend the vast majority of time working on setting the infrastructure project standards/guidelines/documentation. While that sounds really unsexy, and like it will take I think TOS is small enough that's likely a relatively minor job. _______________________________________________ tos mailing list tos@teachingopensource.org http://teachingopensource.org/mailman/listinfo/tos
