[05:10] <nixternal> !meeting
[05:10] <nixternal> !meetings
[05:10] <nixternal> !time
[07:21] <cyphermox> geser, was the MC meeting cancelled?
[07:24] <geser> no, but the other MC members are not here yet
[07:25] <geser> persia, nhandler, nixternal, jpds: here?
[07:33] <kecsap_> what happens the mc meeting today?
[07:34] <kecsap_> when will it take place
[07:34] <kecsap_> ?
[07:34] <cyphermox> kecsap_, it's as geser said :)
[07:34] <geser> when we have quorum
[07:34] <kecsap_> ok
[07:34] <kecsap_> so waiting....
[07:34] <kecsap_> thanks
[07:35] <cyphermox> kecsap_, sorry, i hadn't realized you probably didn't see the messages
[07:35] <kecsap_> cyphermox, my laptop was frozen and it was needed to restart it. no problem. :)
[07:56] <geser> dholbach: kecsap_ and cyphermox are waiting for us
[07:57] <geser> Quintasan|Szel: are you here too?
[08:05] <cyphermox> geser, dholbach, I'm very sorry but I guess I'll have to reschedule, it's getting really late here and I need to get some sleep... so it's going to be back in January :)
[08:06] <kecsap_> from my side, I can still wait, no problem for me
[08:06] <dholbach> cyphermox: I'm sorry - either January or we might manage to have an adhoc meeting
[08:06] <cyphermox> not a problem
[08:07]  * dholbach hugs cyphermox
[08:07] <dholbach> sleep tight :)
[08:07]  * cyphermox hugs back
[08:07] <cyphermox> from the Meeting page, "Ad-hoc meeting on 11 December 2009 on 14 UTC", is that valid?
[08:07] <geser> cyphermox: if 6h of sleep are enough for you :), we are trying to do an adhoc meeting at 14 UTC today
[08:07] <dholbach> for Quintasan|Szel
[08:07] <cyphermox> geser, my point exactly :)
[08:08] <geser> if we reach quorum at that time, yes
[08:08] <cyphermox> alright, I should be there
[08:09] <kecsap_> can I still wait or this meeting is obviously lost?
[08:09] <cyphermox> later!
[08:09] <dholbach> kecsap_: I just texted two other MC members - it's an obvious problem we have as the MC is literally spread around the globe
[08:10] <dholbach> (east side of the US, Europe and Japan :))
[08:10] <dholbach> kecsap_: so if you still have time, don't give up hope yet
[08:11] <kecsap_> ok, I still have hope. :)
[08:13] <geser> kecsap_: I see in your application page no testimonials and no sponsored uploads. did you work with the community till now?
[08:13] <dholbach> kecsap_: you're CsabaKertesz?
[08:15] <kecsap_> as I mentioned there I did not work on ubuntu distribution, but on upstream projects
[08:15] <dholbach> kecsap_: it's a bit hard for us to approve MOTU membership for people who we haven't seen getting patches into Ubuntu itself
[08:15] <kecsap_> that is what I would like to push with my patches now: https://bugs.launchpad.net/ubuntu/+source/opencv/+bug/311188
[08:15] <dholbach> kecsap_: usually we use the Sponsorship Process to get patches and packages uploaded to Ubuntu for people who are not part of the team yet
[08:15] <dholbach> (basically you just subscribe the reviewers team to the bug)
[08:16] <dholbach> https://wiki.ubuntu.com/SponsorshipProcess has more detail about that
[08:16] <dholbach> having had a few conversations about patches between reviewers and somebody who applies makes it easier for us to approve membership
[08:16] <dholbach> https://wiki.ubuntu.com/MOTU/GettingStarted lists all the other good documentation too
[08:17] <kecsap_> so first I should patch some software in lucid and try the membership after that?
[08:17] <dholbach> kecsap_: exactly
[08:18] <dholbach> kecsap_: so the next time we meet we can have a look at what you've done and what others have said about you
[08:18] <kecsap_> ok and how much bugs should I fix for this? :)
[08:18] <dholbach> kecsap_: that makes the whole thing more straight-forward than having to make assumptions about what you know and what you don't know :)
[08:18] <dholbach> kecsap_: what I find very helpful is talking to sponsors and reviewers
[08:18] <geser> that way you can prove your packaging skills, your knowlegde of the processes and if you can work with others (and others with you)
[08:19] <kecsap_> ok
[08:19] <dholbach> kecsap_: they might have had a look at a few of your patches and will be happy to add an endorsement to your wiki page
[08:19] <dholbach> kecsap_: I really hope you don't see this as a set-back
[08:19] <dholbach> kecsap_: we're there in #ubuntu-motu all the time to help with anything you might need
[08:20] <dholbach> https://wiki.ubuntu.com/MOTU/GettingStarted should give you all the most important info to get started
[08:20] <kecsap_> let's see. if others will be responsive and helpful then no problem
[08:20] <dholbach> awesome - the sponsorship process usually works out quite well
[08:21] <kecsap_> ok, then I will fix some bugs and update my motu membership application.
[08:21] <dholbach> thanks a lot kecsap_
[08:21] <dholbach> kecsap_: I really appreciate your understanding
[08:21] <kecsap_> thanks to you
[08:21] <dholbach> and as I said: #ubuntu-motu has a lot of future friends :)
[08:21] <kecsap_> c u on january. :)
[08:21] <dholbach> kecsap_: I'll comment out your application from the meeting page for now, ok?
[08:22] <kecsap_> ok
[08:22] <dholbach> thanks a bunch
[08:22] <dholbach> and have a great day!
[08:22] <kecsap_> ok, bye
[14:03] <Quintasan> dholbach: you're around?
[14:04] <dholbach> hello quintasan
[14:04] <persia> Quintasan: Unfortunately, while some of us are around, we're still chasing down the other couple.
[14:04] <dholbach> cyphermox: ready? :)
[14:04] <Quintasan> dholbach: hello
[14:04] <cyphermox> yep
[14:04] <dholbach> let's kick off the meeting anyway
[14:04] <Quintasan> persia: okay
[14:04] <dholbach> if we can't have the full vote, we'll handle the rest via email - I'll try to get people into the meeting as we go :)
[14:04] <dholbach> persia: want to drive the meeting?
[14:04] <persia> Sure.
[14:04] <dholbach> :)
[14:04] <geser> cyphermox: did you sleep well?
[14:05] <persia> #startmeeting
[14:05] <dholbach> super
[14:05] <MootBot> Meeting started at 08:04. The chair is persia.
[14:05] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:05] <cyphermox> not too bad. A little short ;)
[14:05] <persia> [TOPIC] Contributing Developer applicatio for Mathieu Trudel
[14:05] <MootBot> New Topic:  Contributing Developer applicatio for Mathieu Trudel
[14:05] <persia> [LINK] https://wiki.ubuntu.com/Mtrudel/ContributingDeveloperApplication
[14:05] <MootBot> LINK received:  https://wiki.ubuntu.com/Mtrudel/ContributingDeveloperApplication
[14:05] <dholbach> (this is the agenda for those who haven't seen it yet: https://wiki.ubuntu.com/MOTU/Council/Meeting :-))
[14:06] <persia> dholbach: Thanks :)
[14:06] <persia> cyphermox: Welcome.  So, what is your motivation for becoming a Contributing Developer?
[14:07] <persia> (not why do you develop, but why do you apply for this group now?)
[14:07] <cyphermox> I'm very interested in Ubuntu developer and I think packaging rocks :) My plan is to join the MOTU team, and I see it as another step in becoming more versed into what is going on
[14:08] <dholbach> cyphermox: who did you mostly work with in the Ubuntu world?
[14:08] <persia> Well, you're already an Ubuntu Member, so there's no additional rights or permissions that go with being a Contributing Developer.
[14:08] <cyphermox> dholbach, mostly asac and awe as part of the NetworkManager team, which I am now a part of.
[14:08] <dholbach> nice
[14:08] <cyphermox> otherwise, I've done work on some patches here and there on other stuff
[14:08] <asac> yes.. cyphermox is doing a remarkable job there
[14:08] <cyphermox> e.g. telepathy-butterfly
[14:09] <asac> consider a +1 for me on his application!
[14:09] <cyphermox> I also started this cool little project to test EC2 images, --> lp:checklist ;)
[14:10] <persia> geser: dholbach: Do either of you have any other questions?
[14:10] <dholbach> persia: no :)
[14:11] <dholbach> pretty uncontroversial :)
[14:11] <geser> just a quick question
[14:11] <geser> I see that you got one upload sponsored for hardy, then a longer pause and several uploads for karmic. any specific reason for this long pause?
[14:11] <ScottK> cyphermox: In Kubuntu we often have trouble with NetworkManager and the KDE front end getting out of sync.
[14:12] <ScottK> Would you be able to help us out with fixing such problems?
[14:12] <cyphermox> geser, I'd say it's because of my work. kind of busy in some aspects, and following my upload some coworkers convinced me to be more active. jcastro helped out in convincing me too :)
[14:13] <cyphermox> ScottK, I'd love to. My C skills aren't perfect, but I believe it's good enough to fix some bugs. I'm much better at python though
[14:13] <geser> so you plan to stay active? sounds good :)
[14:13] <cyphermox> OTOH, as I don't use KDE all that much (probably because of the very issues you speak of), I haven't had as much exposure to it as I'd like
[14:14] <cyphermox> geser, indeed
[14:14] <ScottK> We can fix that ...
[14:14] <ScottK> asac gave us some big help the last cycle and we'll miss his assistance.
[14:14] <cyphermox> as I said, work takes a lot of my time -- I'm a sysadmin in a fairly small team to take on *lots* of systems. but I work on Ubuntu whenever I can
[14:15] <asac> ScottK: good thing is that NM wont be that aggressivley up-to-date in future, so the knetworkmanager upstream delay might already be good enough
[14:15] <ScottK> asac: Good to know, just looking for resources if it comes up ....
[14:15] <asac> yep
[14:16] <JontheEchidna> hopefully they'll support NM 0.8 longer than they did 0.7 ;-) ... but I'm getting off-topic
[14:16] <asac> kubuntu team should get someone in the netowrk-manager team imo
[14:16] <asac> so we can train someone etc.
[14:16] <persia> So, any more queries for cyphermox ?
[14:16] <dholbach> not from me
[14:17] <persia> geser: ?
[14:17] <geser> no question from me too
[14:18] <dholbach> shall we vote and chase missing votes per mailing list?
[14:18] <persia> OK.  We're unfortunately still not quorate, but given that granting membership to an Ubuntu Member is a no-op, I'm happy to accept success if three of us vote in favour.  Does that sound reasonable dholbach, geser?
[14:18] <geser> sure :)
[14:19] <dholbach> +1 :)
[14:19] <persia> [VOTE] Accept Mathieu Trudel as a Contributing Developer
[14:19] <MootBot> Please vote on:  Accept Mathieu Trudel as a Contributing Developer.
[14:19] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[14:19] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[14:19] <geser> +1
[14:19] <MootBot> +1 received from geser. 1 for, 0 against. 0 have abstained. Count is now 1
[14:19] <persia> +1
[14:19] <MootBot> +1 received from persia. 2 for, 0 against. 0 have abstained. Count is now 2
[14:19] <dholbach> +1
[14:19] <MootBot> +1 received from dholbach. 3 for, 0 against. 0 have abstained. Count is now 3
[14:19] <persia> [ENDVOTE]
[14:19] <MootBot> Final result is 3 for, 0 against. 0 abstained. Total: 3
[14:20] <persia> cyphermox: Congratulations!  This doesn't get you much, as you're already a member, but welcome to the team!
[14:20] <JontheEchidna> Congrats. :)
[14:20] <cyphermox> thanks :)
[14:20] <Quintasan> Grats :D
[14:20] <dholbach> cyphermox: rock on! on to motu-ship (or wherever you go next)!
[14:20] <dholbach> I'm sure you'll do a good job
[14:21] <persia> OK.  Next up.
[14:21] <persia> [TOPIC] MOTU application for Michal Zajac
[14:21] <MootBot> New Topic:  MOTU application for Michal Zajac
[14:22] <persia> [LINK] https://wiki.ubuntu.com/MichalZajac/MOTUApplication
[14:22] <MootBot> LINK received:  https://wiki.ubuntu.com/MichalZajac/MOTUApplication
[14:22] <persia> Quintasan: How are you doing today?
[14:22] <Quintasan> persia: oh, good, excited :)
[14:23] <persia> Quintasan: I notice that you're really focused in Kubuntu Development.  What prompts you to apply to MOTU rather than as Kubuntu-dev (or is there a parallel application in process?)
[14:23]  * geser has the same question
[14:23] <ScottK> persia: There is a lot of KDE stuff in Universe that kubuntu-dev does not give upload rights for.
[14:24] <persia> ScottK: Is that something that ought be addressed, or just a coincidence?
[14:24] <Quintasan> persia: well I think upload rights to main are big responsibility and I'd like to spend some more time on learning packaging, also being a dev involves coding somehow and I recently picked c++
[14:24] <dholbach> how much of https://launchpad.net/~quintasan/+related-software is core Kubuntu?
[14:25] <ScottK> persia: I think it's an open question.  Quintasan has shown an interest in the 'long tail' of KDE stuff and has many of the attributes that would make him suitable to be a MOTU gardener.
[14:25] <Quintasan> dholbach: most of the Uploaded packages with exception to dooble and recorditnow
[14:25] <dholbach> alright
[14:26] <dholbach> Quintasan: one comment on the application said you might want to consider talking to upstream developer some more. is that on your radar somehow?
[14:26] <persia> Quintasan: What do you think is the best way to tackle the needs-packaging list?
[14:27] <Quintasan> dholbach: yup, I have gluon to package and I will contact debian-qt-kde devels to consult the package splitting with them
[14:27] <dholbach> Quintasan: do you think it's hard to be and stay in touch with upstream kde and upstream debian?
[14:28] <Quintasan> persia: I would first gather all reports that contain unmaintained and WIP application and check whether it's worth packaging or not
[14:28] <persia> Quintasan: So begin a process of discrimination to exclude packages that don't appear to add value?
[14:29] <Quintasan> dholbach: I really think it depends on type a package, if it's a core package then it can be hard sometimes, like 4.4 packaging :)
[14:30] <Quintasan> persia: something like this, there is no point in including all of available apps out there, is there?
[14:30] <dholbach> Quintasan: what did you find problematic or "not so easy" there?
[14:30] <persia> That's the core of the debate :)  The counter argument is that users should never have to go anywhere else for software.
[14:31] <Quintasan> dholbach: I had few problems with libs and missing files but I sorted them out after few hours.
[14:31] <dholbach> Quintasan: with upstreams help? :)
[14:32] <Quintasan> dholbach: not really, though there were few changes in okteta and I needed to consult with upstream what to do with files
[14:32] <dholbach> alright
[14:32] <dholbach> Quintasan: how's the polish ubuntu translations scene?
[14:33] <Quintasan> dholbach: I think quite good. There are many skilled translators and I saw movement on our mailing list
[14:33] <dholbach> that's great to hear
[14:34] <persia> Quintasan: I notice a number of build failures from some of your recent uploads (e.g. kdeadmin).  What steps have you taken to address these?
[14:36] <Quintasan> AFAIK everything with exception to kdegames was built successfully.
[14:36]  * ScottK notes for the record that he had build failures with the recent KDE 4.4 beta too.  It was a complex transition.
[14:36] <Riddell> I'd like to reitterate my comments on Quintasan's application, he's learnt well and would be a positive contribution to MOTU and KDE packages in universe if approved
[14:37] <JontheEchidna> yeah, 4.4 beta was brutal
[14:37] <Quintasan> I just can nod :)
[14:37] <persia> I'm sure it was.  I'm more curious about Quintasan's explanation of the process to address the failures than that the source happened to be difficult.
[14:38] <Quintasan> persia: I can't quite remember having problems with kdeadmin though I might have forgotten to change *.so version, that was the most common source of build failures for me
[14:39] <Quintasan> let me look in bzr
[14:39] <JontheEchidna> Quintasan: there was a build-dep on libx11-dev that was forgotten
[14:39] <JontheEchidna> but I missed that in my sponsoring of your package, so I'm just as much to blame as you
[14:39] <Riddell> which was actually an issue elsewhere
[14:39] <JontheEchidna> yeah, that too
[14:39] <persia> Quintasan: Feel free to pick another example package.  It's that the last several showed up at https://launchpad.net/~quintasan/+related-software rather than kdeadmin specifically
[14:40] <JontheEchidna> most of those other ones are just ports failures, as far as I can see
[14:40] <Quintasan> I was about to type this
[14:40] <JontheEchidna> All ports excpet powerpc I believe are a bit busted at the moment
[14:41] <Quintasan> persia: AFAIK ports are most problematic
[14:41] <JontheEchidna> wait, not powerpc
[14:41] <Quintasan> armel?
[14:41] <JontheEchidna> sparc
[14:41] <JontheEchidna> all ports except sparc are busted due to failures at a lower-level than kde
[14:42] <Quintasan> Not much I can do about this :P
[14:42]  * persia is done with questions, but generally encourages existing developers to let candidates answer questions, as it becomes hard to judge knowledge of processes and procedures, and technical skills when the answers come from many directions :)
[14:43] <persia> dholbach: geser: ?
[14:43]  * dholbach is done too
[14:43] <geser> no further questions
[14:43] <JontheEchidna> oh, sorry :P
[14:43] <persia> Quintasan: Apologies, but apparently we've a couple ill council members today.  We'll start voting, but have to finish via email.
[14:44] <persia> [VOTE] MOTU Application for Michal Zajac
[14:44] <MootBot> Please vote on:  MOTU Application for Michal Zajac.
[14:44] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[14:44] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[14:44] <persia> +1 : with this level of support from the rest of the Kubuntu folk, I'm confident any remaining wrinkles will be flattened soon.
[14:44] <MootBot> +1 received from persia. 1 for, 0 against. 0 have abstained. Count is now 1
[14:44] <geser> +1
[14:44] <MootBot> +1 received from geser. 2 for, 0 against. 0 have abstained. Count is now 2
[14:44] <dholbach> +1
[14:44] <MootBot> +1 received from dholbach. 3 for, 0 against. 0 have abstained. Count is now 3
[14:45] <JontheEchidna> Quintasan: good luck with the rest
[14:45] <Quintasan> JontheEchidna, ScottK, Riddell: thanks for showing up :)
[14:45] <ScottK> No problem.  Glad to be here.
[14:45] <Quintasan> dholbach, persia, geser: Thanks guys!
[14:45] <persia> [ENDVOTE]
[14:45] <MootBot> Final result is 3 for, 0 against. 0 abstained. Total: 3
[14:45] <dholbach> Quintasan: keep up the good work!
[14:46] <persia> Quintasan: With luck you'll get a firm answer in the next few days.
[14:46] <persia> [TOPIC] Business before MOTU Council
[14:46] <MootBot> New Topic:  Business before MOTU Council
[14:46] <Quintasan> I bet I will be checking my mail every few minutes :P
[14:46] <persia> Nobody put anything on the agenda.  Does anyone have any ad-hoc items?
[14:46] <dholbach> persia: just who takes care of processing the applications
[14:47] <persia> I'll do that today, as well as update the headers and the report.
[14:47] <dholbach> persia: thanks muchly!
[14:47]  * dholbach has no further business
[14:47] <persia> OK.  As a reminder, the next meeting has been postponed in favour of being lazy at year-end.
[14:48] <persia> We'll be reconvening 8th December, at 7:00 UTC.
[14:48] <geser> December?
[14:48] <persia> Right!
[14:48] <dholbach> January :)
[14:48]  * persia is getting an early start of the being lazy bit :)
[14:48] <dholbach> hehe
[14:48] <persia> We'll be reconvening 8th *January*, at 7:00 UTC.
[14:49] <persia> #endmeeting
[14:49] <MootBot> Meeting finished at 08:49.
[14:49] <dholbach> thanks a bunch everybody!
[14:50] <geser> woohoo, that was the last MC meeting for this year :)
[14:52] <dholbach> geser: you're right :)
[14:53] <geser> wasn't it even the last MC meeting for this decade?
[14:53] <Quintasan> :O
[14:53] <dholbach> that we still have to find out :)
[14:55] <geser> doesn't 2010 start the new decade?
[14:55] <cyphermox> geser, it does
[14:57] <dholbach> oh well, sorry guys :)
[15:15] <mhall119|work> I thought 2011 started the new decade
[15:18] <geirha> Doesn't every year start a new decade?
[15:44] <ScottK> mhall119|work is technically correct since there was no year 0.
[15:58] <pitti> o/
[15:58]  * asac waves
[15:58] <jiboumans> \\o
[15:59]  * ogra lurks
[15:59]  * apw zones in
[15:59] <ttx> o/
[16:00]  * marjo wave
[16:00]  * slangasek waves
[16:03] <slangasek> robbiew, cjwatson, davidm, rickspencer3, Riddell, ScottK, njpatel, jdstrand: ping
[16:03] <robbiew> o/
[16:03] <rickspencer3> hi
[16:03] <njpatel> hey
[16:03] <jdstrand> o/
[16:03] <Riddell> afternoon
[16:03] <slangasek> hi, all
[16:03] <slangasek> #startmeeting
[16:03] <MootBot> Meeting started at 10:03. The chair is slangasek.
[16:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <ttx> cjwatson is away today, methink
[16:03] <mdz> \o
[16:04] <slangasek> [LINK] https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-12-11
[16:04] <MootBot> LINK received:  https://wiki.ubuntu.com/ReleaseTeam/Meeting/2009-12-11
[16:04] <slangasek> [TOPIC] Actions from previous meeting
[16:04] <MootBot> New Topic:  Actions from previous meeting
[16:04] <slangasek> most of these I know were done
[16:04] <pitti> ah, I talked to dbarth
[16:04] <slangasek>   * asac to announce https://wiki.ubuntu.com/ARM/Thumb2 to the broader developer community
[16:04] <pitti> and also left the questions in the whiteboard
[16:04] <asac> done (today)
[16:04]  * pitti checks
[16:04] <slangasek> ok, great
[16:05] <pitti> hm, wasn't fixed yet, though
[16:06] <pitti> slangasek: but the plymouth MIR is filed, anyway
[16:06] <slangasek> ok
[16:06]  * ogra is really curious how that will behave on armel
[16:06] <slangasek> pitti: so I think we can strike that from the list as well
[16:08] <slangasek> [TOPIC] final spec lists to ubuntu-release@lists.ubuntu.com
[16:08] <MootBot> New Topic:  final spec lists to ubuntu-release@lists.ubuntu.com
[16:08] <slangasek> just a brief reminder about this, since I haven't received any new ones since last week - I have foundations and desktop, and that's it
[16:08] <asac> in what form?
[16:08] <asac> oh i think i can look at what was send
[16:08] <asac> nevermind
[16:09]  * apw missed that action, applogies
[16:09] <slangasek> you can check the list archive for examples - https://lists.ubuntu.com/archives/ubuntu-release/2009-December/
[16:09] <pitti> slangasek: would you mind if I go first today, since I need to leave in 20 mins? (sorry, big family event)
[16:10] <slangasek> I'm not too fussy about the form of the mail, I just want to make sure we have something that details, from your own mouths, what your team considers the priorities for this cycle to make sure we're all on the same page
[16:10] <slangasek> pitti: ok
[16:10] <slangasek> [TOPIC] Desktop Team
[16:10] <MootBot> New Topic:  Desktop Team
[16:10] <slangasek> pitti: let's get right to it, then :)
[16:10] <pitti> thanks
[16:11] <pitti> as usual, our report is on https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:11] <pitti> activity this week: desktop startup speed, landed X.org halsectomy, started power-saving work, landed first wave of new DX indicator work
[16:11] <pitti> a2 work items: on track
[16:11] <pitti> RC bug status: pretty calm
[16:11] <slangasek> [LINK] https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:11] <MootBot> LINK received:  https://wiki.ubuntu.com/DesktopTeam/ReleaseStatus
[16:11] <pitti> I expect that the bugs will come once we enable apport again (retracer chroots are now set up, BTW)
[16:12] <pitti> there are a couple of X crashes which we need more info on, but right now the apport bit of X is disabled (needs porting)
[16:12] <pitti> but by and large the udevified X caused way less trouble than anticipated
[16:13] <slangasek> I'll withhold my own judgement on that until my X server stops crashing when I close my lid ;)
[16:13] <pitti> oh?
[16:13] <slangasek> bug is filed - just an idle comment, don't worry about it :)
[16:13] <pitti> wrt desktop-lucid-une: Didier Roche will work on this, but he only starts on January 7th
[16:14] <pitti> so we'll handle that during his induction sprint in Paris that week
[16:14] <asac> hmm. on arm i saw some udev complains on console and X didnt start. thought it was something else with our install;... so there were udev related changes to X?
[16:14] <asac> but lets talk about that after meeting
[16:14] <pitti> asac: it should start either way; what can happen is that you don't have any input devices
[16:15] <pitti> asac: bug report with x log and udevadm info --export-db would be appreciated
[16:15] <pitti> (please subscribe me)
[16:15] <asac> yeah. i wasnt that far yet ;).
[16:15] <slangasek> pitti: the release status page misses the bug link for the nv crasher bug; is that on your radar elsewhere?
[16:16] <pitti> oops, sorry
[16:16] <slangasek> (494627, fwiw)
[16:16] <pitti> bug 494627, will add to the page now
[16:17] <slangasek> pitti: any concerns about other specs targeted for alpha-2?
[16:17] <pitti> the one that's really big and potentially in jeopardy is social-from-the-start
[16:18] <pitti> OTOH it's not a dealbreaker if it slips
[16:18] <pitti> it's just on a2 because it has rather intrusive changes
[16:18] <slangasek> ok
[16:18] <pitti> but by and large I think we're on track
[16:18] <slangasek> great
[16:18] <slangasek> any questions for desktop from others?
[16:19] <slangasek> [TOPIC] QA Team
[16:19] <MootBot> New Topic:  QA Team
[16:19] <slangasek> pitti: thanks
[16:19] <slangasek> marjo: hi
[16:20] <marjo> * Hardware testing
[16:20] <marjo> Netbook:
[16:20] <marjo>         passed: 9 (69%) failed: 0 (0%)  untested: 4 (31%)
[16:20] <marjo> Laptop:
[16:20] <marjo>         passed: 22 (86%) failed: 2 (7%)  untested: 2 (7%)
[16:20] <marjo> Server:
[16:20] <marjo>         passed: 13 (25%) failed: 33 (62%)        untested: 7 (13%)
[16:20] <marjo> Desktop:
[16:20] <marjo>         passed: 12 (100%) failed: 0 (0%)  untested: 0 (0%)
[16:20] <pitti> oops, what happened on server?
[16:21] <fader_> pitti: bug 494052
[16:21] <pitti> ah, so it's like "one major bug which affects many machines"?
[16:21] <fader_> It's a popular network card and it's not being initialized properly, preventing the install
[16:21] <slangasek> yep
[16:21] <fader_> pitti: indeed
[16:21] <pitti> *phew*
[16:21] <fader_> Hehe
[16:21] <slangasek> I've proposed a permanent fix for that class of bug in bug #494774
[16:22] <marjo> pitti: i know you're already looking for 100%s all around
[16:22] <marjo> give it some time, we'll get there!
[16:22] <slangasek> marjo: are the two laptop failures anything that need to be discussed?
[16:22] <marjo> fader_ promises so
[16:23] <slangasek> and was 494052 the /only/ bug hampering us on server?
[16:23] <marjo> http://people.canonical.com/~fader/hw-testing/current.html
[16:23] <MootBot> LINK received:  http://people.canonical.com/~fader/hw-testing/current.html
[16:24] <marjo> same bug, 2 failures
[16:24] <fader_> slangasek: The laptop failures were X starting in low-graphics mode, but it seems to be fixed now
[16:24] <marjo> is that what you meant?
[16:24] <fader_> I'll ask moustafa to double-check that in the lab
[16:24] <slangasek> ok
[16:24] <fader_> And yes, that is the only distro bug we're currently seeing on servers
[16:24] <slangasek> not a bad result after all, then :)
[16:24] <marjo> that's pretty good this early on
[16:25] <marjo> imho
[16:25] <fader_> (there were a couple of power issues but those don't seem to be bugs in the distro but environmental/hardware issues)
[16:26] <marjo> slangasek ready for alpha1 test report?
[16:26] <slangasek> marjo: do we need to discuss anything on lucid-qa-checkbox-desktop-experience-tests?  it missed the alpha-1 target, but I don't know that it's anything we need to discuss here?
[16:26] <slangasek> marjo: oh, yes, please go ahead with that first
[16:26] <marjo> oh, sorry
[16:26] <marjo> * UbuntuSpec:lucid-qa-checkbox-desktop-experience-tests
[16:26] <marjo> [cr3] Add DX PPA when testing and reboot if new packages are discovered: INPROGRESS
[16:27] <marjo> Lucid Alpha 1 Test Report
[16:27] <marjo> 2009-12-11
[16:27] <marjo> = Summary =
[16:27] <marjo> == Test Coverage ==
[16:27] <marjo> Image Test Coverage = 72%
[16:27] <marjo> Test Case Coverage = 55%
[16:27] <marjo> The main reason of the low coverage is that images were not installable
[16:27] <marjo> until Wednesday morning, leaving only one day for testing the final images.
[16:28] <marjo> overall, quite good coverage for alpha1
[16:28]  * ScottK is here now.
[16:28]  * pitti waves; sorry, have to leave; please direct desktopish questions to rickspencer3
[16:28] <slangasek> pitti: thanks, have fun
[16:28] <marjo> [16:28] <marjo> 23 Test Failures
[16:28] <marjo> Failure Rate 23/181 = 12.7%
[16:28] <mdz> marjo: in light of the reduced coverage, will we continue to test alpha 1 until we get full coverage, or is that not worthwhile at this point?
[16:29] <marjo> mdz: we could do that, let's see if we can keep the testers going
[16:29] <marjo> since all is set up now
[16:29] <slangasek> the untested images consist of DVDs + edubuntu + mythbuntu + ubuntustudio, I believe
[16:30] <mdz> the DVDs have some testing but not full coverage
[16:30] <slangasek> I don't think it's worth having people test DVDs that we don't mean to publish; any problems they find are so unlikely to apply to the next milestone
[16:30] <marjo> slangasek: so, we focus the testing appropriately that way
[16:30] <slangasek> oh, so they do - those results came in after alpha-1 was published without the DVDs then
[16:31] <marjo> slangasek: it doesn't hurt to test anyway right?
[16:31] <slangasek> marjo: as long as you're not burning up your testers' good will :)
[16:31] <mdz> the DVD tests have found some bugs
[16:31] <marjo> slangasek: practice makes perfect, but i agree w/ you
[16:32] <mdz> bug 495194 notably which seems potentially DVD-specific
[16:32] <marjo> the more we get testers in the groove now, i think will make things go smoother later
[16:33] <slangasek> ok
[16:33] <marjo> == Bugs summary ==
[16:33] <marjo> [16:33] <marjo> 26 bugs unfixed
[16:33] <marjo> Critical - 3
[16:33] <marjo> #489791  	 Compilation fails because of changed interface in libpoppler  		Fix Released
[16:33] <marjo> #491342 	assembly fails to build on armel/lucid												Fix Released
[16:33] <marjo> #494027 	After upgrade to KDE 4.4 beta in Lucid, no KDE applications will start.	Fix Released
[16:33] <marjo> High - 5
[16:33] <marjo> Medium - 2
[16:33] <marjo> Low - 1
[16:33] <marjo> Undecided - 15
[16:33] <marjo> [16:33] <marjo> 3 bugs fixed
[16:33] <marjo> High - 1
[16:33] <marjo> Medium - 1
[16:33] <marjo> Unknown - 1
[16:34] <mdz> marjo: the 3 critical bugs under 'unfixed' all say 'fixed released'; what does that mean?
[16:34] <slangasek> all three of the *un*fixed issues are marked "Fix released"?
[16:34] <marjo> full report will follow in email
[16:34] <marjo> that means at the time report was written, they were showing critical and not fixed released yet
[16:35] <marjo> when i looked this morning, they were "fix released"
[16:35] <marjo> already
[16:35] <slangasek> ok
[16:35] <marjo> timing issue, i think
[16:35] <marjo> that's all for QA
[16:35] <slangasek> is anyone triaging the 'undecided' bugs to make sure they get importances and targets set appropriately?
[16:36] <marjo> yes
[16:36] <slangasek> ok, thanks
[16:36] <slangasek> anyone have questions for QA?
[16:37] <marjo> thx all
[16:37] <slangasek> [TOPIC] DX Team
[16:37] <MootBot> New Topic:  DX Team
[16:37] <slangasek> marjo: thanks
[16:37] <slangasek> njpatel: hi, are you covering for DX?
[16:38] <njpatel> slangasek: I can try :)
[16:38] <slangasek> the one agenda item I had up for DX is dx-lucid-xsplash - does that appear to be on track?
[16:39] <slangasek> I gather that the next step is one you're waiting for scott on
[16:39] <njpatel> I'm finding out
[16:39] <slangasek> do you want us to move along and come back to you?
[16:39] <Keybuk> waiting for me?
[16:39] <Keybuk> or another scott?
[16:39] <slangasek> Keybuk: you
[16:40] <njpatel> slangasek: dbarth seems to have not made it, so can we come back to dx? I'll try and get some info 'till then
[16:40] <Keybuk> slangasek: I'm not aware of anyone waiting on me for anything
[16:40] <slangasek> Keybuk: "get xsplash prototype from scott: TODO"
[16:40] <Keybuk> slangasek: DX haz it
[16:40] <slangasek> ah, whiteboard needs updating then :)
[16:40] <slangasek> njpatel: yep, sounds good
[16:40] <slangasek> [TOPIC] Mobile Team
[16:40] <MootBot> New Topic:  Mobile Team
[16:40] <slangasek> asac, ogra: hello
[16:40] <asac> https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:40] <slangasek> [LINK] https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:40] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/ReleaseStatus/Lucid
[16:40] <ogra> here
[16:41] <asac> so we had problems with hardware and image production
[16:41] <asac> but managed to get a bootable image in the end ;)
[16:41] <asac> for imx51
[16:41] <ogra> (we always have probs with HW production :) )
[16:41] <asac> so not much progress was done on other bugs this week
[16:42]  * slangasek nods
[16:42] <ogra> it had installer issues due to a cryptsetup bug which we fixed today
[16:42] <asac> also our dove port owner is on vacation ... so we need to catch up next week
[16:42] <asac> yeah. 495161: cryptsetup: initramfs-tools cryproot hook adds >10M to initrd size ... got fixed now
[16:43] <slangasek> ogra, asac: is the missing /lib/modules/$(uname -r)/kernel/arch/.../crypto directory also a bug, btw?
[16:43] <ogra> nope
[16:43] <asac> slangasek: seems its  built-in
[16:43] <slangasek> ok
[16:43] <ogra> our encryption device is compiled in on the SoC
[16:43] <ogra> we need to cross check on dove though
[16:43] <slangasek> glad that got fixed; too bad it missed alpha-1
[16:44] <asac> yeah. but there is a workaround you can use to install the image ... so its not that bad ;)
[16:44] <ogra> yeah
[16:44] <ogra> well, we have a workaround i'Äm just trying out
[16:44] <ogra> but i discovered other odd things, seems compcache doesnt behave niocely on armel atm
[16:45] <ogra> i'll have ot research that more before filing a bug
[16:45] <asac> on the blueprint side we are slightly behind, but there are ab unch of low hanging fruits we can go for to get below the trend line for alpha-2
[16:45] <asac> so i think we are on track there in general
[16:46] <ogra> (the chart robbiew pointed to didnt look like we're behind)
[16:46] <slangasek> hum, if you're doing the low-hanging fruit to get below the trend line, doesn't that mean you'll be pressed at the end? :)
[16:46] <asac> slangasek: no. those were tasks to be done in the beginning anyway. its not picking easy stuff from the end
[16:47] <slangasek> you guys have several specs marked essential for alpha-2; anything that should be discussd there?
[16:47] <slangasek> gcc v7+thumb2 is in the archive for a while, I know - are the build failures manageable at this point?
[16:48] <asac> so far yes. but i expect more to come
[16:48] <slangasek> alright
[16:48] <asac> dave martin from arm prepared a list of packages that are potential causing issues. so we will go through that proativeyl now
[16:49] <asac> (with help of kees)
[16:49] <slangasek> ok, great
[16:49] <asac> that list was supposed to be on the thumb2 wiki by now
[16:49] <asac> will prod him
[16:49] <asac> the others essential ones look good
[16:49] <asac> 2d-launcher waits for a code drop
[16:50] <asac> but once we have that it should go quick
[16:50] <ogra> uboot just needs code cleanup of the proof of concept and different defaults in the package
[16:50] <slangasek> who's responsible for that code drop?
[16:50] <asac> OEM
[16:50] <ogra> one or two days at most
[16:51] <slangasek> (should that be a work item on https://blueprints.launchpad.net/ubuntu/+spec/mobile-lucid-une-2d-launcher, assigned to them?)
[16:51]  * asac  checks
[16:51] <asac> its in status atm
[16:51] <slangasek> yes, which means it doesn't get on the reports :)
[16:51] <slangasek> (AFAIK)
[16:52] <asac> i will check whats the status
[16:52] <asac> and add it as work item
[16:52] <slangasek> thanks
[16:52] <asac> if there seems to be something not on track
[16:52] <slangasek> anything else on mobile?  any questions for them?
[16:53] <asac> not from me
[16:53] <ScottK> FYI, qt4-x11 is now built on armel
[16:53]  * ogra noticed that :)
[16:53] <ogra> ScottK, what about the rest of KDE land ?
[16:53] <slangasek> ScottK: how did your kubuntu arm build fare?
[16:54] <ScottK> Currently kde4libs FTBFS due to qreal stuff.
[16:54] <ogra> slangasek, mostly FTBFS due to qt
[16:54] <ScottK> Riddell has a test build going in the porter's PPA now.
[16:54] <ScottK> So we've started work.
[16:54] <slangasek> the image build, I meant
[16:54] <slangasek> or did you never get that far?
[16:54] <ogra> didnt NCommander fix that several times already ?
[16:54] <ogra> (qreal)
[16:54] <ScottK> slangasek: We haven't been installable for quite some time
[16:54] <asac> ScottK: Riddell: remember to file bugs with armel/armv7 tag and ubuntu-armel subscribed
[16:55] <ogra> yeah
[16:55] <ScottK> So no Kubuntu builds for armel yet
[16:55] <ScottK> (ISO builds)
[16:55]  * slangasek nods
[16:55] <asac> do we need to make a spec or something we can track for kde-arm?
[16:56] <ScottK> ogra: NCommander has been a huge help, but we get new qreal stuff every release.  We've talked to upstream and they're trying to train people to avoid it.
[16:56] <ScottK> asac: No, we'll do it as part of our Kubuntu work.
[16:56] <asac> ok
[16:56] <ScottK> ... and scream when we need help.
[16:56] <ogra> asac, we just need to give them the buildds from time to time :)
[16:56] <ogra> so the big chunk can be uploaded
[16:57] <asac> ok. cool. thx ScottK.
[16:57] <slangasek> anything els?
[16:57] <slangasek> +e
[16:58] <ogra> not here
[16:58] <asac> move on.
[16:58] <slangasek> [TOPIC] Server Team
[16:58] <MootBot> New Topic:  Server Team
[16:58] <ttx> o/
[16:58] <slangasek> asac, ogra: thanks
[16:58] <slangasek> ttx: hello
[16:58] <ttx> Team status updated at https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:58] <ttx> now with graphs !
[16:58] <slangasek> njpatel: shout when you're ready for me to come back to you, btw
[16:58] <slangasek> [LINK] https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:58] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/ReleaseStatus
[16:59] <ttx> Testing of ISOs early in the week allowed us to spot the most blocking issues for alpha1
[16:59] <ttx> and fix them before the candidate was baked
[16:59] <njpatel> slangasek: no new news unfortunately :( It seems like the only change is receiving the prototype from scrott
[16:59] <njpatel> er, scott
[16:59] <ttx> all in all alpha1 is pretty good, with Eucalyptus 1.6.1 landed and usable
[17:00] <ttx> we'll break that next week by going to 1.6.2
[17:00] <ttx> Progress on  the alpha 2 targeted spec is OK, as the burndown charts nicely show
[17:00] <ttx> specs*
[17:01] <ttx> Alpha1 ISO testing uncoeverd a few bugs that we targeted to Lucid
[17:01] <ttx> the most painful one being bug 494595, because it's difficult to investigate
[17:02] <ttx> That's about it from us... questions ?
[17:04] <slangasek> server-lucid-uec-testing says there should be testing happening at A1, but the test plans aren't written yet - is that in progress somewhere?
[17:04] <jiboumans> slangasek: the spec IS to create tests
[17:05] <slangasek> so the work items about testing at a1 should be dropped?
[17:05] <ttx> jiboumans: right there are some abusive work items in that spec
[17:05] <mdz> slangasek has a point, there are work items due for A1
[17:05] <mdz> ttx: abusive?
[17:05] <ttx> or I'd say "optimistic"
[17:05] <mdz> I'd say "late"
[17:05] <mdz> :-)
[17:06] <jiboumans> ah, i thought he was referring to the wiki section of 'test plan'
[17:06] <jiboumans> right, late is the right answer in that case. alpha1 was a 'nice to have', alpha2 is the real target
[17:06] <slangasek> ok
[17:06] <ttx> well, we applied the test plan as it currently stands -- which is an empty one :)
[17:07] <jiboumans> (which is why the spec itself is targeted for alpha2)
[17:07] <jiboumans> practically, mathiaz is on holiday and we lack some of the hardware to do the tests
[17:07] <mdz> jiboumans: we can use alpha 1 to exercise the test infrastructure when it's ready
[17:07] <jiboumans> mdz: exactly
[17:07] <slangasek> when is mathiaz back from holiday?
[17:07] <ttx> wednesday.
[17:08] <mdz> though it won't support all of the configurations
[17:08] <jiboumans> next wednesday, the 16th
[17:08] <mdz> so we should change "for A1" to "on A1" I suppose
[17:09] <ttx> mdz: i'm on it.
[17:09] <slangasek> ok, so we probably won't see much progress on this by next week either... not too many more weeks before alpha-2, and that's a long list of work items - you guys are still comfortable that this is going to make it for alpha-2?
[17:09] <jiboumans> slangasek: hardware delivery permitting
[17:10] <slangasek> ok
[17:10] <slangasek> anything else on server?
[17:10] <ttx> fixed.
[17:11] <slangasek> [TOPIC] DX Team
[17:11] <MootBot> New Topic:  DX Team
[17:11] <slangasek> ttx, jiboumans: thanks
[17:12] <slangasek> njpatel: "the only change is receiving the prototype from scott" - so everyone involved knows what needs to happen next?
[17:12] <slangasek> (i.e., they're aware they're unblocked by Keybuk, even if the whiteboard isn't)
[17:13] <njpatel> slangasek: yes -- and in case david doesn't know, I've already sent him a mail
[17:13] <slangasek> ok
[17:13] <slangasek> does anyone else have other concerns to raise with DX?
[17:14] <slangasek> njpatel: you get off easy today, then :)
[17:14] <slangasek> [TOPIC] Kernel Team
[17:14] <MootBot> New Topic:  Kernel Team
[17:14] <slangasek> apw: hi
[17:14] <apw> Overall Kernel Team status is summarised at the URL below, including the items called out in the agenda.  The AppArmor item from last week did not make the Alpha-1 upload due to a last minute kitten killer, but will be in the first upload of Alpha-2.  So far our main alpha-2 deliverables are on track, ubuntu-delta updates are ahead of schedule.
[17:14] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[17:14] <njpatel> slangasek: sweet :)
[17:14] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid
[17:14] <apw> Note of caution regarding the embedded burn down charts, it seems we have lost some 10 items since yesterday, and I have not yet figured out where they have gone.  I believe we would remain below the trend line ... but ...
[17:14] <apw> Lucid kernel update is ready for upload post Alpha-1, this contains a large number of updates to ubuntu drivers.  Of note we have an updates AppArmor matching that going upstream, also we are enabling KMS for ATI Radeon (x-team is aware).  This also includes the first patches to help with the boot performance goal.
[17:16] <slangasek> nice
[17:18] <slangasek> no questions here
[17:18] <slangasek> anyone else?
[17:18] <Riddell> I didn't give a Kubuntu update, it would have said we got KDE SC 4.4 beta 1 uploaded
[17:19] <Riddell> and that beta 2 is due to be tagged sometime next week
[17:19] <slangasek> Riddell: I meant "anyone else have kernel issues to mention" :)
[17:20] <Riddell> oh right :)
[17:20] <slangasek> (but thanks for the report)
[17:21] <slangasek> [TOPIC] Security Team
[17:21] <MootBot> New Topic:  Security Team
[17:21] <slangasek> apw: thanks
[17:21] <slangasek> jdstrand: hi
[17:21] <jdstrand> hi
[17:22] <jdstrand> so, our status page moved to https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:22] <slangasek> [LINK] https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:22] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/ReleaseStatus/Lucid
[17:23] <jdstrand> there isn't a lot to report (like last week). Due to the nature of the security team's work (ie security updates take precedence over dev work), we aren't committing to alpha-2 stuff
[17:23] <jdstrand> that said, we are plugging away at our specs as time allows, and are so far on track
[17:24] <jdstrand> no problems so far
[17:24] <jdstrand> that's pretty much it for now. any questions for the security team?
[17:25] <slangasek> not from me
[17:26] <slangasek> anyone else?
[17:26] <slangasek> [TOPIC] Foundations Team
[17:26] <MootBot> New Topic:  Foundations Team
[17:26] <slangasek> jdstrand: thanks
[17:26] <slangasek> robbiew: around?
[17:26] <jdstrand> sure :)
[17:26] <slangasek> cjwatson: ping?
[17:27]  * robbiew recalls him needing to run an errand, but I thought he had arranged for backup :/
[17:27] <ScottK> cjwatson: is on holiday today.
[17:27] <ScottK> (I think)
[17:27] <slangasek> [LINK] https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:27] <MootBot> LINK received:  https://wiki.ubuntu.com/FoundationsTeam/ReleaseStatus/Lucid
[17:28] <robbiew> we're under the line for Alpha2...so things are good ;)
[17:28] <slangasek> huh, looks like we also lost some work items in the latest report
[17:28] <robbiew> the alpha 2 chart was broken
[17:28] <robbiew> cjwatson noticed yesterday and fixed it
[17:28] <robbiew> well...asked pitti to fix it ;)
[17:29] <slangasek> and that's why the main chart has fewer work items now? ok
[17:29] <robbiew> um..yeah
[17:29] <robbiew> heh
[17:30] <slangasek> does dbarth know he has a workitem for foundations that blocks an alpha-2 spec?
[17:30] <robbiew> the xsplash security review one?
[17:30] <slangasek> I don't think the burndown charts address letting people from other teams /know/ they're assigned to workitems
[17:30] <slangasek> robbiew: "develop  greeter offering choice between "Try Ubuntu without installing" and "Install Ubuntu""
[17:31] <robbiew> ah
[17:31] <robbiew> yes
[17:31]  * robbiew was cc'd on an email from cjwatson
[17:31] <robbiew> to dbarth
[17:31] <slangasek> ok
[17:31] <robbiew> so he /should/ know
[17:31] <slangasek> not worrying, then
[17:31] <robbiew> fwiw, I think the assignee of the blueprint should let others know
[17:32] <slangasek> agreed
[17:32] <slangasek> anyone have any questions on foundations?
[17:32] <robbiew> and just a shout out for plymouth being uploaded and working....at least for me ;)
[17:32] <slangasek> I need to test that after the meeting :)
[17:32] <robbiew> in universe...but MIR has been submitted
[17:33] <ScottK> Python coordination with Debian is progressing, but is taking a lot of effort.
[17:33] <robbiew> \o/
[17:33] <ScottK> slangasek: I sent a mail to u-d-a on Boost that needs to be moderated.
[17:34] <slangasek> (moderated)
[17:34] <ScottK> Thanks.
[17:34] <slangasek> anything else on foundations?
[17:35] <slangasek> [TOPIC] MOTU
[17:35] <MootBot> New Topic:  MOTU
[17:35] <ScottK> Nothing to report.
[17:35]  * ScottK didn't have time to work on the binary removal spec
[17:36] <slangasek> is there someone else who could help with some of that, while you're busy with python?
[17:37] <ScottK> Anyone who's got a little time and can do some grep/shell or python work to sort through stuff
[17:37]  * ScottK can provide advice.
[17:37] <slangasek> but you don't have a volunteer in mind, ok :)
[17:38] <james_w> just a note that when the code on piware is updated from the branch and works again things like this should work:
[17:38] <james_w> http://www.piware.de/workitems/global/lucid/report.html#james-w
[17:38] <MootBot> LINK received:  http://www.piware.de/workitems/global/lucid/report.html#james-w
[17:38] <RoAkSoAx> ScottK, i do!
[17:38] <slangasek> james_w: oh, nice
[17:38] <james_w> which will take you directly to your list of all workitems across all teams
[17:38] <ScottK> RoAkSoAx: Excellent.  Let's chat after the meeting.
[17:38] <RoAkSoAx> ScottK, sure!
[17:38] <ScottK> Any other questions for MOTU?
[17:38] <slangasek> [ACTION] ScottK and RoAkSoAx to discuss hand-off of part of the binary removal spec
[17:38] <MootBot> ACTION received:  ScottK and RoAkSoAx to discuss hand-off of part of the binary removal spec
[17:39] <slangasek> RoAkSoAx: great, thank you :)
[17:39] <slangasek> no questions here
[17:39] <RoAkSoAx> slangasek, no prob :)
[17:39] <slangasek> anything else before we wrap?
[17:39] <slangasek> #endmeeting
[17:39] <MootBot> Meeting finished at 11:39.
[17:39] <slangasek> done.  thanks, folks!
[17:41] <ScottK> RoAkSoAx: Would you please join #ubuntuwire
[17:42] <asac> thx