IRCteamproposal
Differences between revisions 30 and 72 (spanning 42 versions)
|
Size: 2861
Comment:
|
← Revision 72 as of 2014-02-28 14:04:44 ⇥
Size: 1056
Comment: yeah, that was a just do it kind of suggestion, !ops-offtopic is now <reply> Thanks for letting us know you are here, someone will be along presently
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 4: | Line 4: |
| /* Entries here are for current agenda items */ == #ubuntu-release-party access list == 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. |
/* Entries here are for current agenda items, feel free to flesh them out. When removing items please comment on what the resolution was and/or link to meeting logs where they were discussed. */ |
| Line 8: | Line 6: |
| == Consider deactivating/re-purposing ~ubuntu-irc == This team exists from before we had separate Launchpad teams for the operators of each channel. It currently doesn't serve much of a purpose. I would like to propose that we "shut it down" for the time being. By that, I mean deactivating everyone, making it restricted, and changing the description to make it clear that it currently serves no purpose. This would help eliminate any confusion about the team's purpose, stop people from trying to join it, and allow us to revive the team at a later point if we have a need for an ~ubuntu-irc team. |
== Factoid Review == |
| Line 11: | Line 8: |
| ---- = Reference Entries = /* Entries here are kept only for reference */ == 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. |
It has been suggested that some of the ubottu [[http://ubottu.com/factoids.cgi|factoids]] are not very "friendly". Some need to be edited,updated, and some disabled entirely. Work on this has been started at [[http://pad.ubuntu.com/factoids|Review Pad]] == Alignment of launchpad and channel access lists == we use Launchpad teams to manage the process of applying for ops, but access is defined in channel access lists which are not tied automatically to launchpad https://docs.google.com/spreadsheet/ccc?key=0Ankl5FhsdSiZdGZVV2ZuLVRwa2c5M3pqX3BEaUhXMFE we need to do some maintenance to get these aligned one way or another and then have a semi-automatic process going forward to nudge things back into alignment as things change. |
Please Put any background information for your Agenda issue here.
Agenda Entries
Factoid Review
It has been suggested that some of the ubottu factoids are not very "friendly". Some need to be edited,updated, and some disabled entirely. Work on this has been started at Review Pad
Alignment of launchpad and channel access lists
we use Launchpad teams to manage the process of applying for ops, but access is defined in channel access lists which are not tied automatically to launchpad
we need to do some maintenance to get these aligned one way or another and then have a semi-automatic process going forward to nudge things back into alignment as things change.
IRC/IrcCouncil/IRCteamproposal (last edited 2014-02-28 14:04:44 by host217-36-92-70)