[10:35]  * MaWaLe is away: brb
[10:37]  * MaWaLe is back (gone 00:01:34)
[13:04] <pan1nx> wasn't there supposed to be ubuntu-mobile meeting?
[13:05] <pan1nx> hu, June 4, 12:00 – 13:00
[13:05] <pan1nx> Description * Location: IRC channel #ubuntu-meeting * Agenda: None listed as of publication
[13:15] <ogra> wrong timing :)
[13:16] <ogra> 21:00 UTC
[13:16] <pan1nx> But the fridge sais something else
[13:16] <pan1nx> ogra: http://fridge.ubuntu.com/calendar
[13:17] <ogra> so the fridge is obviously wrong
[13:18] <pan1nx> m'key...so we/someone should change that?
[13:18] <pan1nx> persia?
[13:22] <persia> Someone should definitely change that.
[13:33] <cody-somerville> What should it be?
[13:34] <ogra> 21:00 UTC
[13:34] <cody-somerville> Is it correct now?
[13:35] <ogra> yep, thanks cody-somerville
[13:35] <persia> cody-somerville, That looks great.  Thanks.
[13:36] <cody-somerville> I've updated all the events in the series so it should be fixed retroactively as well as for all future occurrences.
[13:37] <persia> cody-somerville, Is that on the base calendar, or from an invite?
[13:38] <cody-somerville> Its actually on the fridge calendar.
[13:38] <persia> Also, "fixed" retroactively might be a bit misleading.  For a long time, 12:00 UTC was the correct time.
[13:38] <persia> (not that it ought matter for the future)
[13:38] <cody-somerville> oops
[13:39] <cody-somerville> persia, Do you want me to transfer ownership of the event series to yourself?
[13:40] <persia> Um, no.  While I know a bunch about it, I'm unsure I understand how to maintain it.
[13:40] <persia> 21:00 UTC should be stable for at least several months to come (12:00 UTC lasted about 16 months).
[21:00] <NCommander> #startmeeting
[21:00] <MootBot> Meeting started at 15:00. The chair is NCommander.
[21:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[21:00] <NCommander> argh, wrong time
[21:00] <NCommander> #endmeeting
[21:00] <MootBot> Meeting finished at 15:00.
[21:58] <davidm> hi ogra
[21:59] <ogra> hey
[22:00] <NCommander> #startmeeting
[22:00] <MootBot> Meeting started at 16:00. The chair is NCommander.
[22:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[22:00] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090604
[22:00] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090604
[22:00] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Roadmap
[22:00] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Roadmap
[22:00] <NCommander> alright, who's here?
[22:00] <plars> o/
[22:01] <davidm> I am
[22:01]  * ogra waves
[22:01] <lool> I'm here too; albeit I found my desktop crashed again
[22:01] <ogra> same here
[22:02]  * ogra is working from an old celeron cmpc 
[22:02]  * NCommander notes his laptop been unstable, so if I go silent, it usually means my laptop is rebooting
[22:02] <NCommander> I'm going to reinstall it tonight; I just finished backing up everything important :-)
[22:02] <ogra> semms i was to brave with the new intel driver :)
[22:02]  * NCommander will be setting his laptop to use the NVIDIA one until he's sure the intel one is more stable :-)
[22:03] <ogra> you should work from your babbage ;) its stable
[22:03] <NCommander> paulliu is MIA
[22:03] <ogra> bad time for him
[22:03] <NCommander> ogra, I don't have an external monitor or keyboard here
[22:04] <NCommander> ogra, so is persia and StevenK, should I proceed or wait?
[22:04] <NCommander> (and dyfet)
[22:04] <dyfet> here :)
[22:04] <NCommander> Never mind on that last bit :-)
[22:04] <davidm> it's an ugly time in Taiwan right now.
[22:04] <NCommander> hi StevenK
[22:04] <NCommander> davidm, indeed, and I suspect chaos would ensure if we attempted to float the IRC meeting
[22:05] <ogra> davidm, well, .au or .jp isnt much better
[22:05] <davidm> just slightly I agree
[22:05]  * StevenK looks for the matchsticks to hold his eyes open
[22:05]  * NCommander hooks a coffee IV into StevenK's arm
[22:05] <StevenK> Ewww, coffee
[22:05] <NCommander> StevenK, how about caffienated vegemite :-)
[22:05] <davidm> StevenK, just stick them under your fingernails you'll stay away then with NP
[22:05] <ogra> hey you dont have to drink it that way :)
[22:06] <StevenK> NCommander: I don't think I want my Vegemite tainted with additives
[22:06] <NCommander> StevenK, meh. I still can't find it in NYC, although I did find a store that sells Marmite, but anyway, I think we need to start now
[22:07] <StevenK> That doesn't sound right.
[22:07] <StevenK> NYC is well, New York. *Somewhere* has to
[22:07] <NCommander> StevenK, the person I talked to said he knew a place in NJ that has it
[22:07] <ogra> NCommander, can you put the regular babbage update back on the roadmap ?
[22:07] <NCommander> ogra, oh, sure
[22:07] <ogra> i think its worth having it
[22:07] <NCommander> [topic] Action Item Review
[22:07] <MootBot> New Topic:  Action Item Review
[22:07] <NCommander> [topic] #
[22:07] <NCommander> NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 (co)
[22:07] <MootBot> New Topic:  #
[22:07]  * NCommander sighs
[22:07] <NCommander> Still c/o
[22:08] <ogra> well, probably karmic helps :)
[22:08] <ogra> (if the buildds work again)
[22:08] <NCommander> [topic] NCommander and GrueMaster to debug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809
[22:08] <MootBot> New Topic:  NCommander and GrueMaster to debug https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809
[22:08] <NCommander> THat's still a c/o
[22:08] <GrueMaster> rgr that
[22:08] <NCommander> and I don't think we need to care about the lpia configuration item
[22:09] <NCommander> [topic] Roadmap Review
[22:09] <MootBot> New Topic:  Roadmap Review
[22:09] <NCommander> [topic] Babbage Status for Karmic (ogra)
[22:09] <MootBot> New Topic:  Babbage Status for Karmic (ogra)
[22:09] <ogra> no kernel before A3 i was told
[22:09] <NCommander> ogra, do we at least have kernel sources this time around?
[22:09] <ogra> beyond that i have a karmic rootfs running on my B2
[22:10] <ogra> according to amit we do
[22:10] <ogra> but same issue as last time
[22:10] <ogra> 30M tarball and he has to cherrypick
[22:10] <NCommander> ow
[22:10] <ogra> yeah
[22:10] <NCommander> brb, something is burning
[22:11] <ogra> there goes the fireman ...
[22:11] <st33med> The roof is on fire!
[22:11] <st33med> The roof is on fire!
[22:11] <st33med> Raise the roof!
[22:11] <st33med> Raise the roof!
[22:11] <st33med> :)
[22:11] <dyfet> hopefully not his babbage bd...
[22:11] <lool> dyfet: Mind picking up the chair?
[22:11] <ogra> well, he wont need the B1 anymore ... apart from possible jaunty stuff
[22:12] <NCommander> back
[22:12] <NCommander> I'm just going to hope that smell is from outside.
[22:12] <dyfet> okay....
[22:12] <NCommander> ogra, my B1s are in Rochester ATM actually :-/
[22:12] <ogra> ok, re-> B2 ... i tested the audio bits with the 2.6.26 kernel
[22:13] <ogra> there seems to be a HW issue when playing back music ...
[22:14] <ogra> not sure its caused by the driver so i'll wait for our own kernel, but playback only works for a certain amount of time until odd sounds come up
[22:14] <NCommander> ogra, with raw ALSA or pulse running?
[22:14] <ogra> we also have no driver for the DVI port
[22:14] <ogra> with either
[22:14] <ogra> there is a GL driver thats supposed to work which i couldnt test yet
[22:15] <ogra> we'll also need to repackage that, its not poroperly packaged (GL libs replacing mesa etc)
[22:15] <plars> ogra: is that related to bug #358851
[22:16] <ogra> nspoluginwrapper ?
[22:16] <ogra> no, i was using rhytmbox and totem ...
[22:16] <NCommander> plars, nspluginwrapper won't work on ARM unless they hooked up an extreme scary QEMU hack
[22:16] <plars> sorry, bug #358831
[22:16] <NCommander> *extremely
[22:16] <GrueMaster> wow. I can't even access that bug.
[22:16]  * plars can't type today :)
[22:16] <NCommander> GrueMaster, you aren't in ubuntu-bugsquad?
[22:17] <ogra> if you play back any audio file after about a munite a tick sound appears
[22:17] <NCommander> ogra, were you using pulse?
[22:17] <ogra> the ticking frequency raises over time
[22:17] <GrueMaster> I thought I was.
[22:17] <ogra> both, with gstreamer wset to alsa or pulse
[22:17] <ogra> mist be a codec, driver or hardware issue
[22:18] <ogra> it sounds like a scratched CD
[22:18] <ogra> just that the frequency raises ... after some mins its not bearable anymore
[22:18] <ogra> and its reliably reproducable
[22:18] <NCommander> That sounds like a Babbage 2 issue. I don't remember encountering that on the B1, but I can retest that once I go home
[22:18] <NCommander> (hopefully this weekend)
[22:18] <ogra> lets wait for our own kernel, it might be the alsa driver in the 2.6.26 kernel
[22:19] <NCommander> So what action items do we want to take from this?
[22:19] <GrueMaster> 2.6.26 has a really old alsa.  Could be the issue.
[22:19] <ogra> its just something i tested this week, no need to discuss it in depth
[22:19] <ogra> i'm happy to report that we have images btw :)
[22:20] <NCommander> ogra, the live images work?
[22:20] <NCommander> woo!
[22:20] <GrueMaster> yea.
[22:20] <ogra> they might take 1h to boot but we have some
[22:20] <NCommander> ogra, is there an open bug on the boot time?
[22:20] <ogra> unionfs/fuse is extremely slow in karmic
[22:20] <NCommander> s/in karmic//g
[22:20] <NCommander> Fixed that for you :-P
[22:21] <ogra> cjwatson knows about it and i think the general plan is to wait for mount --union instead of fixing unionfs-fuse
[22:21] <ogra> NCommander, it was ok speedwise in jaunty
[22:21] <ogra> (not great but ok)
[22:21] <ogra> now its really really slow
[22:22] <ogra> well, thats about the babbage status ...
[22:22] <ogra> feel free to move on :)
[22:23] <NCommander> [topic] Specification Review
[22:23] <MootBot> New Topic:  Specification Review
[22:23] <NCommander> I think we should save drafting the new roadmap until next week incase we still have unwritten specifications.
[22:23] <StevenK> Agreed
[22:24]  * ogra has still a lot
[22:24] <StevenK> Naughty ogra
[22:24] <StevenK> But I can't talk
[22:24] <ogra> :0
[22:24] <ogra> :)
[22:24]  * NCommander grumbles
[22:24] <NCommander> Oh well
[22:25] <davidm> Need to crank on the spec 's
[22:25] <NCommander> "All specifications from UDS to be considered for karmic must be drafted for next meeting to be included on the roadmap" - does that sound about right?
[22:26] <ogra> yup
[22:26] <davidm> yup
[22:26] <NCommander> [action] All specifications from UDS to be considered for karmic must be drafted for next meeting to be included on the roadmap
[22:26] <MootBot> ACTION received:  All specifications from UDS to be considered for karmic must be drafted for next meeting to be included on the roadmap
[22:26] <NCommander> There :-)
[22:27] <NCommander> There been no status changes in any bugs we are tracking, I don't think we need to go over them
[22:27] <NCommander> Anyone have any bugs we want to add to the roadmap?
[22:27] <lool> There are a couple from ARM
[22:28] <lool> https://bugs.launchpad.net/ubuntu/+source/gcc-4.3/+bug/347864
[22:28] <lool> https://bugs.launchpad.net/ubuntu/karmic/+source/ffmpeg/+bug/383240
[22:28] <ogra> yeah loic spammed my inbox yesterday :)
[22:28]  * NCommander hasn't even dealt with the backup of LP spam :-/
[22:28] <lool> In general, there are other interesting bugs to work on
[22:28]  * ogra has inbox zero at least once a day 
[22:28] <NCommander> lool, are we tagging bugs from ARM?
[22:28] <lool> The thunderbird crash 340595
[22:28] <ogra> yeah
[22:28] <lool> And gnome-keyring's -O1 has been dropped, so it should bug again
[22:29] <ogra> davidm bumped the retracer RT for that
[22:29] <NCommander> ogra, my inbox broke 2000 emails during the last two days of UDS, its down to about 400 now.
[22:29] <NCommander> ogra, I can retrace it manually if its not been resolved by weeks end, I don't want that to be a blocker
[22:29] <ogra> so we should get proper arm retracers soon i hope
[22:30] <NCommander> ogra, well, the ARM retracer is setup on rimu, the problem just a firewall issue; I had pitti setup the retracers on all architectures awhile ago
[22:30] <ogra> NCommander, its more important that apport works imho, butr feel free to attack the TB bug
[22:30] <NCommander> TB?
[22:30] <StevenK> Thunderbird
[22:30] <ogra> thunderbird
[22:30] <NCommander> Bug #340595
[22:30] <StevenK> Not tuberculosis
[22:30] <ogra> *grin*
[22:30] <NCommander> StevenK, actually, I was thinking technical board :-P
[22:31] <StevenK> TB is also 'Terabyte'
[22:31] <ogra> *not* tebibyte :P
[22:31] <NCommander> We had thunderbird issues in jaunty with just getting that beast to compile
[22:31] <NCommander> :-/
[22:31] <ogra> (one of the maikl threads i really dont need)
[22:32] <ogra> well, involve asac, he might be able to help
[22:32] <ogra> or anyone else from the mizilla team
[22:32] <NCommander> ogra, we still need decent backtraces first :-)
[22:32] <ogra> yeah
[22:33] <NCommander> I don't think I saw an answer; is there a tag we want to be tracking beside the normal arm/armel ones?
[22:33] <ogra> no, the two suffice imho
[22:33] <NCommander> Ok
[22:33] <ogra> bad enough that we have two
[22:33] <lool> I think it's nice to tag, but what matters is who is subscribed/assigned
[22:33] <davidm> We need to document the tag on the wiki
[22:33] <lool> We should be in charge of the @canonical-mobile bugs
[22:33] <NCommander> lool, if we have a consistant tag, I'll make a note to check it when I make new meeting pages.
[22:33] <davidm> s/tag/tags/
[22:33] <ogra> we really should unify on one
[22:34] <NCommander> lool, or should I say a high-priority tag
[22:34] <plars> we just need to agree on which it should be, if we pick arm over armel though, apport will have to be fixed to deal with it
[22:34] <lool> We have priorities on the bugs
[22:34] <lool> I like the way the desktop team handles bugs
[22:34] <NCommander> I think we need to go with armel, its the actual architecture flag
[22:34] <ogra> right, i'm all for armel
[22:34] <lool> They use priorities, milestones, and assignments
[22:34] <ogra> lool, dont we too ?
[22:34] <NCommander> And if we ever need to target big-endian arm hardware, then we'll have armeb
[22:35] <lool> I don't mind tagging bugs related to arm "arm" or "armel", but that doesn't commit us from dealing with them
[22:35] <plars> I can convert all the arm to armel if needed
[22:35] <lool> armel might be a better choice then; it's what apport adds by default
[22:35] <ogra> lool, i'd personally like to have only one tag
[22:35] <NCommander> Is there a way we could get some sorta armel report on people?
[22:35] <lool> ogra: I agree
[22:35] <lool> There are TWO discussions going on here
[22:35] <plars> NCommander: such as?
[22:35] <lool> One about looking for work items, which shouldn't be tracked by tags
[22:36] <lool> And another about how to tag arm specific issues
[22:36] <ogra> yeah
[22:36] <NCommander> Ok
[22:36] <NCommander> [topic] How to tag arm specific issues
[22:36] <MootBot> New Topic:  How to tag arm specific issues
[22:36] <lool> I think everybody agrees with tagging ARM issues "armel" and only that; not "arm"
[22:36] <ogra> NCommander, please sort :)
[22:36] <NCommander> Lets take care of this one first, I think its the easier one :-)
[22:36] <plars> I can generate reports based on tags if that's what you're looking for
[22:36] <lool> plars: Not really
[22:36] <ogra> ++ for armel only
[22:36] <NCommander> +1 on armel as well
[22:37] <plars> +1 armel
[22:37] <lool> plars: It's just an interesting piece of info which we should try to keep, but what matters to us is not the fact that it's ARM specific or not, just whether it's important, and on our plate
[22:37] <ogra> sounds like we all agree on armel ...
[22:37] <ogra> or most of us at least
[22:37] <davidm> +1 from me too
[22:38] <lool> So the other topic is gathering bugs which should be on our radar
[22:38] <ogra> NCommander, ?
[22:38] <NCommander> Who wants the action item on this? (which I'm not 100% sure it should be)
[22:38] <lool> I don't know whether people are aware of the nice tool which rickspencer3 wrote for the desktop team's bugs
[22:38]  * ogra is i was in the talk :)
[22:38] <NCommander> I wasn't, is there a link on what this tool was?
[22:38] <ogra> we should use it
[22:39] <lool> NCommander: He said he'd publish it, but I don't know whether he did and am not aware where it is publicly available
[22:39] <ogra> it is on LP
[22:39] <ogra> i'll ask him about it if he's back from holiday
[22:39] <ogra> action that for me
[22:40] <NCommander> Ah, its pm-dashboard
[22:40] <NCommander> [action] ogra to investigate pm-dashboard
[22:40] <MootBot> ACTION received:  ogra to investigate pm-dashboard
[22:40] <ogra> thanks
[22:40] <plars> https://launchpad.net/pm-dashboard
[22:41] <StevenK> https://code.edge.launchpad.net/~rick-rickspencer3/pm-dashboard/trunk
[22:41] <NCommander> [topic] Looking for Work items
[22:41] <MootBot> New Topic:  Looking for Work items
[22:41] <ogra> yeah
[22:41] <NCommander> Ok, so on this topic now
[22:41] <lool> ( https://code.edge.launchpad.net/~rick-rickspencer3/pm-dashboard/trunk )
[22:41] <NCommander> lool, you were saying?
[22:41] <StevenK> I beat lool finding something on LP? O.o
[22:41] <NCommander> [link] https://launchpad.net/pm-dashboard
[22:41] <MootBot> LINK received:  https://launchpad.net/pm-dashboard
[22:41] <lool> I was saying that I prefer using some team to put bugs on our radar
[22:41] <NCommander> [link] https://code.edge.launchpad.net/~rick-rickspencer3/pm-dashboard/trunk
[22:41] <MootBot> LINK received:  https://code.edge.launchpad.net/~rick-rickspencer3/pm-dashboard/trunk
[22:42] <lool> StevenK: Actually I got it from rick :)
[22:42] <cjwatson> ogra: actually the speed was fine once I remembered to allocate 256MB of memory rather than kvm's default 128MB
[22:42] <lool> see #ubuntu-desktop
[22:42] <cjwatson> (unionfs-fuse live CDs)
[22:42] <ogra> cjwatson, my ltsp tests today got me 4minute boots for just bringing up X
[22:42] <NCommander> BTW, screenshot of pm-dashboard https://wiki.ubuntu.com/RickSpencer?action=AttachFile&do=get&target=pm-dashboard.png
[22:42] <NCommander> [link] https://wiki.ubuntu.com/RickSpencer?action=AttachFile&do=get&target=pm-dashboard.png
[22:42] <MootBot> LINK received:  https://wiki.ubuntu.com/RickSpencer?action=AttachFile&do=get&target=pm-dashboard.png
[22:42] <ogra> cjwatson, vs 30sec boots to login window in jaunty
[22:42] <lool> plars: Did you have any QA specific conversations around best usage?
[22:43] <cjwatson> ogra: ah, you have a worse problem than I do then. Anyway, didn't mean to interrupt ...
[22:43] <plars> lool: best usage of?
[22:43] <lool> I would say: subscribe canonical-mobile to get it on the radar of people in the canonical mobile team and assign it when it's in their reponsability to fix
[22:43] <ogra> lool, canoical-mobile or ubuntu-mobile ?
[22:43] <NCommander> lool, only partner's will likely do that; any bug reports from our user base will either put ubuntu-mobile, or not put it at all.
[22:43] <lool> plars: We want a good bug workflow; so far, it has wild and handled differently from person to person
[22:44] <plars> lool: ah, qa process stuff, yes
[22:44] <NCommander> I think we should discuss lool's idea on assigning this task
[22:44] <lool> ogra: I think ~ubuntu-mobile is conflated and canonical-mobile is clearly defined; I've seen some canonical teams use canonical-$team
[22:44] <NCommander> lool, I think using canonical-mobile is the wrong thing to do, since it suggests removing non-canonical involvement in the ARM port
[22:45] <lool> Why so?
[22:45] <ogra> NCommander, pretty moot point with the set of HW we'll support in karmic
[22:45] <NCommander> ogra, I'm worried on setting a president
[22:46] <ogra> there is no community to test the arm fixes we do
[22:46] <lool> NCommander: I think it's fine if other people join and help; they can assign themselves to bugs or subscribe themselves too
[22:47] <NCommander> lool, I get a bad feeling by using canonical-mobile vs. a non-canonical team. It basically says the ARM port will only be handled by Canonical folks.
[22:47] <StevenK> No it doesn't.
[22:47] <StevenK> It says this bug will
[22:47] <ogra> well, we will only support HW nobody else has
[22:48] <ogra> where should a community come from to help or test
[22:48] <NCommander> I'll give the point, but I think this is an issue we may want to rediscuss in the future.
[22:48] <lool> I don't think it's exclusive to say canonical-mobile has interest in a bug when the team is subscribed to it; the only thing which might be exclusive is the assignee
[22:48] <plars> why not canonical-arm?
[22:48]  * NCommander forgot we had canonical-arm
[22:48] <plars> for just the arm specific ones
[22:48] <lool> plars: canonical-$team matches real canonical teams rather than people working on specific projects
[22:49] <ogra> feel free to subscribe both teams
[22:49] <NCommander> ogra, I think this is for bug assignments, not subscription.
[22:49] <lool> There were arguments against creating an ubuntu-arm in the past (ML and team); I personally wouldn't object to that in general, but I would like to stop proliferation
[22:49] <ogra> NCommander, subscription
[22:50] <ogra> assignment should still be to specific people
[22:50]  * NCommander notes the kernel team uses assignments
[22:50] <NCommander> We're running out of time, do we want to save this issue for next meeting?
[22:50] <lool> So we have this mass of bugs from which we're going to extract a subset where a) canonical is genuinously interested in fixing for business reasons b) canonical is interested because of general maintenance of the port
[22:50] <plars> assignment implies that the individual is actively working on the bug
[22:51] <NCommander> I think having a clear policy on handling ARM bugs is a good idea
[22:51] <lool> plars: Or has responsability to fix it
[22:52] <NCommander> I'm going to call time on this issue, and put it in the agenda for next week.
[22:52] <NCommander> [action] Management of ARM bugs to continue next week
[22:52] <MootBot> ACTION received:  Management of ARM bugs to continue next week
[22:53] <NCommander> [topic] Any other business
[22:53] <MootBot> New Topic:  Any other business
[22:53] <plars> NCommander: I'd like to not limit it to just arm bugs, but all bugs we care about
[22:53] <NCommander> [action] Management of Mobile Team Bugs to continue next week
[22:53] <MootBot> ACTION received:  Management of Mobile Team Bugs to continue next week
[22:53] <NCommander> plars, good idea.
[22:53] <plars> thanks :)
[22:53] <NCommander> actually
[22:54] <NCommander> If anyone has a good proposal for how to handle this, please send it to my canonical email address, and we'll iterate in turn on each one, as well as keep discussion open
[22:54] <plars> doh... only I won't be able to make the meeting next week
[22:54] <lool> plars: I agree, I don't think the discussion needs to be ARM specific
[22:54] <NCommander> plars, see above :-)
[22:54] <plars> ok
[22:55] <NCommander> I just have concerns on cramming everything in especially with roadmap construction next session.
[22:55] <ogra> plars, what, no multitasking ? :)
[22:55] <plars> ogra: only if I can connect to irc from a plane
[22:55] <ogra> heh
[22:55]  * ogra wasnt serious
[22:56] <plars> :)
[22:56] <NCommander> plars, Delta been rolling out wifi on their flights :-)
[22:56] <ogra> though lufthansa has wlan in their first vclass since years
[22:57] <NCommander> [action] Any member who would like to make a proposal for handling of bugs, please send it to NCommander's email, to be discussed and summarized during the next IRC meeting.
[22:57] <MootBot> ACTION received:  Any member who would like to make a proposal for handling of bugs, please send it to NCommander's email, to be discussed and summarized during the next IRC meeting.
[22:57] <ogra> 3mins ...
[22:58] <NCommander> actually
[22:58] <NCommander> Who's going to be here next week?
[22:58]  * NCommander wonders if there are enough people to warrant a meeting and roadmap construction
[22:58]  * ogra is
[22:58]  * NCommander is
[22:58] <davidm> I might be depending on connectivity
[22:58] <NCommander> davidm, do you want me to proceed with roadmap construction (pending your final approval) if your not?
[22:58]  * StevenK is
[22:59] <dyfet> what happens next week? :)
[22:59] <davidm> HAve meetings next week however and they could overrun this timeslot
[22:59] <ogra> on site visit
[22:59] <davidm> NCommander, sure
[22:59] <dyfet> ogra: ah...
[22:59] <NCommander> davidm, *nods*
[22:59] <ogra> yeah, we need to get the rodmap together
[22:59] <NCommander> Ok, so we'll have our meeting as planned. Hopefully with everyone here :-)
[23:00] <GrueMaster> I will depending on how my desktop rebuild goes.
[23:00] <NCommander> #endmeeting
[23:00] <MootBot> Meeting finished at 17:00.
[23:00] <NCommander> Cya next week :-)
[23:00] <ogra> bye
[23:00] <lool> bye