23 May 2007 06:19
Re: "Roles", was PROJECT: Bug Tracking
Julian De Marchi <julian <at> jdcomputers.com.au>
2007-05-23 04:19:47 GMT
2007-05-23 04:19:47 GMT
Robin wrote: > OK, here's a list of the folks who've volunteered for the teams so far: > > admins > krystal <at> devnull.net > shdwdrgn <at> sourpuss.net > julian <at> jdcomputers.com.au > > architects > krystal <at> devnull.net > shdwdrgn <at> sourpuss.net > thatoneguy <at> aaronjangel.us > > auditor > > bugmeister > shdwdrgn <at> sourpuss.net > > dbadmins > thatoneguy <at> aaronjangel.us > > hostmasters > krystal <at> devnull.net (root, opennic.glue, .null) > dennisthetiger <at> gmail.com (root, opennic.glue, .fur) > shdwdrgn <at> sourpuss.net (.oss) > > list admins > > pr reps > webmasters > brian <at> pongonova.net (Wiki) > shdwdrgn <at> sourpuss.net (registration, bug tracking) > > I will do the first audit myself, since no one's volunteered for it, but > since I'm admin on zero I'm not a good long-term candidate for auditor; > ideally that role should be filled by someone who's not an admin and can > thus monitor all the servers from the outside. > > The hostmasters list here is just the current hostmasters who've > commened; I'll fill it out with the rest of the current hostmasters when > I post the next revision. > > I can also continue as list admin for a while, I suppose, though I'd be > very grateful if someone could take that on. I'll be setting up mailman > on zero and setting up the team lists in it. > > Until someone volunteers to organize PR specifically, I'd suggest that > we assume everyone on these teams has some PR responsibilities? > > We do need a lead for webmasters. I definitely can't get the time to > redesign the site myself and work on the other parts I'll be responsible > for.> > -robin > Just putting some more ideas into the pot for support and monitoring. Request Tracker 3.0 to run a support system, where we all share equal responsibilities for support issues and monitor the RT for support tickets. I feel that using RT will give everyone an idea of what the common issues for OpenNIC users are. Also for monitoring of the OpenNIC systems, Nagios[0] might be a good choice to monitor all host systems. Nagios also has great graphing tools so we can put together a downtime chart, and various other informative charts. Has anyone had experience in both packages? I have setup a Request Tracker system, but have not had the privilege yet to play in depth with Nagios. ----- 0 - http://nagios.org/ Regards, Julian De Marchi ###################################################################### This is the discussion list for the Open Network Information Center. You can unsubscribe by sending an email containing the words "unsubscribe discuss" in the body of the message to "majordomo <at> opennic.glue" or "majordomo <at> opennic.unrated.net". ######################################################################
>
> -robin
>
Just putting some more ideas into the pot for support and monitoring.
Request Tracker 3.0 to run a support system, where we all share equal
responsibilities for support issues and monitor the RT for support
tickets. I feel that using RT will give everyone an idea of what the
common issues for OpenNIC users are.
Also for monitoring of the OpenNIC systems, Nagios[0] might be a good
choice to monitor all host systems. Nagios also has great graphing tools
so we can put together a downtime chart, and various other informative
charts.
Has anyone had experience in both packages? I have setup a Request
Tracker system, but have not had the privilege yet to play in depth with
Nagios.
-----
0 -
RSS Feed