[11:01] <topyli> ircc meeting. jussi nhandler tsimpson elky?
[11:01] <elky> \o
[11:02] <tsimpson> o/
[11:02] <jussi> o/
[11:02] <topyli> it's probably not nhandler's best hour
[11:02] <jussi> He said he wouldnt be here
[11:02] <elky> He already notified he'd be asleep
[11:03] <topyli> aye
[11:03] <topyli> #startmeeting
[11:03] <meetingology> Meeting started Sat Aug 13 11:03:18 2011 UTC.  The chair is topyli. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[11:03] <meetingology> Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting.
[11:03] <topyli> https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[11:03] <jussi> Remeber this is a different bot
[11:04] <topyli> #link https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda
[11:04] <topyli> grr. i blame the bot
[11:04] <topyli> did we have any actions from last time?
[11:05] <topyli> we didn't
[11:05] <jussi> not that I see
[11:05] <tsimpson> we do have the previous-previous actions
[11:05] <jussi> still have this bug open: https://bugs.launchpad.net/ubuntu-community/+bug/788503
[11:06] <jussi> tsimpson: which were?
[11:06] <tsimpson> that bug :)
[11:06] <topyli> is it still in progress?
[11:06] <tsimpson> it stalled
[11:07] <elky> howso?
[11:08] <tsimpson> in that all activity on it seems to have stopped
[11:08] <elky> you volunteering to chase up on those who were contributing?
[11:08] <tsimpson> m4v posted an sample draft, but that's about it
[11:08] <tsimpson> https://launchpadlibrarian.net/72478406/guidelines_example_m4v.txt
[11:09] <jussi> So any ideas on making this go forward? is it just someone needs to go do the work? or?
[11:09] <topyli> oh i meant to study that but i forgot all about it. bad topyli
[11:09] <elky> i volunteer topyli then :P
[11:10] <topyli> i could see what m4v's draft changes and if it's good. i can action that and report in the next meeting
[11:11] <topyli> does that sound sane?
[11:11] <jussi> Ill work with you on that if you like
[11:12] <topyli> i would. won't hurt to have more eyeballs, it's a rather important document
[11:12] <topyli> #action topyli and jussi to review m4v's guidelines draft
[11:12] <meetingology> ACTION: topyli and jussi to review m4v's guidelines draft
[11:13] <topyli> #topic Add eir to #ubuntu
[11:13] <meetingology> TOPIC: Add eir to #ubuntu
[11:13] <topyli> tsimpson: you know how this is going :)
[11:13] <jussi> Peoples, Im real sorry, I need to run. Something has just come up.
[11:13] <elky> whaaa...
[11:14] <tsimpson> it's basically ready
[11:14]  * elky points at the topic vandalism. bad bot, bad
[11:14] <topyli> elky: oh good point, need to change that before ending the meeting
[11:15] <topyli> tsimpson: i haven't been following this very well either. is it in testing as planned?
[11:15] <tsimpson> looks like it changes it back at the end of the meeting
[11:15] <topyli> ah
[11:15] <elky> it probably shouldnt' change at all in this channel...
[11:15] <tsimpson> topyli: nhandler and I have tested it, the worst way it can fail is that comments aren't added to the BT
[11:16] <tsimpson> we were hoping for more people to test it out, but testers didn't materialize
[11:16] <tsimpson> still, I think it's generally usable
[11:17] <topyli> maybe just go ahead and put it to real life testing in #ubuntu, monitor it and see whether or not it works?
[11:17] <topyli> if it fails dramatically, we should notice it in a matter of hours
[11:17] <tsimpson> that's the plan
[11:18] <tsimpson> as I say though, it really can't disrupt anything
[11:18] <topyli> yeah, but not having BT comments would be a regression. which we'll notice
[11:19] <topyli> it's not hard to pull it back if necessary, is it?
[11:19] <tsimpson> no, only the comments directed to eir would not be added
[11:19] <jussi> right, Im back
[11:19] <tsimpson> people can still use @comment or the web interface
[11:19] <topyli> ahh
[11:20] <topyli> jussi: quick work, whatever it was :)
[11:20] <jussi> the emeergency that wasnt
[11:20] <elky> the best kind of emergency
[11:21] <jussi> anyway, I say we make the announcement and put eir in.
[11:22] <tsimpson> we already announced that it was planned, we just need to pick a date and announce that
[11:22] <jussi> Monday :) then most people are around.
[11:22] <topyli> yes. how soon can you manage it?
[11:23] <tsimpson> whenever, I just need to change some @config values
[11:23] <tsimpson> (it's already in ubottu, just not enabled in #ubuntu etc)
[11:23] <tsimpson> and we'd need to actually get eir in #ubuntu and -ops-team
[11:23] <jussi> So any probs then with  monday morning, tsimpson time?
[11:24] <topyli> monday would give us time to announce it, i'm for it
[11:24] <tsimpson> we need to actually teach people how to use eir too
[11:25] <jussi> Maybe we could run a session or 2 on that
[11:25] <tsimpson> and probably explain exactly what we want to use it for
[11:25] <jussi> put the logs somewhere
[11:25] <tsimpson> I think some people think it's replacing the ban tracker
[11:26] <topyli> i've noticed that too
[11:26] <topyli> so maybe monday is too soon? should we give it a week still?
[11:27] <tsimpson> I think the opposite ;)
[11:27] <elky> i'd give it until the docs are done.
[11:27] <jussi> mind, this could be explained in the announcement
[11:27] <topyli> jussi: true
[11:27] <tsimpson> put eir in there, so people can play with it
[11:27] <jussi> docs are done already
[11:28] <tsimpson> docs are available on http://freenode.net/eir.shtml
[11:28] <tsimpson> it just takes a little getting used to
[11:28] <jussi> Im still well in favour of monday, if tsimpson can get the announcement written by then
[11:29] <tsimpson> I'd like to collaborate with nhandler on it too, he's the resident eir guru
[11:29] <topyli> the confidence level here suggests i should agree :)
[11:29] <elky> i'm more interested in everyone being prepared for it.
[11:30] <elky> rather than how fast we can get the shiny toy
[11:30] <tsimpson> there's not a lot to prepare for, all the eir commands are post-action
[11:30] <tsimpson> so ops can still act as before, eir is just an add-on
[11:30] <topyli> people can work as they always have, as i understand this eir doesn't take anything away
[11:30] <IdleOne> add the bot to the channel and let's get to it.
[11:30] <IdleOne> we can learn on our feet
[11:30] <IdleOne> MHO
[11:31] <elky> then can we vote or whatever rather than this
[11:31] <tsimpson> all ops need to remember, is to communicate with eir in #ubuntu-ops-team rather than in private (so ubottu can pick up the comments)
[11:31] <topyli> "MHCO, my humble but corrrect opinion"
[11:31] <jussi> IdleOne: I agree. it isnt going to affect much if people dont know it yet, they will learn on the fly.
[11:31] <IdleOne> +1
[11:33] <topyli> elky: object to tsimpson making the announcement and going ahead with on monday?
[11:33] <elky> nope
[11:33] <topyli> alright, no vote
[11:33] <tsimpson> we already voted for it anyway, this is just the implementation
[11:33] <elky> any other business?
[11:34] <topyli> #action tsimpson to announce and enable eir in #ubuntu
[11:34] <meetingology> ACTION: tsimpson to announce and enable eir in #ubuntu
[11:34] <topyli> looks like we're done then
[11:35] <topyli> #endmeeting
[11:35] <meetingology> Meeting ended Sat Aug 13 11:35:05 2011 UTC.  Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot . (v 0.1.4)
[11:35] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-13-11.03.moin.txt
[11:35] <elky> excellent
[11:35] <topyli> oh look, it did the change the topic
[11:35] <elky> can someone see if that topic changey business can be stopped for this channel?
[11:35] <topyli> i'll do the post-meeting stuff as per custom :)
[11:36] <elky> i suppose i should ping AlanBell for it.
[11:36] <elky> anyway, ciao
[11:36] <topyli> i don't know how bad that is anyway. the topic being discussion might as well be in the topic. why not?
[11:37] <tsimpson> I tend to agree
[11:37] <jussi> Its designed like that, and I kinda like it. It outs the old toopic back after the meeting
[11:37] <elky> i don't think it's quite appropriate for /this/ channel.
[11:37] <topyli> i also gasped a little at first, but since it does the right thing after the meeting...
[11:37] <jussi> If anything, it should prefix with which meeting is going on.
[11:38] <topyli> oh yes
[11:40] <topyli> anyway, got to go and finance wallet-losing wife's affairs, and mock her
[11:41] <tsimpson> topyli: and do the post-meeting tasks ;)
[11:41] <topyli> i'll get them done today :)
[18:49] <AlanBell> the idea with the topic is it should attempt to change the /topic and if that doesn't work it should speak in the channel
[18:49] <AlanBell> at the moment it does both
[18:50] <AlanBell> so both is redundant and is a bug, I can stop it doing the /topic, but personally I would rather stop it talking
[18:50] <Mkaysi> AlanBell: Are there any channel for meetingology (development) ? :)
[18:51] <AlanBell> in general it should not say anything, unless it has something useful to say
[18:51] <AlanBell> #ubuntu-bots probably
[18:51] <AlanBell> or find me somewhere
[18:52] <Mkaysi> Ok
[18:52] <Mkaysi> But you aren't at #ubuntu-bots
[18:53] <AlanBell> I have a bad connection at the moment so culled my channel list to prevent annoying people
[18:53] <Mkaysi> Ok
[18:54] <AlanBell> elky: clearly opinion is divided on the /topic changing feature, would that be an IRC council agenda topic to decide?
[18:58] <AlanBell> and yes, it should prefix the meeting title, I think there might be some not-quite-implemented code to do exactly that
[18:58] <AlanBell> the code is all designed and debugged, all I have to do is type it in