nickrud | yes, a more codified way of handling bans among the various operators | 00:00 |
---|---|---|
nickrud | not looking for a resolution, but something that I think is a pressing issue for the future | 00:00 |
nalioth | nickrud: do you mean "ban resolution" or "ban setting" ? | 00:00 |
elkbuntu | something more than the bantracker? | 00:00 |
nalioth | i 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 BT | 00:01 |
nickrud | resolution. 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 zones | 00:01 |
elkbuntu | nalioth, even for repeat/chronic offenders? | 00:02 |
Flannel | elkbuntu: Those should have comments in the bantracker | 00:02 |
nickrud | that issue of repeaters has crossed my mind, so it's no simple matter to find a reasonably flexible but fair mechanism | 00:03 |
jussi01 | Ok, im off to bed, Ill catch up on backlog in the morning, nini all | 00:03 |
elkbuntu | Flannel, those usually have a huge-ass list in the ban tracker of prior bans/removes | 00:03 |
nalioth | elkbuntu: repeat offenders will be commented at some time in their pasts, i'd presume and should come up in a BT search | 00:03 |
nickrud | I'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 scheme | 00:04 |
nickrud | or informal, but a scheme none the less | 00:05 |
nalioth | nickrud: do we see a wiki page somewhere from you on this? | 00:05 |
nickrud | nalioth not yet. I'm still scratching my head. I find good reasons not to do whatever I think up. | 00:05 |
elkbuntu | it is worth trying, but i do warn against blindly unbanning people just becuase they have no comment. | 00:06 |
nalioth | elkbuntu: a single entry into the BT usually indicates no prior history | 00:06 |
PriceChild | Everyone comment on the bt more! :) | 00:06 |
nickrud | I think a good first step is simply commenting. And noting in the comment that it's ok to unban. | 00:06 |
elkbuntu | agreed | 00:07 |
nickrud | no ok, no unban | 00:07 |
nalioth | not 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 |
Pici | The 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 |
nickrud | Pici only with explicit prior permission in the bt | 00:08 |
nalioth | Pici: that has never been a hard rule, it's just come to be "the way things are" | 00:08 |
elkbuntu | Pici, that one should really only be enforced for repeat offenders | 00:09 |
nickrud | I'm suggesting that, anyway | 00:09 |
Pici | Agreed | 00:09 |
PriceChild | I 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 commas | 00:10 | |
nalioth | somethign like dircbot, anyway | 00:10 |
nalioth | okay, any other business? | 00:10 |
elkbuntu | couldnt it just be hacked into our current frankenstein? | 00:10 |
nalioth | elkbuntu: that option is available to us | 00:10 |
elkbuntu | nalioth, one other item. retrieving the name ubotu. | 00:11 |
nalioth | we wouldn't be using dircbot, but a clone thereof | 00:11 |
elkbuntu | is it at all possible/is seveas willing to part with it? | 00:11 |
nalioth | seveas is still active in #ubuntu, why not ask him? | 00:11 |
elkbuntu | it gets asked of -ops several times a week, but i havent had time to annoy him abou tit | 00:12 |
nalioth | we chose the bot names we have for ease of <tab-complete> | 00:12 |
nalioth | but it would be nice to get the other nick(s) back | 00:12 |
Flannel | ubotu 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 stuffs | 00:13 |
nalioth | Flannel: yes, but that wouldn't be very friendly | 00:13 |
elkbuntu | Seveas, is also here in this channel. maybe he could volunteer to discuss with the ops team at a later time | 00:13 |
Pici | Right, but it would be courteous to talk to him about it | 00:13 |
Flannel | nalioth: no, which is why I said it was in case it fell through | 00:14 |
nalioth | Flannel: noted | 00:14 |
nalioth | anything else on anyones plate? | 00:14 |
PriceChild | Great well that's it then. | 00:18 |
PriceChild | Will 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 | @now | 16:41 |
ubottu | boredandblogging: Current time in Etc/UTC: July 20 2008, 15:41:11 - Next meeting: Asia and Oceania Ubuntu Membership Approval Board in 1 day | 16:41 |
Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!