[10:57] <Vantrax> Summoning Asia-Oceania RMB, persia, fenris,
[10:57] <Vantrax> Summoning Asia-Oceania RMB, persia, fenris, elky, takdir, lifeless, freeflying, amachu
[10:58] <freeflying> Vantrax: hi
[10:58] <Vantrax> hiya
[10:58] <czajkowski> if yer stuck I'm about
[10:58] <Vantrax> might be, bad run lately >.<
[10:59] <elky> Vantrax, hi
[10:59] <Vantrax> hi elky
[10:59]  * persia is about
[10:59] <Vantrax> czajkowski, which RMB are you on btw?
[11:00] <Vantrax> hi takdir
[11:00] <czajkowski> Vantrax: EMEA
[11:00] <takdir> hi Vantrax
[11:01] <czajkowski> you've 5 so you seem to be ok now
[11:01] <Vantrax> fyi if you didnt already know RMB peoples we have two extra items to get through today
[11:01] <Vantrax> #startmeeting
[11:01] <MootBot> Meeting started at 05:01. The chair is Vantrax.
[11:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[11:02] <Vantrax> Prabhash Rajarathne
[11:02] <Vantrax> are you present
[11:02] <Prabhash> yes
[11:02] <Vantrax> Please introduce yourself
[11:02] <Prabhash> Hi I'm Prabhash Rajarathne from Kandy
[11:03] <Prabhash> I'm currently contributing for Linux Localization Projects
[11:03] <Prabhash> empathy is my full Localization Project
[11:04] <Prabhash> Ah Kandy is 2nd Main city of SRI LANKA
[11:05] <Prabhash> Vantrax anything else I wanna tell??
[11:05] <Vantrax> your working with l10n for Ubuntu but not a member of the team and have no karma?
[11:06] <Prabhash> ya
[11:06] <elky> Is this linux localisation project thing an Ubuntu team?
[11:07] <Vantrax> My question then is where is your contribution recorded, and why do you not have testimonials from the group to support you?
[11:08] <Vantrax> I do like that you are teaching teachers Ubuntu, thats a good way to go
[11:08] <Prabhash> No I'm doing localization for Ubuntu as well as Fedora
[11:09] <Prabhash> I'm Mainly doing that Teacher Training programmes
[11:09] <Prabhash> Thanks Vantrax
[11:09] <Vantrax> A large part of the requirement for membership is a sustained contribution to the Ubuntu community, from what you have provided we have little to work from to identify your contribution. How do you contribute specifically to the Ubuntu community
[11:09] <freeflying> Prabhash: where can I find the training you've done?
[11:10] <Prabhash> what you mean  freeflying ?
[11:11] <freeflying> Prabhash: any article/blog/press news about your training?
[11:12] <Prabhash> unfortunatly theres know articles about that but have some Facebook Pictures
[11:12] <Vantrax> Prabhash from what you have shown we have little to go off, I would recommend you revisit this process in a few months but in the mean time check out https://wiki.ubuntu.com/SriLankanTeam, http://www.facebook.com/pages/Ubuntu-Sri-Lanka/234185506302 and contact https://wiki.ubuntu.com/AbdulHaleem
[11:13] <Vantrax> The best thing to do for work like what you have been doing is to have active members of the Sri Lanka loco support you in your application through testimonials or coming here to support you in person
[11:13] <Vantrax> It looks to me like you are on the right track, just a little under prepared this time:P
[11:14] <Vantrax> You need to show us that you have been contributing for a sustained period of time (typically 6 months), part of this can be testimonials from other people in the community supporting you and the work you do in education
[11:15] <Vantrax> I would also suggest getting in touch with the ubuntu manual/ubuntu education groups
[11:15] <Vantrax> Does that all make sense Prabhash
[11:15] <Prabhash> ya
[11:16] <Vantrax> Okies, any questions before we move on?
[11:17] <Prabhash> No
[11:17] <Vantrax> Mohana Kumar are you here and ready?
[11:17] <Mohan_chml> Vantrax: Yes
[11:17] <Vantrax> Thank you for coming Prabhash
[11:17] <Vantrax> Please introduce yourself
[11:18] <Mohan_chml> Hello all. I am Mohana kumar [ wiki.ubuntu.com/Mohan_chml ]. I am from Tamil Nadu, India. I like advocating for Ubuntu in a convincing way, among the mass. I am working in Ubuntu for the past two years. I like helping people with issues anytime, to my best and like to spread Ubuntu everywhere.
[11:19] <Mohan_chml> I believe in support from the back rather than just making people to migrate and to try working out their problems by themselves. I made in and around 150 people near my locality to work in Ubuntu and successfully managing them to not to get back from Ubuntu. I managed to install Ubuntu in my college for 60 machines and I am currently working on listing the Free Software alternatives for Proprietary software.
[11:19] <Vantrax> btw prabhash, i recommend you check Mohan_chml's wiki page, its a great example
[11:19] <Prabhash> ya sure
[11:20]  * Vantrax has no questions for mohi (mohi is in BT like me)
[11:20] <Mohan_chml> I switched over from Win X for its lack of security and vulnerabilities. I mostly involve in helping people at #ubuntu-beginners, where I learned a lot and I am currently a member of UBT. Till now I spent time with around 1000 people in 6 Colleges and I am helping the beginners who like to switch over. I initiate people to try Dual boot and then shift completely. I |am/and will be| serving for Ubuntu at my best wherever I go.
[11:20] <Mohan_chml> Vantrax: =]
[11:21]  * Vantrax waits for persia to ask one of his patented awsome questions
[11:22] <persia> Mohan_chml, Are the materials you used in the seminar you conducted available anywhere?  Similarly, has your work in documentation extended to documenting advocacy?
[11:23] <Mohan_chml> I do not have a written document. But my friend akkash is here as we worked together in FSFTN workshops [ http://fsftn.org/content/workshop-vcet-1 ]
[11:23] <Vantrax> I lied... where are you based mohi?
[11:23] <Vantrax> nm.. you already answered that, I lied again
[11:24] <Mohan_chml> I can't get you Vantrax
[11:24] <akkash> Hi Persia , Vantrax . I am mohan's friend we organized a workshop for college students . Around 300 + participated in the workshop.http://www.fsftn.org/content/workshop-vcet-1
[11:25] <persia> Towards what were the proceeds applied?
[11:26] <akkash> I missed the opportunity to participate in another workshop conducted in Kovilpatti. Which mohan participated .http://www.fsftn.org/content/workshop-kovilpati-1
[11:26] <Mohan_chml> persia: I have no documetation of my work till now and to be true, none knows about even Linux here. I Move along with FSFTN and I demonstrate the people about Ubuntu
[11:27] <Mohan_chml> persia: My whole Beginners team knows what I am doing daily and that is the only log that I can search for you for updates
[11:28] <Vantrax> I can confirm alof of the testimonies given to mohi and have seen his work since he joined the Beginners Team. He has been done great work in IRC support as well as his events in India
[11:28] <Mohan_chml> persia: I have my Blog http://infodevils.wordpress.com/2010/08/08/two-days-foss-workshop-at-national-engineering-college/ for an FSF speech
[11:30] <Vantrax> Any more questions for mohi? or are we happy to proceed?
[11:30] <duanedesign> I am here to cheer on Mohan_chml :)
[11:30]  * persia has no more questions
[11:30] <Mohan_chml> heya duanedesign =]
[11:31] <andrew_46> Lots of cheers here as well :)
[11:31] <Vantrax> [VOTE] Mohana Kumar for Ubuntu Membership
[11:31] <MootBot> Please vote on:  Mohana Kumar for Ubuntu Membership.
[11:31] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[11:31] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[11:31] <elky> +1
[11:31] <MootBot> +1 received from elky. 1 for, 0 against. 0 have abstained. Count is now 1
[11:31] <Vantrax> +1
[11:31] <MootBot> +1 received from Vantrax. 2 for, 0 against. 0 have abstained. Count is now 2
[11:31] <akkash> +1
[11:31] <MootBot> +1 received from akkash. 3 for, 0 against. 0 have abstained. Count is now 3
[11:31] <Mohan_chml> akkash: you can't
[11:31] <akkash> oops soory
[11:31] <Vantrax> lol only RMB memebers votes are counted akkash
[11:31] <akkash> sorry
[11:32] <Vantrax> it happens, quite often
[11:32] <Mohan_chml> sorry for that Vantrax
[11:32] <Vantrax> poke takdir
[11:33] <Vantrax> or czajkowski
[11:33] <persia> +1
[11:33] <takdir> +1 for Mohan_chml
[11:33] <MootBot> +1 received from persia. 4 for, 0 against. 0 have abstained. Count is now 4
[11:33] <MootBot> +1 received from takdir. 5 for, 0 against. 0 have abstained. Count is now 5
[11:33] <Vantrax> [ENDVOTE]
[11:33] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[11:33] <Vantrax> Grats Mohi
[11:33] <elky> Hmm, close call :P
[11:33] <Mohan_chml> Ty guys
[11:34] <andrew_46> Mohan_chml: Congrats!!!!!!!!!!!!!!!!
[11:34] <hyperair> congrats Mohan_chml
[11:34] <Vantrax> last but not least, Gary Dean your up
[11:34] <duanedesign> \o/
[11:34]  * KuKuKaChu is here
[11:34] <Mohan_chml> ty andrew_46 and hyperair and duanedesign  for making your presence
[11:34] <KuKuKaChu> I am Gary Dean, aka KuKuKaChu.
[11:35] <KuKuKaChu> I am a business management consultant in Jakarta, Indonesia (http://www.okusiassociates.com)
[11:35] <KuKuKaChu> I also operate a smaller computer support business (http://www.okusicomputersupport.com) specialising in setting up Ubuntu servers for small and medium businesses.
[11:36] <KuKuKaChu> I guess my main contribution to ubuntu is setting up a forum for Indonesian users of Ubuntu (http://ubuntu-indonesia.com).
[11:37] <KuKuKaChu> I have actively promoted use of Ubuntu in Indonesia, including producing at my own expense 1000 CDs for free distribution in Indonesia.
[11:37] <KuKuKaChu> i also actively promote Ubuntu through my websites.
[11:37] <Vantrax> that is a pretty major forum, and alot of CDs
[11:37] <KuKuKaChu> I also sometimes contribute Indonesian translations, though not as often as a should.
[11:38] <KuKuKaChu> vantrax, yes, it got rather big :)
[11:39] <Vantrax> I can see that, you are a little light on the translation side, something you plan on doing more of, or will you be focused on the forum and spreading the 'gospel' of ubuntu?
[11:40]  * Vantrax is constantly amazed how much ubuntu seems like a cult of linux:P
[11:41] <persia> KuKuKaChu, How would you describe the relation between BlankOn and Ubuntu?
[11:41] <takdir> KuKuKaChu, there is an ubuntu community at Jakarta, it's named Ubuntu Metro. this is a part of Ubuntu-ID. what is your plan to ubuntu community at Jakarta ? or do you just active in ubuntu-indonesia.com forum ?
[11:41] <KuKuKaChu> far question. i'm planning on contributing more to translations, as i know i can do a good job of it, but my time is very limited. i run a very busy company, and promoting ubuntu is a bit of an indulgence.
[11:42] <KuKuKaChu> before setting up ubuntu-indonesia.com i tried contacting people at ubuntu-id.org about the forum on that site, which was permanently unavailable.  i never got replies.
[11:42] <KuKuKaChu> i;ve never heard of Ubuntu Metro
[11:43] <takdir> ubuntu metro : http://groups.google.com/group/id-ubuntu/browse_thread/thread/a86b7c902a8359c0/cc656b91be43f4a0?lnk=gst&q=Ubuntu+Jakarta#cc656b91be43f4a0
[11:43] <KuKuKaChu> i am mainly active in ubuntu-indonesia.com
[11:43]  * Vantrax thinks takdir and KuKuKaChu should chat:P
[11:44] <Vantrax> anyone still need to ask more questions/need more time?
[11:44]  * persia is still waiting for an answer
[11:45] <KuKuKaChu> persia, sorry didnt see that
[11:45] <Vantrax> KuKuKaChu, [20:41] <persia> KuKuKaChu, How would you describe the relation between BlankOn and Ubuntu?
[11:46] <didrocks> Riddell: do you think there is still an opened window for a late unity upload fixing an issue with nautilus on file copy?
[11:46] <persia> didrocks, ECHAN ?
[11:46] <KuKuKaChu> well, i've never felt compeltely comfortable with the blankon project. i feel a properly translated Ubuntu should be sufficient
[11:46] <didrocks> persia: urgh, right :)
[11:48] <persia> Vantrax, Shall we proceed?
[11:49] <Vantrax> [VOTE] KuKuKaChi for Ubuntu Membership
[11:49] <MootBot> Please vote on:  KuKuKaChi for Ubuntu Membership.
[11:49] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[11:49] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[11:49] <takdir> KuKuKaChu, may be you should have testimonial from ubuntu-indonesia.com member and ubuntu-id community especially from Jakarta ? :)
[11:50] <persia> +0 : lots of great work, but uncertain integration with other (accepted) groups in Indonesia: would benefit from review/integration and discussion with takdir and (hopefully) return shortly.
[11:50] <MootBot> Abstention received from persia. 0 for, 0 against. 1 have abstained. Count is now 0
[11:50] <Vantrax> +0 Same reason as persia, its about integration into the Ubuntu community as much as the contribution (which is great)
[11:50] <MootBot> Abstention received from Vantrax. 0 for, 0 against. 2 have abstained. Count is now 0
[11:51] <elky> +0 same
[11:51] <MootBot> Abstention received from elky. 0 for, 0 against. 3 have abstained. Count is now 0
[11:52] <freeflying> +0
[11:52] <MootBot> Abstention received from freeflying. 0 for, 0 against. 4 have abstained. Count is now 0
[11:52] <Vantrax> [ENDVOTE]
[11:52] <MootBot> Final result is 0 for, 0 against. 4 abstained. Total: 0
[11:52] <takdir> +0 .. there is a great ubuntu indonesia forum since ubuntu-id forum is not active, may we should communicate at ubuntu-id milist
[11:52] <Vantrax> I would REALLY encourage you to come back in a few months after getting more plugged into your LoCo and other Ubuntu groups in your area.
[11:53] <Vantrax> do you have any questions or comments KuKuKaChu?
[11:54]  * persia would be happy to see back in a few weeks even, if it was part of a general reintegration of the apparently fractured ubuntu-id community.
[11:54] <KuKuKaChu> vantax, thanks. like i mentioned, my inability to make contact with the loco was my primary reason for go alone with ubuntu-indonesia, but hopefully now that i have made contact with takdir i can move forward and integrate it into the local forums
[11:54] <Vantrax> I would suggest keeping in contact with takdir and he will likely have you reapplying soon
[11:54] <KuKuKaChu> thank you, i shall
[11:55] <Vantrax> Okies, a few other admin items quickly before we break
[11:55] <persia> KuKuKaChu, And don't take this as indication you should close your forums: it's worth supporting those users, just in a way that helps bring everyone together for common sharing of solutions, etc.
[11:55] <Vantrax> ..... if you closed it we would have to hunt you down :P
[11:56] <Vantrax> Its a great thing, just not enough for your requirements on its own
[11:56] <KuKuKaChu> persia, thanks. no intention of closing. i would be lynched! it has a life of it's own now!
[11:56] <persia> Great!
[11:56] <elky> This is incentive to finish integrating with the community at large :)
[11:56] <Vantrax> Id like a volunteer to handle the team reporting function for the RMB. There are new reporting requirements (that require maintaining another wiki page) that we are not following and should be.
[11:57] <takdir> Ok KuKuKaChu, we will waiting you at ubuntu-id ? :)
[11:57] <elky> Vantrax, feel free to take over the paperwork! I shall not stop you
[11:57] <Vantrax> my wiki-fu is weak
[11:57] <KuKuKaChu> takdir, sure. answer your emails! ;)
[11:57] <elky> :(
[11:57] <elky> Vantrax, if you need "wiki-fu" then they're expecting an awful lot...
[11:57] <Vantrax> and since i started this new job my free time is not much
[11:57] <Vantrax> nhandler will step whoever wants to have a go through it all
[11:58] <Vantrax> if no one wants it, ill look at it and revisit this in a month or two
[11:58] <persia> Vantrax, I'll take it if you're too busy.  It's not much, and it's important.
[11:59] <Vantrax> thanks persia
[11:59] <elky> I have to admit I'm very much not in favour of the "Hi, we're your volunteers" "here, jump through these paperwork hoops" stuff that keeps snowballing.
[11:59] <Vantrax> ill help you where I can
[11:59] <Vantrax> Ok last bit, our CC approved restructure.
[11:59] <persia> elky, This is unrelated to that.  Team Reporting is *OLD*, and is just getting revived so we have a way to share knowledge that is clearer than the current systems.
[11:59] <elky> persia, if one needs "wiki fu" then there's somethign wrong
[11:59] <Vantrax> The approved change is that to cover our area effectively is to expand the team, run two meetings each with a quorum of 4
[12:00] <Vantrax> One meeting run at around 1900 GMT+5:30 and one at the current time or one hour earlier at 19:00 GMT+10.
[12:00] <Vantrax> As you can all make this meeting I assume the current time is fine and possibly one more person in the GMT +10 region. As most of you can't make a much later time, I propose we add 3 more in the GMT+5-6 region.
[12:00] <persia> elky, One doesn't really.
[12:00] <persia> Vantrax, These are not good times.
[12:00] <Vantrax> my definition of wiki-fu is rather broad:P
[12:01] <Vantrax> recommendation then persia?
[12:01] <Vantrax> I want to get this process kicked of this week
[12:01]  * persia tries to do math
[12:02] <persia> OK.  I'd suggest one about 8:00 UTC (Australia moves east in a week or so), and the other around 14:00 UTC (commutes in India are often very long).
[12:02] <Vantrax> that would be a meeting starting 4-5 hours from now
[12:03] <elky> Vantrax, which is fine for the indian/se-asian folks
[12:03] <Vantrax> if you go to 8:00 UTC you might have issues with people being able to make it with getting home at aroud 6pm and dinner
[12:03] <persia> Isn't that 22:00 in NZ, or did I do math wrong?
[12:03] <elky> which is what we're already doing to the indian/se-asian folks
[12:04] <elky> persia, nz is currently midnight right now
[12:04] <Vantrax> yep
[12:04] <elky> next week it'll be 10pm now for me
[12:04] <persia> And it's 11:00 UTC.  OK.  I'm happy with 9:00 rather than 8:00.
[12:04] <elky> Vantrax, you're melb or perth? can't remember
[12:04] <persia> Key is that we can't have it late enough that it's never good in NZ.
[12:04] <Vantrax> Brisbane, so im always on the same time
[12:05] <Vantrax> how about we try with 0900 and 1400 and see how we go, we can move the times around if we find it doesnt work
[12:05] <Vantrax> but do we all agree in principle, and on the times +-1hr
[12:05] <persia> Works for me, except I wonder how many can attend the 14:00.
[12:06] <persia> because I know at least three of us find that very late.
[12:06] <Vantrax> that would be why we would recruit people in central and western asia
[12:06] <Vantrax> to fill that
[12:06] <Vantrax> for example, india, sri lanka, china
[12:06] <persia> Right.  We need to be better at that (recruiting has been our continuing failure since we started).
[12:07] <elky> nigelb, around?
[12:07] <Vantrax> with 12 on the board and 4 required for quorum we should meet it more often now
[12:07] <Vantrax> with this going ahead
[12:07] <persia> China gets annoying because of the one-time-zone bit.  Being farther west doesn't help.
[12:08] <Vantrax> persia, true
[12:08] <Vantrax> always seemed odd that
[12:08] <persia> Vantrax, http://en.wikipedia.org/wiki/Time_in_China goes into great depth
[12:08] <Vantrax> we are over time guys, ill be sending out an email to ubuntu members advertising positions tonight.
[12:09] <elky> I nominate nigelb if he feels he's up to it
[12:09] <Vantrax> he he he
[12:09] <persia> Didn't we already get a nomination for him?  I thought I heard about one.
[12:09] <Vantrax> yeah we did, before we called for em
[12:09] <elky> I know he was considering it last time, but I don't know that anything happened
[12:10] <Vantrax> #endmeeting
[12:10] <MootBot> Meeting finished at 06:10.
[12:10] <elky> I think he might have had second thoughts, but that was months ago so he might be more easily coerced now :)
[12:10] <Vantrax> ill send an email out shortly
[12:10] <persia> I think we'd do well to check with everyone that has been nominated for various reasons previously, as we've put out previous calls for nominations, and not always acted on them clearly.
[12:10] <Vantrax> good idea
[12:11] <elky> persia, i agree. previous nominations were for a reason, and previous refusals might change with the new times
[12:11] <persia> I'm not convinced we've responded to all the previous nominations, but I may be incorrect.
[12:11] <persia> Anyway.  Any other business?
[12:13] <Vantrax> nope, we done
[13:59] <NCommander> #startmeeting
[13:59] <MootBot> Meeting started at 07:59. The chair is NCommander.
[13:59] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[13:59] <rsalveti> hey
[13:59]  * NCommander pokes GrueMaster dyfet ogra persia rsalveti and davidm
[14:00] <dyfet> that tickles
[14:00]  * ogra is here
[14:00] <mpoirier> o?
[14:00] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100928
[14:00] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100928
[14:00] <mpoirier> o/
[14:00]  * GrueMaster grumbles over his ginormous coffee mug.
[14:01] <NCommander> [topic] Action Item Review
[14:01] <MootBot> New Topic:  Action Item Review
[14:01] <NCommander> [topic] NCommander to clear out assigned bugs
[14:01] <MootBot> New Topic:  NCommander to clear out assigned bugs
[14:01] <NCommander> c/o
[14:01] <ogra> well
[14:02] <ogra> we'Re hard frozen now for RC
[14:02] <NCommander> [topic] Standing Items
[14:02] <MootBot> New Topic:  Standing Items
[14:02] <ogra> so you should have some time
[14:02] <ogra> :P
[14:02] <NCommander> [link] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:02] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:02] <davidm> G'day
[14:02] <NCommander> morning davidm
[14:02] <ogra> persia still has 3 todos
[14:03] <ogra> making us touch the trendline !
[14:03] <ogra> time to postpone them i'd say
[14:03] <GrueMaster> Ouch.  It burns!
[14:03] <persia> I've been postponing spec work, since none of it directly affected the release.  if it's causing you guys issues, I'll focus on that this week.
[14:04] <ogra> juts makes us look bad in the chart
[14:04] <persia> can't have that :)
[14:04] <ogra> (the overall one)
[14:05] <NCommander> [topic] http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html
[14:05] <MootBot> New Topic:  http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html
[14:05] <ogra> the milestone release one lookd fine
[14:05] <ogra> *looks
[14:05] <ogra> NCommander, you could port erlang this week ;)
[14:06] <NCommander> :-P
[14:06] <NCommander> cna I move on?
[14:06] <ogra> sure
[14:06] <NCommander> [topic] Kernel Status (cooloney, mpoirier, lag)
[14:06] <MootBot> New Topic:  Kernel Status (cooloney, mpoirier, lag)
[14:06] <mpoirier> It's going to be a shorter one this week:
[14:06] <mpoirier> Marvel (mvl-dove):
[14:06] <mpoirier>  * Marvell new LSP 5.3.5 drop has been integrated in Lucid.  Maverick is coming soon.
[14:06] <mpoirier> Freescale (fsl-imx51):
[14:06] <mpoirier>  * nothing new this week.
[14:06] <mpoirier> OMAP3:
[14:06] <mpoirier>  * SGX driver has been integrated to maverick and proven to work properly.  Will be introduced in N.
[14:06] <mpoirier>  * ftrace graph tracing integration has been put on hold as it need a lot of work.
[14:06] <mpoirier> OMAP4:
[14:06] <mpoirier>  * B647890 - FIXED: Building error when turning off CONFIG_SMP
[14:06] <mpoirier>  * B633227 - ONGOING: Instabilities with highmem activated - we have 1G memory without highmem but need to disable SMP or L2 cache.
[14:07] <mpoirier>  * B637947 - ONGOING: A solution seems to be in line for panda with proper renaming of sound card.  Awaiting patch from TI.
[14:07] <mpoirier> ..
[14:07] <ogra> there is a dove metapackage upload missing
[14:07] <ogra> the new kernel most likely wont end up in the images
[14:07] <ogra> (bjf uploaded one yesterday)
[14:07] <persia> I thought I saw a request in -release to push that pre-RC
[14:07] <ogra> ah, ok
[14:08] <ogra> i didnt follow release that closely, the spam^Wqueuebot was so noisy
[14:08] <rsalveti> for bug 633227 we're still trying to find an easy way to reproduce it, to try to understand it better
[14:08] <GrueMaster> Hope they fix bug 634161 when they push it out.
[14:08] <rsalveti> even when we remove highmem of the picture, we still face the issue
[14:08] <ogra> mpoirier, any plans to bring the IGEP2 stuff into an SRU post release ?
[14:09] <persia> GrueMaster, It's just a meta-upload.  Nothing substantive.
[14:09] <rsalveti> I was only able to make it work properly when running without highmem and no SMP, or no L2
[14:09] <mpoirier> ogra: the new paches or support the board ?
[14:09] <rsalveti> so probably a racing condition
[14:09] <ogra> mpoirier, yep
[14:09] <ogra> seems we have a lot progress on that platform
[14:09] <ogra> would be sad to lose the fixes
[14:09] <rsalveti> yup, would be good to push them forward
[14:09] <GrueMaster> persia: The bug only requires turning off the parport_pc driver in the config.
[14:09] <ogra> i understand they cant go into the release though
[14:10] <ogra> but probably in a post release SRU
[14:10] <rsalveti> post release would be fine
[14:10] <mpoirier> ogra: I think time started that - I'll look into it.
[14:10] <ogra> no hurry though
[14:10] <persia> GrueMaster, Right, but config is part of the source package for the kernel, not the -meta source package: unlikely the release team will approve such an upload, as it breaks the installer, etc.
[14:10] <NCommander> cna I move on?
[14:10] <rsalveti> and would be good if at least one of us could get one, to be able to check and test the kernel
[14:10] <ogra> post release is ... well after release :)
[14:10] <ogra> how is the progress on sound on OMAP4 ?
[14:11] <mpoirier> After conversation on alsa-soc yesterday it is clear the fix is not in the kernel.
[14:11]  * ogra didnt see much discussion in #ubuntu-arm recently
[14:11] <mpoirier> putting it there, even nicely, would be refused by upstream and therefore wasted time.
[14:11] <ogra> mind to update us on that ?
[14:12] <ogra> what exactly is required and what do we have
[14:12] <mpoirier> well, soc guys have purposely avoided putting a scheme forward for config in kernel.
[14:12] <persia> mpoirier, I read that differently: I read it as changing the kernel to ensure we had unique strings, and then creating userspace configs.
[14:13] <mpoirier> persia: I never denied that.
[14:13] <persia> Sorry, then I misunderstood your "the fix is not in the kernel".
[14:14] <mpoirier> persia: we won't apply the configs for the cards in the kernel.
[14:14] <mpoirier> the kernel names the card properly, which is pickup in userspace, where configs files are.
[14:14] <persia> berco has some config files that mostly work for panda: the same scheme could probably be extended to other boards.  There's an outstanding issue with saving the mixer state on reboot which needs investigation (if someone can replicate on beagle, I'm happy to investigate, but that requires someone with panda and beagle to confirm it's a parallel issue)
[14:15] <GrueMaster> Sounds like something for me to test.
[14:15] <ogra> so we'll use /usr/share/alsa* and the kernel gets a patch that /usr/share/alsa picks up stuff properly ?
[14:15] <mpoirier> we still have a problem in omap3 where cards for beagle C4, XM and gumstix are named the same.
[14:15] <mpoirier> ogra: yes.
[14:15]  * ogra is most concerned about OMAP4 atm :)
[14:16] <persia> ogra, Precisely.
[14:16] <ogra> OAMP3 is all nice to have
[14:16] <mpoirier> again, if we want to follow the same in omap3, a little bit of work is needed.
[14:16] <persia> mpoirier, Do we have differentiation for the differing wiremaps for the omap4 variants?
[14:16] <mpoirier> having a common solution for all our omapX platform would be nice.
[14:16] <GrueMaster> We have the same issue in Dove as well.
[14:17] <mpoirier> persia: omap4 variants ?
[14:17] <persia> We have the same issue for all SoCs where the kernel driver is reporting the codec chip rather than a unique per-wiremap string.
[14:17] <persia> mpoirier, I've at least heard "panda" and "blaze" mentioned on #ubuntu-arm.  I presume there are more design wins pending.
[14:17] <ogra> persia, we dont even have HW to test atm
[14:17] <persia> ogra, That hasn't been a blocker before :)
[14:17] <ogra> no ES2.0 blazes around currently
[14:18] <ogra> i'm sure you can get a wiremap though
[14:18] <mpoirier> i thought blaze was an omap3... I am I correct ?
[14:18] <ogra> no
[14:18] <ogra> blaze is omap4
[14:18] <mpoirier> ok.
[14:18] <GrueMaster> persia: W/o hw, we don't know what future designs will entail.
[14:18] <mpoirier> Again, the problem is exactly the same as omap3.
[14:18] <mpoirier> the name of the card is reported with no information on the platform.
[14:18] <ogra> blaze likely has a lot more options than panda
[14:18] <persia> GrueMaster, Right, but if we design something that is sufficiently modular that it will be a trivial patch for new designs, that's far better than assuming one device is the only way an SoC will behave.
[14:19] <ogra> but thats userspace stuff then as i understand
[14:19] <GrueMaster> persia: Best to let the kernel expose all and tweak it in user space on a case by case basis.
[14:19] <GrueMaster> reduces kernel bloat, faster to fix.
[14:20] <persia> ogra, kernelspace needs to report a unique string.  userspace can then use that unique string to set configuration through autodetection.
[14:20] <persia> GrueMaster, Indeed.  Precisely.
[14:20] <ogra> persia, right
[14:20] <mpoirier> persia: that's what I'be been saying.
[14:20] <persia> Right.
[14:20] <mpoirier> I had a chat with Irg on that front.
[14:21] <mpoirier> let see what they come back with.
[14:21] <NCommander> I hate to be a pain, but we have other things ot discuss, can we movw past kernel  bugs?
[14:21] <ogra> other things ?
[14:22] <mpoirier> ..
[14:22] <ogra> more important than kernel bugs ?
[14:22] <ogra> cant be
[14:22] <NCommander> on the agenda
[14:22] <ogra> :)
[14:22] <ogra> move
[14:22] <NCommander> :-p
[14:22] <NCommander> [topic] QA Status (GrueMaster)
[14:22] <MootBot> New Topic:  QA Status (GrueMaster)
[14:23] <GrueMaster> Not much to report.  Still finding obscure bugs.  Main focus has been on Dove audio (since omap audio is currently covered).
[14:23] <GrueMaster> I have a couple of bugs that I need to file, but absolutely no idea what to file against.
[14:23] <GrueMaster> Will try consulting #ubuntu-bugs again after the meeting.
[14:23] <NCommander> GrueMaster: pokem after the meeting and I'll help
[14:24] <NCommander> [topic]  * ARM Porting/FTBFS status ([[MichaelCasadevall|NCommander]], [[DavidSugar|dyfet]])
[14:24] <MootBot> New Topic:   * ARM Porting/FTBFS status ([[MichaelCasadevall|NCommander]], [[DavidSugar|dyfet]])
[14:24] <NCommander> pp[s
[14:24] <NCommander> *opps
[14:24] <ogra> NCommander, tsk
[14:24] <GrueMaster> (and I guess I'm done).
[14:24] <NCommander> Nothing new to report
[14:24] <ogra> let tobin finish :)
[14:24] <NCommander> [topic] QA Status (GrueMaster)
[14:24] <MootBot> New Topic:  QA Status (GrueMaster)
[14:24] <ogra> heh
[14:24] <ogra> hooray for complete messup :P
[14:25] <GrueMaster> Still looking into a bug query that is more useful to us.
[14:25] <NCommander> ;-P
[14:25] <GrueMaster> Not much else to report other than the images have been having build issues.
[14:25] <ogra> move ?
[14:25] <GrueMaster> move
[14:26] <NCommander> [topic]  ARM Image Status
[14:26] <MootBot> New Topic:   ARM Image Status
[14:26] <ogra> NCommander, skipping FTBFS ?
[14:26] <NCommander> ailed to build due to archive skew due to libgtk+2.0
[14:26] <NCommander> ogra: already did it
[14:26] <ogra> no
[14:26] <ogra> you mumble jumbled around
[14:27]  * ogra has been heavily grilled for FTBFS stuff by the release team
[14:27] <NCommander> [topic]  * ARM Porting/FTBFS stats NCommander/dyfet
[14:27] <MootBot> New Topic:   * ARM Porting/FTBFS stats NCommander/dyfet
[14:27] <ogra> the plplot disaster mader it all up to the release manager level
[14:27] <dyfet> I had worked on plplot yesterday, but it seems uneeded
[14:27] <ogra> the bug was lying dead for two weeks ...
[14:28] <ogra> please, if you cant work on bugs, tell me
[14:28] <ogra> it was pretty bad
[14:28] <persia> Um, about images, today is the day RC images spin, so it's kinda important to get them sorted...
[14:28] <ogra> persia, we'll get to that
[14:28] <persia> OK :)
[14:28] <ogra> NCommander, that was all i had to say about FTBFS
[14:28] <ogra> doko worked the whole wekend apparently to solve the issue
[14:29] <ogra> after we didnt move a bit on that bug
[14:29] <ogra> NCommander, move :)
[14:29] <NCommander> [topic]  ARM Image Status
[14:29] <MootBot> New Topic:   ARM Image Status
[14:29] <doko> ahh, that was the weekend before. just had the idea to ask upstream
[14:29] <ogra> should be building fine again with the next build
[14:30] <ogra> doko, thanks anyway for saving our butts
[14:30] <ogra> :)
[14:31] <ogra> the omap3 image had an issue with switching to linaro u-boot since that wasnt seeded yet
[14:31] <ogra> thats why we ended up without partition table on it
[14:31] <GrueMaster> oops
[14:31] <persia> So vstehle's bug is closed now?
[14:31] <ogra> beyond that the archive is in bad state currently
[14:31] <ogra> persia, fix committed
[14:31] <ogra> i'll set it to released after a testbuild
[14:31] <persia> OK.
[14:32] <ogra> once the archive has setteled
[14:32] <persia> Be glad you aren't trying to make this work on powerpc :)
[14:32] <ogra> also we're in RC preparation ... no manual builds ... Riddell is the master of antimony now
[14:32] <persia> Or, hrm.  Seems things are mostly caught up again.
[14:32] <ogra> all builds should be channelled or at least nodded off by him
[14:32] <ogra> (image builds i mean)
[14:33]  * Riddell feels the power
[14:33] <ogra> :)
[14:33] <ogra> NCommander, anything from you for images ?
[14:33] <GrueMaster> how long will it take to churn through the gtk update?
[14:33] <ogra> dove builds all fine ?
[14:34] <ogra> GrueMaster, just watch the build queue :)
[14:34] <GrueMaster> yea, that will keep me awake.  :P
[14:34] <ogra> its exciting :)
[14:35]  * ogra tickles NCommander 
[14:35] <davidm> NCommander, anything from you on images?
[14:36]  * davidm thinks NCommander needs a better Internet connection
[14:36] <ogra> or stronger coffee
[14:36] <ogra> well, we still have nearly 30 min ...
[14:36] <ogra> *twiddle*
[14:37] <davidm> We what is next on the agenda?
[14:37] <NCommander> sory, laptop haes me
[14:37] <davidm> Ah he's back
[14:37] <davidm> NCommander, , anything from you for images ?
[14:37] <NCommander> Worked on Dove ubiquity iconand other things
[14:38] <NCommander> go a patch but didn'tmake it in tfrom rc freeze, will test it some more and submit it before EOD today
[14:38] <NCommander> I think that's it for me
[14:39] <NCommander> [topic] ABO
[14:39] <MootBot> New Topic:  ABO
[14:40] <NCommander> folks, its spec drafting time
[14:40] <NCommander> onl6 news I have
[14:40] <ogra> and activity report time too :)
[14:40] <ogra> only rsalveti has submitted his yet
[14:41] <ogra> we others suck !
[14:41] <NCommander> anyway, anything else, or I am going to close out the meeting
[14:41]  * GrueMaster is ready to post
[14:41] <NCommander> once
[14:41] <NCommander> twice
[14:41]  * ogra not but will do so today
[14:41] <NCommander> three timeis the charm
[14:41] <NCommander> and good night folks
[14:41] <NCommander> #endmeeting
[14:41] <MootBot> Meeting finished at 08:41.
[14:42]  * NCommander goes AFK
[17:55] <JFo> o/
[17:56]  * JFo starts the wave
[17:59] <JFo> \o/
[18:00] <bjf> #startmeeting
[18:00] <MootBot> Meeting started at 12:00. The chair is bjf.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:00] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:00] <bjf> #
[18:00] <bjf> # NOTE: '..' indicates that you are finished with your input.
[18:00] <bjf> #
[18:01] <bjf> [TOPIC] ARM Status (lag)
[18:01] <MootBot> New Topic:  ARM Status (lag)
[18:01] <bjf> lag is on vacation, anyone have status?
[18:01] <bjf> guess not, moving on
[18:01] <bjf> [TOPIC] Release Metrics: (JFo)
[18:01] <MootBot> New Topic:  Release Metrics: (JFo)
[18:01] <JFo> please note that the statistics are for a 2 week time period:
[18:01] <JFo> Release Meeting Bugs (5 bugs, 9 Blueprints)
[18:01] <JFo> [18:01] <JFo>  * 1 linux kernel bugs (no change)
[18:01] <JFo>  * 0 linux-fsl-imx51 bugs (no change)
[18:01] <JFo>  * 0 linux-ec2 bugs (no change)
[18:01] <JFo>  * 0 linux-mvl-dove bugs (no change)
[18:01] <JFo>  * 0 linux-ti-omap bugs (no change)
[18:01] <tgardner> bjf,  lag chases snakes in his sleep. does taht count?
[18:01] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[18:01] <JFo> [18:01] <JFo>  * 13 linux kernel bugs (up 6)
[18:01] <JFo>  * 0 linux-fsl-imx51 bugs (down 1)
[18:01] <JFo>  * 0 linux-ec2 bugs (down 1)
[18:01] <JFo>  * 2 linux-mvl-dove bugs (down 1)
[18:01] <JFo>  * 0 linux-ti-omap bugs (down 1)
[18:02] <JFo>  * 0 linux-meta-ti-omap bug (no change)
[18:02] <JFo> [18:02] <JFo>  * 13 blueprints (Including HWE Blueprints)
[18:02] <JFo> [18:02] <JFo>  * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]
[18:02] <JFo>  * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]
[18:02] <JFo> heh
[18:02] <JFo> ..
[18:02] <bjf> tgardner, it does and will be noted in the meeting minutes
[18:02] <bjf> [TOPIC] Blueprint: kernel-maverick-bug-handling (JFo)
[18:02] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:02] <MootBot> New Topic:  Blueprint: kernel-maverick-bug-handling (JFo)
[18:02] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:02] <JFo> remaining items postponed. To be discussed at UDS.
[18:02] <JFo> ..
[18:03] <bjf> so i will remove this from the agenda
[18:03] <JFo> thank you sir
[18:03] <bjf> [TOPIC] Status: Maverick (ogasawara)
[18:03] <MootBot> New Topic:  Status: Maverick (ogasawara)
[18:03] <ogasawara> The Maverick Release Candidate comes out this Thurs Sept 30 and the Release Team has stopped processing upload requests for the Ubuntu 10.10 Release Candidate. See https://wiki.ubuntu.com/ReleaseCandidateProcess for more info.
[18:03] <ogasawara> We've been queuing patches for Maverick SRU which includes the latest 2.6.35.5 and 2.6.35.6 stable updates.  We are also planning a 0-day kernel upload which has been documented at bug 647071 .  I'd finally like to point out that we have closed out all Maverick blueprint work items \o/.  We have been and will be below the trend line for the entire Maverick cycle for our overall burn down chart.
[18:03] <ogasawara> [LINK] http://people.canonical.com/~platform/workitems/maverick/canonical-kernel-team.html
[18:03] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone ubuntu-10.10
[18:03] <MootBot> LINK received:  http://people.canonical.com/~platform/workitems/maverick/canonical-kernel-team.html
[18:03] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick#Milestone ubuntu-10.10
[18:04] <ogasawara> ..
[18:05] <bjf> [TOPIC] Security & bugfix kernels - Lucid/Karmic/Jaunty/Hardy/Others (smb)
[18:05] <MootBot> New Topic:  Security & bugfix kernels - Lucid/Karmic/Jaunty/Hardy/Others (smb)
[18:05] <smb> ||                   || Upd./Sec.     || Proposed      || TiP || Verified    ||
[18:05] <smb> || Dapper: Kernel    || 2.6.15-55.88  ||               ||     ||             ||
[18:05] <smb> || Hardy:  Kernel    || 2.6.24-28.79  ||               ||     ||             ||
[18:05] <smb> || =       LRM       || 2.6.24.18-28.7||               ||     ||             ||
[18:05] <smb> || Jaunty: Kernel    || 2.6.28-19.65  ||               ||     ||             ||
[18:05] <smb> || Karmic: Kernel    || 2.6.31-22.65  || 2.6.31-22.66  ||   5 ||  1/ 4 (+ 1) ||
[18:05] <smb> || =       mvl-dove  || 2.6.31-214.30 || 2.6.31-214.32 ||   5 ||  1/ 4 (+ 1) ||
[18:05] <smb> || =       fsl-imx51 || -- retired -- ||               ||     ||             ||
[18:05] <smb> || =       ec2       || 2.6.31-307.17 || 2.6.32-307.18 ||   5 ||  1/ 4 (+ 1) ||
[18:05] <smb> || Lucid:  Kernel    || 2.6.32-25.44  ||               ||     ||             ||
[18:05] <smb> || =       LBM       || 2.6.32-25.23  || 2.6.32-25.24  ||   1 ||  0/ 1       ||
[18:05] <smb> || =       mvl-dove  || 2.6.32-209.25 || 2.6.32-211.27 ||   0 ||             ||
[18:05] <smb> || =       fsl-imx51 || 2.6.31-608.19 || 2.6.31-608.20 ||   0 ||             ||
[18:05] <smb> || =       ti-omap   || 2.6.33-502.10 || (in progress) ||     ||             ||
[18:05] <smb> || =       ec2       || 2.6.32-308.16 || (in progress) ||     ||             ||
[18:05] <smb>  * The Lucid proposed kernel has been moved to updates. Topic branch updates
[18:05] <smb>    which are rebased against this have or will be uploaded.
[18:05] <smb>  * Karmic fsl-imx51 has been retired.
[18:05] <smb> ..
[18:06] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[18:06] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[18:06] <JFo> 629 Maverick Bugs (up 96)
[18:06] <JFo> 978 Lucid Bugs (down 58)
[18:06] <JFo> Current regression stats (broken down by release):
[18:06] <JFo> [18:06] <JFo>   * 320 maverick bugs (up 48)
[18:06] <JFo>   * 160 lucid bugs (down 10: to be converted to regression-release)
[18:06] <JFo> [18:06] <JFo>   * 55 lucid bugs (up 8)
[18:06] <JFo>   * 7 karmic bugs (no change)
[18:06] <JFo>   * 4 jaunty bugs (no change)
[18:06] <JFo>   * 0 hardy bugs (no change)
[18:06] <JFo> [18:06] <JFo>   * 170 lucid bugs (down 11)
[18:06] <JFo>   * 36 karmic bugs (down 1)
[18:06] <JFo>   * 17 jaunty bugs (down 1)
[18:06] <JFo>   * 2 hardy bugs (down 1)
[18:06] <JFo> [18:06] <JFo>   * 6 lucid bugs (down 1)
[18:06] <JFo>   * 1 karmic bug (no change)
[18:07] <JFo> Jaunty bugs will be closed and removed from this list once Jaunty EOLs
[18:07] <JFo> ..
[18:07] <bjf> i didn't notice any comments regarding my email about most of the new bugs are "kerneloops" generated
[18:07] <JFo> ah, I meant to respond to that
[18:07]  * cking will attend to that at some point
[18:07] <JFo> Colin and I are working to enhance my knowledge on oopses
[18:07] <JFo> so there will be more coming on that front
[18:07] <JFo> ..
[18:08] <JFo> oh
[18:08] <JFo> speaking of kerneloops
[18:08] <JFo> ogasawara, is there some point when I need to ask to have oopses turned back off?
[18:08] <bjf> yes?
[18:09] <JFo> I can follow up on that offline
[18:09] <ogasawara> JFo: usually they'll turn it off when we release, but it wouldn't hurt to remind them
[18:09] <JFo> sorry bjf
[18:09] <JFo> ogasawara, will do
[18:09] <JFo> ..
[18:09] <bjf> JFo, np, that's why we're here
[18:09] <bjf> [TOPIC] Incoming Bugs: Bug day report (JFo)
[18:09] <MootBot> New Topic:  Incoming Bugs: Bug day report (JFo)
[18:10] <JFo> I've put off the bug day till next week due to the past week of traveling. The next Kernel Community Bug Day will be on bugs in the New status improperly.
[18:10] <JFo> There are curently about 1500 bugs in the New state.
[18:10] <JFo> My guess is that many of these are the result of people simply marking Expired bugs to new without doing the requested tasks.
[18:10] <JFo> The majority should move to Invalid or Triaged depending on the reporters interaction.
[18:10] <JFo> We will continue to have the Team Bug Day to address the Top 50 list as half days on Friday and Monday unless someone has an objection.
[18:10] <JFo> Reviewers, please take a look at your needs-review lists and help us keep the process moving. There are several lists that are not getting a look.
[18:10] <JFo> Please also take ownership of your bugs as you work them so we can get them fixed or otherwise off the list. There are a number in need of love.
[18:10] <JFo> There are several subsystems owned by all that need to be reviewed for inclusion in our top 50 list.
[18:10] <JFo> ..
[18:11] <bjf> why are we seeing the "New" graph going up but not the "Triaged"?
[18:11] <bjf> shouldn't our scripts be moving more bugs to "Triaged"?
[18:11] <JFo> I think mainly due to the habit of people to change bugs to new when they are expired
[18:11] <JFo> bjf, they do but we are only getting to a few due to these improper new bugs
[18:12] <JFo> so the scripts aren't able to get to most of them
[18:12] <bjf> thanks
[18:12] <bjf> ..
[18:12] <JFo> ..
[18:12] <bjf> [TOPIC] Triage Status (JFo)
[18:12] <MootBot> New Topic:  Triage Status (JFo)
[18:12] <JFo> There was a surprising amount of attendance in the UHS Kernel Bugs talk and a  number of the participants were actively listening, so I hope this means that we will have some good buy in on the process form these folks should any of them come on board with hardware/kernel bugs.
[18:12] <JFo> Since I was traveling, I have not had the chance to interact with the community over the past week.
[18:12] <JFo> ..
[18:13] <bjf> [TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)
[18:13] <MootBot> New Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)
[18:13] <bjf> huh, well then ...
[18:13] <bjf> thanks everyone
[18:13] <bjf> #endmeeting
[18:13] <MootBot> Meeting finished at 12:13.
[18:13] <JFo> thanks bjf
[18:13] <kamal> thanks bjf
[18:14] <sconklin> thanks
[18:14] <smb> bjf, ta
[18:14] <cking> thanks bjf
[18:14] <cking> sweet and short
[18:58] <zul> afternoon
[18:58] <hggdh> ~ô~
[18:58] <RoAkSoAx> o/
[18:59] <smoser> o/
[19:00] <mathiaz> o/
[19:00] <JamesPage> o/
[19:00] <ttx> \o
[19:00] <Daviey> -o-
[19:01] <RoAkSoAx> O_o
[19:01] <SpamapS> o/
[19:02] <ttx> waiting on chair (kirkland)
[19:02]  * kirkland is here, but not really here
[19:03] <ttx> smoser: can you take it ?
[19:03] <jiboumans> d'oh
[19:03] <hggdh> oh. kirkland has been replaced by a Turing machine
[19:03] <smoser> ugh. yes.
[19:03] <ttx> or Heisenberg cat
[19:03] <smoser> ok. /me is scribe.
[19:03] <Daviey> automata !
[19:04] <zul> or a drinking duck
[19:04] <smoser> how do i do this ?
[19:04] <smoser> doc on how to start meeting and commands and such ?
[19:04] <jiboumans> smoser: #startmeeting
[19:04] <smoser> #startmeeting
[19:04] <MootBot> Meeting started at 13:04. The chair is smoser.
[19:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:04] <ttx> and #topic
[19:05] <smoser> #topic Review ACTION points from previous meeting
[19:05] <ttx> hmm, I mean [TOPIC] and [ACTION]
[19:05] <ttx> sorry
[19:05] <smoser> [TOPIC] Review ACTION points from previous meeting
[19:05] <MootBot> New Topic:  Review ACTION points from previous meeting
[19:05] <smoser>  * jib to check with kim0 if he can attend meetings regularly ro not
[19:06] <kim0> I can
[19:06] <jiboumans> smoser: that was done already last meeting though :)
[19:06] <jiboumans> and tada, there he is!
[19:06] <kim0> lol
[19:06] <smoser> pfft
[19:06] <smoser>  * ttx to add link to server-mrs tag search from the releasestatus wiki page
[19:06] <ttx> done
[19:06] <smoser>  * SpamapS to look at the state of drizzle in maverick - if it build this week ScottK to accept FFe
[19:07] <smoser> SpamapS, ^
[19:07] <SpamapS> sorry
[19:07] <SpamapS> still not great
[19:07] <SpamapS> It builds
[19:07] <SpamapS> and tests ok
[19:08] <SpamapS> but there are copyright ambiguities that have prevented it from passing ftp master approval in sid
[19:08] <SpamapS> I THINK we have addressed them all now
[19:08] <SpamapS> But, the state is currently "maybe".
[19:08] <smoser> so we're still hoping for something in maverick ? i would have thought we were passed any reasonable freeze date.
[19:09] <SpamapS> Given that it is completely broken for i386, and a VERY old build, ScottK's willing to sponsor the exception as long as it hits debian first.
[19:09] <ttx> smoser: it's in universe
[19:09] <ttx> smoser: so it doesn't affect any release deliverable
[19:10] <Daviey> SpamapS, I thought he said that deal was only good for last week?
[19:10] <smoser> ah. ok.
[19:10] <ttx> smoser: but still.
[19:10] <SpamapS> Daviey: indeed, for "1 week".. so today is the end of that.
[19:10] <Daviey> lol
[19:10] <SpamapS> We're going to keep pushing and get it into sid.
[19:11] <smoser> ok. i think this is marked as "not going to happen" for maverick
[19:11] <mathiaz> SpamapS: you can probably get it accepted until the archive is also frozen for universe
[19:11] <SpamapS> If that takes 3 more days, then it will probably have to be broken in maverick. :-/
[19:11] <mathiaz> SpamapS: should be it removed instead?
[19:11] <SpamapS> mathiaz: probably. Its an alpha version now.. the beta, which is releasing pretty much as we speak, is quite different.
[19:12] <SpamapS> and guarantees on disk and API compatibility with future releases
[19:12] <SpamapS> first time drizzle has ever done that.
[19:13] <ttx> SpamapS: do your best. I can live with or without it
[19:13] <SpamapS> anyway, state of the action item is that the status in maverick is still broken, and that we are pushing quite hard to get it done and into maverick before the archive is frozen.
[19:13] <SpamapS> Its more important to drizzle than it is to us IMO.
[19:13] <smoser> [ACTION] SpamapS to chase drizzle in maverick decide between "broken" and "removed" with slight possibility of "beta"
[19:13] <MootBot> ACTION received:  SpamapS to chase drizzle in maverick decide between "broken" and "removed" with slight possibility of "beta"
[19:13] <smoser> reasonable ^ ?
[19:13] <SpamapS> quite, thanks.
[19:13] <smoser> moving on
[19:13] <smoser>  * jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas
[19:14] <jiboumans> i assumed we had that as part of the minutes actually
[19:14] <jiboumans> but thinking about it, a seperate call is probably a good idea
[19:14] <jiboumans> so, not done, but will do - carry over
[19:14] <smoser> [ACTION] jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas
[19:14] <MootBot> ACTION received:  jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas
[19:14] <smoser>  * mathiaz to send out a call for ideas on ubuntu to the puppet community
[19:14] <smoser> [
[19:15] <mathiaz> smoser: not done - carry over
[19:15] <smoser> [ACTION] (carryover) mathiaz to send out a call for ideas on ubuntu to the puppet community
[19:15] <MootBot> ACTION received:  (carryover) mathiaz to send out a call for ideas on ubuntu to the puppet community
[19:15] <smoser> ok. moving on.
[19:15] <smoser> [TOPIC] Maverick development (jib)
[19:15] <MootBot> New Topic:  Maverick development (jib)
[19:15] <jiboumans> With RC this Thursday, the main focus is the nail any critical bugs; daily triage is *essential* at this point (remember to update your work items!). At RC time, ISO testing, ISO testing and maybe some more ISO testing :) It's time to shake out the last snags so we can ship a release we can be really proud of. For those not on the release path, Friday and onwards will allow you to focus on Natty proposals if there are no critical bugs; the idea
[19:15] <jiboumans> pool is already filling up nicely and the time to put some meat in those ideas is next week.
[19:16] <jiboumans> our goal is to have a solid idea list by friday for Natty, and some real meat to those ideas by next friday
[19:16] <jiboumans> that will serve as the input for UDS sessions
[19:16] <jiboumans> as mentioned, I'll mail this out in a post to the mailing list as well
[19:16] <smoser> Where do list items go ?
[19:17] <jiboumans> https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool # add your ideas here
[19:17] <jiboumans> and thanks to all who already contributed
[19:17] <smoser> gracias.
[19:17] <SpamapS> I know jorge put out an email/video on what to do.. but I haven't really had any time to devote to it. We need to have all of our ideas in the list by Friday?
[19:17] <ttx> I sorted it, somehow
[19:17] <SpamapS> oh thats something different?
[19:17] <ttx> SpamapS: the list is more for brainstorming/awareness
[19:17] <jiboumans> spamaps: this is the idea pool and just that - thinks worth exploring
[19:18] <jiboumans> the exploration to happen next week
[19:18] <SpamapS> 10-4
[19:18] <jiboumans> that's it for Maverick I think, and also with Natty ramp up
[19:18] <smoser> [TOPIC] RC release status (ttx)
[19:18] <MootBot> New Topic:  RC release status (ttx)
[19:19] <ttx> I think jiboumans summed it well... No more milestoned bugs
[19:19] <ttx> On high/critical maverick bug, a placeholder about eucalyptus upgrade issues
[19:19] <Daviey> (fix being tested)
[19:19] <ttx> ack
[19:19] <smoser> [TOPIC] The road to 10.10.10 release (ttx)
[19:19] <MootBot> New Topic:  The road to 10.10.10 release (ttx)
[19:19] <ttx> So, the current step is ISO testing
[19:19] <ttx> we have candidates up
[19:20] <ttx> That can start now
[19:20] <ttx> Daily triage is particularly important right now... since we are at that tiny window where we can still consider fixing a high-impact issue that comes up
[19:20] <ttx> so please have it covered, and let me know if you catch something
[19:21] <smoser> ec2 image candidates will arrive later today.  We're waiting on a fix for 649833
[19:21] <smoser> bug 649833
[19:21] <ttx> The closer we get to release... the less likely we are to introduce a fix
[19:21] <ttx> At that point I'd say only high bugs are worthy of a fix... though low-impact med/low can make it as well
[19:21] <ttx> I advise that everyone goes through peer review before submitting to the release team
[19:22] <ttx> As a reminder, I'm at a conference Thursday and Friday
[19:22] <ttx> and traveling for a few hours on Wednesday
[19:22] <ttx> Daviey and mathiaz will cover for release stuff
[19:22] <Daviey> ack
[19:22] <ttx> and smoser will cover for cloud images release stuff
[19:22] <smoser> moving on ?
[19:23] <ttx> i'll be in London for the release sprint next week, from Wed to sunday.
[19:23] <ttx> (if need be)
[19:23] <ttx> the goal is to have the server ISO ready to ship by Friday, so that nobody has to stay up for the weekend
[19:23] <ttx> EOF
[19:23] <smoser> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[19:23] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[19:23] <hggdh> hi
[19:23] <ttx> questions > #ubuntu-server, I guess
[19:24] <hggdh> The only news is euca testing keeps on
[19:24] <hggdh> oh
[19:24] <hggdh> one thing: we (QA) just sent an email to -dev proposing a change on the usage of the 'regression-*' tags
[19:24] <hggdh> comments are appreciated
[19:25] <Daviey> hggdh, I possibly won't need you to test lucid -> maverick before approaching the release team.  I've done 2 upgrades here.. so i feel comfortable with pushing it for release.  Once it's in the archive (hopefully), normal testing then is appreciated :)
[19:25] <smoser> woohoo Daviey !
[19:25] <hggdh> Daviey: roj. Since I am already on Lucid, I will wait for it to hit the archives, and will do an upgrade, just in case
[19:26] <ttx> Daviey: be happy until next test !
[19:26] <Daviey> lol
[19:26] <smoser> moving on.
[19:26] <smoser> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:26] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:27] <smoser> jjohansen, ^
[19:27] <smoser>  * bug 613083 is fixed in my testing (both in maverick and in lucid tests for the 20100923 refresh of 10.04)
[19:28] <smoser> (that bug was regarding user data being corrupted)
[19:28] <ttx> is it released, or will be released as a 0-day SRU ?
[19:29] <smoser> its fixed (on amazons side)
[19:29] <smoser> no changes required, it works fine now.
[19:29] <smoser> Other kernel bugs of interest:
[19:30] <smoser>  * bug 613273 has been popping up in maverick instances occasionally.
[19:30] <smoser>  * bug 634487 is still present, we're getting some help from amazon on that, but have not made any real progress, jjohansen should be looking at it some also.
[19:31] <smoser> jjohansen, apparently is not here, so i will stop talking to myself.
[19:31] <smoser> Those are the maverick bugs related to uec images.
[19:31] <jjohansen> I'm here the lag is just bad
[19:31] <smoser> :)
[19:32] <jjohansen> I have multiple conversations running atm
[19:32] <smoser> in SRU news, our metabug friend bug 574910 is expected to move into -proposed this week.
[19:33] <ttx> smoser: maybe mark the bug fixed if there is nothing else to do
[19:33] <smoser> i was just doing that, ttx.
[19:33]  * SpamapS always imagines a GIANT beetle stomping on the city when he hears the term "metabug"
[19:33] <ttx> SpamapS: that's about a right description
[19:35] <smoser> jjohansen, can you confirm that out side of kitten killers we're basically frozen for kernel release.
[19:35] <jjohansen> yes
[19:35] <jjohansen> there will be a 0 day kernel update that we are queuing fixes for
[19:35] <smoser> the bugs above will have to be addressed in -updates.  The good part of it is, that they *can* be addressed in updates, and with an 'apt-get dist-upgrade'.
[19:35] <smoser> woowhoo for pv-grub.
[19:36] <jiboumans> woohoo indeed
[19:36] <jiboumans> smoser++ jjohansen++
[19:36] <smoser> i'm done here. jjohansen anything else?
[19:36] <kim0> so ec2 users can now upgrade their kernels ? :)
[19:36] <smoser> kim0, yes.
[19:36] <kim0> yaay
[19:36] <Daviey> \o/
[19:36] <jjohansen> if they use ebs
[19:36] <Daviey> awesome
[19:36] <ttx> kim0: that's one of the biggest features in maverick :)
[19:36] <smoser> they could in lucid with ebs.
[19:36] <kim0> indeed
[19:37] <smoser> on maverick, instance store and ebs just require reboot
[19:37] <smoser> something to chase at some point is to see if we can't get ksplice to support -virtual kernel
[19:37] <smoser> which would then get us security patches without even reboot on ec2 or uec
[19:37] <smoser> anyway.
[19:38] <zul> thats a big if
[19:38]  * SpamapS grabs the reigns on smoser's pony..  WHOA THERE
[19:38] <smoser> (one really nice affect of us using -virtual on ec2 is that the above is more likely)
[19:38] <smoser> anyway
[19:38] <smoser> narwhals, narwhals
[19:38] <smoser> moving on
[19:38] <smoser> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[19:38] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[19:39] <smoser> sommer, ^
[19:39] <sommer> nothing new from me
[19:40] <sommer> was there questions from anyone?
[19:40] <smoser> [TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[19:40] <MootBot> New Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[19:41] <kim0> hey folks
[19:41] <kim0> This week we're collecting feedback this week from "newcomer" Ubuntu server community
[19:41] <kim0> The goal being to understand if we're doing a good job accepting new community members, availing helpful data, things to work on, and guidance along the path
[19:41] <kim0> I actually received pings from a dozen people who want to contribute, which is awesome, I hope to follow up with them after we're done with this survey thing this week
[19:41] <kim0> Also, another thing, I would like to start collecting feedback on the next version of the cloud portal. If anyone has ideas on what should go there during 11.04 cycle please throw me a few lines
[19:42] <kim0> that should generally be it for me
[19:42] <mathiaz> kim0: where is the cloud portal now?
[19:42] <kim0> mathiaz: at IS for deploy
[19:42] <kim0> stuck mostly
[19:42] <kim0> :)
[19:42] <smoser> it will grace us with its presence at cloud.ubuntu.com ?
[19:42] <kim0> I hope to have it up around 10.10
[19:42] <kim0> smoser: that's the plan
[19:42]  * mathiaz thinks it may hard to provide feedback on something that isn't accessible yet
[19:43] <smoser> mathiaz, you need to think outside the box man
[19:43] <kim0> :)
[19:43] <kim0> sorry for that .. should be up soon though
[19:43] <smoser> kim0, table showing latest AMIs
[19:43] <kim0> smoser: yes there now
[19:43] <smoser> awesome.
[19:43] <Daviey> \o/
[19:44] <smoser> ok. if no one has anything else for kim0 then we're going on.
[19:44] <smoser> [TOPIC] Open Discussion
[19:44] <MootBot> New Topic:  Open Discussion
[19:44] <zul> i like turtles
[19:44] <SpamapS> me too
[19:44] <smoser>  * narwhals, narwhals
[19:45] <RoAkSoAx> lol
[19:45] <SpamapS> Did anybody have a chance to look at the solution I proposed for the SSL passphrase dialog in plymouth?
[19:45] <Daviey> i thought ttx did?
[19:45] <smoser> SpamapS, link ?
[19:45] <zul> ttx did
[19:45] <SpamapS> bug 582963
[19:45] <zul> and defered it to natty
[19:45] <ttx> SpamapS: I looked at it from an impact perspective -- didn't test it
[19:45] <SpamapS> yeah, Just wondering if anybody cared to comment. ;)
[19:46] <ttx> SpamapS: I commented :P
[19:46] <SpamapS> ttx: oh you always have SOMETHING to say don't you? ;)
[19:46] <ttx> SpamapS: yes
[19:47] <kim0> mathiaz: smoser append "217.139.24.3 kimos.com" to /etc/hosts and visit kimos.com my dev box,
[19:47] <RoAkSoAx> i have a tropical depression coming tomorrow (hopefully it wont turn into a hurricane) :(
[19:48] <ttx> don't tell me next UDS is in Florida
[19:48] <smoser> Walt will protect us.
[19:48] <Daviey> That is a mickey mouse idea smoser
[19:48] <ttx> smoser: not sure, he never put a narwhal in his movies
[19:48] <SpamapS> ttx: its ok, Hurricane season is over 1 week before UDS
[19:48] <ttx> maybe he just hates them.
[19:49] <smoser> ok.
[19:49] <ttx> anyway, Florida looks less dangerous than Texas
[19:49] <smoser> i'm calling it
[19:49] <RoAkSoAx> i'm in a worse danger area than orlando though lol, so Orlando should be good for UDS, dont get scared ttx :P
[19:50] <Daviey> smoser, next meeting?
[19:50] <smoser> oops
[19:50] <jiboumans> smoser: when done, #endmeeting
[19:50] <Daviey> rinse and repeat
[19:50] <SpamapS> announce next time
[19:50] <SpamapS> then end
[19:50] <SpamapS> then \o/
[19:50] <smoser> next meeting:
[19:50] <smoser> Tuesday 2010-10-05 at 1800 UTC - #ubuntu-meeting
[19:51] <smoser> #endmeeting
[19:51] <MootBot> Meeting finished at 13:51.
[19:51] <ttx> smoser: many thanks for covering up
[19:51] <Daviey> yeah... usually not wearing clothes is not cool.
[19:51] <JFo> twitch*
[19:51] <smoser> if its ok for mickey its ok for me
[19:51] <hggdh> oh, TMI, TMI...
[19:52] <RoAkSoAx> mickey is evil
[19:52] <RoAkSoAx> lol
[19:52] <smoser> now. everyone go to : http://www.weebls-stuff.com/songs/Narwhals/