[08:02] <lifeless> do we have a asia pac meeting tonight
[08:04] <nigelb> there wasn't one last week, so I'd assume yes
[11:08] <rodrigo_> diwic: is the meeting now?
[11:09] <diwic> rodrigo_, yes, but we seem to be the only ones present
[11:09] <rodrigo_> :)
[11:11] <diwic> rodrigo_, I pinged awolfson and TheMuso, I'll give them a minute or two and see if they show up
[11:11] <diwic> awolfson's on the channel, can't see ronoc anywhere
[11:11] <diwic> ok, let's start
[11:11] <diwic> #startmeeting
[11:11] <MootBot> Meeting started at 05:11. The chair is diwic.
[11:11] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[11:12] <diwic> First; anybody want a topic to add, something we should discuss?
[11:12] <TheMuso> So I assume we don't have an agenda...
[11:13] <diwic> [LINK] https://wiki.ubuntu.com/Audio/MeetingAgenda
[11:13] <MootBot> LINK received:  https://wiki.ubuntu.com/Audio/MeetingAgenda
[11:13] <diwic> [TOPIC] Anything in particular we want to discuss
[11:13] <MootBot> New Topic:  Anything in particular we want to discuss
[11:14] <diwic> So; a few days ago I found bug #579300, about OSS emulation removal and a few angry users having their features removed.
[11:15] <diwic> I still think it's the right thing to do but I would like some arguments :-)
[11:16] <diwic> TheMuso, do you know more than I do?
[11:16] <TheMuso> no
[11:16] <diwic> ok; so basically, this was Daniel's decision and we trust him?
[11:17] <TheMuso> We both made the decision, as Fedora and other distros have disabled it as well. We meant to get ossproxy packaged for maverick, but that didn't happen.
[11:17] <rodrigo_> so, this is to make oss apps use pulseaudio?
[11:18] <TheMuso> Yes
[11:18] <rodrigo_> then yes, +1 :-)
[11:19] <diwic> TheMuso, so let's add an action item to package ossproxy for Natty, if we think that'll help
[11:19] <diwic> Any volunteers?
[11:19] <TheMuso> It will help.
[11:19] <TheMuso> If its trivial, I could probably get it packaged when I have a few spare cycles.
[11:19] <TheMuso> But if someone wants experience in packaging, them feel free to take it, and I am happy to review it.
[11:19] <rodrigo_> same here, if it's too complicated, I might need help
[11:20] <rodrigo_> TheMuso, ok, I'll take it, and ask you for help if I can't, ok?
[11:20] <TheMuso> Sounds good.
[11:20] <diwic> [AGREED] rodrigo_ to package ossproxy for Natty (with assistance from TheMuso if necessary)
[11:20] <MootBot> AGREED received:  rodrigo_ to package ossproxy for Natty (with assistance from TheMuso if necessary)
[11:21] <diwic> Or was that "Action"? Who knows :-)
[11:21] <TheMuso> I think action is what you want.
[11:21] <diwic> [ACTION] rodrigo_ to package ossproxy for Natty (with assistance from TheMuso if necessary)
[11:21] <MootBot> ACTION received:  rodrigo_ to package ossproxy for Natty (with assistance from TheMuso if necessary)
[11:22] <diwic> Ok, anything else?
[11:23] <diwic> Let's move on
[11:23] <diwic> [TOPIC] Any bugs we should look into in particular?
[11:23] <MootBot> New Topic:  Any bugs we should look into in particular?
[11:23] <diwic> What's pestering you the most currently?
[11:24] <rodrigo_> not much, audio working quite good, even on natty :)
[11:24] <diwic> fantastic :-)
[11:24] <diwic> I'm currently trying to make upstream ALSA understand the need for consistent volume control naming
[11:25] <rodrigo_> there's still the GTK3 bugs for indicator, bit the desktop team has plans to coordinate that with unity
[11:25] <rodrigo_> so, no pestering there
[11:26] <diwic> The "Front" volume control or switch sometimes control front line-out only, and sometimes headphones and/or internal speakers as well
[11:26] <rodrigo_> nice :)
[11:26] <diwic> Front as in the channel (i e not C/LFE/surround), not as in location
[11:27] <diwic> with the result that we can't code PulseAudio in a way that'll work everywhere
[11:27] <diwic> I discovered that we have a PA patch that adds "Master Front", and we let that mean something controlling HP and Speakers as well, and let "Front" control the line-out only
[11:28] <diwic> But upstream doesn't like the "Master Front" and want to change the other name instead
[11:30] <diwic> *sigh*
[11:30] <diwic> so now that I've finished moaning, let's move on
[11:30] <rodrigo_> :)
[11:30] <diwic>  [TOPIC] Anything in particular we've been working on the previous week
[11:30] <diwic> [TOPIC] Anything in particular we've been working on the previous week
[11:30] <MootBot> New Topic:  Anything in particular we've been working on the previous week
[11:31] <diwic> Well, I've actually started a little on the audio apport symptom
[11:32] <diwic> I wrote a "Jack" parser from the codec file, see http://pastebin.ubuntu.com/535499/
[11:32] <diwic> Do you think it looks good?
[11:32] <TheMuso> Cool.
[11:33] <rodrigo_> looks ok, but too complex for basic users, I think
[11:34] <rodrigo_> but looks ok for someone really knowing what is it
[11:34] <diwic> rodrigo_, hmm? It was based on the suggestion on the UDS session that normal users want to relate to the Jacks rather than the card name
[11:34] <rodrigo_> ah, ok
[11:34] <TheMuso> Since I am on rotatino, I just did a little reading of bug mail, and merged packages from Debian, mainly jack stuff.
[11:35] <diwic> rodrigo_, but I'm open for suggestions
[11:35] <diwic> TheMuso, so anything interesting coming in from Debian at this point?
[11:35] <rodrigo_> on my part, since we now have libcanberra-gtk3 in natty, started working on packaging stuff that use it, like gnome-media
[11:35] <rodrigo_> diwic, not sure what to suggest, so I'll shut up for now :-)
[11:36] <diwic> rodrigo_, ok, let me know if you have improvement ideas
[11:36] <rodrigo_> yes, I will
[11:36] <TheMuso> not that I know of.
[11:36] <TheMuso> nothing jack wise anyway.
[11:36] <rodrigo_> although I guess we could accompany that in the UI with a nice picture of the jacks
[11:36] <rodrigo_> that should make it user-friendly
[11:37] <rodrigo_> can we do that in the apport stuff?
[11:37] <TheMuso> Oh rtkit is now synced with Debian, so rtkit is not maintained in pkg-multimedia repos in debian.
[11:37] <rodrigo_> that is, add an image to the dialog?
[11:37] <TheMuso> s/not/now/
[11:37] <diwic> TheMuso, do you have upload rights for those things in Debian?
[11:37] <TheMuso> No.
[11:38] <TheMuso> But I have git commit access, so if we need something urgently, I can always temporarily create an Ubuntu branch, make an Ubuntu package, and merge the changes into debian's branch, and an upload to debian will straighten things out.
[11:39] <diwic> rodrigo_, it's going to be hard for the cli version ;-)
[11:39] <rodrigo_> diwic, well, average users would probably always use the GUI version, right?
[11:39] <persia> There's a fair few folk active in Ubuntu with upload access for pkg-multimedia stuff, so it's not typically hard to get an upload there.
[11:40] <diwic> rodrigo_, but for gtk, it should be possible, I think that'll require a little more knowledge in apport than I currently have
[11:40] <rodrigo_> diwic, ok, I'll have a look
[11:40] <diwic> rodrigo_, are you familiar with apport/python?
[11:41] <rodrigo_> not much with apport, but a little bit, so will look at it
[11:42] <diwic> ok
[11:43] <diwic> rodrigo_, lets chat a little about that after the meeting if you like
[11:43] <rodrigo_> ok
[11:44] <diwic> Other than that, I've been quite busy with HWE work these weeks, so there hasn't been that much time to do other things
[11:44] <rodrigo_> HWE?
[11:45] <diwic> HWE = HardWare Enablement, i e what I'm hired for :-)
[11:45] <rodrigo_> ah, ok :)
[11:45] <diwic> Anything else?
[11:46] <diwic> let's move on
[11:46] <diwic> [TOPIC] Anything in particular we plan to do the coming week?
[11:46] <MootBot> New Topic:  Anything in particular we plan to do the coming week?
[11:46] <rodrigo_> for me, packaging ossproxy and look at the apport stuff, apart from packaging more stuff that uses the libcanberra-gtk3 thing
[11:47] <diwic> I'll hope I have some time to continue on the apport symptom, perhaps also start on some of the pro-audio-secured stuff.
[11:47] <TheMuso> Me, nothing on the audio front, unless I am prodded by someone to review/upload audio related packages. :)
[11:48] <diwic> As for these meetings, I think every 14 days will suffice, rather than once a week, or what do you think?
[11:49] <TheMuso> Seconded.
[11:49] <diwic> Btw, do any of you have gmail accounts?
[11:50] <TheMuso> No, but I do have a canonical calendar hosted on Google.
[11:50] <TheMuso> i.e a canonical.com google calendar.
[11:51] <diwic> TheMuso, the same goes for me, and it might cause problems with the fridge calendar
[11:51] <diwic> But I'll struggle with it to next meeting :-)
[11:51] <TheMuso> heh
[11:52] <rodrigo_> diwic, yes, rodrmoya@gmail.com
[11:53] <diwic> rodrigo_, would you mind following https://wiki.ubuntu.com/Fridge/Calendar instructions and try to set up a meeting dec 7?
[11:54] <diwic> rodrigo_, and see if it works better for you?
[11:54] <rodrigo_> ok
[11:55] <diwic> [AGREED] Meeting interval is every 14 days, next meeting is Dec 7.
[11:55] <MootBot> AGREED received:  Meeting interval is every 14 days, next meeting is Dec 7.
[11:55] <awolfson> hello
[11:55] <TheMuso> Is there anything else that I need to be present for? Its getting late here...
[11:56] <diwic> TheMuso, I was about to end the meeting unless awolfson or someone else has anything to add?
[11:56] <rodrigo_> so, Dec 7 at 12PM CET, right?
[11:56] <diwic> rodrigo_, right
[11:56] <TheMuso> diwic: sounds good.
[11:57] <diwic> ok, let's end the meeting then
[11:57] <diwic> #endmeeting
[11:57] <MootBot> Meeting finished at 05:57.
[11:57] <diwic> thanks for attending
[11:57] <TheMuso> thanks folks.
[11:58] <diwic> awolfson, a little late perhaps :-)
[12:00] <awolfson> when meeting starts? i thought 7:00 EST?
[12:00] <rodrigo_> diwic, ok, seems it worked
[12:01] <awolfson> ooo, looks like 6:00 EST, because of day saving
[12:02] <rodrigo_> ugh, I removed it
[12:02] <diwic> awolfson, hmm, hope I didn't calculate things wrong for you
[12:02] <diwic> awolfson, sorry :-(
[12:03] <awolfson> diwic, so it is 6:00 my time ?
[12:04] <diwic> awolfson, I'm afraid so, thought you were at UTC-4
[12:04] <awolfson> it is 7:04 here now
[12:04] <awolfson> I guess it is daylight saving change
[12:06] <diwic> awolfson, maybe
[12:59] <NCommander> #startmeeting
[12:59] <MootBot> Meeting started at 06:59. The chair is NCommander.
[12:59] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[12:59]  * NCommander notes the laptop clock is a bit fast
[12:59] <NCommander> who's here?
[13:01] <NCommander> davidm_: GrueMaster_: ogra: ping?
[13:01] <NCommander> persia: ?
[13:02] <ogra> moo
[13:02] <GrueMaster_> me
[13:02] <NCommander> oh good, signs of life
[13:02] <ogra> david is on vacation
[13:02] <ogra> as well as ricardo
[13:02] <GrueMaster> no life here
[13:03] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20101123
[13:03] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20101123
[13:03]  * NCommander feels hidious so wishes to make this a short meeting
[13:03]  * ogra fixes the bugtasks link
[13:03] <NCommander> [topic] Action Item Review
[13:03] <MootBot> New Topic:  Action Item Review
[13:04] <NCommander> skipping non-president people's items
[13:04] <ogra> ricardos item is done
[13:04] <NCommander> [topic] ogra_ac and rsalveti to talk to davidm on proper approach to fix Qt
[13:04] <MootBot> New Topic:  ogra_ac and rsalveti to talk to davidm on proper approach to fix Qt
[13:04] <ogra> we did that during the meeting iirc
[13:04] <NCommander> oh
[13:04] <NCommander> [topic] GrueMaster to fix assigned bugs list
[13:04] <MootBot> New Topic:  GrueMaster to fix assigned bugs list
[13:04] <ogra> after you made it an action
[13:05] <GrueMaster> ogra fixed it before I could.
[13:05] <ogra> sorry :)
[13:05] <NCommander> [topic] ogra_ac to follow omap3 kernel situation
[13:05] <MootBot> New Topic:  ogra_ac to follow omap3 kernel situation
[13:05] <ogra> still in progress
[13:05] <ogra> and i looked at ebay
[13:05] <ogra> under which name is that soul offered ?
[13:06]  * ogra couldnt find anything
[13:06] <NCommander> ogra: discovered that eBaying one's soul is against the Terms of Service
[13:06] <ogra> pfft
[13:06] <ogra> just name it differently :)
[13:06] <NCommander> /dev/life?
[13:07] <ogra> so how is that mono stuff going forward ?
[13:07] <NCommander> Made some progress, discovered we're not building mono with VFP, and have some test cases
[13:07] <ogra> cool !
[13:08] <NCommander> Got sidetracked by being patch pilot and high priority stuff from davidm plus the fact that my lungs are full of uninvited guests
[13:08] <ogra> well, patch politing is fun :)
[13:08] <NCommander> Also discovered that cars beside my own are prone to having their doors freeze shut and I'm going to probably be spending part of tomorrow trying to fix that.
[13:09] <ogra> put graphite on the gasket
[13:09]  * NCommander notes its a *very* cold day in Portland
[13:09] <NCommander> ogra: not my car. Wish it was, I won't be afraid I was going to pull off a handle or something
[13:09] <NCommander> Anyway
[13:09] <NCommander> [topic] Standing Items
[13:09] <MootBot> New Topic:  Standing Items
[13:09] <ogra> heh, rather the gasket
[13:09] <NCommander> [link] http://people.canonical.com/~pitti/workitems/natty/canonical-arm.html
[13:09] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/natty/canonical-arm.html
[13:10] <NCommander> [link] http://people.canonical.com/~pitti/workitems/natty/canonical-arm-natty-alpha-1.html
[13:10] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/natty/canonical-arm-natty-alpha-1.html
[13:10] <ogra> we're getting terribly close to the trend line
[13:10] <NCommander> hrm
[13:10] <ogra> dont forget A1 in dec. 2nd
[13:10] <NCommander> my specs are STILL not there
[13:10] <NCommander> *grumble*
[13:10] <NCommander> oh wait
[13:10] <ogra> they are
[13:10] <NCommander> yes they are, I already did my workitems for this cycle
[13:10] <NCommander> er
[13:10] <NCommander> milestone
[13:11] <NCommander> */half dead*
[13:11] <NCommander> I thikn I forgot to strike it off my TODO list ...
[13:11] <NCommander> [link] http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html
[13:11] <MootBot> LINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html
[13:11] <ogra> wrong link
[13:11] <ogra> !!
[13:11]  * NCommander refreshs
[13:11]  * ogra fixed it on the wiki
[13:12] <NCommander> [link] http://qa.ubuntu.com/reports/team-assigned/canonical-arm-assigned-bug-tasks.html
[13:12] <MootBot> LINK received:  http://qa.ubuntu.com/reports/team-assigned/canonical-arm-assigned-bug-tasks.html
[13:12] <GrueMaster> should be [link] http://reports.qa.ubuntu.com/reports/team-assigned/canonical-arm-assigned-bug-tasks.html
[13:12] <NCommander> er no
[13:12] <ogra> shows that persia is a slacker :)
[13:12] <NCommander> I didn it wrong twice >.<
[13:12]  * NCommander notes it would be nice if he attended our meetings ...
[13:12] <ogra> yes, it would
[13:12] <NCommander> Finally confirmed bug #626749
[13:12]  * NCommander coughs
[13:12] <ogra> but the time is bad for him
[13:12] <NCommander> There's no actual bug here
[13:12] <persia> Um, you folk have a funny definition of "attendance"
[13:13] <NCommander> Cause the code is doing exactly what its supposed to
[13:13] <ogra> heh
[13:13] <ogra> NCommander, its not
[13:13] <ogra> obviously it doesnt use a method the HW can deal with
[13:13] <NCommander> ogra: I wrote the code to intentionally try to write to NAND if it was on a Beagle Board
[13:13] <NCommander> Beagle XM says its a Beagleboard
[13:13] <ogra> yes
[13:13] <NCommander> I therefore say its a hardware bug, and we need ot fix it software :-)
[13:13] <NCommander> Thus I'm not at fault
[13:13] <ogra> you are
[13:13] <NCommander> :-P
[13:13] <GrueMaster> beagleXM is omap3
[13:14] <ogra> since you added that code
[13:14] <ogra> make it work or remove it
[13:14] <NCommander> ogra: the cirmstances which the code is being run changed :-P
[13:14] <persia> It7s generally better to do things like try to detect if there *is* MTD, rather than depending on detection.  Such work is likely to be much more applicable in the future.
[13:14] <NCommander> but I plan on fixing it anyway
[13:14] <NCommander> since I have an XM now
[13:15] <ogra> right
[13:15] <ogra> more checks please :)
[13:15] <NCommander> preferable with five figures on them :-)
[13:15] <NCommander> *preferably
[13:15] <ogra> that should be possible independently from the board type
[13:15] <NCommander> ogra: yeah, I plan to add something look for the mtd device and maybe even check for u-boot or something in flash
[13:16] <ogra> also for a vfat containing uImage etc etc
[13:16] <ogra> you need to cover all possible cases to make it proper and generic
[13:16] <NCommander> ogra: right that code is there and is known to work
[13:16] <persia> Well, kinda.  It works sometimes, for some hardware.
[13:16] <ogra> .oO(tell that to Neko)
[13:16] <NCommander> What isn't working is that the code assumes that a board saying its a Beagle has NAND
[13:17] <NCommander> That assumption proved to be incorrect
[13:17] <ogra> the bug as about a blaze iirc
[13:17] <persia> MTD detection, partitioning management, etc. is kinda funny, in several annoying ways.
[13:17] <ogra> which has only eMMC
[13:17] <NCommander> d-i has a lot of ugly code dealing with it :-/
[13:17] <ogra> for which we have no solution yet afaik
[13:17] <ogra> but your code needs to take that into account too
[13:17] <NCommander> indeed
[13:17] <NCommander> [topic] Kernel Status (cooloney)
[13:17] <MootBot> New Topic:  Kernel Status (cooloney)
[13:18] <ogra> not around
[13:18] <GrueMaster> Until I get an upgraded blaze, we have no way of testing it.
[13:18] <ogra> i have an upgrade card
[13:18] <ogra> just not in the balze atm
[13:18] <ogra> *blaze
[13:19] <NCommander> [topic] QA Status (GrueMaster)
[13:19] <MootBot> New Topic:  QA Status (GrueMaster)
[13:19] <GrueMaster> Currently working on test for QT neon.
[13:20] <ogra> i thought you can only do that next week ?
[13:20] <GrueMaster> Friday's omap4 image fails to boot after 2nd reboot.  Not sure if it is X related.  Kernel segfaults.
[13:20] <ogra> did you dig deeper into why the omap4 images dont work ?
[13:20] <ogra> ah
[13:20] <GrueMaster> Not yet.
[13:21] <ogra> might be a toolcahin issue
[13:21] <ogra> *toolchain
[13:21] <GrueMaster> I have a pastebin of the console log.
[13:21] <ogra> https://blueprints.launchpad.net/ubuntu/+spec/none-kernel-n-misc has a workitem for us
[13:21] <ogra> could you take an onap4 image and replace the kernel with the linaro omap3 one ?
[13:22] <ogra> and see how that works
[13:22] <ogra> *omap
[13:22] <ogra> cool, file a bug
[13:22] <GrueMaster> Will it work on omap4?  I only have a panda.
[13:23] <GrueMaster> I'll file a bug when I can narrow down the segfault.
[13:23] <ogra> oh, you dont have your XM with you
[13:23] <ogra> file the bug asap probably someone can tell something about it
[13:24] <GrueMaster> I only have my panda.  Thisis a holiday week and I had only planned on working on my blueprints this week.
[13:24] <GrueMaster> Will do.
[13:24] <ogra> might be because the kernel wasnt recompiled with the new toolchain or so
[13:24] <GrueMaster> It boots up to mounting rootfs.
[13:25] <GrueMaster> jasper boot sequence runs fine.
[13:25] <ogra> oh
[13:25] <ogra> thats different indeed
[13:25] <GrueMaster> exactly.
[13:25] <ogra> must be userspace then
[13:25] <GrueMaster> see http://paste.ubuntu.com/535244/
[13:26] <GrueMaster> I have limited resources, but will try to narrow it down.
[13:26] <NCommander> can I mov eon?
[13:26] <GrueMaster> go
[13:27] <ogra> chvt: can't open console
[13:27] <ogra> thats your main issue
[13:28] <NCommander> [topic] ARM Porting/FTBFS status (NCommander)
[13:28] <MootBot> New Topic:  ARM Porting/FTBFS status (NCommander)
[13:28] <NCommander> mostly mono work
[13:28] <ogra> any idea how KDE is progressing ?
[13:28] <ogra> did you talk to ScottK
[13:28]  * ogra is still waiting for the QT mail from asa
[13:28] <ogra> c
[13:29] <NCommander> ogra: didn't have a chance yet
[13:29] <NCommander> will do so
[13:29] <ogra> given that he wanted to discuss with thiago at meego conf
[13:29] <NCommander> [action] NCommander to speak with ScottK on KDE progress
[13:29] <MootBot> ACTION received:  NCommander to speak with ScottK on KDE progress
[13:29] <ogra> i see him going wild on the different ARM channels
[13:29] <ogra> which is awseome :)
[13:29] <NCommander> [topic] ARM Image Status (ogra, NCommander)
[13:29] <MootBot> New Topic:  ARM Image Status (ogra, NCommander)
[13:30] <GrueMaster> Not working.
[13:30] <ogra> U1 acts up today
[13:30] <ogra> u-n-d-s was fixed
[13:31] <ogra> i hope if U1 is in sync we will have images again
[13:31] <ogra> nothing more about image status
[13:33] <NCommander> [topic] abo
[13:33] <MootBot> New Topic:  abo
[13:33] <NCommander> er
[13:33] <NCommander> [topic] AOB
[13:33] <MootBot> New Topic:  AOB
[13:33] <ogra> BOA ?
[13:34] <ogra> nothing here ... i guess meeting time has to wait until we are complete again
[13:35] <ogra> persia, anything from you ?
[13:35] <ogra> i.e. about ubuntu-armel and work items ?
[13:36] <ogra> i.e. reveal your plans to a wider audience
[13:37] <persia> Hrm?  Oh, yeah, I want there to be an Ubuntu ARM team, rather than just Canonical ARM.
[13:37] <persia> I'm not sure how much there is to say about that: it's in part up to you to want to do that :)
[13:37] <ogra> which is there, but mainly used for bug triage atm
[13:38] <ogra> well, its trivial to add another WI tracker, i just thought you wanted to elaborate a bit on it
[13:38] <ogra> i.e. do you want its status covered in this meeting etc
[13:39] <persia> Dunno how much to elaborate.  I know of several things happening with ARM by people who don't much attend this meeting, so my other encouragemetns to you are mostly about being inclusive.
[13:39] <ogra> and make sure NCommander invites the people from that team to attend it
[13:40] <ogra> just having a tracker if nobody watches it doesnt seem to make much sense to me
[13:40] <persia> Well, if there is a meeting that tracks some ARM stuff, I'd rather track all ARM stuff, and encourage more participants.  I think it's up to individual folk whether they want to participate, to some degree, but I think it would be worthwhile to have an overview of everything happening in ARM.
[13:40] <ogra> so it would need additional actions around that
[13:40] <persia> Additional actions?
[13:40] <ogra> i.e. invites from NCommander and a note in the meeting announcement etc
[13:41] <ogra> NCommander, oh, btw, the meeting announcement ... we're the ARM team ;(
[13:41] <ogra> ;)
[13:41] <ogra> and we should mobve to a new namespace on the wiki
[13:41]  * GrueMaster never saw one this week.
[13:41] <persia> The meeting announcement needs help anyway.  Fixing it one way or the other is probably the same work.
[13:41] <ogra> NCommander, can you handle that ?
[13:42] <ogra> GrueMaster, it goes to ubuntu-devel now, since thats our new mailing list
[13:42] <GrueMaster> argh
[13:42] <ogra> GrueMaster, make sure to be subscribed to it and probably u-d-discuss
[13:42] <ogra> we talked about it before
[13:42] <ogra> u-mobile is essentially dead
[13:43] <ogra> (not sure david removed it completely yet, but that will happen soon)
[13:44] <NCommander> anything else, or can I close it out?
[13:44]  * NCommander is feeling pretty close to death ATM
[13:44]  * ogra waits for answers from NCommander 
[13:44] <ogra> (and probably some actions)
[13:45] <ogra> but after that you can happily close :P
[13:45] <persia> ogra, So, you poked me to talk about a wider team definition.  Do you have an opinion on that?
[13:45] <NCommander> ogra: which answers?
[13:45] <ogra> well, as long as the team is included and invited
 NCommander, oh, btw, the meeting announcement ... we're the ARM team
 and we should mobve to a new namespace on the wiki
 NCommander, can you handle that ?
