Gregory Ruiz-Ade wrote: > > I think what's making this painful for us is that there's no clear > definitions of who's responsible for what on sparkplug.
We have a semblance of a list, that is the sudoers file. Of course, there is no separation of tasks (ie: OS maitenance, website maintance, mailing list, ftp, whatever else we happen to be running). If you want to handle the OS(admin) side of the website and mailing list, I shan't stand in your way! (I'm not a fan of either plone or mailman). Hell, I'll let you deal with postfix too! Take me out of sudoers, and I'l be sad :( > I think we actually need to create some organizational structure for > management of sparkplug, and some clear policies on notifying others > of changes made to the club's server/services. Do I smell a wiki? That would actually work well. Especially a ``private'' one for the admin(s). Provided, of course, it were actually *used*. We did have another mailing list, [EMAIL PROTECTED], that could also be used for such a thing. Assuming people are happier with email than with a wiki Properly, it should be archived (such as a mailing list) so future admins can look into the past for changes updates etc. > I would like to say, though, that Josh has done an admirable job of getting > everything going, especially with the new OS install, migration to Plone > for the website and Mailman for the lists. All this in his spare time > outside of work and home life, too. Ditto. > Basically, if we created the position of "KPLUG SysAdmin", I'd be happy to > fill it, barring any other members' objections, since I tend to hear about > all the niggling kplug sysadminny problems anyway. :) Heh, you are not the only one ;) -john -- [email protected] http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer
