/srv/irclogs.ubuntu.com/2008/07/20/#ubuntu-meeting.txt

nickrudyes, a more codified way of handling bans among the various operators00:00
nickrudnot looking for a resolution, but something that I think is a pressing issue for the future00:00
naliothnickrud: do you mean "ban resolution" or "ban setting" ?00:00
elkbuntusomething more than the bantracker?00:00
naliothi personally think that if the op hasn't commented the bantracker, his/her bans should be able to be released after 24h by by any op with access to the BT00:01
nickrudresolution. Ban tracker is good, but no one ever comments about grounds for unbanning, if the op is not around. And I've seen more than a handful of bans placed by people in conflicting time zones00:01
elkbuntunalioth, even for repeat/chronic offenders?00:02
Flannelelkbuntu: Those should have comments in the bantracker00:02
nickrudthat issue of repeaters has crossed my mind, so it's no simple matter to find a reasonably flexible but fair mechanism00:03
jussi01Ok, im off to bed, Ill catch up on backlog in the morning, nini all00:03
elkbuntuFlannel, those usually have a huge-ass list in the ban tracker of prior bans/removes00:03
naliothelkbuntu: repeat offenders will be commented at some time in their pasts, i'd presume and should come up in a BT search00:03
nickrudI'm definitely not a good bt commenter myself so I can't point at anyone else. But I think it would be a good move for us to start being more consistent about it. Then we'll have more data to mash about while we try to work out some formal scheme00:04
nickrudor informal, but a scheme none the less00:05
naliothnickrud: do we see a wiki page somewhere from you on this?00:05
nickrudnalioth not yet. I'm still scratching my head. I find good reasons not to do whatever I think up.00:05
elkbuntuit is worth trying, but i do warn against blindly unbanning people just becuase they have no comment.00:06
naliothelkbuntu: a single entry into the BT usually indicates no prior history00:06
PriceChildEveryone comment on the bt more! :)00:06
nickrudI think a good first step is simply commenting. And noting in the comment that it's ok to unban.00:06
elkbuntuagreed00:07
nickrudno ok, no unban00:07
naliothnot sure if any of you are familiar with dircbot, but if there is enough interest, perhaps we could do something like that ( iow, you tell the bot your reason for bannning at the time )00:08
PiciThe rule used to be for operators who banned someone to be the person to deal with their unbanning, are we dismissing that rule?00:08
nickrudPici only with explicit prior permission in the bt00:08
naliothPici: that has never been a hard rule, it's just come to be "the way things are"00:08
elkbuntuPici, that one should really only be enforced for repeat offenders00:09
nickrudI'm suggesting that, anyway00:09
PiciAgreed00:09
PriceChildI think dircbot would be good, and would like to try it out, its quite good at making you add comments so things make sense(ish).00:10
* PriceChild removes some commas00:10
naliothsomethign like dircbot, anyway00:10
naliothokay, any other business?00:10
elkbuntucouldnt it just be hacked into our current frankenstein?00:10
naliothelkbuntu: that option is available to us00:10
elkbuntunalioth, one other item. retrieving the name ubotu.00:11
naliothwe wouldn't be using dircbot, but a clone thereof00:11
elkbuntuis it at all possible/is seveas willing to part with it?00:11
naliothseveas is still active in #ubuntu, why not ask him?00:11
elkbuntuit gets asked of -ops several times a week, but i havent had time to annoy him abou tit00:12
naliothwe chose the bot names we have for ease of <tab-complete>00:12
naliothbut it would be nice to get the other nick(s) back00:12
Flannelubotu hasn't logged in for 11 weeks, so even if he doesn't agree, we can technically take the nick back through regular freenode nick stuffs00:13
naliothFlannel: yes, but that wouldn't be very friendly00:13
elkbuntuSeveas, is also here in this channel. maybe he could volunteer to discuss with the ops team at a later time00:13
PiciRight, but it would be courteous to talk to him about it00:13
Flannelnalioth: no, which is why I said it was in case it fell through00:14
naliothFlannel: noted00:14
naliothanything else on anyones plate?00:14
PriceChildGreat well that's it then.00:18
PriceChildWill get the email sorted, and try to sort out a meeting for in 2 weeks or so, announce it earlier and yes :)00:19
=== ubottu changed the topic of #ubuntu-meeting to: Calendar: http://fridge.ubuntu.com/event | Logs: https://wiki.ubuntu.com/MeetingLogs/ | 22 Jul 11:00 UTC: Asia and Oceania Ubuntu Membership Approval Board | 22 Jul 15:00 UTC: Server Team | 22 Jul 18:00 UTC: LoCo Council | 23 Jul 17:00 UTC: QA Team | 23 Jul 22:00 UTC: Platform Team | 24 Jul 13:00 UTC: Desktop Team
=== nealmcb1 is now known as nealmcb
=== asac_ is now known as asac
=== mc44_ is now known as mc44
=== mc44_ is now known as mc44
boredandblogging@now16:41
ubottuboredandblogging: Current time in Etc/UTC: July 20 2008, 15:41:11 - Next meeting: Asia and Oceania Ubuntu Membership Approval Board in 1 day16:41

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!