[10:36] <lifeless> I'm here, may be a few minutes late to swtch over at the right time
[10:36] <coolbhavi> lifeless, hello
[10:37] <lifeless> hi
[10:37] <coolbhavi> for reapplying as ubuntu member this is the channel to attend the meet.. Am I right?
[10:38] <lifeless> this is the channel membership board meetings are held in yes
[10:38] <lifeless> if you were a member but let it lapse I think you can just reactivate it over the web
[10:38] <coolbhavi> okay
[10:39] <coolbhavi> lifeless, mine is another 3 months down for lapsing but since I have holidays now I have reapplied
[10:40] <coolbhavi> after a week from now college term starts and I ll be occupied
[10:40] <coolbhavi> :)
[10:43] <popey> you dont need to re-attend a meeting coolbhavi
[10:43] <coolbhavi> popey, then? reactivation?
[10:44] <popey> just re-activiate your own account
[10:44] <popey> launchpad will email you when it's about to run out i think
[10:45] <coolbhavi> popey, just like a team wherein members are invited to activate themselves after the period gets over
[10:45] <popey> yes
[10:45] <coolbhavi> am I getting it right?
[10:45] <coolbhavi> okay thanks
[10:45] <coolbhavi> :)
[10:46] <coolbhavi> then I ll remove my name
[10:46] <coolbhavi> off the wiki
[10:59]  * persia peers about
[11:00] <lifeless> hai
[11:00] <TheMuso> Hi all.
[11:01] <persia> So, without coolbhavi, do we have anything else on the agenda?
[11:02] <freeflying> persia: I was invited here, not sure if it is
[11:03] <persia> Excellent.  That's an item then.
[11:03] <persia> we would do best to wait for elky to say something and amachu to appear though.
[11:11] <amachu> hi
[11:12] <TheMuso> Hey amachu.
[11:12] <amachu> ten minutes gone
[11:13] <amachu> TheMuso: Hi
[11:14] <amachu> persia: elky: Hi
[11:14] <persia> amachu, Hey.  So the agenda is empty, but you invited freeflying.
[11:15] <amachu> and lifeless: Hey
[11:17] <amachu> persia: I had invited him for last meeting, and I couldn't turn out for, posted a reminder to him
[11:19] <amachu> freeflying is ZhengPengHou?
[11:19] <freeflying> amachu: yes
[11:20] <amachu> freeflying: Welcome!
[11:20] <freeflying> amachu: thanks
[11:21] <amachu> freeflying: were you available for last meeting?
[11:22] <TheMuso> Afaicr he was here.
[11:22] <persia> Indeed, although quiet.
[11:23] <lifeless> hi amachu
[11:23] <amachu> persia: Yes, I didn't add that to agenda, but had mentioned in the reminder sent to the list last time
[11:23] <amachu> lifeless: Yes.
[11:24] <amachu> persia: so shall take up this meet to take his consent to be part of the team?
[11:24] <amachu> persia: elky: lifeless: What do you all feel?
[11:24] <persia> Sure, if we're doing it in a meeting.
[11:24] <TheMuso> I have no thoughts/feelings one way or another. I haven't really seen what he has been up to in the community.
[11:25] <amachu> elky: are you there?
[11:25] <amachu> persia: I hope this doesn't need a quorum and majority here :-)
[11:26] <amachu> freeflying: We would like to take your consent to be part of Asia Oceania Membership Board.
[11:26] <amachu> I second persia's nomination in this regard
[11:27] <freeflying> amachu: its my pleasure
[11:27] <amachu> lifeless: elky: opinions?
[11:27] <amachu> hey this has been pending for a long time..
[11:28] <amachu> freeflying: great!
[11:28] <amachu> persia: comments?
[11:28] <persia> None not already expressed.
[11:28] <persia> Note that I'm not sure we are authorised to extend ourselves.  Our role may be to send a recommendation to the CC.
[11:29] <amachu> persia: I hope we took that to CC way back, and got it approved for a 2+
[11:31] <persia> amachu, Approved to grow, yes.  Approved to decide who is approved, I'm not sure.
[11:31] <persia> I don't say we aren't, just that I'm not sure.
[11:32] <lifeless> I'm for increasing the board size
[11:32] <lifeless> and the primary thing board members need, IMO, is the ability to understand the requirements we're looking for and assess candidates
[11:33] <lifeless> I have no idea whether freeflying has this or not :)
[11:33] <persia> How do we determine that?
[11:33] <lifeless> no idea
[11:33] <amachu> I hope CC will nod. I will put it to CCs and freeflying's willingness
[11:35] <amachu> persia: Now that freeflying has agreed, I feel we will refer it to CC and recommend his inclusion
[11:36] <amachu> Will that be fine?
[11:36] <lifeless> works for me
[11:36] <persia> Fine by me
[11:36] <amachu> Thanks
[11:37] <amachu> freeflying: thanks for nodding to be part of the Team. We will keep you updated on CCs decision.
[11:37] <freeflying> amachu: np :), I will be delight to take this kind of reponsebility
[11:38] <persia> OK.  Do we have anything else to discuss?
[11:38] <amachu> freeflying: thank you for turning out today.
[11:38] <TheMuso> I don't
[11:38] <amachu> I don't have any
[11:38] <amachu> lifeless: ?
[11:38] <elky> sorry all. only just got home
[11:38] <lifeless> nope
[11:39] <elky> hi freeflying :)
[11:40] <persia> Shall we adjourn, unless elky has anything?
[11:41] <amachu> elky: Do you have something to say?
[11:42] <freeflying> elky: hi
[11:42] <elky> persia, i'm trying to catch up on 2 concurrent meetings. did we vote on something?
[11:43] <persia> elky, Two items came up for discussion, and were agreed by consensus.  1: we'll refer freeflying to the CC as a candidate for this board, and 2: we're done.
[11:43] <elky> persia, yay for first. yay for second :)
[11:44]  * persia goes off in search of food
[11:44] <persia> Have a good evening all.
[11:47] <amachu> freeflying Thanks for joining and thank you everyone for participating
[11:47] <amachu> bye bye
[11:48] <freeflying> amachu: np, have a nice night
[14:03] <StevenK> Right, so let's start this thing
[14:03] <StevenK> #startmeeting
[14:03] <MootBot> Meeting started at 08:03. The chair is StevenK.
[14:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:03]  * ogra wouldnt mind if we skipped actually, was there even an announcement ?
[14:04] <ogra> i cant remember seeing one
[14:04] <StevenK> Yeah, I can't either.
[14:04] <ogra> We'll be having the usual IRC meeting on #ubuntu-meeting, on
[14:04] <ogra> Tueday 2009-07-21 at the new time 13:00 UTC.
[14:04] <plars> that was back on the 17th
[14:04] <ogra> thats the last one NCommander sent out
[14:04] <plars> right
[14:04] <StevenK> [vote] Skip the meeting
[14:04] <MootBot> Please vote on:  Skip the meeting.
[14:04] <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
[14:04] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[14:04]  * StevenK grins
[14:05] <plars> ha
[14:05] <ogra> +1
[14:05] <MootBot> +1 received from ogra. 1 for, 0 against. 0 have abstained. Count is now 1
[14:05] <StevenK> +1
[14:05] <MootBot> +1 received from StevenK. 2 for, 0 against. 0 have abstained. Count is now 2
[14:05] <paulliu> +0
[14:05] <MootBot> Abstention received from paulliu. 2 for, 0 against. 1 have abstained. Count is now 2
[14:05] <ogra> davidm, ?
[14:05] <dyfet> 1
[14:05] <davidm> +1
[14:05] <MootBot> +1 received from davidm. 3 for, 0 against. 1 have abstained. Count is now 3
[14:05] <bjf> +0
[14:05] <MootBot> Abstention received from bjf. 3 for, 0 against. 2 have abstained. Count is now 3
[14:05] <plars> +0
[14:05] <MootBot> Abstention received from plars. 3 for, 0 against. 3 have abstained. Count is now 3
[14:05] <davidm> dyfet, you need to add a plus
[14:05] <dyfet> +1
[14:05] <MootBot> +1 received from dyfet. 4 for, 0 against. 3 have abstained. Count is now 4
[14:05] <StevenK> #endvote
[14:05] <StevenK> Hm
[14:06] <davidm> [endvote]
[14:06] <StevenK> Oh, right
[14:06] <StevenK> [endvote]
[14:06] <MootBot> Final result is 4 for, 0 against. 3 abstained. Total: 4
[14:06] <StevenK> Right, so it seems we skip the meeting. :-)
[14:07]  * ogra applauds 
[14:07] <ogra> so much democracy in this team :)
[14:07] <StevenK> #endmeeting
[14:07] <MootBot> Meeting finished at 08:07.
[15:01] <mdz> cjwatson,Keybuk,sabdfl: ping
[15:03] <mdz> #startmeeting
[15:03] <MootBot> Meeting started at 09:03. The chair is mdz.
[15:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:04] <mdz> I haven't been able to reach cjwatson or Keybuk yet
[15:05] <sabdfl> a lot on the agenda
[15:05] <mdz> Colin is at DebConf, but I thought he would still be here
[15:07] <mdz> Colin's phone rings to voicemail
[15:07] <cjwatson> hello
[15:07] <cjwatson> sorry, I was engrossed in something else
[15:07] <cjwatson> Keybuk texted me to say he'd miss the start
[15:08] <mdz> cjwatson: oh, hi
[15:08]  * Keybuk is here now too
[15:08] <mdz> perfect
[15:08] <cjwatson> was busy with multiarch impl details :)
[15:08] <Keybuk> randa called me as I was logging in
[15:08] <mdz> Keybuk: did you record any actions from the previous meeting?
[15:09] <cjwatson> let's skip my archive reorg item this week, I've done nothing due to alpha-3 feature work and then debconf
[15:09] <Keybuk> mdz: I do not recall ACTION items, reading the notes now
[15:09] <Keybuk> oh, yes there were
[15:09] <mdz> ok, we'll go ahead with the agenda then
[15:09] <Keybuk> Colin was to set up interviews with developers
[15:09] <mdz> Keybuk: oh, ok. please paste
[15:09] <Keybuk> Jono was to provide another draft of the patent policy
[15:09] <Keybuk> You were to review the seed lists Colin posted
[15:09] <mdz> I did that
[15:10] <cjwatson> interviews> I suck. I'm going to do that during the sprint
[15:10] <jono> Keybuk, I have updated it
[15:10] <cjwatson> mdz: oh, did you send mail about that? I must have missed it
[15:11] <cjwatson> never mind, found it now
[15:11] <mdz> Date: Tue, 14 Jul 2009 18:14:04 +0100
[15:11] <mdz> From: Matt Zimmerman <mdz@canonical.com>
[15:11] <mdz> To: Colin Watson <cjwatson@ubuntu.com>
[15:11] <mdz> Subject: Re: Initial package sets for archive reorganisation
[15:11] <cjwatson> it's very tricky to extract the gnome stuff automatically, but I'll see what I can do
[15:12] <mdz> jono: I'm having trouble tracking down that patent policy draft, did you send something to t-b@ about it?
[15:12] <mdz> jono: I looked for it last week to review before the meeting, but didn't see it
[15:12] <jono> mdz, no, I updated the wiki page
[15:13] <jono> and I emailed the TB about it
[15:13] <mdz> jono: I didn't see a mail, and therefore have not read it
[15:14] <mdz> I've just scanned the changes, and they look fine
[15:14] <mdz> I'm pretty sure I acked the previous draft
[15:14] <mdz> jono: have you kept track of who has reviewed it so far?
[15:15] <jono> mdz, I sent it on the 20th
[15:15] <jono> mdz, yes I merged in changes from you and cjwatson
[15:15] <mdz> cjwatson: Keybuk: sabdfl: have any of you reviewed the latest draft?
[15:15] <Keybuk> I reviewed it and replied
[15:15] <Keybuk> (21 July 10:16am)
[15:15] <mdz> Keybuk: the 20 July version?
[15:16] <cjwatson> I have not
[15:16] <cjwatson> ... but I have now and I'm happy with the changes
[15:16] <mdz> sabdfl: ?
[15:16] <mdz> Keybuk: weird, I don't seem to have your mail either
[15:16] <cjwatson> (https://wiki.canonical.com/UbuntuPlatform/Community/Development/PatentPolicy?action=diff&rev2=5&rev1=4)
[15:16] <sabdfl> i was basically happy with the earlier version and haven't looked at the updated one
[15:16] <cjwatson> I have Keybuk's mail
[15:17] <mdz> sabdfl: do you want to give your blessing to the latest draft or do you need time to review it?
[15:18] <sabdfl> looks fine to me now
[15:19] <mdz> ok, shall we vote on it then?
[15:19] <sabdfl> can do
[15:19] <mdz> [VOTE] Accept the patent policy drafted by Jono as an official TB policy
[15:19] <MootBot> Please vote on:  Accept the patent policy drafted by Jono as an official TB policy.
[15:19] <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
[15:19] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[15:20] <cjwatson> +1
[15:20] <MootBot> +1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 1
[15:20] <mdz> +1
[15:20] <MootBot> +1 received from mdz. 2 for, 0 against. 0 have abstained. Count is now 2
[15:20] <mdz> sabdfl: Keybuk: ?
[15:20] <Keybuk> +1
[15:20] <MootBot> +1 received from Keybuk. 3 for, 0 against. 0 have abstained. Count is now 3
[15:21] <Keybuk> sorry, was checking for sneaky changes ;)
[15:21] <sabdfl> +1
[15:21] <MootBot> +1 received from sabdfl. 4 for, 0 against. 0 have abstained. Count is now 4
[15:21] <mdz> #endvote
[15:21] <mdz> [ENDVOTE]
[15:21] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[15:21] <mdz> [ACTION] Matt to communicate the new patent policy
[15:21] <MootBot> ACTION received:  Matt to communicate the new patent policy
[15:21] <mdz> [TOPIC] Nomination period ends for TB election
[15:21] <MootBot> New Topic:  Nomination period ends for TB election
[15:21] <mdz> Keybuk: you seem to be most on top of this
[15:21] <jono> mdz, if you need any help with communicating it, let me know, happy to help
[15:22] <Keybuk> right, we have received a number of nominations
[15:22] <mdz> I've seen 4 nominations come in to the TB list
[15:22] <Keybuk> some from the candidates themselves
[15:22] <Keybuk> and some indirectly
[15:22] <mdz> jono: thanks
[15:22] <Keybuk> our next step should be to contact those individuals to see if they wish to stand
[15:22] <cjwatson> we've had 5 nominations, by my count
[15:22] <Keybuk> cjwatson: the extra one you've seen, was that just sent to you?
[15:22] <mdz> cjwatson: ah, there was a new one I hadn't read yet
[15:23] <cjwatson> Keybuk: no, it was sent to TB
[15:23] <Keybuk> oh, no, I'd read that one too
[15:23] <mdz> oh, I forgot to count myself, so 6
[15:23] <cjwatson> 6?
[15:23] <cjwatson> oh, I missed one too
[15:23] <mdz> Keybuk: do you want to do that, or shall I?
[15:23] <cjwatson> can we name names before the people have agreed to stand?
[15:23] <cjwatson> let's make sure we have the right set of people
[15:23] <mdz> cjwatson: I think we probably shouldn't
[15:24] <sabdfl> is the list still private
[15:24] <sabdfl> ?
[15:24] <cjwatson> ok, I see one person who was nominated twice
[15:24] <cjwatson> which may account for the discrepancy
[15:24] <mdz> cjwatson: right, I have 6 nominations, 5 unique names
[15:24] <mdz> sabdfl: yes
[15:24] <Keybuk> sabdfl: until we actually confirm with people who have been nominated that they wish to stand, I would say it should be private for now
[15:24] <Keybuk> and confirm with you that you would accept their appointment if they were voted in, obviously ;-)
[15:25] <cjwatson> I find it disappointing that we have no non-Canonical nominations
[15:25] <mdz> I've just PMed the list to all of you to confirm
[15:25] <cjwatson> confirmed
[15:25] <mdz> Keybuk: ok, I'll do it
[15:25] <Keybuk> mdz: oops, missed that
[15:25] <mdz> [ACTION] Matt to contact TB nominees to confirm they wish to stand
[15:25] <MootBot> ACTION received:  Matt to contact TB nominees to confirm they wish to stand
[15:25] <Keybuk> yes, I think it's appropriate for you to do that
[15:26] <mdz> [TOPIC] Developer application board (ScottJamesRemnant)
[15:26] <MootBot> New Topic:  Developer application board (ScottJamesRemnant)
[15:26] <Keybuk> the feedback from the MOTU Council and CC was positive
[15:26] <Keybuk> we seemed to agree on the name Developer Membership Board
[15:26] <Keybuk> I see no reason not to go ahead with this if everybody is in agreement
[15:26] <mdz> I thought it was Membership Council
[15:26] <Keybuk> mdz: Board in your mail of 17 July
[15:26] <cjwatson> I heard board
[15:26] <mdz> but if it's Board...whatever I agreed to in email
[15:26] <cjwatson> but I really don't care :)
[15:26] <mdz> whatever all of the others are called
[15:27] <Keybuk> I kinda deliberately put Board in originally to reflect it was a TB-derived power not CC
[15:27] <sabdfl> Board would be consistent with the CC's membership delegation
[15:27] <mdz> Board it is
[15:27] <Keybuk> I'm happy to take the ACTION to enact the LP changes and send out the announcements
[15:27] <Keybuk> (and arrange mailing list changes, etc.)
[15:27] <mdz> Keybuk: we already voted on this, right?
[15:28] <mdz> or do we need to do that still?
[15:28] <Keybuk> we did
[15:28] <mdz> Keybuk: I couldn't find the vote, but I'll trust you on it
[15:28] <mdz> so what's the next step to putting it into practice?
[15:28] <Keybuk> we agreed the text and content on the ML
[15:28] <Keybuk> we didn't have an IRC vote
[15:29] <Keybuk> the next step is to put it into practice
[15:29] <Keybuk> an LP team needs creating
[15:29] <Keybuk> that team should become the admin of ubuntu-core-dev and ubuntu-dev replacing TB
[15:29] <Keybuk> with TB as an admin of that team
[15:29] <Keybuk> membership of that team should be set up
[15:29] <Keybuk> a Mailing List for the team should be set up
[15:29] <Keybuk> and some magic waved to make the TB mailing list public from now on, without opening up the current archives
[15:29] <mdz> Keybuk: documentation updates?
[15:29] <cjwatson> but specifically not admin of motu, presumably
[15:30] <mdz>  processes/newmember or whatever, probably
[15:30] <Keybuk> mdz: right, I'll hunt those down too
[15:30] <Keybuk> cjwatson: indeed
[15:30] <mdz> and also the MOTU wiki documentation
[15:30] <mdz> jono: could your team help with that?
[15:30] <cjwatson> since that's motu-council right now IIRC
[15:30] <cjwatson> (sorry, my network connection is a bit slow right now)
[15:30] <mdz> Keybuk: so will you take the action to do the necessary setup in LP etc.?
[15:30] <jono> sorry just reading up, was sending a few mails
[15:30] <cjwatson> oh, the TB is a co-administrator of motu together with motu-council
[15:31] <cjwatson> so I suggest that the DMB should also replace the TB as co-admin of motu
[15:31] <mdz> [ACTION] Scott to implement Developer Membership Board proposal (LP, mailing list, documentation, etc.)
[15:31] <MootBot> ACTION received:  Scott to implement Developer Membership Board proposal (LP, mailing list, documentation, etc.)
[15:31] <nhandler> cjwatson: Just to be clear, even though they will be a co-admin, the MC will still continue to handle MOTU applications
[15:31] <Keybuk> correct
[15:31] <jono> mdz, yes, we can help with that
[15:32] <jono> hi nhandler :)
[15:32] <cjwatson> nhandler: yes
[15:32] <mdz> [ACTION] Jono to see that documentation is updated to reflect the Developer Membership Board
[15:32] <MootBot> ACTION received:  Jono to see that documentation is updated to reflect the Developer Membership Board
[15:32] <mdz> anything else on the DMB topic?
[15:33] <mdz> [TOPIC] patent policy
[15:33] <MootBot> New Topic:  patent policy
[15:33] <mdz> already covered above, including vote
[15:33] <mdz> [TOPIC] #
[15:33] <mdz> Technical Board governance review (JonoBacon) - Outstanding Issues documented at https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment
[15:33] <MootBot> New Topic:  #
[15:33] <mdz> [TOPIC] Technical Board governance review (JonoBacon) - Outstanding Issues documented at https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment
[15:33] <MootBot> New Topic:  Technical Board governance review (JonoBacon) - Outstanding Issues documented at https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment
[15:33] <mdz> let's just go through these one by one
[15:33] <jono> we may be able to tend to these issues on the mailing list
[15:34] <mdz> [LINK] https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment
[15:34] <MootBot> LINK received:  https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment
[15:34] <mdz> first is updating http://www.ubuntu.com/community/processes/techboard
[15:34] <mdz> somebody just needs to take an action to fix this up
[15:34] <mdz> so far, I have 2 actions, scott has 1, colin has 1 (carried over), jono has 1
[15:34] <sabdfl> where do we stand on the expansion of the TB?
[15:35] <cjwatson> I have had absolutely no luck getting /community/processes/techboard fixed in the past
[15:35] <cjwatson> the action needs to be newz2000's :P
[15:35] <Keybuk> sabdfl: nominations received, mdz will contact them to confirm they wish to stand
[15:35] <Keybuk> we'll then present the list to you
[15:35] <sabdfl> i get that part ;-)
[15:35] <cjwatson> we have exactly five nominations for five seats
[15:35] <Keybuk> you acknowledge them/don't
[15:35] <Keybuk> and then at the next TB meeting, voting opens for the seats
[15:35] <cjwatson> do we still want to open five seats?
[15:35] <Keybuk> and lasts for two weeks
[15:35] <sabdfl> but i'm concerned that 5 nominations doesn't leave much room for a race and larger TB
[15:35] <mdz> sabdfl,cjwatson: it was 6 seats
[15:35] <jono> sabdfl, agreed
[15:35] <cjwatson> or call for nominations again, more forcefully?
[15:35] <mdz> oh, sorry, 5 open seats
[15:36] <cjwatson> yes, the mail says 5 open
[15:36] <jono> would it be possible for us to have seven nominations?
[15:36] <Keybuk> I though it was 4 open seats?
[15:36] <mdz> jono: there is no limit to the number of nominations; we can accept as many as we receive
[15:36] <Keybuk> jono: we don't *have* seven people to nominate ;)
[15:36] <cjwatson> I'd really like to have some non-Canonical nominations, and actually wanted to go through core-dev list and nominate some myself, but ran out of time ...
[15:36] <mdz> jono: we simply haven't received very many
[15:36] <jono> Keybuk, thats what I figured
[15:36] <popey> If the nomination period was to be extended, I'd like to nominate a non-canonical person..
[15:37] <mdz> perhaps the members of the TB would like to put forward more nominees
[15:37] <cjwatson> popey: if you'd like to send it to technical-board@ *really* quickly*
[15:37] <Keybuk> so we should agree on some points
[15:37] <popey> done cjwatson
[15:37] <Keybuk> - how many seats are open?
[15:37] <popey> gah, bounced
[15:37] <Keybuk> - who is retaining their seat?
[15:38] <sabdfl> me!
[15:38] <sabdfl> and colin
[15:38] <Keybuk> sabdfl: then that reduces us to 3 open seats
[15:38] <Keybuk> with 5 nominations
[15:38] <sabdfl> that's not too bad, then
[15:39] <cjwatson> err, four open seats, not 3
[15:39] <Keybuk> cjwatson: I count 3
[15:39] <jono> did we extend an invitation to all core-dev folks?
[15:39] <Keybuk> no?
[15:39] <cjwatson> the mail says we wanted to expand to six members total
[15:39] <jono> as in, email them?
[15:39] <cjwatson> sabdfl, me, +4
[15:39] <popey> cjwatson: sent
[15:39] <Keybuk> oh, I had 5 in my head
[15:39] <mdz> sabdfl: my understanding from the previous meeting was that you were nominating yourself for re-election
[15:39] <cjwatson> yes, I remembered that too ...
[15:39] <sabdfl> i can do that too
[15:39] <mdz> like Scott and I are
[15:40] <sabdfl> sure
[15:40] <mdz> so 6 seats total minus colin = 5 open seats
[15:40] <cjwatson> oh, you didn't say actually, that explains the confusion
[15:40] <cjwatson> I think the discussion went just past the end of the meeting slot
[15:41] <mdz> Keybuk: I think we're clear on those two points. anything else?
[15:41] <Keybuk> nope, sounds like we're clear
[15:41] <mdz> so the only matter is that we'd like to have more nominations
[15:41] <mdz> I suggest that the TB try to think of some, rather than just extending the nomination period and hoping for more
[15:41] <jono> mdz, I am wondering if all the possible people who could be suitable for the TB know about the election
[15:42] <Keybuk> jono: I mailed ubuntu-devel-announce ;)
[15:42] <jono> which is why I was wondering if we should email all core-dev developers directly
[15:42] <mdz> jono: it was on -devel-announce, on planet ubuntu, in UWN...
[15:42] <sabdfl> we also don't know what the dynamic will be now that developer membership is being delegated
[15:42] <sabdfl> hopefully, the TB becomes more tech-oriented than team-oriented
[15:42] <sabdfl> a smaller group may be fine for that
[15:42] <Keybuk> that's the plan :-)
[15:42] <mdz> jono: I think it's more likely that people are too shy/modest/busy to nominate themselves, which is why I think the TB should come up with a couple
[15:42] <sabdfl> so, we could roll with what we have and see how it goes
[15:42] <jono> Keybuk, sure but I suspect many people miss announcements on -devel-announce
[15:42] <jono> right
[15:43] <Keybuk> jono: I think that developers missing announcements on the developer announcements mailing list are unlikely to be suitable for the TB
[15:43] <sabdfl> if we have 5 seats and a Debian representative, that's quite large already
[15:43] <Keybuk> sabdfl: 6 and a Debian representative
[15:43] <sabdfl> 6 requires more nominations, 5 doesn't
[15:43] <Keybuk> ok, fair point
[15:43] <jono> Keybuk, I mainly think that because the announcement list gets updated infrequently and many people will filter it to a folder, so may never see the updated
[15:44] <jono> updates
[15:44] <mdz> sabdfl: 6 total seats, 5 open for this election
[15:44] <popey> There wasn't a huge amount of time for nominations..
[15:44] <mdz> popey: two weeks
[15:44] <popey> during the holiday season..
[15:44] <Keybuk> jono: it was, as mdz says, also sent to ubuntu-devel, ubuntu-devel-discuss, appeared in UWN and on Planet Ubuntu -- you'd have to be pretty deliberately *not* paying attention to miss it <g>
[15:44] <jono> Keybuk, ok, no worries :)
[15:45] <mdz> can we get back to the assessment now?
[15:45] <cjwatson> I've sent another nomination to techboard
[15:45] <mdz> we need a volunteer to fix the text on the website
[15:45] <cjwatson> I will volunteer if I can have access
[15:46] <mdz> [ACTION] Colin to update http://www.ubuntu.com/community/processes/techboard
[15:46] <MootBot> ACTION received:  Colin to update http://www.ubuntu.com/community/processes/techboard
[15:46] <mdz> next item is:Regarding input on key issues such as Pulseaudio, Mono and DX work:
[15:46] <mdz> The TB should determine if they should offer this kid of input and how.
[15:46] <cjwatson> how should I go about convincing the web team to let me? :)
[15:46] <mdz> I think we implicitly agreed this by making the Mono position statement
[15:46] <cjwatson> I guess I'll use my initiative ...
[15:46] <sabdfl> cjwatson: i can clear a path
[15:46] <mdz> cjwatson: and CC me
[15:47] <cjwatson> ok, thanks
[15:47] <mdz> # Should the TB have a regular Call For Topics in the core-dev/MOTU developer community to discuss areas of interest/concern and advise and provide insight? This would help provide a function in the community in which the TB is pro-active as opposed to being reactive with topics of question or concern on an agenda.
[15:47] <mdz> AFAIC, the fortnightly meeting is an implicit call for topics
[15:47] <mdz> though I wouldn't mind if someone sent out an explicit one a few days prior to the meeting (just not me please)
[15:47] <jono> mdz, I think we can better promote the use of the TB for this kind of discussion
[15:48] <Keybuk> right
[15:48] <sabdfl> why not generate a list and work through them at our leisure
[15:48] <mdz> jono: can you set up a process to collect those topics for us?
[15:48] <Keybuk> now we've devolved membership powers, we have an hour's meeting every week to discuss such topics
[15:48] <Keybuk> and a ML
[15:48] <Keybuk> ;)
[15:48] <sabdfl> can we invite non-TB folks to join conversations that they are experts in?
[15:48] <mdz> we have only 10 minutes left, and I actually need to leave 5 minutes early
[15:48] <jono> mdz, I think the process for collecting the topics is to use the agenda page, but I think we can improve the messaging to the community that the TB can discuss key topics
[15:49] <jono> I am happy to send that message out
[15:49] <sabdfl> let's create space on the agenda page, and we choose the order / priority
[15:49] <jono> sabdfl, a specific section would be good
[15:49] <mdz> [ACTION] Jono to draft text to communicate the TB's willingness to review key topics submitted by the community
[15:49] <jono> I am happy to set that up
[15:49] <MootBot> ACTION received:  Jono to draft text to communicate the TB's willingness to review key topics submitted by the community
[15:49] <mdz> # The TB should provide a means of recording whether quorum can be maintained in meetings. If it becomes a problem, consider a discussion of solutions.
[15:49] <Keybuk> it'd be nice to include that text on the website
[15:49] <jono> Keybuk, agreed
[15:50] <mdz> I'm not too concerned about quorum; this has very rarely been a problem in practice
[15:50] <jono> Keybuk, I will get that done first and then mail cjwatson so he can add it when performing the other site update
[15:50] <mdz> jono: sounds good
[15:50] <cjwatson> I don't think we've had a quorum problem since I joined
[15:50] <mdz> is anyone else concerned about quorum?
[15:50] <Keybuk> indeed, Quorum issues have tended to be solved by SMS/Phone calls ;-)
[15:50] <cjwatson> IIRC it was a problem when there were only 3
[15:50] <mdz> jono: was this something raised specifically during the assessment?
[15:50] <sabdfl> timezones in this group make it easier
[15:50] <jono> mdz, it was
[15:51] <jono> mdz, but I think it's rare enough that we don't need a process
[15:51] <jono> lets review at the next UDS if there are quorum issues
[15:51] <mdz> o
[15:51] <mdz> k
[15:51] <mdz> expansion of the board we already decided
[15:51] <mdz> # TB to discuss whether there should be a place for a Debian representative on the board. While it could be argued that Colin Watson is a natural candidate here, it could be beneficial to have more Debian focused representative in that seat.
[15:52] <Keybuk> I think Mark's suggestion of approaching the Debian Technical Committee seemed the right lines
[15:52] <cjwatson> TC> I agree
[15:52] <mdz> cjwatson: maybe you could talk to people at DebConf?
[15:52] <jono> Keybuk, I was just about to saythe same thing
[15:52] <cjwatson> remind me who the current chair is
[15:52] <Keybuk> ftr, the current membership of the TC is
[15:52] <Keybuk>  chairman Bdale Garbee
[15:52] <Keybuk>      member Russ Allbery
[15:52] <Keybuk>      member Don Armstrong
[15:52] <Keybuk>      member Andreas Barth
[15:52] <Keybuk>      member Ian Jackson
[15:52] <Keybuk>      member Steve Langasek
[15:52] <Keybuk>      member Manoj Srivastava
[15:52] <cjwatson> I can certainly talk to bdale
[15:52] <mdz> cjwatson: bdale
[15:53] <jono> Bdale would be fantastic
[15:53] <Keybuk> jono: however he is somewhat busy being fantastic at a thousand other things
[15:53] <cjwatson> is this a "turn up every two weeks to a meeting" thing, or something lighter-weight?
[15:53] <mdz> [ACTION] Colin to discuss with Bdale (Debian technical committee chair) about having a Debian representative on the Ubuntu TB
[15:53] <MootBot> ACTION received:  Colin to discuss with Bdale (Debian technical committee chair) about having a Debian representative on the Ubuntu TB
[15:53] <jono> Keybuk, lets see if he has the time
[15:54] <mdz> cjwatson: I think they could afford to be somewhat less active than the Ubuntu members of the board, but am open to defining the role based on the desire of the individual to participate, and the needs of Debian
[15:54] <mdz> that's the end of the recommendations
[15:54] <cjwatson> ok
[15:54] <mdz> [TOPIC] Select a chair for the next meeting
[15:54] <MootBot> New Topic:  Select a chair for the next meeting
[15:54] <Keybuk> Colin again, he volunteered this time but didn't ;)
[15:54] <cjwatson> I think it's my turn isn't it?
[15:55] <mdz> [ACTION] Colin to chair next TB meeting
[15:55] <MootBot> ACTION received:  Colin to chair next TB meeting
[15:55]  * jono laughs
[15:55] <cjwatson> erm, yeah, sorry about that :-(
[15:55] <mdz> thanks, all
[15:55] <mdz> #endmeeting
[15:55] <MootBot> Meeting finished at 09:55.
[15:55] <jono> thanks everyone
[15:55] <jono> :)
[15:55] <cjwatson> latency here is sufficiently awful that I would have been a terrible chair anyway
[15:55] <cjwatson> I'm relying on typeahead and a good memory ...
[15:56] <jono> cjwatson, I thought your brain was actually directly connected to the Internet :)
[15:56] <sabdfl> thanks all
[15:56] <cjwatson> that would be SO FRUSTRATING
[15:56] <jono> :)
[15:56] <cjwatson> also plz to not be introducing security holes into my brain
[15:57] <elky> aww!
[15:57]  * elky puts the security hole away for another time.
[15:57]  * Keybuk knows of a security hole in Colin's brain
[15:57]  * Keybuk starts singing
[15:57] <cjwatson> agadoo?
[15:57] <Keybuk> mah-nah-mah-nah!
[15:57] <jono> hehe
[15:57] <jono> lets all DoS cjwatson :)
[15:58]  * Keybuk pushes pineapple
[15:58]  * Keybuk shakes the tree
[15:58] <elky> can this be done while i can actually see his soul get haxXord?
[15:58]  * Keybuk pushes pineapple again
[15:59]  * Keybuk grinds coffee
[15:59]  * hyperair stares at the scrollback and laughs
[15:59]  * sabdfl is completely baffled
[15:59]  * sabdfl *pineapple*?
[16:00] <sabdfl> cheers all
[16:02] <elky> Keybuk, your mission, if you should choose it, is to kindly differentially baffle our dictator.
[16:02]  * mathiaz waves
[16:02] <sommer> o//
[16:02] <mathiaz> Has the TB meeting ended?
[16:03] <jmdault> hello mathiaz
[16:04] <hyperair> http://www.lyricsdownload.com/black-lace-agadoo-lyrics.html <-- this appears to be what the pineapple's all about =\
[16:04] <popey> mathiaz: yes
[16:04] <mathiaz> allright then - let's get the Ubuntu Server team meeting rolling
[16:04] <mathiaz> #startmeeting
[16:04] <MootBot> Meeting started at 10:04. The chair is mathiaz.
[16:04] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[16:04] <mathiaz> Today's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting
[16:05] <mathiaz> Last week minutes: https://wiki.ubuntu.com/MeetingLogs/Server/20090721
[16:05] <mathiaz> [TOPIC] SRU tracking on server-related packages
[16:05] <MootBot> New Topic:  SRU tracking on server-related packages
[16:05] <mathiaz> So I've asked bdmurray about a script to get the list of bugs marked fixed released during a previous week
[16:06] <mathiaz> he said he almost had such a script
[16:06] <mathiaz> I need to follow up with him and see how and where we can run this script
[16:07] <mathiaz> [ACTION] mathiaz to follow up with bdmurray about the list of fixed released bugs related to the ubuntu-server team.
[16:07] <MootBot> ACTION received:  mathiaz to follow up with bdmurray about the list of fixed released bugs related to the ubuntu-server team.
[16:07] <mathiaz> anything else to add on this topic?
[16:08] <zul> are we going to review it every week at the meeting?
[16:08] <zul> or should it be an automated email to the server mailing list?
[16:09] <mathiaz> zul: let's start by a weekly review in this meeting
[16:09] <mathiaz> zul: if this takes too much time, we can always move it to the mailing list
[16:10] <zul> k
[16:10] <mathiaz> anything else related to this topic?
[16:11] <mathiaz> nope - let's move on
[16:11] <mathiaz> [TOPIC] Preparing a 2009 edition of the Server Survey
[16:11] <MootBot> New Topic:  Preparing a 2009 edition of the Server Survey
[16:11] <mathiaz> nijaba wrote up a blog post about it: http://nicolas.barcet.com/drupal/en/preparing-2009-server-survey
[16:12] <mathiaz> anything else to add to this topic?
[16:13] <mathiaz> nope - let's move on
[16:14] <mathiaz> [TOPIC] Ubuntu HA team: Cluster stack update
[16:14] <MootBot> New Topic:  Ubuntu HA team: Cluster stack update
[16:14] <mathiaz> neither RoAkSoAx nor ivoks seem to be around
[16:15] <mathiaz> on a related note Debian has moved to DKMS for the drbd package
[16:15] <mathiaz> and the latest version of drbd has been synced in karmic this morning
[16:15] <mathiaz> congratulation to ivoks for driving this packaging effort in both Debian and Ubuntu
[16:16]  * sommer cheers
[16:17] <mathiaz> ivoks told me yesterday he was now focusing on packaging the pacemaker+openais+... stack for karmic
[16:17] <mathiaz> anything else to say on the cluster stack?
[16:18] <mathiaz> it seems not. Let's move on.
[16:19] <mathiaz> That's all I had from last week minutes.
[16:19] <mathiaz> Anything else to add related to last week meeting?
[16:20] <mathiaz> seems not - let's move on.
[16:20] <mathiaz> [TOPIC] Mysql 5.1 in karmic main
[16:20] <MootBot> New Topic:  Mysql 5.1 in karmic main
[16:21] <mathiaz> Debian unstable saw the upload of 5.1 into unstable last weekend
[16:21] <mathiaz> and thus transition to libmysql16 has started in unstable.
[16:21] <mathiaz> The question is whether we should do the same in karmic now?
[16:22] <zul> i dont see why not
[16:22] <mathiaz> The two blockers I had when I looked at moving 5.1 into main a couple of week ago were:
[16:22] <mathiaz> 1. the test suite was not enabled during build time, while it was in 5.0
[16:22] <mathiaz> 2. the cluster engine is not available in 5.1 while it is in 5.0
[16:22] <zul> is there a reason why it was disabled?
[16:23] <mathiaz> zul: because it wasn't successful?
[16:23] <mathiaz> zul: because it wasn't successful.
[16:23] <zul> pretty good reason
[16:23] <mathiaz> zul: hm well - what are you refering to 1 or 2?
[16:23] <zul> both probably
[16:25] <mathiaz> For 2. one solution could be to add a check in pre and see if the ndb engine is used
[16:25] <mathiaz> if so the upgrade would abort and suggest to remove mysql-server
[16:25] <mathiaz> and leave mysql-server-5.0
[16:25] <mathiaz> and leave mysql-server-5.0 installed on the system
[16:25] <zul> sounds reasonable
[16:26] <mathiaz> as transitionning from 5.0 to 5.1 in karmic main means that mysql-server would be provided by 5.1 instead of 5.0
[16:27] <mathiaz> The kubuntu team also would like to move to 5.1 as it would simplify the packaging of amarok
[16:27] <mathiaz> and it seems that we'd want to have 5.1 for the next LTS
[16:28] <mathiaz> uploading 5.1 to main now would mean going through another library transition - I wonder if it's not too late in the release cycle
[16:28] <zul> how many libraries are affected again?
[16:29] <zul> if its alot then it would be just a matter of going to motu's saying we need help to transition mysql libraries to 5.1
[16:29] <mathiaz> zul: well - not really - only packages in main would have to be transitioned in karmic
[16:29] <mathiaz> zul: as we could keep 5.0 in universe for this release cycle
[16:30] <zul> true
[16:30] <mathiaz> zul: in debian there are around 160 pkg IIRC
[16:30] <mathiaz> zul: but there isn't a difference between main and universe
[16:30] <zul> but this would also be an opprotunity to help debian out as well
[16:30] <mathiaz> I've check point 1 (test suite not enabled in 5.1) and it's not true anymore
[16:31] <mathiaz> the test suite is run at build time IIUC
[16:31] <mathiaz> so the only blocker I have is point 2 and we have a workaround for karmic.
[16:31] <mathiaz> so I think the next step is to send an email to ubuntu-devel to discuss the transition to mysql 5.1 in main
[16:32] <mathiaz> and file a MIR for 5.1
[16:32] <mathiaz> which may take some time to get processed.
[16:32] <zul> cool beans
[16:32] <mathiaz> anything else to add?
[16:33] <mathiaz> [ACTION] mathiaz to send an email to ubuntu-devel about moving 5.1 to main
[16:33] <MootBot> ACTION received:  mathiaz to send an email to ubuntu-devel about moving 5.1 to main
[16:33] <mathiaz> let's move on.
[16:33] <mathiaz> [TOPIC] Cloud power management
[16:33] <MootBot> New Topic:  Cloud power management
[16:33] <mathiaz> kirkland: ^^
[16:33] <mathiaz> kirkland: anything new on this front?
[16:33] <kirkland> mathiaz: howdy o/
[16:33] <kirkland> mathiaz: not much since last week, really
[16:34] <kirkland> mathiaz: i expect that the functionality is basically done for karmic
[16:34] <kirkland> mathiaz: and i've moved into test-mode
[16:34] <mathiaz> kirkland: allright - feature complete, testing required.
[16:34] <kirkland> mathiaz: yessir!
[16:34] <mathiaz> kirkland: are you looking for specific hardware?
[16:34] <mathiaz> kirkland: are there any test instructions?
[16:35] <kirkland> mathiaz: yes, still looking for a rackable server that has S3 in /proc/acpi/sleep
[16:35] <kirkland> if you are in possession of one of these, let me know :-)
[16:36] <mathiaz> kirkland: are you focusing on hardware support testing or software testing?
[16:36] <kirkland> mathiaz: software testing of PowerNap and PowerWake
[16:36] <kirkland> mathiaz: i considered the work I did testing suspend/hibernate/resume in Jaunty to verify the hardware support
[16:36] <mathiaz> kirkland: I'd suggest to talk to cr3 - he may have some hardware available
[16:37] <kirkland> mathiaz: okay
[16:38] <mathiaz> anything else to add to this topic?
[16:38] <kirkland> mathiaz: nope, not really
[16:38] <mathiaz> ok. Let's move on.
[16:38] <mathiaz> [TOPIC] Ubuntu Server Gudie
[16:38] <MootBot> New Topic:  Ubuntu Server Gudie
[16:38] <mathiaz> [TOPIC] Ubuntu Server Guide
[16:38] <MootBot> New Topic:  Ubuntu Server Guide
[16:38] <mathiaz> sommer: ^^
[16:38] <mathiaz> sommer: how is it going on this front?
[16:40] <sommer> mathiaz: slowly but surely... been busier than normal with the day job and real life
[16:40] <sommer> mathiaz: I think everything in the blueprint should get done though :)
[16:40] <mathiaz> sommer: awesome - what are the deadlines?
[16:41]  * RoAkSoAx waves
[16:41] <mathiaz> sommer: has the doc team changed the milestones this release cycle?
[16:41] <sommer> Doc Freeze is Oct 1st
[16:41] <sommer> mathiaz: nope as far as I know the milestones are the same
[16:42] <mathiaz> sommer: ok - keep up the good work!
[16:42] <mathiaz> sommer: and ask around for some help
[16:42] <mathiaz> sommer: since there is a list of items to be done on a wiki page (where?) people can pick up some tasks listed there.
[16:42] <sommer> mathiaz: ya, I've been meaning to do a blog post about the new sections
[16:43] <sommer> https://wiki.ubuntu.com/KarmicServerGuide is the spec
[16:43] <mathiaz> sommer: great!
[16:44] <mathiaz> anything else to add on the topic of documentation?
[16:44] <sommer> think that's it for me
[16:45] <mathiaz> allright - let's move on then.
[16:45] <mathiaz> [TOPIC] Ubuntu HA team: Cluster stack update
[16:45] <MootBot> New Topic:  Ubuntu HA team: Cluster stack update
[16:45] <mathiaz> RoAkSoAx: now that you're around - I've given a quick status update earlier in the meeting
[16:46] <mathiaz> RoAkSoAx: did you get a chance to update the Roadmap?
[16:46] <RoAkSoAx> mathiaz, yes: https://wiki.ubuntu.com/UbuntuHighAvailabilityTeam/Roadmap
[16:46] <mathiaz> RoAkSoAx: with a brief overview of what needs to be done
[16:47] <RoAkSoAx> Well for now, we are just waiting for the Debian packages of pacemaker and heartbeat, since openais sis already in debian experimental, and corosync is about to reach it
[16:47] <mathiaz> RoAkSoAx: awesome thanks.
[16:47] <mathiaz> RoAkSoAx: great - and then all of these packages need to be synced in karmic?
[16:48] <RoAkSoAx> mathiaz, yes
[16:49] <mathiaz> ok - anything else to add related to the Cluster stack?
[16:49] <RoAkSoAx> we are just gonna wait for debian packages, do our own tests and see if there are any other needed for Ubuntu. Other than that, those packages already contains our changes
[16:49] <RoAkSoAx> and that would be it
[16:50] <mathiaz> RoAkSoAx: great - keep up the good work.
[16:50] <mathiaz> RoAkSoAx: and once the packages are in Ubuntu, I'd suggest to write up a blog post to ask for more testing
[16:50] <mathiaz> let's move on.
[16:51] <mathiaz> [TOPIC] Open Discussion
[16:51] <MootBot> New Topic:  Open Discussion
[16:51] <mathiaz> Anything else to add?
[16:52] <jmdault> mathiaz: I'm back from vacation and resuming work on Asterisk
[16:52] <mathiaz> jmdault: great!
[16:52] <mathiaz> jmdault: are you up-to-date on what happened in Debian in the mean time?
[16:53] <mathiaz> jmdault: (I'm not)
[16:53] <jmdault> It's more work than I expected, I will have to work with Debian in making newer packages
[16:53] <jmdault> mathiaz: nothing has changed on the Debian side. The dahdi drivers are still 2.0-rc5
[16:53] <jmdault> But the final 2.0 are out from digium, and it fixes some kernel panics
[16:53] <mathiaz> jmdault: ok - is there a wiki page where the plans for Karmic are recorded/outlined?
[16:54] <jmdault> mathiaz: not yet
[16:56] <mathiaz> jmdault: it may be worth spending some time to write a short description of the plan for karmic
[16:56] <mathiaz> jmdault: and get in touch with the debian team to work together.
[16:56] <mathiaz> anything else to add before we wrap up?
[16:56] <jmdault> mathiaz: https://wiki.ubuntu.com/AsteriskIntegration ?
[16:56] <mathiaz> jmdault: looks like a good place
[16:57] <mathiaz> [TOPIC] Agree on next meeting date and time
[16:57] <MootBot> New Topic:  Agree on next meeting date and time
[16:57] <mathiaz> next week, same place, same time?
[16:58] <sommer> +1
[16:59] <mathiaz> allright then.
[16:59] <mathiaz> see you all next week, same place, sime time.
[16:59] <mathiaz> #endmeeting
[16:59] <MootBot> Meeting finished at 10:59.
[17:01] <sommer> thanks mathiaz, later all
[17:12] <Daviey> Gah!  missed the meeting
[17:59] <bjf> Roll Call
[18:00]  * manjo waves
[18:00] <lieb> hi
[18:00]  * ogasawara waves
[18:00]  * rtg_ is herwe
[18:00]  * apw waves
[18:00]  * jjohansen waves
[18:00]  * awe waves
[18:00]  * cking is here
[18:00]  * gnarl reports in for smb
[18:01] <bjf> #startmeeting
[18:01] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[18:01] <MootBot> Meeting started at 12:01. The chair is bjf.
[18:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:01] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting
[18:01] <bjf> [TOPIC] Open Action Items: (apw) Close Blueprints: kernel-karmic-kernel-config-review
[18:01] <MootBot> New Topic:  Open Action Items: (apw) Close Blueprints: kernel-karmic-kernel-config-review
[18:01]  * pgraner waves
[18:01] <apw> That one is done ...
[18:01] <bjf> [TOPIC] Open Action Items: (smb) Organise a sprint session on review of "Blueprint: kernel-karmic-kernel-config-review"
[18:01] <MootBot> New Topic:  Open Action Items: (smb) Organise a sprint session on review of "Blueprint: kernel-karmic-kernel-config-review"
[18:02] <bjf> gnarl?
[18:02] <gnarl> ok
[18:02] <gnarl> sort of put it into a agena i think
[18:02]  * amitk appears belatedly
[18:02]  * rtg_ is really tired of reviewing configs.
[18:03] <bjf> [TOPIC] Open Action Items: (apw, rtg) Sync with J. Johansen before upload on AA enablement
[18:03] <MootBot> New Topic:  Open Action Items: (apw, rtg) Sync with J. Johansen before upload on AA enablement
[18:03] <rtg_> bjf, done
[18:03] <apw> It was determined that AA could be safely enabled and the Karmic kernel now has AA enabled by default.
[18:03] <bjf> [TOPIC] Open Action Items: (apw) Close the 386 flavour task
[18:03] <MootBot> New Topic:  Open Action Items: (apw) Close the 386 flavour task
[18:03] <apw> That is closed off
[18:03] <bjf> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:03] <MootBot> LINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:03] <bjf> [TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)
[18:03] <MootBot> New Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)
[18:03] <ogasawara> Release Meeting Bugs (3 bugs) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic
[18:03] <ogasawara> RC Milestoned bugs - none so far for Alpha 4
[18:03] <ogasawara> Release Targeted Bugs (5 bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux
[18:04] <bjf> [TOPIC] Karmic Release Status: Milestoned Features
[18:04] <MootBot> New Topic:  Karmic Release Status: Milestoned Features
[18:04] <ogasawara> https://launchpad.net/ubuntu/+milestone/karmic-alpha-4
[18:05] <bjf> [TOPIC] Blueprints: kernel-karmic-hwdb-workshop (ogasawara)
[18:05] <ogasawara> it looks like the one that concerns are team has been Implemented by Tim (Karmic kernel flavours)
[18:05] <MootBot> New Topic:  Blueprints: kernel-karmic-hwdb-workshop (ogasawara)
[18:05] <ogasawara> bjf: nothing new to add for hwdb
[18:05] <rtg_> ogguess I should update its status
[18:05] <rtg_> ogasawara, ^^
[18:05] <ogasawara> rtg_: it's already marked as Implemented
[18:06] <rtg_> ogasawara, indeed it is.
[18:06] <bjf> [TOPIC] Blueprints: kernel-karmic-kms (apw)
[18:06] <MootBot> New Topic:  Blueprints: kernel-karmic-kms (apw)
[18:06] <apw> Testing ongoing, results generally good.  Suspend issues now seem resolved.  Tracking a couple of upstream patches which are expected to land in 2.6.31-rc5.  Pulled Intel and ATI Radeon KMS -next branches and pushed to KMS PPA for xorg-edgers testing.
[18:07] <bjf> [TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:07] <MootBot> New Topic:  Blueprints: kernel-karmic-new-kernel-on-lts (rtg)
[18:07] <rtg_> no progress, see last week
[18:07] <bjf> [TOPIC] Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)
[18:07] <MootBot> New Topic:  Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)
[18:07] <gnarl> no progress since last week
[18:07] <bjf> [TOPIC] Blueprints: kernel-karmic-android (coolony)
[18:07] <MootBot> New Topic:  Blueprints: kernel-karmic-android (coolony)
[18:07] <rtg_> apw, what about drbd? ivoks said there is a DKMS package for it
[18:08] <bjf> no progress since last week (speaking for coolony)
[18:08] <apw> rtg_, the original source is dkms aware ... we have an updated version in ubuntu/ for now
[18:08] <apw> noone has stepped up to own a dkms package to my knowledge
[18:08] <rtg_> apw, right, its up-rev from the DKMS version
[18:09] <bjf> [TOPIC] Blueprints: kernel-karmic-sponsoring-staging-drivers (smb)
[18:09] <MootBot> New Topic:  Blueprints: kernel-karmic-sponsoring-staging-drivers (smb)
[18:09] <gnarl> stalled
[18:09] <bjf> [TOPIC] Blueprints: kernel-karmic-suspend-resume (manjo)
[18:09] <MootBot> New Topic:  Blueprints: kernel-karmic-suspend-resume (manjo)
[18:09] <apw> [ACTION] apw, check up on drbd status in dkms package and kernel
[18:09] <manjo> plan on doing a laptop testing session at the dublin meet
[18:09] <cking> tested those images yet? :-)
[18:10] <manjo> put together a test plan on testing
[18:10] <manjo> will be testing kms & suspend/resume
[18:10] <manjo> cking, still downloading
[18:10] <cking> 'k
[18:10] <bjf> [TOPIC] Blueprints: kernel-karmic-wifi (rtg)
[18:10] <MootBot> New Topic:  Blueprints: kernel-karmic-wifi (rtg)
[18:11] <rtg_> making progress on rfkill
[18:11] <rtg_> there are some kernel patches in the pipeline that'll help acpi-support
[18:11] <bjf> [TOPIC] Blueprints: kernel-karmic-better-power-mgt (amitk)
[18:11] <MootBot> New Topic:  Blueprints: kernel-karmic-better-power-mgt (amitk)
[18:11] <amitk> no progress since last week
[18:11] <bjf> [TOPIC] Other Release Tasks: AppArmor (jjohansen)
[18:11] <MootBot> New Topic:  Other Release Tasks: AppArmor (jjohansen)
[18:11] <jjohansen> closed out my clone regression
[18:12] <jjohansen> still have ecryptfs regression to fix 359338
[18:12] <apw> jjohansen, do we already have the clone fix in the batch i added last week
[18:12] <apw> or is there more coming?
[18:12] <jjohansen> more coming, I am still testing through the x cases on the clone but it all looks good so far
[18:13] <rtg_> jjohansen, have you had time to think about the next merge window?
[18:13] <apw> most excellent, thats the last regression i believe from the test suite
[18:13] <bjf> [TOPIC] Other Release Tasks: ARM-Freescale (amitk, bjf)
[18:13] <MootBot> New Topic:  Other Release Tasks: ARM-Freescale (amitk, bjf)
[18:13] <jjohansen> rtg_: yeah, a little
[18:14] <amitk> first set of patches (from Jaunty) was integrated into Karmic and a kernel is available in the archive
[18:14] <bjf> Freescale stuff for me is in place, nothing new, waiting for next patch drop
[18:14] <bjf> should be this week I think (maybe next)
[18:14] <amitk> working on the second set of patches (130) now. Hope to finish them by end of this week
[18:15] <amitk> also working with ogra to figure out why DVI doesn't work on Karmic
[18:15] <amitk> DVI on babbage 2 boards, that is
[18:15] <amitk> that's it
[18:15] <bjf> [TOPIC] Other Release Tasks: Union Mount Solution (apw)
[18:15] <MootBot> New Topic:  Other Release Tasks: Union Mount Solution (apw)
[18:15] <apw> aufs2 testing on livecd seems good.  Pulled in updated aufs2 sources from aufs mainline bringing in a number of bug fixes, uploaded for testing.
[18:16] <apw> Activity ramping back up on vfs union mounts, but not going to be anywhere near .31 ready
[18:16] <bjf> [TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb/gnarl)
[18:16] <MootBot> New Topic:  Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb/gnarl)
[18:16] <gnarl> * Dapper:   2.6.15-54.77 (security)
[18:16] <gnarl> * Hardy:    2.6.24-24.56 (updates)
[18:16] <gnarl>             Planning new proposed upload to get Acer Aspire Ones booting
[18:16] <gnarl>             (unfortunately got delayed with that one)
[18:16] <gnarl> * Intrepid: 2.6.27-14.35 (security)
[18:16] <gnarl>             2.6.27-14.36 (proposed+security)[21] with 5/24 verifications
[18:16] <gnarl> * Jaunty:   2.6.28-13.45 (security)
[18:16] <gnarl>             2.6.28-14.46 (proposed)[20] with 4/15 verifications
[18:16] <gnarl>             ABI bumping versions of LRM and LBM waiting as well
[18:17] <gnarl> No progress on verifications for Intrepid and Jaunty. This delays the
[18:17] <gnarl> move to updates for those.
[18:17] <apw> gnarl, is there something we can do to poke the reporters
[18:17] <apw> on the bugs which need verification?  perhaps getting the arsenal to do it automatically?
[18:17] <apw> ogasawara, ?
[18:17] <gnarl> probably nothhing more thann go to the bugs and repeat
[18:17] <gnarl> but they get a notification normally
[18:17] <ogasawara> yup, I could have a script stock reply them to test
[18:18] <bjf> [TOPIC] Status: Karmic (rtg, apw)
[18:18] <MootBot> New Topic:  Status: Karmic (rtg, apw)
[18:18] <gnarl> Right, maybe we could "remind" them after 7 days
[18:18] <apw> lets talka bout it at sprint
[18:19] <apw> Kamic now has initial ARM imx51 support.  AppArmor has been updated fixing a number of regressions, it is also enabled by default.`
[18:19] <rtg_> -rc5 is imminent
[18:19] <bjf> [TOPIC] Status: ARM (amitk, bjf)
[18:19] <MootBot> New Topic:  Status: ARM (amitk, bjf)
[18:20] <amitk> nothing else to add. This Status should perhaps be removed
[18:20] <bjf> Marvell has applied their patches to a 2.6.31-rc4 git repo, I'm reviewing the patches and will request a pull soon.
[18:21] <bjf> I don't think they started with a Karmic tree but a stock 2.6.31-rc4 so there will be a little work for me to do
[18:21] <apw> hurry else we'll have moved to -rc5 ;)
[18:22] <bjf> this is another HUGH patchset (250+ patches)
[18:22]  * apw goes bling
[18:22] <bjf> [TOPIC] Status: Netbook (sconklin, apw)
[18:22] <MootBot> New Topic:  Status: Netbook (sconklin, apw)
[18:22] <apw> blind
[18:22] <sconklin> No new status since last week.
[18:22] <bjf> [TOPIC] Incoming Bugs: Regressions (ogasawara)
[18:22] <MootBot> New Topic:  Incoming Bugs: Regressions (ogasawara)
[18:22] <ogasawara> 5 regression-potential and 1 regression-release bugs were added this week
[18:23] <ogasawara> one has been resolved with the 2.6.31-4 kernel and another will likely be resolved after the next upload.
[18:23] <ogasawara> I'll also start joining apw and smb on their weekly regression bug call
[18:24] <bjf> [TOPIC] Incoming Bugs: Bug day report (ogasawara)
[18:24] <MootBot> New Topic:  Incoming Bugs: Bug day report (ogasawara)
[18:24] <ogasawara> Highlight is we closed 31 bugs from the weekly kernel bug list.
[18:24] <ogasawara> Refer to http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090721.html for the complete bug day stats.
[18:24] <ogasawara> I'm going to send an announcement that we'll cancel next week's bug day since everyone will be at the sprint
[18:24] <gnarl> good point
[18:25] <bjf> [TOPIC] Open Discussion or Questions: Anyone have anything?
[18:25] <MootBot> New Topic:  Open Discussion or Questions: Anyone have anything?
[18:25]  * ogasawara raises hand
[18:25] <ogasawara> The issue of unwatched packages (ie no one is subscribed to the bug mail) was recently brought to my attention.
[18:25] <ogasawara> Specifically one package kernel-wedge was thought to be the responsibility of the kernel team but is currently unwatched.
[18:25] <apw> which packages you thinking of
[18:25] <ogasawara> Is it okay if the kernel team is subscribed to this package?  It currently has 1 bug so is extremely low traffic
[18:26] <apw> i had a look at kernel-wedge and there is only one bug there
[18:26] <gnarl> so it is quite safe to add
[18:26] <rtg_> ogasawara, I really want cjwatson to own kernel-wedge
[18:26] <apw> that seems appropriate to me
[18:26] <ogasawara> rtg_: ack, I'll propose he be subscribed then
[18:27] <rtg_> kernel-wedge is all about producing udebs for the installer
[18:27] <bjf> anyone else have anything they want to bring up?
[18:27] <cking> we could do with some kernel team know-how on kernel wedge
[18:27] <rtg_> cking, I know enough to be scared of it
[18:28] <cking> agree
[18:28] <rtg_> its real quirky
[18:28] <bjf> going....
[18:28] <bjf> going .....
[18:29] <bjf> Are we going to have an IRC meeting next week? (Sprint week)
[18:29] <rtg_> bjf, I suggest we cancel it
[18:29] <cking> +1 on that
[18:29] <apw> seems reasonable to me
[18:30] <bjf> ok no meeting next week
[18:30] <gnarl> +1
[18:30] <bjf> [TOPIC] Next Meeting Chair: Colin King
[18:30] <MootBot> New Topic:  Next Meeting Chair: Colin King
[18:30] <cking> ack
[18:30] <apw> and two weeks to forget :)
[18:30] <bjf> #endmeeting
[18:30] <MootBot> Meeting finished at 12:30.
[18:30] <cking> I won't!
[18:31] <apw> will
[18:39] <cjwatson> ogasawara: I've subscribed ubuntu-installer to kernel-wedge
[18:39] <cjwatson> that's better than me personally
[18:39] <ogasawara> cjwatson: great, thanks!
[23:56] <bodhi_zazen> 5 min =)