/srv/irclogs.ubuntu.com/2010/03/09/#ubuntu-meeting.txt

=== robbiew is now known as robbiew_
=== emma_ is now known as emma
amachuhi10:02
amachupersia, elky, lifeless, Hi10:02
elkyOh ok!10:03
persiaHey10:03
elkylifeless: you there?10:03
lifelessperhaps s:10:04
lifeless:P10:04
elkyquorum!10:04
TheMusoHey folks,.10:04
amachuTheMuso, Hi10:04
elkyi see no duluu10:05
amachuom26er, Hi10:05
elkyThere's an om26er_ though. Shall we start?10:05
om26er_amachu, hello10:05
TheMusosure lets go10:05
amachuelky, yep10:06
elkyom26er, please introduce yourself10:06
om26er_elky, my name is omer akram I live in pakistan spend most of the time at launchpad I am 1910:07
elkyom26er_, what do you do on launchpad?10:07
om26er_I very much enjoy triaging10:07
om26er_elky, triage bugs for empathy, gwibber indicator-* a bit software center etc10:08
om26er_Before coming to triaging I used to help people at #ubutnu10:09
amachuom26er_, are you part of Ubuntu Pakistan Loco?10:10
om26er_amachu, no I just joined the team,10:11
om26er_actually people here use computer in english10:11
amachuom26er_, just? How long?10:11
elkyom26er_, there's still things locos can do even in english-using places.10:11
=== Tonio__ is now known as Tonio_
om26er_the ubuntu-pk channel only have a few people there10:12
elkyom26er_, well more now that you're there ;)10:12
freeflyinghi all10:12
elkyfreeflying, welcome10:13
freeflyingelky: thx10:13
elkylifeless: persia, TheMuso, questions for om26er_?10:14
TheMusono10:14
lifelessdo you have anyone here to cheer for you?10:15
persiaom26er_: Your wiki page has no testimonials.  Have you tried to solicit some from fellow triagers?10:15
om26er_persia, I am a little shy in that area10:16
elkyom26er_, i'm sure we could find you a mentor :)10:17
om26er_elky, yes I was considering that10:17
elkyShall we go to vote, or are there further questions?10:19
TheMusoI think +0 for me at this point. You have made a good start, but I would like to see more sustained contributions.10:19
* persia is ready to vote10:20
lifelessom26er_: how long have you been triaging?10:20
amachuom26er_, would like to see testimonials, more links to substantiate what has been said, have give +0 this time..10:20
om26er_lifeless, three months10:21
amachupersia, lifeless ?10:21
lifelessso, 200 a month or so10:21
om26er_jcastro, can you please have testimonial10:21
lifeless+1 from me10:21
persia-1 from me.  Most activity is in triaging, but mixed comments in -bugs and no testimonials.10:21
om26er_persia, what kind of contribution can a person in a country where people dont mostly use computers10:22
elky+0 from me, 3 months is really short these days. I'd like to see you get a mentor for a bit and come back to us.10:22
om26er_I cant create a loco here10:22
persiaom26er_: I'm not looking for a loco.  Bugwork is great.  I'd just like to see support from other people involved in the same area you're working in, especially because I see some negative commentary in the -bugs channel sometimes.10:23
amachuom26er_, karma in launchpad is good.. keep up the good work..10:24
om26er_thanks all10:24
amachunigelb, Hi10:24
nigelbshall I introduce myself?10:25
amachunigelb, sure, go ahead10:25
nigelbHi, I'm Nigel from India.  My contribution to Ubuntu includes participation with Beginners Team, Bug Squad, Ubuntu Community Learning Project, Classroom Team, and User Days Team.10:25
nigelbI'm learning to fix bugs and moving towards joining MOTU.  As part of the Bug Squad, I've adopted Rhythmbox package - triaging the bugs and coordinating with upstream.  I also created an apport hook for Rhythmbox for easier triaging.10:25
nigelbRecently, I've been thinking of joining the Ubuntu Reviewers to help deal with 2K+ bugs with patches.  I've already started working on a few.10:25
nigelbPlease see more details of my contributions at my wiki page https://wiki.ubuntu.com/NigelBabu10:25
nigelbUnfortunately no one to cheer me because most of the people I have worked with for a long time are in US timezone10:26
nigelbBut, I guess leoquant is here :)10:27
elkysince we have quorum and then some, I'm going to recuse myself from this vote and provide a testimonial for nigelb instead.10:27
persiaI'll cheer for nigelb, even though I failed to add a testimonial.10:27
leoquant+1 for nigelb10:27
elkynigelb, has also been a great encourager of the ubuntu-women team.10:27
nigelbthanks elky10:27
leoquantgreat effort/contribution==>ubuntu user days10:27
nigelbI didn't mention UW because I wasn't sure if I was doing too much to help there, except help issyl when she wanted help with triaging and of course encouraging :)10:29
elkynigelb, mentoring issyl0 is a wonderful help, and so is being encouraging10:29
nigelbelky: :)10:29
persianigelb: So, how do you manage to spend so much time on Ubuntu?10:30
nigelbpersia: I dont spend so much time.  I spend only around 2 hours a day, except when I'm trying to fix a bug and flounder around10:31
nigelbmost of the time, my laptop is on and connected but I'll be away studying10:31
persiaAh, you have achieved the trick of visibility :)10:31
nigelbpersia: well, from you ;)10:32
elkyhe's lying. i theorise he has an rj45 socket, matrix style.10:32
nigelbhaha.  I lead a busy life.  I work and study.  In fact I've taken an hour off from work for this meeting10:32
amachui suppose an unanimous +1 for nigelb10:32
persiaWe should vote.10:33
* lifeless is still looking10:33
AlanBellnigelb++10:33
nigelbthanks AlanBell :)10:33
freeflyingnjpatel: great job, congrats :)10:33
lifelessok, ready to vote10:33
freeflying+110:34
TheMuso+110:34
lifeless+110:35
persia+110:35
amachu+110:35
* elky recused.10:35
amachuwelcome nigelb10:36
leoquantyeah, great congrats nigelb \o/10:36
elkyyay!10:36
nigelbamachu: thank you :)10:36
nigelbI'm honored :)10:36
lifelessdul* isn't here10:37
amachulifeless, yep10:38
lifelesselky: meta: 3 months is reasonably sustained IMO - its more than a school holiday kindof thing. Not saying its enough either; just don't think its particularly short.10:38
elkyseems not. has anyone actually ever laid eyes on him10:38
elkylifeless, these days I find it to be short. however it wasnt the only factor, everyone else already said the rest10:39
lifelesselky: right, I'm not bothered about the rest :P10:39
elkytough :P10:40
amachulifeless, true..10:40
* persia tends to balance "significant" and "sustained" such that a higher volume of work takes less time (but 2-3 months feels like a minimum)10:40
czajkowski.c10:40
amachupersia, on the expiry of team?10:40
persiaamachu: The CC is currently finishing the debate about how we get reelected.  That ought be resolved within a couple weeks.10:40
lifelesselky: I don't think we should be moving the goalposts is what I'm saying.10:40
persiaWith luck we'll be able to solicit guidance after the next CC meeting.10:41
elkylifeless, did you read the recent emails?10:41
lifelesselky: which ones10:41
amachupersia, Ok10:41
elkybtw, my main reason for 0 was that i'd like to see some mentoring10:41
lifelessI think the outcome was appropriate10:41
lifelessI have /no/ issue with it10:41
amachuso we shall meet 22 Mar 10, 10.00 UTC10:42
amachu23 March 1010:42
elkylifeless, the threads dholbach has been involved in10:42
lifelessI'll be asleep then : I fly in thata morning at 7am.10:43
dholbacheh?10:43
elkydholbach, the mails between the member-granting councils/boards re membership criteria10:44
lifelesselky: if its the thread I think it was, I commented in it10:45
persiaelky: Do you have a subject for those?  I'm not sure I've read that sort of thing recently.10:45
elkypersia, clarification: attaining membership10:45
dholbachall the feedback I got was massaged into https://wiki.ubuntu.com/Membership (in December)10:45
elkythey discussed duration of contribution, so it's not /us/ moving the goalposts as lifeless suggested10:45
elky(my only reason for mentioning it)10:46
persiaRe-reading that thread (sorry for the confusion, I don't consider 3 months ago recent), I'm not sure there was consensus on timing.10:48
persiaPersonally speaking, I don't consider less than two months sufficient, and don't tend to give extra points for > 6 months except under exceptional circumstances.10:49
elkypersia, well, it was published to the /Membership wikipage10:49
* elky shrugs10:50
* persia looks again10:50
dholbachand it was no "they" and "us" discussion - all membership boards were in the discussion10:50
persiaelky: Indeed.  I missed that edit when reviewing the discussion.  I concur.10:50
dholbachdo you think we should have the discussion about timespan again?10:51
persiadholbach: There is no "they" and "us" in Ubuntu generally.10:51
lifelesselky: so yes, I provided the wording that is on /Membership in fact10:53
persiaAnyway, let's move on.  I think we can all agree that the wording at /Membership is correct (or raise that in a wider thread).10:54
dholbachso if necessary, I'm happy to participate in another discussion about it - do you need anything else from me? :)10:54
elkydholbach, there is an us in this discussion -- the people on this board at this meeting involved in that decision.10:54
persiaSome of us may be willing to accept some folk with less time, under some conditions.  Complete approval is likely to remain "rare".10:54
lifelessgnight10:55
dholbachelky: sorry, I probably could have been clearer - I just meant to clarify that all the membership boards plus the CC were in that discussion back then10:55
amachupersia, true10:55
elkypersia, sure.10:55
elkydholbach, i'm aware.10:55
persiaelky: dholbach: Could we agree that "the threads discussed ... and "us" as in this board?10:55
elkythere's contexts, yes.10:55
* persia is temporarily annoyed at English overloading the same word to indicate a collection of objects and a connetion of people10:56
persias/nn/ll/10:56
persiaDo we have anything else?10:57
amachunot from my side10:59
asaco/12:59
dyfeto\13:00
ogrameep13:00
JamieBennettmoo13:00
* ogra quickly gets a coffee ... missed that13:00
* asac too13:00
* persia waits for the wiki page to finish saving13:01
asacback i am13:01
* plars hangs another bag of caffeine on the I.V. and cranks up the drip13:01
davidmhello13:01
NCommander#startmeeting13:02
MootBotMeeting started at 07:02. The chair is NCommander.13:02
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]13:02
* NCommander coughs13:02
JamieBennettumm, no action items from last week?13:02
asachi NCommander ;)13:02
* GrueMaster digs for #2 toothpicks and inserts them under eyelids.13:02
NCommander[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010030913:02
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010030913:02
asacJamieBennett: shoud i add ogras AR?13:03
asaci think i saw that in mail ;)13:03
* JamieBennett didn't see that13:03
ograre13:03
asacseems i dreamt that ;)13:03
asacok lets start  i guess :)13:04
* ogra didnt send it yet ... there was a discussion about logs that kept me from sending it :P13:04
asac[LINK] http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html13:04
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.04-beta-1.html13:04
NCommander[topic] Standing Items13:04
MootBotNew Topic:  Standing Items13:04
asacogra: feel free to add to wiki directly ;)13:04
ograwill do13:04
NCommander[topic] Kernel Status (cooloney, ericm)13:04
MootBotNew Topic:  Kernel Status (cooloney, ericm)13:04
JamieBennettNCommander: slow down ;)13:05
ogradude13:05
JamieBennettAnything to comment on for work items?13:05
ograwhere are they ?13:05
asacso for beta13:05
asacbesides from office/email ... what can we do for the other specs?13:05
asacpowermanagement has two bugs somehow13:05
asacthat stops it from being finished13:05
* cooloney waves at ogra 13:05
ogra(the action items from last meeting i mean)13:05
asacogra: ? are those valid to block this spec?13:05
asacNCommander: roll back13:06
asacwe are at standing items review of beta work itmes ;)13:06
NCommander[topic] Beta Work Items13:06
MootBotNew Topic:  Beta Work Items13:06
NCommanderThere, now we're all on the same page :-)13:06
cooloneyfor fsl-imx51, kernel just applied one patch to fix an subtle kernel oops bug found by jeremy kerr13:06
JamieBennettlol13:06
cooloneybug #53169613:07
ubottuLaunchpad bug 531696 in linux-fsl-imx51 "mc13892 LED driver oopses on trigger action" [High,In progress] https://launchpad.net/bugs/53169613:07
ograasac, regulators -> complete FSL patch missing ... not sure we *need* the fix actually ... based on FSL13:07
cooloneyand i did not get any feedback about one of my patch to fix the bsp building error13:08
ograasac, numbers for idle case -> depends on vendors and we wont do any code changes based on it -> DROP13:08
cooloneyi think we forward it to fls13:08
cooloneyfsl13:08
ograasac, what other tiems are you referring to in that spec ?13:08
ogra*items13:09
asac_ok i had a reconnect :(13:09
asac_can someone paste me the scroll back13:09
asac_and cross fingers that i stay up now13:09
JamieBennettasac_: http://pastebin.ubuntu.com/391746/13:10
ograto late13:10
asac_sorry folks. please run the meeting not relying on me13:10
StevenKOr your ISP13:11
ograasac_, http://pastebin.ubuntu.com/391746/13:11
JamieBennett:D13:11
=== asac_ is now known as asac
asacok cross fingers13:11
* ogra crosses fingers13:11
asacid dint get the paste before either13:11
JamieBennettOK, back to work items13:11
JamieBennettasac: http://pastebin.ubuntu.com/391746/13:11
ograasac, so what items were you referring to in the spec ?13:11
asacok so should those bugs be linked to spec?13:11
ograimho we can set them all to dropped unless something comes from FSL13:12
asacor just tracked as bugs?13:12
asacimo i would think that feature bugs should be linked13:12
asacto specs, but not real bugs13:12
ograwhich bugs exactly ?13:12
asacok lets unlink them13:12
asachmm wasnt powermanagement spec linked to bugs?13:12
ograyes13:12
ograsadly the spec page gives no overview about the bug status :(13:13
ograi think most of them are fix released13:13
* NCommander has the action items for this week once ogra releases the wiki page lock13:13
asacbug 50900613:14
ubottuLaunchpad bug 509006 in linux-mvl-dove "[dove] hibernation failed to resume" [High,Confirmed] https://launchpad.net/bugs/50900613:14
ograi dont do anything on the page13:14
asacthats still open13:14
ograNCommander, grab it13:14
asac-> unlink13:14
asac?13:14
ografix rather ?13:14
ericm_that's not fixed13:14
plarsI think GrueMaster said he tested that yesterday, and that it was still broken13:14
asacright. my question was if we should make specs for bug tracking13:14
ograwell, we'Re in kernel freeze ?13:14
asacif we cant close a spec if there are bugs left we can never finalize it for a milestone13:14
NCommanderaction items up13:15
ericm_asac, which spec depends on hibernation?13:15
GrueMasterI tested both apw's kernel and the latest image.13:15
ograwell, then unlink13:15
asacif we say: its ok to be behind because we track bugs that come out of specs thats fine13:15
NCommanderwe'll do those once we finish Standing Items13:15
asacericm_: power management13:15
ograhttps://blueprints.launchpad.net/ubuntu/+spec/mobile-lucid-arm-per-soc-powermanagement13:15
GrueMasterapw's kernel failed, but the latest image worked fine.13:15
ograGrueMaster, did you tell that apw ?13:15
asacok lets move on to another spec ;)13:15
ericm_can we just unlink it, as I know hibernation shouldn't block power management13:15
ericm_in other aspects13:15
GrueMasteryes.  It should be in the irc log.13:15
asaclets screw it ... i will approach you individually after the meeting ;)13:16
ograunlinked13:16
asactoo many reconnects ;)13:16
asacogra: thanks13:16
JamieBennettasac: ++13:16
asacNCommander: lets go on with standing items13:16
asac;)13:16
ograasac, action items first :)13:17
asacright13:17
asacthose were not there when i last looked ;)13:17
ograwhoops ... i didnt do mine :(13:17
ograasac, our chair is slacking :)13:17
NCommander[topic] Kernel Status (cooloney, ericm)13:18
MootBotNew Topic:  Kernel Status (cooloney, ericm)13:18
ograNCommander, action items please13:18
NCommander[topic] Action Item review13:18
MootBotNew Topic:  Action Item review13:18
NCommander[topic] asac to talk to team about training session13:18
MootBotNew Topic:  asac to talk to team about training session13:18
asaci started to write on alpha-3 stuff ... i think -efl bugs are not yet done13:18
* NCommander was dealing with a very persistant cat13:18
asacNCommander: i lost context on training session ;)13:18
ograwe did one13:18
ograthat was the thumb2 session13:18
asacthat was about the thumb2?13:18
ograyup13:18
asacyeah then that was done two weeks ago ;)13:19
ograso strike13:19
JamieBennettasac: (these action items are from 2 weeks ago)13:19
NCommander[topic] asac and JamieBennett to triage netbook-launcher-efl bugs13:19
MootBotNew Topic:  asac and JamieBennett to triage netbook-launcher-efl bugs13:19
asackeep bloggin and -efl bugs13:19
asaccf13:19
NCommanderasac: cf?13:19
JamieBennettcarry forward13:19
asaccarry forward13:19
ogracarry forward13:19
* NCommander hears an echo13:19
ograor creepy fish13:19
asacno need to make topics for each of the items ;)13:19
asacbut go ahead13:19
NCommander[topic] ogra to file a bug on LP not tracking bug links to blueprints or sending emails13:20
MootBotNew Topic:  ogra to file a bug on LP not tracking bug links to blueprints or sending emails13:20
ograco13:20
NCommander[topic] NCommander to investigate KDE FTBFS issues13:20
MootBotNew Topic:  NCommander to investigate KDE FTBFS issues13:20
NCommandertuxdavis took this one over, and found the kdebindings crash13:20
asacthe fix you mean?13:20
ograyeah, seems its fixed13:20
NCommanders/crash/fix13:20
asacright. last i looked there were not so many issues13:20
ograits not on the ftbfs list since some days13:20
asackdeedu was still unhappy13:20
NCommanderI'll look at it sometime this week13:20
NCommanderso I guess c/o on this one too13:21
NCommander[topic] GrueMaster to produce a daily report on image testing and add that to the weekly meeting page13:21
MootBotNew Topic:  GrueMaster to produce a daily report on image testing and add that to the weekly meeting page13:21
GrueMasterWIP13:21
NCommanderco?13:21
ograare you adding it atm ?13:21
GrueMasterStarted this week13:21
asacthats fixed also13:21
asacright GrueMaster and me discussed this and its moving ;)13:21
asaci dont think we need to carry that forward13:22
NCommander[topic] everyone to try rootstock GUI once its in the archive13:22
MootBotNew Topic:  everyone to try rootstock GUI once its in the archive13:22
* ogra had feedback from asac so far on rootstock ui testing13:22
asacwe will see that when checking it13:22
asaci tested it quite a bit13:22
asacthough not to full image ;)13:22
ograthe rest of the team are slackers !13:22
asacbecause of the qemu hangs13:22
ograright13:22
ograi'm hoping the recent upload changes something in qemu13:22
asacis that fixed now ?13:22
ograno13:22
asachmm so the new image format didnt help?13:23
ograand i cant test until glib is built and promoted13:23
plarsI was told by ogra to wait for his fix :)13:23
Riddellon the KDE compile failure tuxdavis concluded its a fault in the toolchain causing the segfault.  kdebindings, kdeedu and other non kde packages are affected.  I've worked out it in kdebindings by not compiling smoke on ARM13:23
ogranope, but there was a fix for disk IO tonight13:23
asacogra: you should really make alocal mirror out of a apt-cache13:23
ograplars, you can test minimal images once glib is there13:23
asacRiddell: thanks!13:23
asacRiddell: is that ok?13:23
asacor a bad hack=?13:23
ograsadly glib breaks debootstrap atm13:23
ogra(we now pull glib into minimal builds since recently )13:24
StevenKArgh13:24
NCommanderew13:24
* ogra waits whan gtk will enter too13:24
* StevenK didn't want to hear that bit13:24
StevenKI just ate, damn it13:24
asachmm glib in minimal? what is pulling that?13:24
ograsend flowers to plymouth :)13:24
* NCommander seconds StevenK's emotion13:24
asacoh13:24
asacok13:24
persia!ohmy13:24
ubottuPlease remember that all Ubuntu IRC channels share the same attitude of providing friendly and polite interaction with all users of all ages and cultures. Basically, this means no foul language and no abuse towards others.13:24
asacok lets move on13:24
asacsummary: qemu is in bad state still :/ no idea whats going on13:25
ograright13:25
NCommander[topic] Kernel Status (cooloney, ericm)
13:25
MootBotNew Topic:  Kernel Status (cooloney, ericm))13:25
Riddellasac: it'll do for kdebindings but the problem is likely to reappear elsewhere13:25
ograwell, i have a better idea13:25
asacogra: please try the file writing/reading loop13:25
asac;)13:25
cooloneyright,13:25
asacin a qemu to check if its reproducible by that13:25
cooloneyit is our turn?13:25
ograasac, next aftzer stracing apt13:25
asaccooloney: go ahead13:25
cooloneyfor fsl-imx51, kernel just applied one patch to fix an subtle kernel oops bug found by jeremy kerr13:25
cooloneybug #53169613:25
ubottuLaunchpad bug 531696 in linux-fsl-imx51 "mc13892 LED driver oopses on trigger action" [High,In progress] https://launchpad.net/bugs/53169613:25
cooloneyi think i sent this patch to ogra13:26
ograyeah, i need to forward it to paul still13:26
cooloneyit should be included in fsl's bsp13:26
ograwil do that before the call today13:26
cooloneyogra: ok, thanks13:26
cooloneyand how about the regulator issue?13:26
ogragiven that next BSP is only plannae dfor end of may its not that urgent i think ...13:27
asacok so that patch came from fsl?13:27
ogracooloney, last call was skipped13:27
ograi'll bring it up today13:27
asacok13:27
cooloneyogra: right, understand13:27
asacwhats the status on regulators?13:27
ograFSL is definately aware13:27
ograwe had enough mails on that13:27
asacstill missing a patch?13:27
cooloneyyeah13:27
ograa part of the patch is missing13:27
asacright. lets bring it up today13:28
ograright13:28
ograthats the plan13:28
cooloneyright, i just got one patch will will break our kernel13:28
* ogra would still looooove to see a fix for bug 45787813:28
ubottuLaunchpad bug 457878 in linux-fsl-imx51 "imx51 on board ethernet plug/unplug events not detected" [Medium,Confirmed] https://launchpad.net/bugs/45787813:28
cooloneyand i also sent out a patch to fix the building error before13:28
asac[ACTION] ogra and asac raise regulator patch issue again with fsl13:28
NCommander+1 ogra13:28
cooloneyis that any feedback13:28
NCommander[ACTION] ogra and asac raise regulator patch issue again with fsl13:28
MootBotACTION received:  ogra and asac raise regulator patch issue again with fsl13:28
ograbut i'm not having high hopes13:28
cooloneyogra:  i am working on that13:29
asaccooloney: do you have any idea?13:29
* ogra humps cooloney's leg13:29
cooloneyand is preparing a patch to add phylib support into fec.c13:29
asacor waiting on fsl input?13:29
cooloneybecuase the upstream also like to see that13:29
ograasac, we know whats wrong, its just a hell lot of work13:29
cooloneyyeah,13:29
cooloneybut if we switched to generic phylib13:30
cooloneyit is better for every one who use fec.c13:30
ograand FSL just didnt do it yet13:30
* ericm_ wonders why fec.c still hasn't been linked with phylib13:30
cooloneyericm_: no idea13:30
ograericm_, especially since that bug is known since jaunty13:30
* persia doesn't press the ohmy button again, as it's too soon, but ...13:30
asacok. if there is info you need from fsl to work on this let us know offline13:30
cooloneyasac: no problem13:30
asacanything else on imx51?13:30
ograpersia, what for would you pressi it ?13:30
cooloneyoh, we found necessary patches for kexec13:31
asacinteresting. how intrusive are those?13:31
cooloneybut still need finalize13:31
asacok. is there a place to track that ?13:31
ograasac, they are in already as i understood13:31
ogra(kexec patches)13:31
ericm_cooloney, what's there still need finanlize?13:31
cooloneyback ported 5 patches to add kexec supporting for our armv713:32
cooloneyericm_: we still need patch kexec-tools13:32
ograoh from .32 to .3113:32
cooloneyor just kexec vmlinux13:32
cooloneyneed a solution13:32
ogranote that its fine to have but we wont do anything for lucid with kexec13:32
asacwhen is the deadline for getting this in?13:32
cooloneyogra: no, backport from .33 to .32 and .3113:32
ograwe will do a lot with it in L+1 if its there though13:32
cooloneyso versatile, dove and imx51 can support that13:32
persiaCool!13:33
ograsince NCommander  will revive softbootloader then13:33
ericm_cooloney, ah right - we might need an updated kexec-tools13:33
ograso dont put kexec on higher prio than the other bugs please13:33
NCommanderogra: I already had managed to get softbootloader working on dove partially weeks ago. I shelved the work this cycle after talking with asac13:33
cooloneyand i think ericm_ already pushed the kexec to lucid13:33
asaci agree with ogra, lets not drop other stuff for kexec13:33
cooloneyi will do that later13:34
asacok13:34
ograthey RC bugs are more important13:34
asaccooloney: when is the last upload deadline?13:34
ericm_11th is the deadline for kernel freeze13:34
ograi think that was today13:34
ograor yesterday13:34
cooloneyericm_: right, thanks13:34
ograapw said 8th13:34
ograto get everything ready before freeze13:34
ericm_oh, I'm lucky then send him the git pull yesterday13:35
asacok so on imx51 we wait for regular patch, work on carrier detect for fec and look into kexec backports13:35
asacanything else?13:35
ogra(for packaging and testing etc)13:35
cooloneyso i need to do that soon,13:35
cooloneyat least for kexec patches13:35
asacregulator13:35
cooloneyasac: good summary13:35
cooloneyright13:35
asacok ericm_ ;) ... your turn!13:35
ericm_cooloney, right - we might want to get the basic stuffs in - anything broken can be fixed later13:35
cooloneyericm_: exactly13:36
apwfreeze is thursday ... to get things up and built before then i 'closed' yesterday13:36
ericm_ok, Marvell made another drop of patchset this week, and I was able to get them in in the git-pull to apw yesterday13:36
apwis there something i am missing whcih is needed for freeze13:36
ericm_basically, there will be three parts of changes13:36
cooloneyapw: so i missed that13:36
ograapw, yeah, we decided to switch FSL to .33 :P13:36
* apw dies13:37
* ogra hides13:37
plarsheh13:37
ericm_kexec + basic Android support (not necessarily turned on in our kernel but to keep our code as close as possible to theirs)13:37
asacapw: nothing planned, but you never know ;)13:37
ericm_+ BMM (a block memory management for physically contiguous memory allocation for their GPU/VPU acceleration)13:37
asacericm_: basic android support? what size is that patch?13:37
ericm_and turning off OABI_COMPAT as discussed13:37
asacright. thanks for that13:38
asac;)13:38
ericm_asac, it's a series of patches13:38
ericm_asac, but we didn't turn on any Android related options - so to keep the impact to minimized13:38
asacericm_: right. wonder what size are those patches?13:39
asacwhats the topic? powermanagement?13:39
ericm_asac, it's not much, lemme check13:39
ericm_asac, < 1M, oh my13:40
asacok13:41
asaclets take that offline13:41
asacany important issues outstanding for dove?13:41
asacwhat about bug 528524: pulseaudio "Sound not working in all apps on dove"13:41
ubottuLaunchpad bug 528524 in totem "Sound not working in all apps on dove" [High,New] https://launchpad.net/bugs/52852413:41
* ogra saw something similar for imx51 today ? 13:41
asacplars: is it really a regression compared to x86?13:42
ericm_mmm.. and mplayer crashes in sound as well - Marvell is working on this13:42
asacok so thats still on the radar?13:42
GrueMasterYes.  But it may be driver related.13:42
plarsasac: it seems specific to that board13:42
asacok good13:42
plarsasac: but we have another similar (but different) pulseaudio issue on imx5113:43
asaclet me add the kernel package13:43
asacjust in case13:43
ograBug 53481513:43
ubottuLaunchpad bug 534815 in pulseaudio "imx51 some audio files play, others do not" [Medium,Confirmed] https://launchpad.net/bugs/53481513:43
asacericm_: do you know where they want to fix it? in kernel?13:43
asacogra: some audio files? e.g. codecs?13:43
asacor apps?13:43
ericm_asac, the crash looks like a kernel bug, so yes - most likely13:43
ograasac, no idea, not my bug13:43
plarsogra: right13:43
plarsI spent a good deal of time looking at that one yesterday13:43
GrueMasterthe mplayer crash on dove is definitely kernel related.  mplayer segfaults when opening the audio device.13:44
asacplars: so on imx51 all apps play sound ... just some codec/format/frequency doesnt work well?13:44
asacGrueMaster: ok thanks. so the dove thing is kernelish ... done.13:45
cooloneyogra: never looked at that bug before13:45
plarsasac: actually that seems to be the case on both boards, but the sampling rates at which they will play is different13:45
asachmm13:45
ogracooloney, reported 11h ago :)13:45
ogracooloney, nobody expected you to look yet :)13:45
asacinteresting bug. we should keep that on the radar13:46
ogra++13:46
asactargetted for lucid13:46
cooloneyogra: oh, thanks,13:46
asacok anthing else for dove?13:47
ericm_asac, nope13:47
asaclets move on ;)13:47
asacNCommander: ^13:47
NCommander[topic] QA Status (GrueMaster, plars)13:47
MootBotNew Topic:  QA Status (GrueMaster, plars)13:47
GrueMasterImage builds continue to be hit and miss.  Currently, 3/7 is the last image built.13:47
GrueMasterTested hibernate multiple times on Dove with latest available image, no issues to report.13:47
GrueMasterTested image install on Babbage 3, no immediate issues seen during imaging.  Sound still appears to be an issue.  System sounds are ok, but no playback from alsa tools.13:47
GrueMasterThat's all from yesterday.13:48
plarsLooks like the suspend/resume tests may go into checkbox main, but I have some things to fix/cleanup on it based on a review I got back from Marc yesterday, so I'll be taking a look at that this week13:48
ograhow about test kernels (which are due to be uploaded today)13:48
GrueMasterI need to backtrack and put some notes together for last week.13:48
ograif you get such things it would make sense to add them to the report13:48
GrueMasterok13:48
asacGrueMaster: today we had no image?13:48
GrueMasterNope.13:49
asacwhat is currently out of sync?13:49
ograasac, see the page :)13:49
ograi reported it13:49
ograunder image status13:49
asackk13:49
asacok thanks plars and GrueMaster13:49
asacplars: will check with you on the final work items of suspend resume13:49
asacoffline ;)13:49
plarssounds good13:50
asacok next13:50
asacNCommander: ^^13:50
NCommander[topic] ARM Application status (JamieBennett, dyfet)13:50
MootBotNew Topic:  ARM Application status (JamieBennett, dyfet)13:50
GrueMasterI also spent a good chunk of Sunday trying to get likewise working.  First order is to get it working on x86.  Still no luck, even with the help of a Windows guru.13:50
JamieBennettLooking OK, netbook-launcher-efl has a few bugs but nothing out of the ordinary13:50
asacGrueMaster: do you have a win server for likewise testing?13:50
ograGrueMaster, thats been moved to the server team last week13:50
GrueMasteryes13:51
asacok cool. i dont think its high priority though13:51
ograGrueMaster, please coordinate with them and comment on the bug if you test it13:51
GrueMasterDoes the server team have access to arm?13:51
asacwhat we want to tes tis whether it doesnt crash ;)13:51
asacGrueMaster: we can run the tests for them if they make a proper server setup available with instructions how to setup the client13:51
asac;)13:51
ograGrueMaster, we offered them help so if you have a setup that would be good13:51
asacso we dont need to fiddle until x86 works first13:51
GrueMasterok13:51
ograbut let them know and ask what they need13:52
GrueMasterClient side is easy.  Getting an NT server going is hard.13:52
asac[ACTION] ogra to check with ttx on what server team needs to help likewise testing on arm13:52
ograNCommander, ^^13:52
NCommander[topic]13:53
MootBotNew Topic:13:53
NCommanderer13:53
ograheh13:53
NCommander[topic] ARM Porting/FTBFS status (NCommander, dyfet)13:53
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander, dyfet)13:53
NCommanderC&P fail13:53
ograerr13:53
asaclibplist -> i have that fixed for armel13:53
NCommander[ACTION] ogra to check with ttx on what server team needs to help likewise testing on arm13:53
MootBotACTION received:  ogra to check with ttx on what server team needs to help likewise testing on arm13:53
ogra[ACTION] ogra to check with ttx on what server team needs to help likewise testing on arm13:53
ograthanks13:53
asacsquid i havent done yet13:53
ograasac, oh, dyfet wanted to look at squid and libpt13:53
ograerr libplist13:53
asaci did plist over the weekend13:53
asaci can keep it private ;)13:54
ograright, dyfet whats the status for squid then ?13:54
asacanyway, there are plenty of ftbfs so fix13:54
asaclibpst13:54
asaciirc13:54
ograright, last week there were only these two pressing13:54
dyfetogra: sorry, missed squid...13:54
asaclibgtk2-perl and libpst13:54
asacdyfet: can you work on one of these today?13:55
asacand squid ;)13:55
dyfetasac: yes, I can13:55
asaclibtommath libtunepimp and ossp-uuid13:55
ogragreat13:55
asacalso look like worthwhile candidates13:55
asacok lets move on13:56
GrueMasterNot sure if it is helpful (and I don't have all the details), but apparently there is a fix for gcc for the -fPic issue.13:56
asaci think the image status is quite well documented on the wiki13:57
asaci dont have questions. anyone?13:57
GrueMasterupstream in svn.13:57
asacGrueMaster: which -fPIC issue?13:57
NCommander[topic] ARM Image Status (ogra, persia)
13:57
MootBotNew Topic:  ARM Image Status (ogra, persia))13:57
ograGrueMaster, talk to doko ?13:57
asac4:57 < asac> i think the image status is quite well documented on the wiki13:57
asac14:57 < asac> i dont have questions. anyone?13:57
* ogra doesnt :P13:57
* StevenK neither13:57
NCommander[topic] Any Other Business13:57
MootBotNew Topic:  Any Other Business13:57
persiaWe only currently have server images, but expect to have Ubuntu netbook ones tomorrow.13:58
* ogra wonmders how server could build13:58
StevenKNo glib gets dragged in13:58
ograif basic debootstrapping doesnt work13:58
ograweird13:58
StevenKogra: Ah, because the server is alternate13:58
ograserver uses plymouth13:58
asacyeah. alternate probably does the trick13:59
asacdo we still produce them?13:59
ograserver13:59
StevenKIt would fail to install, but it would still build13:59
StevenKasac: Yes13:59
ograyeah, right13:59
ograanyway, we'Re at AOB ...13:59
ogradid anyone have an idea for gSoC13:59
ograor do we have intrested students attending that would like to run a gSoC project ?14:00
ogra(and look for a mentor in the mobile/arm area)14:00
asacporting the rest of thumb2 ;)14:00
* ogra was pondering to put rootstock up for gSoC14:00
ograasac, that doesnt fit the timeframe :)14:00
ogragSoC will be L+114:01
asac3 month? full time ;)?14:01
asacogra: universe will have plenty of stuff left14:01
GrueMasterToo bad it is restricted to current students.  I have someone that would be interested otherwise, but won't be going to college until fall.14:01
ograGrueMaster, i'm not sure its restricted that closely14:01
StevenKNeither14:01
GrueMasterIt is, we checked.14:01
ograprobably its enough to prove that you are starting to study soon14:01
ogragah14:02
asaci think a "flexible image building" project would be helpful ... or softbootloader maybe14:02
GrueMasterNeed to be enrolled.14:02
ograelasitc images, heh14:02
GrueMasterDoes that mean they bounce back after a hard crash?14:02
ograyeah !14:02
asacok14:03
ograwell, doesnt look like we have anything concrete yet14:03
asacso one more thing: next week part of the team will be in london for training14:03
asacso probably out of office from mon to wed14:03
ograyeah14:03
asaci think persia likes the idea to write meeting minutes ;)14:03
asacor someone else :)14:03
asacout of office will be asac, jamie and ogra14:04
persiaI think them to have been written.  I'll write them if nobody else does, but it's easier to write when people stay on topic.14:04
persias/think/like/14:04
* persia doesn't really like writing minutes in the middle of the night14:05
asacpersia: for today? i mean next week when we are in london ;)14:05
asacok. i think thats it ;)14:05
persiaOh that's fine.  Have fun :)14:05
asaclets go back working/sleeping ;)14:05
ograzzzzZZZZ14:06
asacwhatever is appropriate for the timezone you are in ;)14:06
ogradamned14:06
* ogra had hopes14:06
* persia hopes the chair will exercise the MootBot command soon14:07
* StevenK too14:07
asacNCommander: ^^ #endmeeting please, sir14:07
* ogra thinks the chair is not looking14:07
ograNCommander, E N D M E E T I N G !!!!!!!!!!!!!!!!!!!!14:08
NCommander#endmeeting14:09
MootBotMeeting finished at 08:09.14:09
ograheh14:09
* GrueMaster pinged his cell.14:09
ograhahaha14:09
* NCommander isn't quite here this morning :-/14:09
GrueMasterAnd that is different from other days because...14:10
=== robbiew_ is now known as robbiew
kees\o14:55
cjwatsonhi14:59
pittio/15:02
keesheya pitti.  you, cjwatson, and myself so far.15:02
KeybukI'm here15:02
keesand Keybuk!  :)15:03
cjwatsonmdz: here?15:05
* cjwatson pokes sabdfl15:06
cjwatsonok, so just awaiting mdz15:07
cjwatsonKeybuk: you're the chair, why am I doing this? :-)15:07
sabdflmdz is on holiday15:07
cjwatsonok15:07
Keybukcjwatson: I can't be the chair, again nobody has told me that I am15:07
keesKeybuk: you don't read the meeting minutes?  :)15:08
persiaIt was in the -devel-announce mail15:08
Keybukkees: I am so far behind with my e-mail, I'm close to bankrupcy15:08
keesKeybuk: heh15:09
pittiso, looks like https://wiki.ubuntu.com/TechnicalBoardAgenda isn't current, right?15:10
* pitti tries to find what should be there15:10
sabdfli'll chair15:10
persiaWhy isn't it current?  Lots from last meeting, but that ran out of time.15:10
keespitti: it should be current; I removed all the stuff from last time.15:10
cjwatsonthanks15:11
pittiah, ok15:11
sabdflwhat's the magic incantation to start the mootbot?15:11
pittiI thought the sponsoring merge was by and large done and discussed15:11
cjwatson"#startmeeting"15:11
dholbachthe sponsors item can be dropped from it15:11
persiadholbach: Thanks.15:11
dholbachit's blocked on an RT ticket15:11
cjwatsondholbach: it hasn't been implemented yet; is that on your queue?15:11
cjwatsonah15:11
cjwatsonthat RT ticket is done15:11
dholbachit's on my queue, yes15:11
Keybuk(sorry to be a pain, but I'm so behind on everything at the moment, that I'd spend half the chair time trying to find things)15:12
dholbachcjwatson: 37728 isn't afaics15:12
cjwatsonoh, sorry, I'm thinking of a different RT ticket.  you mean https://rt.admin.canonical.com/Ticket/Display.html?id=3772815:12
cjwatsonI was thinking of the -reviews one15:12
sabdfl#startmeeting15:12
MootBotMeeting started at 09:12. The chair is sabdfl.15:12
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:12
dholbachcjwatson: thanks - I'll see that I can find somebody to look into it15:13
sabdfl[TOPIC] Archive reorganisation (standing item; ColinWatson)15:13
MootBotNew Topic:  Archive reorganisation (standing item; ColinWatson)15:13
sabdflDanielHolbach: merge ubuntu-universe-sponsors and ubuntu-main-sponsors (Discussion)15:13
sabdfldholbach: status?15:13
cjwatsondholbach: is there anything else you want to push forward here other than the -sponsors merge?15:13
cjwatsonsabdfl: see above :-)15:13
dholbachsabdfl: waiting on https://rt.admin.canonical.com/Ticket/Display.html?id=3772815:13
dholbachthe rest will be pretty straight-forward15:13
* persia makes a pro-forma statement about how this shouldn't need TB action15:13
sabdflok15:14
dholbachit can be moved off the agenda15:14
cjwatsonpersia: ?15:14
sabdflemmet hikory mailed about developer permissions, ubuntu membership, and the web of interlinked teams they represent15:14
persiacjwatson: That merging the sponsors queue shouldn't require TB approval.  I wrote a longer mail about it.15:14
cjwatsonoh right15:14
persiaIt doesn't matter, because it's getting done (and all support it)15:14
sabdflpersia: are you clearer now about the requirements?15:14
persiasabdfl: I'm clear about the requirements.  I need to think I bit about infographics and documentation, and I'll send a new proposal.15:15
sabdflokdokey15:15
cjwatsonsabdfl: one moment15:15
cjwatsonsabdfl: I'd like to enquire about your statement "the ability to participate as a developer before fully qualifying for membership"15:15
cjwatsonsabdfl: by that, do you mean a contributor whose changes are reviewed, rather than somebody with upload permissions?15:15
cjwatsonor do you mean somebody with upload permissions?15:16
sabdflper-package upload permissions should not depend on having made a significant and sustained contribution to ubuntu, they should depend on one's credible skills to do that work15:16
sabdfli want to decouple the allocation of membership to the allocation of permissions15:17
sabdflit would be up to teams how they handled that15:17
cjwatsonHmm.  I have a disagreement with that lurking around somewhere, but I can hold it off until I figure out how to articulate it :-)15:17
sabdflokdokey15:17
persiaWe may need to change how we handle those to meet that requirement.  Our current model expects both credibility and significant&sustained (and considers those folk polity for TB&DMB selection)15:17
sabdflas I see it, there will be several ways to participate in development:15:17
gesersabdfl: so you would give someone PPU permission to a person that doesn't qualify for membership?15:18
sabdfl - proposed merges to relevant branches15:18
sabdfl - commit to relevant branches15:18
sabdfl - upload to a package, or package set15:18
sabdfl - join one of the generalist upload teams (core, motu)15:18
sabdflgeser: yes15:18
pittian example for this would be a DD who wants to upload his packages to Ubuntu as well15:18
sabdflconsider a DD, who is perfectly competent to manage... yes15:18
pittiI have no strong opinion whether we'd require membership before approving PPU15:19
persiaSo we'd drop the expectation that that DD had shown activity in Ubuntu for some time, to meet the significant&sustained guideline?15:19
sabdflof course, people do need to *understand* certain things about our development process15:19
sabdflpersia: yes15:19
pittibut it would feel a bit sad to reject the courtesy15:19
sabdflwe don't want people who will break freezes or policy15:19
sabdflpitti: if you mean, we should take the opportunity to collaborate immediately, and not wait for someone to demonstrate a deep commitment to ubuntu specifically rather than the quality of the package, i agree15:20
* persia thinks it takes a full cycle to learn freezes and policy, and that anyone continuing to do stuff actively that long tends to qualify for significant&sustained15:20
sabdfli think folks' enjoyment and appreciation for ubuntu will grow from there15:20
pittiOTOH we don't really expect ubuntu members to understand our freeze policy either?15:21
sabdflanyhow - TB is responsible for developer guidelines and permissions, CC for membership and governance15:21
persiaI'll write something up based on the guidelines, and CC+TB can discuss in that mail thread.15:22
sabdflin this intersection, i'm comfortable taking this path. TB and it's delegated decision makers (the leaders of various teams responsible for package sets) get to structure permissions to get the most efficient participation and quality15:22
sabdflpersia: a picture would be worth well north of 1000 words in this case :-)15:22
sabdflany other comments on archive-reorg?15:22
persiasabdfl: I've been working with an artist, so I'll attach a graphic as well next time.15:22
sabdflok, next15:23
sabdfl[TOPIC] https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy upstream is http://techbase.kde.org/Policies/Minor_Point_Release_Policy/Draft15:24
MootBotNew Topic:  https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy upstream is http://techbase.kde.org/Policies/Minor_Point_Release_Policy/Draft15:24
Riddellstill no change upstram I'm afraid15:24
cjwatsonare we pushing, or waiting?15:24
Riddellit mostly needs me to tidy it up and get agreement15:24
cjwatsonlet's move on then15:25
sabdflRiddell: this looks good, can i ask what the blocker is upstream?15:26
Riddellsabdfl: I just need to find time to answer some people's queries and make the changes they suggested15:26
sabdflwas the idea put forward by them, or us?15:27
Riddellby me15:27
sabdflin general, i think it's brilliant to sync on SRU policies, and do a mutual commitment: they do good updates, we ship 'em15:28
Riddellupstream has an unwritten policy and it seems to make sense to get that written down15:28
sabdflok, sounds good15:28
sabdfl[TOPIC] Units policy - Check up on feedback from Debian TC15:28
MootBotNew Topic:  Units policy - Check up on feedback from Debian TC15:28
keesnothing new here15:29
keesbdale sent it on, but it hasn't gotten any traction.15:29
sabdfl[ACTION] Riddell to get agreement with KDE on point release criteria15:29
MootBotACTION received:  Riddell to get agreement with KDE on point release criteria15:29
sabdfl(i think that will be recorded in the wrong topic, sorry)15:29
sabdflis there anything we can do to catalyse the discussion?15:29
keesi think we need to just move forward with the policy on our end.15:30
sabdflfile bugs?15:30
sabdfl+1 to moving forward15:30
cjwatsonI believe we agreed to move on if we didn't get feedback within a few weeks15:30
keesI think if we tracked the Debian bugs (and obviously our fixes) on the Units wiki page, we'd have something to show Debian if they ask about our status/progress.15:30
sabdflwhy do we always end up doing the work on both sides?15:31
cjwatsonwe don't15:31
cjwatsonthis is just perception bias15:31
pittiKeybuk: is the policy as it is okay for you? I thought you had an objection against the "add --si option to CLI programs" part?15:32
cjwatsonwe do end up doing more work for things we care about and other folks don't, but that's sort of natural :)15:32
Keybukpitti: I do, but I've given up with it15:32
sabdfllet's just tag the bugs a particular way, and put a link in the wiki15:33
sabdflok, quick poll15:34
pitticurrent https://wiki.ubuntu.com/UnitsPolicy looks great to me15:34
keesyeah, I'm good with it15:35
sabdfl[VOTE] Ubuntu will move forward on the https://wiki.ubuntu.com/UnitsPolicy and track bugs with a tag so Debian can find and follow them quickly15:35
MootBotPlease vote on:  Ubuntu will move forward on the https://wiki.ubuntu.com/UnitsPolicy and track bugs with a tag so Debian can find and follow them quickly.15:35
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:35
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:35
pittiI'd perhaps add a third "file size" possibility to just show base-1015:35
kees+115:35
sabdfl+115:35
MootBot+1 received from sabdfl. 1 for, 0 against. 0 have abstained. Count is now 115:35
MootBot+1 received from kees. 2 for, 0 against. 0 have abstained. Count is now 215:35
pitti+115:35
MootBot+1 received from pitti. 3 for, 0 against. 0 have abstained. Count is now 315:35
cjwatson+0 - I don't like the "must" in there for command-line applications any more than Keybuk does, but we can always revise in the future and I don't want to get in the way of the desktop work15:36
MootBotAbstention received from cjwatson. 3 for, 0 against. 1 have abstained. Count is now 315:36
cjwatson(tracking bugs with a tag seems obviously sane)15:36
Keybuk-1 still15:36
MootBot-1 received from Keybuk. 3 for, 1 against. 1 have abstained. Count is now 215:36
cjwatsonwhose votes would change in what way if we changed must -> may?15:37
sabdflmdz is away, i can't see any more expected votes15:37
cjwatsonunder "Exception"15:37
pitticjwatson: +1.1 from me :)15:37
keesheh15:38
pitti(but oh well, ls, du, df, etc. already have that)15:38
cjwatsonI would rather have consensus if we can achieve it15:38
sabdflme too15:38
pittibut so far we just voted about "move forward without waiting on debian"15:38
sabdflKeybuk: what would it take for you to support the proposal?15:38
sabdflis there an estimate in the proposal of how long the string is, for main?15:39
pitti"the string"?15:39
sabdfland is there a "core subset" that would represent the main, meaningful, useful set15:39
sabdflpitti: how much work it is to be done15:39
Keybuksabdfl: I don't really like most of it, but since it's clear the rest of the board are happy, it's not worth me holding it up15:39
cjwatsonI don't think anyone has attempted to work out how many packages are involved15:39
* sabdfl thinks that this could gain momentum if we commit to it15:40
pittiI don't think we should drop everything to comb the archive for violations of that, but we should encourage testers to file appropriately tagged bugs, so that we can start pointing ot the policy in upstream bug reports, etc.15:40
sabdflthe policy is as rational as one could expect15:40
sabdflwe could socialise it with GNU, for example15:40
pittithere is a long discussion in an upstream glib report, for example15:40
sabdfldoes it reference our wiki page?15:40
pittinot yet (since it's not official yet)15:41
sabdflor is there a similar, canonical as it were, policy :-)15:41
pittibut the arguments of the various ML discussions15:41
pittiIf we (as "Ubuntu") would just go ahead and change it, it might be a bit more convincing15:41
cjwatsonI would be surprised if GNU followed a marketing standard (disk sizes as advertised by hard disk manufacturers) over a prior technical standard15:41
cjwatsonpersonally15:41
cjwatsonit's not their style15:41
sabdfli would prefer that we follow GNU, if they develop a policy, than get into a standoff15:42
cjwatsonthey might be persuaded to use consistent terms for each of the units15:42
cjwatsonmost of the GNU packages concerned fall under the "Exception" section, though15:42
sabdfli don't know that it's fair to call it a  "marketing standard", though, since it's consistent and rigorous, isn't it?15:42
cjwatsonit's a standard initiated by hard disk manufacturers wishing to make their disks sound larger15:42
cjwatsonI think it's an entirely fair name :)15:43
cjwatsonI don't know the history on network bandwidth so am not qualified to comment there15:43
pittiI never ever saw base-2 units in networking15:44
persiaMy (dredged) memory on that is that it was related to 1bit/cycle in early wire protocols, so 1MHz ~ 1Mbit15:44
cjwatsonthis is not me saying that we shouldn't pick standard units for these things in desktop-visible parts of Ubuntu, just saying that there is no point being overly hopeful15:44
pittistarting from my old 33.6 kBaud modem up to 100Mbit ethenet15:44
pittiwe could at least fix nautilus15:45
cjwatsonI'm happy with the policy with the exception that I think it's a waste of time to declare a "must" for a bunch of shell scripts that output file sizes :)15:45
cjwatsonor whatever15:45
cjwatsonhence my query above about a modification15:45
pittiit's currently a bit ridiculous to have the computer place show an "80 GB disk" and then you open it and see a 76.32whatnot GB volume15:45
cjwatsonagreed15:45
pitticjwatson: s/must/may/ sounds good to me15:46
pittiI also propose to add a third and preferred file size possibility to just show base-1015:46
pittiadding options everywhere doesn't seem practical nor desirable to me15:46
cjwatsonI think I agree with you15:47
keespersia: yeah, it's from baud, which was always base-10.15:47
pittiKeybuk: with above two changes, would you feel better about it?15:47
Keybukit wouldn't be as bad yeah15:48
* pitti edits page15:49
pittihttps://wiki.ubuntu.com/UnitsPolicy?action=diff&rev2=21&rev1=2015:51
pittihttps://wiki.ubuntu.com/UnitsPolicy?action=diff&rev2=22&rev1=2115:51
pittisabdfl: hm, so maybe we should vote about the actual policy here, now that we decided to unblock on Debian?15:52
sabdflcjwatson: if we say MAY then it's NOTABUG15:52
cjwatsonsabdfl: yup15:52
sabdflif we say MUST, then it's a low importance bug15:52
cjwatson*blink*15:52
pittisabdfl: well, it could be a wishlist bug15:52
cjwatsonif we want it to be a bug but low-importance, that's "should"15:52
cjwatson"must" to me denotes an assertion failure15:52
sabdflI'd prefer that we adopt a policy that says MUST, but say that the bugs can be low importance15:52
sabdflok, i'd be happier with SHOULD then15:53
cjwatsonin many cases I think this change would be actively undesirable15:53
cjwatsonit is better to leave small programs robust and simple than to add complexity to them, in many cases15:53
cjwatsonhence why I think MUST would be a bug in the policy15:53
sabdfli would be happy for the policy to say that, too15:53
* pitti would go with MAY, start fixing GUIs first, and then perhaps adjusting it later on15:53
pittii. e. start small15:54
sabdflok, so it's more an attempt to harmonise, than a standard15:55
sabdflok, that's fine, i'd +1 that15:55
cjwatsonharmonising the GUI is a lot more important than the rest of it, I think15:55
sabdflhow do i finish the existing vote?15:55
sabdfl[/VOTE]15:56
sabdflnup15:56
cjwatson[ENDVOTE] or #endvote, I can never remember which15:56
geser"#endvote" or "[ENDVOTE]"15:56
sabdfl[ENDVOTE]15:56
MootBotFinal result is 3 for, 1 against. 1 abstained. Total: 215:56
cjwatsonhttps://wiki.ubuntu.com/ScribesTeam/MootBot15:56
Keybuk"/msg #irc-ops please k-line mootbot" works, I find :p15:56
sabdfl[VOTE] Ubuntu will adopt https://wiki.ubuntu.com/UnitsPolicy15:56
MootBotPlease vote on:  Ubuntu will adopt https://wiki.ubuntu.com/UnitsPolicy.15:57
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:57
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:57
sabdfl+115:57
MootBot+1 received from sabdfl. 1 for, 0 against. 0 have abstained. Count is now 115:57
pitti+115:57
MootBot+1 received from pitti. 2 for, 0 against. 0 have abstained. Count is now 215:57
Keybuk+115:57
MootBot+1 received from Keybuk. 3 for, 0 against. 0 have abstained. Count is now 315:57
cjwatson+115:57
MootBot+1 received from cjwatson. 4 for, 0 against. 0 have abstained. Count is now 415:57
Keybuk(on the basis the policy currently says "may")15:57
pitti^ it does now15:57
pittikees?15:59
kees+115:59
MootBot+1 received from kees. 5 for, 0 against. 0 have abstained. Count is now 515:59
pittisabdfl: looks unanimous :)16:00
sabdfl[ENDVOTE]16:00
MootBotFinal result is 5 for, 0 against. 0 abstained. Total: 516:00
sabdflphew16:00
sabdflthanks all16:00
sabdflmotion carried16:00
* pitti removes the "draft"16:00
sabdflhttps://bugs.edge.launchpad.net/ubuntu-community/+bugs?field.assignee=techboard16:00
sabdflonly the one, about my position16:00
sabdfldholbach, what's the url for the leadership-appointment page, which mentions this?16:01
dholbachhttps://wiki.ubuntu.com/CommunityCouncil/RestaffingProposal16:02
dholbachsabdfl: I hope that's the one you meant?16:02
sabdflthat page isn't final, but it mentions this special-case16:02
sabdflcan i close the bug?16:02
dholbachsounds good to me16:03
pittisounds fine16:03
dholbachI'll ping everybody for a round of feedback on the document again, then we can go and approve it16:03
sabdflok, dholbach will you close the bug when it's approved?16:04
dholbacheffectively it's what "we've been doing all the time", so another round of feedback and renaming the doc should be fine16:04
dholbachsabdfl: I can do that too, sure16:04
sabdfl[ACTION] dholbach to finalise LeadershipAppointment page, and close bug on sabdfl role in TB16:04
MootBotACTION received:  dholbach to finalise LeadershipAppointment page, and close bug on sabdfl role in TB16:04
sabdfl[TOPIC] Discuss https://lists.ubuntu.com/archives/edubuntu-devel/2010-February/003323.html16:04
MootBotNew Topic:  Discuss https://lists.ubuntu.com/archives/edubuntu-devel/2010-February/003323.html16:04
sabdflwhy do they need to do this: "The ~ubuntu-core-dev[5] and ~developer-membership-board[6] teams have16:05
sabdflbeen invited to join the ~edubuntu-dev team."16:05
sabdfl?16:05
cjwatsonstandard practice for delegated teams16:05
sabdflis that a soyuz permissions limitation, that requires clusterfscking the teams?16:05
cjwatsontwo different issues16:06
pittiu-core-dev is good to have for being able to commit to their branches16:06
cjwatson~developer-membership-board should be able to administer all the delegated teams (we agreed a while back)16:06
cjwatsonand what pitti said16:06
sabdflso DMB is added as an admin16:06
sabdflthe branch commit thing seems like something that could be fixed in LP16:06
pittisabdfl: eventually it will, with the auto-imports16:07
cjwatsonI think it mostly works already16:07
sabdflok16:07
pittibut right now it's still required for manually created branches16:07
cjwatsonbut there are some edge cases, like seeds, that are difficult to address16:07
=== yofel_ is now known as yofel
cjwatsonI agree that it is a workaround16:07
sabdfl[VOTE] Edubuntu Council to assume responsibility for edubuntu-dev as per https://lists.ubuntu.com/archives/edubuntu-devel/2010-February/003323.html16:07
MootBotPlease vote on:  Edubuntu Council to assume responsibility for edubuntu-dev as per https://lists.ubuntu.com/archives/edubuntu-devel/2010-February/003323.html.16:07
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 MootBot16:07
MootBotE.g. /msg MootBot +1 #ubuntu-meeting16:07
sabdfl+116:07
MootBot+1 received from sabdfl. 1 for, 0 against. 0 have abstained. Count is now 116:07
cjwatsonlet's just be explicit, this is also a request for edubuntu-dev to be allowed to upload to packages in the edubuntu package set, yes?16:08
sabdflyes16:08
cjwatsonI just noticed that that was mentioned nowhere explicitly in the mail, but there isn't much point otherwise :)16:08
sabdflat least, that's my understanding, if that's what kubuntu-dev does16:08
cjwatsonit is16:08
kees+1 (looks to me like the right set of people in that council)16:09
MootBot+1 received from kees. 2 for, 0 against. 0 have abstained. Count is now 216:09
Keybuk+116:09
MootBot+1 received from Keybuk. 3 for, 0 against. 0 have abstained. Count is now 316:09
cjwatsonI'm happy with the request, Edubuntu has been quite active of late and it's good to see them getting organised like this16:09
pittiI know three members from the current team pretty well, and I trust stgraber to pick good developers (he is also in the DMB after all)16:09
cjwatson+116:09
MootBot+1 received from cjwatson. 4 for, 0 against. 0 have abstained. Count is now 416:09
pittithus16:09
pitti+116:09
MootBot+1 received from pitti. 5 for, 0 against. 0 have abstained. Count is now 516:09
sabdfl[ENDVOTE]16:09
MootBotFinal result is 5 for, 0 against. 0 abstained. Total: 516:09
sabdflyay!16:09
sabdflmotion carried, congratulations, edubuntu16:10
cjwatsonI'll implement16:10
sabdflalright, on the chair, may I suggest we rotate alphabetically?16:10
cjwatsonby first name?  that would be mdz next then16:10
sabdfl[ACTION] cjwatson to implement edubuntu-dev delegations16:10
MootBotACTION received:  cjwatson to implement edubuntu-dev delegations16:10
cjwatsonthanks16:10
sabdfli don't mind on what basis, could be last letter of first name :-)16:10
cjwatsonor by nick, in which case I think it would be me16:10
sabdflnick it is16:11
sabdflthat way, we can spend less time wondering16:11
cjwatsonBRAIN FILLED WITH IRC16:11
cjwatsonok16:11
sabdflfolks can arrange substitutions, but the skeleton is fixed16:11
sabdflthanks colin16:11
sabdfland thanks all, apologies for tardy timekeeping16:11
sabdfl#endmeeting16:11
MootBotMeeting finished at 10:11.16:11
KeybukOne piece of OB16:11
LaneyCan I quickly ask that you guys respond to my CLI/mono mail?16:11
cjwatsonwe didn't start until :12 anyway :-)16:11
cjwatsonLaney: our bad, will do16:12
Keybukfor the purposes of appropriate notification, I'm considering stepping down from this board16:12
KeybukI haven't made a decision yet, but will do so before the next meeting16:12
cody-somerville:o16:13
JFoo/16:59
amitk\o17:00
ckingo/17:00
ogasawarayo17:00
* pgraner o/17:00
bjfRoll Call17:00
manjo..17:01
jjohansen\o17:01
bjf#startmeeting17:01
MootBotMeeting started at 11:01. The chair is bjf.17:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:01
* apw zones in17:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid17:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting17:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid17:01
bjfNOTE: '..' indicates that you are finished with your input.17:01
bjf[TOPIC] Open Action Item: None17:01
* smb holds up his cup of tea in a greeting gesture17:01
MootBotNew Topic:  Open Action Item: None17:01
bjf[TOPIC] Release Metrics: (JFo)17:02
MootBotNew Topic:  Release Metrics: (JFo)17:02
JFoRelease Meeting Bugs (4 bugs, 7 blueprints)17:02
JFo===17:02
JFoBeta 1 Milestoned Bugs (74 bugs against all packages (up 12))17:02
JFo * 9 linux kernel bugs (up 1)17:02
JFo * 1 linux-fsl-imx51 bugs (no change)17:02
JFo * 1 linux-ec2 bug (no change)17:02
JFo * 1 linux-mvl-dove bugs (up 1)17:02
JFo===17:02
JFoRelease Targeted Bugs (207 bugs against all packages (up 43))17:02
JFo * 24 linux kernel bugs (up 6)17:02
JFo * 1 linux-fsl-imx51 bugs (no change)17:02
JFo * 1 linux-ec2 bug (no change)17:02
JFo * 2 linux-mvl-dove bugs (up 2)17:02
JFo===17:02
JFoMilestoned Features -17:02
JFo * 0 blueprints17:02
JFo..17:02
bjf[TOPIC] Blueprints: kernel-lucid-bug-handling (JFo)17:02
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-bug-handling17:02
MootBotNew Topic:  Blueprints: kernel-lucid-bug-handling (JFo)17:02
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-bug-handling17:02
JFo* I'm almost done with my analysis of the X debugging pages. I will update the team on the current state of the Kernel Team pages and my initial draft of recommended changes to the structure and layout via the e-mail list.17:02
JFo * I'll have the arsenal scripts running (not in dry run mode) by the end of this week.17:02
JFo..17:02
bjf[TOPIC] Blueprints: kernel-lucid-kernel-config-review (apw)17:03
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-config-review17:03
MootBotNew Topic:  Blueprints: kernel-lucid-kernel-config-review (apw)17:03
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-config-review17:03
apwWe have pulled out the HID devices to modular.  Discussions on other drivers still pending, any changes will have to occur post beta-1 now.17:03
apw..17:03
bjf[TOPIC] Blueprints: kernel-lucid-kms (sconklin / apw)17:03
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kms17:03
MootBotNew Topic:  Blueprints: kernel-lucid-kms (sconklin / apw)17:03
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kms17:03
apwWe have committed to the v2.6.33 drm backport which is now uploaded to the archive.  Re-testing of graphics issues now to be requested.17:03
apw..17:03
sconklin..17:03
bjf[TOPIC] Blueprints: kernel-lucid-suspend-resume (manjo)17:04
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume17:04
MootBotNew Topic:  Blueprints: kernel-lucid-suspend-resume (manjo)17:04
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume17:04
manjo..17:04
bjf[TOPIC] Blueprints: kernel-lucid-apparmor-development (jjohansen)17:04
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-apparmor-development17:04
MootBotNew Topic:  Blueprints: kernel-lucid-apparmor-development (jjohansen)17:04
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-apparmor-development17:04
jjohansenEditing text for another push to LKML17:04
pgranerbjf, JFo: we need to put out a CFT for the .33 drm stack asap17:04
* JFo makes a note17:04
apwpgraner, i think that X are meant to be doing that, so you might want to check17:05
cndCFT?17:05
apwcall for testing17:05
JFoCall For Testing17:05
bjfbjf, wonders why I'm being told that17:05
cndk17:05
JFo..17:05
pgranerbjf: for an action item, no more17:05
bjf[ACTION] we need to put out a CFT for the .33 drm stack asap17:05
MootBotACTION received:  we need to put out a CFT for the .33 drm stack asap17:05
pgranerJFo: pls check with Bryce on the X testing17:06
JFopgraner, ack17:06
jjohansenI still have a few LSM audit issues to attend to and we will see how the __d_path discussions play out.  Currently trying to keep the 2 pushes separate17:06
jjohansen..17:06
bjf[TOPIC] Blueprints: kernel-lucid-boot-performance (apw, csurbhi)17:07
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-boot-performance17:07
MootBotNew Topic:  Blueprints: kernel-lucid-boot-performance (apw, csurbhi)17:07
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-boot-performance17:07
apwNothing to report.17:07
apw..17:07
bjf[TOPIC] Other Release Tasks: Lucid Audio Support (bjf)17:07
MootBotNew Topic:  Other Release Tasks: Lucid Audio Support (bjf)17:07
bjfNothing new this week.17:07
bjf..17:07
bjf[TOPIC] Other Release Tasks: Lucid Better Power Mgt (amitk)17:07
MootBotNew Topic:  Other Release Tasks: Lucid Better Power Mgt (amitk)17:07
amitkPushed some power policy scripts to https://code.edge.launchpad.net/~amitk/ubuntu/lucid/pm-utils-powersave-policy/amit17:07
amitkwill prepare a package in PPA and issue call for testing tomorrow17:08
amitkpitti is going to review them in the mean while, but other comments welcome17:08
amitk..17:08
bjf[TOPIC] Other Release Tasks: EC2 Lucid Kernel Status (jjohansen)17:09
MootBotNew Topic:  Other Release Tasks: EC2 Lucid Kernel Status (jjohansen)17:09
jjohansenBug #527208 is still outstanding17:09
ubottuLaunchpad bug 527208 in linux-ec2 "ec2 instance fails boot, no console output on c1.xlarge" [High,Confirmed] https://launchpad.net/bugs/52720817:09
jjohansenother than that no known issues17:10
jjohansenhowever it may be affecting more than just c1.xlarge kernels17:10
jjohansenjust not reliably17:10
jjohansenand of course its one of those bugs we get no, debugging info for17:11
jjohansen..17:11
bjf[TOPIC] Status: Lucid (apw)17:11
MootBotNew Topic:  Status: Lucid (apw)17:11
apwLucid remains at stable v2.6.32.9.  As mentioned above we have taken the v2.6.33 DRM backport as this greatly improves stability and removes the need for the Nouveau LBM module, cleaning up installs.  We have also incorporated building the kernel perf tool.17:11
apwAll of the main kernel (linux, linux-fsl-imx51, linux-mvl-dove, and linux-qcm-msm) are now closed for the Beta-1, uploaded and building, linux-ec2 has been tested and pending a build-test is ready to upload.  Anything which requires a kernel change will have to wait until after beta-1 and will have to pass the abbreviated SRU process (2 acks required).17:12
apw..17:12
bjf[TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (gnarl/smb)17:12
MootBotNew Topic:  Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (gnarl/smb)17:12
smbDapper:      2.6.15-55.82  (security)17:12
smbHardy:       2.6.24-27.65  (security)17:12
smb             2.6.24-27.67  (proposed)[15]   1/ 3 verifications done (+0)17:12
smbIntrepid:    2.6.27-17.45  (security)17:12
smbJaunty:      2.6.28-18.59  (security)17:12
smbKarmic:      2.6.31-20.57  (updates)17:12
smb - LBM       2.6.31-20.22  (updates)17:12
smb - mvl-dove  2.6.31-211.22 (security)17:12
smb             2.6.31-211.23 (waiting for acceptance)17:12
smb - fsl-imx51 2.6.31-108.21 (security)17:12
smb             2.6.31-108.23 (proposed)[5]  0/ 1 verifications done (+0)17:12
smb - ec2       2.6.31-304.11 (updates)17:13
smbHardy is just about to move to updates.17:13
smbComing up another security update, then final big upload for Karmic.17:13
smb..17:13
bjf[TOPIC] Incoming Bugs: Regressions (JFo)17:13
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)17:13
JFoIncoming Bugs17:13
JFo280 Lucid Bugs (up 95)17:13
JFoCurrent regression stats (broken down by release):17:13
JFo==== regression-potential (up 29) ====17:13
JFo  * 86 lucid bugs17:13
JFo==== regression-update (up 1) ====17:13
JFo  * 11 karmic bugs17:13
JFo  * 5 jaunty bugs17:13
JFo  * 2 intrepid bugs17:13
JFo  * 1 hardy bug17:13
JFo==== regression-release (down 2) ====17:13
JFo  * 56 karmic bugs17:13
JFo  * 22 jaunty bugs17:13
JFo  * 11 intrepid bugs17:13
JFo  * 4 hardy bugs17:13
JFo==== regression-proposed (no change) ====17:13
JFo  * 1 karmic bug17:13
JFo..17:13
bjf[TOPIC] Incoming Bugs: Bug day report (JFo)17:13
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)17:14
JFoThere was no bug day last week. This is a gentle reminder that we have decided to hold a weekly Kernel Bug Day to deal with regression bugs. What this means is that for one day a week we would like for the kernel team to focus on addressing 'regression-' tagged bugs. We'd like to see a significant reduction in the numbers reported above.17:14
JFohttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-potential+regression-release+regression-proposed+regression-updates&field.tags_combinator=ANY17:14
JFoThe plan, as I see it, is to implement this up to release and then discuss the continued utility of having a Kernel Team Bug Day much like the Bug Days we have now with the community.17:14
JFoThe next Bug Day will be next Tuesday. The focus will be on Bugs with patches attached. As usual, all are welcome to help, and all help is greatly appreciated. :)17:14
JFoany thoughts?17:14
apwseems good, we want a real focus on regressions in lucid17:15
JFoI think this is a good start17:15
JFowe can refine as needed17:15
JFoI'd also like to keep the community focussed bug day stuff17:15
JFounless any of you feel that is too much17:15
smbJFo, Did yo mention here when that kernel team day will be?17:16
manjosmb, tue17:16
JFoI don't think I did here smb17:16
smbmanjo, THought that is community day17:16
JFoThe Kernel Bug Day will be on Tuesday of every week until release17:16
smbok, so same day17:16
apwnormally we have a community section17:17
JFoThe community bug days will be scheduled for Tuesdays as well unless we think it should be moved.17:17
JFoI am flexible on that17:17
JFowe can discuss offline.17:17
JFo..17:17
bjf[TOPIC] Open Discussion or Questions: Anyone have anything?17:17
MootBotNew Topic:  Open Discussion or Questions: Anyone have anything?17:17
apwo/17:18
JFoI do...17:18
bjfgo apw17:18
apwWe are now basically frozen for Beta-1 (barring kitten killers), I will be pushing out any tasks which required kernel changes to Beta-2 shortly, there is almost nothing in this category.  The remainder of our non-release tasks for Beta-1 need focus, and if they aren't going to make it I want to know.17:18
JFoSeveral links that you may find useful:17:18
JFohttps://bugs.edge.launchpad.net/~kernel-bugs/+packagebugs17:18
JFohttps://bugs.edge.launchpad.net/~kernel-bugs/+patches?start=50&batch=5017:18
apw..17:18
JFothe first is a breakdown of bugs by package17:18
JFothe second is a view created by the Launchpad team of bugs with patches by age17:18
bjfthe chair has not yet recognized JFo :-)17:18
manjoapw, when is the last upload you are doing ? before kernel freeze ?17:18
JFowhoops :)17:18
apwmanjo, they are already in the pipe17:19
apwwith a 6 hour build time one needs a days slack17:19
bjfJFo, you now have the floor17:20
JFoheh, sorry about that17:20
bjfcost you a beer for everyone17:20
JFothe only other thing I have on the above is the fact that the second link is not completely accurate yet17:20
apw192 beers ouch17:20
amitk:)17:20
JFobjf, I'm ok with that for the kernel team ;)17:20
JFo..17:21
bjfanyone else?17:21
bjfthanks everyone17:21
bjf#endmeeting17:21
MootBotMeeting finished at 11:21.17:21
* manjo thanks bjf 17:21
smbbjf, Ta17:21
JFothanks bjf17:21
csurbhithanks bjf17:21
ckingta bjf17:21
JFoapw, my apologies for stomping on your remarks17:21
JFo:)17:21
apwjfo np17:21
=== mcasadevall is now known as NCommander
=== jamie is now known as Guest26145
=== Guest26145 is now known as JamieBennett
=== mcasadevall is now known as NCommander
=== dutchie_ is now known as dutchie
=== Claudinux_ is now known as Claudinux

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