[14:00] <NCommander> #startmeeting
[14:00] <MootBot> Meeting started at 08:00. The chair is NCommander.
[14:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:00]  * ogra stumbles in
[14:00] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20091006
[14:00] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20091006
[14:00] <NCommander> [link] http://piware.de/workitems/mobile/karmic/report.html
[14:00] <MootBot> LINK received:  http://piware.de/workitems/mobile/karmic/report.html
[14:00] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Roadmap
[14:00] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Roadmap
[14:00]  * NCommander waits for his coffee to cool
[14:00] <paulliu> hi
[14:00] <ogra> how about you call people by name first ? :)
[14:01] <dyfet> here
[14:01] <lool> hey
[14:01]  * GrueMaster mumbles incoherently.  
[14:01]  * NCommander pours coffee on GrueMaster, StevenK, JamieBennett, 
[14:01] <JamieBennett> :P
[14:01] <lool> davidm bjf njpatel: poke
[14:01] <davidm> hi NCommander
[14:01] <NCommander> JamieBennett, coffee is a way of life on this team
[14:01] <NCommander> morning davidm
[14:02] <JamieBennett> I have my waayyyy oversized coffee cup in hand
[14:02] <davidm> Coffee, mmmm Good
[14:02] <ogra> NCommander, brits != coffee :)
[14:02] <ogra> NCommander, brits == tea
[14:02] <JamieBennett> ogra: Not necessarily
[14:02] <ogra> oh, JamieBennett might be an exception :)
[14:02] <JamieBennett> Coffee and Green Tea for me
[14:03]  * NCommander has his new "interesting" blend of coffee beans, black.
[14:03]  * ogra always thought tea and marmaid make you a ture brit :)
[14:03] <ogra> *true even
[14:03] <NCommander> Oooh, marmaid ...
[14:03] <JamieBennett> orgra: that's tea and scones
[14:03] <ogra> heh
[14:03] <NCommander> JamieBennett, your lucky though, you get Marmite
[14:03] <mvo> green tea++
[14:03] <NCommander> Its a PAIN to fine in the united states
[14:03]  * NCommander gives it another minute before actually starting
[14:03] <JamieBennett> I'll bring some over for UDS ;)
[14:03] <NCommander> JamieBennett, !
[14:04] <NCommander> JamieBennett, yay!
[14:04] <paulliu> mermaid?
[14:04] <ogra> lol
[14:04] <GrueMaster> wake me when the real meeting starts.
[14:04] <NCommander> paulliu, I'll introduce you to it
[14:04]  * NCommander pokes StevenK 
[14:05] <ogra> s/it/her/ ?
[14:05] <NCommander> No StevenK ...
[14:06] <lool> 10% of meeting time already flew by; let's move on
[14:06] <NCommander> [topic] Action Item Review
[14:06] <MootBot> New Topic:  Action Item Review
[14:06] <NCommander> [topic] dyfet to move lubuntu seed to proper location and enable amd64
[14:06] <MootBot> New Topic:  dyfet to move lubuntu seed to proper location and enable amd64
[14:06]  * StevenK arrives
[14:06] <StevenK> Sorry guys
[14:06] <dyfet> New architectures (amd64 included) were enabled
[14:06] <NCommander> dyfet, so I can run lubuntu on my ia64? :-)
[14:06] <lool> I tested the RTC fix and it doesn't work for me
[14:06] <ogra> did it move ?
[14:06] <NCommander> ah, ok
[14:06] <dyfet> yes
[14:07] <lool> Neither on babbage 2.0 nor on 2.5
[14:07] <NCommander> [topic] Current Items
[14:07] <MootBot> New Topic:  Current Items
[14:07] <ogra> where to ?
[14:07] <lool> Even after nights of charing
[14:07] <lool> *charging
[14:07] <NCommander> lool, this might be a stupid suggestion, but is it possible the RTC battery has been discharged for so long that it won't charge anymore/
[14:07] <dyfet> NCommander: and on your sparc and ia64 too ;)
[14:07] <ogra> dyfet, where did it move to ?
[14:07] <lool> dyfet: the current package says: seed_base: bzr+ssh://bazaar.launchpad.net/~lubuntu-desktop/+junk,bzr+ssh://bazaar.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/
[14:07] <NCommander> lool, my powermac's batteries are notourious for doing that.
[14:08] <lool>  -- David Sugar <david.sugar@canonical.com>  Thu, 17 Sep 2009 15:52:01 -0400
[14:08] <GrueMaster> dyfet: will there be daily images available on cdimage.ubuntu.com?
[14:08] <lool> GrueMaster: No
[14:08] <dyfet> It was kept in the community repository because that is what the community wanted
[14:08] <ogra> NCommander, read the bug :)
[14:08]  * NCommander coughs
[14:08] <NCommander> Anyway
[14:08] <dyfet> GrueMaster: we did not commit to having lubuntu spins, just a meta
[14:08] <ogra> NCommander, we measured voltage
[14:08] <lool> dyfet: The problem is with the /+junk part
[14:08] <lool> dyfet: This is what I've complained about since 3 weeks+
[14:08] <NCommander> ogra, too geeky!
[14:08] <lool> dyfet: It takes 5 minutes to fix it
[14:08]  * NCommander should probably have a multimeter though
[14:08] <ogra> .oO(it would be good if we wouldnt discuss two topics at once)
[14:09] <lool> dyfet: So plesae push to /ubuntu-seeds/lubuntu.karmic and update lubuntu-meta to match
[14:09] <dyfet> lool: ok
[14:09] <ogra> mr. chair ...
[14:09] <lool> dyfet: We've lost more time tracking this than fixing it
[14:09]  * ogra looks at NCommander 
[14:09] <NCommander> [action] dyfet and lool to move lubuntu seed to proper location and push the package
[14:09] <MootBot> ACTION received:  dyfet and lool to move lubuntu seed to proper location and push the package
[14:09] <NCommander> There
[14:09] <NCommander> [topic] Specification Review
[14:09] <MootBot> New Topic:  Specification Review
[14:09] <lool> I cant move it, I'm in ~lubuntu-dev
[14:09] <NCommander> [link] https://blueprints.edge.launchpad.net/~canonical-mobile?show=all
[14:09] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/~canonical-mobile?show=all
[14:10] <lool> GrueMaster: Did you look into trimming down UNR this week?
[14:10] <NCommander> oh wow, eveyrthing ont he spec page is either implemented or deferred
[14:10] <NCommander> so ..
[14:10] <GrueMaster> No, I have been focusing on UMR.
[14:10] <NCommander> [topic] UNR Status
[14:10] <MootBot> New Topic:  UNR Status
[14:10] <StevenK> Is Wubi deferred then?
[14:10] <lool> NCommander: Well some work items are still open
[14:10] <StevenK> Wubi just needs testing, but my Windows install went kaboom
[14:10] <ogra> NCommander, it would be nice if you wouldnt race through the items so fast
[14:11] <lool> NCommander: the specs are considered implemented in that they are mostly done and we only need to fix optional stuff but we should review them still
[14:11] <StevenK> (Who woulda thunk it)
[14:11] <NCommander> StevenK, you installed Windows?
[14:11] <ogra> we start getting a lot overlapping discussions here
[14:11] <NCommander> right, ok, hold on
[14:11] <lool> NCommander: he did but StevenK is blockde on a wubi bug
[14:11] <NCommander> [topic] Spec Discussion
[14:11] <MootBot> New Topic:  Spec Discussion
[14:11] <lool> wubi and unr translations are blocked outside of mobile team
[14:12] <lool> release team knows about wubi, kyle knows about trasnlations
[14:12] <StevenK> lool: I've heard that wubi is, or should be fixed
[14:12] <lool> Oh cool
[14:12] <ogra> there was some work during beta release
[14:12] <lool> Apart of that moblin moving to universe is still in progress
[14:12] <lool> and lsb testing will continue til release
[14:12] <StevenK> I was planning to test it today, but Windows is ka-boom
[14:12] <lool> So we only need to check for wubi moblin and UNR status next week
[14:13] <davmor2> StevenK: today's installer is a bit borked which isn't helping wubi
[14:13] <paulliu> lool: there will be a 3-rd run of sync to universe. Is it still able to sync after Beta??
[14:13] <lool> paulliu: Probably
[14:13] <paulliu> lool: ok.
[14:13] <lool> paulliu: new stuff or moblin stuff I would guess so
[14:13]  * NCommander recommends anyone who has a machine capable of running UNR and has a Windows install should help test
[14:13] <lool> NCommander: Ok to move on for me
[14:13] <paulliu> lool: Why moblin spec is not in that page?
[14:13] <paulliu> I mean blueprints
[14:13] <NCommander> anyone else got anything?
[14:13] <lool> paulliu: It's on http://piware.de/workitems/mobile/karmic/report.html
[14:14] <paulliu> ok. thanks
[14:14] <NCommander> [topic] UNR Status
[14:14] <MootBot> New Topic:  UNR Status
[14:14] <lool> paulliu: Should appear now
[14:15] <lool> UNR status is good; I pushed the theme update, desktop-switcher removal
[14:15] <lool> and added software-center to favorites
[14:15] <StevenK> I concur
[14:15] <lool> didnt test that last change
[14:15] <plars> ?
[14:15] <lool> Someone saw it in favorites?
[14:15] <lool> I just pushed this morning
[14:15] <plars> ah
[14:15] <lool> But an update should get it
[14:15] <StevenK> It wouldn't have hit the daily then
[14:16] <lool> The rest was pushed yesterday though
[14:16] <ogra> plars, you dont test in your sleep ? what kind of QA guy are you ?
[14:16] <lool> I pushed the latest upstream releases
[14:16] <lool> StevenK: did I miss any tarball?
[14:16] <StevenK> lool: I'll check that tomorrow morning
[14:16] <plars> ogra: I could wind up filing some interesting bugs that way
[14:16] <lool> Concerning seeds, I pulled the latest changes; StevenK did I miss any there?
[14:16] <ogra> hehe
[14:16] <StevenK> lool: Not that I saw.
[14:17] <lool> I expect some more icon updates for bugs discovered after the lsat update
[14:17] <lool> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:17] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:17] <lool> 430277 > will wontfix
[14:17] <lool> The rest if upstream
[14:18] <lool> Ok nothing else for me on UNR
[14:18] <lool> StevenK: you?
[14:18] <StevenK> lool: Nope, I'm good
[14:18] <NCommander> [topic] UMR Status
[14:18] <MootBot> New Topic:  UMR Status
[14:19] <paulliu> TMC5 ported is done. Moblin2.1 is done.
[14:19] <lool> Wow
[14:19] <lool> Cool
[14:19] <lool> paulliu: Is 2.1 final?
[14:19] <paulliu> Not yet. But we are follow up them now.
[14:19] <lool> I did the /etc/apt/preferences fixes; took me 2.5 days to get them right  :-(
[14:20] <NCommander> lool, ow
[14:20] <paulliu> And anerley can be sync to universe now. So anjal (anjal-anerley) can also be in universe.
[14:20] <lool> High prio issues on my radar: fixing /etc/apt/sources.list after install and fixing the APT popup during install (might relate)
[14:20] <lool> the preferneces file didn't help these bugs though
[14:20] <lool> paulliu: excellent
[14:20] <lool> paulliu: You have a double-build anjal already?
[14:20] <StevenK> lool: So /etc/apt/sources.list can be fixed with a preseed file change
[14:20] <paulliu> lool: Yes. Already.
[14:21] <lool> StevenK: Good to know; could you share that in the bug?
[14:21] <paulliu> lool: We just need to debdiff the one in PPA and in universe and file the bug.
[14:21] <lool> paulliu: You rock
[14:21] <ogra> ++
[14:21] <plars> nice
[14:21] <lool> paulliu: Anything else release worthy for UMR?
[14:21] <StevenK> lool: What's the bug number?
[14:21] <lool> I personally can hardly run UMR
[14:22] <GrueMaster> Next step would be to have Moblin installed with UNR & KNR.  Makes for one hell of a demo install.
[14:22] <paulliu> lool: No. We need another FFe for 3-rd run of syncing. Including moblin-mutter and moblin-panel-*
[14:22] <lool> On my eeepc 701sd, it's slow as hell (I mean I need to wait 5 secs for text to appear in terminal)
[14:22] <StevenK> GrueMaster: Kubuntu Netbook is not a remix
[14:22] <lool> In vbox it's similar, slightly better, but cant run ubiquity
[14:22] <lool> StevenK: https://bugs.launchpad.net/ubuntu-moblin-remix/+bug/420048
[14:23] <lool> paulliu: We need a new FFE?
[14:23] <lool> paulliu: Are these new packages?
[14:23] <paulliu> lool: We have to fix the sources.list in Ubiquity, right?
[14:23] <ScottK> StevenK: Thanks.
[14:23] <paulliu> lool: yes, new packages.
[14:23] <lool> paulliu: Well StevenK says it can be done in preseed (cdimage/debian-cd stuff)
[14:23] <lool> paulliu: Ok; I think it's ok to just use the same FFE but feel free to file a new one if you prefer (weren't mentionnde in first FFE)
[14:23] <lool> ScottK: Your opinion?
[14:23] <paulliu> lool: OK.
[14:24] <lool> ScottK: New FFE needed or ok to reuse the moblin FFE when pushing entirely new packages to universe?
[14:24] <lool> (moblin specific)
[14:24] <lool> Our moblin ffe for karmic is https://bugs.launchpad.net/ubuntu/+bug/425547
[14:24] <ScottK> lool: I figured your FFe was open season for whatever moblin stuff you thought best.
[14:24] <lool> ScottK: Ok thanks
[14:24] <paulliu> ScottK: thanks.
[14:24] <lool> paulliu: I think it's ok as these are fully new packages
[14:24] <lool> paulliu: anjal needs a separate FFE though
[14:24] <lool> and a reviewer
[14:25] <paulliu> lool: ok.
[14:25] <lool> StevenK: Could you review the anjal changes for merging in kramic?
[14:25] <lool> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-moblin
[14:25] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-moblin
[14:25] <lool> So good
[14:25] <lool> StevenK: Anything else we need to cover for moblin?
[14:26] <StevenK> lool: I can, if paulliu points me at when it's filed
[14:26] <lool> (UNR update -- netbook remix -- njpatel tells us that we should expect some bug fixes updates before end of week)
[14:26] <StevenK> lool: Not that I can think of.
[14:26] <paulliu> StevenK: Not yet. I'll file that bug soon.
[14:26] <lool> paulliu: Can you sub StevenK to the anjal update so that we can quickly review + sponsor it once the FFE is approved?
[14:27] <paulliu> lool: ok.
[14:27] <lool> My only concern is to not break moblin with major updates near final
[14:27] <lool> or rc
[14:27] <lool> So if we just fix what we mentionned and release, I'm happy
[14:27] <lool> NCommander: Ok to move on
[14:27] <NCommander> [topic] Any Other Business
[14:27] <MootBot> New Topic:  Any Other Business
[14:27] <lool> Hmm we didn't cover ARM bugs
[14:27] <lool> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel
[14:27] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel
[14:28] <ogra> imx kernel bugs seem to actually get forward
[14:28] <lool> I'm getting help from jk on the ethernet issue
[14:28] <ogra> yeah
[14:28] <lool> he provided two test kernels this morning
[14:28] <ogra> bjf, i added a bunch of hacks to bug 438680
[14:28] <lool> I have the feeling some easy bugs are not taken care of
[14:28] <bjf> I looked into the RTC bug, applied Amitk's suggestion and it didn't help (it made it worse) ...
[14:28] <lool> I think we should have had weekly meetings with kernel team to discuss them earlier
[14:28] <ogra> bjf, look at my last comment
[14:28] <bjf> ogra, I've just applied those and am building
[14:29] <ogra> there are multiple options
[14:29] <lool> As in, every week review the armel bugs with kernel team
[14:29] <ogra> (for RTC)
[14:29] <bjf> ogra, will check on it
[14:29] <ogra> i think the disabled one is the jaunty one amit referred to actually
[14:30] <lool> Things which are not filed as bugs yet (I think) but would be nice to have if time permits: 2d GPU enabling patch for babbage and lange 5.1 patches merged in
[14:30] <ogra> bjf, also the regulator messages seen in the bootmsg bug imply that something doesnt properly hook into the kernel subsystem
[14:30] <bjf> ogra, will look at it again, and retest
[14:30] <ogra> lool, ++
[14:30] <lool> Dove is in relatively good shape except that partman-uboot is really needed
[14:30] <ogra> well, alternate for imx51 doesnt work at all yet
[14:30] <lool> It would also be nice to have better documentation for various installer options and to provide an uboot for Y1 boards, but overall it's ok
[14:31] <bjf> am also hoping to look at bug 438687 today
[14:31] <ogra> we're still waiting for NIC modules for netinst images
[14:31] <lool> ogra: We are?
[14:31] <ogra> and the general alternate dies on searching for the CD
[14:31] <lool> ogra: I though nic was builtin?
[14:31] <ogra> lool, yes, the bug is fix committed
[14:31] <lool> Hmm ok
[14:31] <ogra> the builtin NIC doesnt work at all
[14:31] <bjf> ogra, do you just need a build?
[14:31] <ogra> though i see it
[14:31] <lool> I thought it worked again now?
[14:31] <ogra> but cant connect
[14:31] <lool> Except in NM
[14:31] <ogra> not in d-i
[14:32] <lool> Ouch that's odd
[14:32] <ogra> right, in normal systems it works just fine
[14:32] <ogra> yes
[14:32] <lool> bjf: jk has WIP patches on bug 438687
[14:32] <ogra> i discovered that during beta testing but postponed furtehr research
[14:32] <lool> bjf: Ann from FSL will also help with what she can
[14:32] <lool> bjf: perhaps one bug worth your attention is the audio one
[14:32] <ogra> ++
[14:32] <lool> It has relevant hints and suggestions, just not a tested patch
[14:32] <ogra> we need to test the audio apps
[14:33] <ogra> its way to late to even fix them if we find issues
[14:33] <lool> Outside of kernel stuff, there's also the toolchain situation
[14:33] <ogra> but we should at least be able to list them before release
[14:33] <lool> doko (hey) pushed a new binutils earier today
[14:33] <NCommander> ogra, maybe we should have a specification for that for lucid
[14:33] <lool> I think we miss an updated gcc-4.4 patch
[14:33] <lool> and then we should rebuild the world
[14:33] <lool> well the C++ world mostly
[14:33] <ogra> NCommander, make kernels work early enough spec ?
[14:34] <NCommander> ogra, for testing audio applications and having a set policy for it
[14:34] <doko> lool: not yet ready, tracking down some binutils gold build problems
[14:34] <lool> bjf: Thanks for helping with the imx51 bugs; they need some love right now   ;-)
[14:34] <ogra> NCommander, we have no prob testing audio apps
[14:34] <ogra> NCommander, we have no sound devices
[14:34] <lool> bjf: basically they are filling up the list of armel bugs we care about
[14:34] <NCommander> d'oh
[14:34] <bjf> lool, that's all I'm doing this week (and probably next)
[14:34]  * ogra hugs bjf for taking the blame during this week 
[14:34] <lool> bjf: Ok cool
[14:34]  * NCommander hugs bjf for his work
[14:34] <lool> bjf: Do you have anything to raise in terms of dove/imx51 status on your side?
[14:35] <lool> bjf: What would you think of a weekly kernel/mobile meeting to review armel bugs?
[14:35] <bjf> lool, not really, dove looks good to me
[14:35] <lool> Perhaps bjf+amitk+OEM kernel engineers who'd like that+ogra+NCommander+lool if around
[14:35] <ogra> NCommander, do you have the rotatoing MAC issue fixed ?
[14:35] <bjf> lool, between this meeting and the kernel team meeting in 3.5 hours do we need more?
[14:35] <ogra> lool, ++
[14:35] <lool> +Jamie too now  :)
[14:35] <NCommander> ogra, no, but if its set in u-boot, it seems to go away
[14:36] <JamieBennett> :)
[14:36] <lool> bjf: Well amitk isn't usually attending these meetings and we usually dont attend kernel meetings
[14:36] <ogra> NCommander, well, what do you do ? randomly generater one in your uboot script for each install ?
[14:36] <lool> bjf: I have the feeling other people here or in the kernel meeting would be bored if we covered status of each individual bug
[14:37] <lool> bjf: But if you think we should make room in either of these meetings, that's ok with me
[14:37] <NCommander> ogra, I brought that up on the board, but I'm not qualified to say how the MAC should be handled or not
[14:37] <bjf> lool, I guess I don't mind another meeting, need to discuss with amit when would be good for him
[14:37] <lool> bjf: let's make it simplest for you and amit
[14:38] <lool> bjf: check with him and tell us where you want us to cover armel bugs weekly in depth
[14:38] <lool> NCommander: [action] $@ ^
[14:38] <bjf> lool, ack
[14:38] <ogra> lool, oh, btw, dyfet wanted to package the fsl gstreamer codecs ...
[14:38] <lool> bjf: thanks
[14:38] <ogra> dyfet, whats the status there ?
[14:38] <NCommander> [topic] bjf to check with amit on going indepth on armel bugs
[14:38] <MootBot> New Topic:  bjf to check with amit on going indepth on armel bugs
[14:38] <ogra> (since i'm still busy with xserver and reproducing kernel issues)
[14:39] <dyfet> ogra: in progress
[14:39] <lool> Ok; anything else armel?
[14:40] <lool> Anything else at all?
[14:40] <lool> davidm: You have any queries?
[14:40] <ogra> dyfet, please make sure to contact me if you get stuck anywhere
[14:40]  * NCommander wonders when he should start hitting the spec drum
[14:40] <davidm> I'm interested in when the corrected toolchain will be in place.
[14:40] <dyfet> ogra: okay
[14:40] <lool> davidm: toolchain > first round of uploads had a broken patch; second round is failing to build for now; once it's in we can check whether it helps oo.o and also kick some rebuilds of various packges; there aren't too many and it's not a big deal, should be doable for release
[14:41] <lool> Hopefully toolchain should be built tomorrow
[14:41] <davidm> OK, make sure mono in in the queue for rebuild
[14:41] <lool> doko: What do you think?
[14:41] <ogra> davidm, mono doesnt use C++
[14:41] <lool> mono didn't show up on my list
[14:42] <davidm> lool, if you are sure
[14:42] <lool> It could be affected by other libraries
[14:42] <dyfet> ogra: the bug I have in it seems exception related
[14:42] <ogra> generally mono works fine
[14:42] <lool> I mean worst case we can give it a try, in a second batch of rebuilds perhaps
[14:42] <davidm> OK
[14:42] <doko> lool: tomorrow is optimistic, but Thu should work
[14:42] <lool> AFAIK it works at least basically; e.g. tomboy starts up
[14:42] <ogra> seems to be issues with specific functions from specific libs
[14:42] <lool> doko: Ok; good to know thanks
[14:43] <ogra> dyfet, most mono apps i tested work fine ... did you track it down to a specific lib or function ?
[14:43] <dyfet> ogra: I get corrupted stack frames, but what you suggest is plausable that it is tied to a specific library that raises an exception
[14:44] <ogra> right, else we would see it across the board
[14:44] <dyfet> ogra: agreed
[14:44] <ogra> and i personally only see banshee fail
[14:44] <ogra> though with a totally different error than you
[14:44] <lool> let's start wiht rebuilding what we know is borken and see if that improves
[14:44] <ogra> (still btw, i tested on the weekend)
[14:44] <lool> We could do a mono rebuild afterwards but I dont think it will help
[14:44] <dyfet> ogra: and I still get mine, which is different ;)
[14:45] <lool> Any other topic anyone?
[14:45] <ogra> lool, do you have your new n900 already ? and do you bring it on the WE ?
[14:45] <ogra> :)
[14:46] <ian_brasil> lool, you have an N900?
[14:46] <ian_brasil> we do not have N900 and we work for Nokia !
[14:46] <lool> ian_brasil: Sure, I have a N1010 too; you dont?
[14:46] <lool> ian_brasil: Seriously though, no I dont
[14:46] <ogra> hehe
[14:46] <JamieBennett> lol
[14:47] <lool> I find it funny that ian_brasil is on the chan and jumps in the air as soon as N900 appears  ;-)
[14:47] <ogra> yeah
[14:47]  * lool plans to buy one near end of year if price permits
[14:47] <ogra> how about MIR while you are here ?
[14:47] <lool> But not something really relevant here  ;-)
[14:47]  * NCommander is considering an N900 himself
[14:47] <ogra> any news ?
[14:47] <ian_brasil> i am waiting for the second hand market to appear
[14:47] <lool> ogra: MIR?
[14:47] <ogra> err
[14:47] <ogra> MER
[14:47] <lool> Oh
[14:48] <lool> ogra: I think ian_brasil had his own project; loosely connected to Mer
[14:48] <ogra> ah
[14:49] <ian_brasil> we talked with the Mer guys ..seems they have latest python-hildon packaged
[14:49] <lool> Not sure we need to cover it here and now though; it's karmic+1 material at this point Id guess
[14:49] <ogra> likely indeed
[14:49] <lool> ogra, ian_brasil: Let's chat about that in #ubuntu-mobile and plan that for lucid
[14:49] <lool> anything else?
[14:49] <ian_brasil> lool, ok
[14:49] <lool> NCommander: I guess you can close; thanks for chairing!
[14:50] <NCommander> #endmeeting
[14:50] <MootBot> Meeting finished at 08:50.
[14:50] <lool> NCommander: You might want to add an action for dyfet;s packaging of gst bits
[14:50] <ogra> thanks
[14:50] <NCommander> lool, will do
[14:50] <ogra> oh, yeah
[14:50] <ogra> time is getting short slowly :)
[14:50] <pitti> hello
[14:54] <pitti> cjwatson, kees, mdz, Keybuk: reminder for TB meeting in 5 mins
[14:55] <cjwatson> yes
[14:56] <mdz> pitti: here
[14:56] <mdz> bdale: welcome
[14:57] <bdale> mdz: g'morning from Colorado!
[14:57] <pitti> hey bdale
[14:57] <bdale> pitti: hi
[14:58] <cjwatson> hello. hmm, not much of an agenda this week!
[14:58] <mdz> err
[14:58] <mdz> that's not right
[14:58] <pitti> I SMSed Keybuk
[14:59] <mdz> pitti: in general, we keep WIP items on the agenda until they're complete, so that we're checking progress at each meeting
[14:59] <pitti> mdz: ok, ok; I just commented them for now, let me restore
[14:59] <bdale> where is the agenda?
[14:59] <cjwatson> https://wiki.ubuntu.com/TechnicalBoardAgenda
[14:59] <bdale> cjwatson: thanks!
[14:59] <pitti> restored, please reload agenda
[15:00] <pitti> sabdfl pinged, Keybuk doesn't seem to respond; should we wait a bit for him, or start?
[15:00] <mdz> pitti: clan has nudged sabdfl; he is in the meeting room a few meters away
[15:00] <cjwatson> I got mail from Keybuk not that long ago ...
[15:02] <mdz> pitti: sabdfl came back to his desk but has now gone off somewhere else; I recommend that we do not wait for him
[15:02] <cjwatson> we ought to go on though. How about kees?
[15:03] <pitti> pinged, but no response either
[15:03] <pitti> looking for his mobile number and SMSing him
[15:03] <mdz> pitti: I'll do that, so you can get started with the agenda
[15:03] <mdz> we're already running late
[15:04] <pitti> ok, thanks
[15:04] <pitti> #startmeeting
[15:04] <MootBot> Meeting started at 09:04. The chair is pitti.
[15:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:04] <pitti> https://wiki.ubuntu.com/TechnicalBoardAgenda is the current agenda
[15:04] <pitti> [TOPIC] Actions from previous meeting
[15:04] <MootBot> New Topic:  Actions from previous meeting
[15:04] <pitti> Keybuk to find Bdale at LinuxCon to hash out participation
[15:04] <pitti> given that bdale is here, this obviously worked :)
[15:04] <cjwatson> however
[15:05] <cjwatson> we should actually take the opportunity to talk about how the Debian relationship here is going to work
[15:05] <cjwatson> otherwise it's a bit silly :-)
[15:05] <Keybuk> I did manage to talk to bdale briefly over lunch one day at LPC
[15:05] <bdale> right, not a long chat, but useful
[15:05] <pitti> right; let's turn this into a separate agenda topic, though, shall we?
[15:05] <cjwatson> ok
[15:05]  * cjwatson defers to the chair
[15:05] <bdale> I'd be pleased to more or less observe a meeting or two, then have a discussion.  make sense?
[15:06] <pitti> [TOPIC] TB/Debian relationship
[15:06] <MootBot> New Topic:  TB/Debian relationship
[15:06] <pitti> right
[15:06] <cjwatson> if that works best for you, that's fine. Conversely, are there Debian TC IRC meetings these days that we ought to observe, or should we just follow the mailing list?
[15:07] <cjwatson> (which I do occasionally, but pretty infrequently)
[15:07] <mdz> well, I'd at least like to say that I'm glad you're here, bdale, and look forward to having Debian participation in this forum
[15:07] <bdale> just the mailing list.  one of the things Keybuk and I talked about is the notion that I can spot discussions on the TB list and try to get appropriate Debian folk to join meetings here... how that should work will be easier for me to comprehend once I've watched a couple myself
[15:07] <mdz> bdale: has cjwatson briefed you on the basics of how the technical board works?
[15:07] <bdale> mdz: right, thanks.  I'm also pleased to think we can make some goodness happen
[15:08] <bdale> mdz: more or less, yes
[15:08] <pitti> it makes sense to be in each other's meeting to ensure that we stay compatible on a large scale, like the units policy or large technical changes
[15:08] <cjwatson> I think the operative bit is "brief", but yes
[15:08] <bdale> pitti: right, there just aren't any "meetings" of the Debian TC except the BOF we try to hold at Debconf each year... it's an email-mostly and some private IRC chats kind of thing right now
[15:09] <mdz> cjwatson: did we discuss whether bdale should be on the mailing list?
[15:09] <cjwatson> we did, and I added him
[15:09] <mdz> oh good
[15:09] <cody-somerville> Hi
[15:10] <Keybuk> cody-somerville: please don't interrupt the meeting
[15:10] <pitti> ok, back to
[15:10] <pitti> [TOPIC] Actions from previous meeting
[15:10] <MootBot> New Topic:  Actions from previous meeting
[15:10] <pitti> * kees to drive sun-java6 email thread and get resolution on responsibility
[15:10] <pitti> there were two followups, but still no final resolution
[15:11] <pitti> it seems to me that we manoeuvred ourselves into a pretty bad situation with this
[15:11] <cjwatson> for bdale's context, that was the attempted removal of the non-free Sun Java 6 packages from Ubuntu in light of OpenJDK; however it turns out quite a lot of stuff still seems to need the Sun packages, and we've been trying to figure out how to get that moving effectively
[15:12] <pitti> last thing I saw was that Neil wanted to get a list of non-main packages they rely on
[15:13] <mdz> cjwatson: s/attempted/proposed/ ;-)
[15:13] <mdz> I think we can put this aside for 9.10 and put it on the list of things to consider for 10.04
[15:13] <cjwatson> the question from last meeting was essentially whether we ought to continue spending Ubuntu platform team resources on it, or conversely whether trying to move that out to our partner repository would just lead to the corporate services people asking us for help with it all the time
[15:13] <pitti> but it seems to me that we'd need to extend the sun-java6 SRU policy at least for jaunty, and won't be able to drop it in karmic just yet
[15:14] <cjwatson> we certainly need to put it aside for 9.10, but it would be rather nice to have an end in sight
[15:15] <cjwatson> however, Neil said that he was soliciting migration plans
[15:16] <pitti> so, should I ping Neil again about other packages they rely on, and some plan how to get rid of it eventually?
[15:16] <cjwatson> so perhaps the right answer is just to bring this up again at UDS for a status check?
[15:17] <mdz> cjwatson: yes, I think it should be further explored as a foundations task for 10.04
[15:17] <cjwatson> I've made a note of that
[15:17] <mdz> move on?
[15:18] <cjwatson> fine by me
[15:18] <pitti> * cjwatson to drive DMB email thread to conclusion
[15:18] <pitti> that happened today, and voting is underway
[15:18] <cjwatson> we can complete the vote quickly here if people are up-to-date on mail?
[15:18] <pitti> so for the purposes of "actions from previous meeting" this is done, and we'll have a full agenda topic about this, too
[15:19] <pitti> I just sent my +1 via mail
[15:19] <cjwatson> ok, let's proceed rather than block on that then, and I'll just exhort people (hypocritically) to get through that mail thread quickly
[15:19] <pitti> summary, cjwatson proposed to establish a minimal standard of adding new uploaders to teams:
[15:20] <cjwatson> well, dholbach did
[15:20] <pitti> documentation, declaring intent, discussion with applicant, public announcement
[15:20] <pitti> but I think it's better if everyone reads the entire mail first
[15:20] <pitti> everyone ok to finish this by mail?
[15:20] <pitti> (to avoid voting without enough context)
[15:21]  * pitti assumes "yes"
[15:21] <pitti> * Keybuk to finalize unit policy and email to TB for vote
[15:21]  * mdz falls over laughing at "up-to-date on mail"
[15:21] <Keybuk> pitti: continue to defer until I'm not getting 2,000-3,000 mails from LP a second in my INBOX
[15:21]  * bdale ^5's mdz
[15:22] <pitti> Keybuk: noted
[15:22] <pitti> [ACTION] Keybuk to finalize unit policy and email to TB for vote
[15:22] <MootBot> ACTION received:  Keybuk to finalize unit policy and email to TB for vote
[15:22] <pitti> * cjwatson to drive vote on Archive Reorg rights for ubuntu-desktop and mythbuntu in email
[15:22] <cjwatson> this is blocked on the developer membership thing
[15:22] <pitti> that depends on the former vote, right?
[15:23] <pitti> so, just pushing forward
[15:23] <pitti> [ACTION] cjwatson to drive vote on Archive Reorg rights for ubuntu-desktop and mythbuntu in email
[15:23] <MootBot> ACTION received:  cjwatson to drive vote on Archive Reorg rights for ubuntu-desktop and mythbuntu in email
[15:23] <pitti> [TOPIC] Discuss Developer membership board
[15:23] <MootBot> New Topic:  Discuss Developer membership board
[15:24] <pitti> it seems to me that the email thread is sufficient for this, or does anyone still need to discuss something here?
[15:24] <cjwatson> is there any more here beyond the mail thread?
[15:24] <pitti> :)
[15:25] <cjwatson> let's time out and move on
[15:25] <pitti> so, remaining thing here is for everyone to respond and vote
[15:25] <mdz> I've read the thread now
[15:25] <pitti> [TOPIC] Archive reorg
[15:25] <MootBot> New Topic:  Archive reorg
[15:25] <mdz> and am +1 on the four points
[15:26] <cjwatson> that's 4/6, I'll allow until tomorrow for comments and then document it
[15:26] <cjwatson> nothing on archive reorg beyond this DMB thread. I blame beta.
[15:26] <pitti> just pushing forward then, next time we should have the vote settled
[15:27] <pitti> cjwatson: btw, do you know if there's a proper kubuntu uploaders team now?
[15:27] <pitti> or should I ping Riddell to create a separate one from the "contributors/interested folks"?
[15:28] <cjwatson> pitti: I've been talking with Riddell and co about that on and off, and it came up at the last Kubuntu meeting; I believe they were going to create a new team
[15:28] <pitti> good
[15:28] <pitti> [TOPIC] Naming of new packages
[15:28] <MootBot> New Topic:  Naming of new packages
[15:28] <cjwatson> they did say clearly that ~kubuntu-ninjas wasn't appropriate
[15:28] <pitti> mdz?
[15:29] <cjwatson> I think they were just trying to sort out who would run the team, as ~kubuntu-council is not entirely technical
[15:29] <cjwatson> oh, hey, ~kubuntu-dev exists now
[15:29] <Riddell> we have made ~kubuntu-dev
[15:29] <mdz> I was thinking recently, that we've had a couple of situations where a package has entered the archive and then we've needed to change the name
[15:29] <mdz> the most recent example is software-center (nee software-store, nee something else)
[15:29] <cjwatson> Riddell: expect mail about that tomorrow, then
[15:29] <Riddell> and kubuntu council is happy for it  to be self appointing for the moment
[15:29] <pitti> Riddell: thanks; that team looks fine
[15:30] <mdz> and so was wondering if we ought to add a naming check for new packages
[15:30] <mdz> not only to ensure that it's policy compliant (which I assume we already do), but that it can be considered reasonably final
[15:30] <pitti> mdz: archive admins have been known to reject packages with overly general names
[15:30] <pitti> i. e. for policy compliance
[15:30] <mdz> I'm thinking mainly about packages which originate in Ubuntu which are being named "upstream" at the same time
[15:31] <pitti> this obviously doesn't cover the more politically-sensitive bits like store vs. center
[15:31] <cjwatson> software-store is a particularly difficult example there; I understand that the objections did not really arise until users saw it in the archive, and that it was then appealed and sabdfl decided on the name change
[15:31] <Keybuk> doesn't that then become simply a policy for naming of Ubuntu upstream projects?
[15:31] <mdz> I'm not expecting archive admins to judge whether a name is good or correct, only to check that it is "final"
[15:31] <mdz> Keybuk: no, it is a process step to ask the relevant people to confirm the status of the name
[15:31] <cjwatson> I think that would actually have been counterproductive here
[15:32] <mdz> the "image store" (aka appliance store) is potentially in a similar situation
[15:32] <pitti> mdz: in this particular case we should probably have decided the name at UDS already
[15:32] <cjwatson> the DX team were pretty clear that software-store was the final name
[15:32] <Keybuk> indeed, in the software-centre case, the problem was that the developers were not going to change the name
[15:32] <cjwatson> it was only changed after community objections
[15:32] <Keybuk> it was sabdfl who intervened to change it
[15:32] <pitti> s/decided/discussed/, I meant
[15:32] <mdz> I acknowledge that that was a poor choice of example and it has confused my point
[15:32] <sabdfl> based on a request from mdke, representing those who objected
[15:33]  * cjwatson deletes his follow-up comment then :)
[15:33] <mdz> please forget about software-center for the moment
[15:33] <Keybuk> I'm concerned that naming your project is, apparently, the hardest part of developing it
[15:33] <mdz> I just want to set the expectation that a certain amount of due diligence is done with regard to naming before a new package goes into the archive
[15:33] <mdz> because renaming is expensive
[15:33] <Keybuk> and if we block any new package on having its name finalised, we're *never* going to get new packages into the archive
[15:33] <Keybuk> landing changes late because the name wasn't finalised/signed off is worse than having to rename
[15:33] <Keybuk> imo
[15:33] <pitti> TBH I didn't see it happen often enough to consider it a major concern
[15:33] <cjwatson> so I'm pretty sure we don't need to do this for packages that aren't really significantly user-visible
[15:33] <bdale> sounds like a corner case to me
[15:34] <cjwatson> I remember it being an issue for ubiquity (nee espresso, nee ubuntu-express)
[15:34] <sabdfl> it was a bad outcome to have to rename - i left it up to mvo as to whether that should be deferred till lucid, but his pref was just to take the hit now
[15:34] <sabdfl> it's an unusual situation
[15:34] <mdz> ok, I'll withdraw for now, and come back with a list of packages which were renamed and how much developer effort was wasted :-)
[15:34] <Keybuk> computer system cruft remover janitor sprints to mind too ;)
[15:34]  * cjwatson notes that ubiquity's package metadata still has upgrade handling for espresso, because I'm anal that way
[15:35] <mdz> pitti: we can move on
[15:35] <pitti> TOPIC] Naming of software-center
[15:35] <Keybuk> mdz: only if you can prove that the developer effort would not have been wasted if they couldn't have got the package in the archive because the name wasn't finalised
[15:35] <cjwatson> mdz: I think this is an interesting point, don't take my comments as rejection of it
[15:35] <pitti> requested by mdz, not sure whether it's still relevant
[15:35] <cjwatson> I'm not at all sure of the proper handling though
[15:35] <mdz> I put this forward as there was email on the TB list and I didn't see a response
[15:35] <pitti> it's hard to measure how "final" a package name is, indeed
[15:35] <mdz> if it's over, then ignore me
[15:36] <cjwatson> mdz: I think that was overtaken by events
[15:36] <cjwatson> I will respond to the requestor saying so
[15:36] <cjwatson> (just for completeness)
[15:36] <pitti> I didn't see objections against s-center
[15:36] <cjwatson> the mail was an objection against software-store, IIRC
[15:36] <mdz> Keybuk: if you are claiming that progress is severely hindered by not getting software into the archive, you haven't a leg to stand on :-P
[15:36] <pitti> cjwatson: right
[15:37] <Keybuk> mdz: on the contrary, I think legs or no, I have a lot of experience to sit on :-P
[15:37] <pitti> [TOPIC] https://wiki.ubuntu.com/CodySomerville/CoreDeveloperApplication
[15:37] <MootBot> New Topic:  https://wiki.ubuntu.com/CodySomerville/CoreDeveloperApplication
[15:37] <pitti> I'm not sure on protocol here
[15:37] <Keybuk> pitti: that is for the DMB not the T
[15:37] <Keybuk> TB
[15:37] <pitti> should we do this via mail on DMB, or here on IRC?
[15:37] <mdz> I asked pitti to add t his
[15:37] <mdz> because there was an email sent to d-m-b on 10 September and it looks like nobody has responded
[15:37] <Keybuk> the DMB is held up in discussions about policy
[15:38] <mdz> it still needs a response
[15:38] <mdz> we shouldn't leave applications hanging without explanation
[15:38] <mdz> can someone who knows more about what's going on with DMB than I do, respond to the email?
[15:39] <pitti> it requires a majority from dmb@ now?
[15:40] <mdz> pitti: I don't know how to answer that question
[15:40] <cjwatson> was the most recent consensus to use mail for this, or to schedule a meeting with the applicant? honestly, I've lost track
[15:40] <Keybuk> we have achieved no consensus
[15:40] <cjwatson> I think we should schedule an IRC meeting since that will force us to move it forward
[15:40] <cjwatson> in this instance
[15:40] <Keybuk> at least, dholbach has undone the previous consensus :)
[15:41] <cjwatson> how about Thursday 1500 UTC
[15:41] <pitti> WFM
[15:42] <mdz> this week is impossible for me in at any time which would be acceptable in the US
[15:42] <mdz> but don't block on me
[15:42] <Keybuk> cjwatson: if there's going to be an IRC meeting, I would prefer it *not* to be the same week as the TB meeting
[15:42] <Keybuk> why don't we use the TB slot in alternate weeks to the TB?
[15:42] <cjwatson> Keybuk: in this particular case I'm suggesting a one-off rather than recurring, just to move things forward
[15:42] <cjwatson> but I have no problem using the alternate TB slot
[15:43] <pitti> [ACTION] pitti to announce DMB meeting next Tuesday 1400 on the DMB ML
[15:43] <MootBot> ACTION received:  pitti to announce DMB meeting next Tuesday 1400 on the DMB ML
[15:43] <pitti> ok?
[15:43] <cjwatson> doit
[15:43] <mdz> pitti: someone needs an action to reply to the email
[15:43] <Keybuk> though the DMB ML only goes to the DMB :)  UD may be more appropriate
[15:43] <cjwatson> I'll reply to Cody
[15:43] <mdz> cjwatson: thank you
[15:44] <pitti> mdz: that's blocked on us actually establishing what to do about DMB votes, though?
[15:44] <pitti> [TOPIC] Check up on community bugs
[15:44] <MootBot> New Topic:  Check up on community bugs
[15:44] <pitti> none
[15:44] <cjwatson> pitti: I don't know of any remaining blockage there
[15:45] <pitti> cjwatson: isn't that why we just settled for a DMB meeting next week, to figure this out?
[15:46] <pitti> [TOPIC] Select a chair for the next meeting
[15:46] <cjwatson> pitti: we should talk with Cody at that point; he has been kept waiting too long. If we need to figure something else out, we can do that as well.
[15:46] <MootBot> New Topic:  Select a chair for the next meeting
[15:46] <Keybuk> my turn next I think
[15:46] <pitti> [TOPIC] AOB
[15:46] <MootBot> New Topic:  AOB
[15:47] <pitti> 10 sec timeout
[15:47] <pitti> #endmeeting
[15:47] <MootBot> Meeting finished at 09:47.
[15:47] <pitti> thanks everyone!
[15:47] <mdz> thanks, pitti
[15:47] <pitti> I'll summarize the meeting and update the wiki reports
[15:47] <pitti> thanks for bearing with me
[15:48] <cjwatson> this meeting felt ... kind of bureaucratic to me. Let's try to have more interesting substance next time :)
[15:49] <sabdfl> thanks all
[15:52] <zul> helo
[15:56] <kees> argh, off-by-one error with alarm clock.
[16:00] <kirkland> o/
[16:00] <ttx> o/
[16:01] <nijaba> o/
[16:01] <alexm> o/
[16:01] <mdz> \o
[16:01] <mdz> (I'm right handed)
[16:01] <Daviey> \o
[16:01] <soren> o/
[16:01] <mdz> mathiaz: zul: smoser: ping
[16:02] <smoser> o/
[16:02] <zul> here
[16:02] <mathiaz>  /o\
[16:02]  * soren is also right handed, but has no backslash on this keyboard(!)
[16:02] <zul> *hmmph* danish keyboards
[16:02] <zul> ;)
[16:02] <ttx> soren: good thing you are not working on windows, then
[16:03] <soren> American keyboards, actually.
[16:03] <alexm> mdz: it depends if o is looking at you or you're o looking at the screen ;)
[16:03] <mdz> #startmeeting
[16:03] <MootBot> Meeting started at 10:03. The chair is mdz.
[16:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:03] <mdz> [LINK] https://wiki.ubuntu.com/ServerTeam/Meeting
[16:03] <MootBot> LINK received:  https://wiki.ubuntu.com/ServerTeam/Meeting
[16:03] <mdz> [TOPIC] Review ACTION points from previous meeting
[16:03] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:03] <mdz> [LINK] https://wiki.ubuntu.com/MeetingLogs/Server/20090929
[16:03] <MootBot> LINK received:  https://wiki.ubuntu.com/MeetingLogs/Server/20090929
[16:04] <mdz> ACTION: niemeyer to send mathiaz and nurmi a mail with details on how to test the image-store-proxy integration with fakestoreapi.py.
[16:04] <mathiaz> mdz: done
[16:04] <mdz> ACTION: ttx and smoser to review the automation of the image publication process.
[16:04] <mathiaz> mdz: haven't had time to conduct testing though
[16:04] <mdz> mathiaz: understood
[16:05] <mdz> ttx, smoser, status of the image publishing automation?
[16:05] <ttx> mdz: that was done prior to beta, and it showed quite a few things that still need manual interaction
[16:05] <ttx> especially ec2 publication
[16:05] <smoser> regarding review of automation, i'm working on that now.  the NamingConvention (https://wiki.ubuntu.com/UEC/Images/NamingConvention) was part of that.
[16:05] <mdz> smoser: is it on track to be sufficiently tested to be able to be used for RC?
[16:05] <smoser> i think it can be.
[16:06] <mdz> ok
[16:06] <mdz> ACTION: smoser to open bugs to cover kernel/ramdisk GPL reqs and renaming
[16:06] <smoser> i hope that by end of week we can have nightly builds being published.
[16:06] <smoser>  - bug 444598 : renaming
[16:06] <smoser>  - bug 444605 : gpl source
[16:06] <mdz> smoser: great news, thanks
[16:06] <mdz> (done then)
[16:06] <mdz> ACTION: ttx to test UEC images + UEC kernel/ramdisk on karmic UEC
[16:06] <ttx> mdz: done for beta release
[16:06] <mdz> ACTION: ttx to see if some bugs assigned to soren need urgent reassignment
[16:07] <ttx> mdz: most of those were eucalyptus-related. The others are vmbuidler ones that are not critical
[16:07] <mdz> ttx: now that soren is back, it might be useful to review his bug list with him to make sure it's aligned with current tasking and release status
[16:07] <mdz> ACTION: Daviey to setup a doodle poll and send the url to the ubuntu-server@ mailing list.
[16:08] <Daviey> Ok, this was done - but the dates were suboptimal
[16:08] <ttx> mdz: sure, we'll review it when we arrive at the "assigned bug list review" item of the meeting
[16:08] <Daviey> soren mentioned that for many it wasn't a consistent week.
[16:08] <ttx> or off-meeting.
[16:08] <mdz> ttx: agreed
[16:08] <soren> Daviey: That's not the problem.
[16:08] <soren> Daviey: The problem is that the data we collect will only be good for three weeks.
[16:09] <mdz> the action from last week is completed; if there is further discussion needed, please take it off-meeting or add to the end of the agenda
[16:09] <smoser> that really stinks. doodle really needs time zone info.
[16:09] <soren> ...because that's when some of us switch from DST to "regular time".
[16:09] <mdz> [topic] Beta release postmortem
[16:09] <MootBot> New Topic:  Beta release postmortem
[16:09] <soren> One week later, other people switch.
[16:09] <Daviey> oh sure i see that, but it's a good "idea", and we can take daylight savings adjustments into account.
[16:09] <soren> Other people again don't switch at all.
[16:09] <soren> Some may swithc in the opposite direction at other times.
[16:09] <mdz> ttx: there was no name next to this, but I think you added it. how do you want to structure this discussion?
[16:10] <ttx> just a few comments on how beta release went, plus opportunity for anyone to chime in
[16:10] <ttx> Beta release went relatively ok, the main issue was lack of UEC testing capability
[16:10] <soren> Daviey: We can discuss it under the "# Agree on next meeting date and time " item.
[16:10]  * soren shuts up now
[16:11] <ttx> which made it difficult to confirm the bugs that were found
[16:11] <mdz> we also had a bit of a blind spot with regard to the UEC kernel and initramfs
[16:11] <ttx> mdz: that's linked to it. With more testers, we would have uncovered it before
[16:11] <ttx> I was busy validating UEC, so UEC image testing was delayed
[16:11] <mdz> ttx: I think it's a separate issue. our test plan simply didn't cover this: it instructed the user to copy the host kernel instead
[16:12] <ttx> another thing we need to adjust is the test plan, yes
[16:12] <mdz> I'm not sure why that happened, or if it's been corrected
[16:13] <ttx> we probably shouldn't validate UEC with a moving target UEC image
[16:13] <ttx> there are tests for the UEC images and tests for the UEC install, those need to be separated
[16:13] <mdz> we can do testing with the beta image now, and post-9.10 we can use the 9.10 image for smoke testing UEC
[16:13] <kirkland> mdz: it hasn't been corrected; it looks to me like the instructions are still geared toward using the host kernel/initrd
[16:13] <mdz> ttx: I believe they already are
[16:13] <mdz> http://testcases.qa.ubuntu.com/System/CloudImages is for testing the images
[16:13] <MootBot> LINK received:  http://testcases.qa.ubuntu.com/System/CloudImages is for testing the images
[16:14] <mdz> http://testcases.qa.ubuntu.com/System/Eucalyptus is for testing UEC
[16:14] <mdz> [action] smoser to update CloudImages test case to use the UEC and EC2 kernel+initramfs rather than the host's
[16:15] <kirkland> specifically: http://testcases.qa.ubuntu.com/Install/ServerEConfig
[16:15] <mdz> ttx: what do we need to do to solve the UEC testing bottleneck?
[16:15] <mdz> is anyone still waiting on hardware?
[16:15] <ttx> mdz: please action me on reviewing tests and making sure they are aligned
[16:15] <kirkland> ....  euca-bundle-image -i /boot/vmlinuz-$(uname -r) --kernel true ...
[16:15] <mdz> [action] ttx to review test plans and ensure they are aligned with 9.10
[16:15] <ttx> mdz: we need at least two test setups in different timezones
[16:15] <Moot2> LINK received:  http://testcases.qa.ubuntu.com/System/Eucalyptus is for testing UEC
[16:15] <mdz> hmm, I think mootbot is lagging
[16:15] <ttx> (that can reliably run UEC instances)
[16:15] <kirkland> ttx: that's you and me, right?
[16:16] <ttx> kirkland: now, yes.
[16:16] <kirkland> ttx: oh "reliably"
[16:16] <mdz> kirkland has also ordered some additional hardware
[16:16]  * kirkland puts his hand down
[16:16] <kirkland> mdz: this hardware arrives tomorrow
[16:16] <mdz> kirkland: what do we need to do to fix the "reliably"?
[16:16] <kirkland> mdz: :-)  that was just a smartarse comment
[16:16] <ttx> kirkland: you cna run UEC instances alright, now ?
[16:16] <mdz> is this problem solved now that kirkland and ttx have spare hardware?
[16:17] <kirkland> ttx: i'm reinstalling with today's iso's now
[16:17] <Moot2> ACTION received:  smoser to update CloudImages test case to use the UEC and EC2 kernel+initramfs rather than the host's
[16:17] <kirkland> mdz: we have cloud testing setups now in the middle of France, and the middle of Tejas
[16:17] <Moot2> ACTION received:  ttx to review test plans and ensure they are aligned with 9.10
[16:17] <ttx> mdz: when kirkland says that he can run UEC images alright, I think we are covered
[16:17] <ttx> the more testers the better, obviously
[16:17] <mdz> [action] kirkland to confirm that his test rig is fully operational
[16:18] <smoser> verify, the url for above action is http://testcases.qa.ubuntu.com/Install/ServerEConfig
[16:18] <smoser> right ?
[16:18] <kirkland> mdz: sure, will do that today
[16:18] <Moot2> ACTION received:  kirkland to confirm that his test rig is fully operational
[16:18] <mdz> I believe it was also suggested that mathiaz could gain access to some cert hardware for this purpose
[16:18] <mathiaz> mdz: there isn't so much spare hardware in the cert lab
[16:19] <mdz> I've also thought about setting up an NC on my host while running the CLC/SC/CC/Walrus inside of KVM
[16:19] <kirkland> mdz: when can we expect Canonical IS to have an Ubuntu 9.10-based cloud?
[16:19] <mathiaz> mdz: and with release around the corner, most of the hardware is used on a daily basis
[16:19] <mdz> kirkland: that's RT #35519
[16:19] <mdz> I haven't checked it recently
[16:20] <mdz> mathiaz: ok
[16:20] <kirkland> mdz: okay, but sometime shortly after GA, roughly?
[16:20] <mdz> I should be able to arrange a bit of extra hardware for the release sprint but that will only help for the very final validation step
[16:20] <mdz> kirkland: they started on it as soon as 1.6 landed, so yes, they're tracking toward having something in place soonish
[16:20] <kirkland> mdz: once we have that, i would think *that* would be the proper place for *image* verification
[16:21] <kirkland> mdz: with our local, distributed setups being the right place for actual cloud development and testing
[16:21] <mdz> ok, any other comments on beta, things we should fix before the next milestone?
[16:21] <mdz> kirkland: agreed
[16:21] <mdz> [topic] RC preparation
[16:21] <MootBot> New Topic:  RC preparation
[16:21] <mdz> # Further improvements to release process
[16:21] <mdz> # Sweeping server bugs for release-critical and regression bugs
[16:21] <mdz> # Staying on top of beta bugs: Triage days
[16:22] <mdz> re: release process, there were a few of these outstanding from alpha 6 which I haven't checked into since beta, if we could quickly review them
[16:22] <mdz>  * Automate publishing of AMIs to EC2 [smoser]: DEFERRED
[16:22] <mdz>  * Automate updating ec2-version-query [soren]: PENDING on previous item
[16:22] <mdz>  * Publish ec2-version-query in a more appropriate place [soren]:
[16:22] <mdz>    Thought to be in slangasek hands now, needs to be confirmed
[16:22] <mdz> the first item I think we covered, it's still WIP
[16:23] <mdz> soren, smoser, who is looking after ec2-version-query?
[16:23] <soren> I haven't looked at it since I got back.
[16:23] <smoser> i had kind of just left that off to soren, but when thinking of the naming convention stuff last night, i realized that s3 might be a good place to store this
[16:23] <soren> Should I?
[16:23] <mdz> smoser: do you have the necessary access to finish that off, or do you need soren?
[16:24] <smoser> i can probably find my way through it, but will likely need some help from soren along the way
[16:24]  * soren doesn't think he has special access for any of this
[16:24] <smoser> mostly, at the moment ican't write to ~soren on people.canonical.com so i'm sol
[16:24] <soren> smoser: I'm happy to provide any information you may need.
[16:24] <mdz> smoser: ok, let's consider it your task then, and you can ask for help as you need it
[16:25] <mdz>  * mathiaz to set up OpenLDAP/sssd test infra on EC2 - INPROGRESS
[16:25] <soren> Well, the first step of this is to move it /away/ from there anyway.
[16:25] <smoser> fair enough
[16:25] <mathiaz> mdz: in progress.
[16:25] <mdz> [action] mathiaz to set up OpenLDAP/sssd test infra on EC2
[16:25] <MootBot> ACTION received:  mathiaz to set up OpenLDAP/sssd test infra on EC2
[16:25] <mdz> mathiaz to get help from Michael Vogt on bug 194140 - PENDING
[16:26] <mdz> mvo: ^^
[16:26] <mdz> kirkland to adapt help.ubuntu.com VM recipe(s?) to use libvirt - TODO
[16:26] <kirkland> mdz: haven't started that one
[16:26] <kirkland> mdz: though I'm signed up for an OpenWeek session on the topic
[16:26] <mdz> [action] kirkland to adapt help.ubuntu.com VM recipe(s?) to use libvirt
[16:26] <MootBot> ACTION received:  kirkland to adapt help.ubuntu.com VM recipe(s?) to use libvirt
[16:26] <kirkland> mdz: i'll update that documentation in prep for the OpenWeek session
[16:27] <mdz> I think the others are completed
[16:27] <mdz> ttx: Sweeping server bugs for release-critical and regression bugs?
[16:27] <ttx> mdz: so we need to get a more accurate picture of release-relevant bugs in packages others than eucalyptus
[16:28] <ttx> like you mentioned, it's strange that we don't have any regression bug so far
[16:28] <mdz> as I mentioned in email to some of you, it's important to tag regression bugs as such when you find them
[16:28] <kirkland> ttx: some qemu-kvm bugs have started trickling in
[16:28] <mdz> use the tag regression-potential
[16:28] <kirkland> ttx: i haven't had much time to look at them
[16:28] <mvo> mdz: uh, I'm very sorry, I will look at it tomorrow :/
[16:29] <mdz> further documentation on regressions at https://wiki.ubuntu.com/QATeam/RegressionTracking
[16:29] <ttx> everyone should help, obviously, but we need people to cover the packages that will slip in the holes
[16:29] <kirkland> ttx: libvirt needs a big hug; there are a ton of untriaged bugs against that very important package
[16:29] <mdz> mvo: no worries, thank you
[16:29] <ttx> zul and mathiaz should coordinate the effort
[16:29] <mdz> kirkland: bug day?
[16:29] <zul> ack
[16:29] <kirkland> mdz: not yet scheduled; but would be a good thing
[16:29] <mdz> ttx: is there an established plan for this that we can put into motion, or do we need to decide how it will work?
[16:29] <mathiaz> ttx: right - zul could you focus on the bugs that are in New,Undecided?
[16:30] <ttx> mdz: we need to decide
[16:30] <mathiaz> zul: I'll look at the Confirmed, Triagged
[16:30] <zul> mathiaz: okies
[16:30] <mdz> looks like mathiaz and zul have decided on a basic plan of action
[16:30] <mdz> zul,mathiaz: this is across all server team packages, right?
[16:30] <zul> mdz: correct
[16:31] <mathiaz> My proposal is that zul focuses on triagging/confirming bugs, while I'll have look at the triagged/confirmed for release critical things
[16:31] <ttx> mdz: we should still ahve a way for others to participate, like "hey, I'll look at tomcat6 and dnsmasq"
[16:31] <mathiaz> mdz: yes
[16:31] <mdz> zul,mathiaz: do you think it would be helpful to organize a server bug day on this?
[16:31] <ttx> since I usually triage this package anyway
[16:31] <mdz> ttx: a bug day would provide a framework for participation
[16:31] <zul> mdz: its based on this list https://bugs..launchpad.net/~ubuntu-server/+packagebugs
[16:31] <kirkland> mdz: what's the timeframe for such a bug day?
[16:31] <kirkland> mdz: we'd need to do it before RC, right?
[16:31] <mdz> kirkland: they happen all the time, someone just needs to get in touch with the QA team
[16:32] <kirkland> mdz: right, i'm just curious... before or after RC?
[16:32] <mdz> kirkland: ASAP, definitely before
[16:32] <mathiaz> zul: http://qa.ubuntu.com/reports/ubuntu-server-team/dailynewbugs.ubuntu-server.mon.html
[16:32] <kirkland> mdz: okay, right
[16:32] <mathiaz> zul: ^^ could you focus on the list of bugs above?
[16:32] <mdz> kirkland: RC is meant to be a dry run of the final bits; we should be ready to release at that point
[16:32] <zul> mathiaz: i have as well
[16:32] <mdz> mathiaz: could you take the action to ask about a bug day?
[16:33] <mathiaz> mdz: sure
[16:33] <mdz> [action] mathiaz to work with the QA team on a server bug day for Karmic
[16:33] <MootBot> ACTION received:  mathiaz to work with the QA team on a server bug day for Karmic
[16:33] <mdz> ttx: Staying on top of beta bugs: Triage days
[16:33] <mdz> is this something to do in addition to the bug day?
[16:33] <ttx> yes.
[16:33] <ttx> The idea is that server is only tested very late in the release process
[16:34] <ttx> so we need to stay on top of new bugs filed against server apckages
[16:34] <mdz> what action is needed to get started on this?
[16:34] <kirkland> mdz: mathiaz: would have to be Monday or Tuesday of next week
[16:34] <ttx> to quickly identify regressions/ critical bugs
[16:34] <mdz> [action] mdz to follow up with marjo regarding general QA support in Karmic
[16:34] <MootBot> ACTION received:  mdz to follow up with marjo regarding general QA support in Karmic
[16:34] <ttx> https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#Bug%20Triager%20resources
[16:35] <mdz> (note to myself)
[16:35] <ttx> describes bug lists that can be used
[16:35] <ttx> to make sure New,Undecided bugs are at least prioritized
[16:35] <ttx> ten we can assign a team member to each day
[16:35] <ttx> then...
[16:36] <ttx> mathiaz: you have been setting up the bug lists, any comment ?
[16:36] <mdz> mathiaz: how can I help?
[16:36] <mathiaz> ttx: not really - they're just ready for general usage
[16:37] <mathiaz> now it's a matter of getting people to use them
[16:37] <mathiaz> the goal is to have the list emptied every day
[16:38] <mathiaz> there is a backlog though
[16:38] <mdz> mathiaz: I'll mention this to marjo as well and see if he can provide any help
[16:38] <mathiaz> once the backlog is dealt with, it should be around 10/12 days a bug
[16:38] <mathiaz> hm bug <-> day
[16:38] <mdz> we need to move on to status
[16:38] <mdz> [topic] #
[16:38] <mdz> Eucalyptus status, including review of open issues (kirkland, ttx)
[16:38] <MootBot> New Topic:  #
[16:38] <kirkland> there is an external job posting for an Ubuntu Server QA Engineer
[16:38] <mdz> [topic]  Eucalyptus status, including review of open issues (kirkland, ttx)
[16:38] <MootBot> New Topic:   Eucalyptus status, including review of open issues (kirkland, ttx)
[16:39] <kirkland> mdz: uploaded a new eucalyptus yesterday
[16:39] <mdz> kirkland: yes, but we can't rely on much help there for 9.10 due to the timeframe involved
[16:39] <kirkland> mdz: merge of upstream code, closes ~12 bugs
[16:39] <ttx> I tested it, it's working correctly
[16:39] <ttx> I filed a series of bugs though
[16:39] <mdz> how about the installation+autoregistration?
[16:39] <kirkland> mdz: ah, okay; i thought we were disucssing bug triage in the long term, rather than the 9.10 timeframe
[16:39] <ttx> autoregistration works, but by accident
[16:39] <mdz> kirkland: both, but more urgently 9.10
[16:40] <ttx> we need to fix a few bugs to make it work by design
[16:40] <kirkland> i had just started the new ISO install when this meeting started
[16:40] <mdz> ttx: are those bugs assigned and targeted for Karmic?
[16:40] <kirkland> mdz: my upgrade testing from the previous package went very well
[16:40] <ttx> assigned - yes, targeted to karmic, i'll check and fix if needed
[16:40] <kirkland> mdz: ttx: nurmi arrives in Austin at 11pm tonight; we're spending the following two days hardening UEC
[16:41] <mdz> ttx: please mention the bug numbers here for tracking purposes
[16:41] <kirkland> ttx: if you can verify our work in your locale, that would be great
[16:41] <mdz> kirkland: excellent
[16:41] <kirkland> ttx: s/verify/test/
[16:41] <ttx> bug 444352 could use someone to reproduce it
[16:41] <kirkland> i propose at this point that we cherry pick individual commits from upstream eucalyptus to solve bugs
[16:42] <kirkland> ie, i propose that we do no more wholesale merges
[16:42] <ttx> bug 443325 and bug 444504 are the ones that make autoregistration work, once combined
[16:42] <kirkland> for karmic
[16:42] <kirkland> ttx: when you say "once combined", you mean once both fixes are applied?
[16:42] <mdz> ttx: ok, thanks
[16:42] <mdz> anything else on eucalyptus?
[16:42] <mdz> https://bugs.launchpad.net/ubuntu/+source/eucalyptus
[16:43] <ttx> nothing from me
[16:43] <kirkland> mdz: not really from me
[16:43] <mdz> kirkland: are we nearer to a resolution for bug 432154?
[16:43] <ttx> I'm writing some blogposts about running UEC, they are getting good press coverage
[16:43] <kirkland> mdz: delayed that one until nurmi arrives
[16:43] <mdz> kees: any news on  bug 436407?
[16:43] <kirkland> mdz: that will be one of our top priorities
[16:44] <mdz> kees: er, 436977
[16:44] <mdz> bug 436977
[16:44] <mdz> kirkland: ok, is that on the agenda that you sent me?
[16:44] <kirkland> mdz: absolutely
[16:44] <kirkland> mdz: i'll like to review that agenda with you briefly today
[16:44] <mdz> kirkland: ok, I'll hopefully be able to review that today
[16:44] <mdz> [topic] UEC images, including review of active bugs (smoser)
[16:44] <MootBot> New Topic:  UEC images, including review of active bugs (smoser)
[16:45] <mdz> [link] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=uec-images
[16:45] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/+bugs?field.tag=uec-images
[16:45] <mdz> smoser: are you able to test these yourself in UEC?
[16:45] <mdz> there seems to still be an MIR pending
[16:45] <smoser> no. not at the moment.
[16:46] <smoser> yeah, the MIR is assigned to zul. not pointing fingers, just saying. i think he may know more.
[16:46] <smoser> i do have hardware for uec that i'd like to get up and running to help test with
[16:46] <smoser> its just time.
[16:46] <mdz> smoser: bug 444605 looks like it needs to be fixed for 9.10
[16:47] <smoser> yes.
[16:47] <smoser> of the bugs listed there, those that will surely be fixed are:
[16:47] <smoser> bug 444605
[16:47] <smoser> bug 444598
[16:48] <mdz> smoser: I expect cjwatson would have good input on 444605, I suggest asking him about it
[16:48] <smoser> at this point i expect to fix bug 440757 also.
[16:48] <smoser> i will copy cjwatson and pester him for input
[16:48] <mdz> smoser: anything on the "surely be fixed" list should be targeted for karmic + milestoned to ubuntu-9.10; please update LP accordingly
[16:48] <smoser> will do that now.
[16:49] <mdz> [action] smoser to follow up with mdz regarding UEC image testing capability
[16:49] <MootBot> ACTION received:  smoser to follow up with mdz regarding UEC image testing capability
[16:49] <mdz> [topic] EC2 AMIs, including review of active bugs (smoser)
[16:49] <MootBot> New Topic:  EC2 AMIs, including review of active bugs (smoser)
[16:49] <mdz> [link] https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=ec2-images
[16:49] <MootBot> LINK received:  https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=ec2-images
[16:49] <mdz> only one High there, and it's the (same) MIR
[16:49] <smoser> the plan-to-fix list is the same for ec2 as it is for uec.
[16:49] <smoser> right.
[16:49] <mdz> zul: is there anything blocking getting that MIR completed this week?
[16:50] <zul> mdz: just fixing the testusite
[16:50] <mdz> smoser: are you feeling confident about the UEC and EC2 kernels at this stage?
[16:51] <mdz> [action] zul to fix m2crypto test suite and ensure that MIR is processed
[16:51] <MootBot> ACTION received:  zul to fix m2crypto test suite and ensure that MIR is processed
[16:51] <smoser> well, the ones we have and have been using surely seem solid (no issues have been raised)
[16:51] <smoser> jjohansen has put up some others with tweaked configs (bug 428692)
[16:52] <mdz> smoser: until recently, as noted earlier, we weren't testing the exact bits in the UEC kernel+initramfs, so we might want to test more thoroughly there
[16:52] <mdz> am I remembering correctly that the UEC image won't boot in plain KVM because it tries to contact the metadata service?
[16:52] <smoser> that is correct, however, now there is a workaround
[16:52] <smoser> you can pass kernel param ec2init=0
[16:53] <mdz> kirkland: ttx: meanwhile, could you spare some UEC cycles to help test the images this week?
[16:53] <smoser> or mount image and modify /etc/ec2-init/.... have to look it up
[16:53] <mdz> smoser: oh, good to know
[16:53] <ttx> mdz: sure.
[16:53] <mdz> [topic] Virtual appliance - reference appliance (soren)
[16:53] <MootBot> New Topic:  Virtual appliance - reference appliance (soren)
[16:53] <kirkland> mdz: yes, i can do that
[16:53] <kirkland> smoser: please PM me the url to the images you want tested
[16:53] <mdz> ttx, kirkland, thank you
[16:53] <ttx> smoser: same, ping me when you need one tested
[16:54] <mdz> soren: we seem to be in a tight spot with regard to the reference appliance; there is some disagreement on the exact requirements
[16:54] <soren> Oh, I didn't prepare for this.
[16:54] <smoser> i will verify, but i think that output of nightly build should have valid kernel/ramdisk now
[16:54] <soren> mdz: Yes, very much so.
[16:54] <mdz> it is critical that we get this resolved ASAP
[16:55] <soren> mdz: Yes. Who actually defines these requirements? Who is the authoritive person to ask?
[16:55] <mdz> niemeyer: soren: what do we need to do in order to resolve this? we don't have time to discuss here but I think you need to hold a separate meeting about this
[16:55] <mdz> soren: I'll do for the moment
[16:55] <soren> mdz: I'm feeling slightly wiser than yesterday on the subject, but there's still a lot of open questions.
[16:55] <soren> mdz: Ok.
[16:56] <soren> We can do a meeting tomorrow, perhaps?
[16:56] <mdz> [action] soren/niemeyer to arrange a meeting to discuss reference appliance plan of action
[16:56] <MootBot> ACTION received:  soren/niemeyer to arrange a meeting to discuss reference appliance plan of action
[16:56] <mdz> [topic] Image store status (niemeyer)
[16:56] <MootBot> New Topic:  Image store status (niemeyer)
[16:56] <soren> I believe I'm free all day (until 16:00 UTC)
[16:56] <mdz> niemeyer: how are we doing on this front?
[16:57] <niemeyer> mdz: I will provide mathiaz with an updated version with a couple of very minor changes today
[16:57] <niemeyer> mdz: I don't envision further changes at this point, except for any bug fixes we find necessary
[16:57] <mathiaz> niemeyer: did you rework the gpg integration?
[16:57] <mdz> niemeyer: is the version in karmic functional, to the point where it can be tested with the fake server?
[16:57] <niemeyer> mathiaz: "rework" as in "add the --homedir" option?
[16:58] <mathiaz> niemeyer: yeah :D
[16:58] <niemeyer> mdz: Yes, absolutely.. I've been testing it here
[16:58] <mathiaz> mdz: the next issue is - what should be put in the fakestore?
[16:58] <niemeyer> mdz: Mathiaz and Daniel have instructions to run it
[16:58] <mathiaz> niemeyer: do you have an appliance to put in the store?
[16:58] <niemeyer> mathiaz: Ok, "rework" is a little strong then.. :)
[16:58] <niemeyer> mathiaz: Yes, I've added the option with tests and all
[16:58] <mathiaz> niemeyer: great to hear that
[16:58] <mdz> mathiaz: are niemeyer's testing instructions in the testcases wiki yet?
[16:59] <mathiaz> mdz: not that I know of
[16:59] <mathiaz> mdz: I've got them in an email
[16:59] <mdz> [action] mathiaz to document test plan for image store
[16:59] <MootBot> ACTION received:  mathiaz to document test plan for image store
[16:59] <niemeyer> mathiaz: Yes, I haven an "appliance"
[16:59] <niemeyer> mathiaz: I have an image I downloaded from the Eucalyptus web site
[16:59] <mathiaz> mdz: and all this image-store testing depends on having a working UEC cloud
[16:59] <niemeyer> mathiaz: Any image which works with Eucalyptus should be good for testing the image store proxy
[16:59] <mathiaz> niemeyer: ok.
[17:00] <mdz> mathiaz: maybe you could ask kirkland or ttx to run the test plan and correct as necessary
[17:00] <kirkland> mdz: sure, i've edited it slightly almost every time I've run it
[17:00] <mathiaz> mdz: sure. I'll keep in touch with dustin here.
[17:00] <mdz> kirkland: after your sprint, will the new test rig be available? perhaps it could go back with mathiaz so we add an additional tester for karmic
[17:01] <mdz> kirkland: I mean the image store test plan, which isn't in the wiki yet
[17:01] <niemeyer> kirkland, mathiaz: Please ping me if you need any help with whatever
[17:01] <kirkland> mdz: Estimated Delivery Date:	10/19/2009  :-(
[17:01] <mdz> niemeyer: any other actions needed in the coming week?
[17:01] <mdz> kirkland: oh, never mind
[17:01] <kirkland> mdz: but i do have a 2-machine cluster already
[17:01] <mdz> we're over time and need to wrap up
[17:01] <niemeyer> mdz: As far as the image store proxy goes, I don't think so
[17:01] <kirkland> mdz: we'll run with the 2 systems we have here now
[17:01] <niemeyer> mdz: There's that other topic about the "Services" tab.. I don't know where to fit this
[17:02] <mdz> niemeyer: let's take that off-meeting
[17:02] <mdz> [topic] assigned bugs
[17:02] <MootBot> New Topic:  assigned bugs
[17:02] <niemeyer> mdz: Ok
[17:02] <mdz> there are a bunch of importance-Undecided bugs on this list
[17:02] <mdz> [topic] http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html
[17:02] <MootBot> New Topic:  http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html
[17:02] <mdz> mostly assigned to zul, and one to soren
[17:03] <mdz> [action] zul to triage his assigned bugs
[17:03] <MootBot> ACTION received:  zul to triage his assigned bugs
[17:03] <zul> mdz: ill go through that list today
[17:03] <mdz> the highest importance triaged bugs on that list are the vmbuilder ones, assigned to soren
[17:03] <mdz> both targeted to karmic
[17:03] <soren> I've got some VMBuilder time scheduled for tomorrow.
[17:03] <soren> I expet to be able to cover it there.
[17:03] <soren> expect, even.
[17:03] <mdz> soren: glad to hear it, thanks
[17:03] <mdz> [topic] AOB
[17:03] <MootBot> New Topic:  AOB
[17:04] <mdz> I'm going to be out of the office next week, please contact ttx in my absence
[17:04] <soren> Well, there's the meeting time thing, but that's an item of its own.
[17:04] <soren> Right?
[17:04] <mdz> soren: take it to email?
[17:05] <soren> I tried. Noone answered.
[17:05] <ttx> soren: I did ;)
[17:05] <soren> ttx: orly?
[17:05] <mdz> I don't see it in my inbox, but I'll follow up separately
[17:05] <soren> Oh, to the original one?
[17:05] <mdz> thanks, all
[17:05] <soren> right, right.
[17:05] <mdz> #endmeeting
[17:05] <MootBot> Meeting finished at 11:05.
[17:07] <Daviey> woot.
[18:00] <bjf> Roll Call
[18:00]  * ogasawara waves
[18:00]  * pgraner waves o/
[18:00] <smb> \o
[18:00]  * apw drops in ... hot
[18:00]  * cking \o/
[18:00] <rafael_carreras> o/
[18:00]  * rtg waves
[18:00] <bjf> #startmeeting
[18:00] <MootBot> Meeting started at 12:00. The chair is bjf.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00]  * lieb_ waves
[18:01] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:01] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:01] <bjf> [TOPIC] Open Action Items: (apw) Check up on drdb status in dkms package and kernel
[18:01] <MootBot> New Topic:  Open Action Items: (apw) Check up on drdb status in dkms package and kernel
[18:01] <bjf> apw, ??
[18:01] <apw> ok seems that server is using a newer version in dkms
[18:01] <apw> they recon we can drop it from the kernel, just need to formally ask them
[18:02] <apw> on their email list ...
[18:02] <apw> will get it sorted out
[18:02] <apw> as of .33 it will be upstream anyhow
[18:02] <bjf> [ACTION] apw to get it sorted out
[18:02] <MootBot> ACTION received:  apw to get it sorted out
[18:02] <apw> :)
[18:02] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:02] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:02] <bjf> [TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs
[18:02] <MootBot> New Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs
[18:02] <ogasawara>  * Release Meeting Bugs (9 bugs) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:02] <ogasawara>  * RC Milestoned Bugs Beta (4 kernel bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+bugs?field.milestone%3Alist=12698
[18:02] <ogasawara>  * Release Targeted Bugs (17 bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux
[18:03] <bjf> [TOPIC] Karmic Release Status: Milestoned Features
[18:03] <MootBot> New Topic:  Karmic Release Status: Milestoned Features
[18:03] <ogasawara> see https://edge.launchpad.net/ubuntu/+milestone/ubuntu-9.10
[18:04] <pgraner> ogasawara: your RC script above ignores imx51 and dove bugs
[18:04] <pgraner> ogasawara: RC Milestoned that is
[18:04] <ogasawara> pgraner: yah, there's no way in launchpad to combine multiple packages into one link
[18:04] <pgraner> ogasawara: thwarted by LP once again
[18:05] <ogasawara> pgraner: I'll pull the links for the other packages for future meetings
[18:05] <bjf> [TOPIC] Blueprints: kernel-karmic-hwdb-workshop (ogasawara)
[18:05] <pgraner> ogasawara: thanks
[18:05] <MootBot> New Topic:  Blueprints: kernel-karmic-hwdb-workshop (ogasawara)
[18:05] <ogasawara> Nothing new to report, we can probably drop this from the agenda
[18:05] <pgraner> bjf: ack that
[18:05] <pgraner> bjf back up a sec
[18:05] <bjf> [ACTION] bjf to drop this from agenda
[18:05] <MootBot> ACTION received:  bjf to drop this from agenda
[18:05] <bjf> pgraner, go!
[18:06] <pgraner> bjf: What is happening with the  Release Targeted Bugs (17 bugs)
[18:06] <pgraner> bjf: I'm not seeing much movement
[18:06] <pgraner> bjf: specifically the HIGH and above
[18:06] <pgraner> bjf: they are on the list week over week
[18:06] <pgraner> Anyone?^^^^
[18:07] <bjf> if you have one of the bugs assigned to you, speak up
[18:07] <apw> a lot of the bugs are being looked at one way or another
[18:07] <apw> we were waiting on the kernel that rtg jut got in with 2.6.31.2 to do a retest
[18:07] <apw> before heavy lifting them
[18:07] <pgraner> apw: the expectation that is if they are targeted for release they will be fixed or some other action needs to be taken
[18:07] <pgraner> apw: Kernel freeze is the 15th
[18:07] <pgraner> apw: running out of time
[18:08] <pgraner> apw: ok, so by next weeks meeting we should see many of them go bye bye?
[18:08] <apw> pgraner, yes understood, smb perhaps we could do a list review first thing tomorrow
[18:08] <ogasawara> pgraner: looks like 4/5 high ones are assigned, the 5th will be getting a fix via the next stable kernel
[18:08] <smb> apw, ack
[18:08] <pgraner> apw: sure lets plan on doing it in #ubuntu-kernel
[18:08] <apw> and at least make sure they are being retested, and make sure they are assigned to the right place
[18:08] <apw> pgraner, ok
[18:08] <pgraner> bjf: Ok I'm done
[18:09] <bjf> [TOPIC] Blueprints: kernel-karmic-kms (apw)
[18:09] <MootBot> New Topic:  Blueprints: kernel-karmic-kms (apw)
[18:09] <apw> that one we can close, support for KMS is now in
[18:09] <bjf> [ACTION] bjf to remove from agenda
[18:09] <MootBot> ACTION received:  bjf to remove from agenda
[18:09] <apw> and on as we expect it to be in final.  bug fixing as normal
[18:09] <bjf> [TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:09] <MootBot> New Topic:  Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:10] <rtg> bjf, deferred for now.
[18:10] <bjf> [TOPIC] Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)
[18:10] <MootBot> New Topic:  Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)
[18:10] <smb> Is done. Should be marked as such if I did the right things.
[18:10] <pgraner> bjf: drop from this meeting agenda
[18:11] <bjf> [ACTION] bjf to drop from agenda
[18:11] <MootBot> ACTION received:  bjf to drop from agenda
[18:11] <bjf> [TOPIC] Blueprints: kernel-karmic-suspend-resume (manjo)
[18:11] <MootBot> New Topic:  Blueprints: kernel-karmic-suspend-resume (manjo)
[18:11] <manjo> working on samsung nc10 resume issue workaround
[18:11] <manjo> foundation team will need to put in a quirk
[18:11] <pgraner> manjo: make sure that gets followed up and the bug closed pls
[18:12] <manjo> pgraner, ack
[18:12] <pgraner> manjo: thans
[18:12] <pgraner> thanks even
[18:12] <bjf> [TOPIC] Other Release Tasks: ARM-Freescale/Marvell (amitk, bjf)
[18:12] <MootBot> New Topic:  Other Release Tasks: ARM-Freescale/Marvell (amitk, bjf)
[18:12] <bjf> [LINK]  https://bugs.edge.launchpad.net/ubuntu/karmic/+bugs?field.searchtext=linux-fsl-imx51&milestone=12698
[18:12] <MootBot> LINK received:   https://bugs.edge.launchpad.net/ubuntu/karmic/+bugs?field.searchtext=linux-fsl-imx51&milestone=12698
[18:12] <bjf> Marvell-dove seems to be in good shape, I'm working on the imx51 bugs.  I've looked at the RTC bug a bit,
[18:12] <bjf> trying Amit's suggestion and not had any success. Am going to look into the FIC driver next.
[18:13] <pgraner> rtg: hardware should be to you
[18:13] <manjo> pgraner, quick update on that ... slangasek has put in the quirk
[18:13] <rtg> bjf, I should be getting an imx51 today
[18:13] <apw> how many bugs do we have outstanding for release? ofr arm ?
[18:13] <bjf> rtg, lucky you
[18:13] <pgraner> rtg: we need to jump on these bugs and try and squash so mobile can keep working
[18:13] <rtg> pgraner, jump and squash :)
[18:14] <apw> sounds like a cheesy song title
[18:14] <bjf> [TOPIC] Other Release Tasks: EC2 Karmic Kernel Status
[18:14] <MootBot> New Topic:  Other Release Tasks: EC2 Karmic Kernel Status
[18:14] <rtg> bjf, I think ec2 is looking OK.
[18:14] <bjf> rtg, want to take that?
[18:14] <bjf> [TOPIC] Status: Karmic (rtg, apw)
[18:14] <MootBot> New Topic:  Status: Karmic (rtg, apw)
[18:15] <apw> we just uploaded new master kernel with 2.6.31.2 stable updates
[18:15] <rtg> horked in mammoth stable update yesterday
[18:15] <apw> the last of the stable updates before release
[18:15] <apw> (most likely)
[18:16] <bjf> [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:16] <MootBot> New Topic:  Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:16] <smb> [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others
[18:16] <smb> * Dapper:   2.6.15-54.79 (security)
[18:16] <smb> * Hardy:    2.6.24-24.61 (updates)
[18:16] <smb> * Intrepid: 2.6.27-14.41 (updates)
[18:16] <smb> * Jaunty    2.6.28-15.52 (updates)
[18:16] <smb> \o/ no proposed kernels pending
[18:16] <pgraner> testing testing is this mic on?
[18:16] <bjf> [TOPIC] Incoming Bugs: Regressions (ogasawara)
[18:16] <MootBot> New Topic:  Incoming Bugs: Regressions (ogasawara)
[18:17] <ogasawara>  * Current regression stats:
[18:17] <ogasawara>   * 39 regression-potential https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-potential
[18:17] <ogasawara>   * 41 regression-release https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-release
[18:17] <ogasawara>   * 10 regression-update https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-update
[18:17] <apw> pgraner, reading you 20/20
[18:17] <ogasawara>   * 0 regression-proposed https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-proposed
[18:17] <ogasawara> Going forward in future meetings I'll also start providing a delta from the previous week so we can measure any trends.
[18:17] <bjf> [TOPIC] Incoming Bugs: Bug day report (ogasawara)
[18:17] <MootBot> New Topic:  Incoming Bugs: Bug day report (ogasawara)
[18:17] <ogasawara> Last week's stats can be seen at http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090929.html
[18:17] <ogasawara> Approximately 20% (54 bugs) were tackled.
[18:17] <ogasawara> Unfortunately there was no major community involvement this time around.
[18:18] <ogasawara> but we are getting hits from interested community members
[18:18] <bjf> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:18] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:19] <bjf> pgraner, anything?
[18:19] <pgraner>  
[18:19] <bjf> going, once
[18:19] <bjf> going, twice
[18:19] <bjf> gone!
[18:19] <bjf> #endmeeting
[18:19] <MootBot> Meeting finished at 12:19.
[18:19] <pgraner> ogasawara: what about all the bugs JFo did on Global Jam?
[18:19] <apw> bjf, thanks
[18:20] <cking> is that a record?
[18:20] <smb> bjf, thanks
[18:20] <lieb_> tnx bjf
[18:20] <smb> cking, Feels like
[18:20] <pgraner> I got a bad lag
[18:20] <ogasawara> pgraner: indeed, that's were a lot of our non bug day contributions are coming from
[18:20] <cking> I'm still 5 mins behind
[18:20] <rtg> pgraner, its killing me today. there must be some widespread carnage
[18:20] <pgraner> ogasawara: Ok so you don't consider Global Jam in with bug day
[18:21] <ogasawara> pgraner:  I considered it separate
[18:21] <pgraner> It only updates when I send somethng
[18:21] <pgraner> then I get a big burst of incoming text
[18:21] <pgraner> ogasawara: Ok thanks
[19:08] <seiflotfy> hey guys
[19:08] <seiflotfy> is the membership meeting over?
[19:09] <seiflotfy> ah still 2 hours
[20:56]  * twright waiting for ubuntu membership meeting
[20:56]  * forumsmatthew is too.
[20:56] <forumsmatthew> Greetings, everyone!
[20:58] <twright> greetings
[20:59]  * rafael_carreras too
[20:59] <twright> hi rafael_carreras :-)
[20:59] <joaopinto> hi
[20:59] <rafael_carreras> hi twright
[21:00] <twright> hi everyone
[21:00] <jarlen> hey there
[21:00] <popey> o/
[21:01]  * twright would not have remembered if not for evolution :-)
[21:01]  * popey pokes Seveas 
[21:01] <seiflotfy> hi guys
[21:01] <seiflotfy> :)
[21:01] <stgraber> hello, I'm currently at a customer, I may not be able to attend at least part of the meeting
[21:01] <popey> ok, lets move quick then! :)
[21:02] <popey> who's up first?
[21:02] <seiflotfy> uhm
[21:02] <seiflotfy> me?
[21:02] <seiflotfy> :)
[21:03] <popey> https://wiki.ubuntu.com/Membership/RegionalBoards/EMEA
[21:03] <popey> hmm, we still have
[21:03] <forumsmatthew> The first person listed, Sarvatt, is already a member. We can move to the next person.
[21:04] <popey> Sarvatt and pgquiles
[21:04] <forumsmatthew> see his provile
[21:04] <forumsmatthew> profile
[21:04] <popey> pgquiles is being dealt with by Daniel for MOTU
[21:04] <twright> I don't think jeansch is in the chanel
[21:04] <seiflotfy> o hshit forgot to list myslef
[21:04] <seiflotfy> can i stil ldo that
[21:05] <forumsmatthew> put it at the end and we'll see if we have time
[21:05] <popey> ok twright you're up!
[21:05] <twright> great
[21:06] <popey> At this point we like people to have a few lines about themselves ready to paste into the channel
[21:06] <twright> ok
[21:06] <popey> everyone else waiting, can you have yours ready
[21:07] <twright> Just got the stuff from the wiki
[21:07] <twright> I have installed Ubuntu at least 100 times over the past 3 years, on just about every PC in my house and others whilst helping other to use it in person, online and even in at concerts and in newsagents (don't ask!). At the same time I have created mockups and graphics for several Ubuntu release cycles and OpenOffice.org and consistently ran and reported/helped with bugs on development releases (Karmic is my main system at the moment) but I still wan
[21:07] <twright> t to become more involved in the project and thus am looking to become a Ubuntu member, blog more tips and tutorials and help out anywhere I can.
[21:07] <twright> not to long I hope
[21:08] <popey> there are some links on your wiki page to artwork pages..
[21:08] <twright> yes... mainly those I created
[21:08] <popey> you created some artwork?
[21:09] <twright> the pages, not the artwork
[21:09] <popey> ok
[21:09] <twright> I have done a lot of mockups though
[21:09] <popey> do you have anyone here to cheer for you?
[21:10] <twright> sorry, no
[21:10] <popey> ok
[21:10] <twright> although there is quite a lot of positive feedback on the wiki pages
[21:11] <popey> I'm going to vote -0 for now on the basis that I'd like to see a more sustained contribution and some feedback from other members on your wiki page.
[21:11] <forumsmatthew> I don't see any testimonials on your wiki page
[21:11] <twright> e.g. 'Wow, I love this. I think it is so simple. yet so amazing. It's inspired me, I wish that 8.10 will looks like this. It would be a great achievement.'
[21:11] <popey> I would recommend that you continue contributing and come back to us in ~3 months..
[21:11] <forumsmatthew> popey beat me to it
[21:11] <twright> right, thank you
[21:12] <forumsmatthew> -0, but hopeful for next time
[21:12] <popey> stgraber?
[21:12] <popey> i agree forumsmatthew, we need more young people singing Ubuntu from the rooftops!
[21:12] <stgraber> I'd like to see more evidence of contribution as well. +0
[21:13] <popey> great, keep up the good work twright !
[21:13] <twright> thank you
[21:13] <popey> joaopinto.. you're up!
[21:13] <joaopinto> Hello all
[21:13] <joaopinto> I am FOSS developer and Linux user since 1999, for details check my wiki page: https://wiki.ubuntu.com/JoaoPinto
[21:13] <joaopinto> I am an Ubuntu user since 2006, with a significant intial participation on support, irc and forums
[21:13] <joaopinto> Later I have developed interested for debian packaging, my main work is now on the non official projects getdeb & playdeb
[21:13] <joaopinto> I am also a regular tester and bug reporter.
[21:14] <joaopinto> and that's all :)
[21:14] <popey> You package for getdeb?
[21:14] <forumsmatthew> I think he started it, didn't he?
[21:14] <joaopinto> yes, I am the project founder
[21:14]  * popey bows down
[21:15] <popey> nice testimonial from Tiago!
[21:15]  * seiflotfy is star struck by joaopinto
[21:15] <popey> seiflotfy: pssst.. me too ;)
[21:15] <joaopinto> :)
[21:16] <forumsmatthew> I've been aware of your contributions for a long time, going back to the start of getdeb and stuff
[21:16] <popey> ok, that's an easy +1 from me. It's clear to see a sustained and helpful contribution to the community. I know I've used getdeb before personally. I appreciate the work you do
[21:16] <forumsmatthew> +1
[21:16] <stgraber> +1
[21:16] <popey> wheee!
[21:16] <joaopinto> Thanks :))
[21:17] <popey> added you to ~ubuntumembers, welcome!
[21:17] <hggdh> way to go, joapinto! and no need for cheering ;-)
[21:17] <popey> oh, you had people here to cheer!?
[21:17] <joaopinto> eheh, thank you all :)
[21:17] <popey> who?
[21:17]  * hggdh was
[21:17] <hggdh> or is ;-)
[21:17] <popey> excellent, thanks for coming hggdh
[21:17] <jarlen> I'm not here to cheer, but if he started getdeb, I'd like to, anyway :)
[21:18] <popey> :)
[21:18] <popey> okay, next up is rafael_carreras
[21:18] <rafael_carreras> that's right
[21:18] <rafael_carreras> Hello, I'm Catalan LoCo Team Contact. I founded it back in 2006.
[21:18] <rafael_carreras> I've been KDE translator for several years
[21:18] <rafael_carreras> I began using GNU/Linux with a Mandrake in 1999 and I remained quite attached to it until Ubuntu Warty came. I have been running the GLUG Caliu (CAtalan GNU/LInux Users) since 2001 as its Secretary. I organize the Software Freedom Day in Barcelona every year since 2005.
[21:18] <popey> What do you guys do for SFD typically?
[21:19] <rafael_carreras> talk to people in the street
[21:20] <rafael_carreras> in the center of  Barcelona
[21:20] <popey> oh excellent, thats fun :)
[21:20] <alexm> popey: http://www.flickr.com/photos/alexm/collections/72157602674952585/ has some sets
[21:20] <rafael_carreras> but this year we did a more serious event
[21:20] <rafael_carreras> speeches and all in a nice place
[21:20] <rafael_carreras> quite good attendance
[21:20] <popey> did you get many attendees?
[21:21] <forumsmatthew> I was about 90% ready to give an enthusiastic +1, then I saw this: http://rcarreras.caliu.cat/2006/11/07/la-meva-batleth/ . Now, I'm sure...
[21:21] <rafael_carreras> yes, about 50 people, i'd say
[21:21] <forumsmatthew> good testimonials, sustained presence, and a batleth
[21:21] <rafael_carreras> forumsmatthew: :)
[21:21] <alexm> forumsmatthew: qapla!
[21:21] <popey> http://www.flickr.com/photos/siscogarcia/3522814910/ cute T-shirts :)
[21:22] <popey> well, I'm impressed with the sustained effort, +1 from me!
[21:22] <rafael_carreras> good dessigners on our LoCo
[21:22] <popey> great idea doing children-sizeed t-shirts
[21:22] <stgraber> +1 from me too
[21:22] <alexm> popey: catalan loco t-shirts http://www.flickr.com/photos/alexm/3978203588/
[21:22] <popey> i need to get some of those for my kids :)
[21:23] <popey> they are awesome!
[21:23] <forumsmatthew> agreed
[21:23] <arualavi> my daughter got one and love it
[21:23] <popey> ok, thats 3 +1's you're a member! Keep up the fantastic work!
[21:23] <alexm> popey: http://www.cafepress.co.uk/ubuntu_cat
[21:23] <popey> I look forward to seeing karmic photos
[21:24] <rafael_carreras> thaks a lot!
[21:24] <rafael_carreras> popey: you'll see
[21:24] <tsdgeos> \o/
[21:24] <stgraber> heading back to the office now, sorry. I'll be back in 20 min or so. If we still have quorum without me, I'd like to say a huge +1 to seiflotfy for his work (met him at UDS-Barcelona, well, rather Zurich in fact) :)
[21:24] <alexm> congrats rafael_carreras :)
[21:24] <popey> :)
[21:24] <forumsmatthew> congratulations!
[21:24] <popey> blog it on planet ubuntu now you can :)
[21:24] <popey> thanks stgraber !
[21:24] <forumsmatthew> thank you
[21:24] <popey> Jarlen you're up next
[21:24]  * jarlen steps forward
[21:25] <jarlen> I'm an active member and part of the formal leadership of the danish LoCo, and have been for some years now, my main contributions have been through the local team and as LoCo contact for most of the current year. I've helped arrange release parties and helped make it work on-site. I'm also working on the (belated) Global Jam, the danish team is having next saturday.
[21:25] <jarlen> I'm a moderator on the danish LoCo's forum and have spent a lot of time moderating, assisting, teaching others, and writing guides.
[21:25] <jarlen> I've been the driving force on the new website for the danish team, and the process of moving to a new CMS (Drupal).
[21:25] <jarlen> Furthermore I'm co-host of the newly started Ubuntu-dk podcast.
[21:25] <jarlen> oh yeah... and I wear my Ubuntu t-shirt in public :P
[21:25] <popey> haha
[21:25] <popey> podcasting huh? :)
[21:26] <soren> I can wouch for jarlen as well. He's been around for ages and have been doing rocking work all along.
[21:26] <popey> thanks soren
[21:26]  * sbc is also here to cheer for jarlen.
[21:26] <popey> jarlen: good to see another european podcast
[21:26] <soren> I can also spell vouch correctly.
[21:26] <jarlen> Yeah, recently started a danish podcast, got it accepted for iTunes and all (I guess that's a good idea?)
[21:26] <popey> jarlen: we get 50% of our listeners from itunes.. so yeah, i guess ;)
[21:26] <eitreach> jarlen is an excellent driving force in the community. Committed and hard-working.
[21:27] <popey> jarlen: what did you plan for 8.10 release party? danish beer?
[21:27]  * Snigepige cheers for jarlen, a good guy, devoted and always got a minute to help others
[21:27] <jarlen> We've only released 1 chapter so far, but I think we have 2-3 more bewing
[21:27] <jarlen> personally I plan danish beer for every occasion I can
[21:27] <popey> ;)
[21:27] <forumsmatthew> lol
[21:27] <jarlen> but I've promised the others that I'll save it 'till the evening
[21:27] <popey> https://wiki.ubuntu.com/DanishTeam/Arrangementer/IntrepidReleaseParty i like the poster, very professional
[21:28] <jarlen> we'll spend all day in a mall trying to talk to people, show off what our ubuntu-machines can do
[21:28] <jarlen> and try and convince regular people to not waste money on OSs
[21:28] <popey> are you finding more people are already knowing what it is? or are most of them unaware of Ubuntu?
[21:28] <jarlen> yeah, we have some good guys doing graphics :)
[21:29] <jarlen> well, I'm studying at a technical university, so of course I'm surrounded by more linux-aware people than most others
[21:29] <jarlen> on the streets it's a different story, and my t-shirt is rarely recognized
[21:29] <popey> heh
[21:29] <forumsmatthew> :)
[21:29] <popey> I meant in the streets
[21:30] <jarlen> though we did have 60-70 people showing up for our release party in copenhagen for 7.10
[21:30] <popey> wow
[21:30] <popey> thats great
[21:30] <jarlen> and one of our large rooms turned into install help and ubuntu support
[21:30] <popey> right, ready fo	?
[21:30] <popey> er
[21:30] <popey> right, ready forumsmatthew
[21:30] <forumsmatthew> I like what I'm seeing, and with the cheering squad that turned up here, 'm happy
[21:30] <jarlen> so apparantly there was a lot non-too-tech-savy people who were interested
[21:30] <forumsmatthew> +1
[21:31] <popey> +1 from me too
[21:31] <popey> great work and great cheers, thanks to those who came along to cheer along..
[21:31] <jarlen> thank you :)
[21:31] <popey> keep up the great work
[21:32] <forumsmatthew> congratulations!
[21:32] <jarlen> soren, eitreach and sbc especially
[21:32] <forumsmatthew> MajestyX doesn't have a wiki page listed. That's always been a requirement, so we can have a list of activities, testimonials, etc. in one place
[21:32] <popey> https://wiki.ubuntu.com/Majestyx
[21:32] <forumsmatthew> great!
[21:32] <popey> i think it's just a busted link
[21:33] <popey> but Majestyx isnt here...
[21:33] <forumsmatthew> doh!
[21:33] <forumsmatthew> let's move on then
[21:33] <popey> ok
[21:33] <popey> seiflotfy: we've run out of time sorry
[21:33] <popey> kidding!
[21:33] <forumsmatthew> lol
[21:33] <seiflotfy> popey: ok
[21:33] <seiflotfy> :P
[21:33] <seiflotfy> so
[21:33] <popey> :)
[21:33] <seiflotfy> Hello my name in Seif Lotfy. I have been using Linux since 2001 mostly SuSE and Debian. Switched to Ubuntu November 2004.
[21:34] <seiflotfy> Most of my work is however upstream contribution, so I understand if my work is not considered Ubuntu.
[21:34] <seiflotfy> I used to work on GNOME projects such Gimmie and founded the Zeitgeist and GNOME Zeitgeist Projects.
[21:34] <seiflotfy> Most of my work is done very closely with Ubuntu users and Canonical employees to provide a unified experience on Ubuntu.
[21:34] <seiflotfy> Also I followed their suggestion to make it KDE compatible and fulfill all dependanceis supported by Ubuntu.
[21:34] <seiflotfy> I installed Ubuntu for almost every family member now. And turned the finance department of the family business (around 30 Computers) to use Ubuntu.
[21:35] <seiflotfy> I am one of the first Egyptian Loco Team members. And since the Loco Team is a bit down lately.
[21:35] <seiflotfy>  I have started some studies to determine howto deploy more Ubuntu and FLOSS in the middle east and which obstacles are being faced. This study i will present at the next UDS.
[21:35] <popey> you're going to UDS-L ?
[21:35] <seiflotfy> yeah
[21:35] <seiflotfy> self financed
[21:35] <seiflotfy> since i did not get sponsorship
[21:35] <seiflotfy> :)
[21:35] <popey> thats dedication
[21:35] <seiflotfy> last year too
[21:35] <seiflotfy> as in alst uds barcelona
[21:35] <seiflotfy> was self financed
[21:36] <seiflotfy> u can chekc out my wiki
[21:36] <seiflotfy> https://wiki.ubuntu.com/SeifLotfy
[21:36] <forumsmatthew> you have some very nice testimonials
[21:36] <forumsmatthew> is there anyone here to cheer?
[21:36] <seiflotfy> no1 really i think
[21:36] <seiflotfy> only
[21:36] <seiflotfy> (10:24:48 PM) stgraber:
[21:36] <seiflotfy> heading back to the office now, sorry. I'll be back in 20 min or so. If we still have quorum without me, I'd like to say a huge +1 to seiflotfy for his work (met him at UDS-Barcelona, well, rather Zurich in fact) :)
[21:36] <popey> that helps :)
[21:37] <forumsmatthew> I realize not all of your activites are purely Ubuntu centered, but they do benefit us
[21:37] <seiflotfy> yeah sorry :(
[21:37] <forumsmatthew> Also, there is some good community support for your application
[21:37] <seiflotfy> i try my best
[21:37] <popey> please dont apologise..
[21:37] <popey> we need upstream!
[21:38] <popey> we're a theme and a notifcation bubble without it ;)
[21:38] <forumsmatthew> I am actually looking at your application very positively
[21:38] <nixternal> ahh, RMB meeting...was wondering who was adding all these new Ubuntu members... CONGRATS!
[21:38] <nixternal> congrats to you to popey !!!
[21:38] <popey> you too nixternal ;)
[21:38] <forumsmatthew> hey, nixternal
[21:38] <forumsmatthew> :)
[21:38] <popey> ok, lets vote
[21:38] <forumsmatthew> so, for seiflotfy I'm +1
[21:38] <djsiegel_> +1
[21:38] <forumsmatthew> and I look forward to meeting you in Dallas
[21:39] <popey> we have a very positive +1 from stgraber, and I'm gonna +1 too based on great testimonials from respected people
[21:39] <forumsmatthew> congratulations!
[21:39] <djsiegel_> way to go, Seif!
[21:39] <popey> congratulations, and I too look forward to meeting you in Dallas!
[21:39] <seiflotfy> thanks guys
[21:39] <seiflotfy> :)
[21:39] <popey> and..
[21:40] <popey> gimmie gimmie!
[21:40] <popey> thats everyone isn't it?
[21:40] <popey> we're done
[21:40] <forumsmatthew> yep
[21:40] <forumsmatthew> thanks, everyone!
[21:41] <popey> ^5
[21:41] <seiflotfy> thanks guys
[21:42]  * popey goes back to sleep
[21:44] <seiflotfy> thanks guys
[21:44] <seiflotfy> back to hacking
[21:44] <popey> \o/
[21:44] <seiflotfy> popey: yeah we r rewriting the API now
[21:44] <seiflotfy> Do and Docky ftw
[21:44] <seiflotfy> :)
[21:45] <popey> great!
[21:45] <popey> I might have to grab you for an interview for the podcast soon :)
[21:45] <seiflotfy> sweet
[21:45] <seiflotfy> :)
[21:46] <kalon33> ;)
[21:46] <seiflotfy> ok really need to handle some hacking here
[22:02] <Rocket2DMn> let's rock n roll