/srv/irclogs.ubuntu.com/2009/07/28/#ubuntu-meeting.txt

=== asac_ is now known as asac
=== Ursinha is now known as Ursinha-afk
=== cjwatson_ is now known as cjwatson
=== Zic is now known as Guest45626
=== Guest45626 is now known as Zic
=== ShadowChild is now known as lukjad007
lifelessI'm here, may be a few minutes late to swtch over at the right time10:36
coolbhavilifeless, hello10:36
lifelesshi10:37
coolbhavifor reapplying as ubuntu member this is the channel to attend the meet.. Am I right?10:37
lifelessthis is the channel membership board meetings are held in yes10:38
lifelessif you were a member but let it lapse I think you can just reactivate it over the web10:38
coolbhaviokay10:38
coolbhavilifeless, mine is another 3 months down for lapsing but since I have holidays now I have reapplied10:39
coolbhaviafter a week from now college term starts and I ll be occupied10:40
coolbhavi:)10:40
popeyyou dont need to re-attend a meeting coolbhavi10:43
coolbhavipopey, then? reactivation?10:43
popeyjust re-activiate your own account10:44
popeylaunchpad will email you when it's about to run out i think10:44
coolbhavipopey, just like a team wherein members are invited to activate themselves after the period gets over10:45
popeyyes10:45
coolbhaviam I getting it right?10:45
coolbhaviokay thanks10:45
coolbhavi:)10:45
coolbhavithen I ll remove my name10:46
coolbhavioff the wiki10:46
* persia peers about10:59
lifelesshai11:00
TheMusoHi all.11:00
persiaSo, without coolbhavi, do we have anything else on the agenda?11:01
freeflyingpersia: I was invited here, not sure if it is11:02
persiaExcellent.  That's an item then.11:03
persiawe would do best to wait for elky to say something and amachu to appear though.11:03
amachuhi11:11
TheMusoHey amachu.11:12
amachuten minutes gone11:12
amachuTheMuso: Hi11:13
amachupersia: elky: Hi11:14
persiaamachu, Hey.  So the agenda is empty, but you invited freeflying.11:14
amachuand lifeless: Hey11:15
amachupersia: I had invited him for last meeting, and I couldn't turn out for, posted a reminder to him11:17
amachufreeflying is ZhengPengHou?11:19
freeflyingamachu: yes11:19
amachufreeflying: Welcome!11:20
freeflyingamachu: thanks11:20
amachufreeflying: were you available for last meeting?11:21
TheMusoAfaicr he was here.11:22
persiaIndeed, although quiet.11:22
lifelesshi amachu11:23
amachupersia: Yes, I didn't add that to agenda, but had mentioned in the reminder sent to the list last time11:23
amachulifeless: Yes.11:23
amachupersia: so shall take up this meet to take his consent to be part of the team?11:24
amachupersia: elky: lifeless: What do you all feel?11:24
persiaSure, if we're doing it in a meeting.11:24
TheMusoI have no thoughts/feelings one way or another. I haven't really seen what he has been up to in the community.11:24
amachuelky: are you there?11:25
amachupersia: I hope this doesn't need a quorum and majority here :-)11:25
amachufreeflying: We would like to take your consent to be part of Asia Oceania Membership Board.11:26
amachuI second persia's nomination in this regard11:26
freeflyingamachu: its my pleasure11:27
amachulifeless: elky: opinions?11:27
amachuhey this has been pending for a long time..11:27
amachufreeflying: great!11:28
amachupersia: comments?11:28
persiaNone not already expressed.11:28
persiaNote that I'm not sure we are authorised to extend ourselves.  Our role may be to send a recommendation to the CC.11:28
amachupersia: I hope we took that to CC way back, and got it approved for a 2+11:29
persiaamachu, Approved to grow, yes.  Approved to decide who is approved, I'm not sure.11:31
persiaI don't say we aren't, just that I'm not sure.11:31
lifelessI'm for increasing the board size11:32
lifelessand the primary thing board members need, IMO, is the ability to understand the requirements we're looking for and assess candidates11:32
lifelessI have no idea whether freeflying has this or not :)11:33
persiaHow do we determine that?11:33
lifelessno idea11:33
amachuI hope CC will nod. I will put it to CCs and freeflying's willingness11:33
amachupersia: Now that freeflying has agreed, I feel we will refer it to CC and recommend his inclusion11:35
amachuWill that be fine?11:36
lifelessworks for me11:36
persiaFine by me11:36
amachuThanks11:36
amachufreeflying: thanks for nodding to be part of the Team. We will keep you updated on CCs decision.11:37
freeflyingamachu: np :), I will be delight to take this kind of reponsebility11:37
persiaOK.  Do we have anything else to discuss?11:38
amachufreeflying: thank you for turning out today.11:38
TheMusoI don't11:38
amachuI don't have any11:38
amachulifeless: ?11:38
elkysorry all. only just got home11:38
lifelessnope11:38
=== ian_brasil-afk is now known as ian_brasil
elkyhi freeflying :)11:39
persiaShall we adjourn, unless elky has anything?11:40
amachuelky: Do you have something to say?11:41
freeflyingelky: hi11:42
elkypersia, i'm trying to catch up on 2 concurrent meetings. did we vote on something?11:42
persiaelky, 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
elkypersia, yay for first. yay for second :)11:43
* persia goes off in search of food11:44
persiaHave a good evening all.11:44
amachufreeflying Thanks for joining and thank you everyone for participating11:47
amachubye bye11:47
freeflyingamachu: np, have a nice night11:48
=== fader|away is now known as fader_
=== ember_ is now known as ember
StevenKRight, so let's start this thing14:03
StevenK#startmeeting14:03
MootBotMeeting started at 08:03. The chair is StevenK.14:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:03
* ogra wouldnt mind if we skipped actually, was there even an announcement ?14:03
ograi cant remember seeing one14:04
StevenKYeah, I can't either.14:04
ograWe'll be having the usual IRC meeting on #ubuntu-meeting, on14:04
ograTueday 2009-07-21 at the new time 13:00 UTC.14:04
plarsthat was back on the 17th14:04
ograthats the last one NCommander sent out14:04
plarsright14:04
StevenK[vote] Skip the meeting14:04
MootBotPlease vote on:  Skip the meeting.14:04
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot14:04
MootBotE.g. /msg MootBot +1 #ubuntu-meeting14:04
* StevenK grins14:04
plarsha14:05
ogra+114:05
MootBot+1 received from ogra. 1 for, 0 against. 0 have abstained. Count is now 114:05
StevenK+114:05
MootBot+1 received from StevenK. 2 for, 0 against. 0 have abstained. Count is now 214:05
paulliu+014:05
MootBotAbstention received from paulliu. 2 for, 0 against. 1 have abstained. Count is now 214:05
ogradavidm, ?14:05
dyfet114:05
davidm+114:05
MootBot+1 received from davidm. 3 for, 0 against. 1 have abstained. Count is now 314:05
bjf+014:05
MootBotAbstention received from bjf. 3 for, 0 against. 2 have abstained. Count is now 314:05
plars+014:05
MootBotAbstention received from plars. 3 for, 0 against. 3 have abstained. Count is now 314:05
davidmdyfet, you need to add a plus14:05
dyfet+114:05
MootBot+1 received from dyfet. 4 for, 0 against. 3 have abstained. Count is now 414:05
StevenK#endvote14:05
StevenKHm14:05
davidm[endvote]14:06
StevenKOh, right14:06
StevenK[endvote]14:06
MootBotFinal result is 4 for, 0 against. 3 abstained. Total: 414:06
StevenKRight, so it seems we skip the meeting. :-)14:06
* ogra applauds 14:07
ograso much democracy in this team :)14:07
StevenK#endmeeting14:07
MootBotMeeting finished at 08:07.14:07
=== vorian is now known as LadiesMan217
=== LadiesMan217 is now known as vorian
mdzcjwatson,Keybuk,sabdfl: ping15:01
mdz#startmeeting15:03
MootBotMeeting started at 09:03. The chair is mdz.15:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:03
mdzI haven't been able to reach cjwatson or Keybuk yet15:04
sabdfla lot on the agenda15:05
mdzColin is at DebConf, but I thought he would still be here15:05
mdzColin's phone rings to voicemail15:07
cjwatsonhello15:07
cjwatsonsorry, I was engrossed in something else15:07
cjwatsonKeybuk texted me to say he'd miss the start15:07
mdzcjwatson: oh, hi15:08
* Keybuk is here now too15:08
mdzperfect15:08
cjwatsonwas busy with multiarch impl details :)15:08
Keybukranda called me as I was logging in15:08
mdzKeybuk: did you record any actions from the previous meeting?15:08
cjwatsonlet's skip my archive reorg item this week, I've done nothing due to alpha-3 feature work and then debconf15:09
Keybukmdz: I do not recall ACTION items, reading the notes now15:09
Keybukoh, yes there were15:09
mdzok, we'll go ahead with the agenda then15:09
KeybukColin was to set up interviews with developers15:09
mdzKeybuk: oh, ok. please paste15:09
KeybukJono was to provide another draft of the patent policy15:09
KeybukYou were to review the seed lists Colin posted15:09
mdzI did that15:09
cjwatsoninterviews> I suck. I'm going to do that during the sprint15:10
jonoKeybuk, I have updated it15:10
cjwatsonmdz: oh, did you send mail about that? I must have missed it15:10
cjwatsonnever mind, found it now15:11
mdzDate: Tue, 14 Jul 2009 18:14:04 +010015:11
mdzFrom: Matt Zimmerman <mdz@canonical.com>15:11
mdzTo: Colin Watson <cjwatson@ubuntu.com>15:11
mdzSubject: Re: Initial package sets for archive reorganisation15:11
cjwatsonit's very tricky to extract the gnome stuff automatically, but I'll see what I can do15:11
mdzjono: I'm having trouble tracking down that patent policy draft, did you send something to t-b@ about it?15:12
mdzjono: I looked for it last week to review before the meeting, but didn't see it15:12
jonomdz, no, I updated the wiki page15:12
jonoand I emailed the TB about it15:13
mdzjono: I didn't see a mail, and therefore have not read it15:13
mdzI've just scanned the changes, and they look fine15:14
mdzI'm pretty sure I acked the previous draft15:14
mdzjono: have you kept track of who has reviewed it so far?15:14
jonomdz, I sent it on the 20th15:15
jonomdz, yes I merged in changes from you and cjwatson15:15
mdzcjwatson: Keybuk: sabdfl: have any of you reviewed the latest draft?15:15
KeybukI reviewed it and replied15:15
Keybuk(21 July 10:16am)15:15
mdzKeybuk: the 20 July version?15:15
cjwatsonI have not15:16
cjwatson... but I have now and I'm happy with the changes15:16
mdzsabdfl: ?15:16
mdzKeybuk: weird, I don't seem to have your mail either15:16
cjwatson(https://wiki.canonical.com/UbuntuPlatform/Community/Development/PatentPolicy?action=diff&rev2=5&rev1=4)15:16
sabdfli was basically happy with the earlier version and haven't looked at the updated one15:16
cjwatsonI have Keybuk's mail15:16
mdzsabdfl: do you want to give your blessing to the latest draft or do you need time to review it?15:17
sabdfllooks fine to me now15:18
mdzok, shall we vote on it then?15:19
sabdflcan do15:19
mdz[VOTE] Accept the patent policy drafted by Jono as an official TB policy15:19
MootBotPlease vote on:  Accept the patent policy drafted by Jono as an official TB policy.15:19
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:19
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:19
cjwatson+115:20
MootBot+1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 115:20
mdz+115:20
MootBot+1 received from mdz. 2 for, 0 against. 0 have abstained. Count is now 215:20
mdzsabdfl: Keybuk: ?15:20
Keybuk+115:20
MootBot+1 received from Keybuk. 3 for, 0 against. 0 have abstained. Count is now 315:20
Keybuksorry, was checking for sneaky changes ;)15:21
sabdfl+115:21
MootBot+1 received from sabdfl. 4 for, 0 against. 0 have abstained. Count is now 415:21
mdz#endvote15:21
mdz[ENDVOTE]15:21
MootBotFinal result is 4 for, 0 against. 0 abstained. Total: 415:21
mdz[ACTION] Matt to communicate the new patent policy15:21
MootBotACTION received:  Matt to communicate the new patent policy15:21
mdz[TOPIC] Nomination period ends for TB election15:21
MootBotNew Topic:  Nomination period ends for TB election15:21
mdzKeybuk: you seem to be most on top of this15:21
jonomdz, if you need any help with communicating it, let me know, happy to help15:21
Keybukright, we have received a number of nominations15:22
mdzI've seen 4 nominations come in to the TB list15:22
Keybuksome from the candidates themselves15:22
Keybukand some indirectly15:22
mdzjono: thanks15:22
Keybukour next step should be to contact those individuals to see if they wish to stand15:22
cjwatsonwe've had 5 nominations, by my count15:22
Keybukcjwatson: the extra one you've seen, was that just sent to you?15:22
mdzcjwatson: ah, there was a new one I hadn't read yet15:22
cjwatsonKeybuk: no, it was sent to TB15:23
Keybukoh, no, I'd read that one too15:23
mdzoh, I forgot to count myself, so 615:23
cjwatson6?15:23
cjwatsonoh, I missed one too15:23
mdzKeybuk: do you want to do that, or shall I?15:23
cjwatsoncan we name names before the people have agreed to stand?15:23
cjwatsonlet's make sure we have the right set of people15:23
mdzcjwatson: I think we probably shouldn't15:23
sabdflis the list still private15:24
sabdfl?15:24
cjwatsonok, I see one person who was nominated twice15:24
cjwatsonwhich may account for the discrepancy15:24
mdzcjwatson: right, I have 6 nominations, 5 unique names15:24
mdzsabdfl: yes15:24
Keybuksabdfl: until we actually confirm with people who have been nominated that they wish to stand, I would say it should be private for now15:24
Keybukand confirm with you that you would accept their appointment if they were voted in, obviously ;-)15:24
cjwatsonI find it disappointing that we have no non-Canonical nominations15:25
mdzI've just PMed the list to all of you to confirm15:25
cjwatsonconfirmed15:25
mdzKeybuk: ok, I'll do it15:25
Keybukmdz: oops, missed that15:25
mdz[ACTION] Matt to contact TB nominees to confirm they wish to stand15:25
MootBotACTION received:  Matt to contact TB nominees to confirm they wish to stand15:25
Keybukyes, I think it's appropriate for you to do that15:25
mdz[TOPIC] Developer application board (ScottJamesRemnant)15:26
MootBotNew Topic:  Developer application board (ScottJamesRemnant)15:26
Keybukthe feedback from the MOTU Council and CC was positive15:26
Keybukwe seemed to agree on the name Developer Membership Board15:26
KeybukI see no reason not to go ahead with this if everybody is in agreement15:26
mdzI thought it was Membership Council15:26
Keybukmdz: Board in your mail of 17 July15:26
cjwatsonI heard board15:26
mdzbut if it's Board...whatever I agreed to in email15:26
cjwatsonbut I really don't care :)15:26
mdzwhatever all of the others are called15:26
KeybukI kinda deliberately put Board in originally to reflect it was a TB-derived power not CC15:27
sabdflBoard would be consistent with the CC's membership delegation15:27
mdzBoard it is15:27
KeybukI'm happy to take the ACTION to enact the LP changes and send out the announcements15:27
Keybuk(and arrange mailing list changes, etc.)15:27
mdzKeybuk: we already voted on this, right?15:27
mdzor do we need to do that still?15:28
Keybukwe did15:28
mdzKeybuk: I couldn't find the vote, but I'll trust you on it15:28
mdzso what's the next step to putting it into practice?15:28
Keybukwe agreed the text and content on the ML15:28
Keybukwe didn't have an IRC vote15:28
Keybukthe next step is to put it into practice15:29
Keybukan LP team needs creating15:29
Keybukthat team should become the admin of ubuntu-core-dev and ubuntu-dev replacing TB15:29
Keybukwith TB as an admin of that team15:29
Keybukmembership of that team should be set up15:29
Keybuka Mailing List for the team should be set up15:29
Keybukand some magic waved to make the TB mailing list public from now on, without opening up the current archives15:29
mdzKeybuk: documentation updates?15:29
cjwatsonbut specifically not admin of motu, presumably15:29
mdz processes/newmember or whatever, probably15:30
Keybukmdz: right, I'll hunt those down too15:30
Keybukcjwatson: indeed15:30
mdzand also the MOTU wiki documentation15:30
mdzjono: could your team help with that?15:30
cjwatsonsince that's motu-council right now IIRC15:30
cjwatson(sorry, my network connection is a bit slow right now)15:30
mdzKeybuk: so will you take the action to do the necessary setup in LP etc.?15:30
jonosorry just reading up, was sending a few mails15:30
cjwatsonoh, the TB is a co-administrator of motu together with motu-council15:30
cjwatsonso I suggest that the DMB should also replace the TB as co-admin of motu15:31
mdz[ACTION] Scott to implement Developer Membership Board proposal (LP, mailing list, documentation, etc.)15:31
MootBotACTION received:  Scott to implement Developer Membership Board proposal (LP, mailing list, documentation, etc.)15:31
nhandlercjwatson: Just to be clear, even though they will be a co-admin, the MC will still continue to handle MOTU applications15:31
Keybukcorrect15:31
jonomdz, yes, we can help with that15:31
jonohi nhandler :)15:32
cjwatsonnhandler: yes15:32
mdz[ACTION] Jono to see that documentation is updated to reflect the Developer Membership Board15:32
MootBotACTION received:  Jono to see that documentation is updated to reflect the Developer Membership Board15:32
mdzanything else on the DMB topic?15:32
mdz[TOPIC] patent policy15:33
MootBotNew Topic:  patent policy15:33
mdzalready covered above, including vote15:33
mdz[TOPIC] #15:33
mdzTechnical Board governance review (JonoBacon) - Outstanding Issues documented at https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment15:33
MootBotNew Topic:  #15:33
mdz[TOPIC] Technical Board governance review (JonoBacon) - Outstanding Issues documented at https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment15:33
MootBotNew Topic:  Technical Board governance review (JonoBacon) - Outstanding Issues documented at https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment15:33
=== nhandler changed the topic of #ubuntu-meeting to: Calendar/Scheduled meetings: http://fridge.ubuntu.com/calendar | Logs: https://wiki.ubuntu.com/MeetingLogs and
mdzlet's just go through these one by one15:33
jonowe may be able to tend to these issues on the mailing list15:33
mdz[LINK] https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment15:34
MootBotLINK received:  https://wiki.ubuntu.com/TechnicalBoard/JauntyAssessment15:34
mdzfirst is updating http://www.ubuntu.com/community/processes/techboard15:34
mdzsomebody just needs to take an action to fix this up15:34
mdzso far, I have 2 actions, scott has 1, colin has 1 (carried over), jono has 115:34
sabdflwhere do we stand on the expansion of the TB?15:34
cjwatsonI have had absolutely no luck getting /community/processes/techboard fixed in the past15:35
cjwatsonthe action needs to be newz2000's :P15:35
Keybuksabdfl: nominations received, mdz will contact them to confirm they wish to stand15:35
Keybukwe'll then present the list to you15:35
sabdfli get that part ;-)15:35
cjwatsonwe have exactly five nominations for five seats15:35
Keybukyou acknowledge them/don't15:35
Keybukand then at the next TB meeting, voting opens for the seats15:35
cjwatsondo we still want to open five seats?15:35
Keybukand lasts for two weeks15:35
sabdflbut i'm concerned that 5 nominations doesn't leave much room for a race and larger TB15:35
mdzsabdfl,cjwatson: it was 6 seats15:35
jonosabdfl, agreed15:35
cjwatsonor call for nominations again, more forcefully?15:35
mdzoh, sorry, 5 open seats15:35
cjwatsonyes, the mail says 5 open15:36
jonowould it be possible for us to have seven nominations?15:36
KeybukI though it was 4 open seats?15:36
mdzjono: there is no limit to the number of nominations; we can accept as many as we receive15:36
Keybukjono: we don't *have* seven people to nominate ;)15:36
cjwatsonI'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
mdzjono: we simply haven't received very many15:36
jonoKeybuk, thats what I figured15:36
popeyIf the nomination period was to be extended, I'd like to nominate a non-canonical person..15:36
mdzperhaps the members of the TB would like to put forward more nominees15:37
cjwatsonpopey: if you'd like to send it to technical-board@ *really* quickly*15:37
Keybukso we should agree on some points15:37
popeydone cjwatson15:37
Keybuk- how many seats are open?15:37
popeygah, bounced15:37
Keybuk- who is retaining their seat?15:37
sabdflme!15:38
sabdfland colin15:38
Keybuksabdfl: then that reduces us to 3 open seats15:38
Keybukwith 5 nominations15:38
sabdflthat's not too bad, then15:38
cjwatsonerr, four open seats, not 315:39
Keybukcjwatson: I count 315:39
jonodid we extend an invitation to all core-dev folks?15:39
Keybukno?15:39
cjwatsonthe mail says we wanted to expand to six members total15:39
jonoas in, email them?15:39
cjwatsonsabdfl, me, +415:39
popeycjwatson: sent15:39
Keybukoh, I had 5 in my head15:39
mdzsabdfl: my understanding from the previous meeting was that you were nominating yourself for re-election15:39
cjwatsonyes, I remembered that too ...15:39
sabdfli can do that too15:39
mdzlike Scott and I are15:39
sabdflsure15:40
mdzso 6 seats total minus colin = 5 open seats15:40
cjwatsonoh, you didn't say actually, that explains the confusion15:40
cjwatsonI think the discussion went just past the end of the meeting slot15:40
mdzKeybuk: I think we're clear on those two points. anything else?15:41
Keybuknope, sounds like we're clear15:41
mdzso the only matter is that we'd like to have more nominations15:41
mdzI suggest that the TB try to think of some, rather than just extending the nomination period and hoping for more15:41
jonomdz, I am wondering if all the possible people who could be suitable for the TB know about the election15:41
Keybukjono: I mailed ubuntu-devel-announce ;)15:42
jonowhich is why I was wondering if we should email all core-dev developers directly15:42
mdzjono: it was on -devel-announce, on planet ubuntu, in UWN...15:42
sabdflwe also don't know what the dynamic will be now that developer membership is being delegated15:42
sabdflhopefully, the TB becomes more tech-oriented than team-oriented15:42
sabdfla smaller group may be fine for that15:42
Keybukthat's the plan :-)15:42
mdzjono: 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 couple15:42
sabdflso, we could roll with what we have and see how it goes15:42
jonoKeybuk, sure but I suspect many people miss announcements on -devel-announce15:42
jonoright15:42
Keybukjono: I think that developers missing announcements on the developer announcements mailing list are unlikely to be suitable for the TB15:43
sabdflif we have 5 seats and a Debian representative, that's quite large already15:43
Keybuksabdfl: 6 and a Debian representative15:43
sabdfl6 requires more nominations, 5 doesn't15:43
Keybukok, fair point15:43
jonoKeybuk, 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 updated15:43
jonoupdates15:44
mdzsabdfl: 6 total seats, 5 open for this election15:44
popeyThere wasn't a huge amount of time for nominations..15:44
mdzpopey: two weeks15:44
popeyduring the holiday season..15:44
Keybukjono: 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
jonoKeybuk, ok, no worries :)15:44
=== Ursinha-afk is now known as Ursinha
mdzcan we get back to the assessment now?15:45
cjwatsonI've sent another nomination to techboard15:45
mdzwe need a volunteer to fix the text on the website15:45
cjwatsonI will volunteer if I can have access15:45
mdz[ACTION] Colin to update http://www.ubuntu.com/community/processes/techboard15:46
MootBotACTION received:  Colin to update http://www.ubuntu.com/community/processes/techboard15:46
mdznext item is:Regarding input on key issues such as Pulseaudio, Mono and DX work:15:46
mdzThe TB should determine if they should offer this kid of input and how.15:46
cjwatsonhow should I go about convincing the web team to let me? :)15:46
mdzI think we implicitly agreed this by making the Mono position statement15:46
cjwatsonI guess I'll use my initiative ...15:46
sabdflcjwatson: i can clear a path15:46
mdzcjwatson: and CC me15:46
cjwatsonok, thanks15: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
mdzAFAIC, the fortnightly meeting is an implicit call for topics15:47
mdzthough I wouldn't mind if someone sent out an explicit one a few days prior to the meeting (just not me please)15:47
jonomdz, I think we can better promote the use of the TB for this kind of discussion15:47
Keybukright15:48
sabdflwhy not generate a list and work through them at our leisure15:48
mdzjono: can you set up a process to collect those topics for us?15:48
Keybuknow we've devolved membership powers, we have an hour's meeting every week to discuss such topics15:48
Keybukand a ML15:48
Keybuk;)15:48
sabdflcan we invite non-TB folks to join conversations that they are experts in?15:48
mdzwe have only 10 minutes left, and I actually need to leave 5 minutes early15:48
jonomdz, 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 topics15:48
jonoI am happy to send that message out15:49
sabdfllet's create space on the agenda page, and we choose the order / priority15:49
jonosabdfl, a specific section would be good15:49
mdz[ACTION] Jono to draft text to communicate the TB's willingness to review key topics submitted by the community15:49
jonoI am happy to set that up15:49
MootBotACTION received:  Jono to draft text to communicate the TB's willingness to review key topics submitted by the community15: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
Keybukit'd be nice to include that text on the website15:49
jonoKeybuk, agreed15:49
mdzI'm not too concerned about quorum; this has very rarely been a problem in practice15:50
jonoKeybuk, I will get that done first and then mail cjwatson so he can add it when performing the other site update15:50
mdzjono: sounds good15:50
cjwatsonI don't think we've had a quorum problem since I joined15:50
mdzis anyone else concerned about quorum?15:50
Keybukindeed, Quorum issues have tended to be solved by SMS/Phone calls ;-)15:50
cjwatsonIIRC it was a problem when there were only 315:50
mdzjono: was this something raised specifically during the assessment?15:50
sabdfltimezones in this group make it easier15:50
jonomdz, it was15:50
jonomdz, but I think it's rare enough that we don't need a process15:51
jonolets review at the next UDS if there are quorum issues15:51
mdzo15:51
mdzk15:51
mdzexpansion of the board we already decided15: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:51
KeybukI think Mark's suggestion of approaching the Debian Technical Committee seemed the right lines15:52
cjwatsonTC> I agree15:52
mdzcjwatson: maybe you could talk to people at DebConf?15:52
jonoKeybuk, I was just about to saythe same thing15:52
cjwatsonremind me who the current chair is15:52
Keybukftr, the current membership of the TC is15:52
Keybuk chairman Bdale Garbee15:52
Keybuk     member Russ Allbery15:52
Keybuk     member Don Armstrong15:52
Keybuk     member Andreas Barth15:52
Keybuk     member Ian Jackson15:52
Keybuk     member Steve Langasek15:52
Keybuk     member Manoj Srivastava15:52
cjwatsonI can certainly talk to bdale15:52
mdzcjwatson: bdale15:52
jonoBdale would be fantastic15:53
Keybukjono: however he is somewhat busy being fantastic at a thousand other things15:53
cjwatsonis 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 TB15:53
MootBotACTION received:  Colin to discuss with Bdale (Debian technical committee chair) about having a Debian representative on the Ubuntu TB15:53
jonoKeybuk, lets see if he has the time15:53
mdzcjwatson: 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 Debian15:54
mdzthat's the end of the recommendations15:54
cjwatsonok15:54
mdz[TOPIC] Select a chair for the next meeting15:54
MootBotNew Topic:  Select a chair for the next meeting15:54
KeybukColin again, he volunteered this time but didn't ;)15:54
cjwatsonI think it's my turn isn't it?15:54
mdz[ACTION] Colin to chair next TB meeting15:55
MootBotACTION received:  Colin to chair next TB meeting15:55
* jono laughs15:55
cjwatsonerm, yeah, sorry about that :-(15:55
mdzthanks, all15:55
mdz#endmeeting15:55
MootBotMeeting finished at 09:55.15:55
jonothanks everyone15:55
jono:)15:55
cjwatsonlatency here is sufficiently awful that I would have been a terrible chair anyway15:55
cjwatsonI'm relying on typeahead and a good memory ...15:55
jonocjwatson, I thought your brain was actually directly connected to the Internet :)15:56
sabdflthanks all15:56
cjwatsonthat would be SO FRUSTRATING15:56
jono:)15:56
cjwatsonalso plz to not be introducing security holes into my brain15:56
elkyaww!15:57
* elky puts the security hole away for another time.15:57
* Keybuk knows of a security hole in Colin's brain15:57
* Keybuk starts singing15:57
cjwatsonagadoo?15:57
Keybukmah-nah-mah-nah!15:57
jonohehe15:57
jonolets all DoS cjwatson :)15:57
* Keybuk pushes pineapple15:58
* Keybuk shakes the tree15:58
elkycan this be done while i can actually see his soul get haxXord?15:58
* Keybuk pushes pineapple again15:58
* Keybuk grinds coffee15:59
* hyperair stares at the scrollback and laughs15:59
* sabdfl is completely baffled15:59
* sabdfl *pineapple*?15:59
sabdflcheers all16:00
elkyKeybuk, your mission, if you should choose it, is to kindly differentially baffle our dictator.16:02
* mathiaz waves16:02
sommero//16:02
mathiazHas the TB meeting ended?16:02
jmdaulthello mathiaz16:03
hyperairhttp://www.lyricsdownload.com/black-lace-agadoo-lyrics.html <-- this appears to be what the pineapple's all about =\16:04
popeymathiaz: yes16:04
mathiazallright then - let's get the Ubuntu Server team meeting rolling16:04
mathiaz#startmeeting16:04
MootBotMeeting started at 10:04. The chair is mathiaz.16:04
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:04
mathiazToday's agenda: https://wiki.ubuntu.com/ServerTeam/Meeting16:04
mathiazLast week minutes: https://wiki.ubuntu.com/MeetingLogs/Server/2009072116:05
mathiaz[TOPIC] SRU tracking on server-related packages16:05
MootBotNew Topic:  SRU tracking on server-related packages16:05
mathiazSo I've asked bdmurray about a script to get the list of bugs marked fixed released during a previous week16:05
mathiazhe said he almost had such a script16:06
mathiazI need to follow up with him and see how and where we can run this script16:06
mathiaz[ACTION] mathiaz to follow up with bdmurray about the list of fixed released bugs related to the ubuntu-server team.16:07
MootBotACTION received:  mathiaz to follow up with bdmurray about the list of fixed released bugs related to the ubuntu-server team.16:07
mathiazanything else to add on this topic?16:07
zulare we going to review it every week at the meeting?16:08
zulor should it be an automated email to the server mailing list?16:08
mathiazzul: let's start by a weekly review in this meeting16:09
mathiazzul: if this takes too much time, we can always move it to the mailing list16:09
zulk16:10
mathiazanything else related to this topic?16:10
mathiaznope - let's move on16:11
mathiaz[TOPIC] Preparing a 2009 edition of the Server Survey16:11
MootBotNew Topic:  Preparing a 2009 edition of the Server Survey16:11
mathiaznijaba wrote up a blog post about it: http://nicolas.barcet.com/drupal/en/preparing-2009-server-survey16:11
mathiazanything else to add to this topic?16:12
mathiaznope - let's move on16:13
mathiaz[TOPIC] Ubuntu HA team: Cluster stack update16:14
MootBotNew Topic:  Ubuntu HA team: Cluster stack update16:14
mathiazneither RoAkSoAx nor ivoks seem to be around16:14
mathiazon a related note Debian has moved to DKMS for the drbd package16:15
mathiazand the latest version of drbd has been synced in karmic this morning16:15
mathiazcongratulation to ivoks for driving this packaging effort in both Debian and Ubuntu16:15
* sommer cheers16:16
mathiazivoks told me yesterday he was now focusing on packaging the pacemaker+openais+... stack for karmic16:17
mathiazanything else to say on the cluster stack?16:17
mathiazit seems not. Let's move on.16:18
mathiazThat's all I had from last week minutes.16:19
mathiazAnything else to add related to last week meeting?16:19
mathiazseems not - let's move on.16:20
mathiaz[TOPIC] Mysql 5.1 in karmic main16:20
MootBotNew Topic:  Mysql 5.1 in karmic main16:20
mathiazDebian unstable saw the upload of 5.1 into unstable last weekend16:21
mathiazand thus transition to libmysql16 has started in unstable.16:21
mathiazThe question is whether we should do the same in karmic now?16:21
zuli dont see why not16:22
mathiazThe two blockers I had when I looked at moving 5.1 into main a couple of week ago were:16:22
mathiaz1. the test suite was not enabled during build time, while it was in 5.016:22
mathiaz2. the cluster engine is not available in 5.1 while it is in 5.016:22
zulis there a reason why it was disabled?16:22
mathiazzul: because it wasn't successful?16:23
mathiazzul: because it wasn't successful.16:23
zulpretty good reason16:23
mathiazzul: hm well - what are you refering to 1 or 2?16:23
zulboth probably16:23
mathiazFor 2. one solution could be to add a check in pre and see if the ndb engine is used16:25
mathiazif so the upgrade would abort and suggest to remove mysql-server16:25
mathiazand leave mysql-server-5.016:25
mathiazand leave mysql-server-5.0 installed on the system16:25
zulsounds reasonable16:25
mathiazas transitionning from 5.0 to 5.1 in karmic main means that mysql-server would be provided by 5.1 instead of 5.016:26
mathiazThe kubuntu team also would like to move to 5.1 as it would simplify the packaging of amarok16:27
mathiazand it seems that we'd want to have 5.1 for the next LTS16:27
mathiazuploading 5.1 to main now would mean going through another library transition - I wonder if it's not too late in the release cycle16:28
zulhow many libraries are affected again?16:28
zulif its alot then it would be just a matter of going to motu's saying we need help to transition mysql libraries to 5.116:29
mathiazzul: well - not really - only packages in main would have to be transitioned in karmic16:29
mathiazzul: as we could keep 5.0 in universe for this release cycle16:29
zultrue16:30
mathiazzul: in debian there are around 160 pkg IIRC16:30
mathiazzul: but there isn't a difference between main and universe16:30
zulbut this would also be an opprotunity to help debian out as well16:30
mathiazI've check point 1 (test suite not enabled in 5.1) and it's not true anymore16:30
mathiazthe test suite is run at build time IIUC16:31
mathiazso the only blocker I have is point 2 and we have a workaround for karmic.16:31
mathiazso I think the next step is to send an email to ubuntu-devel to discuss the transition to mysql 5.1 in main16:31
mathiazand file a MIR for 5.116:32
mathiazwhich may take some time to get processed.16:32
zulcool beans16:32
mathiazanything else to add?16:32
mathiaz[ACTION] mathiaz to send an email to ubuntu-devel about moving 5.1 to main16:33
MootBotACTION received:  mathiaz to send an email to ubuntu-devel about moving 5.1 to main16:33
mathiazlet's move on.16:33
mathiaz[TOPIC] Cloud power management16:33
MootBotNew Topic:  Cloud power management16:33
mathiazkirkland: ^^16:33
mathiazkirkland: anything new on this front?16:33
kirklandmathiaz: howdy o/16:33
kirklandmathiaz: not much since last week, really16:33
kirklandmathiaz: i expect that the functionality is basically done for karmic16:34
kirklandmathiaz: and i've moved into test-mode16:34
mathiazkirkland: allright - feature complete, testing required.16:34
kirklandmathiaz: yessir!16:34
mathiazkirkland: are you looking for specific hardware?16:34
mathiazkirkland: are there any test instructions?16:34
kirklandmathiaz: yes, still looking for a rackable server that has S3 in /proc/acpi/sleep16:35
kirklandif you are in possession of one of these, let me know :-)16:35
mathiazkirkland: are you focusing on hardware support testing or software testing?16:36
kirklandmathiaz: software testing of PowerNap and PowerWake16:36
kirklandmathiaz: i considered the work I did testing suspend/hibernate/resume in Jaunty to verify the hardware support16:36
mathiazkirkland: I'd suggest to talk to cr3 - he may have some hardware available16:36
kirklandmathiaz: okay16:37
mathiazanything else to add to this topic?16:38
kirklandmathiaz: nope, not really16:38
mathiazok. Let's move on.16:38
mathiaz[TOPIC] Ubuntu Server Gudie16:38
MootBotNew Topic:  Ubuntu Server Gudie16:38
mathiaz[TOPIC] Ubuntu Server Guide16:38
MootBotNew Topic:  Ubuntu Server Guide16:38
mathiazsommer: ^^16:38
mathiazsommer: how is it going on this front?16:38
sommermathiaz: slowly but surely... been busier than normal with the day job and real life16:40
sommermathiaz: I think everything in the blueprint should get done though :)16:40
mathiazsommer: awesome - what are the deadlines?16:40
* RoAkSoAx waves16:41
mathiazsommer: has the doc team changed the milestones this release cycle?16:41
sommerDoc Freeze is Oct 1st16:41
sommermathiaz: nope as far as I know the milestones are the same16:41
mathiazsommer: ok - keep up the good work!16:42
mathiazsommer: and ask around for some help16:42
mathiazsommer: 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
sommermathiaz: ya, I've been meaning to do a blog post about the new sections16:42
sommerhttps://wiki.ubuntu.com/KarmicServerGuide is the spec16:43
mathiazsommer: great!16:43
mathiazanything else to add on the topic of documentation?16:44
sommerthink that's it for me16:44
mathiazallright - let's move on then.16:45
mathiaz[TOPIC] Ubuntu HA team: Cluster stack update16:45
MootBotNew Topic:  Ubuntu HA team: Cluster stack update16:45
mathiazRoAkSoAx: now that you're around - I've given a quick status update earlier in the meeting16:45
mathiazRoAkSoAx: did you get a chance to update the Roadmap?16:46
RoAkSoAxmathiaz, yes: https://wiki.ubuntu.com/UbuntuHighAvailabilityTeam/Roadmap16:46
mathiazRoAkSoAx: with a brief overview of what needs to be done16:46
RoAkSoAxWell 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 it16:47
mathiazRoAkSoAx: awesome thanks.16:47
mathiazRoAkSoAx: great - and then all of these packages need to be synced in karmic?16:47
RoAkSoAxmathiaz, yes16:48
mathiazok - anything else to add related to the Cluster stack?16:49
RoAkSoAxwe 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 changes16:49
RoAkSoAxand that would be it16:49
mathiazRoAkSoAx: great - keep up the good work.16:50
mathiazRoAkSoAx: and once the packages are in Ubuntu, I'd suggest to write up a blog post to ask for more testing16:50
mathiazlet's move on.16:50
mathiaz[TOPIC] Open Discussion16:51
MootBotNew Topic:  Open Discussion16:51
mathiazAnything else to add?16:51
jmdaultmathiaz: I'm back from vacation and resuming work on Asterisk16:52
mathiazjmdault: great!16:52
mathiazjmdault: are you up-to-date on what happened in Debian in the mean time?16:52
mathiazjmdault: (I'm not)16:53
jmdaultIt's more work than I expected, I will have to work with Debian in making newer packages16:53
jmdaultmathiaz: nothing has changed on the Debian side. The dahdi drivers are still 2.0-rc516:53
jmdaultBut the final 2.0 are out from digium, and it fixes some kernel panics16:53
mathiazjmdault: ok - is there a wiki page where the plans for Karmic are recorded/outlined?16:53
jmdaultmathiaz: not yet16:54
mathiazjmdault: it may be worth spending some time to write a short description of the plan for karmic16:56
mathiazjmdault: and get in touch with the debian team to work together.16:56
mathiazanything else to add before we wrap up?16:56
jmdaultmathiaz: https://wiki.ubuntu.com/AsteriskIntegration ?16:56
mathiazjmdault: looks like a good place16:56
mathiaz[TOPIC] Agree on next meeting date and time16:57
MootBotNew Topic:  Agree on next meeting date and time16:57
mathiaznext week, same place, same time?16:57
sommer+116:58
mathiazallright then.16:59
mathiazsee you all next week, same place, sime time.16:59
mathiaz#endmeeting16:59
MootBotMeeting finished at 10:59.16:59
sommerthanks mathiaz, later all17:01
=== JamalFanaian is now known as JamalFanaian|afk
=== ejat is now known as e-jat
DavieyGah!  missed the meeting17:12
=== ogasawara_ is now known as ogasawara
bjfRoll Call17:59
* manjo waves18:00
liebhi18:00
* ogasawara waves18:00
* rtg_ is herwe18:00
* apw waves18:00
* jjohansen waves18:00
* awe waves18:00
* cking is here18:00
* gnarl reports in for smb18:00
bjf#startmeeting18:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting18:01
MootBotMeeting started at 12:01. The chair is bjf.18:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting18:01
bjf[TOPIC] Open Action Items: (apw) Close Blueprints: kernel-karmic-kernel-config-review18:01
MootBotNew Topic:  Open Action Items: (apw) Close Blueprints: kernel-karmic-kernel-config-review18:01
* pgraner waves18:01
apwThat 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
MootBotNew Topic:  Open Action Items: (smb) Organise a sprint session on review of "Blueprint: kernel-karmic-kernel-config-review"18:01
bjfgnarl?18:02
gnarlok18:02
gnarlsort of put it into a agena i think18:02
* amitk appears belatedly18:02
* rtg_ is really tired of reviewing configs.18:02
bjf[TOPIC] Open Action Items: (apw, rtg) Sync with J. Johansen before upload on AA enablement18:03
MootBotNew Topic:  Open Action Items: (apw, rtg) Sync with J. Johansen before upload on AA enablement18:03
rtg_bjf, done18:03
apwIt 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 task18:03
MootBotNew Topic:  Open Action Items: (apw) Close the 386 flavour task18:03
apwThat is closed off18:03
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic18:03
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic18:03
bjf[TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)18:03
MootBotNew Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs)18:03
ogasawaraRelease Meeting Bugs (3 bugs) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic18:03
ogasawaraRC Milestoned bugs - none so far for Alpha 418:03
ogasawaraRelease Targeted Bugs (5 bugs) - https://bugs.edge.launchpad.net/ubuntu/karmic/+source/linux18:03
bjf[TOPIC] Karmic Release Status: Milestoned Features18:04
MootBotNew Topic:  Karmic Release Status: Milestoned Features18:04
ogasawarahttps://launchpad.net/ubuntu/+milestone/karmic-alpha-418:04
bjf[TOPIC] Blueprints: kernel-karmic-hwdb-workshop (ogasawara)18:05
ogasawarait looks like the one that concerns are team has been Implemented by Tim (Karmic kernel flavours)18:05
MootBotNew Topic:  Blueprints: kernel-karmic-hwdb-workshop (ogasawara)18:05
ogasawarabjf: nothing new to add for hwdb18:05
rtg_ogguess I should update its status18:05
rtg_ogasawara, ^^18:05
ogasawarartg_: it's already marked as Implemented18:05
rtg_ogasawara, indeed it is.18:06
bjf[TOPIC] Blueprints: kernel-karmic-kms (apw)18:06
MootBotNew Topic:  Blueprints: kernel-karmic-kms (apw)18:06
apwTesting 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:06
bjf[TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts (rtg)18:07
MootBotNew Topic:  Blueprints: kernel-karmic-new-kernel-on-lts (rtg)18:07
rtg_no progress, see last week18:07
bjf[TOPIC] Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)18:07
MootBotNew Topic:  Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)18:07
gnarlno progress since last week18:07
bjf[TOPIC] Blueprints: kernel-karmic-android (coolony)18:07
MootBotNew Topic:  Blueprints: kernel-karmic-android (coolony)18:07
rtg_apw, what about drbd? ivoks said there is a DKMS package for it18:07
bjfno progress since last week (speaking for coolony)18:08
apwrtg_, the original source is dkms aware ... we have an updated version in ubuntu/ for now18:08
apwnoone has stepped up to own a dkms package to my knowledge18:08
rtg_apw, right, its up-rev from the DKMS version18:08
bjf[TOPIC] Blueprints: kernel-karmic-sponsoring-staging-drivers (smb)18:09
MootBotNew Topic:  Blueprints: kernel-karmic-sponsoring-staging-drivers (smb)18:09
gnarlstalled18:09
bjf[TOPIC] Blueprints: kernel-karmic-suspend-resume (manjo)18:09
MootBotNew Topic:  Blueprints: kernel-karmic-suspend-resume (manjo)18:09
apw[ACTION] apw, check up on drbd status in dkms package and kernel18:09
manjoplan on doing a laptop testing session at the dublin meet18:09
ckingtested those images yet? :-)18:09
manjoput together a test plan on testing18:10
manjowill be testing kms & suspend/resume18:10
manjocking, still downloading18:10
cking'k18:10
bjf[TOPIC] Blueprints: kernel-karmic-wifi (rtg)18:10
MootBotNew Topic:  Blueprints: kernel-karmic-wifi (rtg)18:10
rtg_making progress on rfkill18:11
rtg_there are some kernel patches in the pipeline that'll help acpi-support18:11
bjf[TOPIC] Blueprints: kernel-karmic-better-power-mgt (amitk)18:11
MootBotNew Topic:  Blueprints: kernel-karmic-better-power-mgt (amitk)18:11
amitkno progress since last week18:11
bjf[TOPIC] Other Release Tasks: AppArmor (jjohansen)18:11
MootBotNew Topic:  Other Release Tasks: AppArmor (jjohansen)18:11
jjohansenclosed out my clone regression18:11
jjohansenstill have ecryptfs regression to fix 35933818:12
apwjjohansen, do we already have the clone fix in the batch i added last week18:12
apwor is there more coming?18:12
jjohansenmore coming, I am still testing through the x cases on the clone but it all looks good so far18:12
rtg_jjohansen, have you had time to think about the next merge window?18:13
apwmost excellent, thats the last regression i believe from the test suite18:13
bjf[TOPIC] Other Release Tasks: ARM-Freescale (amitk, bjf)18:13
MootBotNew Topic:  Other Release Tasks: ARM-Freescale (amitk, bjf)18:13
jjohansenrtg_: yeah, a little18:13
amitkfirst set of patches (from Jaunty) was integrated into Karmic and a kernel is available in the archive18:14
bjfFreescale stuff for me is in place, nothing new, waiting for next patch drop18:14
bjfshould be this week I think (maybe next)18:14
amitkworking on the second set of patches (130) now. Hope to finish them by end of this week18:14
amitkalso working with ogra to figure out why DVI doesn't work on Karmic18:15
amitkDVI on babbage 2 boards, that is18:15
amitkthat's it18:15
bjf[TOPIC] Other Release Tasks: Union Mount Solution (apw)18:15
MootBotNew Topic:  Other Release Tasks: Union Mount Solution (apw)18:15
apwaufs2 testing on livecd seems good.  Pulled in updated aufs2 sources from aufs mainline bringing in a number of bug fixes, uploaded for testing.18:15
apwActivity ramping back up on vfs union mounts, but not going to be anywhere near .31 ready18:16
bjf[TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb/gnarl)18:16
MootBotNew 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 booting18: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 verifications18:16
gnarl* Jaunty:   2.6.28-13.45 (security)18:16
gnarl            2.6.28-14.46 (proposed)[20] with 4/15 verifications18:16
gnarl            ABI bumping versions of LRM and LBM waiting as well18:16
gnarlNo progress on verifications for Intrepid and Jaunty. This delays the18:17
gnarlmove to updates for those.18:17
apwgnarl, is there something we can do to poke the reporters18:17
apwon the bugs which need verification?  perhaps getting the arsenal to do it automatically?18:17
apwogasawara, ?18:17
gnarlprobably nothhing more thann go to the bugs and repeat18:17
gnarlbut they get a notification normally18:17
ogasawarayup, I could have a script stock reply them to test18:17
bjf[TOPIC] Status: Karmic (rtg, apw)18:18
MootBotNew Topic:  Status: Karmic (rtg, apw)18:18
gnarlRight, maybe we could "remind" them after 7 days18:18
apwlets talka bout it at sprint18:18
apwKamic 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 imminent18:19
bjf[TOPIC] Status: ARM (amitk, bjf)18:19
MootBotNew Topic:  Status: ARM (amitk, bjf)18:19
amitknothing else to add. This Status should perhaps be removed18:20
bjfMarvell has applied their patches to a 2.6.31-rc4 git repo, I'm reviewing the patches and will request a pull soon.18:20
bjfI 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 do18:21
apwhurry else we'll have moved to -rc5 ;)18:21
bjfthis is another HUGH patchset (250+ patches)18:22
* apw goes bling18:22
bjf[TOPIC] Status: Netbook (sconklin, apw)18:22
MootBotNew Topic:  Status: Netbook (sconklin, apw)18:22
apwblind18:22
sconklinNo new status since last week.18:22
bjf[TOPIC] Incoming Bugs: Regressions (ogasawara)18:22
MootBotNew Topic:  Incoming Bugs: Regressions (ogasawara)18:22
ogasawara5 regression-potential and 1 regression-release bugs were added this week18:22
ogasawaraone has been resolved with the 2.6.31-4 kernel and another will likely be resolved after the next upload.18:23
ogasawaraI'll also start joining apw and smb on their weekly regression bug call18:23
bjf[TOPIC] Incoming Bugs: Bug day report (ogasawara)18:24
MootBotNew Topic:  Incoming Bugs: Bug day report (ogasawara)18:24
ogasawaraHighlight is we closed 31 bugs from the weekly kernel bug list.18:24
ogasawaraRefer to http://qa.ubuntu.com/reports/ogasawara/kernel-bugday/20090721.html for the complete bug day stats.18:24
ogasawaraI'm going to send an announcement that we'll cancel next week's bug day since everyone will be at the sprint18:24
gnarlgood point18:24
bjf[TOPIC] Open Discussion or Questions: Anyone have anything?18:25
MootBotNew Topic:  Open Discussion or Questions: Anyone have anything?18:25
* ogasawara raises hand18:25
ogasawaraThe issue of unwatched packages (ie no one is subscribed to the bug mail) was recently brought to my attention.18:25
ogasawaraSpecifically one package kernel-wedge was thought to be the responsibility of the kernel team but is currently unwatched.18:25
apwwhich packages you thinking of18:25
ogasawaraIs it okay if the kernel team is subscribed to this package?  It currently has 1 bug so is extremely low traffic18:25
apwi had a look at kernel-wedge and there is only one bug there18:26
gnarlso it is quite safe to add18:26
rtg_ogasawara, I really want cjwatson to own kernel-wedge18:26
apwthat seems appropriate to me18:26
ogasawarartg_: ack, I'll propose he be subscribed then18:26
rtg_kernel-wedge is all about producing udebs for the installer18:27
bjfanyone else have anything they want to bring up?18:27
ckingwe could do with some kernel team know-how on kernel wedge18:27
rtg_cking, I know enough to be scared of it18:27
ckingagree18:28
rtg_its real quirky18:28
bjfgoing....18:28
bjfgoing .....18:28
=== fader_ is now known as fader|lunch
bjfAre we going to have an IRC meeting next week? (Sprint week)18:29
rtg_bjf, I suggest we cancel it18:29
cking+1 on that18:29
apwseems reasonable to me18:29
bjfok no meeting next week18:30
gnarl+118:30
bjf[TOPIC] Next Meeting Chair: Colin King18:30
MootBotNew Topic:  Next Meeting Chair: Colin King18:30
ckingack18:30
apwand two weeks to forget :)18:30
bjf#endmeeting18:30
MootBotMeeting finished at 12:30.18:30
ckingI won't!18:30
apwwill18:31
cjwatsonogasawara: I've subscribed ubuntu-installer to kernel-wedge18:39
cjwatsonthat's better than me personally18:39
ogasawaracjwatson: great, thanks!18:39
=== WelshDragon is now known as Fluffles
=== fader|lunch is now known as fader_
=== JamalFanaian|afk is now known as JamalFanaian
=== JamalFanaian is now known as JamalFanaian|afk
=== RoAk is now known as RoAkSoAx
=== fader_ is now known as fader|away
=== RoAk is now known as RoAkSoAx
bodhi_zazen5 min =)23:56
=== nhandler is now known as info
=== info is now known as nhandler

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!