IrcOperatorMeetingAgenda

Differences between revisions 2 and 15 (spanning 13 versions)
⇤ ← Revision 2 as of 2006-12-20 17:38:22 →
Size: 588
Editor: 87-194-86-227
Comment:
← Revision 15 as of 2007-01-29 16:22:36 → ⇥
Size: 1219
Editor: 87-194-86-227
Comment: adding note about channel location
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
The IRC ops meeting will be at dec. 20, 18:00 UTC The IRC ops meeting will be at Jan. 30, 21:00 UTC in #ubuntu-ops NOT #ubuntu-meeting (as the TB meeting will not be finished in time)
Line 5: Line 5:
 * Operator guidelines
  * Kick/ban/abuse policy
  * "Op wars"
 * #ubuntu-ops policy
  * Appeal process
  * Keep it private?
  * Logging?
 * Channel access policy
  * "Leads" for derivatives should have level 30
  * Who are the leads?
 * IRC Council
  * Paul has left, the vacancy needs to be filled
  * Nominations now, voting on the mailinglist
  * Transparency in meetings?
 * Bots
  * more people with control access
  * Bantracker logs public?
 * ubuntu/member/ cloaks
 * Any other issues		  * Nominations (and hopefully vote) for the IRC council
  * ''Please add yourself as nominee here if you want to join the council''
  * I'm willing to undertake this, but will be unable to attend this meeting. -- MelissaDraper (elkbuntu)
  * Lorenzo J. Lucchini (LjL)
 * Which processes should really be written down?
  * Appointing operators
  * Dealing with abuse from operators
  * Rewording/adding Guidelines to https://wiki.ubuntu.com/IrcGuidelines seeing as we have new ops coming on and maybe they are not sure exactly what to do or how to do it. the past few months there has been alot of ops not agreeing with ops, and i think it needs to end.
  * Ops removing other ops bans.
 * Regularity of discussion
  * Do we want to have IRC meetings like this scheduled regularly regardless of obvious concerns, or a monthly e-mail asking for feedback, or anything like that?
 * Technical issues
  * Guidelines (note ''guidelines'', as in "help us know what to do") for dealing with attacks - a.k.a. "when +rR ain't enough". +mz? +J? Smart bots?

The IRC ops meeting will be at Jan. 30, 21:00 UTC in #ubuntu-ops NOT #ubuntu-meeting (as the TB meeting will not be finished in time)

Points to discuss:

  • Nominations (and hopefully vote) for the IRC council

    • Please add yourself as nominee here if you want to join the council

    • I'm willing to undertake this, but will be unable to attend this meeting. -- MelissaDraper (elkbuntu)

    • Lorenzo J. Lucchini (LjL)
  • Which processes should really be written down?
    • Appointing operators
    • Dealing with abuse from operators

    • Rewording/adding Guidelines to https://wiki.ubuntu.com/IrcGuidelines seeing as we have new ops coming on and maybe they are not sure exactly what to do or how to do it. the past few months there has been alot of ops not agreeing with ops, and i think it needs to end.

    • Ops removing other ops bans.
  • Regularity of discussion
    • Do we want to have IRC meetings like this scheduled regularly regardless of obvious concerns, or a monthly e-mail asking for feedback, or anything like that?
  • Technical issues

    • Guidelines (note guidelines, as in "help us know what to do") for dealing with attacks - a.k.a. "when +rR ain't enough". +mz? +J? Smart bots?

IrcOperatorMeetingAgenda (last edited 2008-08-06 16:29:27 by localhost)