/srv/irclogs.ubuntu.com/2010/10/12/#ubuntu-meeting.txt

lifelesspersia: do we have a meeting tonight?08:07
nigelblifeless: as per wiki, seems like you do08:29
persialifeless, I believe so.09:28
lifelesshi10:08
elkyhi10:08
persiaHi.  You live in a benighted realm that believes that sunrise should happen after sensible people are already awake.  Wait an hour.10:09
persiaOr did something change that I missed?10:09
lifelesswiki page says 1000 utc10:11
nigelb@now10:11
ubottuCurrent time in Etc/UTC: October 12 2010, 09:11:5610:11
lifelessis gnome lying to me about time in london ?10:11
persiaRight, and it's 9:00 UTC10:11
lifelessblah10:12
nigelbheh10:12
* lifeless stabs gnome10:12
persiaTime in London doesn't matter.  time in Reykjavik is more interesting.10:12
persiaLondon is part of one of the benighted realms above-mentioned.10:12
nigelbWhen does DST change, last sunday of this month?10:13
lifelessnigelb: I'm already on DST10:15
lifelessso, bleh, this meeting will be @ 11pm.10:15
nigelbheh10:15
persianigelb, Randomly, in abitrary directions, depending on the whim of the governments for the area.  I think the worst was once when a government decided on a Friday that DST started that weekend.10:16
persiaIf you want gory and amusing details, read the tzdata changelog.10:16
lifelessyou can blame NZ for this10:17
nigelbEeek, no thanks10:17
elkyI should probably find some food before this reprieve ends.10:18
* persia remembers one morning having to reschedule a conference call because DST happened in different directions on the same day in the areas where all the participants sat.10:18
persia(and, annoyingly, ending up with a 5am call in Sydney as a result)10:18
nigelbI think this month is going to be generally confusing for meetings10:19
nigelbSomeone should tack that on the /topic10:19
nigelbright, its already there :)10:19
lifelessmmm10:23
lifelessI may not make it10:23
* elky munches and waits.10:45
Mohan_chml@now10:53
ubottuCurrent time in Etc/UTC: October 12 2010, 09:53:5610:53
persiaMohan_chml, Soon.10:54
Mohan_chmlpersia: yeah :)10:54
persiaGood evening Vantrax11:00
persiaSo, um, it's 10:05.  Who is present?  Do we have quorum?11:05
lifelessI'm here for a few minutes; really just a few.11:05
persiaogitux seems not here yet, so we may not have that much business before us.11:06
Mohan_chmlyes. His wiki seems not updated with details11:06
elkyshall we take the moments until he arrives to discuss board population?11:06
persiaSure.11:07
Vantraxyep11:08
elky#startmeeting11:08
MootBotMeeting started at 05:08. The chair is elky.11:08
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]11:08
elkyWoo, I remembered!11:08
elky[TOPIC] Board members11:08
MootBotNew Topic:  Board members11:08
Vantraxnice work:P11:08
VantraxI have seen 4 apps total.11:09
persiaAnd our target is still 9 total members, 3 east, 3 central, and 3 west, right?11:09
Vantraxdo we hand that to CC or go back again and ask for more11:10
VantraxI think its 811:10
Vantrax 11:10
Vantraxerr we have 811:10
persiaRight.  We got one more last time we talked about this, but never the other one, and never moved to split meetings.11:10
Vantraxand 12 was the goal with 2 meetings and 4 for quorum still11:11
elkyI'm rather eager to avoid holding this up unnecessarily.11:11
Vantraxwe are still going to have a numbers issue atm11:11
persia12!  That's larger than I think we need, especially with a quorum of 4.  I'm not precisely happy about assuming most folk won't show up.11:11
Vantraxwe have 8 right now afaik11:12
elkyYeah, that worries me too.11:12
Vantraxwe struggle to get 411:12
elkyWe're still in the rut where it's always the same few who show up.11:12
Vantraxyep11:12
persiaVantrax, yes, but the question is: do we need the folk that don't show?11:13
Vantraxprobably not11:13
* persia would rather have a smaller board that was mostly present: people who only show once every few months are hard to trust11:13
Vantrax we have the same four each time normally11:13
persiaRight.11:14
Vantraxwith amachu and takdir making it intermittantly11:14
persiaSo, let's look at distribution.11:14
persialifeless is *way* east.  elky is east.  I'm central.  Vantrax: I forget if you're east or central?11:14
VantraxI'm east, in brisbane11:15
lifelessI'm so far east, ATM, that I'm really west.11:15
Vantraxlol11:15
lifeless(UTC+13)11:15
persialifeless, For our purposes, that's merely east, when far-west is still +5:3011:16
persiaOK, so we need some central and west.11:16
Vantraxyep, we can safely assume people can make this time11:16
persiaRight.  Let's take the position we don't need anyone else to the east.11:17
elkyCentral is historically where we've had retention issues.11:17
persiaLet's ask the current members that don't show if they want to remain on the board.11:17
elkyMay I suggest that's the wrong question?11:17
VantraxI'm happy with that asumption elky11:18
persiaAnd let's send the list of new nominees and commonly-missing members to the CC as two separate groups, "central" and "west" and ask them to select two central and three west.11:18
Vantraxexcellent idea11:18
persiaelky, What's a better question, assuming that we're not guaranteeing them a continued spot regardless of their answer?11:18
elkypersia, I'm more inclined to ask if they're able, rather than if they're willing.11:18
VantraxI think we should ask what they want11:19
persiaelky, That's a *much* better question.  Good call.11:19
persiaVantrax, As someone who is rarely able to do the set of things I want, I'll say that's dangerous.11:19
lifelessagreed11:20
Vantraxif they can't fulfil the obligation they resign11:20
Vantraxthat is my opinion11:20
elkyVantrax, easily spoken in theory. Harder to actualy do.11:20
elkyNoting that when asking if they're able that we'd be specifying *both* times.11:21
Vantraxyep, I'm pretending its a perfect world11:21
persiaNo, we're not asking that people can make both times.11:21
persiaWe're asking that central people can make both times and western people can make the later time.11:22
elkypersia, we're asking them if they can make at least one of the times.11:22
persiaOK.11:22
persiaI just want to make sure we're not asking our sometimes-present western member to attend the earlier time at which lifeless hasn't already fallen asleep.11:23
Vantraxare we looking at three or two meetings?11:23
persiaTwo ought be enough.11:23
VantraxI agree, was just checking11:23
persiaIf we were doing three meetings, we'd not have enough coherency, and I'd argue we ought to split into an "Asia" board and an "Oceania" board.11:23
VantraxI think 2 should be good coverage11:24
lifelessspeaking of which. ciao.11:24
Vantraxnight champ11:24
elkylifeless, thanks for coming, ciao11:24
Vantraxso we have the same continuing problem11:26
elkyWe do. We've had it since the inception of the RMB.11:26
elkyWe get closer to solving it each time.11:26
Mohan_chmlo/11:26
persiaThat's the point of going from the original 7 to 9 members and splitting the meeting.11:26
Mohan_chmlcan I have a minute?11:26
persiaWe're up to 8 and have 4 regulars, which beats the 3 regulars we had at one point.11:26
Vantraxhello mohi11:26
elkypersia, yep. Improvements have been achieved.11:27
Vantraxtrue, we make quorum usually, even if I'm on my phone like today11:27
persiaSo, Everyone feel good about the plan I've outlined above?11:27
Mohan_chmlwhat about starting an IRC channel for Asia/Ociania memebers and analysing their presence at the time of meeting before making them as an RMB?11:27
Mohan_chmlHola Vantrax =]11:28
persiaMohan_chml, Doesn't help.  I'm often around at this time, but my join/part messages wouldn't even begin to help anyone know that.11:28
Vantraxhrm, not a bad idea11:28
elkyMohan_chml, or they could just attend the meetings like now.11:28
Mohan_chmlelky: that is also acceptable11:28
VantraxI would think people wanting to join would turn up to meetings as elky said11:28
elkyMohan_chml, then consider it already in action ;)11:29
Mohan_chml(:11:29
Mohan_chmlMy suggestion is, Lets make a single meeting for next two times, see the presence of the applicants and their skill of Judging, then making the meeting as two11:30
Vantraxmohi, we don't have enough applicants11:30
Mohan_chmlah..!11:31
nigelbah, a bit of arm twisting required to get more people to apply? :)11:31
Vantraxyep11:31
persiaVantrax, Are you up for taking an action to contact the often-missing members and get them to say whether they'd be able to make one of the new meeting times?11:32
persia(8:00 and 12:00, weren't they?)11:32
Vantraxyes, ill do that and report back11:32
persiaAnyone *not* on the Asia/Oceania RMB who would like to be, or anyone who thinks someone else should be (and has confirmed that person *can*) should also contact the RMB.11:33
VantraxI think it was 0900 and 1200 UTC11:33
persiaIf both those actions complete for next time, we'll be able to ask the CC to give us the new members, and we can meet at the new times.11:33
Vantraxyes, ill get something in the fridge11:34
persia9:00 is still late in +14, but I don't think we have anyone further east than +13 in practice.11:34
Vantraxmaybe we will have more luck11:34
VantraxI rarely get home before 7pm aest11:35
Vantraxtoo much earlier and ill be doing all meetings on a phone:D11:35
persiaAh, so 9:00 is about as early as works.  OK.  9:00 then.11:36
persianigelb, As someone in IST, do you think 12:00 is late enough for your compatriots?  Does it need to be a bit later?11:36
Vantraxearlier?11:37
persiaVantrax, Just to confirm, AE{SD}T varies between +10 and +11, right?11:37
persiaVantrax, I'm not expecting anyone "east" to attend the later meeting :)11:37
Vantraxnot for me, but yes11:37
nigelbpersia: hold on, let me calculate that.11:38
Vantraxthe southern half use daylight savings11:38
elkyHow does the later time pan out for muslim prayer time, too. I know it's been an issue for some in SE Asia previously.11:38
nigelb12:00 UTC is 17:30 local time, which is okay.11:39
* persia looks up relevant prayer schedules11:39
elkynigelb, isn't that commute time?11:39
nigelbelky: varies, commute time is an hour more from then11:40
Vantraxgood point elky11:40
nigelb9:30 to 6:30 is normal office timings (at least in this city)11:40
persiaelky, We can't win for that.  "Sunset" and "evening" are always likely to collide a bit, unless we make it very late indeed.11:40
elkypersia, yeah I figured. Most of the muslim nations I think get a fair crack at EMEA anyway.11:41
persiaLooks like sunset in our region can be as late as 13:4211:41
persia(for 2010: I didn't check past years)11:42
elkyI don't recall any significant meteorological bodies throwing us too far out of traditional orbit, so close enough.11:43
persiaWell, governments have odd ideas about time.  There are precious few places left where the sun is in at the midpoint of it's path at 12:0011:44
Vantraxyeah, I notice that too11:44
Vantraxits confusing sometimes11:44
persiaAnyway, do we have any more topics?11:45
elkyI don't believe so.11:45
elky[ACTION] Vantrax to email current board members for commitment info11:46
MootBotACTION received:  Vantrax to email current board members for commitment info11:46
Vantraxpersia/elky can you send an email with action items, I'm about to head home11:46
elkyI guess we adjourn to list and next fortnight11:47
Vantraxlogs are painful on a phone:p11:47
persiaSounds good to me.11:47
elkyI think that's the only action item actually.11:47
Vantraxyay me11:47
elky[ENDMEETING]11:47
Vantraxill get on to that soon11:47
elky#endmeeting11:47
MootBotMeeting finished at 05:47.11:47
persiaI may have trouble making the next meeting, as I'll be in UTC-4, just as a warning.11:47
elkypersia, next meeting is UDS week?11:47
Vantraxnp persia, thanks for making the effort11:48
persiaTwo weeks from today, yes?11:48
elkyThen I'll also be subject to being in the wrong timezone.11:48
* Vantrax wishes he got to go to uds11:48
Vantraxmaybe next time11:48
nigelbugh, uds11:48
Vantraxcan't even make linux.conf.au this year11:49
elkynigelb, next time you won't have to argue with 'murricans.11:49
persiaelky, With two of us the peer-pressure might be enough to make a 6:00 meeting :)11:49
nigelbelky: I just hope so :/11:49
elkypersia, lifeless not likely to be there?11:49
persiaDunno.  He often seems to make UDSs though, so maybe three.  He's an early person too.11:50
elkyIt's not like we're even from the same countries. We can't even just vote on moving .Au for example. So sad.11:51
* persia fails to be convinced that a vote is sufficient to so accelerate continental drift11:52
elkypersia, who cares about moving the actual landmass.11:54
persiaOh, just the routing assignments?  I tend to be conservative, and want alignment between routing assignments and geographic features.11:55
elkyHow quaint.11:58
ogituxhello all12:52
persiaogitux, Hey.  Meeting ended about an hour ago: it's at 10:00 UTC.  `date -u` run from a terminal will show you current UTC time.12:56
ogitux:(12:57
ogituxhuft I was Late13:00
persiaNext meeting on the 26th.13:01
ogituxok thx persia13:02
persiaI doubt enough members of the Board are awake at this hour, really.13:02
ogituxwhy doubt persia13:02
persiaBecause some of them are in UTC+13 and UTC+11, so it's really late.13:03
ogituxso I have not  been able to join in ubuntu member13:04
ogituxpersia:13:04
persiaNot this week, no.13:05
ogituxnext week yah persia13:05
persiaI don't happen to know offhand when the other boards meet, if you want to try one of them at an odd time, but if you want the evening meeting for Asia/Oceania, you will have to wait for the 26th.13:05
persiaNo, week after next.13:05
ogituxok, what time persia13:06
persia10:00 UTC13:06
ogituxthx13:06
ogituxpersia: where are u?13:12
=== bladernr is now known as bladernr_
=== ogra_ is now known as ogra
NCommander#startmeeting13:59
MootBotMeeting started at 07:59. The chair is NCommander.13:59
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]13:59
NCommander[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010101213:59
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010101213:59
lagA bit premature14:00
lago/14:00
davidmG'day all14:00
NCommanderbetter early than late14:00
davidmtrue14:00
mpoiriero/14:00
* NCommander gives everyone a moment to appear before starting properly14:00
lagTell that to my Mrs ;)14:00
persiaWithin a few seconds is better than most meetings time themselves.14:00
GrueMasterActually, right on time.14:00
davidmGood work all, 10.10 went out well, congratulations.14:01
lag\o/14:01
NCommanderand the world didn't explode14:01
NCommanderI consider tha an important bonus!14:01
dyfetthat's tomorrow's asteroid...14:02
persiaOr if it did, enough was reconstructed so that the difference is inobvious from the PoV of the average developer.14:02
NCommanderdyfet: maybe we'll get lucky and it will only squish Redmond or something :-P14:02
NCommanderanyway14:02
NCommander[topic] Action Item Review14:02
MootBotNew Topic:  Action Item Review14:02
NCommander[topic] persia to close and/or postpone his remaining action items for 10.1014:03
MootBotNew Topic:  persia to close and/or postpone his remaining action items for 10.1014:03
persiaNothing shows up on the new WI tracker.14:03
NCommander[topic] ogra + davidm to determine armel+omap4 releasability and notify the release team with the result14:03
MootBotNew Topic:  ogra + davidm to determine armel+omap4 releasability and notify the release team with the result14:03
ogralong done14:04
ograsince we released apparently14:04
NCommanderNCommander to unassign himself from bugs14:04
ogra(a roll call at the begining of the meeting would have been nice btw)14:05
* NCommander is assigned :-)14:05
NCommander*unassigned14:05
ograyeah, you were a bit over-enthusiastic :)14:05
ograi assigned the flash-kernel breakage back to you14:05
NCommanderI reassigned that to myself :-/14:05
ograit wasnt14:05
ograat least last night14:05
NCommanderargh14:05
NCommanderd'oh14:06
NCommanderwhoops14:06
ograwell, it is now :)14:06
NCommander[topic] Standing Item Review14:06
MootBotNew Topic:  Standing Item Review14:06
NCommanderI don't tihnk there's much point to go over the work trackers14:06
NCommander[topic] Kernel Status (cooloney, mpoirier, lag)14:06
davidmTrue14:06
MootBotNew Topic:  Kernel Status (cooloney, mpoirier, lag)14:06
lag * Texas Instruments (ti-omap)14:07
lag   * REBASE   : ti-omap4 branch is now at Ubuntu-2.6.35-903.1514:07
lag   * ON GOING : B605716 Regression from Karmic - corrected in Maverick - unsure what to do as the reporter has moved to Maverick.14:07
lag   * ON GOING : B637947 Kernel/userspace issue - lag is hosting a meeting with the top ASoC people today to discuss14:07
lag   * ON GOING : B535315 For some reason the net dev watchdog is timing out - more investigation needed.14:07
lag   * ON GOING : B613214 Regression from Karmic - working with user to bisect.14:07
lag   * ON GOING : B390959 For some reason the HID is recognising this keyboard as a joystick - more investigation needed.14:07
lag   * ON GOING : B22070  Looks like a USB issue, rectified in Maverick - need to fix Lucid.14:07
lag   * ON GOING : B43092  pata_pcmcia driver is not receiving correct IRQs - polling works, but was declined upstream.14:07
lag   * FIXED    : B637947 Audio fixing was merged and released - still need some user space configuration to make audio fully work14:07
lag   * FIXED    : B655746 HDMI bug fixing patch was merged.14:07
lag   * FIXED    : B586386 ti-omap4 branch missed this fix which is required by the upstart userspace application.14:07
lag   * FIXED    : B653002 An MLO patch was submitted to decrease the amount of occurence.14:07
lag   * FIXED    : B592295 omapdss DISPC error: SYNC_LOST_DIGIT.14:07
lag   * FIXED    : B605832 LG monitor behaving incorrectly when used in conjunction with the Panda board and HDMI.14:07
lag   * FIXED    : B612895 Unable to handle kernel NULL pointer dereference at virtual address 00000000 - fix released.14:07
lag   * FIXED    : B471228 Acer 5720 laptop will not wake from suspend - this issue has been rectified in Maverick.14:07
lag   * INVALID  : B628029 Not a bug, suspend is just not available on this h/w yet.14:07
lag   * INVALID  : B645420 Not a bug, USB OTG functionality is just not provided yet.14:07
lag   * PATCH    : IGEPv2's 6 patches have been SRU'ed. (OMAP3)14:07
lag   * PATCH    : The new set of ftrace patches have been submitted to linaro. (OMAP3)14:07
lag   * PATCH    : Working with Vincent Rabin on the remaining "graph tracing" patches. (OM14:07
lagOpen those clients :)14:07
lags/open/widen14:07
lag..14:07
lagOh bottom!14:08
* ogra has 1080p here14:08
ografits well14:08
lagI've just realised (a lot of them aren't arm)14:08
persialag, Don't bother to fix it now.14:08
ograwell, for arm we mostly care about the audio stuff14:08
lagk14:08
persiaogra, it's not the resolution of the screen: it's also how one *uses* the client.14:08
lagYep14:08
ografor which we have a meeting today14:08
lag2nd one down14:08
* persia abhors fullscreen harder14:08
NCommanderI think I cna mov eon14:10
NCommander[topic] QA Status (GrueMaster)14:10
MootBotNew Topic:  QA Status (GrueMaster)14:10
GrueMasterImages were tested with only a couple (kubuntu-mobile) seeing issues.14:11
GrueMasterWork started on blueprints for UDS-N related to QA on armel.14:11
persiaMost kubuntu-mobile ARM folk are tweaking the image for use on N900s anyway, so that's only of moderate concern.14:11
ograwhat do they do with the kernel and initrd then ?14:12
ograours wont boot14:12
RiddellGrueMaster: what was the issue with kubuntu-mobile?14:12
ograand without initrd oem-config wont run14:12
ogra(and they will run out of space very fast due to no resize happening)14:13
GrueMasterMet with TI validation team.  Some overlap, but not much.  Their focus is on testing hardware & drivers to the maximum capabilities in a series of long test runs (over a week on dozens of systems).  Our testing is more distro completeness centric.14:13
persiaogra, Dunno: ask rbelem or ian_brasil: I think there's a script that does it, and some documentation.14:13
ograpersia, well, if they dont generate a new initrd and boot with it their image will be horribly broken14:14
GrueMasterThe kubuntu-mobile images are incomplete in that they look like a single partition, not a complete drive with partitions.14:14
ograi dont really care about running our image on n90014:14
persiaogra, I have no detailed idea.14:14
persiaI know you don't care.  they do.14:14
ograright14:14
ograso they should ask for the right way ;)14:14
persiaPoint being that it's not that important that GrueMaster discovered issues.14:15
ograi'm happy to give info ... but to lazy to hunt someone down14:15
GrueMasterThe images worked on RC.  Not sure what changed.14:15
persiaWon't help: N900 isn't a fully open platform.14:15
ograthe kernel surely did14:15
persiaAnyway, enough of that.  Just a note to say that it's not a showstopper for anyone that the images weren't perfect.14:15
ograpersia, they worked on beagle14:15
GrueMasterNo they did not.14:16
ograthey stopped working on beagle with final14:16
* persia ran into OOM issues on beagle14:16
ograerm, where did they work then ?14:16
GrueMasterkubuntu-mobile final images never worked.14:16
ogra(if i say beagle blantly assume i say XM :) )14:16
GrueMasterRC did.14:16
ograGrueMaster, but thats what i said14:16
ogra:)14:16
GrueMasterAnd the kubuntu omap3 testing I did complete was on beagleXM.14:17
ograindeed14:17
ograno point in testing on C414:17
persiaOh, XM worked fine.14:17
persiaomap4 and C4 didn't work, which doesn't matter, because the objectives are met.14:17
ograomap4 still doesnt work ?14:17
* ogra thought it did 14:18
GrueMasterC4 and XM are the same image.  And Neither image (omap3 and omap4) worked for release.  Both worked for RC.14:18
ograk14:18
GrueMasterAs I am the QA guy, I know what I tested.14:18
ogrageez, you keep notes ?!?14:18
NCommanderone would hope14:18
NCommander[topic] ARM Porting/FTBFS status (NCommander, dyfet)14:19
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander, dyfet)14:19
* ogra is overwhelmed14:19
dyfetMost of the ones I did last week were also security vulnerabilities14:19
ogra:)14:19
persiaGrueMaster, XM didn't work for release?  Ah, yeah, that's probably annoying.14:19
GrueMasterpersia: image was incomplete.14:20
GrueMasterCompare it with a different image.  Run "file <image>" and you will see immediately what I am talking about.14:20
GrueMasterNo need to test it on a platform.14:20
persiaAh, right.  Somehow I thought that was only the omap4 image.  Oh well.14:20
GrueMasterSee bug 65728114:21
ubottuLaunchpad bug 657281 in Ubuntu "Kubuntu Maverick on Omap3 & Omap4: screen goes black and never comes back" [Undecided,Incomplete] https://launchpad.net/bugs/65728114:21
GrueMasterI added a note on the bottom detailing the issue.14:21
* ogra doesnt get the reboot part14:21
ograAfter the installation, the installer reboots the board and users are presented with the expected login prompt14:22
persiaRight.  I just misread your comment.14:22
ograi dont get what was tested there14:22
ogranone of omap3 or 4 images reboot after the installer was run14:22
persiaogra, The description is kinda painful, mostly because it's second-hand.14:22
ograah14:22
persiaBasically, jasper works, boot works, oem-config works, reboot doesn't work.14:23
ograwell, i dont get why mpoirier couldnt file it himself either14:23
GrueMastermpoirier ran the test and reported to marjo (instead of filing the bug himself).14:23
persiaFor that matter, even trying to log in post oem-config doesn't work on a C4 (but that's for OOM reasons)14:23
ograright14:23
ograright, screw C414:23
mpoirierI didn't file 'cause I thought someone would look at it right away...14:23
* ogra wants an official note that we dont support it in natty14:23
mpoirierask questions if you need more info.14:23
GrueMasterFile bugs so we can.14:24
ograright14:24
ograthat bug wasnt triaged at all14:24
ograi only heard about it when the final images were done already14:24
persiaIndeed.14:24
ograin fact it still isnt14:24
persiampoirier, Please always file bugs.  Nobody will look at anything that isn't findable.14:24
=== yofel_ is now known as yofel
ograand triage them properly14:24
mpoirierit was friday before the release and the QA team was on.14:25
ogra(subscribe ubuntu-armel and add an armel tag if we should look at it)14:25
mpoirierthe kubuntu was supposed to be waiting.14:25
persiampoirier, Doesn't matter.  We're all responsible for everything, as much as we specialise.  We can't expect anyone else to know what we mean, so we need to work with LP ourselves.14:25
ogrampoirier, well, we would probably still have had time to fix it14:26
ograwe all returned saturday there was time for a respin14:26
ograanyway14:26
* persia only heard about it *late* saturday night.14:26
* ogra heard about it late saturday night 14:27
ogratoo14:27
* NCommander didn't see see any chatter in u-release until it was too late about it unfortunately :-/14:27
ograsat. morning would have given us the time needed14:27
persiaAnyway: problem was one person submitting information to another person.14:28
ograanyway, move14:28
ograNCommander,14:28
persiaWe need to put stuff in LP, and notify teams and channels14:28
ogra^^14:28
persia(yes, move)14:28
NCommander[topic] ARM Porting/FTBFS status (NCommander, dyfet)14:28
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander, dyfet)14:28
ograwell, its over ;)14:28
dyfetI feel dajavu14:29
NCommandermaverick shipped with 81 FTBFS total14:29
ograunless you have SRUs14:29
ogracool14:29
ogra81 isnt as bad as former releases14:29
persiaIn fact, it's the best ever.14:29
dyfetthe ones i focused on last week were also security related...14:29
NCommandermaybe we can get it to 0 for natty ;_)14:29
ograNCommander, if we get doko proper hardware i'm sure of that14:30
ogradavidm, doko urgently needs a panda14:30
persiahttp://skitterman.wordpress.com/2010/10/09/ftbfs-final-score/ was a bit of a nice thing to see14:30
MootBotLINK received:  http://skitterman.wordpress.com/2010/10/09/ftbfs-final-score/ was a bit of a nice thing to see14:30
ogradoko did the heaviest lifting on ftbfs within teh last weeks i have seen yet14:30
davidmogra, as they become available we can get him one14:31
ogradavidm, he should get the first one we recieve ;)14:31
davidmnothing we can do until they go into GA14:31
ografrom the new chunk14:31
ograunderstood14:31
NCommanderyay14:32
NCommander[topic] ARM Image Status (ogra, NCommander)14:32
MootBotNew Topic:  ARM Image Status (ogra, NCommander)14:32
ogravirtually they would be fine if they would exist :)14:32
ograno natty images yet14:32
ograwe're all slackers !14:32
* GrueMaster blames the beer.14:33
ogramaverick images were fine apart from the sound issues14:33
* NCommander smacks ogra 14:33
persiaAnd the Kubuntu-mobile issues Gruemaster discovered.14:33
ograindeed14:33
ograso for kubuntu, i want a clear definition for natty what will be supported and what we will build14:34
ograand a want a *gaurantee* that there are *community* testers14:34
NCommander[action] ogra to follow up with kubuntu-dev with the images to build for natty14:34
MootBotACTION received:  ogra to follow up with kubuntu-dev with the images to build for natty14:34
ograat UDS14:34
NCommander:-)14:34
* ogra wants to have a BOF for that14:34
ograno need for an action14:34
ograrather a spec :)14:34
NCommander[topic] ogra to draft kubuntu image spec14:35
MootBotNew Topic:  ogra to draft kubuntu image spec14:35
ograi dont want to be hammered with kubuntu testing requests from QA the last minute before release becuase the community has no HW14:35
NCommander[topic] Any Other Business14:35
MootBotNew Topic:  Any Other Business14:35
ograspecs ?14:35
dyfetposting status?14:36
persiaogra, http://projects.powerdeveloper.org/project/imx515/801 should help in the HW department for Kubutnu14:36
ograpersia, with what ?14:36
ograwe dont support imx5*14:36
ograi only care about image testing for the official images here14:36
persiaWhat you support and what are images are only tangentially related.  I don't suggest you should support that, but it ought mean less demand for Kubutnu images for arbitrary pre-availability development boards, which ought make less demand on you.14:37
ograand for these i expect a minimum of HW to be available by the community that asks me to build their images, else i wont build them14:37
ograand i want a guarantee in advance at UDS that this testing can happen14:38
persiaI'm in favour of a spec: just noting that you may find less hard requirements on yourself.14:38
ograwell, if we build images i want them tested14:38
persiaAnd so you should.14:39
ograif they cant be tested i wont build them14:39
persiaRight.  Let's have a spec about this.14:39
ograyeah14:39
NCommanderMinimal requirements for us to spin images?14:39
davidmneed blueprints this week14:39
persiaI know that lots of the -testing crowd was unhappy with image validation because of lack of hardware.14:39
ograand invire QA, TI and the KDE community14:39
persiaNCommander, No.  Verification that we actually have testers with hardware for each image built.14:39
ograNCommander, no, specific for kubuntu14:39
persiaogra, Please no.  Other flavours might want it, etc.14:39
ograpersia, well, we dont build for other flavours atm14:40
persiaLet's just set up a chart, and make sure we have volunteers for everywhere.14:40
NCommanderogra: what if xubuntu/mythbuntu/* want images on arm?14:40
davidmI think the hardware issues will get sorted this cycle, the community should have their own hardware this cycle.14:40
ograthey are free to show up in the sessio and raise their hands14:40
persiaogra, Right.  "atm" is the reason for my objection :)14:40
ogradavidm, i want a written down list of stuff that can be testedd and the safety that our team doesnt have to do it in the end14:41
ograsure the HW situation will be better, but people still have to buy it or find a sponsor14:41
GrueMasterogra: Add to that a guarantee from our hw suppliers that we won't need to show up at the last minute for new hw.14:41
persiaogra, You probably also want some agreement from the cdimage team that they won't enable arbitrary other images on platforms with limited HW availability without confirming testers.14:41
NCommander[topic] ogra + persia to take this converation (on community ARM hardware) offline, and report back at UDS14:42
MootBotNew Topic:  ogra + persia to take this converation (on community ARM hardware) offline, and report back at UDS14:42
ograpersia, i can agree to that as a member of that team :)14:42
persiaNCommander, Please reset that action to be to bring a spec to UDS about it.14:42
ograright14:42
persiaogra, Right, but you need to confirm with everyone else on the team too :)14:42
ogramore on specs ?14:43
ogradavidm, by when, friday ?14:43
ograor earlier ?14:44
NCommander[topic] ogra + persia to take this converation (on  community ARM hardware) offline14:44
MootBotNew Topic:  ogra + persia to take this converation (on  community ARM hardware) offline14:44
NCommanderbah14:44
NCommander[topic] ogra + persia to take this converation (on   community ARM hardware) offline14:44
MootBotNew Topic:  ogra + persia to take this converation (on   community ARM hardware) offline14:44
NCommander...14:44
ograNCommander, stop playing with the bot :O14:44
NCommander^- and make a spec on it14:44
NCommanderI'm having copy and paste failures due to hidious lag14:44
davidmogra, as much as can be done by Friday, UDS scheduling needs to get done14:44
ograok, friday it is then14:44
NCommanderGrueMaster's DSL modem ishaving seizures14:44
persiadavidm, Should folk wanting to schedule stuff just set you as approver, or something different?14:45
davidmAnd the areas are different so we nned to submut them ASAP14:45
GrueMasterNo, it isn't14:45
NCommanderdavidm: UDS-N doesn't exist as a target to put specs against.14:45
davidmpersia, that is the main issue I am not a scheduler this UDS14:45
ograuh14:45
davidmthough "technically" I can do it14:45
ograwho is ?14:45
persiaAha.14:45
davidmI'll get the list to you all today for each section14:45
ogradavidm, but you're an approver for our workitems still, right ?14:46
ograi.e. we put you in for approving14:46
davidmWe don't have an ARM track just the general announced tracks that our Blueprints go into14:46
ograyes14:46
persiaI've been told http://ubuntudevelopers.blip.tv/file/3539348/ explains the correct method.14:46
ograi'm not talking about UDS14:46
davidmogra yes for workitems I am the approver14:46
ogragood14:46
davidmogra, in that sense you are correct14:46
NCommanderdavidm: (I can't select UDS-N as the sprint)14:46
davidmNCommander, I'll see when that opens14:47
davidmI would have thought today but perhaps tomorrow14:47
davidmThere was an announcment on naming, so make sure you follow the requirements14:47
NCommanderdavidm: thanks davidm14:48
davidmOr you will have to rename to match later (which is a pain)14:48
persiaNCommander, Next?14:49
ograan annoouncement on naming ?14:50
NCommander[topic] Specification Dicussion]14:50
MootBotNew Topic:  Specification Dicussion]14:50
* ogra missed that14:50
ogracan anyone summarize here ?14:50
persiaogra, $track-$team-n-$whatever14:50
ograand $tarck is the new tarck naming scheme ?14:51
ogra*track14:51
persia$team is some one-word string for the WI tracker.  $track is from summit.ubuntu.com $whatever is freeform.14:51
ograright, thanks14:51
ograand -n- not -natty-14:51
ograk14:51
persiaRight -n-14:51
ograthanks14:51
persiadavidm, If you have a preference for $team you want to impose, you may want to dictate something for your team to use :)14:52
ogra-arm- indeed14:52
persiaWorks.14:52
persiaOK.  Next?14:52
ograi need to adjust the WI tacker for it14:52
ograpast UDS though14:52
ograwe're still mobile there14:52
NCommanderAnything else to bring up? I'm realy to close out the meeting soonish14:53
ograNCommander, always in a hurry eh ?14:53
davidmpersia, we are the ARM team14:54
ograjust a big thank you to the team, well done for maverick :)14:54
davidmI'll echo that most strongly, thanks for the great work.14:54
persiadavidm, Thought so: just wanted verification, as (as ogra pointed out) "mobile" was used for maverick.14:54
davidmNCommander, close it down14:54
davidmpersia, true but we are now more accurately named ;-P14:55
NCommander#endmeeting14:55
MootBotMeeting finished at 08:55.14:55
persiaIndeed :)14:55
simar#ubuntu-bugs15:02
=== cking is now known as cking-afk
=== cking-afk is now known as cking
=== simar__ is now known as simar
=== dantaliz1ng is now known as dantalizing
lago/18:03
kees\o18:06
mdeslaurhello18:07
jdstrand\o18:07
nxvlhi18:07
mdeslaursbeattie?18:12
sbeattiehey18:13
mdeslaurkees: you get to start18:13
* mdeslaur pokes kees with stick18:16
=== simar_ is now known as simar
keeshi!18:17
keessorry, got distracted18:17
keesI'm doing audits this week, and helping the kernel get published some more.18:17
keesthat's really it from me. mdeslaur! :)18:17
mdeslaurok :)18:18
mdeslaurI'm currently building webkit 1.2.5 for karmic, lucid, maverick18:18
mdeslaurthat's what I plan to do this week. I'll pick something up from the CVE list of I have time left.18:18
mdeslaurthat's it!18:19
keesyay for webkit!18:19
mdeslaurjdstrand?18:19
jdstrandI am working on python-django, all mozilla products and libvirt18:21
jdstrandsbeattie: you're up18:21
sbeattieI've got an openjdk update going on this week, as well as triage.18:22
sbeattiethat's it for me.18:23
mdeslaurcool18:23
mdeslaurdoes anyone have anything to discuss with the security team?18:23
keesETIMEOUT18:25
keesthanks mdeslaur!18:25
mdeslaurhehe18:26
smosero/18:54
hallyn\o18:55
RoAkSoAxo/18:55
jiboumans_o/18:56
SpamapS\o\18:56
jjohanseno/18:56
zulafternoon18:57
ttx\\o18:57
hggdh~รด~18:58
ttxnice hat, dude18:58
RoAkSoAxlol18:58
Davieyo/18:59
* ttx has mild connectivity issues, don't worry if I disapeear from the face of the Internet for a few minutes.18:59
* hggdh bows to ttx18:59
SpamapSwell then, shall we?19:00
SpamapS#startmeeting19:00
MootBotMeeting started at 13:00. The chair is SpamapS.19:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:00
SpamapSI see no action points from the previous meeting, so we'll move forward to...19:00
SpamapS[TOPIC] Postmortem for Maverick (ttx)19:00
MootBotNew Topic:  Postmortem for Maverick (ttx)19:00
ttxhm, there was some action points though19:00
ttx  * ACTION: mathiaz to send out a call for ideas on ubuntu to the19:01
ttxpuppet community19:01
ttx  * ACTION: smoser to get skaet info on how to publish EC2 images19:01
ttx  * ACTION:  Everyone to celebrate the 10.10.10 release in their own unique ways19:01
SpamapSRight, they didn't make it into the agenda...19:01
SpamapS[TOPIC] review action points from previous meeting19:01
MootBotNew Topic:  review action points from previous meeting19:01
ttxSpamapS: probably the chair didn't copy them there :P19:01
SpamapSI didn't see an email from mathiaz..19:02
SpamapSand he is at hadoop world19:02
jiboumans_let's follow up with him afterwards19:02
ttxseeing fat elephants19:02
SpamapSso will carry that one forward unless somebody else saw the email?19:02
jiboumans_i didn't see the mail either19:02
SpamapS[ACTION] mathiaz to send out a call for ideas on ubuntu to the puppet community (carry over)19:02
MootBotACTION received:  mathiaz to send out a call for ideas on ubuntu to the puppet community (carry over)19:02
kim0can I help with that19:02
* smoser did get skaet info on how to do that, but still had to wake up sunday morning to help (due to my own mistakes). so 'Done'19:03
SpamapSsmoser: assuming you were able to instruct skaet on EC2 image publishing :)19:03
SpamapSsweet.19:03
ttxkim0: maybe, see with mathiaz19:03
Davieysmoser: Was kinda scary at one point :)19:03
ttxa bit scary.19:03
smoserbah19:03
smosernot scary19:03
smosereverything was under control :)19:03
SpamapSI celebrated by wearing my 101010 shirt and yelling at the TV whenever the Cowboys fumbled.19:03
ttxSpamapS: you got a 101010 shirt ?19:04
zuli killed a bird to celebrate19:04
SpamapSttx: not a 1 or 0, an old 101010 shirt from the 2005 Sysadmin of The Year Contest (I was nominated.. did not win.. too nerdy I presume)19:04
ttxah19:04
SpamapSOk, moving on19:04
SpamapS[TOPIC] Postmortem for Maverick (ttx)19:05
MootBotNew Topic:  Postmortem for Maverick (ttx)19:05
ttxSo you should have a look at your Maverick specs, and close them as "Implemented" or "Deferred"19:05
SpamapS[ACTION] ALL to mark maverick assigned specs as "Implemented" or Deferred19:06
MootBotACTION received:  ALL to mark maverick assigned specs as "Implemented" or Deferred19:06
ttxalso we need to keep a special eye on Maverick bugs19:06
ttxI expect people to stumble upon critical bugs once the release is out19:06
ttxso we need to stay ready for SRUs19:06
ttxI already noted two candidates19:06
ttxBug 658227 and bug 60017419:07
ubottuLaunchpad bug 658227 in openldap (Ubuntu) "upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so slapd aborts with "Program version 4.8 doesn't match environment version 4.7" error message)" [High,Triaged] https://launchpad.net/bugs/65822719:07
ubottuLaunchpad bug 600174 in axis2c (Ubuntu Maverick) "axis2c fails to build from source on maverick/i386" [High,Confirmed] https://launchpad.net/bugs/60017419:07
ttxThe first one being kinda urgent19:07
ttxI hoped mathiaz would be around to pick it up19:07
ttxbut he is not, so it's free game19:07
DavieySecond one.. really needs 'fixing'.. but i was going to propose not being uploaded unless axis2c needs uploading for another reason19:08
ttxDaviey: agreed19:08
Davieyie, backport from natty i guess.19:08
ttxanything else that you saw in daily triage that you think is a maverick regression ?19:08
Davieyno19:08
ttxif not, that's all for mavreick, rest in peace, long live Natty19:08
Daviey\o/19:09
SpamapSThere's a comment on bug 607646 that claims it may have caused a regression, but no actual bug report with details that I've seen yet19:09
ubottuLaunchpad bug 607646 in php5 (Ubuntu) "Segmentation fault in PHP5 with pgsql module" [Medium,Fix released] https://launchpad.net/bugs/60764619:09
ttxSpamapS: ok, you can move on19:10
SpamapSOk, on to Natty?19:10
SpamapS[TOPIC] Natty development19:10
MootBotNew Topic:  Natty development19:10
ttxNatty will open soon19:11
ttxand with it the season of syncs/merges19:11
ttxthat's the process of merging the changes in debian, or syncing to the version in debian19:11
ttxif the newcomers need any light on the process, please ask one of the old-timers.19:11
ttxDeferring to jiboumans for Natty planning19:11
RoAkSoAxwill a list of merges be published?19:12
SpamapSFrom what I understand, maverick had a fairly low percentage of pending merges completed.. so we may have a big backlog.19:12
ttxSpamapS: server looked not too bad.19:12
zulRoAkSoAx: merges.ubuntu.com19:12
DavieyRoAkSoAx: nothing server specific, but https://merges.ubuntu.com is always a good resource.19:12
ttxRoAkSoAx: in MoM, then maybe we'll come up with a server seed crossection19:12
RoAkSoAxlo. i know that but I meant server specific merges19:13
zulRoAkSoAx: i also have a python script if you want19:13
SpamapS298 outstanding merges in main19:13
RoAkSoAx :)19:13
zulSpamapS: we arent doing all that19:13
zul;)19:13
RoAkSoAxzul: for server specific?19:13
zulRoAkSoAx: yep19:13
RoAkSoAxzul: ok cool:)19:13
zulRoAkSoAx: just bug me about it after the meeting ill try to find it for you19:14
RoAkSoAxok thanks :)19:14
ttxSpamapS: moving on19:14
SpamapSOh no specs?19:14
ttxSpamapS: that's jiboumans's subject19:15
ttxthough I can fill in if he dropped19:15
SpamapSjiboumans_: Natty specs preparation (jib)19:15
jiboumans_The time for creating blueprints for UDS sessions is upon us; looking at https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool we have a lot to go on. Right now, only blueprints for topics that you think warrant discussion at UDS are needed to be created; try to group similar topics in a way that makes a good session and list them as part of the "UDS" Section under the right track and remove them from the idea pool. That should be doable for everyone somew19:15
jiboumans_this week I think.19:15
ttxELINETOOLONG19:15
jiboumans_try to group similar topics in a way that makes a good session and list them as part of the "UDS" Section under the right track and remove them from the idea pool. That should be doable for everyone somewhere this week I think.19:16
jiboumans_Any items left in the idea pool after this week are ideally then items that don't need discussion and we can move those to blueprints at a later date just to track implementation. Any questions about next steps?19:16
SpamapSOk, going once...19:16
SpamapSjiboumans_: thanks, moving on..19:17
SpamapS[TOPIC] Weekly Updates & Questions for the QA Team (hggdh)19:17
MootBotNew Topic:  Weekly Updates & Questions for the QA Team (hggdh)19:17
hggdhok19:17
hggdhwe are now phasing out the 'regression-potential' tag19:17
hggdhplease use only regression-release or regression-proposed or regression-updates as needed19:18
ttxok19:18
ttxwho looks at those ?19:18
hggdhwe  -- QA/bugSquad will look at all current bugs set with -potential, and will update them19:19
ttxack19:19
hggdhthe docs and the LP greasemonkey scripts will be updated also19:19
hggdhapart from that, nothing new on the western front19:20
SpamapSAnything else for QA?19:20
SpamapSOn to the kernel then..19:20
SpamapS[TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)19:20
MootBotNew Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)19:20
jjohansenI don't have anything I want to bring up19:20
jjohansensmoser: what do you have for me :)19:20
smoserhm..19:21
smoser2 things.19:21
Davieyheh19:21
smoser1. lucid load, i've beeen promised a fix like 2 weeks ago19:21
jjohansenis that still not in?19:21
smoser(ok, promised was a strong word, but given suggestion that it would be fixed, i relayed in bug)19:21
smoserthere is no udpate to the bug19:21
smoser2.) maverick issue bug 65846119:22
ubottuLaunchpad bug 658461 in linux (Ubuntu) "-virtual kernel missing dependent modules (ahci fails to load)" [Undecided,New] https://launchpad.net/bugs/65846119:22
jjohansenI did the rebase, that was blocking and tested, and handed it back to brad and steve19:22
smoserwell, there is no 'fix-released' comment in the bug. so i'm not aware of it.19:22
jjohansensmoser: right I would expect them to update the bug when the pushed the rebase, I'll look into it19:22
smoserwe also have bug 634487. which i would really like to see fixed in lucid and maverick.19:23
ubottuLaunchpad bug 634487 in linux-ec2 (Ubuntu) "t1.micro instance hangs when installing sun java" [Medium,Confirmed] https://launchpad.net/bugs/63448719:23
SpamapS[ACTION] jjohansen to look into virtual kernel bug status (bug 658461)19:23
MootBotACTION received:  jjohansen to look into virtual kernel bug status (bug 658461)19:23
ubottuLaunchpad bug 658461 in linux (Ubuntu) "-virtual kernel missing dependent modules (ahci fails to load)" [Medium,Confirmed] https://launchpad.net/bugs/65846119:23
jjohansenthanks, I'll try to take a look at it this week19:24
SpamapSsmoser: I thought that was an issue on amazon's side?19:24
SpamapSor was that the reboot issues?19:24
jjohansenSpamapS: may be19:24
smoserSpamapS, there was a data corruption bug on amazon's side for user-data.19:24
SpamapSok19:24
smoserthe java bug is definitely a kernel bug (imho).  a user space process makes kernel go crazy19:24
smoseror crash19:25
SpamapSok, anything else?19:25
SpamapSjjohansen: did you want a single action item to look into both of those bugs?19:25
jjohansenSpamapS: it could be our kernel trying to use unsupported pv-ops19:25
jjohansenSpamapS: sure19:25
SpamapS[ACTION] jjohansen to look into bug 65846119:25
MootBotACTION received:  jjohansen to look into bug 65846119:25
ubottuLaunchpad bug 658461 in linux (Ubuntu) "-virtual kernel missing dependent modules (ahci fails to load)" [Medium,Confirmed] https://launchpad.net/bugs/65846119:25
SpamapSok I'll fold it in to one in the minutes19:25
zulpv-ops is funnn..19:26
SpamapSmoving on to documentation19:26
SpamapS[TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)19:26
MootBotNew Topic:  Weekly Updates & Questions for the Documentation Team (sommer)19:26
DavieyWe miss sommer!19:26
=== jsgotangco_ is now known as jsgotangco
SpamapSoh didn't see that he wasn't here19:26
SpamapSok.. did anybody else have documentation issues they'd like to have relayed to sommer?19:27
ttxSpamapS: no19:27
SpamapS[TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)19:27
MootBotNew Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)19:27
kim0o/19:27
kim0hey folks .. I'd just like to draw attention of OpenWeek. Find the schedule at: https://wiki.ubuntu.com/UbuntuOpenWeek19:27
kim0I'm giving a cloud basics session tomorrow 16:00UTC, I will be demo'ing cloud-init and answering basic questions. Dustin, will be giving a session after it on deploying web apps to the cloud19:27
kim0Other than that, I had sent out a call for contributers, I have around 8 people who want to start contributing to ubuntu-server (Yaaay). I'll be talking to Jono tomorrow on how to best get them involved and any mentoring needed. Any volunteers to help with the process are most welcome19:27
kim0That should be all19:27
* kirkland waves19:28
SpamapSkim0: thanks!19:28
SpamapSand now to everyone's favorite topic19:28
SpamapS[TOPIC] Open Discussion19:28
MootBotNew Topic:  Open Discussion19:28
RoAkSoAxI you haven't read so already, I've successfully setup HA for the UEC-CLC using the cluster stack (pacemaker, heartbeat) and DRBD for replication between CLC's. Everything seems to working as expected. I'll blog post about it later this week when I finish midterms. I'm planning to discuss this at UDS (If Cluster Stack Session get's scheduled).19:28
* SpamapS will be holding a cluster stack session on the beach if it doesn't get scheduled at UDS19:29
* hallyn registers for that one19:30
DavieyRoAkSoAx: You rock! :)19:30
SpamapSIndeed.. cluster FTW :)19:30
SpamapSok, if nobody else has anything?19:30
SpamapSOk then19:31
ttxSpamapS: according to my wife, I snored last night. Bad news for you.19:31
Daviey\o/19:31
SpamapSttx: only if yours overpowers mine19:31
SpamapS[TOPIC] Announce next meeting date and time19:31
MootBotNew Topic:  Announce next meeting date and time19:31
ttxaaaargh19:31
SpamapSNext meeting will be Tuesday 2010-10-19 at 1800 UTC - here in #ubuntu-meeting19:31
SpamapSthanks everyone!19:31
Davieyo/19:31
SpamapS#endmeeting19:32
MootBotMeeting finished at 13:32.19:32
RoAkSoAx\o19:32
ttxSpamapS: yay19:32
=== Ursinha is now known as Ursinha-afk
=== noy_ is now known as noy

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