/srv/irclogs.ubuntu.com/2009/09/08/#ubuntu-meeting.txt

=== m4v_ is now known as m4v
=== hggdh_ is now known as hggdh
=== ecanto is now known as edson
DKcrossjono, :)06:34
jonohey DKcross :)06:34
DKcrosshey jono how are you?06:35
jonoDKcross, good thanks, you?06:37
DKcrossgood :D06:37
DKcrosstesting karmic koala :\06:37
DKcrossare you testing?06:38
=== dholbach_ is now known as dholbach
=== Ng_ is now known as Ng
indushi10:12
indusneed some help10:12
Davieyindus: what with?10:12
indusubuntu membership10:13
indusi am trying asia oceania region but i dont know how to contact them10:13
indushttps://wiki.ubuntu.com/Membership/RegionalBoards/AsiaOceania10:13
indusits not updated and dont list contact info10:13
Davieyindus: they'll be here in 45 mins, if that helps? :)10:15
indusoh really? super10:15
induswhy here? whats today? some meeting?10:16
Davieyindus: "The next meeting is scheduled for 08-Sep-2009, 10:00 UTC and will be held in #ubuntu-meeting"10:16
czajkowskiindus: you still lost :)10:17
indusczajkowski: lol yeah10:17
indushello10:17
czajkowskithis going on now for about 2 weeks,10:17
czajkowskiindus: did you contact any of the board members, popey gave you the email address10:17
indusczajkowski: ya did 1,but no reply10:17
indusczajkowski: so iam not sure if they will attend the meeting today here10:18
czajkowskiindus: unless the mail is waiting moderation I stil suggest contacting one of the board members and leave them an IRC message or email10:18
indusleave an irc message hmm how do i do that10:19
czajkowski /msg nick bleugh10:19
czajkowskiindus: so find a board member on the list, and find user nick on the lp ac10:19
indusczajkowski: i think i tried a few,but they dont seem to be in here at some time or other10:20
popeyindus: there is a link on that page which does have contact details10:20
industhere is a melissa draper10:20
popeythe first link10:20
induswait10:20
popeyhttps://launchpad.net/~ubuntu-membership-board-asia-oceania10:20
czajkowskiindus: that;s elky10:20
popeythat lists members of the team, which you can also click on10:20
popeyto find their irc nicknames, and potentially their email addresses too10:21
* Daviey notes that "Email: No contact email" should probably be resolved :)10:21
popeynot really10:21
popeyyou can click the contact link and it will send to all members of the team10:21
Davieyrly?10:21
popeyya rly10:21
Daviey    Contact this team's owner10:22
DavieyOwner:10:22
Daviey    Ubuntu Community Council10:22
popeyhm10:22
popeythats suboptimal :)10:22
Davieyexactly :)10:22
industeam owner is mark shuttleworth so i dont want to disturb him10:22
popeyyou dont need to10:22
popeythe members are listed as I said10:22
popeyhttps://edge.launchpad.net/~ubuntu-membership-board-asia-oceania/+members#active10:23
czajkowskiindus: do let us know how you get on, curious after 3 weeks of trying ;)10:23
czajkowskifair duce to you10:23
popeyand to be fair...10:24
popey08:42:29 < indus> guys i need your help10:24
popey08:47:22 < hyperair> wrong place. /join #ubuntu10:24
popeythat wasn't exactly helpful10:25
hyperairhmm?10:25
popeynvm, the moment has passed10:25
indusi messaged elky10:28
popeycool10:28
indusshe is away10:28
indusi try another maybe10:28
popeyalthough you could technically talk to any of the membership boards10:28
popeytry me :)10:28
induspopey: hello ,i need help with membership10:28
* Daviey wonders if this conversation would be better suited elsewhere :)10:28
popeyif it's about asia team scheduling then they're best people to speak to, if it's a general membership question I can probably help10:29
popeyDaviey: hang on10:29
popeylets find out what the question is first10:29
popeyindus: whats the specific details of your required help10:29
induspopey: i want to become an ubuntu member10:29
popeyok, great!10:29
popey!member10:29
ubottuWant to become an Ubuntu member? Look at http://www.ubuntu.com/community/processes/newmember10:29
popeythats a good starting page, have you seen it before?10:29
induspopey: i followed wiki , and thanks to czajkowski i added all formalities10:29
czajkowskiindus: you've done all the stuff last week we went through right, the coc, lp ac, and wiki. so you're just needed to sign up to a review board10:30
popeyok, great10:30
popeyso the next step is to choose a board and add your name to their wiki page10:30
popeythen attend their meeting via irc10:30
induspopey: also did10:30
popeyok10:30
induspopey: asia oceania'10:30
popeyso whats the question ? :)10:30
czajkowskipopey: he was trying that, but their pages hasnt been updated to know when the next meeting is on10:30
popeythe page says its in 30 mins10:31
indushttps://wiki.ubuntu.com/Membership/RegionalBoards/AsiaOceania10:31
popeyThe next meeting is scheduled for 08-Sep-2009, 10:00 UTC and will be held in #ubuntu-meeting on irc.freenode.net.10:31
popeyits now 09:30 UTC10:31
indushmm interesting, it was updated now i believe10:31
indusfew hours before it wasnt10:31
indusso will meeting be in here then?10:32
czajkowskiindus: so you're set :)10:32
induswow cool10:32
popeyit was updated yesterday10:32
popeyhttps://wiki.ubuntu.com/Membership/RegionalBoards/AsiaOceania?action=diff&rev2=170&rev1=16910:32
induspopey: hmm well, persistence of vision happened to me i think10:32
popeyhehe10:33
popeyit happens10:33
indus:) ya i was on that page and i kept seeing august 1110:33
popeyI tend to subscribe to pages I am interested in10:33
popeythen I get an email when they get updated10:33
popeyit's a useful feature of the wiki we use10:33
indusso what do you folks do for work10:34
popeythis isn't really a "chat" channel as such. You might get more/better responses in one of the loco team channels10:36
indushmm i thought ill get to know the members10:37
indusnvm10:37
popeyor indeed #ubuntu-locoteams where pretty much everyone who has spoken in the last hour or so hangs out :)10:37
induspopey: but meeting will happen here?10:37
popeyyes10:37
induswho keeps record or minutes of the meeting10:51
czajkowskiindus: the room is logged10:52
czajkowskihmm dpm may have forgotten to change the topic in here since last week10:52
indusok has meeting begun?11:01
indusits time isnt it11:01
zirodayindus: not yet, you'll know when its started don't worry11:01
indusits 10 utc11:01
indusok i wait11:01
amachupersia: elky: lifeless: Hi11:02
indusaah amachu11:03
indusprobably they are reviewing my membership :)11:07
indusfrom wiki i mean11:07
amachupersia, elky, lifeless: Hello11:08
induswhy does he keep quitting11:12
czajkowskiconnection?11:12
induslet me call him11:13
indushi11:18
amachuindus, Hi11:20
amachuwe need a quorum to continue the meeting11:21
indusok11:22
amachupersia, elky, lifeless: there?11:23
indusso now what11:25
amachuindus, We need four of us present to take up membership considerations11:25
amachuindus, else we have to take it up in next meeting11:28
indusso why arent anyone here then11:28
indusshouldnt someone update on the wiki if they are not available11:29
indusnext meeting will be when then amachu11:29
amachufourth tuesday11:31
indushmm ok but can you be sure there will be at least 4 of you here?11:31
amachuwell, people of the board are from different countries, India, Australia, Japan11:32
indusamachu also, what do i need to make my membership application stronger?11:32
amachuand we cover a vast geography..11:32
zirodayindus: you are aware that if you don't find it convenient to meet with the Asia/Oceania board you are free to request membership from any of the other two boards11:32
indusziroday: yes aware11:33
zirodayindus: :)11:33
indusziroday: probably ill be trying that next11:33
amachuindus, your wiki lack references to your claims11:33
indusziroday: just wanted to irritate the asia members first :D11:33
indusamachu hmm ok11:33
indusamachu wait11:34
amachuindus, we would like to see more of your Ubuntu specific contributions than rest11:34
indusamachu well , all of the workshops we do ,the focus is on ubuntu11:34
amachuand some testimonials favouring your membership or people present here at the time of meeting to endorse your work11:34
indusamachu and we distribute cds to all of them, and now, we are supporting mozilla service week with free ubuntu installs11:35
indusmaybe ill add ngoinabox site link to wiki?11:35
amachuindus, not here, make it in the wiki, and turn back next time..11:35
indusi was afraid of spam so i didnt11:35
czajkowskiNgo in a box?11:35
indusyeah11:35
indusyou know of it?11:35
amachuwe regret for the caused to you, time11:35
czajkowskiindus: pop into -locoteams or -ngo will you, meeting isn't going to take place in here11:36
amachu we regret for the inconvenience caused to you, this time11:36
indusya ok np11:36
indusbye folks11:37
indusamachu thanks11:37
amachuindus, you are welcome :-)11:38
elkyoh crap, sorry. a friend was flying through and i forgot it was this tuesday :(13:03
=== zul_ is now known as zul
=== fader|away is now known as fader_
=== imlad|away is now known as imlad
=== marjomercado is now known as marjo
loolHola14:00
loolI didnt think Michael was on leave14:01
paulliuhi14:01
loolplars, ogra, dyfet: ping14:02
plarsyep, here14:02
ogramoop14:02
bjfhere14:02
loolHey Brad14:02
dyfethi14:03
loolnjpatel: Hey!14:03
lool#startmeeting14:03
MootBotMeeting started at 08:03. The chair is lool.14:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:03
njpatelhey hey14:03
loolCrap the meeting link is out of date14:03
loolImagine https://wiki.ubuntu.com/MobileTeam/Meeting/2009/20090908 here14:03
StevenKfour-oh-four14:04
loolI'll co NCommander's items14:04
loolStevenK: Hence the need for your imagination   :)14:04
loolGrueMaster isn't here eithre14:05
looldyfet: You had an action to get lxde-meta sponsored14:05
loolBut I understand that's blocked on the FFE?14:06
dyfetYes14:06
loolOk; that's all we had for last week14:06
loolMoving to specs review14:06
lool[topic] specs review14:06
MootBotNew Topic:  specs review14:06
loolhttp://piware.de/workitems/mobile/karmic/report.html14:06
MootBotLINK received:  http://piware.de/workitems/mobile/karmic/report.html14:06
loolThe graph looks better for various reasons14:06
loolmobile-unr-karmic-applications > needs gruemaster to comment14:07
loolStevenK: Do you know whether gwibber is going in desktop or not after all?14:07
StevenKlool: I do not14:07
loolbjf: mobile-karmic-marvell-desktop > are you aware of any work with respect to CONFIG_s which is still pending?14:07
loolbjf: or are there any reported issues with the dove kernel in karmic?14:08
loologra: Only an oem-config item remaining for this spec to be completed for karmic: mobile-arm-karmic-offline-installer-gui14:08
bjflol, no issues that I'm aware of, continue to look at CONFIG_s but at this point we are probably good14:08
ograyep14:08
loologra: Could you get to that today so that we can mark it implemented?14:08
ograno14:08
bjflool, **14:08
loolbjf: excellent thanks14:08
loolbjf: Yeah it wasnt very funny so I figured it was for me14:09
ograi need a lot of test builds for that, its very time consuming14:09
loolmobile-karmic-armel-toolchain > looking good; no big regressions except oo.o14:09
bjflool, 6am here, just woke up, can't type yet14:09
loologra, dyfet: Did you notice any other regression in the ftbfs lists?14:09
* ogra ponders to defer the oem-config stuff in favor of qemu-arm-static14:09
loolOr is oo.o the only package hit by the toolchain changes?14:09
ograeigen seems to have probs14:10
loologra: new problems?14:10
ogranot sure thats toolchain though14:10
ogranope14:10
loolok14:10
loolStevenK: You were testing wubi with UNR but that failed14:10
loolStevenK: Did that get fixed?14:10
ograeglibc ftbfs but doko preferred to care for that14:10
ograand gst-pliguns-good14:10
loolActually doko sent a list of work items on glibc14:10
dyfetno either....14:10
ogra*plugins14:11
loolI'm happy to share it if some people have time to take care of some of them14:11
StevenKlool: Not as I'm aware, I'll talk to evand about it14:11
loolStevenK: Do we have a bug for the unr wubi issue?14:11
StevenKlool: No, I don't think so14:12
loolmoblin remix > I just updated status, we asked for a FFE to allow merges into karmic14:12
loolStevenK: Could you please file one asap?14:13
loollsb-compliance > seems to lack A5 update; need gruemaster to clarify14:13
loolunr-translations > I've sent merge requests for all translated modules14:13
loolplars: mobile-unr-karmic-compliance-autotesting > on track for A6?14:14
plarslool: yes14:14
plarsjust adding tests at this point14:14
loolplars: There were some chats about updating test plans and getting coverage reports on execution of test cases for Ubuntu alphas; are the UNR and ARM testcases/test plans on http://testcases.qa.ubuntu.com/ already?14:15
loolthis was between mdz and qa + release teams IIRC14:15
ograplars, since you do a lot of checkbox stuff, did you ever test checkbox on babbage or dove ?14:15
plarslool: I was unaware of that... testplans are on testcases.qa, individual tests are mostly going into checkbox14:15
loolplars: Ok14:16
plarsogra: yes, I do use checkbox on armel as well14:16
ograintresting, how does it work ?14:16
loolplars: I think we want the test plans to be in very good shape for next alpha14:16
plarsexcept for some things14:16
plarsi.e. boot loader test, etc... obvious stuff14:16
ogragiven neither dove nor imx51 expose a pci bus14:16
loolCause it's going to be a big focus that we actually test each test case in full14:16
ograso i guess it wont find much HW14:16
loolmobile-karmic-arm-cloud-builds > no progress, i suck  :-(14:17
plarsogra: right, it would just miss some things like that in the report14:17
ograsmoe things ? :)14:17
plarspci14:17
ogralike all hardware ? :)14:17
plarsusb should work14:17
ograright14:17
plarsdisks, etc14:17
loolAny other questions for spec review?14:18
lool[topic] UNR status14:18
MootBotNew Topic:  UNR status14:18
loolStevenK: I think we're pretty much up to date with seeds14:19
StevenKIndeed14:19
loolI just checked and didn't see any functional change since evo-couch14:19
loolStevenK: I think you can readd some langpacks just like the desktop team did14:19
loolwe're at 680M14:19
loolHmm actually is 712730624 oversize?14:19
loolnjpatel: So 5 new tarballs released today IIUC14:20
loolStevenK said he will pick them up14:20
* ogra wonders if we should bump armel to 1G ... we're still using .img there and thats unlikely to change any time soon14:20
njpatellool: yep, definitely by EOD14:20
ograso we could ship an extra ton of langs14:20
njpatellool: will mail you, steve and ubuntu-mobile as per usual14:20
loolWe want translations if possible since otherwise you'll have to reroll tarballs == pain14:20
loolnjpatel: Ok cool14:20
loologra: Not sure, 700 M might be the actual limit14:21
ogranot for .img14:21
loolStevenK: Could you please check that and perhaps add langpacks14:21
ograi changed that weeks ago14:21
loologra: oh for ARM, sure14:21
ogra.img files are 1G14:21
loolfeel free14:21
ograwill need some seed fiddling14:21
loolI was discusing *UNR* status which is why I was confused14:21
StevenKlool: I'll check tomorrow14:21
loolStevenK: k thanks14:22
loolAny other business related to UNR?14:22
lool[topic] Ubuntu Moblin Remix14:22
MootBotNew Topic:  Ubuntu Moblin Remix14:22
lool(feel free to bring up anything I forget to cover and I'll reschedule it)14:22
loolbfiller: Hey14:22
loolbfiller: thanks for joining14:22
paulliuOK. Today empathy update breaks the build and gnome-menu updates breaks moblin-menu14:22
loolSo with paulliu we had a plan to move stuff to karmic14:22
loolBut still waiting on FFE  :-(14:22
paulliuI'll fix it tomorrow. Or the day after tomorrow. I have a session on FAE sprint tomorrow.14:22
bfillerlool: what is FFE?14:23
loolI'll poke motu-release at weekly release meeting if we dont get the FFE before that14:23
paulliuFeature freeze Execption14:23
loolbfiller: feature freeze exception14:23
bfillerlool: thanks14:23
loolfor the addition of the moblin packages to karmic14:23
loolbfiller: I think you wanted me to make the OEM moblin PPA public14:23
paulliuFor packages that cannot uploaded, I'll compile a list of patches and see which patches is *good* to go into karmic packages.14:23
loolbfiller: But as I wrote in my mail, paulliu told me it had some non-distributable bits14:23
loollike flash and what not14:23
bfillerlool: flash is ok to be in public ppa, just can't be in the ubuntu repos because it's not open source14:24
loolpaulliu: Ok; I think we want some wiki page like the one for new packages14:24
loolpaulliu: With a list of patches added to each packages and a comment on go/no-go14:24
paulliulool: Yes, I'll write it in the same page.14:24
bfillerlool, paulliu : was there anything else in the private ppa that worried you?14:24
loolbfiller: Aha14:24
loolbfiller: I think paulliu also mentionned non-free drivers14:24
paulliubfiller: broadcom drivers? Is it ok to open it?14:25
StevenKlool: WRT Wubi bug, bug #426238 (already filed)14:25
ubottuLaunchpad bug 426238 in wubi "ubuntu fails to boot after install." [Undecided,New] https://launchpad.net/bugs/42623814:25
loolStevenK: thanks14:25
paulliubfiller: I didn't find it in our kernel. Maybe we should send it to kernel team?14:25
bfillerlool: right, bcmwl-kernel-source is what we are using and it's ok, it's in ubuntu, I'll remoe the the other broadcom package as no longer using it14:25
bfillerpaulliu: it's in restricted: http://packages.ubuntu.com/search?suite=default&section=all&arch=any&searchon=names&keywords=bcmwl-kernel-source\14:26
paulliubfiller: ok. Thanks.14:26
lool[action] bfiller to remove bcmwl-kernel-source and give a quick check over the private PPA's contents14:26
MootBotACTION received:  bfiller to remove bcmwl-kernel-source and give a quick check over the private PPA's contents14:26
bfillerpaulliu: oops, ignore trailing slahs14:26
bfillerslash14:26
lool[action] lool to switch moblin p3a to public14:26
MootBotACTION received:  lool to switch moblin p3a to public14:26
loolbfiller: We wanted you to check whether we could use the OEM tracker to compare PPA with karmic14:27
loolbfiller: Does it turn out to be possible?14:27
bfillerlool: the package for me to release is broadcom-wl, that is unused, bcmwl-kernel-sources will stay14:27
bfillerlool: sorry, meant to remove14:27
loolok; cant edit the action but you'll know what to do :)14:27
bfillerlool: I haven't check with Cody yet, will do this today14:27
loolbfiller: Can you please ping me when PPA is ok to be made public?14:27
bfillerlool: sure14:27
loolbfiller: Ok; carrying over14:27
loolAny other business with Moblin?14:28
loolbfiller: Anybody else should be added to ~ubuntu-moblin?14:28
bfillerlool: just fyi - the guys from Intel who have been working with OEM group are testing out u-m-r for karmic14:29
loolbfiller: Any comments so far?14:29
bfillerlool: I asked them to file bugs in the ~ubuntu-moblin project with issues they find14:29
loolhttps://launchpad.net/~ubuntu-moblin/+members14:29
bfillerlool: do you have to be a member to file bug? I don't believe you do but wanted to check14:29
loolbfiller: (Project is ubuntu-moblin-remix I think)  thanks!14:29
loolbfiller: you dont14:29
loolbfiller: you're typically a member if you're interested in tracking bugs in UMR14:30
bfillerlool: ok, no comments yet but expect some soon, they are very intersted in moblin compliance14:30
loolthat is, you'll receive bug mail for important moblin bugs14:30
=== UBot-tn is now known as MaWaLe
loolbfiller: We didnt do any effort in testing it yet but I guess we could ask Tobin to look into it14:30
bfillerlool: haven't tried umr yet, does it boot into moblin ui yet?14:30
loolYes14:31
bfillerlool: cool14:31
loolSince 8 days or so14:31
bfillerthat's great, I will try it today14:31
loolbfiller: http://cdimage.ubuntu.com/ubuntu-moblin-remix/daily-live/current/ as usual14:31
loolbfiller, paulliu: thanks14:31
lool[topic] review of >= high bugs14:31
MootBotNew Topic:  review of >= high bugs14:31
loolcanonical-mobile > none14:31
lool[link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel14:31
MootBotLINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-armel14:32
loolooo > ccheney asked upstream for help and will look into it since he didn't get any reply14:32
loolI suggested using porter box and plars has setup remote access14:32
plarsyep, ready if/when he wants to use it14:32
lool422101 initramfs-tools > ogra?  It seems your initial debug was incomplete says the bgu?14:32
plarsprobably a pretty slow option though14:32
loolplars: I did setup my b2.5 for remote access now though, even if slow14:33
ogralool, yes, i will take care for it this week14:33
lool359049 udeb kernel filenames > I raised this for kernel sprint14:33
loolbjf: This is for you and/or amitk to fix during sprint or earlier, but really easy14:33
lool391588 banshee > dyfet/ogra?14:33
ogradyfet ?14:34
bjflool, ack14:34
lool420447 sound on babbage > also kernel sprint14:34
lool423767 enable rt3070sta driver > in progress14:34
ograunusable it seems14:34
lool424400 mac address of usb nics > not reproducible; needs gruemaster to sort out14:35
dyfetI dont have an update other than I was having trouble with debugging the native parts of mono and have yet to see the original issue reported, I hope to have something new on this though when I can test it in a live desktop rather than a xnest, though14:35
looldyfet: You dont have a native desktop yet?14:35
loolI thought dove was working14:35
ogralool, i still suspect gruemasters strange USB KVM to be interfering here14:35
loolAnd you have b2.5 too?14:35
dyfetlool: I have the dove working with the live usb filesystem Friday, I havent setup an install yet14:36
looldyfet: And what about your 2.5?14:36
dyfet2.5 I have no video14:36
loologra and I have video; you dont have any other screen to use with it?14:36
loolYou tried other res?14:36
dyfetyes, I have, ogra said there was no analog signal for the dvi-vga adaptor14:37
loolYou dont have a DVI screen?14:37
loolI mean digital?14:37
ograat least with my DVI->VGA cable i get nothing out of the thing14:37
loolI wonder how much it would cost to fix that14:37
ograa cheapo DVI display shouldnt be to hard to expense i bet :)14:38
plarsright, I had to get a new monitor14:38
dyfetI can get a dvi monitor today, but since dove is working, I was going to shift to that14:38
looldyfet: Can you please send me a quote for a basic DVI D screen in the US?  I'll see if davidm can allow the expense14:38
looldyfet: Well you need to do 2.5 testing too14:38
ogradove is very powerfull14:38
dyfettrue14:38
ograyou likely dont want to do daily test installs on it14:38
ograbut keep a persistent dev env on it14:39
looldyfet: Can you please raise blocking issue like this one to me?  We're really short of babbage hardware so any person with a board which doesn't do graphics testing is a pain14:39
dyfetlool: sorry...okay14:39
looldyfet: Please send me an email with a quote and we'll try to sort it out ASAP14:39
plarslool: hard to find cheap/small ones anymore, I got one off craigslist14:39
looldyfet: thanks14:39
loolbestbuy has a 129 USD one14:40
lool20"14:40
loolI think that's not too bad14:40
loolIt's like a SATA disk14:40
loolanyway14:40
lool383240 ffmpeg neon opts > my bad, will get to it this week14:41
bjflool, dell outlet hase refurbished 17 inch for $89.0014:41
ograDVI capable ?14:41
ograthats cheap14:41
* plars got a 22" for $7514:41
lool385325 thunderbird/jaunty > poked asac and we researched the upstream moz bug; dunno if it's still on track but not critical14:41
plarsdvi and vga connector, no hdmi though14:41
lool420555 mxcfb crash > also scheduled for kernel sprint14:41
ogranot as critical as it seems though14:41
loolAny other armel bugs / stuff to cover?14:41
ograworkaround in place14:41
lool~ubuntu-unr > no milestoned bugs14:42
ograpfft14:43
loolplars: I find that suspicious ^  :)14:43
bjflool, ogra, dyfet, http://www.dell.com/us/en/dfh/monitor/monitor-dell-e1909wfp/pd.aspx?refid=monitor-dell-e1909wfp&s=dfh&cs=2214:43
plarslool: was from craigslist, so it was not new14:43
loolplars, njpatel: I dont want mdz raising critical bugs not on our radar next release meeting  ;-)14:43
bjflool, ogra, dyfet, that's $11914:43
dyfetokay :)14:43
loolplars: I mean the list of bugs14:43
ograbjf, perfect i think14:43
plarslool: will spend some extra time reviewing this week14:44
loolplars: Ok thanks14:44
loolplars: I did some armel triage this morning so we'll be even   :-P14:44
lool[link] https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-moblin14:44
MootBotLINK received:  https://bugs.launchpad.net/ubuntu/karmic/+bugs?field.subscriber=ubuntu-moblin14:44
loolonly the ffe14:44
loolNo other moblin / unr bugs to discuss?14:45
loolian_brasil: Are you with us?  :)14:45
ogranot 100% related, but what happened to the lubuntu FFE discussion14:45
ogradyfet, ^^^14:45
ograi get you guys had a meeting on sun.14:45
dyfetWell, there was concerns raised about how the team maintains the seed14:45
loologra: I mentionned it during specs review but it might be good to track it in karmic + sub canonical-mobile14:45
ogradyfet, what was the outvome of the meeting14:46
dyfetAnd the team did not want to change to existing release policies until everyone votes on it over the week14:46
ograi know whats written in the bug :P14:46
looldyfet: Is there a clear leadership subset of lxde developers in launchpad/ubuntu?14:46
dyfetYes14:46
looldyfet: Oh so a vote is in progress to sort that out?14:46
dyfetYes14:46
loolDid it happen yet?14:46
ograit starts getting urgent slowly ...14:46
dyfetlool, they want it to happen over the next 5 days14:46
ograFF was long agfo14:46
ogra*ago14:46
dyfetyea...14:47
looldyfet: Could you track the bug for karmic + sub canonical-mobile so that it shows in our weekly reviews?14:47
dyfetokay14:47
loolAny other mobile bugs to discuss?14:47
loolarmel unr moblin14:47
lool[topic]     * Ubuntu MID - current status (Ian)14:48
MootBotNew Topic:      * Ubuntu MID - current status (Ian)14:48
loolian_brasil: Hola14:48
ograthere is activity in MID ?14:48
ograwow14:48
loolCurrent status of Ubuntu MID from my end: image is disabled since a long time, I dropped the image from trackers because it was raising red flags without any active maintenance on it14:48
ograyeah14:49
loolAt some point there was chat to move it into Mer's hands but that didn't really happen for unclear reasons14:49
ograand i havent heard from YoKoZar14:49
loolIf there's desire to revive it I'm happy to help getting things on track14:49
ograpersia, do you know anything by chance ?14:49
loolWe dont have time to do actual development of a hildon based spin right now, but we can certainly help with integration/cdimage etc.14:49
ograwell, people still ask in -mobile from time to time14:49
loolYes14:50
ograwould be good to have an answer14:50
ogramore than "we dont know"14:50
loolSo that's all I know of MID; I'm not devoting any time to it unless someone needs help with getting it in shape14:50
ograand given there was a community team that wanted to take it over, a clear statement would be nice14:50
loolian_brasil: Feel free to reschedule if you wanted to clarify stuff about MID14:50
loolOk folks, any other business?14:51
loolWe have to find something to say in these 9 minutes14:51
loolAlpha 6 in 10 days14:52
ogralalalala14:52
loolThanks all!14:52
lool#endmeeting14:52
MootBotMeeting finished at 08:52.14:52
ogradoobedoobedoo14:52
ograthanks14:52
paulliuThanks.14:52
paulliuWhat does "co" mean?14:52
ogracarry over14:52
ograinto next week14:52
ograor next $timeframe_of_work14:53
paulliuogra: I see. Thanks..:)14:53
=== imlad is now known as imlad|away
mdz#startmeeting14:59
MootBotMeeting started at 08:59. The chair is mdz.14:59
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:59
mdztechnical board meeting (regardless of what /topic says)14:59
=== imlad|away is now known as imlad
Keybukhullo!14:59
=== kees changed the topic of #ubuntu-meeting to: Technical Board meeting
keesgood morning :)15:00
mdzcjwatson, pitti, ping15:00
pittihello all15:00
mdz[TOPIC] Review actions from 2009-08-2515:01
MootBotNew Topic:  Review actions from 2009-08-2515:01
mdz[link] https://wiki.ubuntu.com/TeamReports/August2009#Technical Board15:01
MootBotLINK received:  https://wiki.ubuntu.com/TeamReports/August2009#Technical Board15:01
cjwatsonhi15:02
mdzcjwatson was to set up a couple of ACLs, which I believe he did15:02
cjwatsonyep,15:02
mdzcjwatson, update on Debian technical committee?15:02
cjwatsonBdale said:15:03
cjwatson"I was sort of waiting to see if anyone else on the committee jumped in.15:03
cjwatsonSince they haven't, sign me up, and I'll personally make time at least15:03
cjwatsonlong enough to help define what the role of a Debian representative15:03
cjwatsonshould be and see how this works out...15:03
cjwatson"15:03
cjwatson... so argh, we should reply15:03
cjwatsonsorry, I know this was on me but I haven't done it15:03
mdzcjwatson, should we subscribe him to the list?15:03
mdzor just invite him to the meetings?15:03
pittisorry for my ignorance, what was this about?15:04
cjwatsonlet's do both15:04
mdz[topic] Debian technical committee participation in techboard15:04
cjwatsonpitti: we agreed to invite a member of the Debian Technical Committee to sit on the TB15:04
MootBotNew Topic:  Debian technical committee participation in techboard15:04
mdz[action] cjwatson to respond to Bdale, make arrangements for him to participate15:04
MootBotACTION received:  cjwatson to respond to Bdale, make arrangements for him to participate15:04
kees(pitti: ah, the URL mdz gave is sorted by newest-last... just found the Action list they're working from now ...)15:05
mdz[topic] Java SRU policy15:05
MootBotNew Topic:  Java SRU policy15:05
mdz[link] https://wiki.ubuntu.com/StableReleaseUpdates#sun-java*15:05
MootBotLINK received:  https://wiki.ubuntu.com/StableReleaseUpdates#sun-java*15:05
mdzthis has been discussed on the mailing list a fair amount15:06
mdzand revised15:06
keessince I was involved in this pre-TB, what's the best way to involve myself in this discussion?  I have a somewhat biased opinion on it...15:06
mdzkees, you can abstain from the vote if you think it's appropriate15:06
cjwatsonsurely we can apply some useful testing in addition to just "it's a new microrelease"?15:06
mdzbut you should still speak up about it15:06
cjwatsonat least validation15:07
keesmdz: ok15:07
cjwatsonI agree that it doesn't make sense to apply the full rigor15:07
pittidoko said that there is a test suite (the Java Certification Kit thingy), but it's not public15:07
cjwatsonoh, I think that implicitly applies to that whole section actually15:07
cjwatsonpitti: yeah, it also takes man-days just to run it, it's a bit much15:07
mdzI think it wouldn't hurt to make it explicit15:08
cjwatsongiven that those weren't certified beforehand on Ubuntu anyway15:08
pittiright, and nobody really knows how to do or where to get it :/15:08
cjwatsonwe have it for openjdk15:08
cjwatsonbut you can't get hold of it without a complicated process15:08
pittithis basically sounds like a "take it or leave it" thing to me15:08
mdzpitti, Canonical does have it and we've certified using it15:08
cjwatsonpitti: I agree, I just want to make sure we don't break the world by accident during an updatee15:08
cjwatson-e15:08
keesyeah, we can't really "reject" the new versions -- they are what they are, as provided by Sun15:08
cjwatsonright, but, for example, it's possible that new versions might need packaging tweaks that we miss15:09
keessure, smoke-testing is appropriate15:09
pittithis is also why I really wouldn't like to see this being extended to intrepid/jaunty, just hardy15:09
cjwatsonyes, I agree15:09
pittiin the last SRU, we had three or four people testing the update with some programs, the browser plugin, etc., and vouch that they work15:09
* kees puts on security-team hat15:09
pittibut that can hardly cover the entire API, of course15:09
keesa lot of people complain about the lagging sun-java* packages, even in intrepid/jaunty15:10
pittikees: but jaunty has openjdk?15:10
keessince these packages are in non-LTS, I think we need to support them there.15:10
mdzI think that's probably sufficient, given that we can presume the base JDK has been through the JCK test within Sun already15:10
keespitti: agreed, which is why I want to see sun-java* removed entirely from the archive for karmic15:10
mdzwe just need to know that the packaging hasn't horribly broken it15:10
pittikees: +115:10
pittimdz: that should be covered by the basic usage testing, though15:10
mdzkees, I'm pretty sure we agreed that was OK to remove, is there anything blocking it?15:11
pittiI never let anything to -updates without at least someone saying "it still by and large works"15:11
mdzpitti, yes, I'm agreeing15:11
keesmdz: not sure, I saw sun-java5 vanish, but not sun-java615:11
mdzso we can add a blurb which explains the testing methodology which will be applied, based on what has been done for previous SRUs15:11
mdzkees, it won't go away on its own ;-)15:11
keesmdz: sure, but I think it was this meeting that was going to kick sun-java6 out officially.  sun-java5 was removed because support for it is ending.  a different reasoning.15:12
mdzkees, please add that to the agenda directly after this so we don't forget it15:12
cjwatsoncheckrdepends shows some dependencies on sun-java6, but I think that those are mostly non-default alternative dependencies; I need a slightly smarter script to be able to tell me that15:12
mdzare there any other questions on the java SRU policy other than the testing issue, which I tihnk we've resolved?15:13
mdzI'd like to put it to a vote15:13
pittiif cjwatson: heh, currently running that, too; yes, the samples I did just have alternative dependencies15:13
keesmdz: added15:13
mdzok15:13
pittisome are wrong, like "Depends: sun-java6-jre | java1-runtime | java2-runtime"15:13
pittibut not wrong enough to break15:13
mdz[vote] proposed Java SRU policy at https://wiki.ubuntu.com/StableReleaseUpdates#sun-java* as amended for appropriate smoke testing by pitti/kees15:14
MootBotPlease vote on:  proposed Java SRU policy at https://wiki.ubuntu.com/StableReleaseUpdates#sun-java* as amended for appropriate smoke testing by pitti/kees.15:14
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:14
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:14
cjwatsonconfirmed, I only see alternative deps15:14
cjwatson+115:14
MootBot+1 received from cjwatson. 1 for, 0 against. 0 have abstained. Count is now 115:14
* jdstrand is catching up15:14
pitti+115:14
MootBot+1 received from pitti. 2 for, 0 against. 0 have abstained. Count is now 215:14
kees+0 (I'll abstain since this involves me rather directly)15:14
MootBotAbstention received from kees. 2 for, 0 against. 1 have abstained. Count is now 215:14
mdzMootBot, poke15:15
mdzargh, I'm lagging15:15
mdz+115:15
MootBot+1 received from mdz. 3 for, 0 against. 1 have abstained. Count is now 315:15
mdzKeybuk, ?15:15
Keybuk+015:15
MootBotAbstention received from Keybuk. 3 for, 0 against. 2 have abstained. Count is now 315:15
mdz#endvote15:15
Keybukabstaining, since I have no real clue of the technical implications15:15
mdzor is it15:16
mdz[endvote]15:16
MootBotFinal result is 3 for, 0 against. 2 abstained. Total: 315:16
pittiI'll take the action of changing the page, and amend the smoke testing procedure15:16
mdz[action] pitti to update SRU document per vote15:16
MootBotACTION received:  pitti to update SRU document per vote15:16
mdz[topic] Removal of sun-java6 from Karmic15:17
MootBotNew Topic:  Removal of sun-java6 from Karmic15:17
=== asac__ is now known as asac
* kees keeps security-team hat on15:17
pittiI'd really like to get doko's opinion on that15:17
mdzgiven that we're certifying openjdk-6, this seems like a no-brainer15:17
keesI feel that since openjdk-6 passes JCK, there is no reason to carry sun-java6 in karmic.15:17
mdzpitti, is he available?15:17
jdstrandwrt sun-java5-- removing it was a no-brainer cause is is EOL by SUn in )ct15:17
pittimdz: not right now :(15:17
pittiit seems like an obvious thing to me as well15:18
mdzpitti, we can always reupload it ;-)15:18
keesjdstrand: correct, and has been removed so that's all good.15:18
pittiif someone really needs it, they can install it from upstream15:18
pittimdz: true :)15:18
pittibut I'd really like to see it go15:18
keespitti: that has been my thinking as well.15:18
mdzI've heard that alfresco (jaunty/partner) depends on it15:18
cjwatsonI like to confirm with the maintainer if possible for any removal, but I don't know of any obvious blockers15:18
jdstrandsomeone from server should comment, but last I looked the ec2 tools needed sun-java6 and didn't work with openjds-615:18
jdstrandopenjdk-615:18
mdzjdstrand, I don't think that is true anymore15:19
keesjdstrand: which tools?  I've always used openjdk-6 for my ec2 work15:19
cjwatsonin the past there have been bits and pieces that didn't quite work with openjdk for some reason or another and I'd like to extract a quick status dump from doko's head15:19
pittijdstrand: not possible anyway, since ec2 is in main and sun-jdk in multiverse15:19
jdstrandit might just be that amazon only certified on sun-java6 (I really don't know)15:19
mdzok, how about we vote on it, contingent on an ack from doko when he gets back?  then we don't need to wait for another meeting15:19
jdstrandpitti: not ec2-- the amazon tools15:19
mdzjdstrand, we have the euca2ools now as well15:19
pittijdstrand: ah, sorry, mixed up with euca15:19
jdstrandit very well may have changed, I am not up on its status, but wanted to at least mention it15:20
mdz[vote] remove sun-java6 from karmic in favor of openjdk-6, contingent on approval from the maintainer (Matthias Klose)15:20
MootBotPlease vote on:  remove sun-java6 from karmic in favor of openjdk-6, contingent on approval from the maintainer (Matthias Klose).15:20
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:20
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:20
mdz+115:20
MootBot+1 received from mdz. 1 for, 0 against. 0 have abstained. Count is now 115:20
kees+0 (boy I'm helpful today -- this is directly related to security-team work)15:20
cjwatsonopenjdk bugs should be a lot more tractable than sun-java ones were, so even if there are some problems at the moment, I'm:15:20
MootBotAbstention received from kees. 1 for, 0 against. 1 have abstained. Count is now 115:20
cjwatson+115:20
MootBot+1 received from cjwatson. 2 for, 0 against. 1 have abstained. Count is now 215:20
Keybuk+1 on the basis it's what doko wants15:21
pitti+115:21
MootBot+1 received from Keybuk. 3 for, 0 against. 1 have abstained. Count is now 315:21
MootBot+1 received from pitti. 4 for, 0 against. 1 have abstained. Count is now 415:21
Keybuk*that* it's...15:21
mdz[endvote]15:21
MootBotFinal result is 4 for, 0 against. 1 abstained. Total: 415:21
cjwatson(because given the TCK pass I think it's unlikely that the problems are fundamental)15:21
jdstrandthe SRU policy doesn't mention what happens when Sun EOLs a release. eg what will happen with sun-java5 in hardy after Oct?15:21
mdzcan someone take the action to check with doko?15:21
pittijdstrand: we are not bound to support it; it's multiverse, after all15:21
pittiupdates for it are a courtesy, not something people can rely on anyway15:22
keesmdz: I will check with doko15:22
mdz[action] kees to confirm removal of sun-java6 with doko15:22
MootBotACTION received:  kees to confirm removal of sun-java6 with doko15:22
jdstrandpitti: yes, but should it be removed entirely?15:22
pittibut if they are being used heavily, we could write it to ubuntu-announce@? or u-s-a@?15:22
mdz[topic] Developer Application Board15:22
MootBotNew Topic:  Developer Application Board15:22
cjwatsonwe can't remove packages from older releases, at least not without breaking some rules ...15:22
mdzKeybuk, you're up15:22
jdstrandpitti: I ask because there was a lot of rather heated discussion about this, and if nothing else, it should be documented15:22
Keybukthe Developer Membership Board has been created15:22
Keybukthe LP permissions changed15:22
cjwatson(namely that Packages/Sources in the release pocket *never* change)15:22
Keybukthe ML created15:22
Keybukand everybody subscribed15:22
pittijdstrand: u-d-a@ ?15:23
Keybukwe're ready to switch over to it15:23
Keybuk(and update documentation as we go)15:23
Keybukthe MC should begin sending reviews to the DMB rather than the TB15:23
mdzshould it have a regular meeting?15:23
Keybuk(and then we should open a discussion up about merging the MC and DMB later)15:23
KeybukI think that's up to the DMB to decide15:23
mdzKeybuk, has the DMB been updated for the new TB?15:23
kees(sorry for context-loss: who makes up the DMB?)15:23
jdstrandpitti: u-d-a seems reasonable to me (and an update to https://wiki.ubuntu.com/StableReleaseUpdates#sun-java* reflecting that?)15:23
Keybukwhen we discussed it over dinner, the idea was to try and reduce the requirement that people turn up for a time-limited meeting to answer questions15:24
mdzkees, DMB has the same membership as TB for the moment15:24
pittijdstrand: seems fine15:24
keesok15:24
Keybukmdz: is has15:24
Keybukit has15:24
* jdstrand goes to update15:24
cjwatsonkees: two board memberships for the price of one15:24
kees\o/15:24
mdzKeybuk, so what remains to be done?15:24
mdzhas it been announced on -devel-announce?15:24
Keybukmdz: we need to use it15:24
Keybukwe need to announce it15:24
mdzdoes it matter?15:24
Keybukand we need to update the documentation :)15:24
KeybukI think an announcement as part of the TB minutes should suffice15:25
mdzKeybuk, we should notify the MC explicitly to start sending applications elsewhere15:25
cjwatsonit's a governance change, I think -devel-announce would be appropriate15:25
mdzthat too15:25
mdz[action] Keybuk to announce DMB to MC, -devel-announce and update documentation15:26
MootBotACTION received:  Keybuk to announce DMB to MC, -devel-announce and update documentation15:26
mdzanything else?15:26
Keybukif it's going to wait on me having time to do all that, it'll be waiting a while15:27
* Keybuk is supremely busy15:27
mdzKeybuk, this is just finishing off the action you took to implement the DMB; if you want to hand it off, now is a good time15:27
Keybukcjwatson: you were already attacking the TB/membership documentation15:27
Keybukcould you fix wrt DMB as you go?15:27
mdzhe already finished that I think15:27
cjwatsonyeah15:27
cjwatsonI think I took an action to but haven't yet15:28
cjwatson(can you tell I've been running behind?)15:28
cjwatsonbut I can certainly do it15:28
cjwatsonit's more or less a find-replace job after all15:29
mdzI don't think we can foist this off on one of the new TB members, since it requires context from before15:29
mdzcjwatson, thanks15:29
mdz[action] cjwatson to announce DMB to MC, -devel announce and update documentation15:30
MootBotACTION received:  cjwatson to announce DMB to MC, -devel announce and update documentation15:30
mdz[topic] Archive reorganisation (Colin Watson)15:30
MootBotNew Topic:  Archive reorganisation (Colin Watson)15:30
mdzcjwatson, you're up15:30
cjwatsonright, so last time round I said I would aim to get us running on package sets by this meeting15:30
cjwatsonI didn't *quite* make it, but having tested on dogfood, I (a) discovered a couple of non-critical bugs (b) am ready to push the button15:31
mdz"Action: cjwatson to do a final check with the Soyuz team on the details, and start pushing initial sets into LP"15:31
cjwatsonthere's one thing I want to get signed off quickly before I push said button15:31
mdzcjwatson, Keybuk, hmm, actually, reviewing the notes from the last meeting, jono was to update the documentation based on the announcements, so he can help with that15:31
mdz(re: DMB)15:31
cjwatsontoday, I did a validation pass on the permissions, to ensure that I wasn't granting anyone any new permissions *to start with* (I expect we'll do that as we go along)15:31
cjwatsonthere were two failures on that validation pass; I think they're not a problem in practice, but I'd like the TB to check15:32
cjwatsonkarmic-ubuntustudio/kino grants additional permissions to ubuntustudio-dev15:32
cjwatsonkarmic-ubuntustudio/ttf-kochi grants additional permissions to ubuntustudio-dev15:32
cjwatsoni.e. those two packages are in main, and now ubuntustudio-dev will be able to upload them as well15:32
cjwatsonis that OK?15:32
jonomdz, no worries15:32
mdzttf-kochi is used by openjdk-615:33
pitticjwatson: ubuntustudio-dev -> kino seems very reasonable to me15:33
cjwatsonor rather whoever gets attached to ubuntustudio will be able to upload them15:33
pitticjwatson: I don't mind ttf-kochi personally, but I'm curious how that happens?15:33
mdzI don't have a problem with either of those grants15:33
Keybukme neither15:33
cjwatsonerr, I'd checked this for kino, let me quickly check for ttf-kochi15:34
keessounds fine15:34
cjwatsonusually it's because the package was previously in main for edubuntu or something15:34
cjwatsonI think it's a build-dependency of a font that's only otherwise in ubuntustudio15:34
pittiah, I remember15:34
pittiwe recently changed some fonts to a smaller default set15:35
pittiI suppose that wasn't merged to -studio yet15:35
cjwatsonprobably not15:35
cjwatsonsecond question, team ownerships for the package sets that have been defined so far15:35
cjwatsonthis essentially amounts to delegations of upload privileges15:35
mdzdo you have a proposed list?15:36
mdzcjwatson, ?15:38
cjwatsonI do, although I don't expect we'll be able to ratify everything at this meeting - many of the obvious teams have membership that goes well beyond ubuntu-{core-,}dev at the moment15:38
cjwatsonbut:15:38
cjwatson    'core': 'ubuntu-core-dev',15:38
cjwatson    'desktop-core': 'ubuntu-core-dev',15:38
cjwatson    'ubuntu-desktop': 'ubuntu-desktop',15:38
cjwatson    'ubuntu-server': 'ubuntu-core-dev',15:38
cjwatson    'kubuntu': 'kubuntu-ninjas',15:38
cjwatson    'edubuntu': 'edubuntu-dev',15:38
cjwatson    'xubuntu': 'xubuntu-dev',15:38
cjwatson    'mobile': 'ubuntu-mobile-dev',15:38
cjwatson    'unr': 'ubuntu-mobile-dev',15:38
cjwatson    'mythbuntu': 'mythbuntu',15:38
cjwatson    'ubuntustudio': 'ubuntustudio-dev',15:38
cjwatsonI couldn't see an obvious team for server15:39
cjwatson(174 active members)15:39
cjwatsonthere's ubuntu-server but it seemed like more of an "interested" team?15:39
pittiyes, I know people there who don't have any idea about packaging15:39
mdzcjwatson, I can bring that up at the server team meeting directly after this15:39
Keybukit seems to me that the right way to address this would be to have each team apply to own its set15:39
cjwatsonI'm not entirely sure about mythbuntu either15:39
Keybukdescribing its membership, and membership conditions15:39
Keybukwe may want "-dev" teams to be created in some circumstances, for example15:40
cjwatsonKeybuk: I certainly intend to start by assigning them to ubuntu-core-dev or motu as appropriate15:40
* pitti invokes superm1 for mythbuntu15:40
Keybukit also occurs that the -dev teams should be owned/admin'd by the dmb, as well as any local administrators15:40
pittisuperm1: hi15:40
superm1hi piti15:40
superm1er pitti15:40
pittisuperm1: is the "mythbuntu" launchpad team a set of developers whom you'd trust to upload packages, or more like an "users"/"interested people" team?15:41
pitifailtab :)15:41
superm1well they are developers, but I wouldn't trust them to all upload packages as of yet15:41
pittisuperm1: (context: archive reorg to package sets)15:41
superm1i generally help review everything before it gets a push15:41
pittisuperm1: is there a smaller "core developers" team?15:41
superm1not currently, it's just me doing uploads right now.  eventually some of them were going to apply for MOTU though15:42
mdzcjwatson, what do we need to decide here in order to enable you to proceed?15:43
cjwatsonjust a general note on package sets: there is no UI in LP that will tell you what package set a source package is in (I filed a bug, of course). I've bodged a query interface into edit_acl.py in lp:ubuntu-archive-tools, so you can use that to find out what's going on with any given package15:43
pittisuperm1: could we create a mythbuntu-dev team with the subset which should be allowed to upload?15:43
keesperhaps creation mythbuntu-dev with just superm1 for now?15:43
keess/ion/e/15:43
superm1that sounds fine to me for now15:43
cjwatsonmdz: the first question was my only blocker (I could have worked around it but it would have taken another pile of work). This team question is just a discussion I wanted to start15:43
* Daviey would be happy with that.15:43
cjwatsonI'm not blocked at the moment15:44
superm1and as people seem ready to have upload rights for the stuff they care about, add them to the -dev team15:44
mdzcjwatson, ok, maybe a good one to send to the mailing list, where we can copy in the relevant folks and handle them one by one15:44
mdzcan we move on?15:44
pittisuperm1: right; thanks for hopping in15:44
superm1np15:44
cjwatsonright, we need to decide whether the -dev team is owned by the DMB or by superm1/whoever though (the latter implies delegation of the ability to grant upload rights)15:44
cjwatsonyes, we can move on15:44
mdz[topic] community bugs15:44
MootBotNew Topic:  community bugs15:44
mdzzarro boogs found15:44
Keybukcjwatson: the latter in my mind is correct ;)15:45
mdz[topic] select a chair for the next meeting15:45
MootBotNew Topic:  select a chair for the next meeting15:45
cjwatsonKeybuk: probably, yes, but it's a noticeable step15:45
mdzI nominate kees15:45
cjwatsoninitial package sets are on production now :-)15:46
keeswoo, uhm, okay.  means mootbot familiarity, action-review, and agenda-following?15:46
mdzkees, preparing the agenda, rounding up folks for the meeting as necessary, driving mootbot and the agenda, facilitating the meeting15:47
pitticjwatson: with mythbuntu disabled for now?15:47
keescool, I'm on it.15:47
mdzgreat, thanks15:47
cjwatsonpitti: with motu attached to mythbuntu15:47
mdz[topic] AOB15:47
MootBotNew Topic:  AOB15:47
pitticjwatson: ah, great15:47
mdzanything else?15:47
mdz10 seconds15:47
mdz[endmeeting]15:48
mdz#endmeeting15:48
MootBotMeeting finished at 09:48.15:48
pitti09:48? yay time zones15:48
pittithanks everyone15:48
cjwatsonhttp://paste.ubuntu.com/267330/15:49
keesmootbot must be in central US15:50
keesmdz: who sends minutes, updates TeamReport, etc?15:51
mdzkees, the chair (me today, you next time)15:52
pittiStableReleaseUpdates wiki page changed for sun-java* FYI15:52
mdzkees, you should update the agenda for the enxt meeting15:52
keesmdz: okay.  where do you think a good place would be to record the chair duties in the wiki (I want to make sure I don't drop anything)15:52
pittikees: If I were to look, I'd probably start with https://wiki.ubuntu.com/TechnicalBoard15:54
keespitti: yeah, that's what I was thinking.15:54
keesI'll adjust it.15:54
pitticjwatson: so in the future we could e. g. switch karmic-ubuntu-desktop to ~ubuntu-desktop from ~ubuntu-core-dev?15:55
cjwatsonyeah, that's the theory15:55
cjwatsonand then everything you see in './edit_acl.py -P karmic-ubuntu-desktop query' would become uploadable by karmic-ubuntu-desktop15:55
cjwatsonerr, by ~ubuntu-desktop15:56
pittiso far that team can commit to the bzr branches; I trust most of them to do unreviewed uploads15:56
cjwatsondesktop-core is actually a bit more interesting though15:56
cjwatsonthe dependencies made the sets somewhat tricky to figure out ...15:56
cjwatsonyou'll see what I mean if you look through the lists15:56
cjwatsonthough I think there's actually a bug there too, I'll be continuing to refine15:57
pittiwhat is desktop-core?15:57
mdzkees, on the agenda page I'd think15:57
cjwatsondesktop-core is basically platform.karmic/desktop-common plus platform.karmic/supported-installer-desktop; but there's a bug in the generation which I just spotted which is pulling in rather more than that, looking at fixing that15:59
pitti$ ./edit_acl.py -s gnome-panel query15:59
pitti== All uploaders for package 'gnome-panel' ==15:59
pitti(empty)15:59
pittihmm15:59
cjwatsonit doesn't follow the package set chain yet, so that's only telling you about people explicitly authorised to upload just gnome-panel16:00
cjwatsonsome tool work is needed16:00
cjwatson(we should move)16:00
* mathiaz waves16:00
=== kees changed the topic of #ubuntu-meeting to:
soreno/16:00
kirkland_o/16:01
nijabao/16:01
=== mathiaz changed the topic of #ubuntu-meeting to: Ubuntu Server Team meeting
Sam-I-Ammorning16:01
smosero/16:01
sorenOh, are we intruding?16:01
alexmo/16:01
cjwatsonnope16:01
Daviey\o16:01
cjwatsonwe were just having a follow-on discussion16:01
ivokso/16:01
mdz#startmeeting16:01
MootBotMeeting started at 10:01. The chair is mdz.16:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:01
niemeyerYo16:01
mdzmathiaz, here?16:02
mathiazmdz: sure16:02
mdzzul, here?16:02
zulyep sorry16:02
mdz[link] https://wiki.ubuntu.com/ServerTeam/Meeting16:02
MootBotLINK received:  https://wiki.ubuntu.com/ServerTeam/Meeting16:02
mdzhas the agenda16:02
mdzmathiaz, were there any actions from the previous meeting to review?16:03
mathiazhttps://wiki.ubuntu.com/MeetingLogs/Server/2009090116:03
mdz[topic] action items from 2009090116:03
MootBotNew Topic:  action items from 2009090116:03
mathiazAsterisk16:03
mathiazDaviey: ^^?>16:03
mdzACTION: Daviey to follow up with the Asterisk Debian maintainers about adopting dkms for dahdi16:03
mdzACTION: Daviey to call for testing of Asterisk 1.616:04
Davieymdz: Been very quiet16:04
Davieyi pinged debian-voip the other day, asking for more discussion.. but nobody has replied16:04
Davieythe irc channel is often too quiet to get a discussion.16:04
mdzDaviey, how about the CFT?16:04
DavieyApologies, CFT?16:04
mdzcall for testing16:04
mdzyou had an action to call for testing of asterisk 1.6 above16:05
DavieyOh, that hasn't been done yet.16:05
mdzACTION: mathiaz to produce a list of accepted bugs for packages related to the ubuntu-server team.16:05
=== marjomercado is now known as marjo
mathiazmdz: on my todo list16:05
mdzok16:06
mdz[topic] Review status of projects for the current release16:06
MootBotNew Topic:  Review status of projects for the current release16:06
mdzso I'd like to sync up across the board on 9.10 projects16:06
mdzthe list on the agenda is not 100% complete, and doesn't necessarily map 1:1 to specs, but I think it will help us cover the territory16:06
mdz[topic] UEC images (smoser)16:07
MootBotNew Topic:  UEC images (smoser)16:07
smoser- want to release hardy refresh (ideally this week, maybe next)16:07
smoser- add more detail to Refresh Policy, send to ubuntu-devel ( https://wiki.ubuntu.com/ServerTeam/Meeting )16:07
smoser- update https://wiki.ubuntu.com/UEC/Images/Publishing with better instructions (and provide tools for all of it if possible)16:07
=== swoody_ is now known as swoody
smoser- go through and triage bugs and tag which ones for alpha 6 (will do that today)16:08
smoser- open bug and implement kernel/initrd publishing to uec-images16:08
mdzsmoser, how do we keep track of which bugs affect the UEC images presently?16:08
smoseri dont know that there is a way specifically for euc images16:09
mdzok, I'd like to fix that straight away16:09
mdzcan we agree on a tag to use now?16:09
smoserfor ec2 (whihc ideally is identical) we mark them as affecting the ubuntu-on-ec2 project16:09
mdzwe should use a project for this purpose only if it is important to track the status separately in each place16:09
niemeyermdz, smoser: We have to create a process to integrate released images in the image store as wlel16:09
smoserregarding a tag, i dont think i have enough launchpad experience to say.  ttx and soren didn't want tag (i thought)16:10
mdzsoren, ?16:10
sorenI would have preferred if there was another way, but if not, a tag is fine.16:10
smoseri think the main reason is that it is harder to tell someone to open a bug and add a tag. easier to say "open against this project"16:10
mdzsmoser, you can do that with a +filebug URL which automatically adds the tag16:10
mdzsmoser, we can also set it up so that running ubuntu-bug within a running instance does the right thing (like for UNR and the ubuntu-unr tag)16:11
mdzit's important that we get to a point where we can ask Launchpad for all of the relevant bugs in one report so that we know where we stand16:12
mdztags are the simplest way to do that at the moment, I think16:12
smosermdz, i'm generally fine with whatever is the launchpad-best-practice for doing things.  and yes, i'd like to get ubuntu-bug working, and provide a apport hook to collect data also16:12
mdzok, I suggest the tag "uec-images"16:12
mdzwhich matches the download URL and should be reasonably unique16:12
sorenFine with me.16:13
mdz[action] smoser to tag existing UEC image bugs with "uec-images"16:13
MootBotACTION received:  smoser to tag existing UEC image bugs with "uec-images"16:13
smosercan-do16:13
mdz[action] mdz to follow up on ubuntu-bug/apport for uec images16:14
MootBotACTION received:  mdz to follow up on ubuntu-bug/apport for uec images16:14
mdz[topic] EC2 AMIs (smoser)16:14
MootBotNew Topic:  EC2 AMIs (smoser)16:14
mdzpresumably all of the UEC stuff applies here as well, but since there are EC2-specific bits, I thought it would be useful to cover it separately16:14
mdzI sent out a todo list for EC2 for alpha 6 last week16:15
mdz * Add signed MD5SUMS [Steve?]16:15
mdz * Add manifest file for each image, including both the package versions16:15
mdz   inside the image (like the livefs does) and the version numbers of the16:15
mdz   relevant build tools (such as vmbuilder)16:15
mdz * Automate publishing of AMIs to EC2 [Scott?]16:15
mdz * Automate updating ec2-version-query [Soren?]16:15
mdz * Publish ec2-version-query in a more appropriate place [Soren?]16:15
mdz * Ensure inclusion of relevant news in release notes [Eric?]16:15
mdzare any of these done already?16:15
smoserwell, MD5SUMs is written in https://wiki.ubuntu.com/UEC/Images/Publishing16:16
sorenmdz: "Automate updating ec2-version-query" /was/ done, but given Steve's feedback on directory structure, I'll have to rework that.16:16
smoserbut we should make the script that builds them do that, so they're automatically there for all nightlys16:16
mdzsmoser, do you have the access rights to make the changes to the scripts?16:17
smoseri dont knwo if i can push to that bzr branch or not. soren ?16:17
smoserit is something that i need to be able to do, so we'll get that figured out16:17
sorensmoser: I think you can.16:17
smoserif not, i'll bother soren16:18
sorensmoser: If not, let's fix that today.16:18
sorensmoser: (I believe the ubuntu-on-ec2 team owns it.)16:18
mdz[action] soren to ensure that smoser can update the UEC publishing scripts16:18
MootBotACTION received:  soren to ensure that smoser can update the UEC publishing scripts16:18
mdz[action] smoser to add MD5SUMs for UEC images16:18
MootBotACTION received:  smoser to add MD5SUMs for UEC images16:18
mdz[action] soren to add manifest files for UEC images16:19
MootBotACTION received:  soren to add manifest files for UEC images16:19
mdzsmoser, is automatic publishing to EC2 doable for alpha 6?16:19
smosermaybe..16:20
mdzI understand there's likely some IS work involved here, so we should at least get the ball rolling in RT16:20
sorenheh :)16:20
smoseri absolutely want to improve it over what is there now, but fully automated might not make it.16:21
mdz[action] smoser to open dialog with IS about automated publishing to EC2 and agree on a plan16:21
MootBotACTION received:  smoser to open dialog with IS about automated publishing to EC2 and agree on a plan16:21
mdzsmoser, sound achievable for the coming week?16:21
niemeyermdz, smoser: We have to include the image store in these discussions too16:22
smoserto open a dialog, yes.  we dont 100% *need* anything changed, since we can just start an ec2 image that pulls from euc-images rather than pushing from data center to ec216:22
mdzniemeyer, I think that's a separate discussion; we hadn't talked about putting dailies or alphas into the image store16:22
smoserie, without any IS changes, it can still be automated.16:23
mdzsmoser, I meant the "agree a plan" bit ;-)16:23
mdz[action] soren to automate updating of ec2-version-query16:23
MootBotACTION received:  soren to automate updating of ec2-version-query16:23
niemeyermdz: Oh, sorry, I thought it was about what to do in general16:23
mdzniemeyer, this is about the release engineering process for the UEC images, what happens when we want to publish a new build16:23
mdzsoren, have you agreed with slangasek where to publish ec2-version-query?16:24
niemeyermdz: Ok, I guess the image store is a subset of this discussion then16:24
mdzthe thread went quiet over the US holiday I think16:24
sorenmdz: No.16:24
sorenmdz: It did. My fault, though, so not related to the holidays :)16:24
mdz[action] soren to publish ec2-version-query in a more appropriate place16:24
MootBotACTION received:  soren to publish ec2-version-query in a more appropriate place16:24
* soren nods16:24
mdzerichammond doesn't seem to be here; does he not usually attend these meetings?16:25
smosermdz, i can try.  i'd like to get insight/thoughts from soren or anyone else if publish-from-amazon is not an acceptable solution. it actually is faster.16:25
mdzsmoser, I like the idea, but it depends on how much complexity/risk it would add to change the approach this late16:25
smosermdz, that is what i did for alpha 5 (i used amazon)16:26
mdzwhat's happening with the EC2 kernel?16:26
smoserfor *publishing* not building16:26
mdzsmoser, oh16:26
smoserbuilding i think we keep in data cetner for now. but publishing just pulls from uec-images and runs through the upload-bundle, registher-image....16:26
smoserzul, you have ec2 kernel info ?16:27
sorensmoser: It's mostly an IS decision I think. (I.e. can we get the relevant credentials onto EC2 in a secure enough manner)16:27
zulmdz: we have a 2.6.31-rc6 kernel working on ec2, jj was working on packaging before he left the sprint16:27
mdzzul, working on packaging = merging it into the karmic kernel tree?16:27
sorenzul: Working in all zones?16:27
mdz(I don't think we want a separate package)16:27
zulmdz: yes he was merging it into the karmic kernel tree16:28
zulsoren: yep16:28
sorenzul: Based on the Xen patches or pv-ops? Sorry, you probably told me already, but I forgot.16:28
zulsoren: Xen patches :(16:28
sorenOk.16:28
smoserjust for the record, major applause is due to zul and jjohansen. this was really a impossible task.16:28
zuli havent had a chance to sync up with jj yet16:28
mdzpgraner, could you follow up with jj regarding merging the ec2 kernel into the karmic tree and providing it as a package? we need that for alpha 616:28
mdzzul, did we end up going with pv_ops or xen patches?16:29
pgranermdz: ack16:29
zulmdz: xen-patches16:29
mdzpgraner, I guess in that case, we need feedback on whether the patches can actually go into karmic or if they're problematic16:30
mdzwe have something which works, but it's unknown whether it's mergeable16:30
mdz[action] mdz to confirm ec2 kernel status for alpha 616:30
MootBotACTION received:  mdz to confirm ec2 kernel status for alpha 616:31
pgranermdz: we have our team meeting later today would be good to have some server reps there when we discuss. I'll add it to the agenda16:31
smoserjj's thoughts friday were that it was not significant effort to go from 2.6.31-rc6 (what we have) to karmic-ified16:31
mdzsmoser, same question as for the uec images, how do we keep track of bugs which are specific to the AMIs?16:31
mdzsmoser, can you make it to (the relevant part of) the kernel team meeting later today?16:32
smoseri've been doing 'also-effects-project' to the ubuntu-on-ec2 project16:32
smosertime ? pgraner ?16:32
mdzsmoser, I'd like to ask that we use tags there as well, to keep things simple. having multiple status/importance/assignee is just noise unless they're being handled by separate people (which in this case they aren't)16:33
mdzwhat would be a good tag to use? ec2? ec2-ami?16:33
pgranersmoser: : 1700UTC16:34
mdz(~90m from now)16:34
smosermdz, i dont like ec2-ami. as it indicates to me that kernel is not relevant16:34
smoserec2-images, corresponding to uec-images ?16:34
mdzsmoser, sounds good16:35
smosersoren, anyone else, is that tag-based approach ok ?16:35
sorensmoser: Sure.16:35
mdzit lets us get a very simple report out of launchpad of the open issues and their current status16:35
mdzand it's a lot more lightweight (fewer clicks to add the tag)16:35
mdzadding a task is pretty cumbersome just to group the bugs16:36
* smoser makes no objection16:36
mdz[action] smoser to add ec2-images tag to the relevant bugs16:36
MootBotACTION received:  smoser to add ec2-images tag to the relevant bugs16:36
mdzanything else on EC2?16:36
smosermdz, so should i just kill all tasks related to ubuntu-on-ec2 ?16:36
mdzsmoser, kill or ignore as you see fit16:37
mdzI assume there's also documentation to be updated16:37
mdz[action] mdz to see that bug documentation is updated for uec-images, ec2-images tags16:37
MootBotACTION received:  mdz to see that bug documentation is updated for uec-images, ec2-images tags16:37
smosermdz, where does MootBot publish meeting minutes ?16:38
mdzI'm wondering why we have a #ubuntu-ec2 IRC channel16:38
mdzsmoser, I'll email them out and add them to TeamReports on the wiki16:38
mdzI've been hanging out in #ubuntu-ec2 lately, and it seems very dead16:39
mdzwhen someone does come along with a question, there's nobody there to answer it16:39
nijabamdz: it is indeed now a bit rudundant with #ubuntu-cloud, which not very active as well16:39
mdzsince the amount of traffic is so low, I'd like to suggest that we fold it into #ubuntu-server16:39
kirkland_mdz: there's also #ubuntu-virt16:39
mdzaieee, irc fragmentation16:39
mdzkirkland, nijaba, how many messages per day in those channels?16:40
nijabamdz: less than 10 on avg, apart for virt which can be more active16:40
Daviey-cloud has had nothing since the 4th16:41
mdznijaba, if it's <10 messages per day, it would be beneficial to fold it into #-server where there are more people around and it's still on topic16:41
nijabamdz:  agreed16:41
mdzkirkland_, how about #-virt?16:41
mdznijaba, could you take care of obsoleting #-ec2 and #-cloud in favor of #-server, updating web pages etc.?16:41
sorenmdz: ubuntu-virt is very active at times.16:41
nijabamdz: can do16:42
kirkland_mdz:   wc says: 44437  525008 3627666 #ubuntu-virt.log since Apr 29, 200816:42
nijabamdz: should I just update the topic on the channel to invite people to go elsewhere?16:42
mdz[action] nijaba to fold #ubuntu-ec2 and #ubuntu-cloud into #ubuntu-server16:42
MootBotACTION received:  nijaba to fold #ubuntu-ec2 and #ubuntu-cloud into #ubuntu-server16:42
mdznijaba, yes16:42
nijabaok16:42
mdzkirkland_, soren, is there anything in #-virt which would be unwelcome or off-topic in #-server?16:42
kirkland_mdz: i don't think so; merely more traffic, IMO16:43
Davieyit is worth noting that -server is increasingly being used for support, and some devel discussion.16:43
sorenmdz: Not per se, no.16:43
mdzDaviey, #ubuntu-devel is available if folks need a place to go for devel discussion when #-server is too noisy16:43
nijabamdz: note that there re more 50p logged on #-virt16:43
sorenmdz: ...there are a bunch of people interested in virtualisation who don't care about servers, though.16:43
Davieymdz: agreed.16:43
mdzsoren, good point16:44
mdzlet's leave #-virt for now in any case16:44
mdz[topic] Packaging and integration of Eucalyptus 1.6 (Soren)16:44
MootBotNew Topic:  Packaging and integration of Eucalyptus 1.6 (Soren)16:44
* Daviey suggests -cloud and -ec2 automatically redirects to -virt.. easy fix then16:44
Davieythen no docs are really broken.16:44
mdzI talked with the eucalyptus team yesterday and we agreed to use the 'eucalyptus' tag to track the bugs they care about16:44
mdz[link] https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=eucalyptus16:44
MootBotLINK received:  https://bugs.edge.launchpad.net/ubuntu/+bugs?field.tag=eucalyptus16:44
sorenOh, neat.16:45
mdzI asked them to file all of their current issues as bugs so that we can track them16:45
sorenRight. Eucalyptus 1.6 has landed in Ubuntu, now. In main, even. I've been going through some of the bugs today, and hope to get through the list tomorrow and get it all triaged.16:45
mdzsoren, if there are bugs which we should discuss with the eucalyptus team, please add the tag to them16:45
mdzthen when we have our meeting with them, we'll just go over the list of tagged bugs16:46
sorenmdz: Makes sense. Will do.16:46
nurmii'll also be tracking these bugs in LP in case any discussions come up bug comments16:46
mdz[action] soren to triage all eucalyptus bugs, and use the 'eucalyptus' tag for bugs which should be escalated to the eucalyptus team16:46
MootBotACTION received:  soren to triage all eucalyptus bugs, and use the 'eucalyptus' tag for bugs which should be escalated to the eucalyptus team16:46
mdznurmi, oh, good, you're here. welcome!16:46
sorenmdz: Should I add them for eucalyptus bugs as well, so we get a complete list when querying for the tag?16:46
sorenmdz: Bugs in the eucalyptus source package itself, I mean.16:47
mdzsoren, I suggested we use the tag only for bugs which we're tracking together with eucalyptus16:47
mdzmaybe it would have been less confusing to use eucalyptus-systems or something16:47
sorenSo.. "Yes"? :)16:47
mdzsoren, it's hard for me to say without having looked at many of the bugs16:48
sorenmdz: Ok. I think I'm on top of it.16:48
mdzok16:48
mdzsoren, if I made a bad guess at who to assign any of those bugs to, please fix them up for me16:49
sorenmdz: Already done.16:49
mdzttx is on holiday, or I would have sought his advice16:49
mdzsoren, thanks16:49
mdznurmi, is there anything you want to put on the agenda wrt eucalyptus 1.6 in karmic?16:49
nurmimdz: i think the bug list is pretty comprehensive thus far16:50
mdzhow is the installer side looking?16:50
nurmiif we encounter new issues, should we be tagging them with the 'eucalyptus' tag if they effect the karmic package?16:50
mdznurmi, if the bug should be on the list when we look at bugs together, it should get the tag16:51
mdzotherwise, no16:51
nurmimdz: we went through the install process yesterday, just a few issues that were encapsulated in the bug reports (post-install type questions for networking parameters, multiple interface configuration)16:51
mdzif you want to always look at all bugs on the eucalyptus package, we can skip the tag for those and consider it implicit16:52
mdzbut we need to be able to tag the bugs which are not on the eucalyptus package itself anyway16:52
nurmimdz: got it, perfect16:52
mdzsoren, who is tracking uec installer issues on our side?16:52
sorenmdz: Colin.16:52
mdzcjwatson, ping?16:52
sorenmdz: I've talked to him already.16:52
soren...and reassigned the bugs to him.16:52
mdzsoren, perfect, thank you16:53
mdz[topic] Alfresco appliance (kirkland)16:53
MootBotNew Topic:  Alfresco appliance (kirkland)16:53
mdzkirkland_, how is this coming along?16:53
kirkland_mdz: i first noticed that I was assigned this as of your edit of the wiki page yesterday16:53
kirkland_mdz: i'll get some info from soren today about how he's creating appliances16:54
mdzsoren, kirkland_, is it doable to get this done in the next week?16:54
mdzat least an alpha quality appliance?16:54
sorenmdz: I presume so. We need some changes to the alfresco package to get done. Other than that, we should be fine.16:55
kirkland_mdz: on the alfresco side, it would help if it were in multiverse16:55
kirkland_mdz: such that we could make changes and upload fixes to that package ourselves16:55
kirkland_mdz: as it stands, it's in partner16:55
sorenmdz: It currently has a hard dependency on sun's java.16:55
mdzI don't mind if we hand-hack it at this stage, so long as we have an image that we can try out16:56
sorenmdz: This makes it difficult to distribute, as the user is required to accept the EULA, afaiui.16:56
mdzkirkland_, we're short on time. can you agree to give it your best shot? it doesn't need to be a clean build at this stage, something is way better than nothing16:57
kirkland_mdz: yes, i'll have something alpha quality this week16:57
mdz[action] kirkland to build a proof of concept alfresco appliance16:57
MootBotACTION received:  kirkland to build a proof of concept alfresco appliance16:57
mdzkirkland_, lovely, thanks16:57
mdz[topic] Appliance store (niemeyer)16:57
MootBotNew Topic:  Appliance store (niemeyer)16:57
mdzniemeyer, how are we doing?16:57
kirkland_mdz: note that the real issues will probably be licensings, non-technical ones16:57
niemeyermdz: Moving along16:58
niemeyermdz: Here are some status details I wrote down16:58
niemeyerImage Store UI has been pushed upstream and is integrated into 1.6.16:58
niemeyerImage Store UI depends on local proxy, which is being written at the moment.16:58
niemeyerProxy coding status:16:58
niemeyer- Already done: full architecture, internal service and task dispatching        infrastructure, frontend API, AWS signature checking, part of the storage       mechanisms, proxying of API calls to the upstream API (e.g. get dashboard), etc.16:58
niemeyer- Being written now: downloading of images.16:58
niemeyer- To be written: checking of gpg signature, bundling of images, uploading into  Eucalyptus, obtaining credentials through euca_conf.16:58
niemeyerWe have the following external dependencies thus far for the overall concept:   images released by server team must be registered in the store, proxy must be   packaged with Eucalyptus.16:58
niemeyerWe hope to have most of it done by the 14th.16:58
mdzniemeyer, is the image store UI in the 1.6 packages in karmic today?16:59
niemeyermdz: It is16:59
mdzgreat16:59
mdzniemeyer, will the proxy be added to the eucalyptus package or shipped separately?16:59
niemeyermdz: There might be some minor CSS details to fix, but that's just a detail16:59
niemeyermdz: Either way works for us16:59
mdzsoren, what do you think?17:00
niemeyermdz: Might be easier to upgrade being separate17:00
niemeyermdz: But might be easier to package initially being integrated17:00
sorenmdz: It17:00
niemeyermdz: Whatever soren is happy with is great by us17:00
sorenIt's hard to say. I'm not familiar with the code base.17:00
sorenIf it's in a separate package, who will do the packaging=17:01
soren?17:01
niemeyersoren: It's a python package, with a command for starting the proxy up, and a storage directory for cache and image work17:01
mdzsoren, could you look into it with niemeyer this week, decide what to do and help him get it packaged?17:01
sorenniemeyer: Separate package.17:02
niemeyersoren: Rick originally told me "I'll keep someone on the line for packaging this when it's ready."17:02
cjwatsonmdz: responding to ping, although it looks like it's been dealt with17:02
niemeyersoren: I understand it's not very helpful information now17:02
mdzI think niemeyer can maintain the package17:02
mdzonce it's set up, if someone can get the initial packaging into place so he can stay focused on the proxy17:02
sorenniemeyer: I'd prefer it if you could do the packaging. It's hard to commit to packaging something within any timeframe when you haven't seen it yet.17:03
niemeyersoren: I'm not great with deb packaging.. I'd be very happy to have someone's help with this17:03
mdzmathiaz, do you think you could give niemeyer a hand getting it packaged?17:03
niemeyersoren: I'll be on the line for any issues17:03
sorenniemeyer: Unless of course, you could give us the code before a last minute code drop?17:03
mathiazmdz: I can give it a shot - I have access to the code17:04
mathiazmdz: I can give it a shot - *if* I have access to the code17:04
niemeyersoren: It's already the "last minute" in a way :(17:04
mdz[action] mathiaz to get niemeyer's proxy code packaged17:04
MootBotACTION received:  mathiaz to get niemeyer's proxy code packaged17:04
niemeyerEither way, I'll be on the line for any issues with the code, or any questions related to building the package17:04
niemeyermathiaz: Thanks a lot17:04
mdzniemeyer, is there any reason it can't be released publicly today?17:04
niemeyermdz: It is released publicly.. it's just not working yet17:04
mdzok17:05
sorenniemeyer: Oh? WherE?17:05
mathiazniemeyer: where?17:05
niemeyerlp:~niemeyer/+junk/image-store17:05
mdzniemeyer, is there anything else you need?17:05
mdzwe're running late, so I'd like to move on17:05
niemeyermdz: We need to sync up on the registration of images in the store, but nothing else I can think of now17:05
mdz[topic] Canonical application support (zul)17:06
MootBotNew Topic:  Canonical application support (zul)17:06
nurminiemeyer: re euca_conf get credentials - do you need just the query/access keys for 'admin'?17:06
niemeyermdz: Thanks17:06
niemeyernurmi: That and the certificates17:06
zulmdz: rabbitmq-server hasnt been reviewed yet by the MIR team but kees said he was going to look at it today17:06
niemeyernurmi: Dmitrii had some working code in the Dublin sprint.. I'm not sure if it's been integrated17:06
mdzzul, ok, sounds good17:06
nurminiemeyer: nod, i'll send you a note later17:06
niemeyernurmi: Do you know details about this?17:06
niemeyernurmi: Awesome, thank you17:07
mdz[action] zul to ensure rabbitmq-server gets reviewed and promoted17:07
MootBotACTION received:  zul to ensure rabbitmq-server gets reviewed and promoted17:07
zulack17:07
mdz[topic] Directory items (mathiaz)17:07
MootBotNew Topic:  Directory items (mathiaz)17:07
mathiazmdz: openldap 2.4.18 was released sunday17:07
mdzmathiaz, openldap 2.4.18 is the only item outstanding, right?17:07
mathiazmdz: FFe granted last night17:08
mdzexcellent17:08
mathiazmdz: I'll upload the package today17:08
mdz[action] mathiaz to upload openldap 2.4.1817:08
MootBotACTION received:  mathiaz to upload openldap 2.4.1817:08
mdzmathiaz, anything else in this area worth discussing?17:08
mathiazmdz: nope17:08
mathiaznext step: more testing17:08
mdz[topic] CIM/WBEM (mathiaz)17:09
MootBotNew Topic:  CIM/WBEM (mathiaz)17:09
mathiazmdz: provider are available in the archive17:09
mathiazmdz: next step: more testing17:09
mdzmathiaz, are all of the work items in the wiki completed?17:10
mdzupdate wbem stack, package pywbem, package libopendrim, package opendrim providers?17:10
mathiazmdz: yes17:10
mdzok, perfect17:10
mdz[topic] Followups from server team sprint17:11
MootBotNew Topic:  Followups from server team sprint17:11
mdzI'm sorry I missed the end of the sprint17:11
mdzthierry sent me a summary and mentioned a few things we should follow up on17:12
mdzone was testing procedures for the UEC images17:12
mdzsmoser, where does that stand?17:12
mathiazI've updated the test cases - http://testcases.qa.ubuntu.com/System/CloudImages17:13
smoserregarding testing, we need to get to where the tests in iso tracker are fully automated (at least on ec2)17:13
mdzttx said we should add additional tests, because there was only one and it was dependent on a working UEC17:13
mathiazthe main issue we had was that we didn't have access to a working UEC17:13
mdzmathiaz, so the "bundle uec image for ec2" case should cover that now?17:14
smoseronce we get a reasonable framework down, adding additional tests should be fairly easy. for now, it is very error prone to run the tests.17:14
mdzsmoser, do you think that is achievable for alpha 6?17:14
mathiazmdz: hm - kind of.17:14
mathiazmdz: but yes - to test the UEC image delivrable rebundling to ec2 should cover it17:15
mdzmathiaz, well, in that it should be possible to test without UEC if necessary17:15
smosermdz, it "should be" a reasonable thing to achieve. at least to get through the tests we have there.17:15
mathiazmdz: I still think that testing on UEC is important.17:15
smosergiven other things on my list, i don't really want to commit to it though17:15
mdzmathiaz, I agree. the issue ttx raised was that we couldn't pass any tests for the UEC images unless UEC itself was passing tests17:16
mathiazmdz: right - with rebundle-to-ec2 with got another option for testing17:16
mdzsmoser, ok, we can survive with manual tests if necessary17:16
mathiazmdz: testing UEC images. which is better than nothing17:16
mdzis there anything else which was an open issue at the end of the sprint?17:16
mathiaznot that I can think of.17:17
mdzkirkland_, there is some confusion over the image upgrade issue17:17
kirkland_mdz: yes, i was wondering if we were going to get to that today17:18
mdzkirkland_, I suggested that we defer it so that we can focus more on bug fixing and all of the infrastructure/process work we need to do17:18
kirkland_mdz: i'd like some advice on how to proceed17:18
mdzkirkland_, is that ok with you?17:18
kirkland_mdz: that's fine with me, bug fixing sounds more important at this point17:18
kirkland_mdz: my patch is tested, and posted in the bug, for posterity17:18
mdzkirkland_, qemu-kvm is listed as a sprint agenda item which was not crossed off yet17:18
kirkland_mdz: we can revisit at any time17:18
kirkland_mdz: yes, i uploaded qemu-kvm-0.11~rc2 this morning17:19
kirkland_mdz: upstream should GA qemu-kvm-0.11 just before our Beta17:19
kirkland_mdz: these rc's are bug-fixes only, stabilizing the package17:19
kirkland_mdz: we are in lock-step with upstream and Fedora on this particular package17:19
mdzkirkland_, have you sent a call for testing?17:19
kirkland_mdz: which is a very good thing, as we're sharing the testing/debugging burden17:19
mdzI think I saw one from you17:19
kirkland_mdz: http://blog.dustinkirkland.com/2009/09/qemu-kvm-011rc2-uploaded-to-karmic.html17:20
mdzwhat is the next step we need to take?17:20
kirkland_http://blog.dustinkirkland.com/2009/08/qemu-kvm-call-for-testing.html17:20
MootBotLINK received:  http://blog.dustinkirkland.com/2009/08/qemu-kvm-call-for-testing.html17:20
zulkirkland_: i still dont understand why you need bochbios as a build dependency since it builds it own bios17:20
kirkland_mdz: we need significant testing of kvm, itself, by our community17:20
kirkland_mdz: soren and I have noticed that most kvm bugs don't get filed until after GA, sadly17:20
mdzkirkland_, do you need help organizing that?  maybe the QA team could help you run a testing day or something?17:21
kirkland_mdz: and we always SRU several kvm fixes, most of which could have been caught earlier17:21
kirkland_mdz: it's our theory that people just don't test servers until after we release17:21
kirkland_mdz: i would welcome a QA bug day on kvm17:21
sorenI find the spike to be between RC and final. Annoyingly.17:21
mathiazkirkland_: it seems that you're more looking for a QA Testing day17:21
kirkland_soren: ack, okay, just before GA, then17:21
kirkland_mathiaz: agreed, Testing Day, not Bug Day17:22
DavieyIt is hard to test kvm boxes with production level burden, to be fair.17:22
mdz[action] kirkland to speak with marjo about how to get qemu-kvm tested prior to release (and more generally server applications like it)17:22
MootBotACTION received:  kirkland to speak with marjo about how to get qemu-kvm tested prior to release (and more generally server applications like it)17:22
kirkland_Daviey: understood17:22
kirkland_mdz: accepted17:22
mdzkirkland_, please CC me in if you discuss it by email17:22
mdz[topic] Server developer team in LP for ArchiveReorganisation (Matt)17:22
MootBotNew Topic:  Server developer team in LP for ArchiveReorganisation (Matt)17:22
mdzso we now have package sets in Launchpad, and cjwatson was looking for the appropriate teams to have privileges on them17:23
mdzbut there didn't seem to be an appropriate team for Server Edition17:23
Daviey~ubuntu-server is an open team..17:23
mdzright, which makes it incredibly inappropriate for this :-)17:23
cjwatsonyeah, it's clearly inappropriate here17:23
kirkland_Daviey: yeah, too broad to dole out upload perms there17:24
mdzI think what's needed is the creation of an ubuntu-server-dev team, but I would need help populating it17:24
mdzcan someone take the action to sort this out with cjwatson?17:24
mathiazmdz: I can look into this17:24
cjwatsonthis isn't a blocker for archive reorg, but if the server team wants to take advantage of the ability to provide upload privileges for server bits without requiring core-dev, somebody will need to sort it out17:24
cjwatsoncool17:24
mdzmathiaz, thanks17:25
mdz[action] mathiaz to get a server dev team set up in LP and work with cjwatson to get it set up for archive reorg17:25
MootBotACTION received:  mathiaz to get a server dev team set up in LP and work with cjwatson to get it set up for archive reorg17:25
=== nxvl_ is now known as nxvl
mdz[topic] Assigned and to-be-assigned bugs: http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html (all)17:25
MootBotNew Topic:  Assigned and to-be-assigned bugs: http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html (all)17:25
mdz[link]  http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html17:25
MootBotLINK received:   http://qa.ubuntu.com/reports/team-assigned/canonical-server-assigned-bug-tasks.html17:26
mdzI don't know if this list was a regular part of your workflow previously, but I'd like to start using it to keep track of active bugs in the team17:26
mdzit looks like there's a lot of noise on it at the moment17:26
kirkland_mdz: i'm going to go through mine today17:26
mdzincluding 3 old bugs which are assigned to me17:26
Davieymdz: previously this was where we discussed potential SRU acceptance.17:26
mathiazDaviey: not yet17:27
mdzDaviey, we're following https://wiki.ubuntu.com/ServerTeam/Meeting17:27
Davieyoh :)17:27
Daviey<-- fail.17:27
mathiazDaviey: there is another section for SRU17:27
mdzso please look at your list of assigned bugs, and make sure it's up to date17:27
mdzthat's all17:27
mdz[topic] weekly SRU review (mathiaz)17:28
MootBotNew Topic:  weekly SRU review (mathiaz)17:28
mathiazhttp://people.canonical.com/~mathiaz/buglists/fixedbugs.ubuntu-server.latest.html17:28
MootBotLINK received:  http://people.canonical.com/~mathiaz/buglists/fixedbugs.ubuntu-server.latest.html17:28
mathiazanything sru worthy on this list^^?17:28
zulthe net-snmp one17:28
mathiazzul: bug 40617117:29
ubottuLaunchpad bug 406171 in net-snmp "COUNTER64 broken in NetSNMP::agent" [Undecided,Fix released] https://launchpad.net/bugs/40617117:29
mathiazkirkland_: any of the kvm-qemu would apply to kvm?17:29
zulmathiaz: and the samba one might be as well17:29
mathiazzul: bug 423854?17:29
ubottuLaunchpad bug 423854 in samba "Karmic: Multiple crashes in "net usershare list"" [Undecided,Fix released] https://launchpad.net/bugs/42385417:29
zulmathiaz: that has to be investiaged a bit more as well17:30
* nurmi has another engagment to go to; thanks all - i'll be in touch17:30
mathiazzul: for hardy? jaunty?17:30
zulmathiaz: jaunty17:30
DavieyThe mysql one was a regression in karmic mysql 5.1, so not relevant.17:30
mdzmaintenance on jaunty should be minimal at this stage17:30
mathiazzul: both bugs nominated for jautny17:31
mdzunless it's a critical bug (and both of those are Undecided), I'd default to "no"17:31
mdzmathiaz, ready to move on?17:32
mathiazsure17:32
mathiazthere are 4 other lists to look at:17:32
mathiazhttp://us-dappernominated.notlong.com/17:32
MootBotLINK received:  http://us-dappernominated.notlong.com/17:32
Davieynice!17:32
mathiaznothing in there17:32
mathiazhttp://us-hardynominated.notlong.com/17:32
MootBotLINK received:  http://us-hardynominated.notlong.com/17:32
mdzthe dapper one is empty17:32
mdzthe hardy ones are all fix released17:33
mathiazkirkland_: ^^ any bugs worth accepting for hardy?17:33
mathiazkirkland_: they're all libvirt/kvm bugs?17:33
kirkland_mathiaz: most of the kvm bugs have been solved in the hardy-backports package of kvm-8417:34
kirkland_mathiaz: i believe it unwise to waste any more time on kvm-62, unless we find data corruption issues17:34
mathiazkirkland_: so all the bugs should be declined for hardy?17:34
mathiazkirkland_: http://us-hardynominated.notlong.com/17:35
kirkland_mathiaz: i'll go through those, but yes, i'll decline then with a note to try kvm-84 in backports17:35
kirkland_mathiaz: and the correspoding libvirt17:35
mathiazkirkland_: ok - same question for intrepid nominated17:35
mathiazkirkland_: http://us-intrepidnominated.notlong.com/17:35
mathiazkirkland_: they're all libvirt/kvm bugs17:35
sorenSorry, guys. The real world is calling.17:35
mdzunless any of them are Critical importance, skip it17:36
* soren runs off17:36
mdzsoren, understood17:36
kirkland_mathiaz: ditto ... same thing.  kvm-72 was also clearly beta-quality code17:36
mathiazkirkland_: ok - could go through them and decline them?17:36
mdzas a general policy, we should focus maintenance almost exclusively on the current stable and current LTS17:36
mathiazkirkland_: and there is one bug in the jaunty list17:37
mathiazhttp://us-jauntynominated.notlong.com/17:37
MootBotLINK received:  http://us-jauntynominated.notlong.com/17:37
mathiazthat's all for the SRU review17:37
mathiazI'll write up a script to review which bugs have been assigned17:38
mathiazand make sure they're not get stalled17:38
kirkland_mathiaz: i don't think that's SRU-worthy17:38
mdzmathiaz, thanks17:38
mdz[topic] Progress on Roadmap17:38
MootBotNew Topic:  Progress on Roadmap17:38
mathiazkirkland_: ok - I'll decline them17:38
mdzI'm not sure how this section normally works; I find it a bit confusing because the wiki page doesn't list the projects that most of you are working on17:38
mathiazmdz: the Roadmap is not really up-to-date17:38
mathiazmdz: we should skip it17:38
mdzmathiaz, we should also update the Roadmap, no? :-)17:39
mdzI'll ask ttx to take care of that when he gets back from his holiday17:39
mathiazmdz: yes - that would be helpful17:39
mdz[action] ttx to update server team Roadmap to reflect current projects17:39
MootBotACTION received:  ttx to update server team Roadmap to reflect current projects17:39
mdz[topic] AOB17:39
MootBotNew Topic:  AOB17:39
mdzanything else?17:39
mdzcanonical folks, remember there is a conference call immediately following this meeting17:40
Davieyfortunes-ubuntu-server got MIR approval.17:40
Davieyneeds to be added to server seed.17:40
Daviey(and a version bump, to reflect some MIR review changes)17:40
mdzI've not been tracking that as a 9.10 feature17:41
Davieynijaba: ^^ ?17:41
nijabaDaviey: MIR: bug #423667, FFe: bug #423678.  MIR has been granted, nothing has happened on FFe.17:41
ubottuLaunchpad bug 423667 in ubuntu-server-tips "[MIR] fortunes-ubuntu-server" [Medium,Fix committed] https://launchpad.net/bugs/42366717:42
ubottuLaunchpad bug 423678 in ubuntu-server-tips "[FFe] fortunes-ubuntu-server" [Medium,New] https://launchpad.net/bugs/42367817:42
mdzok, so it's not actionable yet anyway17:42
mdzcan we wrap up?17:42
nijabamdz: it was not a tracked feature per say, more something that came along17:42
Davieysure.17:42
mdzgreat, sorry for running so long, we had a lot to catch up on and this is my first server team meeting in a while17:43
mdzthanks a lot, everyone17:43
mdz[endmeeting]17:43
mdz#endmeeting17:43
MootBotMeeting finished at 11:43.17:43
Davieythanks mdz17:43
mdzmathiaz, can I ask you to send out the notes and update the TeamReport?17:43
mathiazmdz: sure17:43
liebkernel meetiing in 517:55
liebRoll Call17:58
* manjo waves 17:59
* cking_ here17:59
* jjohansen waves17:59
* smb is here17:59
* sconklin is here17:59
* pgraner waves17:59
lieb#startmeeting18:00
MootBotMeeting started at 12:00. The chair is lieb.18:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:00
lieb[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting18:00
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting18:00
liebI will fill in Leann' status as we go along...18:00
liebLast week's meeting cancelled due to team travel etc.18:00
lieb#startmeeting18:00
MootBotlieb, There is already a meeting in progress.18:00
lieb[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting18:00
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting18:00
liebI will fill in Leann' status as we go along...18:00
liebLast week's meeting cancelled due to team travel etc.18:00
* pgraner hears an echo18:01
liebcut and paste silliness.18:01
lieb[TOPIC] Open Action Items: (apw) Check up on drdb status in dkms package and kernel18:01
MootBotNew Topic:  Open Action Items: (apw) Check up on drdb status in dkms package and kernel18:01
lieb[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic18:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Karmic18:01
apwthats still hanging about18:01
apwi've not gotten to it as i was out18:02
liebok tnx18:02
* amitk sneaks in18:02
lieb[TOPIC] Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targe18:02
MootBotNew Topic:  Karmic Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targe18:02
apwogasawara normally reports on those i think18:03
liebyes.  I'll dump her status from lastweek18:03
liebFrom ogasawara:18:03
lieb[LINK]  http://qa.ubuntu.com/reports/ogasawara/hwdb/driver-stats.html18:03
MootBotLINK received:   http://qa.ubuntu.com/reports/ogasawara/hwdb/driver-stats.html18:03
lieb * I finally got around to writing a hwdb script to search for all known18:03
liebdrivers and the total number of owners.  In the future this will also18:03
liebshow the total number of bugs related to a specific driver as checkbox18:03
liebjust recently provided a way to save the hw profile submission id for18:03
liebapport to link to a bug.  Note some drivers will have an "*" by their18:04
liebname indicating LP timed out while gathering the data so the stats will18:04
liebbe inaccurate for those.18:04
liebto blue pring status..18:04
lieb[TOPIC] Blueprints: kernel-karmic-kms (apw)18:04
MootBotNew Topic:  Blueprints: kernel-karmic-kms (apw)18:04
apwkms is basically business as usual now18:04
liebclose?18:04
apwfor intel, fixes coming down the pipe18:04
rtgapw, have you been following the GPU lockup issues?18:05
apwfor radeon we are still waiting on that coming18:05
apwrtg not been aware of them no18:05
apwgot a pointer to the discussion and i'll see what i can find out18:05
cking_which GPUs?18:05
rtgapw, ok, there appear to be some tools that help debug that18:05
rtgcking_, i915 so far18:05
apwi think there was at least one hang fix in the -rc9 fixes18:05
* cking_ wonders if we need some GPU tests on the USB test dongle18:06
liebapw, keep this open?18:06
apwi did see some discussion ongoing on making it use its own workqueues to help keep the machine up should it be hanging18:06
rtgapw, https://bugs.edge.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/42405518:06
ubottuUbuntu bug 424055 in xserver-xorg-video-intel "[i945GME] Karmic Intel GPU hang on Dell Mini 10v" [Unknown,Confirmed]18:06
apwlieb, sounds like it to me18:06
liebok18:06
liebnext?18:07
apwrtg thx18:07
lieb[TOPIC] Blueprints: kernel-karmic-new-kernel-on-lts (rtg)18:07
MootBotNew Topic:  Blueprints: kernel-karmic-new-kernel-on-lts (rtg)18:07
rtglts kernel - was ready to upload last week but got side tracked by a  trip top St Louis18:07
pgranerrtg: its time to get QA involved to start testing this on the boxes we have18:07
rtgneed to ask archive admins if I need a MIR. should sort that out this week.18:08
pgranerrtg: don't dump it into the archive yet18:08
rtgpgraner, ack18:08
pgranerrtg: lets get some cycles in testing18:08
rtgpgraner, I'll get a PPA version uploaded18:08
pgranerrtg: I have a call with QA today and we can work out a plan18:08
pgranerrtg: outstanding18:08
rtglieb, thats all from me18:09
lieb[TOPIC] Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)18:09
MootBotNew Topic:  Blueprints: kernel-karmic-review-of-non-upstreamed-code (smb)18:09
smbRemaining:18:09
smb- lenovo-sl: Partially updated, still has one update pending which needs18:09
smb             some more work.18:09
smb- lmpcm_usb: Has not been enabled for a while (patch to remove it ready)18:09
smb             This Logitech gizmo driver sounds like it should be supported18:09
smb             by the normal drivers by now but I have not been validating18:09
smb             this.18:09
lieb[TOPIC] Blueprints: kernel-karmic-sponsoring-staging-drivers (smb)18:09
MootBotNew Topic:  Blueprints: kernel-karmic-sponsoring-staging-drivers (smb)18:09
apwthat one is still on hold iirc18:10
smbNo progress18:10
liebok open for next week18:10
lieb[TOPIC] Blueprints: kernel-karmic-suspend-resume (manjo)18:10
MootBotNew Topic:  Blueprints: kernel-karmic-suspend-resume (manjo)18:10
manjoa lot of progress made on the USB testing last week18:10
manjo* bug reporting on failed results18:10
manjo* no suite selection dialog18:10
manjo* a 'view report' page at the end of the test18:10
manjo* the actual XML report file saved correctly18:10
manjoalso marc is working on supporting HTML tags to descriptions18:11
manjoso that we can have RTF for descriptions18:11
manjoneed to work on uploading test results to server18:11
pgranermanjo: rt ticket is filed, I'll ping IT today18:12
liebtnx18:12
manjopgraner, thanks a ton18:12
* manjo over 18:12
lieb[TOPIC] Blueprints: kernel-karmic-wifi (rtg)18:12
MootBotNew Topic:  Blueprints: kernel-karmic-wifi (rtg)18:12
rtgno progress this last week18:13
pgranerrtg: we missed this earlier I added it to the agenda18:13
pgranerhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/40923318:13
ubottuUbuntu bug 409233 in linux "[Regression] Bluetooth Causes Suspend to fail" [High,Triaged]18:13
rtgpgraner, can you still repro?18:13
pgranerrtg: which goes with the killswitch18:13
pgranerrtg: yep like a charm18:13
pgranermanjo: ????^^^^18:13
rtgpgraner, ok, its probably time to get focused18:14
manjopgraner, want me to look at that one ?18:14
pgranerrtg: I'll test with the latest rc mainline to see if its there18:14
pgranermanjo: can't hurt18:14
manjook18:14
pgranermanjo: I can tell you that I've look at kernel.org bz18:14
apwmanjo, there are some whats to test steps in the bottom of the bug18:14
manjoapw, yep reading that now18:15
pgranermanjo: and there are no reports and on LKML either18:15
manjoI have a 133018:15
apwexcellent18:15
apwthere is anew -10 kernel as of about 20 mins ago you could test18:15
apwand thats a 31-rc9 kernel, for mainline comparison18:15
pgranerapw: ack18:15
lieb[TOPIC] Blueprints: kernel-karmic-better-power-mgt (amitk)18:16
MootBotNew Topic:  Blueprints: kernel-karmic-better-power-mgt (amitk)18:16
manjoapachelogger, ack18:16
manjoapw, ack18:16
bjfremove from agenda?18:16
amitklieb, no progress. This was supposed to be removed18:16
liebdone18:16
lieb[TOPIC] Other Release Tasks: AppArmor (jjohansen)18:16
MootBotNew Topic:  Other Release Tasks: AppArmor (jjohansen)18:16
jjohansenAppArmor closed out bugs affecting security team #419308 #408473 #408445418:16
jjohansen  #419222 #401931 #41950518:17
jjohansenturned #359338 over to jdstrand which he finished testing and closed18:17
jjohansenhave a new bug #41563218:17
ubottuLaunchpad bug 415632 in linux "apparmor not properly handling file deletion on NFS" [Medium,Triaged] https://launchpad.net/bugs/41563218:17
apwis that the only outstanding bug now?18:17
liebkeep open?18:17
pgranerlieb: yep18:18
jjohansenapw: no18:18
liebok18:18
jjohansenthere are a couple tool bugs still open18:18
jjohansenI haven't looked at them yet, need to meet with kees over a couple issues18:18
lieb[TOPIC] Other Release Tasks: EC2 kernel (jjohansen)18:19
MootBotNew Topic:  Other Release Tasks: EC2 kernel (jjohansen)18:19
jjohansenwe managed to get a vanilla 2.6.31 kernel working late friday18:19
jjohansenit boots and gives console in all US east zones18:19
jjohansen#41813018:20
jjohansenwe still don't have any idea why bug #39856818:20
ubottuLaunchpad bug 398568 in ubuntu-on-ec2 "ami-bbf514d2: Sometimes does not start booting (empty console output, no network)" [Critical,Confirmed] https://launchpad.net/bugs/39856818:20
pgranerjjohansen: so does this mean you can get us a Karmic kernel? If so can we make Alpha6?18:20
jjohansenis occuring and need to follow up with amazon, after we get some more detailed time with it one centos 5.018:20
jjohansenpgraner: I believe so18:21
jjohansenI have the patches applied, but it is currently failing to link on some missing symbols18:21
pgranerjjohansen: we prob need to keep a daily irc meeting on this one until we have a solid kernel.18:21
jjohansenas far as I have gotten it is patching in some stuff18:21
jjohansento the xen-tree18:21
jjohansenpgraner: sounds like a good idea18:22
liebaction?18:22
pgranerjjohansen: set up a time and channel, prob #ubuntu-kernel would be best, make sure the server team is invited18:22
lieb[ACTION] jjohansen: set up a time and channel, prob #ubuntu-kernel would be best, make sure the server team is invited18:23
MootBotACTION received:  jjohansen: set up a time and channel, prob #ubuntu-kernel would be best, make sure the server team is invited18:23
jjohansenpgraner: okay, early morning  work best?18:23
pgranerjjohansen: up to the server team, works for most of us since your west coast18:23
jjohansenpgraner: okay I will check with the server team18:24
liebmore?18:24
pgranerlieb: not for now18:24
lieb[TOPIC] Other Release Tasks: ARM-Freescale (amitk, bjf)18:24
MootBotNew Topic:  Other Release Tasks: ARM-Freescale (amitk, bjf)18:24
bjfi'm in the middle of rebasing mvl-dove to -rc9 and testing, that should be done today (real soon now)18:24
amitkI've rebased imx51 to -rc8 and currently testing.18:24
rtgbjf, just pushed a udeb name patch18:24
amitkwill rebase to -rc9 soon18:24
amitkalso working on bug 418238, bug 42044718:25
rtgthe kernel udeb version thingy18:25
ubottuLaunchpad bug 418238 in linux-fsl-imx51 "Ethernet (FEC) not functional on Babbage with 2.6.31" [Medium,Incomplete] https://launchpad.net/bugs/41823818:25
ubottuLaunchpad bug 420447 in linux-fsl-imx51 "no sound devices on babbage board with linux-image-2.6.31-100-imx51" [Medium,Triaged] https://launchpad.net/bugs/42044718:25
bjfrtg, ack18:25
lieb[TOPIC] Other Release Tasks: Union Mount Solution (apw)18:25
MootBotNew Topic:  Other Release Tasks: Union Mount Solution (apw)18:25
pgranerlieb: that one is dead18:25
apwi think this one is closed now.18:25
liebclosed18:26
apwwe are using aufs218:26
lieb[TOPIC] Other Release Tasks: ARM-Freescale (amitk, bjf)18:26
MootBotNew Topic:  Other Release Tasks: ARM-Freescale (amitk, bjf)18:26
liebsorry..18:26
lieb[TOPIC] Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb/gnarl)18:26
MootBotNew Topic:  Security & bugfix kernels - Jaunty/Intrepid/Hardy/Others (smb/gnarl)18:26
smb* Dapper:   2.6.15-54.79 (security)18:26
smb* Hardy:    2.6.24-24.59 (security)18:26
smb            2.6.24-24.60 (proposed)[17] 1/2 verifications18:26
smb            LUM-2.6.24-24.40 (proposed, uploaded today)18:26
smb* Intrepid: 2.6.27-14.39 (security)18:26
smb            2.6.27-14.41 (proposed)[8] 9/24 verifications18:26
smb* Jaunty    2.6.28-15.49 (security)18:26
smb            2.6.28-15.52 (proposed, uploaded today) 8/17 verifications18:26
smb                          1 regression caused by #228399 fixed by revert18:26
smbAs always anyone listening/reading here and having bugs fixed in proposed,18:26
smbplease update the bug with test information.18:27
smb<eof>18:27
lieb[TOPIC] Status: Karmic (rtg, apw)18:27
MootBotNew Topic:  Status: Karmic (rtg, apw)18:27
apwwe have just rebased to 2.6.31-rc9 based kernel18:27
apwthis is expected to be the last -rc, though so was -rc818:27
apwshould have a .31 kernel in before beta18:27
rtgapw, likely late this week I think18:28
* apw concurs18:28
pgranerWe need to turn the troops on regression hunt and killing18:28
pgranerThen high pri bugs in that order18:28
apwpgraner, ack18:28
lieb[TOPIC] Status: ARM (amitk, bjf)18:29
MootBotNew Topic:  Status: ARM (amitk, bjf)18:29
* smb feels DejaVu18:29
bjfconfused at to which meeting agenda we are following18:29
pgranerYea, we just discussed that18:29
bjfthat's covered already18:29
lieb[TOPIC] Status: Netbook (sconklin, apw)18:30
MootBotNew Topic:  Status: Netbook (sconklin, apw)18:30
sconklinNo work by me - apw?18:30
apwrebasing karmic netbook in progress.  should be ready tommorrow18:30
apwnothing else going on to my knowledge18:30
pgranersounds like we can drop this one18:31
lieb[TOPIC] Incoming Bugs: (ogasawara)18:31
MootBotNew Topic:  Incoming Bugs: (ogasawara)18:31
pgranerWhat I want to replace it with is manjo's netbook testing18:31
pgranermanjo: ^^^^^18:31
apwpgraner, sounds like a good plan18:31
sconklinack18:31
liebdone18:31
liebwrt bugs, see Leann's email from Sunday18:32
lieb[TOPIC] Open Discussion or Questions: Anyone have anything?18:32
MootBotNew Topic:  Open Discussion or Questions: Anyone have anything?18:32
liebmove on?18:33
apwnothing here18:33
cking_silence18:33
manjoI will have the usb key image out for team testing sometime this week18:33
manjocomments & suggestions welcome18:33
cking_'k18:33
smback18:33
manjoprobably based on latest alpha/beta18:34
manjoand not alpha4 as I had said earlier ..18:34
lieb[TOPIC] Next Meeting Chair:18:34
MootBotNew Topic:  Next Meeting Chair:18:34
bjfogasawara is next i believe18:34
liebLeann is next?18:34
sconklindidn't we have a list?18:34
sconklinwhere is the list?18:34
cking_alphabet?18:35
manjosconklin, leann is next18:35
liebmotion to ajourn?18:35
pgranerack18:35
apwseconded18:35
lieb#endmeeting18:35
MootBotMeeting finished at 12:35.18:35
czajkowskipgraner: what time is it over there?19:00
pgranerczajkowski: 140019:00
czajkowskipgraner: cheers19:01
=== imlad is now known as imlad|away
=== fader_ is now known as fader|away

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