[13:46] <persia> ogra, The point of inclusiveness is that *everyone* is invited :)  I very much don't want to exclude you (or anyone else).
[13:46] <ogra> persia, no, but the team members need to know about it
[13:46] <persia> I'm even happy to create a teamspace on the wiki for an ARM team, if there is to be an open ARM team.
[13:47] <ogra> so if the announcement needs rephrasing in that direction and the agenda needs points for that, they need to be added
[13:47] <ogra> i.e. have a ARM Community topic
[13:47] <persia> NCommander, Give me actions for those, and when you're feeling better, I'll feed you text :)
[13:47] <ScottK> NCommander and ogra: Qt/KDE is blocked on a gcc fix. The gcc patch was posted upstream for review yesterday, so hopefully we'll see something soon.
[13:47] <ogra> and point out that everyone is invited in the meeting announcement
[13:48] <NCommander> [action] persia to handle namespace renaming
[13:48] <MootBot> ACTION received:  persia to handle namespace renaming
[13:48] <persia> ogra, You can do something about the WI tracker and bug list?
[13:48] <ogra> why the bug list ?
[13:48] <ogra> i can add another team to the tracker, yes
[13:48] <persia> Same rationale as the WI tracker, really.
[13:48] <ogra> you need to give me a mail address for the responsible person for broken tracker entries
[13:49]  * ogra doesnt understand
[13:49] <ogra> we never subscribe ubuntu-armel to any bugs
[13:49] <ogra> but we use it to subscribe the whole team to it
[13:49] <persia> Sure, but members are assigned bugs.
[13:50] <ogra> persia, ping bdmurray about that, he can help
[13:50] <persia> Sure.  I'll do that.
[13:50] <ogra> NCommander, [action] persia and NCommander to work out new meeting announcement text
[13:51] <ogra> NCommander,  [action] persia to make the bugsquad create a bug overview page for ubuntu-armel
[13:51] <ogra> (though the latter will highly overlap with our team list i think)
[13:52] <ogra> NCommander, add these two actions and close the meeting (then back to bed with you !)
[13:53] <persia> ogra, I expect lots of overlap between Ubuntu ARM and Canonical ARM, which I consider a good thing :)
[13:53] <ogra> persia, you are aware that no other team does such a distinction ?
[13:53] <NCommander> [action] persia to make the bugsquad create a  bug overview page for ubuntu-armel
[13:53] <MootBot> ACTION received:  persia to make the bugsquad create a  bug overview page for ubuntu-armel
[13:53] <NCommander> [action] persia and NCommander to work out new  meeting announcement text
[13:53] <MootBot> ACTION received:  persia and NCommander to work out new  meeting announcement text
[13:53] <NCommander> #endmeeting
[13:53] <MootBot> Meeting finished at 07:53.
[13:53] <ogra> NCommander, thanks
[16:00] <zul> hello
[16:00] <JamesPage> o/
[16:00] <zul> ttx stop stalking :)
[16:00] <ttx> o/
[16:00] <hallyn> \o
[16:03] <JamesPage> who's in the seat this week?
[16:04] <hallyn> is Daviey around?
[16:04] <hallyn> he missed his turn last week, poor sod
[16:05] <hallyn> otherwise i'ts you, JamesPage :)
[16:06] <hallyn> though, do we think we have a quorum?
[16:06] <Daviey> eek, sorry
[16:07] <JamesPage> saved by the bell (or Daviey in this case...)
[16:07] <Daviey> Who do we have?
[16:08] <JamesPage> o/
[16:08] <Daviey> nobody else!?
[16:08] <hallyn> o/
[16:08] <ttx> o/
[16:08] <smb> \o
[16:09]  * Daviey glares at SpamapS 
[16:09]  * SpamapS beams at Daviey
[16:09] <Daviey> smoser / kirkland / hggdh ?
[16:09] <smoser> o/
[16:09] <SpamapS> I had a screaming baby to deal with.. dunno what their excuses are. ;)
[16:10] <Daviey> #startmeeting
[16:10] <MootBot> Meeting started at 10:10. The chair is Daviey.
[16:10] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:10] <Daviey> [TOPIC] Review ACTION points from previous meeting
[16:10] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:10] <Daviey> ALL: please check the SRU tracker https://wiki.ubuntu.com/ServerTeam/SRUTracker and help out with verification
[16:10] <smoser> (excuse: i am actually on vacation )
[16:10] <Daviey> Did anybody have a chance to look?
[16:10] <SpamapS> smoser: well then go away. ;)
[16:11] <Daviey> smoser: Vaca? er what?  What is this?
[16:11] <SpamapS> Daviey: I did and helped out where I could. I think we should carry that one over to next meeting.
[16:11] <Daviey> Agreed
[16:11] <Daviey> [ACTION] please check the SRU tracker https://wiki.ubuntu.com/ServerTeam/SRUTracker and help out with verification (carried over)
[16:11] <MootBot> ACTION received:  please check the SRU tracker https://wiki.ubuntu.com/ServerTeam/SRUTracker and help out with verification (carried over)
[16:11] <SpamapS> at least until I complete my action to send a proposal out to ubuntu-devel ;)
[16:11] <Daviey> robbiew to review /ServerTeam wiki
[16:11] <Daviey> not here... so carry over
[16:11] <Daviey> [ACTION} robbiew to review /ServerTeam wiki
[16:11] <MootBot> ACTION received: [ACTION} robbiew to review /ServerTeam wiki
[16:12] <Daviey> SpamapS to email a concrete proposal for addressing SRU verification backlog
[16:12] <SpamapS> not done, carry to next week
[16:12] <Daviey> [ACTION] SpamapS to email a concrete proposal for addressing SRU verification backlog (carried over)
[16:12] <MootBot> ACTION received:  SpamapS to email a concrete proposal for addressing SRU verification backlog (carried over)
[16:12] <Daviey> [TOPIC] Natty Development
[16:12] <MootBot> New Topic:  Natty Development
[16:13] <SpamapS> Has anyone else run into FTBFS's due to the linker/compiler changes?
[16:13] <Daviey> Firstly, I think we are still polishing blueprints and creating work items
[16:13] <Daviey> Is anyone blocked on any of these parts?
[16:13] <Daviey> Super!
[16:14]  * SpamapS predicts the shortest meeting evar ;)
[16:14] <Daviey> SpamapS: I came across a similar bug to you, regarding DSO :)
[16:14] <Daviey> libssl DSO'ing libcrypto
[16:14] <Daviey> Anyone have anything else for Natty devel ?
[16:15] <Daviey> ok, moving on
[16:15] <SpamapS> Daviey: yeah thats pretty common I think because almost nobody uses libssl w/o touching libcrypto in some way
[16:15] <Daviey> Yup.. so we possibly have more FTBFS's at the moment
[16:16] <Daviey> .... normally just requires adding -lcrypto to the linker line
[16:16] <Daviey> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[16:16] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[16:16] <Daviey> hggdh: are you here?
[16:17] <Daviey> moving on..
[16:17] <Daviey> [TOPIC] Weekly Updates & Questions for the Kernel Team (smb)
[16:17] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (smb)
[16:17] <smb> There is not so much updates this week
[16:17] <Daviey> smb: sadly smoser isn't here to ask about EC2 kernel...
[16:17] <Daviey> ... but it looks fixed, right?
[16:17] <smb> Mostly trying to find out why natty does not boot that well on i386
[16:18] <smoser> yeah, that will result in a boring conversation. without me, there wont be any kernel bugs.
[16:18] <smb> But as, when it fails, there are no messages at all, most of the time, I am currently trying to get a local env together based on centos
[16:18] <Daviey> smoser: life is a boring conversation without you
[16:18] <Daviey> smoser: get back to drinking sangria on the beach.
[16:18] <smb> Apart from that, if there are questions... :)
[16:18] <smb> ..
[16:19] <SpamapS> smoser: not true! I brought an NFS bug
[16:19] <SpamapS> bug 661294
[16:19] <Daviey> smb: Okay... so you are working on this at the moment with smoser?
[16:19] <smb> Currently without smoser because he is on vacation
[16:19] <smb> But otherwise yep
[16:20] <SpamapS> smb: there seems to be a patch linked to in the comments that directly addresses this issue.. wondering how likely it is that it will be applied in natty
[16:20] <Daviey> [ACTION] Follow up on EC2 status
[16:20] <MootBot> ACTION received:  Follow up on EC2 status
[16:20] <Daviey> smb: SpamapS's question ?
[16:20] <smb> SpamapS, As this is the first time I seem to see that bug mentioned, it is hard to tell a lot
[16:21] <Daviey> smb: Understood... putting you on the spot a lttle... not essential for a response now
[16:21] <SpamapS> smb: thats fine, I just wanted to get it on your radar.
[16:21] <smb> SpamapS, Success
[16:21] <Daviey> but can you get someone from your team to update the bug before next week please? :)
[16:22] <smb> I put it on the list
[16:22] <Daviey> [ACTION] Kernel team to follow up on bug #https://launchpad.net/bugs/661294
[16:22] <MootBot> ACTION received:  Kernel team to follow up on bug #https://launchpad.net/bugs/661294
[16:22] <Daviey> moving on?
[16:22]  * SpamapS does a fist bump w/ smb and then gets nostalgic for mathiaz.. <sniff>
[16:23] <Daviey> (thanks smb)
[16:23] <Daviey> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[16:23] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[16:23] <Daviey> he isn't here :(
[16:23] <Daviey> [TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[16:23] <MootBot> New Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[16:23] <Daviey> he isn't here :(
[16:24] <Daviey> [TOPIC] Open Discussion
[16:24] <MootBot> New Topic:  Open Discussion
[16:24] <Daviey> nothing here..
[16:24] <Daviey> anyone?
[16:24] <SpamapS> I was thinking one thing..
[16:24] <SpamapS> which is just that the WI tracker seems very incomplete..
[16:24] <Daviey> SpamapS: is it family friendly?
[16:25] <Daviey> SpamapS: it would be, the WI's aren't complete yet
[16:25] <zul> SpamapS: because some of us are blocked on somethings
[16:25] <Daviey> addionally, does the WI pull in non-approved specs?
[16:25] <SpamapS> right, I just was going to ask when its supposed to be?
[16:25] <SpamapS> Daviey: no it does not
[16:25] <SpamapS> So thats probably why it seems so low
[16:25] <Daviey> I imagine this week, robbiew will be doing a final pass
[16:25] <Daviey> jumping on people to get them complete
[16:26] <SpamapS> Also I wonder if here is the place to discuss the ubuntu-server package set?
[16:26] <SpamapS> I think we should actually discuss it next week...
[16:26] <Daviey> SpamapS: I'm not sure we have a wide enough audience tbg
[16:26] <SpamapS> light crew today
[16:26] <Daviey> tbh*
[16:26] <zul> probably...but what has been done and put it on the agenda for next week :)
[16:26] <Daviey> moving on?
[16:27] <Daviey> [TOPIC] Announce next meeting date and time
[16:27] <MootBot> New Topic:  Announce next meeting date and time
[16:27] <zul> yeah i just have one question
[16:27] <zul> why is there a seperate "cloud community meeting"
[16:27] <SpamapS> Oh yeah good point zul
[16:27] <Daviey> Gooooooood question!
[16:27] <SpamapS> especially since we have a community member who never shows up to these meetings.
[16:28] <ttx> who ?
[16:28] <SpamapS> s/community/community team/
[16:28] <Daviey> zul: Do you want to take the action of speaking with kim0 to find out what it is about?
[16:28] <zul> i was going to bug jono about it
[16:28] <Daviey> ... and find out if it might be better to unify the meeting
[16:28] <ScottK> Actually I think it'd be kind of nice to split all the cloud stuff into it's own meeting.
[16:28] <Daviey> zul: I would speak with kim0 first.
[16:29] <zul> Daviey: ack
[16:29] <SpamapS> ScottK: I think thats worthy of a discussion here definitely.
[16:29] <Daviey> ScottK: Well yes... but our community isn't wide enough to split yet :)
[16:29] <Daviey> Next meeting, Tuesday 2010-11-23 at 1600 UTC - #ubuntu-meeting
[16:30] <Daviey> Be there, or be square!
[16:30] <ScottK> Daviey: I think the emphasis on cloud stuff depresses community involvement from those who haven't signed up for the right drugs.
[16:30] <Daviey> ScottK: ack.. the whole team know this.... but until the team becomes large enough, and a critical mass.... we can then talk about seperating
[16:31] <Daviey> ScottK: Considering many of the Ubuntu Server team are working on cloud stuff... this meeting would be even more lonely :)
[16:31] <SpamapS> Its worth having the discussion here at some point soon
[16:31] <Daviey> #endmeeting
[16:31] <MootBot> Meeting finished at 10:31.
[16:31] <ScottK> Daviey: On the other hand, I think the server community will keep getting smaller until you make the split.
[16:31] <SpamapS> Daviey: thanks!
[16:31] <Daviey> ScottK: Do you want to add it to next weeks agenda?
[16:32] <SpamapS> ScottK: that seems a bit extreme. The server product is essential to the cloud, the overlap is *huge*
[16:32] <ScottK> Daviey: I'm not usually available at this time, so I'm not the best one for it.
[16:32] <Daviey> ScottK: Well that is a challenge :(
[16:32] <ScottK> SpamapS: That's an interesting theory that doesn't seem to be matched by Canonical's messaging on the subject.
[16:32] <Daviey> ScottK: you are the most vocal about this concern, so I think you are a required participant of that discussion
[16:33] <Daviey> ScottK: Can you add it to the agenda for a meeting you can attend?
[16:33] <ScottK> Daviey: I'm only rarely available on Tuesdays (only here now because a meeting got cancelled today).
[16:33] <ScottK> I have no way of knowing when that would be.
[16:33] <Daviey> :(
[16:34] <Daviey> ScottK: Is there someone you can load as a proxy?
[16:35] <ScottK> Not really.
[17:00] <bjf> #
[17:00] <bjf> # lets "get 'er done"!
[17:00] <bjf> #
[17:00] <JFo> woo!
[17:00] <bjf> #startmeeting
[17:00] <MootBot> Meeting started at 11:00. The chair is bjf.
[17:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[17:01] <apw> o/
[17:01] <cking> o/
[17:01] <jjohansen> o/
[17:01] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:01] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[17:01] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[17:01] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[17:01] <bjf> #
[17:01] <bjf> # NOTE: '..' indicates that you are finished with your input.
[17:01] <bjf> #
[17:01] <bjf> [TOPIC] ARM Status (bjf)
[17:01] <bjf>  * Marvel (mvl-dove)
[17:01] <bjf>    * Marvell's latest LSP, 5.3.6 has been integrated into our tree and uploaded.
[17:01] <bjf>  * Freescale (fsl-imx51)
[17:01] <bjf>    * Nothing new this week
[17:01] <MootBot> New Topic:  ARM Status (bjf)
[17:01] <bjf>  * Texas Instruments (ti-omap)
[17:01] <bjf>    * Bug #666267 - Added DKMS package to this bug and asked for help from Mario. TI is
[17:01] <bjf>      still based on the 2.6.35 kernel. It is unlikely that we will be cherry-picking
[17:01] <bjf>      patches due to their proliferation all over the tree. They (TI) may move to 2.6.38
[17:01] <bjf>      next year.
[17:01] <bjf> ..
[17:02] <bjf> [TOPIC] Release Metrics (JFo)
[17:02] <MootBot> New Topic:  Release Metrics (JFo)
[17:02] <JFo> Release Meeting Bugs (6 bugs, 13 Blueprints)
[17:02] <JFo> [17:02] <JFo>  * 0 linux kernel bugs (no change)
[17:02] <JFo>  * 0 linux-ti-omap bugs (no change)
[17:02] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[17:02] <JFo> [17:02] <JFo>  * 3 linux kernel bugs (no change)
[17:02] <JFo>  * 0 linux-ti-omap bugs (no change)
[17:02] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[17:02] <JFo> [17:02] <JFo>  * 1 blueprints (Including HWE Blueprints)
[17:02] <JFo> [17:02] <JFo>  * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]
[17:02] <JFo>  * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]
[17:02] <JFo> ..
[17:03] <bjf> [TOPIC] Blueprints: Natty Bug Handling (JFo)
[17:03] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling
[17:03] <MootBot> New Topic:  Blueprints: Natty Bug Handling (JFo)
[17:03] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling
[17:03] <JFo> nothing to report this week
[17:03] <bjf> [TOPIC] Blueprints: Kernel Configuration Review (apw)
[17:03] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-config-review
[17:03] <MootBot> New Topic:  Blueprints: Kernel Configuration Review (apw)
[17:03] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-config-review
[17:03] <apw> All configuration changes from the UDS review session are now applied and uploaded.  Also the AGP drivers of interest have been identified and moved built-in.  Only two items remain, neither critical for natty-alpha-1.  These items are still on track for natty-alpha-1 completion.
[17:03] <apw> ..
[17:03] <bjf> [TOPIC] Blueprints: Enhancements to the firmware test suite (cking)
[17:03] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements
[17:03] <MootBot> New Topic:  Blueprints: Enhancements to the firmware test suite (cking)
[17:03] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements
[17:03] <cking> Changes to fwts (natty development branch):
[17:03] <cking>  * Add in methods tests - 69 new tests to exercise AML Methods
[17:03] <cking>  * Added error checking with CMOS reads
[17:03] <cking>  * Improved FACS 32/64 pointer mismatch checks in FADT
[17:03] <cking>  * Check for \_SB_._OSC buffer overflows
[17:04] <cking> ..
[17:04] <bjf> [TOPIC] Blueprints: Handling of Deviations from Standard Kernels (smb)
[17:04] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance
[17:04] <MootBot> New Topic:  Blueprints: Handling of Deviations from Standard Kernels (smb)
[17:04] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance
[17:04] <smb> Just sent out some rfc for the in-tree documentation
[17:05] <smb> Suggestion was for json format but making it simpler for a script seems not a good reason for changing the format for now
[17:06] <smb> So I would still go with the maintainers format for now
[17:06] <smb> ..
[17:06] <bjf> [TOPIC] Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)
[17:06] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review
[17:06] <MootBot> New Topic:  Blueprints: Review of the Stable Maintenance Process (sconklin / bjf)
[17:06] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review
[17:06] <bjf> We've successfully wrapped up our first trial of the new stable kernel process. Lucid and Maverick
[17:06] <bjf> kernels currently in -proposed are being promoted to -updates today. Everyone involved in the new
[17:06] <bjf> process have identified areas they will be working to improve for the next cycle. Current thinking
[17:06] <bjf> is the next cycle will start with an upload on Dec. 9.
[17:06] <bjf> ..
[17:07] <bjf> [TOPIC] Blueprints: Ubuntu Kernel Delta Review (apw)
[17:07] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-ubuntu-delta-review
[17:07] <MootBot> New Topic:  Blueprints: Ubuntu Kernel Delta Review (apw)
[17:07] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-ubuntu-delta-review
[17:07] <apw> aufs2 updated to official 2.6.37-rcN release from upstream. LIRC patches dropped to clean up the delta. 6 of the 21 personal patch reviews are now done. Some of these are likely to miss the natty-alpha-1 deadline, but none are release critical for the milestone.
[17:07] <apw> ..
[17:07] <bjf> [TOPIC] Blueprints: Kernel Version and Flavours (apw)
[17:07] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-version-and-flavours
[17:07] <MootBot> New Topic:  Blueprints: Kernel Version and Flavours (apw)
[17:07] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-version-and-flavours
[17:08] <apw> Discussions are ongoing as to the kernels to use for omap3, this centres around whether the Linaro kernel is fully featured enough and what levels of support we are able to provide for it.  Discussions continue but we are currently waiting on testing of the Linaro kernel against the current userspace.  This will not become critical until natty-alpha-2.
[17:08] <apw> ..
[17:08] <bjf> [TOPIC] Status: Natty (apw)
[17:08] <MootBot> New Topic:  Status: Natty (apw)
[17:08] <apw> The distro kernels are now rebased onto v2.6.37-rc3 and uploaded.  This latest kernel includes a further update to aufs bringing it in line with upstream.  It also carries the bulk of the configuration changes identified at UDS, harmonising a number of options; where those options are there to fix FTBS those are now documented.  It also carries a preview of the latest version of the "200 line" miracle automatic scheduler group patch, any feedback on t
[17:08] <apw> his kernel appreciated.  Testing generally remains good.
[17:08] <apw> ..
[17:09] <bjf> [TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)
[17:09] <MootBot> New Topic:  Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin / bjf)
[17:09] <bjf> ||                         || Upd./Sec.     || Proposed      || TiP || Verified    ||
[17:09] <bjf> || Dapper: Kernel          || 2.6.15-55.89  ||               ||     ||             ||
[17:09] <bjf> || Hardy:  Kernel          || 2.6.24-28.80  ||               ||     ||             ||
[17:09] <bjf> || =       LRM             || 2.6.24.18-28.7||               ||     ||             ||
[17:09] <bjf> || Karmic: Kernel          || 2.6.31-22.68  ||               ||     ||             ||
[17:09] <bjf> || =       mvl-dove        || 2.6.31-214.30 || 2.6.31-214.32 ||     ||             ||
[17:09] <bjf> || =       ec2             || 2.6.31-307.21 ||               ||     ||             ||
[17:09] <bjf> || Lucid:  Kernel          || 2.6.32-26.47  ||               ||     ||             ||
[17:09] <bjf> || =       LBM             || 2.6.32-25.24  || 2.6.32-26.25  ||     ||             ||
[17:09] <bjf> || =       mvl-dove        || 2.6.32-209.25 || 2.6.32-211.27 ||     ||             ||
[17:09] <bjf> || =       fsl-imx51       || 2.6.31-608.19 || 2.6.31-608.20 ||     ||             ||
[17:09] <bjf> || =       ec2             || 2.6.32-309.18 ||               ||     ||             ||
[17:09] <bjf> || = lts-backport-maverick || 2.6.35.22.34  ||               ||     ||             ||
[17:09] <bjf> || Maverick: Kernel        || 2.6.35-23.40  ||               ||     ||             ||
[17:09] <bjf> || =       mvl-dove        || 2.6.32-410.27 ||               ||     ||             ||
[17:09] <bjf> || =       ti-omap4        || 2.6.35-903.18 ||               ||     ||             ||
[17:09] <bjf> * Lucid and Maverick -proposed kernels promoted to -updates.
[17:09] <bjf> * Call for further testing of ec2 and ARM -proposed kernels for Lucid and Maverick.
[17:10] <bjf>   I've pinged Tobin Davis for ARM.
[17:10] <bjf> ..
[17:10] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[17:10] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[17:10] <JFo> Incoming Bugs
[17:10] <JFo> 19 Natty Bugs (up 7)
[17:10] <JFo> 1062 Maverick Bugs (up 37)
[17:10] <JFo> 1088 Lucid Bugs (up 6)
[17:10] <JFo> Current regression stats (broken down by release):
[17:10] <JFo> [17:10] <JFo> As this tag is deprecated, this listing is only to ensure that I keep it on my radar until
[17:10] <JFo> changes to the apport hooks and my processing of the currently tagged bugs is completed.
[17:10] <JFo>   * 3 natty bugs
[17:10] <smb> bjf, You should ping me for ec2
[17:10] <JFo>   * 396 maverick bugs (up 32 since the final maverick meeting)
[17:10] <JFo>   * 177 lucid bugs (up 14 since the final maverick meeting)
[17:10] <JFo> [17:10] <JFo>   * 20 maverick bugs (no change)
[17:10] <JFo>   * 78 lucid bugs (up 1)
[17:10] <JFo>   * 6 karmic bugs (no change)
[17:10] <JFo>   * 0 hardy bugs (no change)
[17:10] <JFo> [17:10] <JFo>   * 156 maverick bugs (up 9)
[17:10] <JFo>   * 192 lucid bugs (down 1)
[17:10] <JFo>   * 40 karmic bugs (no change)
[17:10] <JFo>   * 2 hardy bugs (no change)
[17:10] <JFo> [17:11] <JFo>   * 13 maverick bugs (no change)
[17:11] <JFo>   * 6 lucid bugs (down 1)
[17:11] <JFo>   * 1 karmic bug (no change)
[17:11] <JFo> ..
[17:11] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[17:11] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[17:11] <JFo> Today is the Bug Day. It is focusing on Bugs with patches so that I can focus
[17:11] <JFo> on getting the particular process I must use to address these bugs organized.
[17:11] <JFo> I will likely be pinging several of you with questions over the next week as
[17:11] <JFo> I work to finalize these steps and get them documented.
[17:11] <JFo> The next bug day will on December 7th. I will define the scope of that bug day in my e-mail
[17:11] <JFo> to the list so that I can take some time to determine what the best use of that
[17:11] <JFo> day will be.
[17:11] <JFo> ..
[17:12] <bjf> [TOPIC] Triage Status (JFo)
[17:12] <MootBot> New Topic:  Triage Status (JFo)
[17:12] <JFo> Spoke this week with Tapas Mishra who is interested in helping out. We had a great conversation on where to start. This conversation had been preceeded by someone providing several key links to wiki documentation that provided a first step toward Tapas' desire to work on wireless issues. My recommendation was to look at current wireless bugs that have been filed and use those issues to gain an understanding of the type of issues we see with wirele
[17:12] <JFo> ss drivers. Unforunately, due to the modular, and sometimes closed corporate nature of wireless drivers, we don't have a way to help someone who is interested in beginning coding on wireless drivers, but I am hopeful that the information I was able to provide and the recommendations smb and I made will be helpful.
[17:12] <JFo> ..
[17:13] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:13] <MootBot> New Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)
[17:13] <smb> \o
[17:13] <apw> o/
[17:13] <bjf> smb, go
[17:13] <smb> Just a question how comfortable those with upload rights are with the patch piloting
[17:13] <smb> And whether they would know what to do.
[17:13] <smb> ..
[17:14]  * apw has no clue
[17:14] <apw> there are some links in the original email which are intended to help one
[17:14] <smb> http://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews
[17:14] <MootBot> LINK received:  http://wiki.ubuntu.com/UbuntuDevelopment/CodeReviews
[17:14] <apw> know what the heck to do.  probabally its going to be a shambles
[17:14] <apw> :)
[17:14] <apw> ..
[17:15] <smb> Ok, so as much knowledge there as I have
[17:15] <smb> ..
[17:15] <bjf> apw, go
[17:16] <apw> just a heads up that alpha1 is coming up.  get your changes in
[17:16] <apw> ..
[17:16] <bjf> if there is nothing else ...
[17:17] <bjf> thanks everyone
[17:17] <bjf> #endmeeting
[17:17] <MootBot> Meeting finished at 11:17.
[17:17] <cking> thanks bjf
[17:17] <jjohansen> thanks bjf
[17:17] <smb> thanks bjf
[17:17] <hggdh> sorry, was on an appointment
[17:17] <JFo> thanks bjf