[09:35] <kcleung> Is the REVU meeting on now?
[14:00] <lool> Meeting?
[14:00]  * ogra twiddles thumbs
[14:00] <GrueMaster> if you insist.
[14:00] <paulliu> hi
[14:00] <bjf> hi
[14:01] <davidm> hi
[14:01]  * ogra tries to not burn his fingers on the hot kbd ... laptop still building mono
[14:02] <lool> plars, dyfet: ping
[14:02] <dyfet> here
[14:03] <lool> #startmeeting
[14:03] <MootBot> Meeting started at 08:03. The chair is lool.
[14:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:03] <lool> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090721
[14:03] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090721
[14:04] <lool> [topic] Action Items from July 14th, 2009
[14:04]  * plars is here
[14:04] <lool> I'll skip over #
[14:04] <lool> NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 (co)
[14:04] <lool> for now as NCommander isn't around
[14:04] <lool> GrueMaster: GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809
[14:04] <GrueMaster> co
[14:05] <MootBot> New Topic:  Action Items from July 14th, 2009
[14:05] <lool> [action] (2nd co) NCommander to investigate  https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148
[14:05] <MootBot> ACTION received:  (2nd co) NCommander to investigate  https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148
[14:05] <lool> [action] (2nd co) GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809
[14:05] <MootBot> ACTION received:  (2nd co) GrueMaster to retest on i386 https://bugs.launchpad.net/ubuntu/+source/linux/+bug/337809
[14:05] <lool> [topic] changing the form of the meeting: everybody would update its spec's status in the whiteboard and we'd review a page summarizing status
[14:05] <MootBot> New Topic:  changing the form of the meeting: everybody would update its spec's status in the whiteboard and we'd review a page summarizing status
[14:06] <lool> I'm voluntarily skipping over Specification Review as it is impacted by this proposal  :)
[14:06] <lool> So I've sent this proposal to the mailing list
[14:06] <plars> yep
[14:06] <lool> The idea is basically for everybody to edit the whiteboard of their specs to reflect status
[14:06]  * ogra gave comments via IRC, sorry for not putting them in mail yet
[14:06] <lool> Just like for Work items, we'd have a one line summary or couple of lines summary of status
[14:07] <lool> This would allow generation of an overview page which we would all review during the meeting and then we'd have an open floor for questions
[14:07] <lool> The goal is to have always available information (not buried in a meeting log) and to skip over the long blueprint pingpong
[14:07] <ogra> ++
[14:08] <lool> Opinions?  Comments?  Reactions?  :)
[14:08] <plars> lool: I didn't see ogra's comments, have there been any objections to this idea raised by him, or anyone else?
[14:08] <lool> ogra: ^
[14:08] <ogra> i didnt really understand the purpose when we started discussing it
[14:08] <ogra> the more i thought bout it the more i liked it
[14:09] <lool> Cool
[14:09] <davidm> I like the idea, personally
[14:09] <lool> plars: I'm not 100% sure but I think it's the only critic I received
[14:09] <ogra> my initial proposal was to have at least per person status reports only on the items that block you thought
[14:09] <lool> Which was IIRC "it sounds like additional work and I don't see the point"
[14:09] <ogra> but i think these are not needed
[14:09] <ogra> s/thought/though/
[14:10] <plars> right, it's basically just a one line update on a wiki page, similar to what you'd be doing on irc if we still did it in-meeting right?
[14:10] <ogra> lool's proposal as it stands is fine
[14:10] <lool> So if there are no objections, I propose we add a "Status:" entry to whiteboards; I'll send a mail about that
[14:10] <ogra> though it requires that we actually prapare a bit more
[14:10] <plars> I like it
[14:10] <ogra> *pre
[14:10] <lool> [action] lool to send email about Status: in whiteboards
[14:10] <MootBot> ACTION received:  lool to send email about Status: in whiteboards
[14:10] <lool> [action] lool to implement script to dump blueprints' statuses
[14:11] <MootBot> ACTION received:  lool to implement script to dump blueprints' statuses
[14:11] <lool> As a related topic
[14:11] <davidm> plars, it an entry on the blueprint whiteboard not a wiki page
[14:11] <lool> [topic] adding work items to all specs which we work on
[14:11] <MootBot> New Topic:  adding work items to all specs which we work on
[14:11] <davidm> plars, from that a wiki status page can be generated
[14:11] <plars> davidm: I see now, from lool's later comments :)
[14:12] <ogra> lool, shouldnt that be an action instead of topic ? :)
[14:12] <lool> plars: Right, sorry, I went a bit fast; it's like Work items: on https://blueprints.launchpad.net/ubuntu/+spec/mobile-karmic-armel-toolchain
[14:12] <lool> So on this new topic, I'd like to ask everyone to please update or add Work items: to their specs
[14:13] <lool> Currently the burndown chart isn't terribly useful because it only works with a subset of the specs/work items which we really want to track
[14:13] <lool> These are the errors I currently get from the cron http://paste.ubuntu.com/223547/
[14:14] <lool> Some specs should be clarified and are not really ours (e.g. hw-emablement or mid-karmic-use-mer) in which case I'll drop them from the list
[14:15] <ogra> mobile-arm-karmic-offline-installer-gui has workitems
[14:15]  * ogra sonders what he did wrong
[14:15] <lool> So you have an empty line
[14:15] <ogra> ah, right
[14:15] <ogra> fix your script :P
[14:15] <lool> The format should be "Work items:" and then one work item per line directly afterwards
[14:16] <lool> ogra: No, it could be anything after the Work items
[14:16] <lool> Also format of work items should be "Froble with foobar: TODO" or DONE or DEFERRED
[14:16] <lool> fixed for this spec
[14:17] <GrueMaster> lool:  For future reference it would be nice to have a document specifying the format you would like to have, instead of coming back and saying we need to fix the specs after we have already written them.
[14:17] <plars> lool: perhaps, if your email about stus updates could include the format for the rest of it as well, that would be helpful
[14:17] <plars> s/stus/status
[14:17] <lool> GrueMaster: that's fair
[14:17] <lool> GrueMaster: Would you mind picking this up?
[14:17] <lool> plars: it will; thanks for the suggestion
[14:17] <GrueMaster> No, because I don't know the exact format that your script is looking for.
[14:17] <lool> It's pitti's script actually
[14:18] <lool> The format is the one I documented above
[14:18] <plars> is that script available in bzr somewhere?
[14:18] <paulliu> lool: OK. I'll document it.
[14:18] <lool> it's available publicly
[14:18] <lool> plars, GrueMaster: http://piware.de/bzr/bin/workitems.py
[14:19] <lool> the chart generator albeit unrelated is at lp:~rick-rickspencer3/+junk/py-burndown-chart
[14:19] <lool> The script is called like:
[14:19] <lool> 03 3 * * * bzr update -q $HOME/bin; $HOME/bin/workitems.py -d data/desktop-workitems.db -r karmic -p 'desktop-karmic-' -m 'https://wiki.ubuntu.com/Kubuntu/Todo/Karmic?action=raw'; $HOME/bin/workitems.py -d data/desktop-workitems.db --csv --to 2009-10-01 | python ubuntu/py-burndown-chart/burndown.py --output=www/www/tmp/desktopteam-burndown-karmic.png -s 300 --height=450 --title='Desktop Team Karmic Burndown' -
[14:19] <lool> BTW this is the current burndown chart URL http://piware.de/tmp/mobileteam-burndown-karmic.png
[14:20] <lool> This is hosted on pitti's server for now due to lack of deps on people.ubuntu.com or people.canonical.com
[14:20] <lool> Any question?
[14:20] <lool> Ok moving to Specification Review
[14:20] <lool> [topic] Specification Review
[14:20] <MootBot> New Topic:  Specification Review
[14:21] <lool> So hopefully our last pingpong week
[14:21] <lool> [link] https://blueprints.launchpad.net/~canonical-mobile?show=all
[14:21] <MootBot> LINK received:  https://blueprints.launchpad.net/~canonical-mobile?show=all
[14:21] <lool> ogra: Mind updating us on your specs?
[14:22] <lool> paulliu, plars: I'll give an update on my specs next and then it will be your turn
[14:22] <ogra> subarches in debian cd ... i started fiddling with the renaming on the weekend ...
[14:22] <ogra> but am not done yet, the buildd issues are way to pressing to do any spec work this week until we have sorted that
[14:22] <ogra> so my full focus is on that
[14:22] <ogra> (mesa building atm here in chroot)
[14:23] <lool> No update on freescale-desktopm easy-rb-mgmt offline-installer-gui and general-resolution-touchscreens?
[14:23] <ogra> i fiddled with a qemu static build that if it enters karmic will speed up rootstock massively
[14:23] <ogra> (this is for offlibe installer gui)
[14:23] <ogra> touchscreens are still not started
[14:24] <ogra> freescale desktop is waiting for HW which i'm supposed to recive soon
[14:24] <lool> ogra: How's A3 looking WRT freescale/mx51?
[14:24] <ogra> (and indeed for the renaming changes in cdimage/debian-cd)
[14:24] <ogra> well
[14:25] <ogra> given that compiz FTBFS thanks to the 40 KDE packages being stuck on the buildd i'D say very bad
[14:25] <ogra> beyond not having mesa
[14:25] <lool> It's uninstallable?
[14:25] <ogra> how would it be installable without kernel ?
[14:25] <lool> I'm speaking of compiz and mesa
[14:25] <ogra> well, the wrong version will be installed
[14:26] <ogra> livefs'es build, images build
[14:26] <lool> That's better than nothing
[14:26] <ogra> http://cdimage.ubuntu.com/ports/daily-live/20090721/ looks good so far but isnt of much use
[14:26] <MootBot> LINK received:  http://cdimage.ubuntu.com/ports/daily-live/20090721/ looks good so far but isnt of much use
[14:26] <lool> ogra: Is it reasonnable to target these two specs for a4?
[14:26] <ogra> yeah
[14:26] <ogra> looks like we will have a working kernel by A4
[14:27] <lool> done
[14:27] <ogra> the changes for imx51 arent hard, uboot scripts will be a bit
[14:27] <ogra> but easier if i have HW
[14:27] <ogra> done
[14:27] <lool> On my own specs, I didn't do any progress on the cloud stuff which I considered lower priority; I want to get something decent started before our sprint
[14:28] <lool> Concerning the toolchain bits, it's stuck on hardware for buildds as qemu isn't a serious option anymore, sadly
[14:28] <lool> As soon as v7 buildds are deployed we can bump the toolchain reqs and move on
[14:28] <ogra> qemu-system-arm is way to slow
[14:28] <lool> paulliu: Could you update us on your specs' status?
[14:28] <lool> GrueMaster: You're next after plars
[14:29] <ogra> (which is why i went down the -static/binfmt road as well with rootstock)
[14:29] <paulliu> Yes. I've request to enable compatible mode in connman packaging.
[14:29] <paulliu> So the rest is to add it into our seed and start debugging.
[14:29] <paulliu> For app-resolutions sorry I still don't have time to look on that.
[14:30] <lool> paulliu: Could you add work items to your specs?
[14:30] <paulliu> lool: yes.
[14:30] <lool> paulliu: What do you think are reasonnable delivery milestones for each spec?
[14:31] <paulliu> lool: before karmic?
[14:31] <paulliu> lool: What do you mean milestones?
[14:31] <lool> paulliu: alpha 4, 5, 6, beta, rc etc.
[14:32] <lool> (I just changed the implementation of mobile-unr-karmic-connman to "Started" since you mentionned work on it)
[14:32] <paulliu> For connman alpha 5 is good.
[14:32] <lool> paulliu: I think connman should land before FF
[14:32] <lool> Ok, let's go for A5
[14:32] <paulliu> lool: yes, the early the better.
[14:32] <lool> Agreed
[14:32] <paulliu> lool: And app-resolution for beta.
[14:32] <lool> Ok
[14:32] <lool> Specs updated with milestones
[14:33] <lool> paulliu: Anything you're blocked on?  Need help with?
[14:33] <paulliu> lool: it's ok. I'll push the maintainer and/or the upstream.
[14:34] <lool> paulliu: Thanks
[14:34] <lool> plars: How are specs going for you?
[14:34] <plars> mobile-qa-karmic-arm and mobile-qa-karmic-unr now have testplans linked on testcases.qa.ubuntu.com
[14:34] <plars> have good progress writing checkbox testcases
[14:34]  * StevenK appears, having lost track of time :-(
[14:34] <lool> Hi StevenK we're reviewing specs status ATM; could you prepare a couple of lines of summary on the ones you're assigned to?  thanks
[14:34] <plars> some manual (guided) and some automated
[14:35] <plars> will be syncing up with cgregan and other soon on testcases to see what can be leveraged for each others' benefits
[14:35] <plars>  mobile-unr-karmic-compliance-autotesting  is unblocked now, kinda
[14:35] <StevenK> The only left is -wubi, which requires me to have more time
[14:35] <lool> plars: Should some implementation statuses say "Good progress"?  Do you have an ETA for delivery of these specs?
[14:36] <lool> StevenK: After GrueMaster if you don't mind
[14:36] <StevenK> Tell me when
[14:36]  * ogra hands StevenK a bag with some minutes in it :)
[14:36] <ogra> there, time :)
[14:36] <plars> UNR one is coming along more quickly than arm one, I'd like to have them with something available for use by alpha4, though I fully expect the set of tests to continue to grow after that
[14:36] <plars> on the compliance autotesting one
[14:37] <plars> that's the one for application screensize/resolution testsuite
[14:37] <plars> The bug affecting LDTP that was blocking me on that is not fixed yet, but I've narrowed it down to the changeset
[14:37] <lool> plars: Ok changed it to good progress and targeted to A5, there's no rush to have it in A4, if we do that's nice
[14:37] <plars> ok
[14:37] <plars> this one is lower priority than the other two though
[14:38] <plars> but the testing benefits the UNR testing overall
[14:38] <plars> so it's really nice to have
[14:38] <lool> plars: Do you think beta is a good target for the testcases specs?
[14:38] <plars> yes, hopefully... I'll have *something* at beta, but I may not have coverage for all apps by that time
[14:39] <lool> ok updated
[14:39] <plars> thanks
[14:39] <lool> GrueMaster: Hola
[14:39] <lool> GrueMaster: I updated mobile-karmic-lsb-compliance-testing slightly last week; any issue wit hit?
[14:39] <lool> *it
[14:40] <GrueMaster> morning.  I have updated the mobile-karmic-lsb-compliance-testing even more since then.  I have added a new work item to move the lsb test results to wiki.ubuntu.com
[14:41] <lool> GrueMaster: I just merged the two Work items: sections into one
[14:41] <GrueMaster> I will also be testing alpha3 this week as soon as they hit iso.qa
[14:41] <lool> GrueMaster: Given the nature of it, I'm targetting it for final since you'll effectively deliver the final work items after final
[14:42] <GrueMaster> No, I am targeting moving the test results for this week.
[14:42] <lool> GrueMaster: Anything else you'd like to raise on the topic of specs?
[14:42] <lool> GrueMaster: I mean I targetted the *spec* for delivery with final
[14:42] <GrueMaster> Ok,
[14:42] <lool> Since one work item is to test final
[14:43] <lool> GrueMaster: Ok thanks
[14:43] <lool> StevenK: Now would be a good time to update us on your specs  :)
[14:43] <lool> dyfet__: You're next
[14:43] <ogra> he's growing underscores since he joined ...
[14:43] <GrueMaster> on the mobile-unr-karmic-applications, davidm and I had decided to abandon it due to lack of communication from the other players.  Since then, I have seen an update on the blueprint (still no email) from Pete asking why.
[14:43] <dyfet__> assuming i survive connectivity issues...
[14:44] <StevenK> Right, -wubi requires more time, which I'll be doing next week
[14:44] <lool> GrueMaster: Actually repete offered clarifications on this spec; I'm happy to participate in a phone call to help rescue the UNR apps spec
[14:44] <StevenK> -translations requiring reviewing and also more time
[14:44] <StevenK> Can anyone see a theme?
[14:44] <lool> StevenK: So you're doing translations after all?
[14:44] <GrueMaster> Pete has also updated the spec wiki to include a new list of applications, which I have been reviewing since last week.
[14:45] <StevenK> lool: I did the first step, by moving them to main.
[14:45] <GrueMaster> ok, guess I'm done.  sigh.
[14:45] <StevenK> I'll be discussing the next steps with dpm tomorrow.
[14:45] <lool> StevenK: Is there a spec about UNR updates for karmic?
[14:45] <StevenK> If you have a phone call about UNR apps, please invite me.
[14:45] <StevenK> lool: UNR updates? Why?
[14:45] <lool> GrueMaster: Sorry, I thought you were done two minutes ago
[14:46] <GrueMaster> I can't type as fast as some of you guys.  Especially without coffee.
[14:46] <lool> StevenK: Because we'll get some UNR drops to push to karmic
[14:46] <StevenK> lool: And? They get uploaded as normal, they don't require that much paperwork
[14:47] <lool> StevenK: Ok; so there are no plans to track karmic's UNR as a spec; I would have found such a spec a better place to document the MIR work for UNR for instance
[14:47] <lool> I don't mind if you think it can simply happen immediately
[14:47] <StevenK> Er, it didn't ... ?
[14:47] <StevenK> I'm confused
[14:48] <lool> StevenK: I'm not tracking UNR plans for karmic closely; I can't comment on the scale of the task
[14:48] <ogra> btw, wasnt there some discussion about the name ?
[14:48] <ogra> does it stay ?
[14:48] <lool> That's not our call
[14:48] <ogra> (just a question out of interest)
[14:48] <lool> StevenK: Anything else you'd like to discuss with your specs?
[14:49] <StevenK> I can't think of any, I'm not really trying to drive -translations, just prod it to get started.
[14:49] <lool> StevenK: Could you please update status of poulsbo-packaging and mobile-hildon-input-methods to reflect their current status?  (Implemented/deferred/obsolete etc.)
[14:50] <StevenK> And having UNR in main was a goal of mine, irrspectively of specs
[14:50] <lool> (These are not targeted at karmic, but would be nice to get them cleared of your list)
[14:50] <StevenK> And translations, etc, etc, handwave
[14:50] <lool> StevenK: That's alright
[14:50] <lool> StevenK: What's the expected delivery milestone for mobile-unr-karmic-wubi?
[14:51] <StevenK> lool: It was supposed to be alpha 3, but I suck
[14:51] <StevenK> Now alpha 4
[14:51]  * ogra doesnt ask for armel support this week :)
[14:51] <lool> I made it Alpha 4 thanks
[14:51] <lool> GrueMaster: Getting back to you, since I skipped too fast to StevenK
[14:51] <lool> GrueMaster: Anything else you'd like to discuss WRT specs?
[14:51] <GrueMaster> What more can I add?  I only have the two, and one has been silently killed off.
[14:51] <lool> GrueMaster: I'm available if you'd like help clarifying/resucing the UNR apps/seed spec with repete
[14:52] <lool> I think it's unfair to call it silently killed off
[14:52] <GrueMaster> I really don't even know what I am supposed to do with that spec.  I only offered to help stevenk with the writeup after UDS.  I'm not sure what direction it is supposed to go in.
[14:53] <lool> I think it was trying to cover too many things at once and was a bit of an undocumented/unclear list of changes as a result
[14:53] <GrueMaster> It was silently killed off because no one was responding to my email inquiries.
[14:53] <lool> If you or StevenK have some genuine interest in getting some of this stuff in karmic, let us work with repete to clarify it
[14:54] <lool> I think we could have an efficient phone meeting to kick it off again
[14:54] <lool> GrueMaster: Ok; let's chat about this off meeting if you don't mind
[14:55] <lool> dyfet: How are you doing with specs?
[14:55] <plars> we are almost out of time
[14:55] <dyfet> well...with the lxde spec, we had community elections for packages to have in the lubuntu seed...
[14:56] <lool> dyfet: So you have a clear plan?
[14:56] <dyfet> yes
[14:56] <lool> dyfet: What the expected delivery milestone?
[14:57] <lool> dyfet: alpha 6?
[14:57] <lool> It's the latest we can add flavours IMO
[14:57] <dyfet> well, it was a low priority spec, but we could target before a6 :)
[14:57] <lool> Ok I made it alpha 5
[14:57] <ogra> lool, it wont be a flavout
[14:57] <lool> but please add work items to the spec
[14:57] <ogra> *r
[14:57] <ogra> only a seed and metapackage
[14:57] <lool> Ok
[14:57] <lool> dyfet: anything else?
[14:57] <dyfet> yes, I kept your notes from earlier on work item comments :)
[14:58] <dyfet> not related to specs...waiting for hw today though
[14:58] <lool> Ok done with specs then
[14:58] <lool> [topic] ihgh prio bugs
[14:58] <MootBot> New Topic:  ihgh prio bugs
[14:58] <StevenK> Depends if you want things like CD builds
[14:58] <lool> https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:58] <lool> StevenK: That one would be for you
[14:58] <StevenK> And before FF is MUCH better
[14:58] <lool> https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel
[14:58] <lool> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:58] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-unr
[14:59] <lool> StevenK: Can you push the new webfav soon?
[14:59]  * StevenK waves his arms furiously
[14:59] <lool> We're running out of time; if people have other commitments they are welcome to go attend; I think we will be done in 5 to 10 mns
[14:59] <StevenK> I only have so much time :-(
[14:59] <StevenK> lool: I'm trying
[15:00] <lool> StevenK: I don't need it next week, but ff3.5 is a karmic goal
[15:00] <lool> bfiller said it was a one line change though  :)
[15:00] <StevenK> lool: I'm well aware, but there are other things wrong with webfav, which need addressing
[15:00] <lool> StevenK: Ok; I'm noting that you don't have much time but will look into it in a near guture
[15:01] <lool> *future
[15:01] <lool> StevenK: ack
[15:01] <lool> [link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel
[15:01] <MootBot> LINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel
[15:01] <lool> dyfet: What about banshee?  This bug has been open in a long while
[15:01] <lool> dyfet: It would be nice to get some debug action  :)
[15:01] <dyfet> I know...I had not been able to get banshee to run far enough to hit that failure on arm
[15:02] <ogra> what HW do you have atm ?
[15:02] <lool> I just assigned myself to the ffmpeg ARM opts bugs 383240
[15:02] <dyfet> well, there is the b1....and the marvell board I cannot run X on and that has an ancient kernel...
[15:03] <ogra> ffmpeg looks like it will only work if we compile with --cpu=armv7-a
[15:03] <lool> dyfet: What's wrong with the B1?
[15:05] <dyfet> when I try it on the b1, I get a failure in dbus init in banshee long before it gets to anything else...
[15:05] <ogra> you try to run it remotely ?
[15:05] <ogra> that wont work
[15:05] <ogra> banshee checks for a local session dbus
[15:05] <lool> ogra: Could you help dyfet get moving on this bug?
[15:06] <ogra> yes
[15:06] <lool> dyfet: Please bring up such issues before we discover them in the meeting; you could document them in the bug or raise them to us on IRC any time  :)
[15:06] <dyfet> I think it is something simple...and I was expecting to get new hw today also
[15:06] <lool> Ok; moving to low prio bugs
[15:06] <lool> There are way too many bugs to review
[15:07] <lool> plars, GrueMaster: Could you guys help us deal with the now larger lists of bugs?
[15:07] <lool> [link] https://bugs.launchpad.net/~canonical-mobile
[15:07] <MootBot> LINK received:  https://bugs.launchpad.net/~canonical-mobile
[15:07]  * ogra notices thats a reoccuring sentence lool emits every release cycle
[15:07] <lool> I wish these be triaged into armel / UNR / other bugs
[15:07] <plars> lool: I plan to spend some omre time triaging today
[15:07] <lool> [link] https://bugs.launchpad.net/~ubuntu-unr
[15:07] <MootBot> LINK received:  https://bugs.launchpad.net/~ubuntu-unr
[15:07] <lool> and
[15:07] <plars> lool: I could use some help on it
[15:07] <lool> [link] https://bugs.launchpad.net/~ubuntu-armel
[15:07] <MootBot> LINK received:  https://bugs.launchpad.net/~ubuntu-armel
[15:08] <lool> GrueMaster: Could you help plars triaging these?
[15:08] <GrueMaster> Looking now.
[15:08] <lool> GrueMaster: As well as New bugs against UNR packages
[15:08] <ogra> lool, hmm, your list has fix released bugs in it
[15:08] <plars> it's not hard, just can be tedious... but the main thing at the moment is to get bugs figured out whether they are specific to ARM/UNR or not, and if so, subscribe them to the appropriate team... if not, remove the tag
[15:08] <GrueMaster> How do you want me to go about armel bugs without a working image?
[15:08] <ogra> bug 390591 is surely not affecting karmic
[15:08] <plars> GrueMaster: you don't need a working image for the most part on this, and UNR is the one that needs the most attention
[15:09] <lool> plars, GrueMaster: What I'd love for the other lists would be bugs without any Undecided/Unknown prio and in state Confirmed or Triaged
[15:09] <plars> general triaging would be useful too of course, but getting the bugs identified correctly is a big part of that
[15:09] <lool> ogra: it's targetted at jaunty, which we still support
[15:09] <ogra> right
[15:09] <lool> Ok; we had a long meeting already
[15:10] <ogra> i thought NCommander wanted to make a backport request
[15:10] <plars> GrueMaster: I'll get with you about it later
[15:10] <GrueMaster> Bug #345126 has been release-noted
[15:10] <lool> I think a week wont be enough to triage all these but we should revisit next week
[15:10] <lool> [topic] AOB
[15:10] <MootBot> New Topic:  AOB
[15:10] <lool> This is a chance to discuss any other important business?
[15:10] <ogra> none, close ....
[15:11] <lool> Crap there was something I wanted to mention but I forgot about
[15:11] <lool> Lucky you
[15:11] <lool> Ok thanks a lot folks
[15:11] <lool> #endmeeting
[15:11] <MootBot> Meeting finished at 09:11.
[15:12] <ogra> heh
[16:00] <kirkland> o/
[16:00] <ttx> o/
[16:00] <sommer> yo
[16:00]  * mathiaz waves
[16:01] <mathiaz> let's get the Ubuntu Server team meeting started
[16:01] <mathiaz> #startmeeting
[16:01] <MootBot> Meeting started at 10:01. The chair is mathiaz.
[16:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:01] <nijaba> o/
[16:01] <mathiaz> Today's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting
[16:02] <mathiaz> thanks ttx for running the meeting last week
[16:02] <mathiaz> ttx: and publishing the minutes
[16:02]  * stgraber waves
[16:02] <ttx> you're welcome.
[16:02] <mathiaz> Last week minutes: https://wiki.ubuntu.com/MeetingLogs/Server/20090714
[16:02] <mathiaz> [TOPIC] #
[16:02] <mathiaz> SRU tracking on server-related packages.
[16:02] <MootBot> New Topic:  #
[16:03] <mathiaz> [TOPIC] SRU tracking on server-related packages.
[16:03] <MootBot> New Topic:  SRU tracking on server-related packages.
[16:03] <mathiaz> ttx: what's you proposal on this subject?
[16:04] <ttx> We need to better track Server-related SRU candidates. Basically monitor the development release updates for changes that could make sense in previous releases
[16:04] <ttx> to define where we want to use our resources to push them to completion.
[16:05] <ttx> So someone could monitor the list, look up the changes and list relevant ones on a wikipage. They would get discussed at the team meeting
[16:05] <Omahn> I would be willing to help in that effort.
[16:05] <ttx> once approved, we would assign them to the ubuntu-server team and make sure they pass the process.
[16:05] <mathiaz> ttx: in my experience SRU candidates are mainly coming from bugs
[16:05] <Omahn> I currently look through the SRU list for updates relevant to servers, mainly for LTS releases though as we mainly use LTS builds.
[16:05] <ttx> mathiaz: yes.
[16:06] <mathiaz> ttx: I'm not sure that monitoring karmic-changes would help
[16:06] <mathiaz> ttx: the problem we're trying to solve is to get more SRU completed or to identify more candidates for SRU?
[16:07] <ttx> mathiaz: I would say, to make sure we SRU all relevant bugs
[16:07] <ttx> and give a forum where their appropriateness would get discussed
[16:07] <mathiaz> ttx: right - so I'd rather focus on the ubuntu-server-bugs mailing list then
[16:07] <ttx> but you're right that -changes monitoring is not enough.
[16:07] <mathiaz> ttx: it seems that karmic-changes is to noisy
[16:07]  * kirkland cheers ttx on
[16:07] <ttx> We need to catch all FixReleased.
[16:08] <mathiaz> ttx: agreed - for a specific list of packages (relevant to the server team)
[16:08] <Omahn> Does a list of packages relevant to the server team exist?
[16:09] <Omahn> (Or is it just common sense?)
[16:09] <mathiaz> Omahn: https://bugs.launchpad.net/~ubuntu-server/+packagebugs
[16:09] <mathiaz> sbeattie: how do yo track relevant SRU bugs?
[16:10] <mathiaz> sbeattie: is there a process in the bug team to track which bugs are currently under an SRU process?
[16:10] <ttx> That doesn't mean we'll do a lot more SRUs, just give some confidence that we are not missing anything important.
[16:10] <mathiaz> ttx: ok - so there is already a list of bugs that are targeted for SRU
[16:10] <mathiaz> ttx: what's we're trying to achieve here is to get more relevant bugs on that list?
[16:11] <ttx> mathiaz: you mean the bugs nominated for a release ?
[16:11] <mathiaz> ttx: yes
[16:12] <mathiaz> ttx: if someone thinks a bug should be fixed in a stable release, one of the first step is to nominate that bug for the target release
[16:12] <ttx> Basically I want to find a way to have a team discussion on what nominated bugs should be approved.
[16:13] <ttx> and assign the key ones to the team rather than expect that the original poster has the nerves to push them to completion.
[16:13] <mathiaz> ttx: ok
[16:13] <mathiaz> ttx: https://bugs.launchpad.net/ubuntu/hardy/
[16:13] <mathiaz> ttx: this is the list of bugs related to hardy
[16:13] <ttx> unfortunately the current nomination acceptation process is a one-man decision right now
[16:14] <mathiaz> ttx: and you can search for all bugs to which the ubuntu-server is a subscriber
[16:15] <mathiaz> ttx: http://tinyurl.com/nmxppq
[16:15] <ttx> mathiaz: can you see those where hardy has been nominated but not accepted ?
[16:15] <mathiaz> ttx: ^^ this is the list of bugs *accepted* for hardy to which the ubuntu-server team is subsribec
[16:15] <mathiaz> ttx: good question - sbeattie or slangasek would know the answer about it
[16:16] <mathiaz> ttx: hm - there is a review nominations link in the page above
[16:16] <mathiaz> ttx: https://bugs.launchpad.net/ubuntu/hardy/+nominations
[16:17] <ttx> mathiaz: so we could use the nomination process to track them.
[16:17] <mathiaz> ttx: http://tinyurl.com/lm7ogv
[16:17] <mathiaz> ttx: and ^^ this is the url relevant to the ubuntu-server tema
[16:17] <ttx> mathiaz: /someone/ would track bugs and make sure nominations are filed were relevant
[16:18] <ttx> and we would review the nominations in the team meeting
[16:18] <ttx> then potentially assign the key ones to the team
[16:18] <mathiaz> ttx: right. The process may be semi-automated by processing the ubuntu-server-bugs mailing list archive
[16:19] <mathiaz> ttx: and present a list of bugs marked 'Fix released' on a period of time
[16:19] <mathiaz> bdmurray: do you have a script that does this^?
[16:19] <ttx> The missing part today is someone making sure everything relevant is nominated.
[16:19] <mathiaz> ttx: agreed.
[16:20] <mathiaz> ttx: so what we could do is to have a weekly review in this meeting about the bugs that have been fixed released in the last week
[16:20] <mathiaz> ttx: and make sure the relevant ones are nominated, approved, assigned, etc...
[16:21] <ttx> mathiaz: I fear that might take too long ?
[16:21] <ttx> mathiaz: what if someone volunteered to track FixReleased and turn them all to nominations where appropriate ?
[16:21] <zul_> why not have like a weekly posting to the ubuntu server mailing list like the kernel-team
[16:21] <ttx> then we could review only those that make sense to be SRUed
[16:22] <mathiaz> ttx: then the burden to accept the nominations would fall on the ubuntu-sru team
[16:22] <mathiaz> ttx: how about trying to setup the list and review it in the next meeting
[16:22] <ttx> mathiaz: you mean only ubuntu-sru should accept a nomination ? I think most devs can.
[16:23] <mathiaz> ttx: and put a maxmimum time we spend on it (say 10 mn)
[16:23] <ttx> ubuntu-sru accept the SRU more tan the nomination
[16:23] <mathiaz> ttx: that way we get the ball rolling and see if we need to make some adjustement in the process
[16:23] <ttx> mathiaz: worksforme
[16:23] <mathiaz> ttx: right - -devs can accept nominations
[16:24] <mathiaz> ttx: IIUC we're trying to come up with a way to make sure that *all* relevant bugs end up in the nomination process
[16:25] <ttx> yes. a bug might be valid but not make a good SRU. That's the -sru teams decisions.
[16:25] <ttx> accepting nominations is more ack-ing that the issue applies to a given release.
[16:25] <mathiaz> ttx: and the proposal is to get a list if fixed bugs in the last week, review it in the server meeting and nominated relevant ones
[16:26] <ttx> I would even nominate/accept them.
[16:26] <kirkland> ttx: mathiaz: can we experiment on libvirt and kvm?  both of these are in jaunty-proposed at the moment
[16:26] <kirkland> I mean, experiment on the publicity, call-for-testing
[16:27] <mathiaz> kirkland: ah right. I'm not sure how that is relevant to the discussion here.
[16:27] <mathiaz> kirkland: testing comes after the SRU has been proccessed
[16:27] <mathiaz> kirkland: ie one of the very last stage of the SRU process.
 [TOPIC] SRU tracking on server-related packages.
