[09:38] <svqyqb> http://tinyurl.com/nkypfa
[10:01] <freeflying> @schedule shanghai
[11:05]  * persia peers about
[11:05] <TheMuso> No amachu yet.
[11:05] <czajkowski> persia: aloha there
[11:05] <persia> hey czajkowski
[11:06] <freeflying> persia: hi dude
[11:06] <persia> evening freeflying
[11:13] <TheMuso> Doesn't appear amachu is even online yet.
[11:16] <persia> Well, perhaps we oughtn't wait just on amachu.
[11:16] <persia> elky, lifeless You about?
[11:20] <lifeless> I am
[11:21] <lifeless> and have been
[11:21] <persia> That's 3.  We just need an elky or an amachu.
[11:21] <lifeless> lifeless without : doesn't hightlight :P
[11:21] <elky> o hai
[11:22] <persia> Ah. good.  Despite the absence of our fearless leader, I believe we have quorum.
[11:22] <persia> robert_ancell, You're up first.  Please introduce yourself.
[11:22] <robert_ancell> ok, my name is Robert. I'm based in Sydney
[11:23] <robert_ancell> I've been using Debian since ~2000 and Ubuntu since warty
[11:23] <robert_ancell> I'm the gcalctool maintainer and a GNOME games developer
[11:23] <robert_ancell> I've been working for Canonical for the last three months packaging and bugfixing gnome
[11:24] <robert_ancell> And  I'm here to apply for Ubuntu membership
[11:25] <lifeless> I'd like to note that we're the *community* membership board
[11:25] <lifeless> so our assessment is going to be focusing on community contributions more than purely technical ones
[11:25] <TheMuso> I've been thinking that starting out as a universe contributor, even though you aren't one technically, may be a better bet.
[11:25] <persia> robert_ancell, Do you have contributions other than just bug triage and uploads?
[11:25] <lifeless> if most of your stuff is technical, MOTU may be a better way to go
[11:26] <robert_ancell> persia, that would be the majority of my contributions.
[11:27] <persia> I think I'll agree with previous statements than that you would be better reviewed as a candidate for Contributing Developer
[11:27] <robert_ancell> My main motivation for membership has been to get syndicated on Planet Ubuntu so I can better communicate with the community (I am currently on Planet GNOME)
[11:28] <lifeless> robert_ancell: membership via MOTU is still membership
[11:28] <lifeless> robert_ancell: and will permit that
[11:29] <persia> And the MOTU Council is likely in a better position to review your integration with the developer segment of the community.
[11:30] <lifeless> next ;)
[11:30] <robert_ancell> ok, thanks
[11:30] <persia> OK.  PmDematagoda, please introduce yourself.
[11:32] <PmDematagoda> persia: well my name is Pramod Dematagoda
[11:32] <PmDematagoda> persia: Im from Sri Lanka
[11:32] <PmDematagoda> I just finished school
[11:32] <PmDematagoda> been using Ubuntu since about 3 years ago if I remember correctly
[11:32] <PmDematagoda> Ive mostly helped around with support on Ubuntu Forums, where I am a moderator
[11:33] <PmDematagoda> Ive also helped on Launchpad, though not to a degree as great as Ive done on Ubuntu Forums
[11:33] <PmDematagoda> and I also do help a little bit here and there in bug reports, testing and translations
[11:33] <PmDematagoda> Im 18 years of age btw :)
[11:34] <PmDematagoda> and my intentions are to start programming on Linux so that I may help the community even more
[11:34] <PmDematagoda> Ive already gained a bit of experience on programming in C and using technologies like DBus and DeviceKit
[11:35] <PmDematagoda> also I would like to help improve the situation of the usage of Linux here locally in Sri Lanka
[11:35] <PmDematagoda> though I still have yet to establish connections with any LUGs as of yet
[11:35] <PmDematagoda> and yeah, thats covers my introduction :)
[11:35] <PmDematagoda> is any more required?
[11:36] <persia> No, although we may have questions as we review the wiki page and other resources
[11:36] <PmDematagoda> ah, ok :)
[11:38] <persia> PmDematagoda, Your forums activity is fairly high (seems to overage > 10 posts a day for the past couple years).  Are there any particular areas of the forums in which you are more active, or any specific work you've done to help shape the forums or forum content?
[11:38] <PmDematagoda> persia: well, in my beginning days, I used to frequent the Absolute Beginner Talk, General Help and Installation & Upgrades section
[11:39] <PmDematagoda> but now I have also expanded into the Programming Talk section and the development sections too whenever I can
[11:39] <PmDematagoda> about forum content, I have made a few how-tos and such, but they are not as much as the support Ive provided
[11:40] <PmDematagoda> one how-to I created is the one on how to use Magic SysRq keys, although I havent updated that in a while
[11:40] <PmDematagoda> and I think that is the only how-to Ive created..
[11:40] <PmDematagoda> but I do take part in discussions where decisions need to be taken on certain issues in the forums
[11:40] <elky> you seem to have learned alot since august 07 anyway
[11:41] <PmDematagoda> that's in the staff forum, which is probably not visible :)
[11:41] <PmDematagoda> elky: yeah, my interest in Linux really helped
[11:41] <PmDematagoda> basically I was a Windows nut until my install got terrible, then I loaded up Ubuntu Feisty in the form of Ubuntu Ultimate and it really caught my attention
[11:44] <TheMuso> Do you have anybody here to support your work at this meeting today?
[11:45] <PmDematagoda> well, there is Pricey, nhandler, but they seem to be away
[11:49] <persia> I'm +1 on the application.  Long history, testimonials from two current Ubuntu Members, member of Forums Staff.
[11:50] <lifeless> +1 too
[11:50] <elky> +1 three
[11:51] <TheMuso> +1
[11:52] <persia> Congratulations PmDematagoda, and welcome.
[11:52] <PmDematagoda> persia: thank you very much :)
[11:52] <freeflying> PmDematagoda: congrats
[11:52] <PmDematagoda> everyone :)
[11:52] <PmDematagoda> freeflying: thank you :)
[11:52] <PmDematagoda> been waiting months for this, great feeling indeed :)
[11:52] <persia> So, who volunteers to be acting secretary this week (update wiki page, do launchpad-fu, send mail, etc.)
[11:52] <lifeless> great point persia. I volunteer you.
[11:52] <lifeless> ;P
[11:53] <lifeless> (If only cause its earlier in your evening)
[11:53] <PmDematagoda> thank you again to all, damn, so happy :)
[11:54] <persia> lifeless, OK (although it's only 06:53 here, so if it's evening, it's kinda late)
[11:54] <lifeless> where are you atm?
[11:54] <persia> Anything else anyone want to raise, or shall we meet again on the 28th?
[11:54] <persia> lifeless, UTC-4 (although I'll be back to the lovely positive lands next week)
[11:54] <lifeless> east coast?
[11:55] <persia> right.
[11:55] <lifeless> enjoy
[11:55] <lifeless> and we'll let you go get brekkie
[11:56] <persia> RIght then.  Adjourned.
[11:56] <TheMuso> nothing to raise here, sorry, had to tend a sick family member.
[14:00] <mcasadevall> #startmeeting
[14:00] <MootBot> Meeting started at 08:00. The chair is mcasadevall.
[14:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:00] <mcasadevall> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090714
[14:00] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090714
[14:00] <mcasadevall> [link] https://wiki.ubuntu.com/MobileTeam/Roadmap
[14:00] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Roadmap
[14:01] <mcasadevall> Who's here?
[14:01] <paulliu> Hi.
[14:01]  * StevenK isn't
[14:01]  * bjf waves
[14:02]  * ogra stals StevenK's joke and stands
[14:02] <ogra> *strands ... GAH
[14:02]  * mcasadevall wants wubi on ARM
[14:02] <mcasadevall> bahahahahhaha
[14:03] <ogra> mcasadevall, only if you can test it under wine on arm :P
[14:03] <mcasadevall> ogra, I could use winelib ...
[14:03]  * ogra doubts that would work
[14:03] <mcasadevall> ogra, you'd be suprised/scared
[14:03]  * GrueMaster mumbles incoherently. 
[14:04] <mcasadevall> lool, dyfet GrueMaster ping
[14:04] <mcasadevall> ah
[14:04] <mcasadevall> plars, ping
[14:04] <StevenK> ogra: Fail
[14:05] <dyfet> here
[14:06] <plars> sorta here
[14:06] <plars> at a conference also
[14:06] <ogra> excuses excuses
[14:06] <ogra> mcasadevall, read your calendar, lool is on holiday
[14:06] <mcasadevall> Oh
[14:07] <mcasadevall> alright then
[14:07] <mcasadevall> lets get started
[14:07] <plars> ogra: there's no excuse for me
[14:07] <ogra> celebrating past countrywide violence
[14:07] <mcasadevall> [topic] Action Item Review
[14:07] <MootBot> New Topic:  Action Item Review
[14:07] <mcasadevall> [topic]#
[14:07] <mcasadevall> NCommander to investigate https://bugs.launchpad.net/ubuntu/+source/vnc4/+bug/338148 (co)
[14:07] <MootBot> New Topic: #
[14:07] <mcasadevall> c/o
[14:07] <GrueMaster> co
[14:07] <mcasadevall> well, that makes that easy
[14:08] <mcasadevall> [topic] Specification review
[14:08] <MootBot> New Topic:  Specification review
[14:08]  * ogra suggests to sort by asignee
[14:08] <mcasadevall> fine
[14:08] <plars> good idea
[14:08] <mcasadevall> [topic] paulliu's specifications
[14:08] <MootBot> New Topic:  paulliu's specifications
[14:08] <mcasadevall> [topic] mobile-unr-karmic-application-res
[14:09] <MootBot> New Topic:  mobile-unr-karmic-application-res
[14:09] <StevenK> But what do I do for the other 99% of the meeting?
[14:09] <paulliu> Good news is we have anjal packages now.
[14:09] <ogra> waking up ?
[14:09] <StevenK> Why, it's 11pm
[14:09] <paulliu> But not much progress this week because I'm busy at moblin packaging.
[14:09] <ogra> oh, i thought 6am :)
[14:09] <mcasadevall> [topic] mobile-unr-karmic-connman
[14:09] <MootBot> New Topic:  mobile-unr-karmic-connman
[14:09] <paulliu> Anjal solves many issues for evolution.
[14:09] <ogra> but that was the other side of the world, i get it
[14:10] <paulliu> connman - still testing with apps. Low progress.
[14:10] <mcasadevall> [topic] GrueMaster's specifications
[14:10] <MootBot> New Topic:  GrueMaster's specifications
[14:10] <plars> paulliu: so is anjal going to happen?
[14:10] <mcasadevall> [topic] karmic-lsb-compliance-testing
[14:10] <MootBot> New Topic:  karmic-lsb-compliance-testing
[14:10] <plars> paulliu: or are we still going to decide if that's going to be in UNR or not?
[14:11] <paulliu> plars: I hope it can be happened. We just need to add some new API into webkit and evolution.
[14:11] <GrueMaster> mcasadevall: slow down.  one topic at a time.
[14:11] <plars> paulliu: what will replace the other functionality from evolution?
[14:11] <plars> calendar, contacts, etc?
[14:11] <plars> iirc, anjal is email component only, correct?
[14:11] <paulliu> plars: Yes, it's only e-mail component.
[14:12] <plars> or maybe that's a question coming up for GrueMaster :)
[14:12] <ogra> seems to fit :)
[14:13] <GrueMaster> karmic-lsb-compliance-testing:  Waiting on Alpha 3.  The testing only happens during iso testing.
[14:13] <paulliu> plars: Other components have to find a replacement.
[14:14] <mcasadevall> [topic] StevenK's specifications
[14:14] <MootBot> New Topic:  StevenK's specifications
[14:14] <mcasadevall> [topic] mobile-unr-karmic-wubi
[14:14] <MootBot> New Topic:  mobile-unr-karmic-wubi
[14:14] <ogra> mcasadevall, ??
[14:14] <ogra> you missed one from GrueMaster
[14:14] <mcasadevall> ogra, its marked deferred
[14:14] <GrueMaster> He always does.
[14:14] <ogra> oh, why is it showing up on the list if its not for karmic
[14:14] <ogra> hrm
[14:15] <mcasadevall> If the specification isn't actually deferred, then someone needs to update the status :-/
[14:15] <StevenK> -wubi is waiting for me to talk to the wubi guy
[14:15] <GrueMaster> Talk to davidm.  He's the boss.  I just work here.  :D
[14:15] <ogra> GrueMaster, is mobile-unr-karmic-applications actually dead for karmic ?
[14:16] <StevenK> I know why the .disk/info parser breaks, and I have a patch
[14:16] <ogra> davidm, ^^^ ?
[14:16] <davidm> the spec is dead, if we have specific apps we need a spec for the apps
[14:16] <ogra> ok
[14:16] <GrueMaster> not that I know of.  Last I was told, pidgin is being swapped with Empathy, and there were a few other apps.  Banshee is still unknown, but looking doubtful.
[14:16] <GrueMaster> ok
[14:16] <ogra> GrueMaster, probably unsubscribe yourself as asignee then
[14:16] <plars> sounds like we need one for anjal
[14:17] <ogra> so it wont show up on the weekly list
[14:18] <GrueMaster> done
[14:18] <ogra> :)
[14:19] <ogra> i guess lool will like if we keep the summary clean
[14:19] <mcasadevall> [topic] plar
[14:19] <MootBot> New Topic:  plar
[14:19] <mcasadevall> [topic] plars's specifications
[14:19] <MootBot> New Topic:  plars's specifications
[14:19] <mcasadevall> [topic] mobile-unr-karmic-compliance-autotesting
[14:19] <MootBot> New Topic:  mobile-unr-karmic-compliance-autotesting
[14:19] <plars> I hit an issue with this
[14:19] <plars> ldtp is currently broken in karmic
[14:20] <ogra> use xautomation and scripts ?
[14:20] <plars> there's a bug in for it currently
[14:20] <plars> ogra: that's a possible backup plan, but would like to avoid it if at all possible
[14:20] <ogra> yeah, its not beautoful indeed
[14:20] <ogra> *baeutiful
[14:20] <ogra> bah
[14:21]  * ogra shuffles the keys on his kbd ...
[14:21] <plars> next
[14:21] <mcasadevall> [topic] NCommander's specifications
[14:21] <MootBot> New Topic:  NCommander's specifications
[14:21] <mcasadevall> [topic] karmic-marvell-desktop
[14:21] <MootBot> New Topic:  karmic-marvell-desktop
[14:21] <plars> oh
[14:21] <ogra> ?
[14:21] <mcasadevall> oh wow
[14:21] <mcasadevall> sorry
[14:21] <mcasadevall> [topic] plars's specifications
[14:21] <MootBot> New Topic:  plars's specifications
[14:21] <mcasadevall> [topic] mobile-qa-karmic-arm
[14:21] <MootBot> New Topic:  mobile-qa-karmic-arm
[14:21]  * ogra throws coffeebeans at mcasadevall 
[14:22]  * mcasadevall falls over
[14:22]  * ogra guesses thats blocked by not having images 
[14:22] <plars> for the arm one, no progress this week, for the unr one, I didn't mark it started (forgot) but I did  do some checkbox tests for it this week
[14:22] <plars> to cover things like unr processes, and start with some rudimentary tests for apps
[14:23] <plars> done
[14:23] <mcasadevall> [topic] ogra's specifications
[14:23] <MootBot> New Topic:  ogra's specifications
[14:23] <mcasadevall> [topic] mobile-karmic-general-resolution-for-touchscreen-handling
[14:23] <MootBot> New Topic:  mobile-karmic-general-resolution-for-touchscreen-handling
[14:23] <ogra> still idling on that one
[14:23] <ogra> so : not started
[14:24] <mcasadevall> [topic] mobile-arm-karmic-subarches-in-debian-cd
[14:24] <MootBot> New Topic:  mobile-arm-karmic-subarches-in-debian-cd
[14:24] <ogra> not started, waiting on uboot-imx which should be ready very soon thanks to mcasadevall
[14:25] <ogra> beyond that i'd like to have prototyping ready for A3, even though we cant test it
[14:25] <ogra> next ...
[14:26]  * ogra twiddles tumbs 
[14:26]  * ogra throws coffeebeans at mcasadevall 
[14:26] <mcasadevall> sorry
[14:26] <mcasadevall> LP being stupid
[14:27] <mcasadevall> [topic] karmic-freescale-desktop
[14:27] <MootBot> New Topic:  karmic-freescale-desktop
[14:27]  * ogra throws coffeebeans at LP
[14:27] <ogra> good progress as far as i can tel without kernel
[14:27] <mcasadevall> On a second note uboot-imx was uploaded yesterday
[14:27] <ogra> worked a lot on the ftbfs list which showed various issues with packages
[14:27] <mcasadevall> (its sitting in the NEW queue)
[14:28] <ogra> mcasadevall, ugh, with the broken synopsis and description ?
[14:28] <ogra> and without the changes mentioned on revu ?
[14:28] <ogra> anyway
[14:28] <mcasadevall> ogra, not quite as bad as the verison on REVU, but I accidently left the "the Das"
[14:28] <ogra> upstart wasnt building, we had massive issues with binutils
[14:28] <mcasadevall> I can request a rejection and reupload if its a huge issue, else I'll fix it on the -0ubuntu2 upload
[14:29] <ogra> lool and doko attacked both yesterday after i had poked around on them the whole weekend
[14:29] <ogra> both appear to be fixed
[14:29] <ogra> livefses for freescale images build
[14:29] <ogra> still a lot of ftbfs issues
[14:29] <ogra> still the timeout issues with various packages
[14:30]  * bjf will be right back
[14:30] <mcasadevall> ogra, the timeout was extended to 600 minutes
[14:30] <ogra> (though the timeout on the buildd seems to have been bumped to 10h)
[14:30] <mcasadevall> But it wasn't long enough for mesa. A few of the previously FTBFSing KDE packages however now build)
[14:30] <ogra> which results in all buildds blocking for 10h
[14:30] <ogra> until it times out again
[14:30] <ogra> which in turn blocks package builds massively now
[14:30] <ogra> so we should discuss dropping lzma on armel imho
[14:31] <ogra> but thats for AOB ...
[14:31] <mcasadevall> ogra, I don't think thats a proper solution to be honest
[14:31] <ogra> done with freescale
[14:31] <mcasadevall> AOB?
[14:31] <mcasadevall> [topic] mobile-arm-karmic-easy-redboot-management
[14:31] <MootBot> New Topic:  mobile-arm-karmic-easy-redboot-management
[14:31] <ogra> mcasadevall, please put "solution for armel builder delays" to the AOB section
[14:32] <ogra> that spec might be obsolete with uboot
[14:32] <mcasadevall> oh
[14:32]  * mcasadevall didn't realize what AOB was
[14:32] <ogra> given that we dont need any redboot tools anymore and all of rdboot goes into pure maintenance with the switch to uboot
[14:33] <ogra> i'll discuss with davidm offline if it can be dropped, uboot has al necessary tools in the archive already
[14:33] <ogra> next
[14:33] <mcasadevall> [topic] mobile-arm-karmic-offline-installer-gui
[14:33] <MootBot> New Topic:  mobile-arm-karmic-offline-installer-gui
[14:34] <ogra> good progress
[14:34]  * bjf is back
[14:34] <ogra> after the switch to project-rootstock i actually had commits and patches from users already
[14:34] <ogra> working on a package
[14:34] <ogra> and started fiddling with glade to get a good gui for the initial setup
[14:35] <ogra> done :)
[14:36] <mcasadevall> [topic] mcasadevall's specs
[14:36] <MootBot> New Topic:  mcasadevall's specs
[14:36] <mcasadevall> [topic] mobile-arm-karmic-softboot-loader
[14:36] <MootBot> New Topic:  mobile-arm-karmic-softboot-loader
[14:36] <mcasadevall> No progress
[14:36] <mcasadevall> [topic] karmic-marvell-desktop
[14:36] <MootBot> New Topic:  karmic-marvell-desktop
[14:36] <mcasadevall> Got hardware, brought it up the u-boot prompt, and we got a source drop, which is now being merged into the kernel. Dep-wait on subarchies in d-i however. Still requires d-i porting
[14:37] <ogra> is it being merged ?
[14:37] <mcasadevall> ogra, what is?
[14:37] <ogra> o thought all ressources are on the imx stuff
[14:37] <ogra> kernel patches
[14:37] <ogra> bjf, ^^^ ?
[14:37] <mcasadevall> ogra, I believe the drop we got was .30
[14:38] <ogra> mcasadevall, i just said that i thought marvell was waiting on imx51 to be done because everyone is busy with that
[14:38] <ogra> no matter what the patch revision is :)
[14:38] <bjf> ogra, I am working on getting a git repo setup for Marvell so they can push their patches into it
[14:39] <ogra> right
[14:39] <ogra> so nothing is being merged atm
[14:39] <bjf> I believe the patch drop we got from Marvell was just a preliminary drop and not one they expected us to apply
[14:39] <ogra> yeah
[14:39] <bjf> ogra, that is correct
[14:39] <ogra> thats what i ment
[14:39] <ogra> we're in idle state there
[14:40] <mcasadevall> Do we want to review the unassigned specs?
[14:40] <ogra> beyond that the board spills segfaults across the board if you try to build anything on it
[14:40] <bjf> i'm waiting on more info back from Marvell devs needed to setup their accounts and the git repo
[14:40] <ogra> but the whole desktop works
[14:41]  * ogra wishes for some better framebuffer modes in the driver so he doesnt need to use a second monitor
[14:42] <mcasadevall> [topic] Any Other Business
[14:42] <MootBot> New Topic:  Any Other Business
[14:42] <ogra> well :)
[14:42] <ogra> what do we do with the armel buildds ?
[14:42] <ogra> if you let three packages with the timeout issue build you essentially put out all buildds for 10h
[14:43] <ogra> tonight someone gave back mesa which then blocked a full buildd for 10h
[14:43] <mcasadevall> ogra, there was a long discussion with IS on this
[14:43]  * mcasadevall did that *cough*
[14:43] <ogra> i'm a bit scared we have someone giving back three at the same time
[14:43] <ogra> which kills the buildfarm for us
[14:44] <ogra> (at least for 10h)
[14:44] <mcasadevall> *sigh*
[14:44] <mcasadevall> THere isn't a great solution for this problem
[14:44] <mcasadevall> I don't think we want to loose lzma compression though, even though image size is less of a concern for us than other architectures
[14:44] <ogra> i cant belive that it takes mesa 10h to zip the ddebs
[14:45] <mcasadevall> ogra, its the -dbgs, and it makes sense. If you have 100-200MB of binary debug symbols, its going to take ages to crunch down to 33MB
[14:45] <ogra> i still doubt it is actually caused by lzma and would like to see deeper research from IS on whats actually happening
[14:45] <mcasadevall> ogra, I can ask them to relook into it, but I setup launchpad-buildd on an ARM board, and ran a few of the failing builds myself
[14:45] <mcasadevall> GIven enough time, they do succeed.
[14:46] <ogra> yes, but we will run into issues with that
[14:46] <ogra> blocking buildds for 10h or more (if we bump it even more) will definately get in our way
[14:47] <mcasadevall> ogra, I realize that, but only a vast minority of builds will block and timeout like that
[14:47] <ogra> have you looked at http://qa.ubuntuwire.com/ftbfs/ ?
[14:47] <ogra> currently the whole of kde sits there
[14:48] <mcasadevall> ogra, due to qt4-x11, yes :-/
[14:48] <ogra> that will take us out of business for a week
[14:48] <ogra> even if only half of the kde packages have the timeout issue
[14:49] <mcasadevall> We're dealing with an architecture that is vastly underpowered unfortunately. I don't have a good solution on this one.
[14:49] <mcasadevall> Even if we remove lzma compression, its a stopgap measure at best
[14:49] <ogra> well, dropping lzma would be one
[14:49] <mcasadevall> Maybe we need something like distlzma for armel :-P
[14:50] <ogra> not a good one, not a beautiful one ... but it would get us back to jaunty buildspeed
[14:50] <ogra> which was slow anyway already
[14:50] <mcasadevall> If we're going to go that route, then I would like to see it be an official policy :-/
[14:50] <ogra> i dont want to see openoffic being uploaded in the current state
[14:50] <mcasadevall> (and then we modify debhelper(?) to ignore the lzma flag on ARM vs. having to edit every package)
[14:51] <ogra> indeed, it would need a well thought out solution
[14:51] <mcasadevall> offloading the lzma compression might be a viable solution
[14:51] <ogra> i'm just saying that the current situation is bloking us
[14:51] <mcasadevall> Not sure how IS will like it
[14:52] <mcasadevall> ogra, no, I agree. the buildd timeout bump was a stopgap measure at best, it didn't solve the underlying problem
[14:52] <ogra> i know there is HW coming for new buildds
[14:52] <ogra> but its not sure when and how fast it will be there
[14:52] <mcasadevall> Its slower in terms of raw muscle.
[14:52] <ogra> 1GHz/512M
[14:52] <ogra> pretty much the same
[14:52] <mcasadevall> Oh
[14:52] <ogra> but USB disks
[14:52] <mcasadevall> I thought the boards we were looking at were 800Mhz
[14:53] <mcasadevall> Yeah, now THAT is going to hurt
[14:53] <ogra> anyway, we wont come to a conclusion now
[14:53] <ogra> lets monitor the issue and put it on the agenda for next week
[14:53] <mcasadevall> [action] ogra and NCommander to confer on lzma compression issues on armel buildds
[14:53] <MootBot> ACTION received:  ogra and NCommander to confer on lzma compression issues on armel buildds
[14:54] <mcasadevall> done
[14:54] <ogra> i'd really like to hear lool about it
[14:55] <mcasadevall> I'm going to end the meeting
[14:55]  * mcasadevall looks left and right
[14:55] <mcasadevall> Anyone have anything else?
[14:56] <mcasadevall> #endmeeting
[14:56] <MootBot> Meeting finished at 08:56.
[15:00] <cjwatson> mdz,Keybuk: TB?
[15:00] <mdz> cjwatson: here
[15:00] <mdz> whose turn is it to chair?
[15:00] <mdz> (not me)
[15:00] <Keybuk> mine I think
[15:00] <mdz> we selected somebody at the end of the last meeting
[15:01] <mdz> Keybuk: ok, all yours
[15:01] <Keybuk> https://wiki.ubuntu.com/TechnicalBoardAgenda
[15:01] <Keybuk> #
[15:01] <Keybuk> Developer application board (ScottJamesRemnant)
[15:01] <mdz> Keybuk: mootbot?
[15:01] <Keybuk> mdz: I can never drive the damned thing
[15:01] <Keybuk> and spend half the meeting looking up its commands
[15:01] <mdz> ok, if you prefer to email out the log, that's fine with me
[15:02] <Keybuk> err, I don't keep logs ;)
[15:02] <Keybuk> #startmeeting
[15:02] <MootBot> Meeting started at 09:02. The chair is Keybuk.
[15:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:02] <Keybuk> I can't seem to see minutes from the previous meeting?
[15:02] <Keybuk> [TOPIC] Developer application board (ScottJamesRemnant)
[15:02] <MootBot> New Topic:  Developer application board (ScottJamesRemnant)
[15:03] <Keybuk> Colin replied to my mail yesterday with a few suggestions for updates
[15:03] <mdz> Keybuk: I emailed them to -devel-announce, want me to forward you a copy?
[15:03] <Keybuk> mdz: ah, so you did, just not ubuntu-devel
[15:03] <cjwatson> in my traditional "the meeting's tomorrow, hmm, what have I forgotten to do"
[15:03] <Keybuk> mdz: did you have a chance to read through his proposed edits?
[15:04] <mdz> Keybuk: I believe cjwatson and I have both supported the general proposal, and just made some suggestions regarding the details
[15:04] <mdz> what has sabdfl said?
[15:04] <Keybuk> indeed, I want to make sure we're all happy with the text
[15:04] <Keybuk> mdz: "+1" was his only reply
[15:04] <Keybuk> the next step would appear to be sending the mail to the Community Council
[15:05] <Keybuk> for their rubber stamp
[15:05] <cjwatson> were the edits I suggested OK, or do we want to adjust them a bit here?
[15:05] <Keybuk> cjwatson: I thought they were fine
[15:05] <mdz> Keybuk: I haven't seen a complete, revised version of the text, but was OK with everything what has been proposed in the thread
[15:05] <mdz> I'm happy for you to incorporate those bits and send it out
[15:06] <Keybuk> mdz: the revised text would be my "Updated text" mail, with the suggested replacement paragraph from Colin
[15:06] <Keybuk> ok
[15:06] <Keybuk> so we should send it to the CC
[15:06] <Keybuk> I guess we should wait for them to acknowledge it, and give them a chance to object
[15:06] <mdz> Keybuk: I don't see that mail
[15:06] <cjwatson> CC motu-council, perhaps, to give them a chance to comment too?
[15:06] <Keybuk> mdz: you _replied_ to that mail ;)
[15:06] <Keybuk> cjwatson: indeed
[15:06] <cjwatson> after all, the intent is that ultimately they will be directly affected
[15:07] <mdz> weird, it's not in my received mail archive
[15:07] <Keybuk> assuming there are no objections, we'll come back to this topic at the next meeting to enact the changes
[15:07] <mdz> I only have "Developer application board"
[15:07] <Keybuk> mdz: it's in that thread
[15:07] <cjwatson> Keybuk: I think mdz means a complete, revised version *including* my replacement paragraph
[15:07] <Keybuk> Date: 	Mon, 29 Jun 2009 10:59:43 +0100
[15:07] <cjwatson> but I don't think it matters if we are agreed anyway
[15:07] <dholbach> motu-council@lists.ubuntu.com is a public list, dunno if that's your intent
[15:07] <dholbach> is there any more details about the developer application board?
[15:07] <Keybuk> dholbach: at this point, I think we're more than happy for our plans to be public :-)
[15:08] <mdz> Keybuk: oh, I thought you meant a newer email entitled "Updated text". never mind.
[15:08] <Keybuk> ok, so
[15:08] <Keybuk> [ACTION] Keybuk to finalise text and send to CC and MOTU Council for review, objections and approval
[15:08] <MootBot> ACTION received:  Keybuk to finalise text and send to CC and MOTU Council for review, objections and approval
[15:09] <Keybuk> [AGREED] revisit at next meeting
[15:09] <MootBot> AGREED received:  revisit at next meeting
[15:09] <Keybuk> [TOPIC] Archive reorganisation (ColinWatson)
[15:09] <MootBot> New Topic:  Archive reorganisation (ColinWatson)
[15:09] <cjwatson> the current steps on the plan are:
[15:09] <cjwatson> (a) the developer application board (above)
[15:09] <cjwatson> (b) the actual package set contents
[15:09] <cjwatson> Keybuk and dholbach gave feedback on the sketch autogeneration I did
[15:09]  * dholbach gave some confused comments. :-)
[15:10] <cjwatson> I'm happy to look at splitting stuff out from core as time goes on but would like to get what I have into LP anyway, if there are no other objections to the general structure
[15:10] <cjwatson> however, there is some temporary blockage on the LP side; the packageset table needs to be attached to distroseries
[15:10] <cjwatson> I've had a phone call with Julian Edwards and others about that and they're taking action
[15:11] <cjwatson> other than that, we are more or less ready to start interviewing developers whose permissions might want to change in the new world order
[15:11] <cjwatson> dholbach: do you want me to start sending those out next week, given that you're on holiday?
[15:12] <cjwatson> ideally, I would be able to CC the new developer application board :-)
[15:12] <dholbach> cjwatson: that'd be great - if there's anything else I can help with (I know it's probably not going to be much), please let me know
[15:12] <cjwatson> but from the above it looks like that will probably not quite be set up next week
[15:12] <cjwatson> so I'll just direct replies to technical-board@, I think
[15:13] <cjwatson> (https://wiki.canonical.com/UbuntuPlatform/Community/ArchiveReorgPlan/Preparation#Interview%20Mail)
[15:14] <cjwatson> I'll edit that a bit to reflect the work I've done on defining the initial package sets
[15:14] <mdz> cjwatson: so next steps are: DAB (as above), and get Launchpad ready
[15:14] <cjwatson> mdz: do you have any feedback on the initial set layout I proposed?
[15:14] <mdz> cjwatson: I didn't see it until today, so I haven't read it yet
[15:15] <mdz> cjwatson: do you want my input before you proceed (modulo LP), or just to keep me informed?
[15:15] <cjwatson> I'd like your input
[15:15] <mdz> ok
[15:15] <cjwatson> as a sanity check if nothing else
[15:15] <mdz> I'll take an action to do that
[15:16] <cjwatson> I have nothing else on this topic for this meeting
[15:16] <mdz> Keybuk: ?
[15:17] <Keybuk> [ACTION] mdz to provide input on proposed package sets
[15:17] <MootBot> ACTION received:  mdz to provide input on proposed package sets
[15:17] <Keybuk> [ACTION] cjwatson to begin interviewing developers whose permissions might change
[15:17] <MootBot> ACTION received:  cjwatson to begin interviewing developers whose permissions might change
[15:17] <Keybuk> that's right?
[15:17] <cjwatson> yes
[15:17] <Keybuk> great
[15:17] <Keybuk> [TOPIC] Patent policy (JonoBacon)
[15:17] <MootBot> New Topic:  Patent policy (JonoBacon)
[15:17] <Keybuk> jono: !
[15:18] <jono> hey
[15:18] <jono> I wanted to check in on the status of the patent policy with the TB
[15:18] <jono> has this been finalized and approved?
[15:18] <mdz> sabdfl: scrollback emailed
[15:18] <mdz> jono: who have you received feedback from so far (or not)?
[15:19] <mdz> I've lost track
[15:19] <cjwatson> I gave feedback yesterday
[15:19] <cjwatson> mostly approving but with some wording suggestions for change of emphasis
[15:19] <jono> feedback from cjwatson mdz Keybuk
[15:19] <Keybuk> jono: from that, it looked like mdz had a few text-related suggestions that could warrant a redraft
[15:19] <Keybuk> likewise cjwatson?
[15:20] <mdz> jono: I replied with some comments (24 Jun), including questions which I think still need answering
[15:20] <jono> ok great
[15:20] <mdz> jono: did you receive those OK?
[15:20] <jono> are there any other topics regarding the policy that we would like to discuss here?
[15:20] <jono> mdz, yes, sorry, my mail is a little jumbled after the GCDS
[15:21] <mdz> ok, so action for jono to review and incorporate the feedback so far
[15:21] <mdz> and also for sabdfl to review and give feedback
[15:21] <jono> yep, I will have that ready for the next meeting
[15:21] <mdz> jono: if you could send it by next Tuesday, then we will have time to review it so we can vote at the next meeting. is that workable?
[15:21] <Keybuk> [ACTION] jono to update proposed patent policy text
[15:21] <MootBot> ACTION received:  jono to update proposed patent policy text
[15:21] <Keybuk> [ACTION] sabdfl to provide feedback
[15:21] <MootBot> ACTION received:  sabdfl to provide feedback
[15:21] <jono> mdz, sounds good
[15:22] <Keybuk> ok, great
[15:22] <Keybuk> [TOPIC] Select a chair for the next meeting
[15:22] <MootBot> New Topic:  Select a chair for the next meeting
[15:22] <Keybuk> cjwatson: looks like it's your turn ?
[15:22] <Keybuk> however it does occur during Debconf
[15:22] <cjwatson> my turn, yes
[15:23] <Keybuk> ok, guess that's agreed ;)
[15:23] <Keybuk> [AGREED] cjwatson will chair the next meeting
[15:23] <MootBot> AGREED received:  cjwatson will chair the next meeting
[15:23] <Keybuk> [TOPIC] AOB
[15:23] <MootBot> New Topic:  AOB
[15:23] <Keybuk> (I didn't see any applications pending review)
[15:23] <mdz> I have one item
[15:23] <Keybuk> mdz: yup?
[15:24] <mdz> I've been trying to facilitate getting a release manifest assembled
[15:24] <mdz> for 9.10
[15:24] <mdz> https://wiki.ubuntu.com/KarmicKoala/ReleaseManifest
[15:24] <mdz> which details exactly what the release deliverables are, who is responsible for them, where they will be hosted and served, where they are announced, etc.
[15:25] <mdz> there are still quite a few question marks on it, and some things which aren't yet signed off (robbiew is helping)
[15:25] <mdz> I'd like to solicit comment from the TB regarding the overall effort, and filling in any of the question marks
[15:26] <cjwatson> I think I wrote the original draft of that so any question marks there are things I didn't know :-)
[15:26] <mdz> and also to make folks aware that this exists as a tool for coordinating work
[15:27] <sabdfl> the manifest is likely to grow a Moblin edition
[15:28] <mdz> cjwatson: was putting the add-on back onto releases a conscious choice?
[15:28] <sabdfl> alongside Xubuntu etc - cdimage, rather than releases.ubuntu.com
[15:28] <Keybuk> it seems generally reasonable
[15:28] <cjwatson> mdz: accident, I think
[15:28] <cjwatson> that should say cdimage
[15:28] <mdz> cjwatson: has there been a conversation between the server and release teams about how we'll get the AMIs onto EC2?
[15:28] <cjwatson> or possibly the original draft predated that move
[15:28] <mdz> will that be part of the publishing process or a separate manual step?
[15:29] <mdz> cjwatson: agreed and edited
[15:29] <cjwatson> mdz: soren is taking care of that independently, as far as I know, and has been working with the IS team
[15:29] <cjwatson> given that they're built on a separate host, I explicitly don't want to have to indirect the publishing through antimony
[15:29] <mdz> cjwatson: are you OK with that, or is it better to centralize as many of those steps as possible within the release team so we don't block?
[15:29] <cjwatson> however, the last communication with the IS team was that the hostname would be ec2-image.ubuntu.com?
[15:29] <cjwatson> so I think that needs to be changed in light of our last conversation on the subject?
[15:30] <cjwatson> mdz: I'm OK with it, until such time as the image building is moved under the control of the cdimage team; I don't see a rush to do that
[15:30] <mdz> cjwatson: I've asked that it be changed, yes (in fact I did so before that request went in, but the message didn't get to all the right folks)
[15:30] <cjwatson> mdz: is that request in the form of an RT ticket?
[15:30] <mdz> cjwatson: no
[15:30] <mdz> just mail in the thread
[15:30] <cjwatson> do we have a naming consensus, so that we can file a ticket?
[15:31] <mdz> best suggestions so far were "uec" and "cloud"
[15:31] <mdz> sabdfl: any preference?
[15:32] <mdz> cjwatson: could you fill in the announcement column to reflect what we did for 9.04, as a starting point?
[15:32] <cjwatson> ok, will do
[15:32] <sabdfl> cloud
[15:32] <sabdfl> would be my preference
[15:32] <cjwatson> cloud-image.ubuntu.com, then?
[15:33] <cjwatson> I'll ask soren to file that, as he also needs to change the actual image file names
[15:33] <sabdfl> mdz is explaining the need for a separate domain to me
[15:34] <mdz> see above: <cjwatson> given that they're built on a separate host, I explicitly don't want to have to indirect the publishing through antimony
[15:34] <sabdfl> go with cloud-image, but please plan to consolidate the images around releases.ubuntu.com
[15:34] <cjwatson> the need is that it is currently not integrated into the regular cdimage build setup and it is hard to do so in the short term because the build process requires root
[15:34] <sabdfl> if we can't do that for 9.10 then fine, cloud-image. is ok
[15:34] <mdz> sabdfl: what I've asked is that they are presented alongside the ISOs on www.ubuntu.com/download
[15:34] <mdz> "I want server edition" -> "metal or cloud?" -> etc.
[15:34] <cjwatson> I can also put a link on releases.ubuntu.com if necessary
[15:35] <cjwatson> I agree that the separation is suboptimal
[15:35] <sabdfl> we need to get that straightened out for 10.04
[15:35] <mdz> the cloud bits are available on EC2 (here's a list of AMIs) or for UEC (here's a download)
[15:36] <cjwatson> sabdfl: ack
[15:36] <Keybuk> ok
[15:36] <Keybuk> [TOPIC] Tech Board membership
[15:36] <MootBot> New Topic:  Tech Board membership
[15:36] <Keybuk> my membership expires again shortly after the next meeting
[15:37] <Keybuk> and mdz's membership expires as well
[15:37] <Keybuk> at UDS, we discussed increasing the number
[15:37] <Keybuk> sabdfl: ?
[15:37] <sabdfl> aiee :-)
[15:37] <sabdfl> on the CC we've decided to have a two-yearly election
[15:37] <sabdfl> we want 12 candidates for 8 seats
[15:38] <Keybuk> I would be in favour of the same system for the TB
[15:38] <sabdfl> i'm happy to try that
[15:38] <Keybuk> are candidates nominating themselves, or selected?
[15:38] <sabdfl> dholbach is gathering nominations for the CC
[15:38] <sabdfl> self, me, CC, others, nominations can come from anywhere
[15:38] <Keybuk> sabdfl: can people self-nominate?
[15:39] <sabdfl> Keybuk: sure
[15:39] <dholbach> Keybuk: yes
[15:39] <nhandler> Just a suggestion, it might be beneficial to hold off on any TB election until after the CC elections
[15:40] <Keybuk> sabdfl: it seems appropriate that cjwatson should receive the nominations, as the only member whose seat is not about to expire?
[15:41] <mdz> https://launchpad.net/~techboard/+members
[15:41] <sabdfl> +1, Keybuk, but how does cjwatson feel about that?
[15:42] <Keybuk> cjwatson: ?
[15:42] <cjwatson> I guess I'm OK with that, although presumably I would essentially be passing them straight over to sabdfl
[15:42] <cjwatson> am I expected to do some vetting?
[15:42] <sabdfl> no, we can do that in the TB
[15:42] <cjwatson> and/or to actively go out seeking nominations?
[15:42] <sabdfl> no
[15:43] <Keybuk> could we not simply ask people to mail the nomination to the mailing list?
[15:43] <cjwatson> nhandler: why? (I'm not opposed, just curious)
[15:43] <Keybuk> what kind of numbers for the board should we target?  should we match the CC's 12 nominations for 8 seats?
[15:44] <nhandler> cjwatson: It might cause an issue if for instance some person is only interested in serving on one council or the other. If they were to make it on the CC, they might not want to be on the TB
[15:44] <Keybuk> nhandler: the CC and TB attract a very different kind of person, and are quite different in responsibility
[15:44] <Keybuk> or should be aim for a smaller number (6 seats?)
[15:45] <nhandler> Keybuk: The responsibilities are different, but I think some people could be qualified to serve on either of the councils
[15:46] <cjwatson> nhandler: as the only person other than sabdfl who's ever sat on both (not concurrently!) I can see why that would be the case, but I think it's reasonable to ask people to choose
[15:46] <mdz> sabdfl: your TB membership does not have an expiration date; is that intentional?
[15:46] <cjwatson> think of it a different way - it would suck if you got onto the CC when you really wanted to work on the TB, only to find out that there were TB elections a month later :-)
[15:46] <nhandler> cjwatson: I just think it would be easier for them to choose after knowing whether or not they make it on the CC
[15:46] <sabdfl> mdz: yes, i don't mind stepping down if that's appropriate
[15:47] <cjwatson> what's the expected timeframe for the CC elections?
[15:48] <sabdfl> we set a six week schedule for the CC, iirc. dholbach?
[15:48] <Keybuk> two weeks for nominations, four for voting?
[15:49] <nhandler> Keybuk: There is a period in there for confirming nominations and generating the short list as well
[15:49] <Keybuk> I'd say we should
[15:49] <cjwatson> that would basically mean extending Keybuk and mdz's memberships by ... what, fourteen weeks or so?
[15:49] <Keybuk> - announce for nominations today, received at the TB mailing list
[15:49] <Keybuk> - receive nominations by the next TB meeting in two weeks time
[15:49] <dholbach> sabdfl: what nhandler said - I'll send out an email about the exact schedule RSN
[15:50] <Keybuk> - announce voting at the TB meeting after that (11/8)
[15:50] <Keybuk> - announce membership at the TB meeting after that (25/8)
[15:50] <Keybuk> does that sound reasonable?
[15:50] <Keybuk> sabdfl, mdz, cjwatson?
[15:50] <cjwatson> nhandler: TBH, I think the sort of person who would be flexible enough to actually serve (as opposed to just apply) for either the CC or the TB would be easily confirmed for either, and so having them choose up-front is in practice not much different
[15:50] <sabdfl> Keybuk: +1
[15:51] <cjwatson> perhaps we should mention it in the nomination papers though
[15:51] <cjwatson> Keybuk: +1
[15:51] <sabdfl> nhandler: i think it's a reasonable concern, but we're able to resolve it during the nominations gathering process
[15:51] <mdz> Keybuk: seems a bit slow, but if it's the best we can do, I'm ok with it
[15:51] <cjwatson> err, "announce membership"?
[15:51] <cjwatson> as in that's the end of the vote?
[15:51] <Keybuk> yes
[15:51] <mdz> cjwatson: that's a 2 week voting period
[15:51] <cjwatson> right. I'm OK with that
[15:51] <Keybuk> two week nomination, two week deliberation and two week voting
[15:51] <Keybuk> each one terminating before a TB meeting
[15:52] <Keybuk> what about numbers?
[15:52] <Keybuk> is 8 too large for the TB?
[15:52] <Keybuk> we currently have 4 seats
[15:52] <cjwatson> it'd be a bit of a shift in style, but I think 8 is at the upper end of OK
[15:52] <mdz> that would mean 4 new slots
[15:52] <Keybuk> cjwatson's expires in 2011
[15:53] <Keybuk> Mark's does not expire
[15:53] <cjwatson> more than that would run into committee syndrome I think
[15:53] <mdz> I agree with cjwatson
[15:53] <Keybuk> mine has long expired, and I have indicated that I would prefer to vacate my seat and nominate myself for re-election to give others a chance
[15:53] <mdz> I think 6 would be sufficient, but definitely no more than 8
[15:53] <Keybuk> and mdz's expires in a few weeks
[15:53] <Keybuk> I think 6 sounds right
[15:54] <cjwatson> compromise on 7? :-) I'd like to err on the slightly larger side if possible to allow room for more non-Canonical participation
[15:54] <Keybuk> I'd be ok with 7
[15:55] <cjwatson> sabdfl: ?
[15:55] <persia> Is that 7 additional, or 7 total?
[15:55] <sabdfl> i'm happy with 6 or 7, but not with growing quorum
[15:55] <Keybuk> persia: total
[15:56] <mdz> if we open up 4 seats, we will be obliged to fill 4 seats, and I think it would be difficult to identify, discuss and vote in that many qualified folks in one go
[15:56] <sabdfl> i.e. if we grow the TB, let's not also make it harder to have quorum
[15:56] <Keybuk> so we would be electing 5 seats, how many nominations should we accept?  8 sounds right for that number
[15:56] <cjwatson> quorum is currently two isn't it?
[15:56] <cjwatson> or do you mean growing the percentage?
[15:57] <sabdfl> 2-3 would be fine
[15:57] <Keybuk> mdz: what kind of numbers do you think are right?
[15:57] <sabdfl> 4 would be difficult
[15:57] <mdz> Keybuk: I suggest 6
[15:57] <cjwatson> so how about total 6 quorum 3?
[15:57] <mdz> quorum is currently 2
[15:57] <cjwatson> atm we seem to have 3 pretty routinely
[15:58] <mdz> I think 3/6 is reasonable, but would like to understand sabdfl's concern better
[15:58] <cjwatson> so I *think* that would work out OK, although it would depend on timezones of the new members
[15:58] <mdz> I have to go to another meeting in 60 seconds though
[15:58] <cjwatson> we're lucky to have all the board members in the same timezone just now
[15:58] <Keybuk> can I just confirm which seats are up?
[15:58] <Keybuk> I know mine is
[15:58] <Keybuk> I'm unsure as to whether mdz's is - or whether yours will auto-renew
[15:58] <Keybuk> and I assume sabdfl's isn't?
[15:58] <sabdfl> 3/6-7 would be fine for me too
[15:59] <Keybuk> sounds like we agree on 6 seats with a Q of 3
[15:59] <sabdfl> on the CC we put the whole lot up :-)
[15:59] <mdz> Keybuk: mine is expiring according to LP
[15:59] <Keybuk> sabdfl: it seems unfair to force cjwatson to be elected twice in the same year ;)
[15:59] <cjwatson> I abstain from this debate :-)
[16:00] <Keybuk> sabdfl: it's up to you, we're just about out of time
[16:00] <mdz> Keybuk: agreed, I see no reason for cjwatson's term to be cut short
[16:00] <Keybuk> and I think we should have a plan now
[16:00] <sabdfl> i agree!
[16:00] <Keybuk> sabdfl: will your seat be up for nomination or will you retain it?
[16:00] <sabdfl> if you're all willing to stand for election, let's say cjwatson sits tight, and the rest is an open field
[16:01] <Keybuk> ok
[16:01] <Keybuk> so that's 5 seats
[16:01] <sabdfl> i'm thinking
[16:01] <sabdfl> i don't mind stepping down, if that will help. i know that my daily involvement in the platform is limited
[16:02] <sabdfl> if it's useful to have me on the TB, i'm happy to stay
[16:02] <Keybuk> sabdfl: that is completely up to you
[16:02] <sabdfl> alright, i'm delighted to appoint myself again ;-)
[16:03] <cjwatson> (appoint or nominate?)
[16:03] <Keybuk> (apologies to the server team)
[16:04] <Keybuk> sabdfl: ?
[16:05] <cjwatson> I think we'll have to cut short there; why don't we confirm the final details by mail?
[16:05] <Keybuk> indeed, it sounds like there's some over-the-desk action happening
[16:05] <Keybuk> #endmeeting
[16:05] <MootBot> Meeting finished at 10:05.
[16:06] <ttx> ok, who is here for the server team meeting ?
[16:06] <alexm> o/
[16:06] <Keybuk> ttx: apologies
[16:06] <ttx> Keybuk: no problem !
[16:06] <sommer> hey all
[16:07] <Daviey> o/
[16:07] <zoopster> o/
[16:07] <ttx> Your regular host, the incredibly entertaining mathiaz, is stuck in another meeting.
[16:07] <aruetten> o/
[16:07] <RoAkSoAx> o/
[16:07] <kirkland> o/
[16:08] <pace_t_zulu> o/
[16:08] <ttx> ok, let's go.
[16:08] <ttx> #startmeeting
[16:08] <MootBot> Meeting started at 10:08. The chair is ttx.
[16:08] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:09] <ttx> Today's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting
[16:09] <ttx> Last week minutes:https://wiki.ubuntu.com/MeetingLogs/Server/20090707
[16:09] <zul> hi
[16:09] <ttx> [TOPIC] Review ACTION points from previous meeting
[16:09] <nealmcb> \o
[16:09] <MootBot> New Topic:  Review ACTION points from previous meeting
[16:10] <ttx> I can't find any ACTION points in last week meeting minutes, so that should be short
[16:10] <ttx> Unless someone has a comment about last week meeting ?
[16:10] <pace_t_zulu> o/
[16:11] <ttx> then... we should proceed to...
[16:11] <ttx> [TOPIC] Roadmap
[16:11] <MootBot> New Topic:  Roadmap
[16:11] <Daviey> The agenda is somewhat thin, no?
[16:11] <ttx> Daviey: you can see through it.
[16:12] <Daviey> :)
[16:12] <ttx> Our Roadmap page still looks a little outdated and jaunty
[16:13] <kirkland> jaundis?
[16:13] <kirkland> oh, jaunty :-)
[16:13] <ttx> We still need to have that discussion on how to best refresh it, but I prefer to have this discussion with mathiaz around, since he designed the current one
[16:14] <ttx> so we'll pass.
[16:14] <ttx> and replace that with kirkland's interesting topic from last week meeting...
[16:15] <ttx> [TOPIC] Name one cool Ubuntu thing you did last week
[16:15] <MootBot> New Topic:  Name one cool Ubuntu thing you did last week
[16:15] <ttx> (an Ubuntu Server thing, pereferably)
[16:15] <Daviey> "I went shopping and i bought a.."
[16:16] <ttx> Daviey: 19U rack full of blades ?
[16:16]  * sommer setup drbd in a soon-to-be-production environment (on hardy though)... it was cool to me anyway :)
[16:17] <kirkland> ttx: I released PowerNap -- part of our cloud power management solution
[16:17]  * alexm reviewed karmic serverguide section about monitoring
[16:17]  * sommer cheers alexm
[16:17] <RoAkSoAx> I've been testing Pacemaker-Heartbeat clusters and fixing a couple bugs, and I should be doing a call for testing :). After that I'll be preparing HowTo's on how to integrate it with DRBD :)
[16:17] <ttx> ok, on my side, I took pictures of koalas during my vacation week.
[16:18] <ttx> he definitely looked karmic.
[16:18] <alexm> sommer: :-)
[16:18] <ttx> and was eating fresh eucalyptus leaves.
[16:18] <ttx> anyone else ?
[16:19]  * alexm installed -proposed kvm-84 in jaunty
[16:19] <ttx> alexm: great ! how did that go ?
[16:19] <alexm> seems to be working fine for me
[16:19]  * kirkland cheers alexm!
[16:19]  * kirkland could really use help getting some verification on 4 bugs a jaunty-proposed kvm-84 fixes
[16:19] <alexm> however, i couldn't provide much feedback on all the bugs listed by kirkland
[16:20] <kirkland> alexm: verified one of them, thanks!
[16:20] <kirkland> i need to move those 4 to verification-done, to get kvm-84 into hardy backports
[16:20] <alexm> some of them are quite specific scenarios
[16:20] <pace_t_zulu> i've been working on libposix
[16:20] <pace_t_zulu> and i'm interested in packaging skia for ubuntu
[16:20] <kirkland> unfortunately, i think most of my kvm testers are just happy running the kvm's i've been providing in ppa's
[16:21]  * ttx looks up skia
[16:21] <alexm> kirkland: there are a couple of reporters willing to test the -proposed ones next week or so
[16:22] <ttx> pace_t_zulu: doesn't look like very server-ish
[16:22] <pace_t_zulu> ttx: no it isn't
[16:22] <ttx> ok, anyone else with cool stuff to report ?
[16:23] <ttx> let's open the bar for general discussion then.
[16:23] <ttx> [TOPIC] Open Discussion
[16:23] <MootBot> New Topic:  Open Discussion
[16:25] <ttx> anyone has soething they want to bring up ? Or July is just too hot ?
[16:26] <alexm> anyone attended to Gran Canaria Desktop Summit?
[16:27] <ttx> alexm: nobody from the sever team, I think
[16:27] <ttx> server, even
[16:27] <kirkland> alexm: mdz did;  he wrote about it in his blog
[16:27] <alexm> i'm not sure if there was any session server-related, being desktop summit
[16:27] <alexm> i was just curious
[16:27] <ttx> it is very desktop-focused.
[16:27] <alexm> kirkland: thanks, i'll take a look
[16:28] <Daviey> I can't help but think the server team should be more involved with SRU bugs related to server packages..
[16:28] <Daviey> Bug #394696 is really "bugging" me
[16:28] <ttx> Daviey: excellent subject, thanks
[16:28] <Daviey> and the motu-sru team is *three* people
[16:28] <ttx> We definitely could do a better job at tracking server SRUs
[16:29] <alexm> would it help having apache2-mpm-itk in main?
[16:30] <ttx> tracking candidates and pushing accepted ones to completion
[16:30] <Daviey> I don't think it really needs to be in main TBH
[16:30] <Daviey> I think server *related* packages matter to the server team, no matter where they are..
[16:31] <alexm> sure, good point
[16:31] <ttx> I think discussion on server SRU tracking deserves some preparation and a full agenda point
[16:31] <Daviey> ttx: agreed
[16:31] <ttx> though for the particular bug you mention, it needs to be fixed asap
[16:32] <ttx> Daviey: but it is blocked on motu-sru afaict
[16:32] <Daviey> ttx: We should perhaps raise the discussion with motu(-sru) about how best to help aswell.
[16:33] <ttx> Daviey: this bug could use a proper SRU request, though it's quite simple
[16:33] <ttx> (step 2 in Procedure at https://wiki.ubuntu.com/StableReleaseUpdates)
[16:34] <ttx> anyway, we cannot subsitute ourselves to motu-sru
[16:34] <ttx> but tracking SRU candidates and having a regular server team meeting agenda point to review them, yes.
[16:35] <ttx> ACTION: ttx to add SRU tracking to next meeting agenda
[16:35] <ttx> [ACTION] ttx to add SRU tracking to next meeting agenda
[16:35] <MootBot> ACTION received:  ttx to add SRU tracking to next meeting agenda
[16:36] <ttx> ivoks: o/
[16:36] <ivoks> hi all
[16:36] <Daviey> ttx: thanks
[16:36] <pace_t_zulu> hi ivoks
[16:36] <ttx> anything else someone wants to mention before we wrap up ?
[16:37] <ivoks> doh...
[16:37] <ogra> icecubes for everyone !
[16:38] <ttx> ivoks: something you wanted to talk about ?
[16:38] <ivoks> not really
[16:38] <ttx> okay then
[16:38] <ttx> [TOPIC] Agree on next meeting date and time
[16:38] <MootBot> New Topic:  Agree on next meeting date and time
[16:38] <ttx> next week, same place, same time ?
[16:39] <alexm> ok
[16:39] <ttx> I think we have a reasonably good attendance with this timing.
[16:39] <sommer> +1
[16:39] <ivoks> and nothing else works... :)
[16:39] <ttx> alright.
[16:40] <ttx> #endmeeting
[16:40] <MootBot> Meeting finished at 10:40.
[16:40] <sommer> thanks ttx
[16:40] <ttx> Thanks everyone
[16:50] <pace_t_zulu> thanks for chairing ttx
[16:54] <alexm> thank you all
[18:00] <amitk> Hola everybody! We are about to start the kernel team meeting.
[18:01] <amitk> Roll Call
[18:01]  * bjf is here
[18:01]  * jjohansen present
[18:01]  * apw enters stage left
[18:01]  * manjo waves his arm
[18:01]  * smb enters right
[18:01]  * cking_ here
[18:01]  * apw crashes into smb
[18:01]  * ogasawara waves
[18:02] <amitk> I guess that's everybody
[18:02]  * manjo insures himself against apw
[18:02] <amitk> First of all, welcome ogasawara (officially now part of the kernel team)
[18:03]  * manjo welcomes ogasawara 
[18:03] <apw> \o/
[18:03] <amitk> ogasawara has already been our QA champion for a while
[18:03] <smb> \o
[18:03] <cking_> horrah
[18:03]  * jjohansen welcomes ogasawara
[18:03] <amitk> #startmeeting
[18:03] <MootBot> Meeting started at 12:03. The chair is amitk.
[18:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:04] <amitk> [TOPIC] Open Action Items: "(apw) update status page for kernel-karmic-kernel-decision-session"
[18:04] <MootBot> New Topic:  Open Action Items: "(apw) update status page for kernel-karmic-kernel-decision-session"
[18:04] <apw> done i believe
[18:04] <amitk> There was a related action for bjf to remove this from the list of blueprints that I've already done
[18:04] <amitk> [TOPIC] Open Action Items: "(jjohansen) to issue AA pull request"
[18:04] <MootBot> New Topic:  Open Action Items: "(jjohansen) to issue AA pull request"
[18:05] <jjohansen> done
[18:05] <apw> yep, and its pulled into the current karmic kernel
[18:05] <amitk> \o/
[18:05] <amitk> moving onto the status of Karmic
[18:05] <amitk> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:05] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:05] <amitk> [TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)
[18:05] <MootBot> New Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)
[18:05] <amitk> ogasawara, apw?
[18:06] <ogasawara> Release meeting bugs and status are at https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:06] <ogasawara> Currentely there are no RC Milestoned Bugs for Alpha3
[18:06] <ogasawara> Release Targeted bugs are at https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux
[18:06] <amitk> [TOPIC] Karmic Release Status: Milestoned Features
[18:06] <MootBot> New Topic:  Karmic Release Status: Milestoned Features
[18:06] <ogasawara> I think those are at https://edge.launchpad.net/ubuntu/+milestone/karmic-alpha-3
[18:07]  * manjo goes to pick up fedex... board is here 
[18:07] <amitk> [LINK] https://edge.launchpad.net/ubuntu/+milestone/karmic-alpha-3
[18:07] <MootBot> LINK received:  https://edge.launchpad.net/ubuntu/+milestone/karmic-alpha-3
[18:07] <amitk> Blueprints then...
[18:07] <amitk> [TOPIC] Blueprints: kernel-karmic-bug-handling
[18:07] <MootBot> New Topic:  Blueprints: kernel-karmic-bug-handling
[18:07] <ogasawara> Running the kernel arsenal scripts is showing good progress. . .
[18:07] <ogasawara> Weekly summary: down 58 Open bugs, down 143 New bugs, up 42 Fix Released bugs
[18:07] <ogasawara> I'm loosly tracking overall progress at http://status.qa.ubuntu.com/qapkgstatus/linux
[18:08] <ogasawara> amitk: done
[18:08] <amitk> ogasawara: should this be removed from the list of blueprints?
[18:09] <apw> its starting to sound like the work is now 'business as usual' to me
[18:09] <apw> and perhaps the general improvements can be reported in the bug stats section ?
[18:09] <ogasawara> amitk: like apw said, it's more of a routine maintenance now
[18:09] <ogasawara> amitk: so I say remove it and I'll report updates when needed
[18:09] <apw> ogasawara, do we want to maek the blueprint complete too?
[18:10] <apw> mark
[18:10] <ogasawara> apw: let me review first to make sure it's complete
[18:10] <amitk> [ACTION] (amitk) Remove Blueprints: kernel-karmic-bug-handling from list
[18:10] <MootBot> ACTION received:  (amitk) Remove Blueprints: kernel-karmic-bug-handling from list
[18:10] <apw> ack
[18:10] <amitk> [ACTION] (apw, ogasawara) Mark Blueprints: kernel-karmic-bug-handling as complete
[18:10] <MootBot> ACTION received:  (apw, ogasawara) Mark Blueprints: kernel-karmic-bug-handling as complete
[18:10] <amitk> [TOPIC] Blueprints: kernel-karmic-hwdb-workshop
[18:10] <MootBot> New Topic:  Blueprints: kernel-karmic-hwdb-workshop
[18:10] <ogasawara> I've been following up with Abel re bug 338772 and bug 399319
[18:10] <ogasawara> Abel and the Launchpad team are still working out the details for pushing the scripts to a central project repo
[18:11] <ogasawara> amitk: should hopefully know more next week about the project repo.  that's it for now.
[18:11] <amitk> [TOPIC] Blueprints: kernel-karmic-kms
[18:11] <MootBot> New Topic:  Blueprints: kernel-karmic-kms
[18:11] <apw> Karmic rebased to -rc3 which brings a slew of i915 updates for KMS.  ATI is still not supported in userspace.  Testing continues with x-edgers.
[18:12] <amitk> Any idea if ATI support will appear before A4?
[18:12] <apw> in userspace, not sure yet.  on my list to sync with them to find out
[18:12] <bjf> apw, what's the story on Nvidia?
[18:13] <apw> we're not expecting anything for nvidia for .31, nouveau is too new there
[18:13] <apw> we are likely to offer it through x-edgers in the meantime
[18:13] <amitk> [TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts
[18:13] <MootBot> New Topic:  Blueprints: kernel-karmic-new-kernel-on-lts
[18:13] <apw> that is rtg, i believe its not moved much since last week
[18:13] <amitk> [TOPIC] Blueprints: kernel-karmic-review-of-non-upstreamed-code
[18:13] <MootBot> New Topic:  Blueprints: kernel-karmic-review-of-non-upstreamed-code
[18:13] <smb> Ongoing, in rogress
[18:14] <smb> progress even
[18:14] <amitk> [TOPIC] Blueprints: kernel-karmic-android
[18:14] <MootBot> New Topic:  Blueprints: kernel-karmic-android
[18:14] <amitk> bjf: know anything?
[18:14] <bjf> stalled waiting on resources
[18:15] <bjf> this is in cooloney's hands now and he's helping with imx51
[18:15] <amitk> [TOPIC] Blueprints: kernel-karmic-sponsoring-staging-drivers
[18:15] <MootBot> New Topic:  Blueprints: kernel-karmic-sponsoring-staging-drivers
[18:15] <apw> this one is on hold
[18:15] <smb> I guess nothing new, yeah
[18:15] <apw> pending resource being available when the rest of the tasks are done
[18:16] <amitk> [TOPIC] Blueprints: kernel-karmic-ssd
[18:16] <MootBot> New Topic:  Blueprints: kernel-karmic-ssd
[18:16] <apw> i think that is complete from our point of view
[18:16] <cking_> that's complete. I needed to send an Email around, I forgot :-(
[18:16] <apw> i think i expected it going off the list this week
[18:16]  * cking_ too
[18:16] <apw> action that cking_ on it :)
[18:17] <cking_> OK
[18:17] <amitk> [ACTION] (cking) to send email about Blueprints: kernel-karmic-ssd
[18:17] <MootBot> ACTION received:  (cking) to send email about Blueprints: kernel-karmic-ssd
[18:17] <amitk> [TOPIC] Blueprints: kernel-karmic-suspend-resume
[18:17] <MootBot> New Topic:  Blueprints: kernel-karmic-suspend-resume
[18:17] <amitk> manjo: ?
[18:18] <manjo> nothing on that yet
[18:18] <apw> he has been working on the review of ubuntu/ so that ones behind it
[18:18] <amitk> [TOPIC] Blueprints: kernel-karmic-wifi
[18:18] <MootBot> New Topic:  Blueprints: kernel-karmic-wifi
[18:18] <manjo> I will be doing a session on it in atlanta linux fest
[18:18] <manjo> and at the sprint to see how kms works
[18:18] <manjo> in karmic
[18:18] <apw> i think that is rtg also, so not sure of wifi status
[18:18] <manjo> wrt to suspend/resume
[18:19] <amitk> ack manjo
[18:19] <amitk> [TOPIC] Blueprints: kernel-karmic-better-power-mgt
[18:19] <MootBot> New Topic:  Blueprints: kernel-karmic-better-power-mgt
[18:19] <amitk> that is stalled on me
[18:19] <amitk> awaiting resources, that is
[18:19] <amitk> [TOPIC] Blueprints: kernel-karmic-flavours
[18:19] <MootBot> New Topic:  Blueprints: kernel-karmic-flavours
[18:20]  * apw checks 
[18:20] <smb> Isn' that already closed?
[18:20] <amitk> it should be, but isn't marked on the Status page
[18:20] <apw> amitk, action me to clean up the status page pls
[18:21] <amitk> [ACTION] (apw) clean up status of Blueprints: kernel-karmic-flavours
[18:21] <MootBot> ACTION received:  (apw) clean up status of Blueprints: kernel-karmic-flavours
[18:21] <amitk> [TOPIC] Blueprints: kernel-karmic-config-rework
[18:21] <MootBot> New Topic:  Blueprints: kernel-karmic-config-rework
[18:21] <amitk> This should be closed too
[18:21] <apw> ok that one is officially complete
[18:21] <apw> i need to get pete to sync the status into the blueprints
[18:21] <bjf> amitk, that wasn't on the meeting agenda
[18:22] <apw> will do that as part of the previous action
[18:22] <amitk> bjf: I guess I didn't edit your mootbot runes correctly :)
[18:22] <amitk> [TOPIC] Other Release Tasks: AppArmor
[18:22] <MootBot> New Topic:  Other Release Tasks: AppArmor
[18:22] <amitk> jjohansen: great work!
[18:23] <apw> the current karmic kernels contain this in a ready to test state
[18:23] <jjohansen> :) can I sleep now ;)
[18:23] <apw> some small regression remain and are being worked
[18:23] <amitk> what is the upstream status?
[18:23] <jjohansen> currently there is a regression in the clone test
[18:23] <amitk> jjohansen: not yet, till we get this upstream ;-p
[18:24] <jjohansen> darn
[18:24] <amitk> has anything been posted to lkml?
[18:24] <jjohansen> I haven't done anything with upstream yet, just focused on the regressions
[18:24] <apw> i assume that we will be aiming to have it upstream in time for the kernel LL is cut from
[18:25] <jjohansen> yes
[18:25] <amitk> thanks jjohansen
[18:25] <amitk> [TOPIC] Other Release Tasks: ARM-Freescale
[18:25] <MootBot> New Topic:  Other Release Tasks: ARM-Freescale
[18:25] <bjf> the saga continues, we are now getting support from Freescale so we hope to see some progress this week, manjo is the new man on the spot
[18:25] <manjo> I built the bjf kernel
[18:25]  * pgraner tags manjo and shouts your it!
[18:25] <manjo> currenly building amitk 's kernel
[18:26] <manjo> waiting on a board
[18:26] <amitk> I've got a minimal imx51 kernel ported to 2.6.31-rc compiling
[18:26] <smb> We need to decide one more thing and I get the topic branch into clean state
[18:26] <manjo> and will check with anmar on a date & time I can be onsite
[18:26] <bjf> lots of Jaunty SRU work going on as well w.r.t. imx51
[18:26] <manjo> I talked to onsite rep and he is ready to go
[18:26] <smb> err, wrong kernel I guess
[18:26] <amitk> and this one uses the in-kernel file structure, APIs, etc.
[18:27] <amitk> [TOPIC] Other Release Tasks: Reintegrate Ports
[18:27] <MootBot> New Topic:  Other Release Tasks: Reintegrate Ports
[18:27] <amitk> apw: can we mark this completed?
[18:27] <apw> that one is complete.  we wanted to drop that one from the agenda
[18:27] <amitk> done
[18:27] <amitk> [TOPIC] Other Release Tasks: Grub2
[18:27] <amitk> same with this?
[18:28] <MootBot> New Topic:  Other Release Tasks: Grub2
[18:28] <cking_> yep.
[18:28] <apw> yep, thats complete
[18:28] <amitk> [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others
[18:28] <smb> * Dapper:   2.6.15-54.77 (security)
[18:28] <smb> * Hardy:    2.6.24-24.55 (security)
[18:28] <smb>             2.6.24-24.56 (proposed+security)[7] with 3/11 verifications
[18:28] <smb> * Intrepid: 2.6.27-14.35 (security)
[18:28] <smb>             2.6.27-14.36 (proposed+security)[7] with 5/24 verifications
[18:28] <smb>             LRM 2.6.27-14.20 (proposed)[25] with 1/2 verifications.
[18:28] <smb>             Verification for LRM should be complete now, but I just updated
[18:28] <MootBot> New Topic:  Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others
[18:28] <smb>             the report today.
[18:28] <smb> * Jaunty:   2.6.28-13.45 (security)
[18:28] <smb>             2.6.28-14.46 (proposed)[6] with 0/15 verifications
[18:28] <smb>             LRM 2.6.28-14.18 (proposed)[6]
[18:28] <smb>             LBM 2.6.28-14.15 (proposed)[6]
[18:28] <smb>             LRM and LBM are rebuilds with bumped ABI, the kernel contains an
[18:28] <smb>             import from upstream stable and should be tested well.
[18:29] <amitk> efficient as always smb :)
[18:29] <smb> I love to be :)
[18:29] <amitk> [TOPIC] Status: Karmic
[18:29] <MootBot> New Topic:  Status: Karmic
[18:29] <apw> The karmic kernel is now rebased to 2.6.31-rc3 (2.6.31-3.19).  Carries a large DRM delta, and some ext4 patches.  Also carries aufs2 for testing.  Finally it carries AppArmour (disabled) for testing.
[18:30] <amitk> Have we triggered a lot of kerneloops reports?
[18:30] <cking_> how do we test AppArmour if it's disabled?
[18:30] <jjohansen> use security=apparmor
[18:30] <cking_> OK
[18:30] <apw> not seen anyything specific for kernel oops
[18:30] <amitk> curious about the uptake of alphas
[18:31] <apw> we have a lot of people who were reporting bugs, and we are seeing a steep rise
[18:31] <apw> in regression-potential bugs, so someone is testing
[18:31] <apw> ogasawara, any feel for how much bug traffic we have?
[18:31] <cking_> any particular kinds of regressions worth mentioning?
[18:31] <smb> failed to boot?
[18:32] <ogasawara> apw: http://status.qa.ubuntu.com/qapkgstatus/linux might give a rough idea
[18:32] <apw> we've had a number of booting issues with specifici hardware, worst in -rc1
[18:32] <apw> things are looking better, but still wobbly
[18:32] <smb> also wireless and rfkill inparticular seemed to be an issue
[18:33] <apw> yeah lots of fallout from the rfkill re-work ...
[18:33] <amitk> Moving on...
[18:33] <amitk> [TOPIC] Status: ARM
[18:33] <MootBot> New Topic:  Status: ARM
[18:33] <amitk> bjf: anything else to add?
[18:33] <bjf> just more Jaunty SRU work being done
[18:34] <amitk> [TOPIC] Status: Netbook
[18:34] <bjf> more of Hugh's team getting involved (imx51 is really sucking up resources)
[18:34] <MootBot> New Topic:  Status: Netbook
[18:34] <smb> I'd say we are close there for the first step
[18:34] <smb> bug as bjf says there are more to come
[18:34] <smb> but
[18:35] <apw> netbook: we pushed and updated jaunty netbook tree for testing
[18:35] <amitk> is OEM the primary customer?
[18:35] <apw> we are moving to a specific flavour for netbook sometime this week, config issues allowing
[18:35] <apw> there is likely to be a karmic one shortly also
[18:35] <cking_> amitk, yep
[18:35] <awe> apw: unlike last time, i'm going to push this version into our repo this afternoon...
[18:36] <apw> awe excellent, let me know how it fairs
[18:36] <awe> apw: so should have testing status for you next week
[18:36] <apw> ack
[18:36] <cking_> awe, that's good
[18:36] <amitk> [TOPIC] Incoming Bugs: Regressions
[18:36] <MootBot> New Topic:  Incoming Bugs: Regressions
[18:36] <ogasawara> There were 5 regression-potential bugs added to the list this week and 1 regression-release.
[18:36] <ogasawara> All have already been commented on by a member of the kernel team.
[18:36] <ogasawara> As mentioned above, boot failures and rfkill types of issues
[18:37] <apw> we are struggling a bit to cope with the bug load right now, with so much resoruce being sucked up
[18:37] <amitk> and it will only get worse once we hit beta, I guess
[18:38]  * apw shudders
[18:38] <smb> As always any help is welcome ;-)
[18:38] <amitk> [TOPIC] Incoming Bugs: Bug day report
[18:38] <MootBot> New Topic:  Incoming Bugs: Bug day report
[18:38] <manjo> also some drivers in staging might need to be moved to latest version... rt2x00 for instanace
[18:38] <ogasawara> Bug day stats are as follows:
[18:38] <ogasawara> Bug Day Stats - Kernel Devs
[18:38] <ogasawara> Fix Released    5 (↑5)
[18:38] <ogasawara> Fix Committed   0 (↑0)
[18:38] <ogasawara> Won't Fix   3 (↑3)
[18:38] <ogasawara> Invalid 5 (↑5)
[18:38] <ogasawara> Reassigned  0 (↑0)
[18:38] <ogasawara> In Progress 2 (↑2)
[18:38] <ogasawara> Incomplete  79 (↑79)
[18:38] <ogasawara> Triaged 21 (↓10)
[18:38] <ogasawara> Confirmed   25 (↓10)
[18:38] <ogasawara> New 80 (↓74)
[18:38] <ogasawara> Bug Day Stats - Community
[18:38] <ogasawara> Fix Released    1 (↑1)
[18:38] <ogasawara> Fix Committed   0 (↑0)
[18:38] <ogasawara> Won't Fix   1 (↑1)
[18:38] <ogasawara> Invalid 1 (↑1)
[18:38] <ogasawara> Reassigned  0 (↑0)
[18:39] <ogasawara> In Progress 1 (↑1)
[18:39] <ogasawara> Incomplete  5 (↑5)
[18:39] <ogasawara> Triaged 40 (↓10)
[18:39] <ogasawara> Confirmed   0 (↑0)
[18:39] <ogasawara> New 1 (↑1)
[18:39] <ogasawara> Of course I want to give a big thank you to Andres Mujica and JFo for helping out last week!
[18:39] <ogasawara> I'd also like to point out that JFo even tackled a list of 30 additional bugs I gave him.
[18:39] <ogasawara> The next bug day will be next Tues 21 July.  We're going to target the backlog of bugs on the weekly kernel buglist.
[18:39] <amitk> Thanks Andres and JFo
[18:39] <apw> yep big thanks both
[18:39] <amitk> Thanks ogasawara
[18:39] <amitk> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:39] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:40] <apw> i'd call that a no
[18:40] <amitk> going once
[18:40] <amitk> going twice..
[18:40] <amitk> gone...
[18:40] <apw> sold to the man in the hat
[18:41] <amitk> Moving on to our favourite topic...
[18:41] <amitk> [TOPIC] Next Meeting Chair Selection
[18:41] <MootBot> New Topic:  Next Meeting Chair Selection
[18:41] <manjo> who is next on the list ?
[18:41] <bjf> apw is next
[18:41] <cking_> alphabetic?
[18:41] <apw> i believe that its me
[18:41] <apw> ack, should be ok for me next week
[18:41] <manjo> are we going by irc nics ?
[18:41] <amitk> [ACTION] (apw) is chair for next meeting
[18:41] <MootBot> ACTION received:  (apw) is chair for next meeting
[18:41] <amitk> That's all folks!
[18:41] <amitk> Thank you
[18:42] <amitk> And have a good day/night
[18:42] <amitk> #endmeeting
[18:42] <lieb> bye
[18:42] <MootBot> Meeting finished at 12:42.
[18:42]  * apw trips off stage right
[18:42]  * smb follows
[18:42]  * amitk stumbles off
[23:58] <Kangarooo> @now
[23:58] <Kangarooo> hello what date it is by ubuntu calendar?
[23:58] <nhandler> 23:00 UTC Kangarooo
[23:59] <bodhi_zazen> is everyone here ?
[23:59] <bodhi_zazen> #startmeeting
[23:59] <MootBot> Meeting started at 17:59. The chair is bodhi_zazen.
[23:59] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[23:59] <bodhi_zazen> Agenda :
[23:59] <bodhi_zazen> [LINK]https://wiki.ubuntu.com/BeginnersTeam/Meetings
[23:59] <MootBot> LINK received: https://wiki.ubuntu.com/BeginnersTeam/Meetings