[10:51] <happyaron> Will Asia Oceania board meeting start in 10 minutes?
[10:51] <Vantrax> yes
[10:51] <happyaron> thx
[10:53] <ZachK_> good morning all
[10:54] <BasicXP> morning
[10:54] <ZachK_> BasicXP: ah hello
[10:55] <Vantrax> who do we have from the board here?
[10:55] <malamut> me I think)
[10:56] <Vantrax> not for the board to evaluate, members of the board
[10:56] <malamut> o! Then like previos meeting - nobody))
[10:57] <malamut> I hope it isn't so...
[10:57] <Vantrax> me too malamut
[10:57]  * ZachK_ hopes the board will show
[10:57] <happyaron> how many board member is required?
[10:58] <happyaron> freeflying: ping, needs board member to start meeting, :)
[10:59] <Vantrax> not so much to start, just need a few more to vote on anythin
[11:00]  * elky looks at the page and tilts head
[11:00] <elky> Am I reading that right?
[11:00] <Vantrax> readin what right?
[11:00] <elky> looked at the applicant list?
[11:00] <Vantrax> yer
[11:00] <freeflying> hi
[11:01] <Vantrax> we have a few
[11:01] <ajmitch> elky: there aren't that many :)
[11:01] <elky> Recognise any names?
[11:01] <Vantrax> we may as well get started
[11:01] <Vantrax> I do
[11:01] <Vantrax>  one BIG name
[11:01] <ajmitch> not at all...
[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:01] <freeflying> elky: can we do vote today?
[11:01] <Vantrax> sound off for the board, who do we have?
[11:02] <elky> o/
[11:02] <freeflying> I saw a lot applicants on the list
[11:03] <ZachK_> four of the applicants don't seem to be here.....yet
[11:03] <malamut> hmm, sorry, I have some problems with english, but I'm here))
[11:03] <happyaron> ZachK_: well, Destine and you are here, :)
[11:03] <ZachK_> check that...only three arn't
[11:03] <Destine> I am～
[11:04] <elky> one can probably be summoned by twitter...
[11:04] <ZachK_> ah Destine you are indeed...missed you entirely
[11:04] <Vantrax> lets give it a few more minutes for a few more to come in
[11:04] <Vantrax> amachu is away today
[11:04] <elky> do we have quorum though?
[11:04] <Vantrax> not yet
[11:04] <ajmitch> lifeless may be lurking around still
[11:04] <Vantrax> im pretty sure its still 4 for quorum
[11:05] <elky> lifeless: hello?
[11:06] <Vantrax> can other board memebers count for quorum?
[11:06] <elky> yes
[11:06] <elky> we've done it numerous times
[11:06] <Vantrax> good paultag gives us one more
[11:07]  * ZachK_ hands paultag a cup o' java
[11:07] <paultag> Are we talking about ZachK_'s membership?
[11:07] <Vantrax> okies then
[11:07] <Vantrax> paultag: were still making quorum, now that your here too we have enough
[11:07] <Vantrax> i think...
[11:07] <elky> paultag, I dunno, is he being bribed with that cuppa? ;)
[11:07] <paultag> elky, >:D
[11:08]  * ZachK_ doesn't bribe.....ever
[11:08]  * ZachK_ was just being a good friend....
[11:08] <paultag> Hey, I'll take a coffee bribe any day
[11:08] <ZachK_> :D
[11:09] <Vantrax> ajmitch: your on one of the other boards arent you?
[11:09] <ajmitch> Vantrax: no
[11:09] <elky> Vantrax, he's a professional lurk.
[11:09] <ajmitch> used to be on motu council way back, but no longer :)
[11:09] <Vantrax> yeah, i thought that was the case
[11:09] <Vantrax> boo:P
[11:09] <ajmitch> sorry
[11:09] <Vantrax> still one short then
[11:09]  * ajmitch just looked at IRC at the wrong time
[11:10] <elky> Vantrax, eh? you, me, freeflying, paultag?
[11:10] <Vantrax> oh yeah, freeflying >.<
[11:10] <Vantrax> my bad
[11:10] <paultag> :)
[11:10] <Vantrax> okies who was first Nasir Khan Saikat you around
[11:11] <elky> not in the channel according to the nick he registered
[11:11] <Vantrax> nope
[11:11] <Vantrax> I know malamut is here
[11:11] <elky> malamut is though
[11:11] <malamut> yes
[11:11] <elky> and we're already 10 mins in
[11:11] <ZachK_> all hail malamut!
[11:11] <Vantrax> Malamut your up, give us your intro
[11:12] <malamut> well, at fist sorry for my english...
[11:14] <Vantrax> long as we can understand the english, its all fine. If not we can always ask for clarification. Give us a short intro on what you do in the Ubuntu community and why we should approve you for membership
[11:14] <malamut> I'm a one of active members of Russian Ubuntu Community. I live in Saint-Petersburg, Russia, work system administrator. I've helped users with Ubuntu since 7.10, now I try to garthe russian dokumentation on single site - help.ubuntu.ru
[11:15] <malamut> I'm an author of Russian Ubuntu Guide also
[11:15] <jdub> (hello, apologies for almost missing the meeting -- thanks to elky for poking me)
[11:15] <malamut> https://launchpad.net/ubuntu-russian-guide
[11:15] <Vantrax> You run that whole site malamut?
[11:16] <Vantrax> [LINK] https://launchpad.net/ubuntu-russian-guide
[11:16] <MootBot> LINK received:  https://launchpad.net/ubuntu-russian-guide
[11:16] <malamut> Well, I'm a leder of Wiki team. And also help with DokuWiki and some technical questions
[11:17] <malamut> and I've made all structure, rules etc for this resource
[11:17] <malamut> help.ubuntu.ru
[11:17] <ZachK_> very nice work my man
[11:17] <Vantrax> Questions anyone? Still working out google translate:P?
[11:18] <ZachK_> I'm reading the lp page right now translated to english via google chrome's translator
[11:18] <Vantrax> Happy to vote?
[11:18] <elky> Vantrax, not yet
[11:18] <malamut> there is on-line version of guide at http://help.ubuntu.ru/manual
[11:19] <elky> malamut, do you have much to do with the IRC channel for the team?
[11:20] <malamut> no, I don't use IRC, I only helps peoples at russian ubuntu forum
[11:20] <elky> malamut, ah ok then. No further question from me.
[11:21] <elky> Vantrax, ready when you are.
[11:21] <wzssyqa> malamut: no more works to show us>
[11:21] <elky> Is anyone here to cheer for malamut?
[11:21] <malamut> well, all is on my wiki page. I think, I've said about major
[11:22] <Vantrax> everyone happy to vote?
[11:22] <freeflying> +1
[11:23] <elky> Yep. Want to prod the bot?
[11:23] <Vantrax> [VOTE]
[11:23] <MootBot> Please vote on: .
[11:23] <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:23] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[11:23] <Vantrax> bah
[11:23] <elky> +1
[11:23] <MootBot> +1 received from elky. 1 for, 0 against. 0 have abstained. Count is now 1
[11:23] <Vantrax> +1
[11:23] <MootBot> +1 received from Vantrax. 2 for, 0 against. 0 have abstained. Count is now 2
[11:23] <Vantrax> <make that vote on malamut for membership>
[11:24]  * Vantrax prods people to vote
[11:24] <BasicXP> should I vote?
[11:24] <Vantrax> only if your on an RMB
[11:24] <freeflying> +1
[11:24] <MootBot> +1 received from freeflying. 3 for, 0 against. 0 have abstained. Count is now 3
[11:25] <freeflying> again
[11:25] <BasicXP> oh ok, not me :)
[11:25] <freeflying> :)
[11:25] <elky> paultag?
[11:25] <paultag> Howdy
[11:25] <paultag> Oh
[11:25] <paultag> +1
[11:25] <MootBot> +1 received from paultag. 4 for, 0 against. 0 have abstained. Count is now 4
[11:25] <elky> malamut, congratulations.
[11:25] <Vantrax> [ENDVOTE]
[11:25] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[11:25] <freeflying> MootBot: congrats
[11:25] <malamut> thank you!
[11:26] <paultag> malamut, well done :)
[11:26] <happyaron> malamut: congrats!
[11:26] <paultag> malamut, 'grats
[11:26] <Agafonov> malamut: \o/
[11:26] <Destine> malamut, congrats
[11:26] <Vantrax> Okies jdub... give us the short version:P
[11:26] <jdub> good morning
[11:26] <takdir> sorry i'm late :(
[11:26] <jdub> i'm renewing, so not sure how detailed this needs to be :-)
[11:26] <jdub> salient details on the wiki page of course
[11:26] <elky> jdub, aww... only "good morning" now?
[11:27] <ajmitch> no freedom lovers here?
[11:27]  * elky ^5's ajmitch
[11:27] <ZachK_> lol
[11:27] <Vantrax> personally im ready to vote, but...
[11:27] <jdub> i'm mostly renewing because i started a new blog about the devel branch
[11:27] <elky> jdub, we can just turn this in to a pick on jdub meeting if you like :D
[11:27] <freeflying> its remind us maybe we shall have a renew process
[11:28] <ajmitch> jdub: it's a nice summary of changes you're doing there :)
[11:28] <jdub> and have been enjoying my ppa enough that i should really start pushing those somewhere more useful ;-)
[11:29] <jdub> am i missing anything that should be covered?
[11:29] <elky> You still haven't finished your greeting.
[11:29] <Vantrax> unless someone has an objection... ill start the vote, paultag has a time constraint
[11:30] <elky> Vantrax, go for it.
[11:30] <Vantrax> [VOTE] jdub for membership renewal
[11:30] <MootBot> Please vote on:  jdub for membership renewal.
[11:30] <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:30] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[11:30] <elky> +1
[11:30] <MootBot> +1 received from elky. 1 for, 0 against. 0 have abstained. Count is now 1
[11:30] <Vantrax> +1
[11:30] <MootBot> +1 received from Vantrax. 2 for, 0 against. 0 have abstained. Count is now 2
[11:30] <freeflying> +1
[11:30] <MootBot> +1 received from freeflying. 3 for, 0 against. 0 have abstained. Count is now 3
[11:30] <takdir> +1
[11:30] <MootBot> +1 received from takdir. 4 for, 0 against. 0 have abstained. Count is now 4
[11:30] <freeflying> jdub: welcome back :)
[11:30] <jdub> thanks everyone :-)
[11:30] <elky> oh, we have a 5th here now, we don't need paultag anymore.
[11:31] <happyaron> jdub: :)
[11:31] <Vantrax> [ENDVOTE]
[11:31] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[11:31] <elky> jdub, welcome back dude.
[11:31] <Vantrax> Woo, thanks for staying paultag
[11:31] <Vantrax> welcome back jdub
[11:31] <Vantrax> Destine you still idling here?
[11:32] <ajmitch> jdub: welcome back
[11:32] <Destine> yes
[11:32] <Destine> Hi, good evening from China.
[11:32] <Destine> I am Eleanor Chen, and I am one of the leading members in Ubuntu China LoCo
[11:33] <Destine> Most of my contributions are in the field of l10n and loco event.
[11:33] <Destine> please refer to my wiki:https://wiki.ubuntu.com/EleanorChen
[11:33] <Vantrax> Great testimonials btw
[11:34] <Destine> i hosted the Ubuntu 10.04 LTS Release Party in Beijing China few weeks ago
[11:34] <Destine> Vantrax, thx.
[11:35] <Destine> also, i translated and rewrote the Ubuntu Desktop Course's Chinese Edition
[11:35] <Destine> I have done a lot of promotions since i was in senior high.
[11:35] <Vantrax> Questions?
[11:37] <elky> None from me.
[11:37] <Vantrax> What do you plan on doing after getting Ubuntu membership, what do you want your future involvment in Ubuntu to be?
[11:37] <Destine> Vantrax, since i am a girl, my first concern would be try to promote it among women.
[11:38] <Vantrax> are you a member of Ubuntu Women?
[11:38] <Destine> Vantrax, in Launchpad, yes.
[11:38] <elky> Destine, \o/
[11:38] <Vantrax> involved with them at all? or still getting started
[11:39] <Destine> Vantrax, getting started, i need sometime to do prepare work for starting it in China.
[11:39] <Vantrax> We can point you in the right direction
[11:40] <Vantrax> Unless there are any other questions, lets vote
[11:40] <Destine> Vantrax, thx.
[11:40] <Destine> :)
[11:40] <Vantrax> imo elky and pleia2 are good places to start talking about that, elky would have a better idea:P
[11:41] <Vantrax> [VOTE] Destine for Ubuntu Membership
[11:41] <MootBot> Please vote on:  Destine for Ubuntu Membership.
[11:41] <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:41] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[11:41] <ZachK_> Vantrax: dont' forget akgraner as she's part of that too
[11:41] <takdir> Destine have a good wiki and testimonial too
[11:41] <Vantrax> +1
[11:41] <MootBot> +1 received from Vantrax. 1 for, 0 against. 0 have abstained. Count is now 1
[11:41] <elky> +1
[11:41] <MootBot> +1 received from elky. 2 for, 0 against. 0 have abstained. Count is now 2
[11:41] <freeflying> +1
[11:41] <MootBot> +1 received from freeflying. 3 for, 0 against. 0 have abstained. Count is now 3
[11:41] <takdir> +1
[11:41] <MootBot> +1 received from takdir. 4 for, 0 against. 0 have abstained. Count is now 4
[11:41] <Vantrax> [ENDVOTE]
[11:41] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[11:41] <freeflying> Destine: congrats
[11:42] <Vantrax> Well done Destine
[11:42] <happyaron> Destine: congrat!
[11:42] <ZachK_> congrats Destine
[11:42] <wzssyqa> congrat!
[11:42] <Destine> Thank you.
[11:42] <Destine> Thank you all.
[11:42] <Vantrax> Ok, ZachK_ thanks for waiting patiently. Your up
[11:42] <ZachK_> Vantrax: thanks
[11:43] <ZachK_> Ok Zach is the name...started using Ubuntu when 8.04 was still Beta...had no idea what to do or where to get started so I looked into the Ubuntu Beginners Team
[11:43] <ZachK_> I've now been part of that team for almost a year and since that time I've become a mentor for that team, I lead a Wiki Team, and I have been working with the Ubuntu Weekly News project
[11:44] <ZachK_> https://wiki.ubuntu.com/ZachK_ is my wiki page which will list more of what i do...
[11:44] <ZachK_> I also do a lot of IRC...helping in the #Ubuntu channel as well as the BT channels, and i try to hit the forums as much as possible
[11:45]  * ZachK_ is open to any and all questions
[11:45] <Vantrax> Whats next for you?
[11:46] <ZachK_> Well my future goals are to continue helping the new users to linux...I also want to learn how to code using Python/Java and I aim to learn how to Triage Bugs on Launchapd
[11:46] <ZachK_> "Launchpad
[11:47] <ZachK_> Figured if I am really good at the Wiki/Doc markup python is a logical step forward...plus python is just cool
[11:48] <Vantrax> Anyone here to cheer for ZachK_
[11:49]  * kermiac cheers for ZachK_
[11:49] <kermiac> he does some awesome work in the UB Team
[11:49] <Vantrax> paultag was unable to stay but he sent this to me earlier: <paultag> Vantrax, I endorse ZachK_'s work on the UBT ( Ubuntu Beginners Team ) totally. He has shown real drive and motivation with regards to leading our Wiki team. I thought for sure that ZachK_ would have quit the team in the first month. I tend to see a lot of people who are "over-motivated", and they don't last long. ZachK_ proved me wrong. I was 100% off
[11:49] <Vantrax> base, and I had no idea that drive was just they way ZachK_ works.
[11:49] <Vantrax> Ill add my own endorsement to that from watchin him grow as part of the team over the last eyar
[11:50] <ZachK_> thanks Vantrax
[11:50] <ZachK_> my wiki page also lists testimonials from the likes of akgraner and joeb454 also swoody
[11:51] <Vantrax> Anyone else have a question for ZachK_ or ready to vote
[11:51] <elky> bring on the votes
[11:51] <Vantrax> [VOTE] ZachK_ for Ubuntu Membership
[11:51] <MootBot> Please vote on:  ZachK_ for Ubuntu Membership.
[11:51] <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:51] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[11:51] <Vantrax> +1
[11:51] <MootBot> +1 received from Vantrax. 1 for, 0 against. 0 have abstained. Count is now 1
[11:51] <freeflying> +1
[11:51] <MootBot> +1 received from freeflying. 2 for, 0 against. 0 have abstained. Count is now 2
[11:52] <elky> +1
[11:52] <MootBot> +1 received from elky. 3 for, 0 against. 0 have abstained. Count is now 3
[11:52] <takdir> +1
[11:52] <MootBot> +1 received from takdir. 4 for, 0 against. 0 have abstained. Count is now 4
[11:52] <Vantrax> [ENDVOTE]
[11:52] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[11:52] <Vantrax> Well done ZachK_
[11:52] <kermiac> congratulations ZachK_!!
[11:53] <ZachK_> thanks very much all
[11:53] <Destine> ZachK_, congrats
[11:53] <Vantrax> congrats to everyone
[11:53] <ZachK_> thanks very much and congrats to the other new members
[11:53] <Vantrax> Email will go out to the news team tonight or tomorrow to let everyone know
[11:54]  * ejat sorry late join ...
[11:54] <elky> Vantrax, thanks for chairing
[11:54] <Vantrax> Okies last call for nasirkhan
[11:54] <ZachK_> he's not here
[11:54] <Vantrax> One last time, Amachu no longer has the time/will to be the Secretary for the board
[11:55] <elky> nickserv doesn't even know the nick, so...
[11:55] <Vantrax> er item not time
[11:55] <ZachK_> elky: sounds like he gave up maybe?
[11:55] <elky> ZachK_, it's not registered
[11:55] <ZachK_> elky: hmm
[11:55] <ZachK_> weird
[11:56] <Vantrax> I volunteered to take over, unless anyone has any objection or would like to do it?
[11:56] <ZachK_> Vantrax: what's the Secretarial duties?
[11:56] <Vantrax> you have to be on the board ZachK_:P
[11:56] <elky> Vantrax, you did a good job tonight, no objection here
[11:56] <ZachK_> oh
[11:56] <ibuclaw> o/ Vantrax
[11:56] <elky> Vantrax, you also have better connectivity than amachu :)
[11:56] <Vantrax> You add the new members, chair the meeting, and send out the emails
[11:56]  * ejat also no objection
[11:57]  * ZachK_ thinks Vantrax would be a great secretary
[11:57] <takdir> +1 for secretary :)
[11:57] <Destine> +1
[11:57] <freeflying> +1
[11:57] <Vantrax> okies, ill update the wiki page and get that email out.
[11:57] <ejat> +1
[11:58] <ZachK_> +1 for Vantrax secretary
[11:58] <freeflying> Vantrax: thx
[11:58] <Vantrax> thanks for coming everyone, grats again to all the new members
[11:58] <ejat> !ping jdub ..
[11:58] <Vantrax> #endmeeting
[11:58] <MootBot> Meeting finished at 05:58.
[11:58] <ZachK_> I do have a question...what about the factoid thing?
[11:58] <ZachK_> I mean hostname
[11:59] <elky> cloaks? you ask in #ubuntu-irc
[11:59] <ZachK_> ok
[12:00] <BasicXP> you guys reminded me to ask for a cloak too :) thx!
[12:00] <ZachK_> thanks elky...do i just say i'm now an ubuntu member? that seems kinda easy to claim
[12:00] <Vantrax> your email will take a little while
[12:00] <ZachK_> ok
[12:00] <Vantrax> ZachK_: your added to the group on launchpad, thats harder to fake
[12:00] <ZachK_> Vantrax: i got the Launchpad one so true
[12:00] <elky> ZachK_, launchpad will confirm for you, so show them your launchpad url
[12:00] <ejat> welcome back to jdub
[12:00] <Vantrax> your email will be whatever the launchpad login is
[12:00] <ZachK_> thanks again all
[12:00] <freeflying> Vantrax: so we done today?
[12:01] <Vantrax> yep, thats it
[12:01] <ZachK_> thanks all..
[12:01]  * ZachK_ out to do more wiki stuff
[12:01] <Vantrax> you are released to your beds, dinner, family, gaming... whatever:P
[12:01] <ZachK_> lol
[12:02] <jdub> thanks ejat
[12:03] <jdub> bye all
[12:04] <ejat> hmm .. jdub leave already .. still remember jdub bad experience when come to MY :( ..
[12:06] <elky> ejat, he's most responsive on twitter these days
[12:07] <ejat> yeah ...
[12:29] <lifeless> hi
[12:29] <lifeless> bah sorry guys, getting adjusted to the right sTZ :(
[13:49] <elky> lifeless, that's ok, we managed
[14:00] <NCommander> #startmeeting
[14:00] <MootBot> Meeting started at 08:00. The chair is NCommander.
[14:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:00] <NCommander> ping ogra, dyfet, GrueMaster,
[14:01] <mpoirier> o/ good morning.
[14:01] <NCommander> morning!
[14:01] <NCommander> morning GrueMaster
[14:01] <dyfet> morning
[14:01] <GrueMaster> meh
[14:01] <ogra> moo
[14:01] <ogra> hey mpoirier
[14:02] <mpoirier> hey ogra.
[14:02]  * NCommander suspects this is going tobe a short meeting
[14:02]  * ogra wonders if we get a link from NCommander
[14:02] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100608
[14:02] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100608
[14:02] <ogra> sweet
[14:02] <NCommander> [topic] Action Items from June 1th, 2010
[14:02] <MootBot> New Topic:  Action Items from June 1th, 2010
[14:03] <ogra> heh
[14:03] <NCommander> [topic]GrueMaster to assemble list on what SRU is going on with kernel team
[14:03] <MootBot> New Topic: GrueMaster to assemble list on what SRU is going on with kernel team
[14:03] <ogra> poor GrueMaster
[14:03] <ogra> werent there c/o's from the former meeting too ?
[14:03] <NCommander> yup
[14:03]  * ogra doesnt see them
[14:04] <GrueMaster> Just a sec.  Still loading my brain.
[14:04] <NCommander> ugh, we'll be here for awhile then  :-/
[14:04] <GrueMaster> Ok, on dove we have bug 509006.
[14:05] <GrueMaster> On imx51 we have bug 559065 and bug 571192.
[14:05] <ogra> NCommander, i see build-timeout discussion, and the linbnih/upstart issues on the c/o list but not on this weeks actions
[14:05] <NCommander> argh oops
[14:05] <ogra> (and response to davidms mail, but he's not here anyway)
[14:06] <ogra> i expect c/o's anyway for everything, but we should not lose them
[14:06] <ogra> GrueMaster, was the dsecond bug not depending on the first one ?
[14:06] <NCommander> ogra: fixed
[14:07] <ogra> thanks
[14:07] <NCommander> c/o on all three for me
[14:07] <ogra> indeed
[14:07] <ogra> no complaints
[14:07] <ogra> GrueMaster, were there no dove bugs ?
[14:07] <NCommander> [topic]  * NCommander to discuss build timeout with lamont
[14:07] <NCommander>  * NCommander to poke Keybuk on libnih
[14:07] <NCommander>  * Entire team to respond to davidm's email on meeting times
[14:07] <MootBot> New Topic:   * NCommander to discuss build timeout with lamont
[14:07] <GrueMaster> Not sure.  I do know that both bug 509006 and bug 559065 have tested patches that have not been released.
[14:07] <NCommander> oops
[14:07] <NCommander> [topic] Standing Items
[14:07] <MootBot> New Topic:  Standing Items
[14:08] <NCommander> [link] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:08] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:08] <ogra> we're above trend
[14:08] <ogra> we should do something about it :)
[14:08] <ogra> preferably before friday (release meeting)
[14:09] <ogra> we need to get 6-10 items done before that
[14:09] <NCommander> I'm blocked on cjwatson on subarch detection, but thats relatively quick to implement once he can review my design
[14:09] <ogra> to get below trend again
[14:09] <NCommander> ARM softbootloader remains the same as usual
[14:09] <ogra> NCommander, but you made a lot progress on image building
[14:09] <ogra> we should be able to close two to three items there
[14:10] <ogra> dyfet, how about you ? you have some very simple items on the imagebuilds without root spec
[14:10] <NCommander> ogra: not quite yet. post-boot-* stuff still isn't fully done.
[14:10] <ogra> NCommander, the missing bits are really trivial
[14:10] <ogra> should be doable before fri.
[14:10] <NCommander> ogra: ah, yes
[14:10] <GrueMaster> I'll see if I can't get a test plan into iso.tracker for the preinstalled-sd-card-images-for-omap bp this week.
[14:11] <ogra> i should be ready to provide a locally built image with jasper today or tomorrow
[14:11] <NCommander> GrueMaster: excellent
[14:11] <ogra> so you can play with something
[14:11] <GrueMaster> cool
[14:11] <ogra> the bad stuff about these images is that you have to dd them newly for each test
[14:11] <ogra> thats a bit time consuming
[14:12] <NCommander> [topic] Kernel Status (cooloney, mpoirier)
[14:12] <MootBot> New Topic:  Kernel Status (cooloney, mpoirier)
[14:12] <mpoirier> omap4 kernel ?
[14:12] <ogra> nah
[14:12] <ogra> we're waiting for TI on that one
[14:12] <ogra> ndec isnt here though
[14:12] <mpoirier> yes indeed.
[14:12] <NCommander> ogra: I pinged him on it
[14:12] <ogra> i know cooloney is working to integrate the panda patches into his PPA omap4 build
[14:13] <mpoirier> correct.
[14:13] <ogra> NCommander, did you mail him as requested (right after last meeting)
[14:13] <ogra> so he actually knows about the meeting
[14:14] <NCommander> ogra: I don't remember, although I remember talking to him on IRC
[14:14] <ogra> NCommander, please mail him *NOW*
[14:14] <ogra> so he can adjust for next week at least
[14:15] <ogra> mpoirier, we have one XM bug with the omap3 kernel
[14:15] <mpoirier> I'm currently fighting an SD card bug.
[14:15] <ogra> do you know who in the omap team on kernel side has an XM ?
[14:15]  * ogra thinks he remembers lag
[14:16] <ogra> and there are bugs with the metapackage
[14:16] <mpoirier> nop, no XM to the extent of my knowledge.
[14:16] <mpoirier> I'll double check though.
[14:16] <ogra> it still pulls in the lucid kernel
[14:16] <ogra> i need to file them :P
[14:16] <mpoirier> yes please.
[14:17]  * ogra thinks thats all for kernel given cooloney isnt here
[14:17] <NCommander> [topic] QA Status (GrueMaster)
[14:17] <MootBot> New Topic:  QA Status (GrueMaster)
[14:17] <ogra> i'll test our maverick omap3 kernel on the touchbook soon, but i dont expect it to actually work
[14:18] <ogra> i think we had QA above somehow :)
[14:18] <ogra> anything additionally GrueMaster ?
[14:18] <GrueMaster> Nothing to report here.  No new bugs that I have seen in the packages.
[14:18] <ogra> did you test maverick already ?
[14:18] <GrueMaster> Same old bugs still exist though.
[14:18] <ogra> i bet there are a ton :)
[14:18] <GrueMaster> Somewhat.  I am doing daily package updates.
[14:19] <ogra> wow, and nothing serious ?
[14:19] <GrueMaster> f-spot still crashes the same way, even though it has a new release.
[14:20] <ogra> pfft f-spot
[14:20] <ogra> afaik the desktop team plans to replace it ?
[14:20] <GrueMaster> I did not know that.
[14:20]  * ogra isnt sure thats a roumor though
[14:20] <ogra> ask them :)
[14:20] <ogra> -> #ubuntu-desktop is that way :)
[14:21] <GrueMaster> later, when I've had more caffeine.
[14:21] <ogra> not that we should stop caring about f-spot, but if they replace it i wont cry :)
[14:21] <ogra> NCommander, move ?
[14:21] <NCommander> [topic] ARM Porting/FTBFS status (NCommander, dyfet)
[14:22] <MootBot> New Topic:  ARM Porting/FTBFS status (NCommander, dyfet)
[14:22] <NCommander> (sorry, got a phone call I had to answer)
[14:22] <ogra> dyfet, any news ?
[14:22] <ogra> anything for us to sponsor
[14:23] <NCommander> (sorry, back, had to take this case)
[14:23] <NCommander> er
[14:23] <NCommander> call
[14:23] <ogra> thats fine
[14:24] <ogra> seems we lost dyfet
[14:25] <NCommander> [topic] ARM Image Status (ogra, NCommander)
[14:25] <MootBot> New Topic:  ARM Image Status (ogra, NCommander)
[14:25] <ogra> looks good :)
[14:25] <ogra> jasper doesnt though
[14:26] <NCommander> (sorry, back fully now, that was my vet)
[14:26] <ogra> but i think we should have images ready real soon
[14:26]  * ogra is trying to debug jasper atm, it does resize the partitions but not the filesystems for some reason
[14:27] <ogra> once thats done and once NCommander has finished the debian-cd scripts we should be good
[14:27] <ogra> there is a minor change to livecd-rootfs pending
[14:27] <ogra> thats all from me for images
[14:27] <ogra> NCommander, anything from you ?
[14:27] <NCommander> w.r.t. to d-cd code, its most there, with some last odds and evens, but its coming together
[14:28] <ogra> right
[14:28] <NCommander> and I'm going to turn my phone off whenever we have a meeting
[14:28] <ogra> we should have images by end of the week, latest start of next week
[14:28]  * NCommander knocks on wood
[14:28] <NCommander> [topic] Any Other Business
[14:28] <MootBot> New Topic:  Any Other Business
[14:28] <ogra> i'll be at LT from thu to sat so i probably cant merge the bits to make it this week
[14:29] <ogra> depends if we manage to land all pieces tomorrow
[14:29] <ogra> i have one organisational AOB for NCommander
[14:29]  * NCommander hides
[14:29] <ogra> the release meeting preparation meeting was somehow set to the same time we have a call on fridays
[14:30] <ogra> are you ok with moving it before that call ?
[14:30]  * NCommander looks at google cal
[14:30] <ogra> i dont want to prepare release reports during a customer call :)
[14:30] <NCommander> yeah, we can move that an hour back
[14:30] <ogra> great
[14:30]  * NCommander isn't thrilled at getting up early, but not a lot we can do
[14:31] <ogra> yeah, during call is surely bad
[14:31] <ogra> and the meeting is directly after the call
[14:31] <NCommander> ogra: ndec just got emailed
[14:31] <ogra> perfect
[14:31] <ogra> oh
[14:31] <NCommander> can I close it out?
[14:31] <ogra> one announcement !
[14:31] <NCommander> guess not
[14:31] <ogra> we are being renamed !
[14:31] <ogra> we're the "arm" team now
[14:31] <ogra> not mobile anymore
[14:32] <NCommander> Great. Now I just sent an email with the wrong team name in it
[14:32]  * NCommander headthunks
[14:32] <ogra> i'll walk through launchpad groups etc once david is back
[14:32] <ogra> lets keep mobile until david is back
[14:32] <ogra> it needs a lot organizational changes i suspect
[14:32] <NCommander> works for me.
[14:32] <ogra> also what do we do with #ubuntu-mobile ?
[14:33] <ogra> redirect it ?
[14:33] <ogra> leave it idling ?
[14:33]  * ogra wishes persia was here
[14:33] <NCommander> ogra: we won't have persia for another two weeks
[14:33] <ogra> he loves such restructuring stuff
[14:33] <ogra> yeah
[14:33] <NCommander> (aren't Japanese holidays great?)
[14:33] <ogra> yeah
[14:33] <ogra> didnt you think about moving out of the US ?
[14:34] <ogra> seems a good place to live
[14:34] <NCommander> I got blocked by familial requirements
[14:34] <ogra> ah
[14:34] <NCommander> Very expensive place to live
[14:34] <NCommander> Still looking to move to Europe in due time though
[14:34] <ogra> anyway, lets close the meeting
[14:34] <NCommander> anyway
[14:34] <NCommander> I think we can close it out
[14:34] <NCommander> #endmeeting
[14:34] <MootBot> Meeting finished at 08:34.
[14:34] <ogra> ++
[14:34] <NCommander> wow
[14:35] <NCommander> two weeks of fast meetings
[14:35] <NCommander> I can get used to this
[14:35] <ogra> well, the team got a lot smaller
[16:05] <micahg> is there a DMB meeting?
[16:05] <barry> should be i think
[16:05] <BlackZ> micahg: yeah, it should
[16:05] <BlackZ> but still not started
[16:06] <stgraber> cjwatson and soren both said they won't be able to attend
[16:07] <stgraber> I don't see cody or persia around on the channel
[16:07] <stgraber> nixternal: ping
[16:07] <stgraber> geser: ping
[16:07] <BlackZ> stgraber: cody is crashed - ping timeout
[16:07] <micahg> persia is on vacation I think
[16:07] <barry> guess it's not happening then :/
[16:08] <stgraber> (I'll only be able to attend until :30 as I mentioned on our mailing list, after that I may try on a 3G connection but it didn't work that well last time)
[16:08] <stgraber> yeah, we won't have quorum it seems ...
[16:08] <stgraber> IIRC we need 4 to have quorum in the DMB
[16:08] <stgraber> and so far I'm the only one around ;)
[16:09] <menesis> :(
[16:09] <stgraber> I'll be staying around on IRC in case 3 others show up at the last minute but I wouldn't be too optimistic, sorry
[16:10] <barry> i'm only available until :50, but i guess if they don't show up fairly soon, it's not happening
[16:10]  * micahg just wanted to follow up about package set
[16:15] <nixternal> stgraber: hola
[16:21]  * geser is here
[16:28] <BlackZ> so the DMB meeting will not start?
[16:31] <geser> without quorum that doesn't make much sense as we would need to defer any votings
 I'll be staying around on IRC in case 3 others show up at the last minute but I wouldn't be too optimistic, sorry
[16:33] <stgraber> got to go
[16:33] <geser> I count current 3 DMB members and with 3 others definitely not being here the chances to reach quorum aren't that big
[16:33] <BlackZ> geser: why 3?
[16:34] <geser> BlackZ: nixternal, stgraber and geser
[16:35] <BlackZ> I thought cody-somerville was around, so I'm wrong, sorry
[16:36] <geser> at least his client is here
[16:36] <BlackZ> heh
[16:39] <geser> Cody can't attend either
[16:39] <geser> so it definitely no quorum today, sorry
[16:40] <barry> oh well, i guess we'll see you in 2 weeks ;)
[16:45] <micahg> thanks anyways geser
[17:43] <vish> @now
[17:58] <JFo> \o/
[17:59]  * jjohansen fades in
[17:59]  * manjo zooms in
[18:00]  * JFo adjusts jjohansen's levels :)
[18:00]  * apw drops in with a thunmp
[18:00]  * cking arrives \o/
[18:00] <cnd>  /o\
[18:00] <kamal> o/
[18:00]  * ogasawara waves
[18:00]  * cnd is cowering in fear
[18:00] <JFo> I wondered
[18:01] <lag>   ___ ___         .__  .__
[18:01] <lag>  /   |   \   ____ |  | |  |   ____
[18:01] <lag> \    Y    /\  ___/|  |_|  |_(  <_> )
[18:01] <lag>  \___|_  /  \___  >____/____/\____/
[18:01] <lag>        \/       \/
[18:01] <cnd> uhhh
[18:01]  * manjo sips coffee
[18:01]  * apw slaps lag
[18:01] <JFo> heh
[18:01]  * lag giggles
[18:02] <bjf> #startmeeting
[18:02] <MootBot> Meeting started at 12:02. The chair is bjf.
[18:02] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:02]  * manjo sips coffee
[18:02] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:02] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:02] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:02] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick
[18:02] <bjf> #
[18:02] <bjf> # NOTE: '..' indicates that you are finished with your input.
[18:02] <bjf> #
[18:02] <bjf> [TOPIC] Release Metrics: (JFo)
[18:02] <MootBot> New Topic:  Release Metrics: (JFo)
[18:02] <JFo> Release Meeting Bugs (0 bugs, 13 Blueprints)
[18:02] <JFo> [18:02] <JFo>  * 1 linux kernel bugs (up 1)
[18:02] <JFo> [18:02] <JFo>  * 3 linux kernel bugs (down 2)
[18:02] <JFo> [18:02] <JFo>  * 14 blueprints
[18:02] <JFo> *** NOTE: This listing includes HWE Blueprints***
[18:02] <JFo> [18:02] <JFo>  * https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on
[18:02] <JFo>  * Breakdown by status:
[18:02] <JFo>    http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/
[18:02] <JFo> ..
[18:03] <bjf> [TOPIC] Blueprint: kernel-maverick-apparmor (jjohansen)
[18:03] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor
[18:03] <MootBot> New Topic:  Blueprint: kernel-maverick-apparmor (jjohansen)
[18:03] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-apparmor
[18:03] <jjohansen> started cross testing of compatibility patch and found some errors that need to fixed before it can be pulled in.  Will try to get that cleaned up today so we can pull in the latest version, and send it upstream.
[18:03] <jjohansen> Caching patch fix - no progress still sitting on the back burner behind cold, compatibility patch, and EC2.
[18:03] <jjohansen> ..
[18:04] <bjf> [TOPIC] Blueprint: kernel-maverick-firewire-stack (manjo)
[18:04] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-firewire-stack
[18:04] <MootBot> New Topic:  Blueprint: kernel-maverick-firewire-stack (manjo)
[18:04] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-firewire-stack
[18:04] <manjo> nothing to report at this time
[18:04] <manjo> ..
[18:04] <bjf> [TOPIC] Blueprint: kernel-maverick-misc (apw)
[18:04] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-misc
[18:04] <MootBot> New Topic:  Blueprint: kernel-maverick-misc (apw)
[18:04] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-misc
[18:04] <apw> The two items slipped out of Alpha-1 are still outstanding, though neither is a release task.  The debian commonisation is currently progressing with Karmic master being retrofitted currently.  We expect to have Karmic and Lucid master both complete by Wednesday, ready for test uploads.
[18:04] <apw> ..
[18:05] <bjf> [TOPIC] Blueprint: kernel-maverick-new-kernel-on-lts (tgardner)
[18:05] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-new-kernel-on-lts
[18:05] <MootBot> New Topic:  Blueprint: kernel-maverick-new-kernel-on-lts (tgardner)
[18:05] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-new-kernel-on-lts
[18:05] <tgardner> The Lucid LTS backport kernel is tracking Maverick at http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu.
[18:05] <tgardner> The current kernel and meta versions are linux-maverick-2.6.35-1.1~lucid1 and linux-meta-lts-backport-maverick-<IP_ADDRESS>.6.
[18:05] <tgardner> ..
[18:05] <bjf> [TOPIC] Blueprint: kernel-maverick-pv-ops-ec2-kernel (jjohansen)
[18:05] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-pv-ops-ec2-kernel
[18:05] <MootBot> New Topic:  Blueprint: kernel-maverick-pv-ops-ec2-kernel (jjohansen)
[18:05] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-pv-ops-ec2-kernel
[18:05] <jjohansen> pv-ops kernel has so far not been working out, and I am following up with Amazon.
[18:05] <jjohansen> Started looking at fallback plan 1 of pv-on-HVM driver but I haven't been able to successfully build them yet (failing in the ballon driver atm).  I need to test building them on an older stock kernel yet.
[18:06] <jjohansen> ..
[18:06] <bjf> [TOPIC] Blueprint: kernel-maverick-tracing-support (cnd)
[18:06] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-tracing-support
[18:06] <MootBot> New Topic:  Blueprint: kernel-maverick-tracing-support (cnd)
[18:06] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-tracing-support
[18:06] <cnd> I sent a patch upstream for relative source paths for perf probe, waiting on feedback
[18:06] <cnd> I took a closer look at trace-cmd and kernelshark
[18:07] <cnd> I'm not convinced quite yet that we really need kernelshark
[18:07] <cnd> so I may just package up trace-cmd when I get the chance
[18:07] <cnd> ..
[18:07] <bjf> [TOPIC] Blueprint: kernel-maverick-ubuntu-delta-review (ogasawara)
[18:07] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-ubuntu-delta-review
[18:07] <MootBot> New Topic:  Blueprint: kernel-maverick-ubuntu-delta-review (ogasawara)
[18:07] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-ubuntu-delta-review
[18:07] <ogasawara> I own the majority of the Alpha2 work items so will start closing those out shortly.
[18:07] <ogasawara> ..
[18:08] <bjf> [TOPIC] Blueprint: kernel-maverick-union-mounts (apw)
[18:08] <bjf> [LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-union-mounts
[18:08] <MootBot> New Topic:  Blueprint: kernel-maverick-union-mounts (apw)
[18:08] <MootBot> LINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-maverick-union-mounts
[18:08] <apw> Waiting on testing from Foundations from updated kernels.  As part of the roll forward to v2.6.35-rc1 we have had to update AUFS2 as it no longer built.  We expect to have to update it again before v2.6.35 final regardless of whether union-mounts make it.
[18:08] <apw> ..
[18:08] <bjf> [TOPIC] Blueprint: kernel-maverick-bug-handling (jfo)
[18:08] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:08] <MootBot> New Topic:  Blueprint: kernel-maverick-bug-handling (jfo)
[18:08] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bug-handling
[18:08] <JFo> Good progress on the wiki. There is now a Todo located at: https://wiki.ubuntu.com/Kernel/WikiToDo and a wiki gardening guide at: https://wiki.ubuntu.com/Kernel/WikiGardening Please use these references when working on the wiki pages.
[18:09] <JFo> Thanks to apw for getting those up and going
[18:09] <JFo> ..
[18:09] <bjf> [TOPIC] Blueprint: kernel-maverick-upstart (apw)
[18:09] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-upstart
[18:09] <MootBot> New Topic:  Blueprint: kernel-maverick-upstart (apw)
[18:09] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-upstart
[18:09] <apw> We have patches pending for the remaining Alpha-1 deliverable, waiting on testing from Foundations.  We have also pulled forward the 'readahead was used' patches from Lucid testing to Maverick and pushed those to a further PPA for testing.
[18:09] <apw> ..
[18:10] <bjf> [TOPIC] Blueprint: kernel-maverick-reducing-dkms-packages-required-for-hardware-enablement (cking)
[18:10] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-reducing-dkms-packages-required-for-hardware-enablement
[18:10] <MootBot> New Topic:  Blueprint: kernel-maverick-reducing-dkms-packages-required-for-hardware-enablement (cking)
[18:10] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-reducing-dkms-packages-required-for-hardware-enablement
[18:10] <cking> Outcome was that "Tiger team" to discuss this to be set up by awe
[18:10] <cking> Blueprint probably should be closed
[18:10] <cking> ..
[18:10] <apw> lets close it off and get it off the meeting
[18:10] <cking> yep
[18:10] <apw> ..
[18:10] <bjf> [TOPIC] Blueprint: kernel-maverick-bios-test-automation (cking)
[18:10] <cking> ..
[18:10] <bjf> [LINK] https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation
[18:10] <MootBot> New Topic:  Blueprint: kernel-maverick-bios-test-automation (cking)
[18:10] <MootBot> LINK received:  https://blueprints.edge.launchpad.net/ubuntu/+spec/kernel-maverick-bios-test-automation
[18:10] <cking> Added the following functionality to the firmware test suite:
[18:10] <cking>   ACPI MCFG table test
[18:10] <cking>   MTRR tests
[18:10] <cking>   HPET sanity checks
[18:10] <cking>   Simple Fan tests
[18:10] <cking>   ACPI FADT table checks
[18:10] <cking>   Simple Battery tests
[18:10] <cking>   PCI Max Read Req sanity check
[18:10] <cking>   BIOS EBDA check
[18:10] <cking> Misc:
[18:11] <cking>   Add in e820 region checking
[18:11] <cking>   Generalised list handling
[18:11] <cking>   Fix iasl + pipe I/O bug
[18:11] <cking>   Re-organise lib headers
[18:11] <cking> ..
[18:11] <bjf> [TOPIC] Status: Maverick (ogasawara)
[18:11] <MootBot> New Topic:  Status: Maverick (ogasawara)
[18:11] <ogasawara> We uploaded the 2.6.35-1.1 kernel which rebased us to 2.6.35-rc1.  I'll be uploading 2.6.35-2.2 within the hour.  This will rebase us to 2.6.35-rc2.  Please test if you are able to.
[18:11] <ogasawara> Also, just a general reminder that Alpha 2 is Thurs July 1 (ie ~3weeks from today) so make sure you're on track with any work items that need doing.
[18:11] <ogasawara> ..
[18:12] <bjf> [TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)
[18:12] <MootBot> New Topic:  Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)
[18:12] <bjf> Dapper:      2.6.15-55.84  (security)
[18:12] <bjf> Hardy:       2.6.24-28.70  (security)
[18:12] <bjf> Jaunty:      2.6.28-19.61  (security)
[18:12] <bjf> Karmic:      2.6.31-22.60  (security)
[18:12] <bjf>  - mvl-dove  2.6.31-214.28 (security)
[18:12] <bjf>  - fsl-imx51 2.6.31-112.28 (security)
[18:12] <bjf>  - ec2       2.6.31-307.15 (security)
[18:12] <bjf> Lucid:       2.6.32-22.36  (security)
[18:12] <bjf>  - mvl-dove  2.6.32-205.18 (security)
[18:12] <bjf>  - fsl-imx51 2.6.31-608.14 (security)
[18:12] <bjf>  - ti-omap   2.6.33-501.7  (security)
[18:12] <bjf>  - qcm-msm   2.6.31-802.4  (security)
[18:12] <bjf>  - ec2       2.6.32-306.11 (security)
[18:12] <bjf>  - LBM       2.6.32-22.15  (waiting for acceptance to proposed)
[18:12] <bjf> The initial security release for Lucid caused a regression for KVM. Though
[18:12] <bjf> the same patch is in Karmic and Jaunty without problems. It has been reverted
[18:12] <bjf> for Lucid and an additional upload was made (thanks apw).
[18:12] <bjf> The current update to Lucid qcm-msm will be the last one as we lack testing
[18:12] <bjf> hardware.
[18:12] <bjf> Currently preparing proposed uploads to Lucid and Karmic and while being on
[18:13] <bjf> those, updating the abstracted debian implementation (apw).
[18:13] <bjf> Lucid proposed will contain upstream stable <IP_ADDRESS>-15 and <IP_ADDRESS>-5 for
[18:13] <bjf> DRM (amongst a lot of other changes). Target for upload to proposed for the
[18:13] <bjf> master branch is Wednesday.
[18:13] <bjf> ..
[18:13] <bjf> [TOPIC] Incoming Bugs: Regressions (JFo)
[18:13] <MootBot> New Topic:  Incoming Bugs: Regressions (JFo)
[18:13] <JFo> Incoming Bugs
[18:13] <JFo> 15 Maverick Bugs (up 10)
[18:13] <JFo> 946 Lucid Bugs (down 59)
[18:13] <JFo> Current regression stats (broken down by release):
[18:13] <JFo> [18:13] <JFo>   * 7 maverick bugs (up 2)
[18:13] <JFo>   * 234 lucid bugs (down 28; to be converted to regression-release)
[18:13] <JFo> [18:13] <JFo>   * 25 lucid bugs (down 1)
[18:13] <JFo>   * 9 karmic bugs (no change)
[18:13] <JFo>   * 5 jaunty bugs (no change)
[18:13] <JFo>   * 1 hardy bug (no change)
[18:13] <JFo> [18:13] <JFo>   * 128 lucid bugs (down 18)
[18:13] <JFo>   * 50 karmic bugs (no change)
[18:13] <JFo>   * 20 jaunty bugs (no change)
[18:13] <JFo>   * 3 hardy bugs (no change)
[18:13] <JFo> [18:13] <JFo>   * 1 lucid bug (no change)
[18:13] <JFo>   * 1 karmic bug (no change)
[18:13] <JFo> please note that we are at a downward slope for Lucid bugs
[18:13] <JFo> this makes me happy.
[18:13] <JFo> ..
[18:13] <apw> o/
[18:14] <bjf> apw, ?
[18:14] <apw> are those lucid bugs going away as fixed or as timed out
[18:14] <apw> expired whatever thats called ?
[18:14] <JFo> mostly timed out
[18:14] <apw> k thanks ..
[18:14] <JFo> np
[18:14] <bjf> 5[TOPIC] Incoming Bugs: Bug day report (JFo)
[18:14] <JFo> The next bug day will be next Tuesday. We will be focusing on working Confirmed bugs and getting them to either Incomplete, by waay of testing or information requests, or Triaged based on the completeness of the bug. My goal is to work through all of the Confirmed bugs to get them in the correct state and work out the best method for addressing them based on conversation with Andy yesterday. I also want to have a Team bug day much like we did this
[18:14] <JFo>  week to work the Top 50 list. I am open to having be two half days on Friday and Monday again if that worked out for everyone last time.
[18:15] <JFo> any suggestions/objections?
[18:15] <JFo> was the two half days more useful than one whole one?
[18:15] <ogasawara> I like the half days
[18:15] <JFo> cool
[18:15] <JFo> anyone else?
[18:15] <apw> i think half is better over all as its easier to do one or the other
[18:16] <apw> but i didn't manage to do either ..
[18:16] <JFo> heh
[18:16] <JFo> ..
[18:16] <bjf> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:16] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:16] <apw> o/
[18:16] <bjf> apw, go
[18:16] <apw> just a reminder that the wiki update is a team task, please do look over the ToDo and see if there are things you know about and can help clean up
[18:16] <apw> ..
[18:17] <JFo> o/
[18:17] <bjf> JFo, go
[18:17] <manjo> apw, is there a pointer to the todo ?
[18:17] <JFo> just wanted to mention that I have been invited to the QA meeting tomorrow to discuss the Triage Summit
[18:17] <manjo> ie link
[18:17] <apw> https://wiki.ubuntu.com/Kernel/WikiToDo
[18:17] <manjo> thanks
[18:17] <JFo> so I suspect there will be some more chat on it and I will be sending out an e-mail this week to kick things off
[18:18] <JFo> ..
[18:18] <ogasawara> hrm, looks like the WikiTodo is empty?
[18:18] <manjo> yeah
[18:18] <apw> ogasawara, not on my screen
[18:18] <manjo> apw, its blank ofr me too
[18:18] <apw> https://wiki.ubuntu.com/Kernel/WikiToDo
[18:18] <cking> looks fine to me
[18:18] <bjf> not on my screen
[18:18] <ogasawara> hrm, mine just shows the letter "a"
[18:19] <JFo> I see tons of outstanding items
[18:19] <apw> thats the wrong todo ogasawara
[18:19] <apw> thats the whole wiki one
[18:19] <ogasawara> ah, oops, helps if i open the right link
[18:19] <apw> :)
[18:19] <JFo> heh
[18:19] <bjf> last call for open items
[18:20] <bjf> thanks everyone
[18:20] <bjf> #endmeeting
[18:20] <MootBot> Meeting finished at 12:20.
[18:20] <JFo> thanks bjf
[18:20] <kamal> bjf: thanks
[18:20] <apw> thanks
[18:20] <cking> bjf, ta
[18:20] <lag> \o/
[18:57] <zul> hi
[18:57] <smoser> o/
[18:58] <Daviey> \o
[18:59] <jjohansen> \o
[18:59] <mathiaz> o/
[18:59] <alexm> o/
[18:59] <hggdh> ~o~
[18:59] <SpamapS> \o/
[18:59] <ttx> \o
[18:59]  * sommer probably won't be available
[19:00] <jiboumans> o/
[19:00] <smoser> hggdh, does the butterfly
[19:00] <jiboumans> morning folks
[19:00] <jiboumans> smoser: hi, didn't expect you today
[19:00] <jiboumans> #startmeeting
[19:00] <MootBot> Meeting started at 13:00. The chair is jiboumans.
[19:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:00] <jiboumans> let's get rolling
[19:00] <hggdh> smoser: freestyle...
[19:01] <jiboumans> [TOPIC] Review action points
[19:01] <MootBot> New Topic:  Review action points
[19:01] <jiboumans> all to run ISO testing coverage on alpha1
[19:01] <jiboumans> i didn't see any big smoke, so i trust all went well?
[19:01] <ttx> yes, relatively
[19:02] <mathiaz> jiboumans: that's because the wind was blowing in the *other* direction
[19:02] <ttx> for alpha2 we'll coordinate and share the load better
[19:02] <Daviey> hmm.. UEC doesn't work with the current Maverick kernel
[19:02] <SpamapS> Nothing horribly broken, but I found a few things.. lamp-server doesn't install /usr/bin/mysql for instance.
[19:02] <zul> besides its only alpha :)
[19:02] <ttx> we had ~50% tset coverage which is good for alpha1 but not enough for alpha2
[19:02] <jiboumans> it does seem a little spotty this way
[19:03] <jiboumans> ttx, can you take it upon you to coordinate this for alpha2?
[19:03] <ttx> yes.
[19:03] <jiboumans> [ACTION] ttx to coordinate iso testing for alpha2
[19:03] <MootBot> ACTION received:  ttx to coordinate iso testing for alpha2
[19:03] <jiboumans> ok, next
[19:03] <jiboumans> ACTION: smoser to ensure cloud images make it to the alpha1 iso tracker
[19:03] <ttx> that was done.
[19:03] <smoser> done. there, tested, pure perfection
[19:03] <jiboumans> smoser++
[19:04] <ttx> smoser: now that slangasek doesn't do release mgt anymore, you need contacts in the release team
[19:04] <jiboumans> ACTION: smoser to coordinate with jjohansen and ttx to provide a more detailed work item overview for server-maverick-cloud-kernel-upgrades
[19:04] <ttx> that could do it as well
[19:04] <smoser> ttx, yes, i need to train someone there. cjwatson just poked me and had me do it. which was fine.
[19:04] <smoser> training is pretty easy, but we should set up someone with an account on the machine and such.
[19:05] <ttx> jiboumans: please action smoser on training someone else in the release team on cloud image release
[19:05] <jiboumans> [ACTION] smoser on training someone else in the release team on cloud image release
[19:05] <MootBot> ACTION received:  smoser on training someone else in the release team on cloud image release
[19:05] <ttx> jiboumans: that someone can be me if need be
[19:05] <smoser> jiboumans, i'll have more detain on server-maverick-cloud-kernel-upgrades sometime soon.  recent events have somewhat changed the plan there. (server-maverick-cloud-kernel-upgrades)
[19:05] <smoser> detail even
[19:05] <jiboumans> smoser: anything worth updating us on?
[19:06] <smoser> no
[19:06] <jiboumans> ok, carrying over then
[19:06] <jiboumans> [ACTION] smoser to coordinate with jjohansen and ttx to provide a more detailed work item overview for server-maverick-cloud-kernel-upgrades
[19:06] <MootBot> ACTION received:  smoser to coordinate with jjohansen and ttx to provide a more detailed work item overview for server-maverick-cloud-kernel-upgrades
[19:06] <jiboumans> ACTION: sommer to present list of sections that need input from server team
[19:07] <jiboumans> sommer: i saw updates to the blueprint. anything to fill us in on during the doc section later or should we postpone till next week?
[19:07] <jiboumans> guess we missed that window
[19:08] <jiboumans> [TOPIC] Maverick development (jib)
[19:08] <MootBot> New Topic:  Maverick development (jib)
[19:08] <jiboumans> First up: Alpha2 subcycle status (ttx)
[19:08] <ttx> http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-2.html
[19:08] <MootBot> LINK received:  http://people.canonical.com/~pitti/workitems/maverick/canonical-server-maverick-alpha-2.html
[19:09] <ttx> The biurndown chart is a little twisted due to sudden appartition of UEC blueprints and more
[19:09] <ttx> All High specs should be at 25% completion right now and this isn't the case
[19:09] <zul> working on it..
[19:10] <ttx> zul:  yours is at 44%, not bad
[19:10] <jiboumans> worrying that at least 3 of the high spcs have 0/1 items done and no status update
[19:10] <SpamapS> cloud-datastores has been in flux due to upstream's odd position
[19:10] <ttx> SpamapS: and we'll discuss that later today
[19:10] <jiboumans> friendly but final reminder: update the status on monday EOB, keep track of your work items
[19:10] <Daviey> ttx: My % will be a little odd this cycle as 4 out of 7 are related to the weekly update
[19:11] <smoser> i'm making some progress on the ebsmount ones, getting help from Alon of turnkey. we have a reasonable plan there.
[19:11] <ttx> Daviey: did you merge eucalyptus yet ?
[19:11] <jiboumans> all: i want to see these updates reflected in workitems AND your blueprints tatus
[19:12] <ttx> all: if you are under 25% the status line should explain why
[19:12] <Daviey> ttx: Sort of.. i need to borrow you (hopefully tommorrow), to do a team review.. delta is LARGE.
[19:12] <jiboumans> [ACTION] all to keep their specs uptodate with workitems (4-16 hours each) and update their status monday EOB
[19:12] <MootBot> ACTION received:  all to keep their specs uptodate with workitems (4-16 hours each) and update their status monday EOB
[19:12] <ttx> in the same vein, your personal completion rate should be ~25% now
[19:13] <Daviey> ttx: If you are happy, then i'd like to upload it tommorrow.
[19:13] <ttx> Daviey: ping me tomorrow so that we spend time on it
[19:13] <Daviey> ttx: Great!
[19:13] <ttx> smoser: are you fully back ?
[19:13] <jiboumans> hggdh, smoser: you both have a large amount of WI but 0/1 completion. do we need to cull specs?
[19:13] <smoser> i'm planning on some half days this week
[19:14] <smoser> as i said above, i'm making reasonableprogress on the ebsmount portions of cloud-init spec.
[19:14] <smoser> the cloud-init portions, i haven't begun.
[19:14] <hggdh> jiboumans: right now, no. I am going thru them and jaguar
[19:14] <smoser> it probably wouldn't be a bad idea to adjust some of those... but i really do want to get them in.
[19:15] <jiboumans> hggdh, smoser: then please update your blueprints accordingly. 0% progress after 2 weeks of dev is not acceptable.
[19:15] <smoser> fwiw, i'm not at 0%
[19:15] <smoser> 6%
[19:15] <ttx> as a rule of thumb, if the work items do not reflect work that you've done... then you should rewrite the work items
[19:15] <ttx> those are work units, not milestones.
[19:15] <jiboumans> smoser: you're not focussing on the essential part of my message
[19:15] <jiboumans> moving on
[19:16] <jiboumans> UEC related specs (jib)
[19:16] <hallyn> (is this a bad time to ask a pragmatic q?)
[19:16] <ttx> hallyn: never
[19:17] <ttx> (never a bad time to ask a q)
[19:17] <hallyn> ok i'm testing an updated qemu-kvm in my personal ppa.  I obv don't have write access to real ppas yet.  How should I (a) go about working it up into maverick archive, and (b) account for 'done' in blueprint?
[19:17] <jiboumans> daviey, ccheney, hallyn, hggdh: please review the blueprints. A split has been made for the work between alpha2/3 and onwards and we'd like to make sure this reflects reality
[19:17] <jiboumans> as dustin is on leave this week, we rely on you to make sure it's accurate
[19:17] <ttx> feel free to ping me if you need help in that exercise
[19:18] <hallyn> ok thx
[19:18] <ttx> hallyn: you need to ask for sponsoring
[19:18] <jiboumans> ttx, all, anything else on the maverick alpha2 work?
[19:18] <ttx> hallyn: ping me or mathiaz off-meeting and we'll explain that to you.
[19:18] <mathiaz> hallyn: right - I can help you out
[19:18] <hallyn> ttx: ok
[19:18] <ttx> jiboumans: no
[19:19] <jiboumans> alright, next topic:
[19:19] <jiboumans> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[19:19] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[19:19] <mathiaz> hallyn: it will be easier than ttx as we're in the same timezone
[19:19] <hggdh> 1. UEC test rig is ready to test the new SRUs
[19:19] <hggdh> 2. I cannot put Maverick in right now due to bug #588861
[19:20] <hggdh> 3. I am indeed a bit behind, but should catch up fast
[19:20] <mathiaz> hggdh: great
[19:20] <mathiaz> hggdh: the 30.2 eucalytpus sru has been accepted earlier today
[19:20] <SpamapS> A user asked to have bug #589566 SRU'd into lucid as the mongodb people have suggested that 1.2 is not really fit for usage anymore. Do we do that for universe packages?
[19:20] <mathiaz> hggdh: so helping out in verifiying eucalyptus in -proposed would be helpful
[19:21] <hggdh> mathiaz: indeed, and this is my intention
[19:21] <mathiaz> hggdh: great - thanks
[19:21] <ttx> SpamapS: no we don't
[19:21] <mathiaz> SpamapS: probably not
[19:21] <SpamapS> what about backports?
[19:21] <mathiaz> SpamapS: yes - that would be the best option
[19:21] <jiboumans> hggdh, Daviey : i see that bug is currently unassigned; do you need help in getting it assigned or is it on track?
[19:21] <mathiaz> SpamapS: unless mongodb is *completly* broken in the lucid
[19:22] <SpamapS> Also I need to have my merge/sync bugs for alpha2 set to a higher importance I think.. have not gotten any attention from sponsors, I'm guessing because the importance is undecided.
[19:22] <Daviey> jiboumans: Hmm.. it's really a kernel issue.. i spoke with them yesterday, and they pretty much said await rc2
[19:22] <ttx> SpamapS: no, importance should be wishlist for those
[19:22] <hggdh> jiboumans: Daviey is better poised to answer
[19:22] <jiboumans> Daviey: you mean alpha2's kernel?
[19:22] <mathiaz> SpamapS: hm - I'd rather say it's a lack of sponsorship manpower
[19:22] <ttx> SpamapS: sync processing is a little slow these days
[19:23] <Daviey> jiboumans: although, some recent updates have asked for triaging information.. but i'll be fixing the underlying issue - so it's not assigned
[19:23] <ttx> SpamapS: for merge sponsoring, don't hesitate to ping one of us
[19:23] <mathiaz> ttx: I think SpamapS is blocked on getting *sponsored*
[19:23] <Daviey> jiboumans: no, upstream kernel.org rc2
[19:23] <jiboumans> Daviey: ah, thanks for clarifying
[19:23] <ttx> mathiaz: ah, sync acking, yes
[19:24] <SpamapS> I've not really done all the steps for getting developer status yet, but I have it on my personal todo list for the week.
[19:24] <mathiaz> SpamapS: hm - we should probably talk about that after the meeting
[19:24] <SpamapS> agreed.
[19:24] <mathiaz> [ACTION] mathiaz to sync up with SpamapS about sponsorship
[19:24] <mathiaz> jiboumans: ^^
[19:25] <jiboumans> hggdh: thanks for that update. any questions for QA?
[19:25] <jiboumans> [ACTION] mathiaz to sync up with SpamapS about sponsorship
[19:25] <MootBot> ACTION received:  mathiaz to sync up with SpamapS about sponsorship
[19:25] <ttx> maybe keep random questions for "open discussion" at the end
[19:25] <jiboumans> moving on:
[19:25] <jiboumans> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:25] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:25] <ttx> so that we don't mix discussions.
[19:26] <ttx> jjohansen: got two for you :)
[19:26] <jjohansen> well I took a look at the atop patches, how important are they
[19:26] <ttx> bug 587893 was fixed
[19:26] <ttx> jjohansen: as in: "how bady do we want them ?"
[19:26] <mathiaz> jjohansen: is there a ppa to run the maverick-backport to lucid?
[19:26] <jjohansen> yes
[19:26] <ttx> badly
[19:27] <ttx> jjohansen: how disruptive are the patches ?
[19:27] <jjohansen> mathiaz: yes to how badly, not ppa
[19:27] <mathiaz> jjohansen: :)
[19:27] <ttx> jjohansen: I think atop is a matter of "if we can do it, we should"
[19:27] <ttx> jjohansen: jib would confirm
[19:27]  * jiboumans confirms
[19:27] <ttx> I wouldn't risk anything for it.
[19:27] <Daviey> jjohansen: Any news on 2.6.35-rc2? :)
[19:28] <jjohansen> okay, I'll present them to the kernel team as such
[19:28] <jiboumans> jjohansen: you said you took a look at the patchset; what's your opinion on it?
[19:28] <jjohansen> Daviey: rc2 rebase should be uploaded today, so kernels should be out by the end of the week
[19:28] <Daviey> jjohansen: That is great news, thanks.
[19:28] <jjohansen> jiboumans: not a fan but it isn't horrible
[19:29] <ttx> jiboumans: we shoudl assess how much usable atop is without that patch
[19:29] <jjohansen> ttx: what about bug #587893
[19:29] <ttx> jjohansen: I think it's fixed now
[19:29] <jiboumans> jjohansen: specifically concerned about possible breakage or performance degradation
[19:29]  * ttx checks the daily
[19:30] <ttx> yesterdays daily is below limits so I suspect the fix landed
[19:30] <jjohansen> ttx: yes it should be "fixed", there are plans to further trim the virtual kernel so that it is only what is needed by kvm/ec2 so it should be getting smaller
[19:31] <ttx> jjohansen: ok, kudos to the kernel team
[19:31] <jiboumans> jjohansen++, kernel team++
[19:31] <ttx> that's all from me
[19:31] <jiboumans> any other questions for the kernel team?
[19:31] <jiboumans> as sommer's not available, we'll skip this weeks Weekly Updates & Questions for the Documentation Team (sommer)
[19:31] <mathiaz> jjohansen: maverick-backport PPA?
[19:32] <smoser> jjohansen, i'm for being careful on shrinking -virtual
[19:32] <smoser> there are already lots of things missing that people legitimately want in "virtual" machines.
[19:32] <smoser> from fuzzy memory, i think ipv6 is missing
[19:32] <jjohansen> mathiaz: sorry I'm not sure on the status of that I will have to check and get back to you
[19:32] <mathiaz> jjohansen: ok - thanks
[19:33] <jiboumans> [ACTION] jjohansen to check on status of backported kernel for lucid
[19:33] <MootBot> ACTION received:  jjohansen to check on status of backported kernel for lucid
[19:33] <jjohansen> smoser: yes we need to be careful, but there are certainly drivers that can be disabled
[19:33] <smoser> yes.
[19:33] <smoser> drivers definitely
[19:33] <jiboumans> alright, moving on:
[19:33] <jiboumans> [TOPIC] Papercuts Alpha2 subcycle status (ttx)
[19:33] <MootBot> New Topic:  Papercuts Alpha2 subcycle status (ttx)
[19:33] <ttx> https://launchpad.net/server-papercuts/+milestone/maverick-alpha-2
[19:33] <mathiaz> smoser: is there a specific tag/package name that is used to track virtual bugs?
[19:34] <ttx> 4 fixed / 14 targets
[19:34] <smoser> not that im aware of, but i think, correctly, they owould hyave the binary package hint  set, is that correct ?
[19:34] <ttx> Remember everyone should take 1-3 bugs in that list. That includes you, mathiaz :P
[19:34] <mathiaz> ttx: :)
[19:34]  * smoser is fuzzy on how all that works in launchpad
[19:34] <ttx> mathiaz: and now the choice is limited :P
[19:34] <jiboumans> ttx: i trust you'll assign if necessary?
[19:34] <mathiaz> ttx: well - that's my fault then
[19:35] <SpamapS> ttx: I have patched 2, but again, awaiting sponsorship
[19:35] <ttx> yes, I'll soon start being nasty
[19:35] <ttx> SpamapS: ack, I think  chuck was looking into some of those
[19:36] <ttx> that's all, we are on track.
[19:36] <jiboumans> thanks ttx
[19:36] <SpamapS> ttx: I'll cover it w/ mathiaz in our post meeting talk about sponsorship.
[19:36] <jiboumans> [TOPIC] Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)
[19:36] <MootBot> New Topic:  Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review (mathiaz)
[19:36]  * mathiaz opens the links
[19:36] <zul> for the curious: v2 http://people.canonical.com/~chucks/SRUTracker/
[19:36]  * SpamapS misses the red
[19:37] <zul> dates are not calculated yet
[19:37] <mathiaz> http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html
[19:37] <MootBot> LINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html
[19:37] <zul> the minicom one should be nominated
[19:37] <mathiaz> ^^ anything worth SRUing in the bugs fixed last week?
[19:37] <zul> who the hell still uses minicom btw ;)
[19:38] <ttx> bug 585911 !
[19:38] <mathiaz> zul: it already is nominated
[19:38] <ttx> beh
[19:38] <zul> mathiaz: ah ok
[19:38] <ttx> bug 585911
[19:39] <mathiaz> hm  - anything else SRU worth?
[19:40] <SpamapS> 280421 seems like it would be hard to work around if you need ethtool
[19:40] <SpamapS> bug 280421 I mean
[19:40] <ttx> I wouldn't move it around in a SRU
[19:40] <SpamapS> symlink to preserve previous location?
[19:41] <zul> i wouldnt SRU that one
[19:41] <mathiaz> would that fit in a criteria outlined in https://wiki.ubuntu.com/StableReleaseUpdates?
[19:41] <mathiaz> https://wiki.ubuntu.com/StableReleaseUpdates#When
[19:42] <mathiaz> ^^ is the list of critiria
[19:42] <SpamapS> ty.. no its not high impact, just annoying. :)
[19:42] <hggdh> I have one question on SRU
[19:42] <mathiaz> hggdh: shoot
[19:43] <hggdh> the samba apport hook to disable reporting if smb.conf is missing -- is it worthy of a SRU?
[19:43] <mathiaz> would that fit in a criteria outlined in https://wiki.ubuntu.com/StableReleaseUpdates#When?
[19:43] <hggdh> mathiaz: no, not at all. But it may inhibit born-invalid bugs
[19:44] <mathiaz> hggdh: no, not at all -> not SRU worthy
[19:44] <hggdh> mathiaz: K, good enough
[19:44] <Daviey> (although, something needs fixing on samba.. it has a massive share of the server bug count)
[19:44] <mathiaz> that's all for the SRU review from me - anything else to add?
[19:45] <jiboumans> [TOPIC] Open Discussion
[19:45] <MootBot> New Topic:  Open Discussion
[19:45] <jiboumans> thanks mathiaz
[19:45] <mathiaz> Daviey: we've discussed that at UDS
[19:45] <ttx> Daviey: what need to be fixed is documentation, and users. Most of the bugs are invalid, they just take time to debunk
[19:45] <mathiaz> Daviey: IIRC the decision was that the server team would keep triaging them
[19:46] <mathiaz> ttx: are you suggesting a user SRU?
[19:46] <jiboumans> could we? :)
[19:46] <Daviey> ^^ Which could mean making sure our apport support is kept awesome.  It could be worth passing by the SRU team for comment.
[19:46] <ttx> mathiaz: the long-term fix is to have a simpler software to handle SMB folder sharing and SMB client
[19:47] <ttx> samba is a complex beast, an users have all sorts of wrong expectations about it
[19:47] <mathiaz> ttx: right - it may worth having a session with the desktop team about that issue at the next UDS
[19:47] <jiboumans> agreed
[19:47] <mathiaz> ttx: for the time being we're kind of stuck :/
[19:47] <Daviey> But if we have great apport hooks on the bugs, we can quickly triage them as not bugs.
[19:47] <jiboumans> it's firmly on my radar though
[19:47] <ttx> mathiaz: yep
[19:47] <hggdh> Daviey: +1
[19:48] <jiboumans> mathiaz: you reckon there'd be mileage in that?
[19:48] <mathiaz> Daviey: right - and we're doing that for maverick
[19:48] <jiboumans> i do like the idea of having that in the LTS most people run
[19:48] <mathiaz> jiboumans: oh yes - I think so
[19:48] <ttx> Daviey: if you look at bug 566560
[19:48] <ttx> Daviey: apport hooks won't help debunking it
[19:48] <SpamapS> Point of order.. I've seen a lot of questions on ubuntu-server go unanswered ... not even a "can you file a bug report for that" response or "did you search for a bug report?" type of response. Should we be going out of our way to answer questions on the list?
[19:48] <mathiaz> jiboumans: you mean what - apport hooks backported to LTS?
[19:48] <Daviey> mathiaz: I'm refering to the "not quite" SRU for the LTS.
[19:48] <SpamapS> (I mean the mailing list not #ubuntu-server)
[19:48] <ttx> Daviey: it just takes time to understand wtf the user has put himself into
[19:49] <SpamapS> and by a lot I mean 2.. :P
[19:49] <ttx> Daviey: in order to dismiss it as 'not a bug'
[19:49] <hggdh> still. Apport hooks should be a special case on SRUs
[19:49] <jiboumans> mathiaz: i mean specifically the apport hook for samba in this case
[19:49] <mathiaz> hggdh: well - IIRC apport is disable on stable releases
[19:49]  * hggdh facepalms
[19:49] <jiboumans> interesting..
[19:50] <Daviey> mathiaz: "ubuntu-bug samba" etc should still catch it?
[19:50] <jiboumans> mathiaz, can i ask you to check up on this ?
[19:50] <mathiaz> Daviey: yes - ubuntu-bug is working
[19:50] <Daviey> So i can still see merit. :)
[19:50] <mathiaz> it's the automation part that is disabled
[19:50] <mathiaz> by default on releases apport won't automatically pop-up IIRC
[19:50] <jiboumans> [ACTION] mathiaz to check if providing an updated apport hook to samba in lucid is useful and possible to keep the invalid bug reports down
[19:50] <MootBot> ACTION received:  mathiaz to check if providing an updated apport hook to samba in lucid is useful and possible to keep the invalid bug reports down
[19:51] <mathiaz> it's one of the last thing done in the release cycle
[19:51] <jiboumans> SpamapS: you mean the mailinglist right?
[19:51] <mathiaz> https://launchpad.net/ubuntu/+source/apport/1.13.3-0ubuntu2
[19:51] <jiboumans> SpamapS: if you have an answer, responding is definitely encouraged. even if that answer is 'please file a bug'
[19:51] <mathiaz>   * etc/default/apport: Disable Apport for the final release.
[19:51] <SpamapS> jiboumans: yes I do. I'm just not sure of what is expected on the list.
[19:52] <ttx> SpamapS: some people have a history of being difficult so people just avoid answering them.
[19:52] <SpamapS> just today somebody had a failed install onto software RAID.. I didn't see any responses.
[19:52] <ttx> SpamapS: doesn't mean we shouldn't :)
[19:52] <jiboumans> in fact, we should
[19:53] <SpamapS> I figured the best response would be to suggest they file a bug but I'm not sure against what or what link to feed them to do that.
[19:53] <ttx> Could someone point me to the right direction? > File a bug ?
[19:53] <SpamapS> Figure you guys know more than I.
[19:53] <jiboumans> 'file a bug, heres the type of info we would need [LINK]'
[19:54] <jiboumans> alterantely, if you know about software raids, ask for the diagnostics and give an answer on list. it's a community help channel so there's more people reading than just the canonical employees
[19:54] <ttx> If the system is running, run ubuntu-bug FOO
[19:54] <SpamapS> Is it acceptable to file a bug for them and respond with a link to it suggesting they add themselves?
[19:54] <ttx> If not (like in this case: use this link: ...
[19:54] <mathiaz> SpamapS: that's another option
[19:54] <jiboumans> any other topics to discuss?
[19:55] <mathiaz> SpamapS: for that specific use case I'd reply on the ml
[19:55] <ttx> SpamapS: that confuses the "original reporter"
[19:55] <Daviey> mathiaz: Any news on the packageset archive access?
[19:55] <mathiaz> SpamapS: asking for more information about the failure
[19:55] <mathiaz> SpamapS: I wouldn't open a bug right away
[19:55] <ttx> SpamapS: who is used to determine "incomplete with a response" type of status
[19:55] <ttx> and other things
[19:55] <jjohansen> the current Lucid backport kernel PPA is at  http://ppa.launchpad.net/kernel-ppa/ppa/ubuntu/
[19:56] <ttx> SpamapS: so I wouldn't file a bug on behalf of someone else
[19:56] <mathiaz> Daviey: need to create a team - and populate it with relevant people
[19:56] <mathiaz> jjohansen: thanks
[19:56] <Daviey> mathiaz: Yup.. Is that on your todo?
[19:56] <mathiaz> Daviey: yes :)
[19:56] <Daviey> \o/
[19:57] <jiboumans> mathiaz++
[19:57] <jiboumans> any final topic?
[19:57] <jiboumans> going once...
[19:57] <Daviey>  /gone
[19:57] <SpamapS> I like cheese...
[19:57] <jiboumans> [TOPIC] Announce next meeting date and time
[19:57] <jiboumans> Tuesday 2010-06-15 at 1800 UTC - #ubuntu-meeting
[19:57] <MootBot> New Topic:  Announce next meeting date and time
[19:57] <jiboumans> there you have it folks, thanks all for attending!
[19:57] <jiboumans> #endmeeting
[19:57] <Daviey> Booo!
[19:57] <MootBot> Meeting finished at 13:57.
[23:59] <paultag> UBT Meeting in T-Minus 1 Minute :)


[00:12] <Unit193> This channel is now closed and forwards to #ubuntu, please update your auto-joins.  For more information please see the mailing list.
[01:39] <holstein> :/
[01:40] <Unit193> holstein: Thank you very much for all the support you provided (and still do!) over the years.
[01:41] <holstein> :)
[02:01] <jose> holstein: you're welcome to stick around ##ubt-survivors :)