[16:27] <mathiaz> kirkland: we're focusing here on the very first step of the process
[16:27] <kirkland> okay
[16:28] <kirkland> i think the last step is important too :-)   testing in -proposed, which I suspect very little happens
[16:28] <mathiaz> kirkland: how to make sure relevant bugs don't fall off the ubuntu-server radar.
[16:28] <mathiaz> kirkland: yes - definetly
[16:28] <mathiaz> kirkland: this is probably the subject of another topic
[16:28] <ttx> well, we should also weekkly-review the status of the ones we committed to do.
[16:28] <mathiaz> let's break things down in manageable chunks
[16:29] <mathiaz> ttx: right - so let's move on
[16:29] <ttx> but I agree that's another part of the SRU puzzle.
[16:29] <mathiaz> I think we have a plan
[16:29] <mathiaz> I'll talk to bdmurray to see if/how we can get a list of fixed bugs
[16:30] <mathiaz> [ACTION] mathiaz to come up with a  way to generate a list of fixed bugs in the last week for packages relevant to the server team
[16:30] <MootBot> ACTION received:  mathiaz to come up with a  way to generate a list of fixed bugs in the last week for packages relevant to the server team
[16:30] <mathiaz> anything else on this particular topic?
[16:31] <mathiaz> nope - let's move on
[16:31] <mathiaz> anything else regarding last week minutes/meeting?
[16:32] <mathiaz> nope - let's move on
[16:32] <mathiaz> [TOPIC] Preparing a 2009 edition of the Server Survey
[16:32] <MootBot> New Topic:  Preparing a 2009 edition of the Server Survey
[16:32] <mathiaz> nijaba: ^^?
[16:32] <nijaba> yes, it has been a year since we launched our first survey
[16:32] <nijaba> or it will be in sept
[16:33] <nijaba> so it is time to start updating our question set for this coming sept
[16:33] <nijaba> anyone interested in helping could have a look at the wiki
[16:33] <nijaba> and file bugs against the project with suggestions?
[16:34] <mathiaz> nijaba: which wiki page?
[16:34] <nijaba> https://wiki.ubuntu.com/ServerTeam/Survey
[16:35] <mathiaz> nijaba: so v1.0.4 was used as the final set of questions for the last survey?
[16:35] <nijaba> also, the limesurvey package needs to be updated.  if anyone feels up to it...
[16:35] <nijaba> mathiaz: yep
[16:36] <mathiaz> nijaba: great - seems like everything is there to get the survey updated.
[16:36] <mathiaz> nijaba: any changes needed to the policy?
[16:36] <nijaba> mathiaz: not that I know of
[16:36] <mathiaz> nijaba: great.
[16:36] <nijaba> mathiaz: but it could use a review if anyone feels up to it
[16:37] <mathiaz> nijaba: any changes to the Launch plan?
[16:37] <mathiaz> nijaba: or is this something to be discussed later?
[16:37] <mathiaz> nijaba: also - what is the timeframe for the launch?
[16:37] <nijaba> mathiaz: good question.  It can be discussed later, but from the last survey, 50% of the respondent came from the banner on ubuntu.com
[16:38] <nijaba> mathiaz: end of sept is my target
[16:38] <mathiaz> nijaba: did you get in touch with the ubuntu-news/marketing team?
[16:38] <nijaba> mathiaz: not yet
[16:39] <mathiaz> ok - any specific action item to record on this topic?
[16:40] <nijaba> mathiaz: just the call for review...
[16:40] <mathiaz> nijaba: writing a blog post?
[16:41] <nijaba> mathiaz: good idea...  i will
[16:41] <mathiaz> nijaba: great.
[16:41] <mathiaz> [ACTION] nijaba to write a blog post asking for review of the ubuntu-server survey questions.
[16:41] <MootBot> ACTION received:  nijaba to write a blog post asking for review of the ubuntu-server survey questions.
[16:41] <mathiaz> anything else on this topic?
[16:41] <nijaba> not from me
[16:42] <mathiaz> ok - let's move on then
[16:44] <mathiaz> [TOPIC] Roadmap refresh
[16:44] <MootBot> New Topic:  Roadmap refresh
[16:44] <mathiaz> what have you been up to in the next week for karmic?
[16:45] <mathiaz> what have you been up to in the *last* week for karmic?
[16:45] <mathiaz> RoAkSoAx: ^^?
[16:45] <RoAkSoAx> mathiaz, working on ipvsadm (updating it to 1.25) which includes support for ipv6
[16:46] <RoAkSoAx> though I have some doubts about how to handle the CFLAGS in debian/rules, so if someone is an expert on the subject and has some free time to help me, please let me know :)
[16:46] <Daviey> nice.
[16:46] <mathiaz> RoAkSoAx: have you asked in ubuntu-motu?
[16:46] <mathiaz> RoAkSoAx: you may be able to find some help there
[16:47] <mathiaz> RoAkSoAx: what else is needed to get packages in shape for karmic?
[16:47] <RoAkSoAx> then I already have a testing howto for heartbeat-pacemaker to do a call for testing, however I'm waiting to have latest pacemaker which I believe ivoks was working on.
[16:47] <RoAkSoAx> mathiaz, I did asked -motu with no luck :)
[16:48] <mathiaz> RoAkSoAx: ok - is there a wiki page somewhere to track what needs to be done?
[16:49] <RoAkSoAx> mathiaz, in the Ubuntu-HA team no. We don't have a wikipage for that
[16:49] <mathiaz> RoAkSoAx: there is a roadmap section on https://wiki.ubuntu.com/UbuntuHighAvailabilityTeam
[16:49] <mathiaz> RoAkSoAx: could this section be updated with the plan for karmic?
[16:50] <mathiaz> RoAkSoAx: just give a list of relevant packages that need to be updated in the archive
[16:50] <RoAkSoAx> mathiaz, sure. Will work on it.
[16:51] <mathiaz> RoAkSoAx: and a short description of how the cluster stack would look like in karmic
[16:51] <mathiaz> RoAkSoAx: great thanks.
[16:51] <RoAkSoAx> will do :)
[16:51] <mathiaz> [ACTION] RoAkSoAx to update the Roadmap section of the Ubuntu HA team with a short description of how the cluster stack would look like in karmic
[16:51] <MootBot> ACTION received:  RoAkSoAx to update the Roadmap section of the Ubuntu HA team with a short description of how the cluster stack would look like in karmic
[16:53] <mathiaz> kirkland: how is powernap going?
[16:53] <kirkland> mathiaz: i've been working on cloud power management
[16:53] <kirkland> powernap + powerwake are two opensource pieces of it
[16:53] <kirkland> going well
[16:53] <kirkland> uploaded, promoted to main
[16:53] <kirkland> dan nurmi of eucalyptus has
[16:54] <kirkland> added hooks into eucalyptus
[16:54] <kirkland> to use powernap to suspend/hibernate/poweroff cloud nodes when unused
[16:54] <kirkland> and powerwake to resume them when demand requires
[16:54] <mathiaz> kirkland: is there anything to be tested?
[16:54] <kirkland> UEC is now a "breathable" cloud
[16:54] <kirkland> well, i think powernap is actually generally useful for servers
[16:55] <kirkland> sort of like a screensaver, but instead of saving your screen, you're saving your powerbill
[16:56] <mathiaz> kirkland: and the planet
[16:56] <kirkland> i'm interested in other ideas, use cases, servers where powernap can be used
[16:56] <kirkland> mathiaz: yes, and on a more grand and noble basis, the planet :-)
[16:56] <kirkland> mathiaz: i'm actually using it on my mythfrontend machines
[16:56] <Daviey> kirkland: Are there any check mechanisms that you would like help with implementing?
[16:56] <kirkland> mathiaz: suspending those when they're not doing anything
[16:56] <kirkland> Daviey: heh, actually, there is at least one :-)
[16:56] <kirkland> Daviey: i have a mechanism that watches for activity on devices (so /dev/tty1 /dev/ptmx and friends)
[16:56] <mathiaz> kirkland: right - and resuming them as fast as possible when you have an urgent need to watch a movie
[16:57] <kirkland> Daviey: and one that watches ps/2 keyboards/mice on /proc/interrupts
[16:57] <Daviey> ^^ Also support USB keyboards?
[16:57] <kirkland> Daviey: i need a way of watching a usb keyboard/mouse with activity *not* happening on a console
[16:57] <Daviey> ahh.. too quick :)
[16:57] <kirkland> Daviey: so, usb keyboard/mouse activity in gnome, for instance
[16:57] <kirkland> low priority, since the server doesn't include X
[16:57] <mathiaz> kirkland: ok - we're running out of time
[16:57] <kirkland> but would be nice to have
[16:58] <kirkland> powernap is python code, btw!
[16:58] <mathiaz> kirkland: do you have a place to track the list of improvment?
[16:58] <Daviey> kirkland: grab you later :)
[16:58] <mathiaz> all right - time to wrap up
[16:58] <kirkland> mathiaz: launchpad
[16:58] <mathiaz> [TOPIC] Agree on next meeting date and time
[16:58] <MootBot> New Topic:  Agree on next meeting date and time
[16:59] <mathiaz> next week, same time, same place?
[16:59] <sommer> +1
[17:00] <mathiaz> great then. next week, same time, same place.
[17:00] <mathiaz> and happy alpha3 testing!
[17:00] <mathiaz> #endmeeting
[17:00] <MootBot> Meeting finished at 11:00.
[17:00] <Daviey> \o/
[17:00] <sommer> thanks mathiaz, later on all
[18:00]  * apw zones in ...
[18:00]  * smb arrives on the bong
[18:00]  * jjohansen waves
[18:00]  * ogasawara waves
[18:00] <apw> Roll Call for the kernel team meeting
[18:00]  * rtg_ is here
[18:00]  * amitk here
[18:00] <apw> #startmeeting
[18:00] <apw> This is the Kernel Weekly Meeting
[18:00] <apw> Agenda for this weeks meeting:
[18:00] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <MootBot> Meeting started at 12:00. The chair is apw.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00]  * awe waves
[18:01] <apw> [TOPIC] Open Action Items: (amitk) Remove Blueprints: kernel-karmic-bug-handling from list
[18:01] <MootBot> New Topic:  Open Action Items: (amitk) Remove Blueprints: kernel-karmic-bug-handling from list
[18:01]  * cking here
[18:01] <apw> think that one can be called done
[18:01] <amitk> done
[18:01] <apw> [TOPIC] Open Action Items: (apw, ogasawara) Mark Blueprints: kernel-karmic-bug-handling as complete
[18:01] <MootBot> New Topic:  Open Action Items: (apw, ogasawara) Mark Blueprints: kernel-karmic-bug-handling as complete
[18:01] <ogasawara> done
[18:01] <apw> wicked thanks
[18:01] <apw> [TOPIC] Open Action Items: (cking) to send email about Blueprints: kernel-karmic-ssd
[18:01] <MootBot> New Topic:  Open Action Items: (cking) to send email about Blueprints: kernel-karmic-ssd
[18:01] <cking> done
[18:01] <apw> nice
[18:01] <apw> [TOPIC] Open Action Items: (apw) clean up status of Blueprints: kernel-karmic-flavours
[18:01] <MootBot> New Topic:  Open Action Items: (apw) clean up status of Blueprints: kernel-karmic-flavours
[18:01] <apw> this one is also done
[18:02] <apw> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:02] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:02]  * apw spits feathers at OSD
[18:02] <apw> [TOPIC] Karmic Release Status: Milestoned Features
[18:02] <MootBot> New Topic:  Karmic Release Status: Milestoned Features
[18:03] <ogasawara> Release Meeting Bugs - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:03] <ogasawara> RC Milestoned bugs - none for Alpha 3 or Alpha 4
[18:03] <ogasawara> Release Targeted Bugs - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux
[18:03] <ogasawara> Milestoned Features - https://launchpad.net/ubuntu/+milestone/karmic-alpha-3
[18:03] <apw> ogasawara, how we looking for alpha-3, it being to late to spin the kernel anyhow
[18:03] <ogasawara> apw: looking good, we have no bugs targetted
[18:04] <apw> [TOPIC] Blueprints: kernel-karmic-hwdb-workshop
[18:04] <MootBot> New Topic:  Blueprints: kernel-karmic-hwdb-workshop
[18:04]  * manjo waves
[18:04] <apw> that one need to be on here any more?
[18:04] <ogasawara> There's ongoing discussion in bug 338772
[18:04] <ogasawara> Also, access to hwdb data has been restricted to the hwdb-team.  The kernel team has been added as a member of this team.
[18:04] <ubott2> Launchpad bug 338772 in checkbox "Data from `lshw` should be submitted to Launchpad" [High,Confirmed] https://launchpad.net/bugs/338772
[18:04] <ubott2> Ubuntu bug 338772 in checkbox "Data from `lshw` should be submitted to Launchpad" [High,Confirmed]
[18:04] <ubott2> Launchpad bug 338772 in checkbox "Data from `lshw` should be submitted to Launchpad" [High,Confirmed] https://launchpad.net/bugs/338772
[18:04] <ogasawara> whoa
[18:04] <apw> heh nice
[18:04] <ogasawara> apw: that's it for now
[18:04] <apw> [TOPIC] Blueprints: kernel-karmic-kernel-config-review
[18:04] <MootBot> New Topic:  Blueprints: kernel-karmic-kernel-config-review
[18:05] <apw> Commonised a chunk of the remaining options on the ubuntu architectures, this included crypto and filesystem options.  This is essentially complete now the remaining updates if any will come as part of testing.
[18:05] <apw> i recon this one has gone about as far as it can ... and propose we call it done
[18:05]  * rtg_ agrees
[18:05] <amitk> +1
[18:05] <apw> [ACTION] apw to close kernel-karmic-kernel-config-review
[18:05] <MootBot> ACTION received:  apw to close kernel-karmic-kernel-config-review
[18:05] <apw> [TOPIC] Blueprints: kernel-karmic-kms
[18:05] <MootBot> New Topic:  Blueprints: kernel-karmic-kms
[18:06] <apw> Things are generally quiet on KMS at the moment.  We are expecting a block of updates for i915 in the next rebase to 2.6.31-rc4 when that is ready.  ATI userspace is likely to be ready for ATI Radeon KMS sometime after alpha-3 releases, and we can switch it on by default.  Testing continues to be pretty encouraging, lots of fixes being pushed up to the kernel by intel as a result of our testing.
[18:06] <apw> [TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts
[18:06] <MootBot> New Topic:  Blueprints: kernel-karmic-new-kernel-on-lts
[18:07] <rtg_> stalled, too many Karmic issues lately.
[18:07] <apw> ack
[18:07] <apw> [TOPIC] Blueprints: kernel-karmic-review-of-non-upstreamed-code
[18:07] <MootBot> New Topic:  Blueprints: kernel-karmic-review-of-non-upstreamed-code
[18:07] <smb> There are only a few items remaining but no progress on those, currently.
[18:07] <apw> we probabally can review whats left at sprint and call it good then?
[18:07] <smb> sounds like a plan
[18:07] <rtg_> and drop those aren't being compiled
[18:08] <apw> yeah we should do that
[18:08] <rtg_> s/those/those that/
[18:08] <apw> [ACTION] smb organise a sprint session on to review our delta
[18:08] <MootBot> ACTION received:  smb organise a sprint session on to review our delta
[18:08] <apw> [TOPIC] Blueprints: kernel-karmic-android
[18:08] <MootBot> New Topic:  Blueprints: kernel-karmic-android
[18:08] <apw> i assume this is still waiting for resource
[18:08] <bjf> apw, yes
[18:09] <apw> ack
[18:09] <apw> [TOPIC] Blueprints: kernel-karmic-sponsoring-staging-drivers
[18:09] <MootBot> New Topic:  Blueprints: kernel-karmic-sponsoring-staging-drivers
[18:09] <apw> and this also waiting for resource
[18:09] <apw> [TOPIC] Blueprints: kernel-karmic-suspend-resume
[18:09] <MootBot> New Topic:  Blueprints: kernel-karmic-suspend-resume
[18:09]  * apw prods manjo
[18:09] <manjo> nothing to report was working on ARM issues all week
[18:09]  * ogra hugs manjo 
[18:09] <apw> ok waiting on resource there too
[18:10] <apw> [TOPIC] Blueprints: kernel-karmic-wifi
[18:10] <MootBot> New Topic:  Blueprints: kernel-karmic-wifi
[18:10] <rtg_> working on rfkill
[18:10]  * manjo thanks ogra
[18:10] <apw> we do have a bunch of inversions and the like reported on rfkill
[18:10] <apw> or devices disabled by default
[18:10] <rtg_> its kind of non-functional in some cases.
[18:10] <apw> should we be pointing you at them?
[18:11] <rtg_> not yet. I need to figure out how its supposed to work.
[18:11] <apw> heh i think we expected that, its a major rewrite in there for sure
[18:11] <manjo> so rt2x00 upgrade was turned down...
[18:11] <rtg_> I'm working with slangasek on acpi-support and wireless-tools
[18:11]  * awe sends sympathy to rtg
[18:11] <smb> manjo, well as the big thing, yes
[18:12] <apw> i assume thats the one in ubuntu/
[18:12] <manjo> no its in main dirs
[18:12] <manjo> drivers/.../wireless
[18:12] <smb> right
[18:12] <smb> but the big diff included a completelly new (and apparently broken) driver
[18:12] <apw> something to get discussed on the mailing list perhaps?
[18:13] <manjo> apw, it was
[18:13] <apw> so is that something we need to talk about now, or take offline?
[18:14] <manjo> we can take it off line
[18:14] <smb> I guess take offline
[18:14] <rtg_> manjo, IIRC even the maintainer said it wasn't ready.
[18:14] <manjo> rtg_, correct
[18:14] <rtg_> seems like tahts the end of the story for now
[18:14] <manjo> k
[18:14] <apw> overall then not taking it yet seems appropriate, we await an updated version
[18:14] <apw> [TOPIC] Blueprints: kernel-karmic-better-power-mgt
[18:14] <MootBot> New Topic:  Blueprints: kernel-karmic-better-power-mgt
[18:15]  * apw suspects this is pending resource
[18:15] <amitk> pending
[18:15] <apw> [TOPIC] Other Release Tasks: AppArmor (jjohansen)
[18:15] <MootBot> New Topic:  Other Release Tasks: AppArmor (jjohansen)
[18:15] <jjohansen> still have the clone regression
[18:15] <jjohansen> and I know of two other oops, now
[18:15] <apw> in addition to the ones you fixed already?
[18:16] <jjohansen> yes
[18:16] <jjohansen> they are in change_profile, jamie reported it yesterday
[18:16] <apw> how are they looking, are they things people are likely to hit?
[18:16] <jjohansen> and one that is showing up in cred
[18:16] <jjohansen> no
[18:16] <jjohansen> jamie is working on a profile that uses changeprofile
[18:16] <apw> i suggest we sync with you before the next upload and decide if you think it is still safe to enable it
[18:17] <jjohansen> which would be the first time its been used in Ubuntu
[18:17] <jjohansen> yes
[18:17] <rtg_> jjohansen, do we have feature parity with Jaunty?
[18:17] <apw> [ACTION] apw/rtg to synv with Jjohansen before upload on AA enablement
[18:17] <MootBot> ACTION received:  apw/rtg to synv with Jjohansen before upload on AA enablement
[18:17] <jjohansen> rtg_: yes
[18:18]  * apw cheers
[18:18] <apw> [TOPIC] Other Release Tasks: ARM-Freescale (amitk, bjf)
[18:18] <MootBot> New Topic:  Other Release Tasks: ARM-Freescale (amitk, bjf)
[18:18] <bjf> imx51 is making good progress on all fronts
[18:18] <amitk> 6.6.31 imx51 kernel now boots and manages to stay alive
[18:19] <amitk> er 2.6.31
[18:19] <amitk> big thanks to manjo and dinh @ freescale
[18:19] <manjo> welcome
[18:19] <apw> souding good.  so are we expecting patches for karmic shortly?
[18:19] <amitk> I've integrated all the patches at http://kernel.ubuntu.com/git?p=amitk/ubuntu-fsl-2.6.31.git;a=summary in case anybody is interested
[18:19] <amitk> are we going to have a separate branch for this stuff?
[18:20] <amitk> I'm cleaning up the commit messages for uniformity and then I'll send a pull request shortly
[18:20] <rtg_> amitk, thats my understanding (for now)
[18:20] <bjf> I think it should go on an "arm" topic branch in the Karmic tree
[18:20] <apw> sounds good, we can get the same machinery smb used on jaunty and use that
[18:20] <amitk> it should be on the next upload for thur/fri as discussed with apw
[18:21] <amitk> _then_ I start porting part2 of the FSL patchset to 2.6.31
[18:21] <amitk> the stuff that bjf already SRU'ed into jaunty
[18:22] <amitk> thats it from my side
[18:22] <apw> ok
[18:22] <apw> [TOPIC] Other Release Tasks: 386 Flavour (apw)
[18:22] <MootBot> New Topic:  Other Release Tasks: 386 Flavour (apw)
[18:22] <apw> Testing has shown that the percieved performance gains from switching to i586 in the archive we actually due to gcc-4.4.
[18:22] <apw> Therefore the 386 flavour is required.  This has been reintegrated into the kernel package.  Item closed.
[18:22] <apw> [ACTION] apw to close the 386 flavour task
[18:22]  * apw pokes mootbot
[18:22] <apw> hrm
[18:23] <apw> [TOPIC] Other Release Tasks: Union Mount Solution (apw)
[18:23] <amitk> MootBot: kick
[18:23] <apw> The latest Karmic kernel now has aufs included.  Testing reports on the livecd have been good so far.  This item is basically done.  Will monitor for a bit then close.
[18:23] <MootBot> ACTION received:  apw to close the 386 flavour task
[18:23] <MootBot> New Topic:  Other Release Tasks: Union Mount Solution (apw)
[18:23] <apw> [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:23] <MootBot> New Topic:  Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb)
[18:23] <smb> * Dapper:   2.6.15-54.77 (security)
[18:23] <smb> * Hardy:    2.6.24-24.56 (updates)
[18:23] <smb>             Planning new proposed upload to get Acer Aspire Ones booting
[18:23] <smb> * Intrepid: 2.6.27-14.35 (security)
[18:23] <smb>             2.6.27-14.36 (proposed+security)[14] with 5/24 verifications
[18:23] <smb>             LRM-2.6.27-14.20 (updates)
[18:23] <smb> * Jaunty:   2.6.28-13.45 (security)
[18:23] <smb>             2.6.28-14.46 (proposed)[13] with 4/15 verifications
[18:23] <smb>             ABI bumping versions of LRM and LBM waiting as well
[18:23] <smb> So Intrepid and Jaunty need a bit more bugs verified against the proposed
[18:23] <smb> kernel.
[18:24] <apw> [TOPIC] Status: Karmic (rtg, apw)
[18:24] <MootBot> New Topic:  Status: Karmic (rtg, apw)
[18:24] <apw> Kernel is currently frozen for alpha-3.  We also have lots of updates for the ports architectures hopefully they will all build on the next upload.
[18:25] <apw> The big thing is the proposal to enable AA for the next upload.  Pending jjohansen's feedback
[18:25] <jjohansen> I think yes
[18:25] <apw> ack
[18:25] <apw> [TOPIC] Status: ARM (amitk, bjf)
[18:25] <MootBot> New Topic:  Status: ARM (amitk, bjf)
[18:25] <amitk> no more to add
[18:26] <apw> do we need this separate in general?
[18:26] <amitk> probably not if we have a blueprint
[18:26] <apw> ok ...
[18:26] <apw> [TOPIC] Status: Netbook (sconklin, apw)
[18:26] <MootBot> New Topic:  Status: Netbook (sconklin, apw)
[18:26] <apw> Released an updated Jaunty netbook release pulling us up to the tip of jaunty and pulling in some oem patches.
[18:26] <apw> we are waiting there on testing feedback
[18:27] <cking> ...no word yet
[18:27] <apw> [TOPIC] Incoming Bugs: Regressions (ogasawara)
[18:27] <MootBot> New Topic:  Incoming Bugs: Regressions (ogasawara)
[18:27] <ogasawara> 5 regressions were added to the bug list this week
[18:27] <ogasawara> 1 regression is already Fix Committed and 1 is In Progress
[18:27] <ogasawara> The remaining 3 are Triaged of which 1 is assigned to smb
[18:27] <awe> apw: ChickenCutlass uploaded it... no status yet
[18:27] <apw> we seem to be getting a lot of regressions all of a sudden
[18:27] <apw> is this due to more testing or?
[18:28] <ogasawara> apw: yes, that's the only explanation I can think of
[18:28] <apw> [TOPIC] Incoming Bugs: Bug day report (ogasawara)
[18:28] <MootBot> New Topic:  Incoming Bugs: Bug day report (ogasawara)
[18:28] <ogasawara> Off to a slow start today.  Refer to http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090721.html for current stats.
[18:28] <apw> with the bugs being assigned bugs in a lot of cases, they are likely to move from incomplete to incomplete
[18:29] <apw> and not change your apparent stats i guess
[18:29] <cking> sorry, I've been focused on OEM stuff today
[18:29] <apw> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:29] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:29] <ogasawara> apw: I was thinking that might be the case for some, I definitely don't think we'll see a large shift from open to closed
[18:29] <apw> ack
[18:30] <apw> 3...
[18:30] <apw> 2...
[18:30] <apw> 1...
[18:30] <apw> [TOPIC] Next Meeting Chair Selection
[18:30] <MootBot> New Topic:  Next Meeting Chair Selection
[18:30] <ogra> 0
[18:30] <apw> who's up
[18:30] <bjf> me
[18:30] <apw> ogra, simon didn't say
[18:30] <cking> good man
[18:30] <ogra> :)
[18:30] <apw> [ACTION] bjf to chair next meeting
[18:30] <apw> then i think we're done ... thanks all
[18:31] <apw> #endmeeting
[18:31] <MootBot> ACTION received:  bjf to chair next meeting
[18:31] <MootBot> Meeting finished at 12:31.
[18:31]  * apw shakes head at MootBot
[18:31] <amitk> MootBot: kick
[20:03] <nizarus> ping boredandblogging
[20:04] <nizarus> the LoCo council meeting is cancelled ?
[20:04]  * ausimage was wondering that
[20:05]  * DiegoTc ask the same question
[20:05]  * janc_ is here
[20:05]  * ausimage is here for New York State Ubuntu Team :D
[20:05] <nizarus> it's 19utc i'm not wrong ?
[20:06] <ausimage> I had it as 3pm EDT at least from my calculation
[20:06] <DiegoTc> yeap
[20:06] <boredandblogging> waiting on quorum
[20:06] <DiegoTc> http://www.timeanddate.com/worldclock/fixedtime.html?month=7&day=21&year=2009&hour=19&min=0&sec=0&p1=0
[20:06] <DiegoTc> its 19utc right now
[20:11] <janc_> juliux, popey: ping
[20:11] <popey> sorry I'm late
[20:12] <DiegoTc> no problem
[20:12] <DiegoTc> :)
[20:12] <janc_> we can start now, I guess?
[20:13] <popey> go for it
[20:13] <boredandblogging> yup
[20:15] <DiegoTc> :)
[20:16] <janc_> what order do we use, by date or by the table?  ;)
[20:17] <DiegoTc> table :p
[20:17] <janc_> okay Ireland first then
[20:18] <DiegoTc> janc_ Ireland wasn't approved on the last council meeting?
[20:19] <DiegoTc> https://wiki.ubuntu.com/UbuntuWeeklyNewsletter/Issue149#Irish%20Team
[20:20] <boredandblog_> yeah Ireland was last meeting
[20:21] <boredandblog_> slovenia?
[20:21] <DiegoTc> i don't about slovenia
[20:21] <DiegoTc> I am waiting for Honduras turn ;9
[20:21] <DiegoTc> ;)
[20:21] <janc_> I guess they were also last meeting then (considering the date on the table)
[20:22]  * ausimage waits for NYS, US :D
[20:22] <janc_> okay Honduras then
[20:22] <DiegoTc> :D
[20:23] <boredandblog_> DiegoTc: do you want to introduce honduras?
[20:23] <DiegoTc> okay
[20:23] <tatica1> :-D Honduras
[20:24] <DiegoTc> Well i am the team contact of U-hn
[20:24] <DiegoTc> by emails I met some persons interested on ubuntu, and with the help of the u-ni we organized our first evet this year
[20:25] <DiegoTc> we have received many help from the ubuntu centralamerican comunity, and we were plannung to organized some schools visits this month
[20:26] <DiegoTc> but we cancel because of the political problems the country is having right know
[20:26] <DiegoTc> we are 40 members, and actively 8-10 guys
[20:26] <janc_> ah, right, we heard about that...
[20:27] <DiegoTc> but we did one school visit this saturday
[20:27] <DiegoTc> the country is adpting to the changes
[20:27] <DiegoTc> and lets hope this doesn't stop us on out mission to spread ubuntu in the country
[20:28] <janc_> DiegoTc, how long does this LoCoTeam exist?
[20:28] <DiegoTc> janc_ funy question
[20:29] <DiegoTc> the team exists since 2007 i think, but it hasn't don't anything
[20:29] <DiegoTc> until this year
[20:29] <popey> would be good if there were dates on the events on the wiki
[20:29] <DiegoTc> when we started to move with help of the u-hn members as tatica1 which is here on the meeting
[20:30] <DiegoTc> popey the events have links to the events page
[20:30] <popey> https://wiki.ubuntu.com/HondurasTeam/Honduras_ApprovalApplication is the page I am talking about
[20:30] <janc_> seems like the renewed activity started around early March this year?
[20:30] <DiegoTc> yes
[20:31] <DiegoTc> actually febraury with our first IRc meeting
[20:31] <DiegoTc> https://wiki.ubuntu.com/HondurasTeam/Reuniones_IRC
[20:31] <janc_> I was guessing from the wiki page edit  ;-)
[20:31] <popey> mmm pizza
[20:31] <DiegoTc> hahaha
[20:31] <popey> yes, that's what I'm getting at, it would be nice if the page had dates on, thats all
[20:32] <DiegoTc> popey the pizza bash was one of our last events we did
[20:32] <DiegoTc> we have done, my mistake
[20:32] <popey> It looks like most of the activity has happened in the last 1-2 months..
[20:33] <popey> I'd like to see a longer period of sustained activity..
[20:33] <DiegoTc> we have on feb went we meet, march our first event, april, the flisol&jaunty party
[20:34] <DiegoTc> june and july also we did activities
[20:34] <janc_> well, preparing those events is activity too, but still at least 6 months would be nice to see
[20:35] <DiegoTc> well from feb-to july are 6 months
[20:35] <DiegoTc> ;)
[20:36] <DiegoTc> don't you think
[20:36] <popey> I'd like to see you guys and girls keep up the great work and come back to us around the karmic release.
[20:37] <DiegoTc> well thanks for all popey
[20:37] <DiegoTc> we will be here
[20:37] <boredandblog_> DiegoTc: keep up the good work
[20:37] <janc_> 7-2 = 5   ;)
[20:38] <DiegoTc> :(
[20:38] <DiegoTc> haha
[20:38] <DiegoTc> okay thanks
[20:39] <popey> Keep it going! Karmic release party - more pizza!
[20:39] <popey> NY up next?
[20:39]  * ausimage is here :D
[20:39]  * ausimage sure hopes our endurance qualifies us ;)
[20:40] <boredandblog_> can we get some sinatra in here?
[20:40] <boredandblog_> NY, NY
[20:40] <janc_> anyway, don't worry, NY State had to come back too, and it looks good for them now IMO  ;)
[20:40] <ausimage> even if sustained efforts wax and wane
[20:40] <ausimage> no not NY NY :(
[20:40] <ausimage> FingerLakes ;)
[20:40] <popey> Who's here for NY?
[20:40] <ausimage> O/
[20:41] <ausimage> popey I am...
[20:41] <popey> I have already looked through the pages for NY and I'm easily already +1
[20:41] <boredandblog_> agree with popey, +1
[20:41] <ausimage> awesome!
[20:41] <popey> impressive back catalog of work!
[20:42] <popey> I think a lot of teams can learn from you guys!
[20:42] <popey> and a magic approval application
[20:42] <ausimage> :)
[20:42] <ausimage> cproffit has been instrumental ;)
[20:42] <janc_> +1 from me too
[20:43] <popey> that's enough votes is it not?
[20:43]  * ausimage holds his breath 
[20:43] <boredandblog_> yup
[20:43] <popey> awesome
[20:44] <popey> well done!
[20:44] <ausimage> Yeah! finally :D
[20:44] <boredandblog_> ausimage: congrats!
[20:44] <nizarus> congrats ausimage
[20:45] <DiegoTc> congratulations asimage
[20:45]  * TwoToneSpirit is proud to be a New Yorker.  :-)
[20:45] <DiegoTc> ausimage
[20:45] <zaafouri> congratulations =)
[20:45]  * DiegoTc & U-hn saids congratulations to NY
[20:46] <hal14450> so NY gets approval then ? we're finally official?
[20:47]  * nizarus is counting seconds until tunisia call
[20:47] <zaafouri> =)
[20:47] <RachedTN> :)
[20:47]  * zaafouri too
[20:47] <janc_> hal14450, yes  :)
[20:48] <ALAYA> congrats hal14450 :)
[20:48] <hal14450> thaank you
[20:49] <AliBB> hal14450,  Tunisia congrats NY :)
[20:49] <zaafouri> =)
[20:49] <RachedTN> Congratulations NY :) Hope we (ubuntu-tn) are the next :)
[20:51] <hal14450> thanks all, and good luck to the other teams
[20:51] <boredandblog_> nizarus: we want to the do the re-approvals on a mailing list
[20:52] <boredandblog_> the procedure was that we would contact the LoCos...
[20:52] <nizarus> boredandblog_, whow is that ?
[20:52] <boredandblog_> we have a huge back log of re-approvals
[20:52] <nizarus> ah ok i see
[20:53] <nizarus> so we have to wait until we got an email ?
[20:53] <janc_> and every time we approve a new team, next year the backlist becomes longer  ;-)
[20:53] <boredandblog_> nizarus: yeah, don't worry about it did we contact you
[20:53] <boredandblog_> s/did/till
[20:53] <boredandblog_> is someone here from the Japan team?
[20:54] <jkbys> I'm here for Japan team
[20:54] <boredandblog_> jkbys: that applies to the japan team as well
[20:54] <boredandblog_> we'll email the contacts and inform them about reapproval
[20:54] <jkbys> I see
[20:55] <nizarus> boredandblog_, reapproval without a meeting ?
[20:55] <boredandblog_> apologies for any inconvenience this may have caused
[20:55] <RachedTN> Ooops, I have prepared a party to celebrate our reapproval, I think I have to drink alone now
[20:55] <zaafouri> RachedTN, me too ='(
[20:55] <RachedTN> :'(
[20:56] <janc_> jkbys, hope you didn't have to stay up until some ungodly hour...   :-/
[20:56] <zaafouri> We will get it =)
[20:56] <nizarus> we remove our line entry from wiki page or we keep it ?
[20:56] <boredandblog_> nizarus: you can remove it
[20:57]  * RachedTN whish the best for the others LoCos and keep the good works guys, VIVA ubuntu :)
[20:57] <DiegoTc> boredandblog_ just one doubt
[20:58] <janc_> DiegoTc, yes?
[20:58] <DiegoTc> you told me we should put dates on our application
[20:58] <DiegoTc> ¿?https://wiki.ubuntu.com/HondurasTeam/Honduras_ApprovalApplication
[20:59] <janc_> yes?
[20:59] <DiegoTc> or i didn't understand well
[20:59] <popey> The "Experience" section, yes
[21:00] <DiegoTc> ohh thinks to do for the next meeting on october
[21:00] <DiegoTc> ;)
[21:01] <janc_> DiegoTc, yes, and if you want, feel free to ask us questions before then
[21:02] <DiegoTc> well thanks for all
[21:02] <DiegoTc> there is not pizza this night
[21:02] <DiegoTc> hahah
[21:03] <janc_> (we're often around in #ubuntu-locoteams if people want to ask questions)
[21:04]  * janc_ hopes he can go back to the family BBQ now, already missed the cake for my nieces birthday  ;)