IRCteamproposal

Revision 26 as of 2010-04-15 14:23:18

Clear message

Please Put any background information for your Agenda issue here.

Agenda Entries

  • #1 I would like the council to review and potentially amend the access list in #ubuntu-release-party before the launch date to consider removing the ubuntumember ship cloak users from the access list. The last party channel was a very rowdy channel and a strong portition of the ubuntu member cloak holders where not mature enough to manage the channel without playing silly games. I understand the channel is supposed to be a fun place but kicking people for fun and placing bans in a channel is not part of that fun. I would suggest adding the core channel operators to the list and removing the membership cloak access.


Reference Entries

Create a basic IRC operator technical guide, how to get +o, how to use /remove, using the Bantracker, etc

We, as operators, tend to use scripts to help in administering the channels we operate in, these scripts are useful and we encourage them. However an IRC operator should know how to preform every action manually. Too often it seems we rely on scripts or bots to do these things for us, this is fine until they break or malfunction. A good grounding in IRC commands is essential and something I don't think we have amongst all of our operators. This includes:

  • Asking ChanServ to give you +o

  • Setting a relevant ban (not to wide or to narrow)
  • How to find bans for a specific nick
  • How to remove bans properly
  • How to quiet/mute a user
  • How to use /remove
  • Using the Bantracker effectively.
  • How to communicate concerns/reasons behind a ban or kick/remove via comments.
  • Always comment on bans/kicks/removes/marks, having to read through a log is not quickest way to find out why the action was taken.
  • Update comments as the issue progresses.
  • Catalysing should always be the first method used to resolve issues.
  • When to use a quiet/mute (to provide an opportunity to talk to the user) instead of just removing.
  • How to react to /msg abuse, what actions can be taken.
  • How and when to use forwards, rather than bans.