IRCteamproposal
Differences between revisions 1 and 72 (spanning 71 versions)
|
Size: 2512
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 1: | Line 1: |
| == Future and purpose of the IRC Team == | Please Put any background information for your Agenda issue here. |
| Line 3: | Line 3: |
| The IRC team is currently described on launchpad as: | = Agenda Entries = /* 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 5: | Line 6: |
| The Ubuntu IRC operator team is responsible for managing the Ubuntu channels on freenode. | == Factoid Review == |
| Line 7: | Line 8: |
| * Ubuntu-IRC is a team of operators, approved by the Ubuntu IRC Council. * The team exists to give Ubuntu channel contacts a ready pool of enthusiastic, trusted operators for their channel should they need it. * Channel contacts should also hopefully be able to trust a user belonging to this group if that user requests access. |
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 == |
| Line 11: | Line 13: |
| The IRC Council accepts new members to this group after observing the sustained positive contribution of an operator in one or more Ubuntu channels. More information is available at the ircteam wiki: https://wiki.ubuntu.com/IrcTeam The question is, is the scope of the team still current, and is more guidelines on how people are assessed for eligibility to join the team necessary? Please feel to add your thoughts and idea here, and bring them to the next council meeting. == Criteria for +v in #ubuntu-ops == Currently there is a rather haphazard way of adding people to the voiced (+v) operator list in #ubuntu-ops. We need to have a uniform and standardized proceedure for eligibility for +v in #ubuntu-ops. The purpose of +v is to show users who are operators in the channels that #ubuntu-ops covers, to understand who can deal with their query. Therefore, in my understanding, an operator in one of the core channels, that are managed by the ubuntu-irc team and come under the scope of #ubuntu-ops, should have +v in that channel. All others should not be permitted under the no idle rule. Comments on this view are welcome below: - == Implementation of same system for #ubuntu-irc == Currently there is an issue with finding operators from the loco channels when a problem arises, and is asked about in #ubuntu-irc. I propose we implement a similar system in #ubuntu-irc, so as operators from the loco channels are easily recognized and able to be found in a simple and timely manner. Discussion here: - == Usage of +v in #ubuntu-ops and #ubuntu-irc == There has been some thought that perhaps it would be better that only operators who are available make themselves +v, so when a person enters #ubuntu-ops/-irc they can quickly see who is actually available to sort out their query. This point is very open for discussion, so points here: - All these points will be discussed at the next IRCC meeting. Thank you. |
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)