#title #ubuntu-meeting Meeting Meeting started by topyli at 11:03:18 UTC. The full logs are available at http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-08-13-11.03.log.html . == Meeting summary == ''LINK:'' https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda (topyli, 11:03:26) ''LINK:'' https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda (topyli, 11:04:08) ''LINK:'' https://launchpadlibrarian.net/72478406/guidelines_example_m4v.txt (tsimpson, 11:08:55) ''ACTION:'' topyli and jussi to review m4v's guidelines draft (topyli, 11:12:55) *Add eir to #ubuntu ''ACTION:'' tsimpson to announce and enable eir in #ubuntu (topyli, 11:34:00) Meeting ended at 11:35:05 UTC. == Votes == == Action items == * topyli and jussi to review m4v's guidelines draft * tsimpson to announce and enable eir in #ubuntu == Action items, by person == * jussi ** topyli and jussi to review m4v's guidelines draft * topyli ** topyli and jussi to review m4v's guidelines draft * tsimpson ** tsimpson to announce and enable eir in #ubuntu == People present (lines said) == * topyli (36) * tsimpson (31) * jussi (18) * elky (13) * meetingology (5) * IdleOne (4) * ubottu (1) == Full Log == 11:03:18 #startmeeting 11:03:18 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:18 Useful Commands: #topic #action #link #idea #voters #vote #chair #action #agreed #help #info #endmeeting. 11:03:26 https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda 11:03:52 Remeber this is a different bot 11:04:08 #link https://wiki.ubuntu.com/IRC/IrcCouncil/MeetingAgenda 11:04:21 grr. i blame the bot 11:04:48 did we have any actions from last time? 11:05:22 we didn't 11:05:23 not that I see 11:05:41 we do have the previous-previous actions 11:05:51 still have this bug open: https://bugs.launchpad.net/ubuntu-community/+bug/788503 11:05:53 Ubuntu bug 788503 in ubuntu-community "IRC Guidelines too #ubuntu centric" [Undecided,In progress] 11:06:05 tsimpson: which were? 11:06:12 that bug :) 11:06:15 is it still in progress? 11:06:29 it stalled 11:07:46 howso? 11:08:01 in that all activity on it seems to have stopped 11:08:24 you volunteering to chase up on those who were contributing? 11:08:26 m4v posted an sample draft, but that's about it 11:08:55 https://launchpadlibrarian.net/72478406/guidelines_example_m4v.txt 11:09:29 So any ideas on making this go forward? is it just someone needs to go do the work? or? 11:09:33 oh i meant to study that but i forgot all about it. bad topyli 11:09:46 i volunteer topyli then :P 11:10:38 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:32 does that sound sane? 11:11:34 Ill work with you on that if you like 11:12:15 i would. won't hurt to have more eyeballs, it's a rather important document 11:12:55 #action topyli and jussi to review m4v's guidelines draft 11:12:55 * meetingology topyli and jussi to review m4v's guidelines draft 11:13:17 #topic Add eir to #ubuntu 11:13:17 TOPIC: Add eir to #ubuntu 11:13:39 tsimpson: you know how this is going :) 11:13:55 Peoples, Im real sorry, I need to run. Something has just come up. 11:13:56 whaaa... 11:14:02 it's basically ready 11:14:09 * elky points at the topic vandalism. bad bot, bad 11:14:36 elky: oh good point, need to change that before ending the meeting 11:15:19 tsimpson: i haven't been following this very well either. is it in testing as planned? 11:15:22 looks like it changes it back at the end of the meeting 11:15:30 ah 11:15:40 it probably shouldnt' change at all in this channel... 11:15:59 topyli: nhandler and I have tested it, the worst way it can fail is that comments aren't added to the BT 11:16:36 we were hoping for more people to test it out, but testers didn't materialize 11:16:44 still, I think it's generally usable 11:17:29 maybe just go ahead and put it to real life testing in #ubuntu, monitor it and see whether or not it works? 11:17:45 if it fails dramatically, we should notice it in a matter of hours 11:17:55 that's the plan 11:18:16 as I say though, it really can't disrupt anything 11:18:58 yeah, but not having BT comments would be a regression. which we'll notice 11:19:09 it's not hard to pull it back if necessary, is it? 11:19:15 no, only the comments directed to eir would not be added 11:19:19 right, Im back 11:19:24 people can still use @comment or the web interface 11:19:27 ahh 11:20:00 jussi: quick work, whatever it was :) 11:20:24 the emeergency that wasnt 11:20:36 the best kind of emergency 11:21:07 anyway, I say we make the announcement and put eir in. 11:22:13 we already announced that it was planned, we just need to pick a date and announce that 11:22:35 Monday :) then most people are around. 11:22:45 yes. how soon can you manage it? 11:23:08 whenever, I just need to change some @config values 11:23:15 (it's already in ubottu, just not enabled in #ubuntu etc) 11:23:52 and we'd need to actually get eir in #ubuntu and -ops-team 11:23:53 So any probs then with monday morning, tsimpson time? 11:24:20 monday would give us time to announce it, i'm for it 11:24:54 we need to actually teach people how to use eir too 11:25:12 Maybe we could run a session or 2 on that 11:25:15 and probably explain exactly what we want to use it for 11:25:19 put the logs somewhere 11:25:29 I think some people think it's replacing the ban tracker 11:26:10 i've noticed that too 11:26:41 so maybe monday is too soon? should we give it a week still? 11:27:13 I think the opposite ;) 11:27:15 i'd give it until the docs are done. 11:27:15 mind, this could be explained in the announcement 11:27:23 jussi: true 11:27:24 put eir in there, so people can play with it 11:27:25 docs are done already 11:28:03 docs are available on http://freenode.net/eir.shtml 11:28:18 it just takes a little getting used to 11:28:31 Im still well in favour of monday, if tsimpson can get the announcement written by then 11:29:19 I'd like to collaborate with nhandler on it too, he's the resident eir guru 11:29:20 the confidence level here suggests i should agree :) 11:29:46 i'm more interested in everyone being prepared for it. 11:30:02 rather than how fast we can get the shiny toy 11:30:07 there's not a lot to prepare for, all the eir commands are post-action 11:30:25 so ops can still act as before, eir is just an add-on 11:30:32 people can work as they always have, as i understand this eir doesn't take anything away 11:30:39 add the bot to the channel and let's get to it. 11:30:47 we can learn on our feet 11:30:52 MHO 11:31:19 then can we vote or whatever rather than this 11:31:20 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:23 "MHCO, my humble but corrrect opinion" 11:31:37 IdleOne: I agree. it isnt going to affect much if people dont know it yet, they will learn on the fly. 11:31:46 +1 11:33:03 elky: object to tsimpson making the announcement and going ahead with on monday? 11:33:10 nope 11:33:23 alright, no vote 11:33:47 we already voted for it anyway, this is just the implementation 11:33:47 any other business? 11:34:00 #action tsimpson to announce and enable eir in #ubuntu 11:34:00 * meetingology tsimpson to announce and enable eir in #ubuntu 11:34:57 looks like we're done then 11:35:05 #endmeeting Generated by MeetBot 0.1.4 (http://wiki.ubuntu.com/AlanBell/mootbot)