IRC administration and development
Helping administer and develop UKCIRC. If you've got experience with doing IRC oper stuff then we'd like to hear from you.
Interested people:
- bcc
ojc4 (No proper experience mind, but willing to learn)
- tdb
mhp2 (same as ojc4, no real experience, but I do kinda live on IRC !)
- drb8
- ah
- Nick Griffiths (nbg2) - no op experience, but willing to learn.
- mpb3 (Dabbled a bit with a friends ircd a while ago)
- wah3
- aa79
- td22 (Dabbled a bit as an oper, no proper ircd config experience)
- jam33 - experienced with people issues, and troublesome irc users (#christian attracts it :| )
- frmb (general user/oper/conf-vi'er)
Ideas:
- Talk about linking to Canterbury Christchurch University College (or whatever it's called)
- #compsoc should become the Network Support Channel
- Encourage greater usage, encourage usage at other campuses on the UKC network
- iBot needs its own account on compsoc1 (any other bots that could use the same?)
- Question: having Compsoc hardware controlled by the uni for the purposes of accounts was raised as a probable condition of getting better external access for compsoc. Having bot accounts could preclude us from this.
- No, it wouldn't -- loads of services run under their own accounts already. You wouldn't be able to log in as iBot; it's just a uid that iBot's processes use. - ats1
We wouldn't do that from compsoc1 anyway, it's in the wrong place physically (it has to be in the machine room, really) and we'd probably do this from one of the RaQ boxes on a clean install
- drb8
- Monty, perhaps? I know somebody said he/she was going to look after Monty, but, compsoc could look after Monty better for the long term
- PJM has another postgrad lined up. When we found out who, we can find out if he wants to run it on compsoc hardware.
- spambot?
Seems to have disappeared
- Question: having Compsoc hardware controlled by the uni for the purposes of accounts was raised as a probable condition of getting better external access for compsoc. Having bot accounts could preclude us from this.
- An actual "misc" channel for random babble, drunkeneness etc - make cs a Computer Science channel (makes sense IMO)
Well, #cs can mean Compsoc
I suggest we leave #cs as the "main" channel. I don't think we can force people to change... #compsoc can be network support.
- Not an idea but I (mpb3) think we should be careful about going power crazy, we rarely have need for an operator on IRC
Sure -- but right at the moment, when we *do* need an operator, it's hard to find one. I'm all in favour of the hands-off approach; I just think there should be more people doing it.
(ats1)
loveserv (td22)