/srv/irclogs.ubuntu.com/2009/12/01/#ubuntu-meeting.txt

=== robbiew is now known as robbiew_
=== bjf is now known as bjf-afk
=== asac_ is now known as asac
=== Ioneye is now known as Ion[AFK]
meanburrito920_valgrind complains that my code has a jump that depends on an uninitialized value, but I believe that is what I want (check if a value is null before operating on it). Is this the correct behavior, or should I tell valgrind to ignore it?01:49
st33medmeanburrito920_, wrong roo01:49
st33medroom01:49
meanburrito920_oops01:49
meanburrito920_sorry, thought I was on ##programming :)01:49
=== jtisme is now known as jtholmes
Keybukmeanburrito920_: damnit, I want to answer your question <g>02:42
Keybukwhy do you think that the value is NULL to begin with?:02:43
KeybukI suspect your error is that you're assuming the value has been initialised to NULL02:43
Keybukwhen, in fact, it hasn't02:43
Keybukso you really are comparing uninitialised data02:43
Keybukwhich is clearly the exact opposite of what you want02:43
Keybuksince uninitialised data may well not be NULL <g>02:43
meanburrito920_i dont know if it will be null; it gets passed in from a function02:43
Keybukright, valgrind follows things through02:44
meanburrito920_lets move this discussion to ##programming instead of using this channel02:44
=== nxvl_ is now known as nxvl
=== cjwatson_ is now known as cjwatson
asachi13:00
StevenKO hai13:00
ogramoop13:00
* plars is13:01
davidmhello13:01
asacGrueMaster: dyfet: JamieBennett: meeting O'clock ;)13:02
cooloneyhello folks13:02
dyfethi13:02
asachi cooloney13:02
davidmwho is running the meeting?13:02
* GrueMaster Zzzzz.13:02
* ogra saw GrueMaster 13:02
asacdavidm: me i guess13:02
ograNCommander didnt hand it off to anyone :(13:02
asacdavidm: is using mootbot essential?13:02
davidmasac, you need to start mootbot13:02
ograwe usually use it13:03
davidmasac, yes it logs the minutes13:03
asac#startmeeting13:03
MootBotMeeting started at 07:03. The chair is asac.13:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]13:03
ericmhi, all13:03
ericmI assume this is a public meeting?13:03
asachttps://wiki.ubuntu.com/MobileTeam/Meeting/2009/2009120113:04
ograericm, yup13:04
asac[LINK] https://wiki.ubuntu.com/MobileTeam/Meeting/2009/2009120113:04
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2009/2009120113:04
asac[TOPIC] Specification Review13:04
MootBotNew Topic:  Specification Review13:04
asac[LINK] https://blueprints.edge.launchpad.net/ubuntu/lucid/+specs?searchtext=mobile+lucid13:04
MootBotLINK received:  https://blueprints.edge.launchpad.net/ubuntu/lucid/+specs?searchtext=mobile+lucid13:04
=== persia` is now known as persia
asacso first thank you everyone for the spec work done13:05
ogramobile-lucid-arm-gcc-v7-thumb2 should be marked informational (since it was informational)13:05
asacogra: the idea is to document the rebuild procedure etc. there13:05
asacwill be finished today.13:05
ograright, but does that make it less informational ?13:05
ograits only documenting what we do on the go, no ?13:06
asacogra: it has actions attached13:06
ograwell, apw attached one today13:06
ograwhich he already solved13:06
asacogra: no. i mean: the rebuild archive notes have actions13:06
asacwe should track imo13:06
ograok13:06
asacok13:07
ograi thought that was covered by the lib testing one13:07
asacso one thing we need to ensure is that the milestone target is about right by end of today13:07
ograif people arent aware yet davem created https://wiki.ubuntu.com/ARM/Thumb2 for the transition13:07
asacthere are quite a few with alpha-1 milestone ... which afaict sounds too eager13:07
asacogra: right. that will be referenced from the gcc spec13:08
ogracurrently it doesntz look like we can even make A113:08
ograbut i'll elaborate later (in the ARM topic)13:08
asacright13:08
asacJamieBennett: mobile-lucid-une-2d-launcher ... you think its realistic to have something at alpha-1?13:08
* asac answers questions and moves it to alpha-213:09
asacogra: mobile-lucid-imx51-debian-cd-to-uboot ... is imx51 uboot done already?13:10
ogranope, only proof of concept13:10
ograbut based on that i should be able to implement it until A213:10
asacogra: implemente == includes the cleanup/unification?13:10
ograthe image issues we have are more serious, i'm concentrating my dev/debug work on that atm13:10
asack13:11
ograno, unificatrion is NCommanders work, the uboot stuff for imx51 is the stuff thats not unifyable13:11
asacok but alpha-2 seems reasonable -> targetted for that milestone13:11
asacright. just wanted to understand what work will be done by alpha-2 then13:11
ograyeah13:11
asacmobile-lucid-arm-alternate-images -> targetted for alpha-1 ...13:12
ograi guess they buiold, didnt look depply yet13:12
asacgiven that ncommander is on vacation till shortly before alpha-1, i would think thats not happening in time13:12
ograhmm, no, they dont13:12
ograthere were no needed changes13:13
persiaRetargeting alternates for alpha-2 seems right.  There might be some for alpha-1, but they wouldn't be well tested.13:13
ograwe used to build them before13:13
persiaWe built them, but I don't think we tested the installs much.13:13
ograso the general builds should just happen13:13
asacok doing.13:13
ograright13:13
ograwell, i tested all imx51 once during karmic13:13
asaci think the milestone we communicate in the spec should be the "beta available" delivery13:14
ograbut not for each milestone13:14
asacso if we have QA and bugfixing actions they can be done after the mentioned milestone13:14
ogratesting alt. images simply takes to long13:14
persiaThat's good to hear.  I thought they were even less tested than that.13:14
asacso "Smoke-test ARM alternate images built by the build system [2 days]: TODO"13:14
ograthey all had bugs :)13:14
asacneeds more days?13:14
ograsmoke test should be doable in 2 days13:15
persia2 days is enough to smoke-test 2 flavors on 2 boards, I'd say.13:15
ograproper testing would need more13:15
persiaYeah.13:15
asacok i think smoke test is what is covered by the spec13:15
asacthe rest should go into our QA processes13:15
ogra(alt install test on the babbage takes at least 3h per installation ... vs 1h for live)13:15
asacok next one: mobile-lucid-bringup-testing13:15
plarsasac: I'll have it partially done at A1, but would like to target for a2 completion13:16
asacplars: i think this is mostly about documenting/specification of the testing and some checkbox support13:16
asacplars: ok. so documentation/specification by A1, implementation/automization by A2?13:16
plarsasac: we need some additional tests, and a checkbox plugin13:16
plarsand a few other bits13:16
plarsright13:16
asacok13:17
asaclets target it officially for alpha-2 then13:17
asacplars: if you have work items yo know that will be finished for alpha-1 you can use this syntax:13:17
asacWork items (MILESTONE):13:18
asac...13:18
plarsok13:18
asacMILESTONE=alpha-1 etc.13:18
asacsame for everyone ... if you want to split the work in chunks by milestones, you can use that syntax (pitti is working on implementating this for the burndownchart thing)13:18
asacnext: mobile-lucid-arm-lightweightbrowser13:19
asaci think we should target both: optimized firefox as well as a chromium browser in archive for alpha-213:19
dyfetOkay....and a2?13:19
asacthere will be some issues that might take till beta, like how to best integrate with mailto/doc content on the desktop13:20
asacbut those should be tracked in other specs imo13:20
dyfetThe one I noted was with gconf keys for default browser, but yes, there is likely other issues13:20
asacdyfet: there is quite a few things to evaluate/implement. lets talk about that after meeting13:21
dyfetagreed13:22
asacnext: per-soc-powermanagement -> ogra, i assume we target that for alpha-2 too?13:22
ograyeah, at least13:22
ograwe need to wait for the new kernels anyway13:22
asacogra: you are the assignee i guess?13:22
ograyep13:22
ograat least i have most of the action items13:22
asacogra: can you add the "wait for new kernel" action item?13:23
ograthough its spread across people and teams13:23
ograyup13:23
ograit just struck me today that it doesnt makes sense to fiddle with the old kernels13:23
asacogra: ok. so alpha-3 is more realisitic?13:23
ograhuh, i cant edit13:23
ograoh, somhow LP logged me out13:23
asachehe13:24
ograyeah, i guess13:24
ograericm, cooloney, any ETA for new kernels ?13:24
ogra(we currently have the karmic ones only)13:24
davidmogra, I think we have the kernel for Freescale it's not planned to change13:24
ericmogra, not atm13:24
cooloneyogra: as we just talked in #kernel13:24
ogradavidm, i was told differently by the kernel team today13:24
cooloneysince lucid imx51 kernel will still be .3113:24
=== fader|away is now known as fader_
cooloneyit will not be compiled into thumb2,13:24
cooloneyjust let you guys know that.13:25
ogradavidm, the lucid kernel will use the complete new FSL drop instead of our forward ported patches13:25
ogradavidm, which definately adds delay13:25
davidmogra, not until such time as Freescale drops one13:25
asacok lets add a agenda item about "kernel status" and continue with specs for now?13:25
cooloneyogra: yeah, seperate tree13:25
ogradavidm, which is due this week13:25
ograyes13:25
asacnext is mobile-lucid-arm-device-tree-support13:26
asacJamieBennett: i assume that is earliest at alpha-3?13:26
ericmasac, I think jk has done some prototyping work on this13:27
asacJamieBennett: do you want a standalone agenda item to report about the progress monitoring?13:27
asac"Weekly monitoring of Grants git tree and report progress (until delivery DATE): TODO"13:27
ericmhttps://wiki.ubuntu.com/KernelTeam/ARMDeviceTrees13:28
asac[LINK] https://wiki.ubuntu.com/KernelTeam/ARMDeviceTrees13:28
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ARMDeviceTrees13:28
asacok tentatively targetted for alpha-3 now13:28
asacnext: mobile-lucid-arm-suspend-resume-testplan13:29
asaci think we need to finish drafting this. i added summary/rational/design to the wiki page already13:29
asacplars: want to fill in the Implementation details maybe?13:29
plarsasac: during the discussion, the implementation details were supposed to be filled in by those who came up with the tests13:30
asacits mostly filling in a table where we can track progress on each testcase i think13:30
asacright. imo we should fill in the points now... then as one workitem, assign individual testcases to martinbogo etc.13:30
asacto fill in details, and implement in checkbox if possible13:31
plarsok13:31
asacok i set you as a drafter for now. we can talk about this after the meeting13:31
plarssounds good13:31
asaclets also decide on the target milestone then.13:32
asacnext one: mobile-lucid-arm-une13:32
asacStevenK: ok to merge this into the application-choices?13:32
dyfetI took stevenk's suggestion to do so....so I hope it is :)13:33
dyfetmobile-lucid-arm-application-choices13:33
* asac tries to do that now13:33
asacok that is a bit harder ... will do after meeting13:34
asacnext is mobile-lucid-arm-debian-cd-cleanup13:34
asaci assume that is blocked by the uboot for freescale13:35
asacsomewhat13:35
ograyep13:35
asacso cannot happen by alpha-213:35
asac-> alpha-313:35
ograit can13:35
ograit cant happen before13:35
asacok targetted for alpha-313:35
ograthe proof of concept i have is pretty fast to implement once i cleaned up the code both should be possible to happen hand in hand for the same milestone13:36
asacogra: right. alpha-3 doesnt mean that everything has to happen _after_ alpha-2 ;) ... we can do as much as possible before13:36
ogra(depending on michael indeed, my side shouldnt block here though)13:36
asacok13:36
asacnext is mobile-lucid-arm-ext-images13:37
asacfirst ... is that really "Medium" priority?13:37
asacrather than low?13:37
* ogra guesse that waits until after NCommanders holidays 13:37
asacwhat win do we get from that?13:37
ogranothing really13:37
ogracomplication of the build process mainly :)13:37
asacok ... so priority Low i guess. feels like a beautification excersize to me13:38
ograand hardlink support in the images (which we dont need)13:38
ograi wouldnt even call it beautification :)13:38
asacso how much ease would we gain from having ext2?13:38
asachmm13:38
ograit was triggered by the fact that the vfat images had a bug13:38
ograand cant use symlinks13:38
asacright. but that is fixed afaict (the bug)13:39
ograboth issues are solved13:39
asacbut would symlinks be something we want?13:39
ograswitching the image build scripts to make ext2 iomages will definately add a lot complexity13:39
ograwe dont need symlinks13:39
asacok lets put it to Low13:39
asacand maybe consider to not implement this13:39
ograit only has a single action item anyway, no ?13:40
* ogra remembers persia's going over the TODOs and busting one by one in the session13:40
davidmI'm in favor of dropping if we gain nothing13:40
ograwith proper and valid arguments :)13:40
asacdavidm: right. but lets not just kill it while ncommander is gone. i noted it in the whiteboard to consider dropping it13:41
ograi would leave the banchmark thing in13:41
ograit will at least gain us some info we might be able to use later13:41
asacnext is mobile-lucid-efficient-install-testing13:41
ograall other TODOs depend on that one13:42
asacplars: what milestone would you like to target this for?13:42
plarswhen do we expect to have images building?13:42
asacplars: feels like its something that is partly on QA team side13:42
plarsit is13:42
asacplars: asap13:42
plarsthey need to create virtual milestones to track this13:42
asacplars: ok. have you discussed this in their meeting?13:42
plarsneed someone with access to the iso tracker admin functions to do that13:42
asaclike: getting feedback if they are supportive etc.13:43
plarsasac: no, but discussed with ara at UDS, I didn't get the impression that it would be that big of a deal13:43
asacok. lets target it for alpha-2 then too for now... but with option to push the full implementation13:43
plarsI don't think there's a huge rush with it, due to the nature of the testing being done13:43
plarsthat works for me13:44
asacright. i see this more as a gradually process. first get it setup etc. in the end make it become standard procedure for the QA team13:44
asacetc.13:44
plarsthe focus is on mobile images for the moment13:44
plarsbut they may be interested in picking it up for others as well13:44
plarsin reality, doing it *anywhere* has wide reaching benefits, since often times the install bugs are pervasive across all arches13:45
asacok. so for mobile images we can probably make this happen as soon as we get the iso tracker suppor then13:45
asac*nod*13:45
JamieBennettdamn, sorry, had to go down the school to pick up a kids, accident but she's OK though.13:46
* JamieBennett reads backchat13:46
ograwe have iso tracker support ...13:46
ograit just has a few bugs, but we use the tracker since karmic13:46
asacJamieBennett: we almost didnt notice ;) ... read backlog what we did to your specs ;)13:46
asacnext is mobile-lucid-une-casper-speedup13:46
ografor which you just showed up in time :)13:46
JamieBennett:D13:46
asacJamieBennett: according to work items most is planned to be done by alpha-2 (with a good bunch for alpha-1)13:46
asacis that still accurate?13:47
asacthe alpha-1 work itesm at least feel a bit at risk13:47
asac(to me)13:47
JamieBennettYep, going to start on that when I finish packaging up netbook-launcher-efl today-ish13:47
ograand it assumes we make A113:47
ograwrt images13:47
JamieBennettogra: indeed13:47
JamieBennettI can profile karmic though with timestamps in the casper.log file13:48
ograthats a good start13:48
asacok . targetted the investigation part for alpha-2 ... commented that the actual speedup fixes obviously can take till final ;)13:48
JamieBennettgive us a good idea of where to start looking13:48
ograright, lucid wont change so much here so the karmic numbers should be helpful enough13:48
asacnext mobile-lucid-arm-application-choices: i think that most stuff is well targetted for alpha-2 as well13:48
ogramodulo thumb2 improvements13:49
asaci will fork out two more specs: a -webservices-mail-integration ... and -webservers-gdoc-integration13:49
asacas those are bigger working blocks13:49
dyfetthere was a couple of questions deferred at UDS related to this...13:49
asacright13:50
asacmusic player13:50
asacmail13:50
asacopenoffice13:50
asacthose three need work/exploration during the cycle13:50
asacso lets move those out to separate specs imo.13:50
dyfetOkay13:50
asacdyfet: can you do a quick write up of the music player spec? e.g. what was discussed, what requirements found etc.?13:51
dyfetYou mean here or after?13:51
asacanyway. back on topic. i think for the rest its safe to have it for alpha-213:51
asacdyfet: after ... but we should get most done by today ;)13:51
dyfetI will attach it to the current wiki spec page as a separate notes item...13:52
asacdyfet: lets sync on this after meeting13:52
asaci noted in whiteboard that we lok into splitting specs up13:52
dyfetok13:52
asacbut targetted the generic choices one for alpha-213:52
asacogra: mobile-lucid-arm-rootstock-gui ...13:53
ogratarget for FF13:53
ograsame for the multiarch one13:53
asacthats for alpha-3 (just so we dont squeeze everything i for alpha-2)13:53
asacagree13:53
asacunfortunately we have no FF milestone ... so alpha-3 is the best we can have there13:53
ograits not on the CD and will be developed in archive13:53
asacright13:53
ograwell, make it A313:53
asacdone13:54
JamieBennettasac: 2D launcher is waiting on MIR's being promoted and me packaging up netbook-launcher-efl and uploading to REVU (do that today). After that we need add it to the ARM seed and figure out how we are going to determine if 3D or 2D is needed.13:54
ograthanks :)13:54
asacmobile-lucid-arm-softboot-loader -> i wondered whether this is really Medium priority13:54
asacfor me it feels unlikely that its going to get fixed in lucid timeframe13:54
ograit depends on the kernels13:54
asacso while we should work hard to make it happen after lucid+113:54
asacwe probably wont get to do it this cycle13:55
ograit will be implemented quickly once we have working kexec support13:55
ograwe have several proof of concept implementations ... they are all blocked on kexec13:55
asacogra: right. i think we need at least work items for kexec then.13:55
asaccurrent spec just says "blocked"13:55
asacnot what can or will be done to unblock that13:56
asac[ACTION]: NCommander to add work items on how to unblock softbootloader to spec13:56
MootBotACTION received: : NCommander to add work items on how to unblock softbootloader to spec13:56
ograwe cant do much but wait for kernel team13:56
asacogra: well. we can at least file bugs, bug kernel team, escalate etc.13:56
ograor hope for upstreams (vendors) to have it fixed in their kernels13:56
asaci am not sure if that has happened13:57
ograi think there are bugs since jaunty13:57
ericmogra, just file a bug so we can follow13:57
asacok targetting for alpha-3 so it comes back to our plate13:57
ograright13:57
ograin any case it needs vendor support anyway ...13:57
asacmobile-lucid-lpia-future -> isnt that informational?13:57
ograand that sounds rather like lucid+113:57
asacogra: thats what i thought. for me it feels really unlikely13:58
asacthat we will get that implemented for lucid13:58
ograwell, it would be good to have our side ready asap13:58
asacright. thats why we have an action now to ensure that we work on unblocking it at least13:59
asacok14:57 < asac> mobile-lucid-lpia-future -> isnt that informational?13:59
ogravendor support here means the vendors need to ship the HW with the softbootloader bits13:59
asacStevenK: ^^13:59
ograand obviously the HW we'll work with in lucid will be already shipping13:59
asacok marked lpia spec as informational for now13:59
asacmobile-lucid-lxde-goals -> alpha-3 ... dyfet?14:00
StevenKasac: Hm. Yes, you're right14:00
ograisnt it implemented too ?14:00
dyfetIt is really an informational spec14:00
dyfetThere are 3 separate community maintained specs14:00
asacStevenK: ok. done now. feel free to add more content about what was decided when you have time ;)14:00
asacdyfet: ok.14:00
asacok i think we have to hurry abit ;)14:01
StevenKasac: Yeah, I think that one can wait14:01
asacspecs done for this meeting14:01
asac[TOPIC] ARM Image Status14:01
MootBotNew Topic:  ARM Image Status14:01
asacogra: lucid images broken atm?14:02
StevenKasac: They are14:03
asacany update?14:03
StevenKasac: imx51 fails due to SIGILL, and dove due to what looks to be brokenness14:03
ogra_hmpf ...14:04
ogra_right14:04
ogra_bad thing is is that the seeds are broken too14:04
ogra_so debugging is currently impossible14:04
GrueMasterWell, that certainly explains why dove is broken.  :P14:04
asachow are they broken?14:04
ogra_and i cant reporduce it locally at all14:04
ogra_asac, MIRs missing ... desktop team is working on it14:04
ogra_but it will take its time, which delays us14:05
asachmm14:05
asacis there any way for us to workaround broken seeds to get initial images?14:05
ogra_no14:05
ogra_the seed will be fixed today by the looks of it14:05
ogra_i know pitti and cjwatson discussed promotion of the missing stuff already14:06
ogra_as soon as thats ok we can go on debugging the SIGILL14:06
ogra_i'm in contact with lamont on that since today14:06
dmartogra_: do you know where the SIGILL was?14:06
ogra_the prob here is that the buildd runs UNR jaunty14:07
StevenKmksquashfs14:07
ogra_what StevenK says14:07
ogra_though it might be an inconsistency between kernel and userspace14:07
dmartOK14:07
asacok safe to assume that desktop team will fix the seeds or do we need an action to ensure things get fixed etc?14:07
ogra_as i said, jaunty pegatron UNR kernel14:07
ogra_no, we dont need any action for that14:07
asacok.14:08
asacanything else on arm image status?14:08
asac[TOPIC] ARM Kernel status14:08
MootBotNew Topic:  ARM Kernel status14:08
ogra_not yet14:08
asaccooloney: ericm: your turn :)14:08
ogra_A1 will still be redboot based for imx51 obviously :)14:08
cooloneyasac: thanks, for lucid imx51 kernel14:09
cooloneyi am waiting for the fsl drop14:09
ericmasac, same here for dove14:09
asacok. any timeline for that?14:09
cooloneyas soon as i get it, i will setup a seperate tree for that14:09
cooloneyi think i will get fsl drop on Dec 4th14:09
asacericm: when will mrvl drop the kernel?14:10
ericmasac, not yet known14:11
asacok. but we can continue with what had for karmic, right?14:11
ericmasac, right14:11
asacwhat is the story about not getting thumb kernel ?14:11
davidmWe need to ask Marvell on the next call when we can expect a drop14:11
ericmdavidm, better if I can be invited14:12
ericmasac, thumb2 needs .3214:12
ericmasac, which means we need to backport to .31 as vendor provides only .3214:12
ericm.31 sorry14:12
cooloneydavidm: could you please forward the meeting minutes of the meeting with fsl14:12
asacericm: are you on marvell call?14:13
ericmasac, not yet14:13
cooloneydavidm: sorry i can't join the meeting, since it's 3am-4am here14:13
ogra_ericm, as i understood MVL will be on .3214:13
ogra_ericm, only FSL will stay on .3114:13
dmartThumb-2 kernel is nice to have, but if we don't get it for imx51 it's not the end of the world.14:13
davidmcooloney, understood14:13
cooloneyogra_: yeah, mvl will be .3214:13
asac[ACTION] davidm and asac to clarify marvell kernel drop date14:13
MootBotACTION received:  davidm and asac to clarify marvell kernel drop date14:13
cooloneydavidm: thanks a lot, so for the fsl patch drop, will they send out to me directly or you will forward them to me?14:14
ericmogra_, cooloney, ok so will wait for their next drop14:14
asacericm: ok. thanks for explaining thumb214:14
ericmasac, well - maybe I can check thumb2 on dove if mvl is delivering .3214:15
cooloneyasac: yeah, so mvl kernel will be thumb2, fsl kernel will be .31 not for thumb2 until fsl upgrades kernel to .3214:15
asacright. thanks for summary14:15
asacanything else on kernel status (we are overtime)14:15
ericmnothing from my side14:15
ogra_SATA patch  ?14:16
cooloneyme either14:16
ogra_on imx5114:16
asacgiven that we are well overtime (due to extensive spec review) ... i would suggest to skip the sponsoring review this week14:16
asacany objection?14:16
ogra_nope14:16
asac[TOPIC] Any Other Business14:16
MootBotNew Topic:  Any Other Business14:16
cooloneyogra_:  for that patch, i just posted to kernel mail list for sru14:16
ogra_there was some discussion about the SATA fix for imx5114:16
davidmcooloney, I'll give them your contact info.14:16
ogra_right, i care more about lucid than karmic atm14:17
GrueMastermobile-lucid-arm-lib-tests may need to be revisited.  Will know more next meeting.14:17
asacGrueMaster: revisited in what way?14:17
ogra_we should have the SATA patch in lucid asap so it gets testing14:17
cooloneyogra_: but we think the change will effect other usb storage device connected to ehci port14:17
GrueMasterI'll explain off line.14:17
asacok14:17
ogra_davidm, there is a spec action item for you on one of my specs btw :)14:17
cooloneydavidm: thanks14:17
* GrueMaster is also interested in sata fix for imx51.14:17
ogra_[davidm] ship SSD media for tesing to team members (2 days): TODO14:18
ogra_https://blueprints.edge.launchpad.net/ubuntu/+spec/mobile-lucid-arm-per-soc-powermanagement14:18
GrueMasterIt should be an SRU to karmic as well.14:18
asacpowermanagement that is14:18
davidmogra_, will take more then 2 days14:18
ogra_cooloney, right, but as soon as you have a proper fix it should get added to lucid first14:18
ericmdavidm, possible for me to join the marvell call?14:18
cooloneyogra_: GrueMaster, yeah i posted the sata fix patch as karmic SRU already14:18
ogra_davidm, minus shipment :)14:18
davidmericm, sure14:19
ogra_cooloney, it should enter lucid first14:19
ogra_and get testing there14:19
cooloneyogra_: ok, got you14:19
asac[ACTION] davidm to invite ericm to marvell call14:19
MootBotACTION received:  davidm to invite ericm to marvell call14:19
davidmwill take more then two days to order have to figure out what SSD and get a PO cut14:19
ogra_if its good in lucid make it an SRU14:19
asac;)14:19
cooloneyogra_: ok, no problem14:20
davidmericm, you have been invited14:20
ogra_given that we want to focus on SDD that SATA patch is essential for some of the spec work14:20
ogra_*SSD14:20
asacdavidm: how much time should we book for that? a week?14:20
ericmdavidm, thanks14:20
cooloneyogra_: as soon as i got the drop and setup the kernel tree14:20
davidmasac, at least14:20
davidmlikely two14:20
asacok thanks ... updating whiteboard14:20
asacok since we are quite over time ... lets do other stuff offline14:21
ogra_++14:21
asacok thanks all!14:21
asac#endmeeting14:22
MootBotMeeting finished at 08:21.14:22
ogra_thanks for running the meeting :)14:22
asachehe14:22
asacnow i need to understand how to get anything out of mootbot ;)14:22
asacMootBot: help14:22
ogra_you should have a PM14:22
asacoh ... indeed :-P14:22
ogra_:)14:22
davidmasac, the minutes will be posted you should have a window that tells you where14:23
asacyeah. i got a link ... but todays minutes are not there yet14:23
asacprobably takes a bit14:23
asacthanks14:23
* ericm has to get some sleep as it's late here14:23
=== ericm is now known as ericm-Zzz
davidmasac, yes takes some time, have a look to see if last weeks meeting mintues are up yet14:24
asacok i think there it is14:25
=== ogra__ is now known as ogra
cjwatsonmdz,kees: do you remember who's chairing this week?15:00
mdzcjwatson: I missed the previous meeting, so I don't know15:02
cjwatsonhttps://lists.ubuntu.com/archives/ubuntu-devel-announce/2009-November/000642.html says Kees15:03
ScottKI'd like to ask that https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy be early in the meeting as I have another committment I need to get to.15:03
cjwatsonthe agenda does not seem to have been updated15:03
ScottKNo, that's different than the one for last meeting.15:03
cjwatsonI made a minor edit just now15:04
ScottKI think it's just that there are a lot of carryover topics15:04
cjwatsonand there were some additions - but lots of those carryovers were dealt with15:04
ScottKOh15:04
mdzI updated the agenda a few days ago15:04
mdzto add the maintainer script item15:05
mdzdo we have a quorum? Keybuk doesn't seem to be online, pitti is idle15:05
cjwatsonI've reorganised it slightly to remove dead items and move kubuntu to the top15:05
cjwatsonkees and sabdfl both idle apparently - no quorum if it's just you and me15:06
tseliotare you going to process recommendations from the Motu council in this meeting?15:07
sabdflhello all15:07
mdztseliot: if it's for upload rights, that's done by the DMB now15:07
cjwatsontseliot: that will be for the DMB next week, I believe15:07
cjwatsonsabdfl: hi, just you, me, and mdz so far15:08
tseliotah, ok, thanks15:08
mdzcjwatson: that's quorum15:09
mdzmight as well start15:09
mdz#startmeeting15:09
MootBotMeeting started at 09:09. The chair is mdz.15:09
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:09
mdz[link] https://wiki.ubuntu.com/TechnicalBoardAgenda?action=show15:10
MootBotLINK received:  https://wiki.ubuntu.com/TechnicalBoardAgenda?action=show15:10
mdzcjwatson: there were a bunch of actions re: archive reorg15:10
mdz   * [ACTION]: Martin to talk to Jonathan about making DMB an admin of kubuntu-dev (done now), and to announce new members to devel-permissions@15:10
mdzand kubuntu team list15:10
mdz   * [ACTION] Martin to talk to Mario about adding DMB as admin of ~mythbuntu-dev and add wiki page about new member procedure15:10
mdz   * [ACTION] Colin to document edit_acl invocation for setting team upload delegation15:10
mdz   * [ACTION] Colin to implement delegations for these three teams after above fixes15:10
mdzcjwatson: any updates on those?15:11
cjwatsonthe team change to kubuntu-dev was done, but not mythbuntu-dev15:11
cjwatsonwe're still blocked on an RT ticket to add devel-permissions - I'll go nag IS about that15:11
mdzthe third was ubuntu-desktop, which is  done, right?15:11
cjwatsondelegations are implemented but not yet the documentation15:11
mdzwhat's the RT#?15:12
* bdale is here, fwiw15:12
cjwatsonmdz: 3613915:13
mdzbdale: hey15:13
cjwatson(I've poked #is)15:13
mdzcjwatson: thanks15:13
mdz  * [ACTION] Scott to redraft Units policy to address Scott's and Matt's concerns and clean up language15:13
mdzthe draft is15:13
mdz[link] https://wiki.ubuntu.com/UnitsPolicy15:13
cjwatsonI haven't seen that redraft15:13
MootBotLINK received:  https://wiki.ubuntu.com/UnitsPolicy15:13
mdzand hasn't been touched since 2009-09-2715:13
mdzso I guess that action is still outstanding15:13
mdz  * [ACTION] Colin to clarify trademark/license distinction on licensing policy15:14
cjwatsonstill outstanding, sorry15:14
mdz[ACTION] Martin to announce DMB meeting next week15:14
MootBotACTION received:  Martin to announce DMB meeting next week15:14
mdzhe did that15:14
cjwatsondone and furthermore moot now :)15:14
mdzok, on to the main agenda15:14
mdz[topic] Archive reorganisation (ColinWatson)15:14
MootBotNew Topic:  Archive reorganisation (ColinWatson)15:14
cjwatsonthere's one more team that would like to get on the path to delegation, but regrettably I have forgotten which15:15
cjwatsonI think it was Xubuntu15:15
cjwatsonwe gave Cody the necessary information to get started15:15
cjwatsonother than that I have no updates15:15
sabdflis there a canonical list of the teams / packagesets anywhere?15:15
mdzis there a wiki page on how to get set up?15:15
cjwatsonsabdfl: in LP, yes15:15
cjwatsonlaunchpad.packagesets15:16
cjwatsonmdz: examples but nothing guidebook-like; I can take an action (argh ...) to write something up15:16
sabdflcvd!15:16
sabdfloww15:16
mdz...15:17
cjwatsonqwp!15:17
sabdflthat's what she said15:17
pittio/15:17
pittisorry15:17
mdzcjwatson: I don't think it's essential, but it would be good to be building up a doc as we go so that other teams can follow15:17
mdzanyway, moving on15:17
cjwatsonpitti: hi. did you talk to Mario about adding DMB as admin of ~mythbuntu-dev and adding a wiki page?15:17
mdz(or not, I'll wait)15:18
cjwatsonmdz: might as well ACTION me even if it doesn't happen right noow15:18
cjwatson-o15:18
pittiI sent a mail, but didn't see a response yet15:18
sabdflcan we not just do that ourselves?15:18
cjwatsonsabdfl: you might be able to, we can't :)15:18
sabdflor, by policy, should we wait for him to do it?15:18
pittiI'll poke him again then15:18
sabdfli can, just not sure it's protocol to use lp.Admin15:18
mdz[action] cjwatson to create a wiki reference for development teams to participate in the reorg15:18
MootBotACTION received:  cjwatson to create a wiki reference for development teams to participate in the reorg15:18
cjwatsonLP admins generally seem to prefer not to15:18
cjwatson(from my observation anyway; it does seem to be skating along the edge)15:19
sabdflin this case, i've technically got project authority too15:19
mdzI would prefer that a team admin do it15:19
sabdflagreed15:19
pittialso, creating a policy wiki page is the main bit here, which the mythbuntu devs should decide themselves?15:19
cjwatsonwe need superm1 to document the process for mythbuntu anyway15:19
mdzsabdfl: for mythbuntu?15:19
sabdflfor *buntu15:19
mdz...15:20
mdzcjwatson: anything else on archive reorg, or can we move on? lots to cover15:20
cjwatsonmove on15:20
mdz[topic] Units Policy15:20
MootBotNew Topic:  Units Policy15:20
mdzwe covered this above; it is waiting for Scott to redraft15:20
mdzthough the agenda says "finish voting"?15:20
cjwatsoncan we do the Kubuntu stuff as ScottK requested? he has a time constraint15:21
cjwatsonthe agenda no longer says that, I edited it15:21
mdzok15:21
cjwatsonreload and you'll get updated ordering too :)15:21
mdz[topic] https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy15:21
MootBotNew Topic:  https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy15:21
mdz[link] https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy15:21
MootBotLINK received:  https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy15:21
cjwatsonI've read this just now, and in general it's a request to bring our KDE practices more into line with how we handle GNOME post-release15:22
mdzScottK: which packages are covered by this proposal?15:22
pitti(note: we don't regularly update the entire gnome stack to new versions, just selected packages)15:22
ScottKmdz: It's the KDE core packages.15:22
ScottKThe ones that come in a KDE 4.x.y release.15:23
cjwatsonScottK: we probably ought to have a standard practice for what to do when (IME "when", not "if") regressions are detected after packages are moved to -updates15:23
mdzScottK: it would be handy to have a list, since my next question is whether or not there are reverse deps outside of KDE itself15:23
cjwatsonthere certainly will be reverse-deps15:23
cjwatsonany KDE application will depend on the core bits15:23
ScottKmdz: The only one I know of that affects Ubuntu is kdebindings15:23
ScottKIt has ubuquity as a reverse depends15:24
cjwatsonmdz: do you mean "outside KDE" or "outside Kubuntu"?15:24
mdzI agree with cjwatson that a contingency plan would be wise15:24
ScottK(That's the only KDE core package that is in both the Ubuntu Desktop and Kubuntu package sets)15:24
bdalecjwatson: I assume he means outside of the set of packages they're already proposing to update15:24
mdzcjwatson: I meant outside of the set of packages in question15:24
mdzwhich, since it's only the core bits and not applications, there are definitely plenty15:25
czajkowski.c15:25
mdzbdale: bingo15:25
cjwatsonso in that case the set of packages is certainly large, just as updating e.g. gnome-vfs has a bunch of reverse-deps15:25
ScottKThis is true.15:25
ScottKThe broadest impact is from kde4libs.15:25
ScottKUpstream promises binary compatibility for that.15:26
cjwatsonI suppose the real question though is whether KDE nowadays meets the same kind of standards that we apply to GNOME post-release updates15:26
sabdflthat's the piece that's missing for me15:26
sabdflsome statement from KDE upstream about the approach they are taking to point releases15:26
mdzScottK: in the rationale section, when considering the arguments against doing updates, the most critical argument in my opinion is that there is an unknown risk of regression15:27
pittiwe actually only had an exception for LTSes for gnome point releases15:27
mdzI would like to see that addressed in the proposal15:27
sabdflif we can get a commitment from KDE that their stable branch maintenance policy is broadly in line with our SRU policy, then point releases -> updates makes sense15:27
ScottKmdz: OK.15:27
pittiand we did have regressions in KDE point releases in the past, too15:27
bdalemdz: they talk a lot about testing for regressions, but it's not clear how broad that testing could/would be, right?15:27
mdzScottK: anything you're doing to mitigate that risk is relevant information for considering this change15:27
pitti(which is why I'm always a bit scared of such blanket policies)15:27
ScottKYes, and we have still seen a few.15:28
ScottKThis is why we proposed the ppa -> proposed -> updates path to give time for testing.15:28
sabdflthat's reasonable, yes15:28
sabdflit wouls just be helpful if there was a real policy upstream about commits to the stable branches15:28
mdzbdale: yes, I think this is to some extent addressed elsewhere in the doc, but it seems like an omission in the rationale15:28
cjwatsondoes somebody have a link to GNOME's documented stable update handling?15:28
mdzif the rationale is that there is no reason NOT to do it, then it needs to cover more ground15:28
ScottKsabdfl: I can ask them for a clear statement of policy.15:28
sabdflwe should look to make a mutual commitment with upstream: if they adopt a firm SRU-compatible policy for point releases, we'll SRU them15:29
mdzthe meat of the rationale seems to be that users expect it15:29
sabdflthat way it's worth their while to do the work, because they know it will have maximum impact15:29
mdzwhich may be because we've done it in the past ;-)15:29
sabdflthe only users who would clamour for it are developer users, who *know* about the point release15:29
sabdflendusers won't know about them15:30
ScottKIn addition to testing, we're also monitoring KDE svn so that if others find regressions and fix them we are aware of it.15:30
bdaleScottK: sure, that's expected15:30
ScottKIt seems clear I have some homework to do.15:30
cjwatsonsabdfl: I have an ongoing campaign about this not being a binary state :) in between we have e.g. users who try multiple distributions and notice discrepancies15:30
sabdfli'm sure KDE will be amenable to a clear policy, since they have regular releases which reduce the temptation to backport "cool new stuff" to a stable release15:30
bdalesabdfl: don't sell endusers short, it depends a lot on how upstream communicates point releases as to how many people know about them and want them... as a non-KDE-user, I don't know in this case15:30
sabdflcjwatson: noted15:30
sabdflmy point is that we should assume that most users want *stability*15:31
ScottKsabdfl: There is a 4.3.4 release today and we've already gotten ping'ed in #kubuntu-devel asking where to find the update from someone who AFAIK is not involved in development.15:31
bdalesabdfl: yes15:31
sabdflif a point release can't be certain to be increasing that, then the only people who would clamour for it are people for whom that particular upstream is very interesting15:31
sabdflif we get a mutual understanding in place with upstream w.r.t. stable branch maintenance, it's win-win15:32
sabdflso ScottK, let's see if that's achievable15:32
ScottKsabdfl: I'm reasonably certain that KDE's policy for updates is reasonably well aligned to what you're asking for.  I don't know that it's clearly documented.15:32
sabdflok15:32
ScottKAre there more questions or additional homework items for me?15:33
mdzok, so what's the next step?15:33
mdzwhere should we pick this up in 2 weeks?15:33
ScottKI think I've got a list of things for Kubuntu to work on among ourselves and with upstream.15:33
mdzScottK: [action] ScottK to revise proposal based on discussion here ?15:34
ScottKHow about if we leave it open since I don't know how long it'll take with upstream.15:34
ScottKYes.  That's good.15:34
mdz[action] ScottK to revise proposal based on discussion here15:34
MootBotACTION received:  ScottK to revise proposal based on discussion here15:34
mdzScottK: thank you15:34
mdzmove on?15:34
ScottKThank you for your time.15:34
mdz[topic] When is it a good idea to fail out of a maintainer script? (mdz)15:35
MootBotNew Topic:  When is it a good idea to fail out of a maintainer script? (mdz)15:35
mdzthis came up in discussion at UDS and there has been some ongoing chatter about it15:35
mdzI thought it would be useful to put it to the TB and see what folks think15:35
pittihm, it should ideally only happen in preinst, and on very exceptional circumstances, such as pending data loss15:35
mdzthe particular case which started the discussion was where maintainer scripts can fail due to transient error conditions, or other problems beyond the scope of the package15:36
mdze.g. a daemon package's postinst failing because the daemon couldn't start15:36
mdzperhaps the admin made a typo in the configuration file, or something else was listening on the port, etc.15:36
mdzsome packages fail in this case, others don't15:36
cjwatsonthe usual case that gives me difficulty is how to encapsulate things where other packages that depend upon that package will themselves fail if the depended-upon package is broken15:36
mdzYokoZar brought up a case in procps, where it was failing because there was some garbage in /etc/sysctl.d15:37
cjwatsonpersonally I would avoid depending on something and assuming that its daemon is running, but that seems a possibility in the more complicated corners of the system15:37
cjwatsonI would make a general recommendation for dependencies to be as weak as possible, in those terms, but how much my recommendation is worth I'm not sure :)15:38
mdzin cases like that one, I don't see the value in failing the maintainer script and forcing the user to clean it up15:38
cjwatsonI suppose the question is what "successfully configured" means15:38
cjwatsonand what other packages are expecting from it15:38
mdzsearching google for "policy manual" returns the Debian policy manual as the second hit for me15:38
bdale;-)15:39
cjwatsonif, say, perl is unable to load its core modules, then everything depending on it is going to be pretty unhappy anyway15:39
cjwatsonthis case is deliberately exaggerated but we clearly need a case where failing *is* reasonable in order to draw the bounds15:39
mdzyes15:39
mdzbut if, say, scrollkeeper fails to register the package's documentation, not so much15:39
bdaleone assumes this is primarily an issue on upgrades?15:40
mdzsome folks have made an argument that it's better to have these problems made evident so that they are diagnosed and fixed15:40
pittianother valid (IMHO) example is a new DB server which detects that you have a previous-version database which can't be automigrated15:40
pittithen the preinst should fail with a message15:40
mdzbut I would argue that failing the upgrade or installation is not the best way to achieve that15:40
cjwatsonit does kind of bother me that we are designing a system that assumes success and hides failures15:40
mdzpitti: I agree, there are definitely cases where it is valid in preinst15:40
mdzthat is much easier to recover from15:40
pittiarguably we need to make our upgrading tools more robust for these cases as well, but in general we have too many failed packages15:40
pittiupgrading tools> if one package in your 5.000 fails to upgrade, you basically loose; no way to bring up update-manager any more to clean up/finish the upgrade15:41
pittiand in a lot of cases you even fail to boot because the initramfs wasn't rebuilt, etc.15:41
mdzbrowsing https://edge.launchpad.net/ubuntu/+bugs?field.tag=apport-package is very educational15:41
ibuclawcjwatson, we wouldn't be the first or last people to do so though ... Windows 7 hides segmentation faults now apparently ;)15:41
cjwatsonI don't have a clear idea on how to set policy on this; I definitely think there are many cases where adding || true is appropriate, but I don't see a way to mandate anything15:42
mdzit should be possible to formulate a rule of thumb, I would tihnk15:42
mdzthink15:42
bdalepitti: a package whose installation failing causes a system to be unbootable sounds like a grave problem, to me.  does that really happen?15:43
mdze.g. failing postinst is only advisable if packages depending on this one will also fail to be configured15:43
cjwatsonI'm looking for a definition of what it means to be "configured" in the dpkg sense, and have been unable to find one15:43
cjwatsonI mean, obviously I know the technical steps involved15:43
mdzcjwatson: me either15:43
pittibdale: yes, because it usually leaves a large trail of unconfigured packages behind15:43
cjwatsonbut I want a definition of desired states15:43
pittibdale: I heared that more than once from acquaintances, that cost me a lot of phone support..15:44
mvo_I think its good that this is discussed, I think failure of (re)starting a daemon should not be a postinst fail (at least in release upgrades)15:44
mdzmvo_: oh hi, thanks for speaking up15:44
cjwatsonconfigured ought to be sufficient for depending-upon packages to work. It ought to be such that you don't need to move lots of files around to make the package work. It ought to be such that the system is in a checkpointed state where it basically still works. Um ...15:44
mdzmvo_: you probably get more than your share of these bug reports ;-)15:45
ibuclawcjwatson, is this the page you are currently at? http://www.debian.org/doc/debian-policy/ch-maintainerscripts.html15:45
mvo_it might be worthwhile to differentiate between normal and release upgrades, the later tend to more troublesome if a script bails out15:45
ibuclawor were at15:45
mvo_mdz: I do15:45
mdzbdale: if the failure causes dpkg/apt to not attempt to configure the dependent packages, even if it would have worked, that's a net loss15:45
mvo_mdz: more than I want :)15:45
bdalemdz: indeed15:45
cjwatsonin the specific case of a daemon I think I generally agree that it is not worth failing postinsts; but I'm hesitant to lay down the law on that because there are a lot of weird cases out there15:45
mdzI think the answer could very well be different in development vs. post-release15:46
mdze.g. --force-overwrite15:46
* mvo_ nods15:46
cjwatsonibuclaw: yes, but it does not answer the question I posed; it specifies the technical steps involved in configuring a package, which I know, but it does not specify the, er, philosophical state of being configured15:46
bdalewe've certainly always tolerated levels of breakage in Debian unstable that would not be considered acceptable in stable15:46
mdzto try to wrap up this agenda item, I wanted to get input on whether this is something the TB should consider in depth and make a recommendation about15:47
cjwatsondoes anyone here have expertise in weird daemons that really do need to be started in order to configure dependent packages?15:47
bdalemdz: my take is that it's a really intersting question, but something that shouldn't be handled hastily15:47
cjwatsonmaybe we can just consider those bugs since they generally won't work inside chroots and the like15:47
bdalemdz: and this is the first TB agenda item for which I think some explicit coordination with the Debian TC would be interesting to pursue15:48
mdzbdale: so if we assume that any TB recommendation would not be made hastily, is it something we should devote some attention to? ;-)15:48
mdzbdale: aha!15:48
pitticjwatson: policykit was such a daemon15:49
ibuclawcjwatson, don't you dpkg-divert --rename initctl and ln -s true initctl in chroot's to disable services from restarting anyway?15:49
pitticjwatson: without it running you couldn't configure hal, since that requires setting up a PK privilege which hal needs15:49
cjwatsonibuclaw: typically, yes, which is what I'm referring to15:49
pittiPK isn't started from postinst, but it's the same principle15:49
cjwatsonin "maybe we can just consider those bugs"15:49
=== bjf-afk is now known as bjf
cjwatsonpitti: was that considered a bug?15:50
mdzlet's try to wrap this up15:50
mdzshould we take some action or no?15:50
mdzoptions:15:50
mdz- open a dialogue with the Debian TC15:50
mdz- somebody go off and give it a good long think and come up with a proposal15:51
mdz- start a discussion thread on a mailing list15:51
mdz- announce a webinar15:51
bdaleany discussion with the Debian TC will proceed better if it starts with a straw-man proposal15:51
mdz...kidding15:51
bdaleas the TC is not in the habit of initiating policy from whole cloth15:51
mdzok, I'm not hearing any strong views so I'll just leave it alone for the moment, we can revisit at the next meeting if we have time15:52
mdz[topic] Ubuntu Licensing Policy (raised by Ken Wimer)15:52
MootBotNew Topic:  Ubuntu Licensing Policy (raised by Ken Wimer)15:52
mdzthis already has an action for colin on the agenda15:52
mdzanything to discuss?15:52
cjwatsonnothing else as far as I'm aware; we discussed it last time15:52
mdz[topic] Execute Permission Policy (KeesCook)15:52
MootBotNew Topic:  Execute Permission Policy (KeesCook)15:52
mdzkees is not here, perhaps we should hold off until he's back?15:52
mdzmeanwhile, folks can review the document15:53
mdz[link] https://wiki.ubuntu.com/SecurityTeam/Policies#Execute-Permission%20Bit%20Required15:53
MootBotLINK received:  https://wiki.ubuntu.com/SecurityTeam/Policies#Execute-Permission%20Bit%20Required15:53
cjwatsonwe discussed much of this last time, but without kees, I think we should postpone15:53
* mdz pokes MootBot15:53
mdzok15:53
cjwatsonthere were some thorny issues15:53
mdz[topic] Check up on community bugs (standing item)15:53
MootBotNew Topic:  Check up on community bugs (standing item)15:53
mdzwe have some bugs!15:53
mdz[topic] bug 485569: TB term length is unclear15:54
MootBotNew Topic:  bug 485569: TB term length is unclear15:54
ubottuLaunchpad bug 485569 in ubuntu-community "TB term length is unclear" [Undecided,New] https://launchpad.net/bugs/48556915:54
mdzLP and www.ubuntu.com disagree about the length of a term on the TB15:54
mdzer, LP and wiki.ubuntu.com15:54
mdzwww.ubuntu.com has nothing to say about it, but probably should15:54
mdzis it one year or two?15:54
cjwatsonI must say I always thought it was two15:54
sabdfli think we tried to stagger it at one stage15:55
mdzI thought so as well, I vaguely recall the rationale being that made it possible to have annual elections with staggered terms15:55
sabdflso some were appointed for one, some for two15:55
sabdflbut the meme elsewhere is to go with two and reappoint the whole group at a time15:55
sabdflwhich is pretty much where we are now15:55
sabdflmodulo cjwatson, iirc15:55
mdzsabdfl: so what should we do to clarify it?15:56
bdaleI note in passing that I'm not listed at https://edge.launchpad.net/~techboard/+members15:56
mdzbdale: IIRC you agreed only to sit in and see what was involved, to help us define a role for a debian representative if one made sense15:57
sabdflhmm, tb at present has an initial period (730 days) and renewal period (365 days)15:57
bdalemdz: true15:57
sabdfli can change the renewal period to 730 days, if that helps15:57
sabdfland can add bdale at the same time if that would best reflect his representing debian here15:57
mdzsabdfl: I think that would be premature15:58
mdzat some point (and we should have set a timeline for this originally, my oversight) we should put a discussion topic on the agenda about this15:58
sabdflit probably grants super cow powers all over the place15:58
mdzbdale agreed to participate in the meetings for a while and see what we do15:58
bdalemdz/sabdfl: mdz makes a good point, we should probably have a discussion offline about how this should work now that I've lurked for a while15:58
mdzso that we could talk about what a debian representative role would entail15:58
sabdflok15:58
mdzbut to come back to the term issue...I'm assuming that this is a sabdfl decision since there's noplace else to appeal to15:59
bdalethe OSI folks, for example, have an explicit 'observer' role that is non-voting but fully participatory otherwise, could be worth considering something intermediate like that15:59
sabdflbut the renewal period to 730 would at least remove some confusion (it's not really relevant, we don't allow self-renewal anyhow)15:59
mdzso...15:59
sabdfli prefer giving folks a real say if they're invited to the party15:59
sabdfladvisory boards are less interesting than real boards :-)16:00
mdzsabdfl: [action] sabdfl to update LP/wiki/www to reflect the actual term length for TB ?16:00
sabdfldone16:00
sabdflwell, LP16:00
mdzwhatever you decide is fine with me16:00
mdzeither 1 or 2 or some combination16:00
sabdflwhere's the relevant wiki page? i also don't know how to edit the website (blush)16:00
mdzsabdfl: it's in the bug16:00
cjwatsonI'll shove it in the website now16:00
mdzI've assigned the bug for tracking16:01
cjwatsonjust say "two years"?16:01
mdzwe're out of time, but there are two more16:01
pittiso people could be elected in phases (as they already are), to avoid replacing the entire board at a time16:01
sabdflcjwatson: +116:01
pittithat should work well with a consistent 2 years period, too16:01
mdzbug 485971 is waiting for an RT ticket to be processed16:02
ubottuLaunchpad bug 485971 in ubuntu-community "Technical Board mailing list archive is private" [Undecided,New] https://launchpad.net/bugs/48597116:02
mdzcjwatson: could you nudge it in the next IS meeting?16:02
cjwatsonok16:02
mdz[action] cjwatson to nudge RT 3542816:02
MootBotACTION received:  cjwatson to nudge RT 3542816:02
mdzbug 48555916:03
ubottuLaunchpad bug 485559 in ubuntu-community "Mark Shuttleworth has no expiration date set in the tech-board LP team" [Low,Confirmed] https://launchpad.net/bugs/48555916:03
cjwatsonI have given it a non-zero priority so that it stops vanishing16:03
mdzsabdfl was re-elected to TB but didn't have an expiry set; this fits into the term discussion as well16:03
mdzsabdfl: should you expire like everybody else or are you special in that regard?16:03
* bdale chuckles16:04
sabdfli certainly hope to be16:04
sabdflbut... mortality beckons16:04
mdzhar16:04
cjwatsonexpires: sometime after upload16:04
sabdfli'm happy to expire from this team like everyone else if you request that16:04
sabdfli've also clarified that a vote of Ubuntu developers means a vote of anyone who can upload to the archive, main or universe, or subsets, or even individual packages16:05
cjwatsonyes, that is how we have implemented things to date16:06
cjwatsonwhich reminds me though, we need to add delegated teams to ubuntu-dev; I'll do that now16:06
mdzsabdfl: it's not up to me, this was just flagged in one of our governance reviews as an inconsistency16:06
sabdflhmm... ubuntu-dev might be used for main/universe upload16:06
mdzthe foundation documents don't specify16:07
cjwatsonit is not16:07
sabdflok16:07
cjwatsonwe verified that when we started doing per-package uploaders, and adding them to ubuntu-dev16:07
cjwatson(universe/multiverse upload => motu; motu is a member of ubuntu-dev)16:07
sabdflmdz: personally, i'd prefer to be on the TB ex officio as long as i'm bdfl16:07
mdzsabdfl: whatever you decide, I think the official www docs should explain it16:08
sabdflif that makes folks uncomfortable, i don't mind dropping off it, but you and others have said it helps16:08
sabdflto build links to other parts of the project16:08
mdzso that we're self-consistent with our governance policies16:08
bdaleI'd write it in as a special case, personally16:08
sabdflok. i don't mind having the same status as the debian representative ;-)16:08
pittinot having the DFL on the technical board sounds kind of strange to me, FWIW16:08
mdzwe're over time, can we wrap up?16:08
mdzwe can pick this up next time16:08
* bdale ^5's sabdfl16:09
mdz[topic] select a chair for the next meeting16:09
MootBotNew Topic:  select a chair for the next meeting16:09
sabdflbackatcha :-)16:09
mdzwho's up?16:09
mdz3...16:09
mdz2...16:09
mdz1...16:09
sabdflwasn't this week due to be kees?16:09
pittikees again?16:09
mdzkees it is16:09
mdz#endmeeting16:09
MootBotMeeting finished at 10:09.16:09
mdzkees: as penalty for skipping your turn chairing, please help me with the TeamReport, as I have back-to-back meetings after this ;-)16:09
pittithanks all, and sorry for being late16:11
keesmdz: ah, sorry, on holiday this week.  I will review the scrollback.16:36
=== yofel_ is now known as yofel
=== fader_ is now known as fader|lunch
=== ogasawara_ is now known as ogasawara
=== sconklin1 is now known as sconklin
bjfRoll Call18:00
* smb is here18:00
* ogasawara waves18:00
* amitk is here18:00
* apw hides behind smb18:00
* pgraner waves 0/18:01
* rtg is here18:01
bjf#startmeeting18:01
MootBotMeeting started at 12:01. The chair is bjf.18:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting18:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting18:01
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid18:01
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid18:01
bjf[TOPIC] Lucid Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs18:01
MootBotNew Topic:  Lucid Release Status: Bugs (Release Meeting Bugs / RC Milestoned Bugs / Release Targeted Bugs18:01
ogasawaraRelease Meeting Bugs (0 bugs) - https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Lucid18:01
ogasawaraAlpha 1 Milestoned Bugs (12 bugs) - https://bugs.edge.launchpad.net/ubuntu/lucid/+bugs?field.milestone%3Alist=2144318:02
ogasawara * 2 linux kernel bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux/+bugs?field.milestone%3Alist=2144318:02
ogasawara * 0 linux-fsl-imx51 bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-fsl-imx51/+bugs?field.milestone%3Alist=2144318:02
ogasawara * 0 linux-ec2 bug - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-ec2/+bugs?field.milestone%3Alist=2144318:02
ogasawara * 0 linux-mvl-dove bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-mvl-dove/+bugs?field.milestone%3Alist=2144318:02
ogasawara* Release Targeted Bugs (54 bugs) https://bugs.edge.launchpad.net/ubuntu/lucid/+bugs18:02
ogasawara * 4 linux kernel bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux18:02
ogasawara * 0 linux-fsl-imx51 bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-fsl-imx5118:02
ogasawara * 0 linux-ec2 bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-ec218:02
ogasawara * 0 linux-mvl-dove bugs - https://bugs.edge.launchpad.net/ubuntu/lucid/+source/linux-mvl-dove18:02
ogasawara..18:02
bjfany comments/questions?18:02
bjf[TOPIC] Lucid Release Status: Milestoned Features18:02
MootBotNew Topic:  Lucid Release Status: Milestoned Features18:02
ogasawaraMilestoned Features - https://edge.launchpad.net/ubuntu/+milestone/ubuntu-10.0418:02
ogasawara..18:03
pgranerapw: do think we can keep up with the Milestoned and Release bugs this cycle?18:03
apwas in get them fixed, or keep track of them18:03
pgranerapw: that is track and fix them at a faster rate then last time?18:03
pgranerapw: both18:03
apwwell we are tracking them better already18:03
pgranerapw: if not fix keep the bugs fresh with status18:04
apwwe will cirtainly be trying to keep them more under control18:04
apwwe may need to pull people in to attack them18:04
rtgogasawara, the milestoned features page does not appear to have any kernel work18:04
pgranerapw: the big complaint last cycle was we had lots of bugs like that but we never touched them18:04
ogasawarartg: nope, not at the moment18:04
pgranerapw: or at least often if we were waiting on upstream18:04
apwpgraner, i ma keeping track of all lucid specific bugs under a new tag18:05
pgranerapw: name?18:05
apwkernel-lucid, so at least we have better visibility of the incoming18:05
pgranerapw: ack18:05
ogasawaraapw: I can give stats on that in this meeting going fwd18:05
* pgraner says OVER18:05
apwogasawara, ack18:06
bjf[TOPIC] Blueprints: kernel-lucid-kernel-decision (apw)18:06
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-decision18:06
MootBotNew Topic:  Blueprints: kernel-lucid-kernel-decision (apw)18:06
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-decision18:06
apwthat is just waitng on publication of the decision18:06
apwthat is expected to occur by the end of the week so we should be able to remove next week18:06
apw..18:06
bjfdoes it need an [ACTION]?18:06
apwi have actions in the release page already18:07
bjf[TOPIC] Blueprints: kernel-lucid-bug-handling (ogasawara)18:07
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-bug-handling18:07
MootBotNew Topic:  Blueprints: kernel-lucid-bug-handling (ogasawara)18:07
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-bug-handling18:07
ogasawaraFinished drafting spec.  Should be ready for Review and then Approval.18:07
ogasawaraas noted above, apw's already started in on some of the work items like tagging by release18:07
ogasawara..18:07
bjf[TOPIC] Blueprints: kernel-lucid-sru-policy-review (smb, ogasawara)18:07
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-sru-policy-review18:07
MootBotNew Topic:  Blueprints: kernel-lucid-sru-policy-review (smb, ogasawara)18:07
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-sru-policy-review18:07
smbdocumentation done. just waits on publication (done in one, no action needed)18:08
smb..18:08
apwwe plan a combined annoucenment update email at the end of the week18:08
bjf[TOPIC] Blueprints: kernel-lucid-review-of-ubuntu-delta (apw)18:08
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-review-of-ubuntu-delta18:08
MootBotNew Topic:  Blueprints: kernel-lucid-review-of-ubuntu-delta (apw)18:08
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-review-of-ubuntu-delta18:08
apwwe have dropped a bunch of old cruft patches.  we are moving on onto the 'review items' now18:08
apwnext is pulling up drivers ... starting with AA18:08
apw..18:08
bjf[TOPIC] Blueprints: kernel-lucid-kernel-config-review (apw)18:09
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-config-review18:09
MootBotNew Topic:  Blueprints: kernel-lucid-kernel-config-review (apw)18:09
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kernel-config-review18:09
apwthat is nearly complete, again announcement is pending18:09
apwthere is a the config checker outstanding there18:09
apw..18:09
bjf[TOPIC] Blueprints: kernel-lucid-kms (sconklin)18:09
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kms18:09
MootBotNew Topic:  Blueprints: kernel-lucid-kms (sconklin)18:09
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-kms18:09
sconklinThe web pages are up to date - discussion is ongoing about how to include nouveau18:10
apwthe review of nouveau is pretty hideous, likely a backports module apprach will be needed18:10
sconklinapw suggested as a backports module, and I think that's brilliant18:10
amitkwill that mean its own drm stack?18:11
sconklinnouveau requires that all of drm-next be brought in18:11
pgraneramitk: yep18:11
* amitk remembers the mess with poulsbo18:11
* apw cries18:11
* pgraner hands apw a crying towel18:11
amitkheaders need to be fixed (if the lbm package is installed)18:11
bjfsconklin, is that all?18:12
sconklinMy comfort level re: nouveau is very low18:12
sconklinyeah18:12
sconklin...18:12
rtgamitk, do we really need to support 3rd party builds?18:12
amitkrtg: dunno. Don't we?18:12
apwseems like a stretch goal to me18:13
rtgfor LBM modules? I don't think so18:13
amitkis this going to be 'supported'?18:13
amitkor an experimental feature18:13
rtgLBM y its nature is only best effort18:13
rtgby*18:13
apwand they will have -nv to fall back on18:14
apwand the binary drivers18:14
amitkI guess its ok then, if that is communicated in advance18:14
bjf[TOPIC] Blueprints: kernel-lucid-suspend-resume (manjo)18:14
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume18:14
MootBotNew Topic:  Blueprints: kernel-lucid-suspend-resume (manjo)18:14
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-suspend-resume18:14
bjfmanjo is out today18:14
bjf..18:14
bjf[TOPIC] Blueprints: kernel-lucid-apparmor-development (jjohansen)18:15
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-apparmor-development18:15
MootBotNew Topic:  Blueprints: kernel-lucid-apparmor-development (jjohansen)18:15
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-apparmor-development18:15
jjohansennext posting should go out thursday18:15
jjohansenec2 and thankgiving ate my cycles last week18:15
apwwe have a plan for pulling in the current version to lucid as soon as its ready to post18:16
jjohansenright18:16
bjf??18:16
apwbjf?18:17
jjohansenjust agreeing with apw18:17
bjfjjohansen, is that all18:17
jjohansenyes18:17
apw..18:17
bjf[TOPIC] Blueprints: kernel-lucid-boot-performance (apw, csurbhi)18:17
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-boot-performance18:17
MootBotNew Topic:  Blueprints: kernel-lucid-boot-performance (apw, csurbhi)18:17
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/kernel-lucid-boot-performance18:17
* apw lets csurbhi talk ...18:17
csurbhidoing tests to see if populate_rootfs can be executed in parallel18:18
csurbhiand if we get any speedup by doing the same18:18
csurbhihad a good result today18:18
rtgcsurbhi, how much time did it save?18:18
csurbhishall do this for lucid kernel by tonight and post a patch and a boot image18:18
csurbhii dont have the exact number for lucid yet18:19
csurbhii did it on a vanilla 2.6.31 kernel to see if any time can be saved18:19
rtga ballpark would suffice :)18:19
csurbhicreating a .deb package for lucid rt now18:19
apwthe times on the test were vastly different, the pictures implied we might get as much as 40% saving for lucid18:19
csurbhii think around 2 sec18:20
rtgwell, thats significant18:20
csurbhibut definitely less than that18:20
csurbhiaround 1+ sec18:20
csurbhiactually18:20
apwthe test kerenl were booting in approx 2x the time of lucid18:20
apwjjohansen, where are we with the apparmour out of18:21
bjfcsurbhi, is that all?18:21
apwinitramfs stuff?  as i assume that'll save us a bit of unpack time18:21
jjohansenI started looking at upstartifying the init script but not very far18:21
apwok ...18:22
apw..18:22
csurbhiyes18:22
bjf[TOPIC] Other Release Tasks: Lucid Audio Support (bjf)18:22
MootBotNew Topic:  Other Release Tasks: Lucid Audio Support (bjf)18:22
bjfI've started working today on my Audio crack of the day build work. I'm starting with the work rtg did for karmic-lbm18:22
bjf..18:22
bjf[TOPIC] Other Release Tasks: Lucid Better Power Mgt (amitk)18:22
MootBotNew Topic:  Other Release Tasks: Lucid Better Power Mgt (amitk)18:22
amitkBeen doing some baseline idle power measurements on my laptop18:23
amitkwaiting on reference HW from pgraner18:23
apwwhat we going to use as reference here?18:23
amitknext steps is to define the set of usecases we care about for measurements18:23
amitkDell Mini 10V was suggested - with and w/o SSD18:23
apwworks for me18:24
amitkother tasks have been defined at18:24
amitkhttps://wiki.ubuntu.com/KernelTeam/ReleaseStatus/LucidTasks18:24
apwhave you seen keybuk's automated tests for boot speed?18:24
apwi wonder if we could produce power numbers in a similar way / get him to in the same builds18:24
amitki chatted with him at UDS about it. I will ping him for the scripts18:24
apwmight be nice to double up on his h/w there, get automatic readings from him18:25
amitkyes, makes sense18:25
amitkbjf: action me18:25
bjf[ACTION] amitk to get with keybuk on automated tests18:25
MootBotACTION received:  amitk to get with keybuk on automated tests18:25
amitkthat is all for now18:26
bjfamitk, is that all? (..)18:26
apwthat looks like a nose18:26
amitkheh18:26
bjf[TOPIC] Other Release Tasks: EC2 Lucid Kernel Status (jjohansen)18:26
MootBotNew Topic:  Other Release Tasks: EC2 Lucid Kernel Status (jjohansen)18:26
jjohansenupdated to latest patchset, apw packaged it into a ppa, everything tested out18:27
jjohansenso apw is going to roll out to the archive18:27
bjf'..' indicates that you are done18:28
jjohansenI still have to do some config updates to get EC2 closer to the virtual kernel configs but we are closer than we were in Karmic18:28
jjohansen..18:28
bjf:-)18:28
bjf[TOPIC] Status: Lucid (apw)18:28
MootBotNew Topic:  Status: Lucid (apw)18:28
apwyep its pleasing to have them so early in the cyle (-ec2)18:28
apwlucid we are mostly waiting on 2.6.32.  otherwise a few security items coming18:29
=== fader|lunch is now known as fader_
apw..18:29
bjf[TOPIC] Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)18:29
MootBotNew Topic:  Security & bugfix kernels - Karmic/Jaunty/Intrepid/Hardy/Others (smb)18:29
smbShort status this time: No current change. Security update nearby. Karmic SRU update follows closely.18:29
smb..18:29
bjf[TOPIC] Incoming Bugs: Regressions (ogasawara)18:29
MootBotNew Topic:  Incoming Bugs: Regressions (ogasawara)18:29
ogasawaraCurrent regression stats:18:29
ogasawara * regression-potential bugs: 9 (down 30) https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-potential18:29
ogasawara * regression-release bugs: 87 (up 34)  https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-release18:29
ogasawara * regression-update bugs: 14 (up 2)  https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-update18:29
ogasawara * regression-proposed: 1 (down 1) https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.tag=regression-proposed18:29
ogasawaraNote that the majority of regression-potential bugs have now become regression-release bugs which accounts for the larger delta this week18:30
ogasawara..18:30
bjf[TOPIC] Incoming Bugs: Bug day report (ogasawara)18:30
MootBotNew Topic:  Incoming Bugs: Bug day report (ogasawara)18:30
ogasawaraNext bug day will be Tues Dec 8.  I'll send email later this week.18:30
ogasawara..18:30
bjf[TOPIC] Open Discussion or Questions: Anyone have anything?18:30
MootBotNew Topic:  Open Discussion or Questions: Anyone have anything?18:30
apwogasawara, on the incoming bugs ...18:30
apwwould it be better to split by series there18:30
apwas the meaning of potential etc changes over time18:31
apw(incoming regressions)18:31
ogasawaraapw: should be easy to do since we're tagging by release18:31
bjf[ACTION] bjf to review lucid tasks to see if anything needs to be added to the meeting agenda18:31
MootBotACTION received:  bjf to review lucid tasks to see if anything needs to be added to the meeting agenda18:31
bjfanything else?18:32
apwbjf we might be able to generate the tasks bits from the status page generator18:32
bjfapw, ok18:32
bjfthanks everyone18:32
bjf#endmeeting18:32
MootBotMeeting finished at 12:32.18:32
apwthx18:32
smbthxbye18:33
amitkkthxbye18:34
=== RainCT_ is now known as RainCT
=== artir is now known as RainCT_
=== RainCT_ is now known as artir
czambuenas tarde, este es el canal de la reunion para ubuntu member?18:59
MenZaczam: I'm not very proficient in Spanish, but assuming you're asking about the EMEA Membership meeting, that's in ~40 minutes from now.19:20
MenZaczam: And yes, this is where you want to be :)19:20
czamMenZa ok, thanks ;)19:20
BlackZhi all :D19:20
IoneyeHi BlackZ19:21
czamHi everyone :D19:21
=== bjf is now known as bjf-afk
frandieguezEMEA in 10 minutes, isn't it?19:51
forumsmatthewyes19:51
MenZaAccording to my schedule, that sounds about right19:51
czamyep19:52
topylihi MenZa <319:52
MenZaHello topyli :)19:53
topylii made it! was called to play drums for some people who needed drums played, but i was able to get out19:53
MenZaexcellent19:53
topyliterrible, long day all in all :\19:54
* MenZa hugs topyli19:54
MenZaI'm quite tired myself19:54
MenZaLooking forward to hopping into bed19:54
fagan_hi all19:54
* topyli tickles MenZa19:54
MenZahello, fagan_19:55
IngForiguaHello everyone19:55
IngForiguagood luck today19:55
IngForigua:)19:55
Ioneyeyou too IngForigua :)19:55
* MenZa bows.19:55
asanchezHi everybody, thanks IngForigua19:56
* Ioneye bows before MenZa 19:56
ibuclawgood evening19:56
AlanBellevening all19:56
IngForiguaGood evening ibuclaw19:57
frandieguezHello everyone19:57
czamAlanBell Hi19:57
BodsdaEvenin all19:57
forumsmatthewwarm and cheerful greetings to all19:57
fmolineroHello everyone!19:57
czamhola paco ;)19:57
tdr112evening19:57
IngForiguahola fmolinero buen trabajo como traductor19:58
czajkowskiAloha19:58
ibuclawBodsda, that was a quick smoke you sure had...19:58
MenZaEvening czajkowski19:58
AlanBellhi czajkowski19:58
declanmgHi all19:58
airurandoEvening everyone.19:59
MenZaibuclaw: You'd be surprised how quickly people can smoke when they're in a hurry :)19:59
AlanBellwow, cz<tab> is ambiguous tonight!19:59
lau1good evening19:59
ibuclawMenZa, indeed =)19:59
MenZaAlanBell: it is!19:59
AlanBellhi czam19:59
* MenZa pours coffee all around19:59
MenZaevening, brobostigon20:00
* Ioneye thanks MenZa 20:00
Neil3ey up :)20:00
brobostigonhêlo MenZa20:00
lielHello20:00
asanchezthanks fmolinero for the translations we use daily, it's difficult to find something untranslated into spanish because of you :D20:00
lielIs there a meeting today of EMEA membership board?20:00
forumsmatthewyes20:00
frandieguezyes20:00
popeyyes!20:00
MenZathere is indeed.20:01
IoneyeYes liel.20:01
frandieguezwe're all waiting20:01
popeySeveas *poke*20:01
fagan_good luck all20:01
* MenZa bows to fagan_ 20:01
popeymarkvandenborre *poke*20:01
frandieguezgood luck!20:01
topyliah i see the clock20:01
markvandenborrepopey: alive and kicking!20:01
popeyyay20:01
popeywho are we missing?20:01
IngForiguait's time :)20:01
lielI wanted to register to this meeting, but I'm going to sleep at 20:30 UTC20:01
forumsmatthewstgraber *poke*20:02
popeyah yes20:02
markvandenborre(I might have to leave the meeting early today!)20:02
hollmanhello all20:02
fagan_evening Mean-Machine20:02
hollmanIngForigua: where is czam ?20:02
popeywell so far we are 320:02
Mean-Machinefagan_: hello20:03
IngForiguahollman is here20:03
MenZapopey: 'tis a start20:03
czamhere I am20:03
czamHi Hollman Thanks for your support :)20:03
IngForiguaczam the hollma's bithday is near xD20:03
hollmanho czam IngForigua  good luck today !!!20:04
popeyjust 1 min and we'll start20:04
IngForiguathanks hollman ;)20:04
markvandenborrepopey: are you taking the lead this time?20:04
popeyyeah, can do20:04
forumsmatthewsounds good to me20:04
Seveasoi20:04
Seveassorry for being late20:04
forumsmatthew\o/20:04
Neil3A - L - A - N - B - E - L - L !!! *waves pompoms* YAY!20:05
* MenZa slides Seveas some taart.jpg.20:05
popeyyay20:05
* AlanBell blushes20:05
popeyright, lets start20:05
Seveasfmolinero, you're up first20:05
fmolineroOk,20:05
ibuclawdrubin, ! :)20:06
fmolineroHello everyone20:06
ibuclawand hi duanedesign,20:06
fmolineroThis is my secon time here20:06
forestpiskiehi ibuclaw20:06
fmolineroMy name is Francisco Molineo. I'm spanish20:06
mhall119|workhey All20:06
popeynice beard20:06
mhall119|workbah20:06
ibuclawhi fmolinero - and forestpiskie20:06
mhall119|workAlanBell:20:06
forestpiskieforumsmatthew: a word please20:06
fmolineroAnd muy main job in Ubuntu is translate to spanish20:06
forumsmatthewreminder: agenda is here https://wiki.ubuntu.com/Membership/RegionalBoards/EMEA20:07
fmolineroI'm a member of Ubuntu spanish ttranslator team20:07
popeyOk, based on testimonials and clealy great translation work, I'm an easy +1 here20:07
Seveasyay, there are testimonials now20:07
Seveas+1, easily20:07
Seveasthanks for coming back fmolinero20:08
forumsmatthewagreed. +1 this time. thank you20:08
fmolineroand may last time here the problem was that I have not people standing me20:08
Seveasmarkvandenborre, ?20:08
markvandenborre+120:08
popeyyay20:08
markvandenborrehurray!20:08
Seveasok, that was quick :)20:08
Seveaswelcome aboard fmolinero!20:08
topyli<320:08
fagan_congrats fmolinero20:08
jchavescongrats!20:08
frandieguezcongrats fmoliinero!20:09
Mamarokcontrats fmolinero20:09
czamcongratulations Fmolinero ;)20:09
fmolinerothank you!20:09
lielfmolinero: I see you are very active in Translations!20:09
Bodsdacongrats fmolinero20:09
MenZacongratulations, fmolinero20:09
lau1well done20:09
hollmanfmolinero: congrats from Colombia20:09
Seveasibuclaw, you're up20:09
Ioneyecongrats fmolinero !20:09
jchavescontracts?20:09
czamfelicidades paco molinero ;)20:09
asanchezenhorabuena Paco!20:09
fmolinerogracias20:09
* popey has added fmolinero to ~ubuntumembers20:09
BlackZfmolinero, congratulations :D20:09
ibuclawSeveas, ty20:09
itnet7congrats fmolinero !!20:09
drubin\o/ ibuclaw goooood luck.20:09
Mamarokoops, congrats, of course :)20:09
IngForigua:) fmolinero bienvenido20:09
jchaveshehe20:09
ibuclawIf you haven't read it. https://wiki.ubuntu.com/ibuclaw20:09
* drubin is here to cheer on ibuclaw20:10
forumsmatthewI will give a quick +1 because I know Iain well from his work in the forums20:10
popeyholy cow look at all those testimonials!20:10
duanedesignIm here to support ibuclaw, his contribution to helping new users on the forums and in #ubuntu-beginners-help is second to none20:10
ibuclawMy name is Iain Buclaw. I am a member of the Beginners Team. I have been contributing on the Forums and IRC since April 2008.20:10
Seveasyeah, that's.... impressive20:10
forumsmatthewalso, forestpiskie asked me to lend his support as he had guests arrive at his house and couldn't stay20:11
* fagan_ didnt have that many testimonials when he got his ubuntu membership20:11
BodsdaI have to go. But ibuclaw has a huge +1 from me20:11
markvandenborresorry to be so quick here, but I think a +1 is appropriate20:11
popeyyeah, thats an easy +1 from me20:11
Silver-Fox-I support ibuclaw.  He's very friendly,  very helpful and an all round  great guy.  Big +1 from me =]20:11
Seveasagreed, +120:11
Seveasok, that's +4, welcome!20:12
ibuclawthanks =)20:12
* popey adds ibuclaw to ~ubuntumembers20:12
duanedesign\o/20:12
frandieguezcongrats20:12
fagan_congrats ibuclaw o/20:12
MenZaibuclaw: congratulations :)20:12
czamcongrats ;)20:12
Seveasfrandieguez, you're next20:12
Ioneyecongrats ibuclaw20:12
frandieguezHi everyone, just like fmolinero is my second time here.20:12
frandieguezMy name is Fran Diéguez from Spain.20:12
drubin\o/ \o/ \o/ \o/ \o/20:12
TuxPurplecongrats ibuclaw :)20:12
Bodsdacongrats ibuclaw20:12
Mamarokcongratulations ibuclaw!20:12
frandieguez I'm a software20:12
frandieguezengineer working at Open Source Department of a large educational20:12
frandieguezinstitution at Galicia (Spain)  http://www.usc.es/osl, here we are20:12
frandieguezinvestigating, developing and deploying open source solutions based on20:12
frandieguezUbuntu distribution.20:12
Bodsda:) \o/ \o/20:12
frandieguezAs a contributor I'm co-coordinator of the Ubuntu Galician Translation20:12
frandieguezTeam, focused on translate the Ubuntu OS to Galician language.  And20:12
frandieguezco-coordinator of Galicia LOCO Team focused on spread the "word of20:12
frandieguezUbuntu" :P20:12
Mean-Machineibuclaw: nice one! congrats!20:12
frandieguezFinally I translate GNOME desktop to galician language with just20:12
frandieguezanother person and currently we are focused on increase quality of20:12
frandiegueztranslations (homogeneization, terminology, and others).20:12
ibuclawthanks all20:12
frandieguezI'm also active on http://www.glug.es/ (Galician GNU/Linux User20:12
frandieguezGroup). On this group we try to talk to all the society the vantages20:12
frandieguezof Open Source, making courses, lectures at University among other20:12
frandieguezevents related with Open Source. At our website you can find a lot of20:12
frandieguezmini howtos based on Ubuntu OS.20:12
jchavescongrats!!20:13
Seveasanother well prepared wikipage with clear contributions and testimonials. Easily +120:14
SeveasI like prepared people. I really do :)20:14
liel+1 :)20:14
forumsmatthewI completely agree, people are following directions and making it very easy for us thus far20:14
forumsmatthew+120:14
popey+1 also20:14
Seveasmarkvandenborre, final verdict is yours20:15
markvandenborre+120:15
Seveasexcellent, +420:15
Seveascongrats frandieguez!20:15
AlanBellcongrats frandieguez20:15
frandieguezThank you all!!20:15
jchaveshurray!20:15
MenZafrandieguez: congratulations :)20:15
Mamarokcongratulations frandieguez :)20:15
SeveasAlanBell, you're up now20:15
fagan_congrats frandieguez20:15
markvandenborre...and from me!20:15
AlanBelljust letting the applause die down for a second20:15
Seveas(popey: can you keep doing the LP mangling?)20:15
itnet7congrats frandieguez and ibuclaw !20:15
asanchezenhorabuena frandieguez20:15
* popey adds frandieguez to ~ubuntumembers20:15
frandieguezasanchez gracias20:15
popeyyes Seveas :)20:15
Seveas++popey20:16
IngForiguaBienvenido frandieguez20:16
jchaveswell done, fran!20:16
czamcongrats ;)20:16
AlanBellHi I am Alan20:16
AlanBellI run a little business called The Open Learning Centre with my friend Alan Lord (aka The Open Sourcerer)20:16
asanchezfrandieguez, we have to talk after this meeting, meybe we have common interests20:16
AlanBellI have been doing IT consultancy of one type or another for 15 years20:16
AlanBellMy main focus used to be as a Lotus Notes and Domino developer, I worked for a number of Lotus then IBM business partners and in 2002 set up my own consulting business called Dominux Consulting, "Dominux" being the result of smashing together Domino and Linux20:16
AlanBellI found the projects where I delivered the best value to my customers were the ones that incorporated a Free Software component as part of the solution20:16
AlanBellso from there we set up a company to focus on the awesomness that is Free Software20:17
AlanBellthen we got enthusiastic about Ubuntu20:17
AlanBellwe are launching products based on Ubuntu20:17
AlanBelland being a part of the Ubuntu community is important to us20:18
popeyI am aware of AlanBells work, have left a testimonial and will +120:18
popeyI may be biassed though because AlanBell has brought me beer at my local pub at least once :)20:18
AlanBellI can confirm that popey also bought a round20:19
markvandenborreI have 100% confidence in popey's judgement, +120:19
SeveasI'm unconvinced by the wikipage, no real contributions to the ubuntu community are listed. Or am I reading it wrong?20:19
czajkowskiAlanBell: rocks and is ver helpful in #ubuntu-uk and is working with us on #ubuntu-women20:19
pleia2I'm here to support AlanBell too, and I didn't accept any bribes ;)20:19
forumsmatthewsame here +120:19
popeySeveas: AlanBell provides support in our loco channel20:19
Neil3+1 for AlanBell have seen that he's really helpful in #ubuntu-uk20:19
mhall119|workI dunno, anyone who does that much with Lotus Notes is probably evil20:19
* czajkowski is here to support AlanBell 20:19
FFEMTcJlol20:19
Seveaspleia2, *always* accept bribes :)20:19
* brobostigon also supports AlanBell 20:19
AlanBellmhall119|work: I am a *retired* notes developer20:20
SeveasAlanBell, are you bitter about it? :)20:20
* fagan_ supports AlanBell 20:20
* Mamarok gives her support to AlanBell, too20:20
mhall119|workokay, you get my non-counting +1 then20:20
AlanBellSeveas: actually no, the core of Notes is fantastic, and the architecture of CouchDB is based on some of the principals of that20:20
* Pendulum also supports AlanBell 20:21
SeveasI'm +0, so +3 for AlanBell, which still is enough :)20:21
Seveaswelcome aboard AlanBell !20:21
mhall119|workAlanBell: it was always the interface for Notes that bothered me20:21
Mamarokcongratulations, AlanBell :)20:21
czajkowskiAlanBell: whoooo congrats!!!!20:21
mhall119|workcongrats AlanBell20:21
MenZaCongratulations, AlanBell.20:21
Ioneyecongrats AlanBell20:21
Neil3'gratz AlanBell20:21
* popey adds AlanBell to ~ubuntumembers20:21
topyliyey!20:21
Seveastopyli, you're up next20:22
fagan_congrats AlanBell20:22
AlanBellthanks!20:22
topyliright20:22
Mamarokyay, topyli!20:22
itnet7congrats AlanBell !20:22
popeyooo, topyli is an easy +1 for me, I've seen topylis work and it's great, combined with great testimonials20:22
Seveas+∞ from me on topily, years of IRC contributions.20:22
Piciwoo! topyli!20:22
* MenZa concurs; topyli does amazing work in keeping -ot tidy and lovely.20:22
popeyget you with your unicode20:22
topylibeen a long day but here's a wiki page for a start https://wiki.ubuntu.com/JuhaSiltala20:22
topylii've been around forever in ubuntu-time, since the beginning. my contributions are mainly in irc support - for the first couple of years in #ubuntu, then in my local #ubuntu-fi. i'm a well known "linux person" in finland (some circles anyway)  and a very active advocate in my work as an academic, even though this work is more general than specific to ubuntu20:23
Seveaspopey, ascii doesn't have an 'infinity' symbol, so I have to make do :)20:23
topyli i'm a board member of the finnish national flug.  i'm a member of the irc operators team, and try to introduce the community spirit and norms to newbies on -offtopic channels, both main and local20:23
forumsmatthewtopyli, in your happy face picture you are wearing a hat that looks Moroccan, have you been there?20:23
topylis/flug/lug :)20:23
* popey chuckles at 'flug'20:23
topyliforumsmatthew, i think i bought it in seville20:24
* stgraber waves20:24
popey\o/ starcraft-ntbk20:24
popeyer20:24
popeystgraber:20:24
stgrabersorry for being late, just got some stuff delivered at home and had to help unload20:24
starcraft-ntbkwho what?20:24
Seveashey stgraber20:24
jussi01A huge +1 for topyli from me, a valuable contributor in #ubuntu-offtopic, being an op in there is a tough job, but he does it with compassion and grace. His contributions in #ubuntu-fi dont go unnoticed either.20:24
popeystarcraft-ntbk: back to sleep20:24
forumsmatthewyay, stgraber20:24
starcraft-ntbkbah, everyone tab fails me ><20:24
MamarokI strongly support topylis application, he does an incredible amount of work in 24 hours, one wonders if he ever sleeps. We need more people like him20:24
Seveasstgraber, you're not too late: lots more people coming up, we're grilling topyli now20:24
jussi01Seveas: can I have a bite when the grillings done? :D20:25
popeymarkvandenborre: you still here?20:25
Mamarokjussi01: behave ;)20:25
markvandenborreyes, but not for long, sorry20:25
topylijussi01, we can talk about it later :)20:25
Mamaroknew members are not for eating20:25
markvandenborre+1 from me20:26
popeystgraber: you ready to vote now you're here?20:26
Seveasforumsmatthew, stgraber?20:26
markvandenborrepopey: and unfortunately, I'll have to go20:26
forumsmatthewbased on the testimonials, +120:26
popeyno worries markvandenborre20:26
Picitopyli gets a definite +1 from me.  I may have been bribed with a promise of a new tales from the offtopic.20:26
markvandenborresee you all, and good luck to the candidates!20:26
forumsmatthewsee you, markvandenborre20:26
stgraber+1 (testimonials, wiki page, ...)20:26
popeyyay20:26
Seveasthat's +5, welcome aboard!20:27
jussi01Congrats topyli!20:27
MenZahuzzah! and now, grilled topyli for all!20:27
Piciyay!20:27
Seveasczam, you're up20:27
MenZaCongrats topyli - very much deserved :)20:27
czamok20:27
Mamarokcongratulations, topyli!!20:27
* popey adds topyli to ~ubuntumembers20:27
fagan_topyli congrats20:27
czamHi everyone ;)  this is mi wiki page https://wiki.ubuntu.com/czam/20:27
SeveasMenZa, behave. You'll be charred in a bit.20:27
Picitopyli: congrats :D20:27
topyliwhee! thanks for your confidence all20:27
czammi name is Carlos Andres Zambrano, I'm a GNU/linux user since 200420:27
czamI give support in the channel #ubuntu-co, in launchpad and mailing lists as ubuntu-es, ubuntu-co and for some days in the ubuntu-ar.20:27
czamalso actively participates promotional events in my Local team such as conferences, installation, SFD, UGJ and Release Party20:28
czamI want to become an official translator into Spanish of Ubuntu20:28
czamI'd like to help schools to implement Edubuntu with LSTP20:28
popeyhttp://picasaweb.google.es/czam01/SOftwareFreedomDayBogota2009#5383736714099226002   I don't think you could fit any more in there :)20:28
czamCurrently i'm working in Industrias Proton in which I'm migrating to Ubuntu 8.04 (hardy Heron),20:28
popeyhttp://picasaweb.google.es/czam01/SOftwareFreedomDayBogota2009#5383736720503829618   Ubuntu stand in 'Busier than mandriva stand' non-shocker! :)20:29
czampopey, that picture was in SFD 200920:29
popeylooks like you had a lot of interest?20:29
IngForiguaLol20:29
hollmanUbuntu stand in 'Busier than mandriva stand' non-shocker! :) ---> yeah :D20:29
Seveasczam, when did you start actively contributing to ubuntu?20:30
czamSeveas, since 2007 when I Satrted with feisty20:30
* Ioneye thinks why he is here...20:31
forumsmatthewlots of launchpad answers and karma for doing so, as well as translation activity20:31
itnet7congrats topyli (sorry out of the area for a sec!)20:31
Seveasczam, I find 2 testimonials a bit thin for over years of contributions20:32
SeveasDo you think you can gather a few more?20:32
czamSeveas, off course ;)20:32
Seveasczam, good, then I'm going to say -1 for now and hope you come to the next meeting with some more testimonials (unless the others vote +1, in which case you can ignore me :))20:33
czamSeveas ok I hope so20:34
forumsmatthewI'm borderline and am going to give a +0 (that will easily turn in to a +1 with more testimonials)20:34
popeyI'm agreed with forumsmatthew, for now +0.5, nearly +1, but if you can get a few more testimonials that would be great20:34
forumsmatthewI wasn't aware we could give fractional amounts... :)20:35
stgraberI'm going to follow forumsmatthew and popey on this one, come back with a few more testimonials and that'll be a +1, for now +0.20:35
popeyand keep up the great work czam !20:36
czamok popey20:36
Seveasok, see you next time czam!20:36
forumsmatthewI look forward to your return20:36
SeveasIngForigua, you're up20:36
IngForiguahi20:36
IngForiguaGood evening, my name is Diego forigua ( https://wiki.ubuntu.com/ingforigua ) ( https://launchpad.net/~ingforigua ) I'm electronic engineer, I'm GNU/linux user since 2004, i used Fedora core 2, Suse 9, red hat 9, i knew ubuntu 2006 (ubuntu 6.06 LTS) and it's my favorite GNU/linux distro20:36
itnet7czam awesome contributions so far!! keep up the good work!20:36
ubottuUbuntu bug 2006 in launchpad-foundations "Deactivated memberships should be hidden" [Medium,Fix released] https://launchpad.net/bugs/200620:36
IngForiguaI'm member of member of the council of Ubuntu-co, i give support at IRC in spanish, lauchpad and mailing lists, i help with answers and translations for ubuntu20:37
IngForiguamy future plans for ubuntu20:37
IngForiguaContinue contributing with Ubuntu (translations, bug report, give answers).20:37
MagicFabIngForigua rocks - *and* he asks/listens a lot for advice :)20:37
IngForiguai'll participate in my Loco team, help translate to Spanish documents, continue to give presentations (conferences) and active member of ubuntu. Help migrate my university to ubuntu from my research groups, EIDOS and Soliun20:38
IngForiguaI love ubuntu :)20:38
IngForiguathanks Magicfab20:38
SeveasIngForigua, czam: you're both in the colombian team, why didn't you leave a testimonial for each other?20:39
IngForiguaI work in venezuela team an ecuador team20:39
czamwe are close friends, but as we know the testimoniasl is only for Ubuntu Member20:40
IngForiguathey can give me a testimonial of my work with ubuntu20:40
* czam supports ingforigua20:40
Seveasczam, no, everyboty can write something to support prospective members, not just existing members20:40
MagicFabSeveas, it's a bit against our culture to recognize each others work too.20:40
* hollman support tooo mucho IngForigua he and czam are among the most active members in our team !!20:41
hollman**much20:41
czamwe don't know that, because we're very actively in Colombian Loco Team20:41
Seveasjust curious: why did you come to the EMEA meeting instead of the Americas meeting?20:41
* cleon recognizes IngForigua as an active member of Ubuntu colombian team in different events and isssues at an IRC chan20:42
IngForiguaclean tanks20:42
IngForiguacleon thanks20:42
czamSeveas, that its beacuse we want to become in a oficial ubuntu member before this year finishes20:42
fmolineroI recognize the great job of IngForigua bringing suggestion in spanish translation20:43
IngForiguaMy team (i'm member of council ubuntu-co) is the most active20:43
Seveasczam, well, to be honest I don't see that happening. For IngForigua I also want to see more testimonials on his wikipage. I find it too hard to judge his contribution properly as it is now. -120:43
forumsmatthewBased on the testimony of MagicFab, I am willing to +1 IngForigua20:43
forumsmatthewwhile having more on the wiki would be nice, he does have a pretty nice cheer squad with him today20:44
IngForiguaforumsmatthew thanks20:44
popeyhmm20:45
MagicFabSeveas, I regularly and consistently see IngForigua in Answers and IRC. he's very active. Testimonials are fine but karma and other info in his wiki should help see through that.20:45
IngForiguaSeveas many people helps me, but i only have testimonials of ubuntu members20:45
forumsmatthewI do understand the concern that Seveas is expressing, though20:45
MagicFabAnd their local work at events is incredible. I see the organizing skills and patience it requires and IngForigua *gets it*. We need more like him.20:46
popeyI'm going to +1 because I trust MagicFab's judgement20:46
SeveasMagicFab, the wikipage doesn't do it for me. It doesn't give any details about contributions to e.g. flisol. Just a few lines would do but it only lists the event20:46
IngForiguapopey thanks20:47
MagicFabWell, all the links point to pictures he's taken as organizer and participant20:47
Seveasstgraber, your vote?20:47
IngForiguaseveas I participate in many research groups, just to name the most important20:48
MagicFabBut yes, point taken, I personally reviewed his page (yes, he even asked for that) and we both overlooked that important detail. FLISOL is a huge, known event but yes it need proper linking.20:48
IngForiguai help with ubuntu mirror in colombia20:48
SeveasMagicFab, don't forget that you've come to the EMEA board, not a local board. I for one do not know FLISOL.20:49
IngForiguahttp://matematicas.unal.edu.co/ubuntu/20:49
Seveasstgraber, are you still with us?20:49
IngForiguait is oficial mirror20:49
MagicFabSeveas, correct, I am actually agreeing those links are missing.20:49
Seveashmm, looks like stgraber(s connection) has gone walkies. I don't really like to continue with only three board members.20:50
forumsmatthewunfortunately, I'm going to have to leave shortly as well20:51
stgraberjust got back20:51
Seveasah nice20:51
forumsmatthewgood20:51
stgraberquickly going through the backlog, give me 30s20:51
IngForiguastgraber ok20:51
SeveasMagicFab, another important thing: due to czam and IngForigua not being properly prepared we lost a lot of time. This is why preparation is important. There are a lot of people in the list for this meeting and now it looks like we have to disappoint a few.20:52
stgraberAlthough I trust MagicFab's judgement, I'd rather see a more detailed wiki page and updated testimonials. -1 for now, will be glad to see both of IngForigua and czam again and change that for a +1.20:53
IoneyeSeveas: patient is bliss ;)20:54
Seveasok, so that's +0, IngForigua please prepare your wikipage better for next time, see you soon!20:54
Seveasebel, you're up20:54
ebelHi20:54
tdr112good luck ebel20:54
czajkowskiwhoooo20:54
IngForiguaSeveas my wiki page is ready20:54
popeykeep up the great work IngForigua20:54
* Mean-Machine is here to support ebel \o/20:54
declanmggo ebel!20:54
fagan_o/*20:54
lau1best of luck ebel20:54
ebelI'm Rory McCann and this is my first time here20:54
ebelMy wiki page https://wiki.ubuntu.com/rorymcc20:54
airurandobest of luck ebel20:54
ebel(cheers guys :) )20:55
slashtomgood luck ebel20:55
ebelI'm from Dublin, Ireland, and I'm the point of contact for the ubuntu-ie loco20:55
* MagicFab whips the horse20:55
czamok see you next time20:55
MagicFabThanks for your time, we'll come back.20:55
forumsmatthewMagicFab, please do so :)20:55
ebelI've been helping run events (from bug jams to release parties to regular monthly pub meets)20:55
popeyi like the testimonials there20:56
ebelI've been chairing ubuntu-ie IRC meetings for a while now.20:56
Seveas+1 for ebel, that's an awesome list of contributions, also well documented and with testimonials20:56
ebelI've also been a camara volunteer, teaching about ubuntu and linux in african schools20:56
forumsmattheweasy +120:56
popeyyeah, +1 here too20:56
ebelaswell as providing some custom installers and tech support for camara20:56
stgraberah, that's easy: +120:57
czajkowskiyay!20:57
Seveasok, +4, welcome aboard!20:57
fagan_congrats ebel20:57
Mean-Machineyea! well done ebel! congrats!20:57
airurandoWell Done Ebel!!!! Whoooooo!!!20:57
itnet7congrats ebel!!! Go ubuntu-ie!!!20:57
* czajkowski gives ebel a great big hug!!!20:57
ebelaw cool :)20:57
slashtomwell done ebel20:57
Seveasdeclanmg, you're up20:57
lau1well done20:57
* popey adds ebel to ~ubuntumembers20:57
tdr112well done ebel20:57
declanmgHi folks, my name is Declan McGrath. I'm a Dublin-based Kubuntu fan and Ruby developer.20:57
Mean-MachineC'mon Ireland!20:57
ebel:D20:57
fagan_thats 5 members for -ie now :)20:57
declanmgBeen turning up to the Linux and Ubuntu Dublin meetups for the best part of 2 years now in search of Free Beer :-)20:57
Seveasforumsmatthew, how much time do you have?20:57
declanmgMy wiki page is at https://wiki.ubuntu.com/declanmg20:57
airurandogood luck declanmg20:57
forumsmatthewIf it is quick, I think I can hang in for one more application20:57
* Mean-Machine is here to support declanmg \o/20:57
ebelgood luck declanmg20:57
declanmgthanks guys!20:58
lau1best of luck declanmg20:58
czajkowskideclanmg: we're rooting for you20:58
declanmgI've been involved on the development side of Ubuntu a little, most recently with the bazaar source control system.20:58
declanmgMy name aim is to try and get as many developers in Ireland into FOSS development.20:58
Seveashmm, ruby programmer, -120:58
declanmgI've been trying podcasting, giving programming lessons and generally any trick I can think of! But those Ubuntu UK Podcasters have the market sown up :-)20:58
popeyhaha20:58
popeydont you believe it!20:58
Seveas(just kidding, but I've been fighting ruby too much lately...)20:58
declanmgand a little python :-)20:58
* fagan_ forgot to give a testimonial for declanmg 20:58
czajkowskiSeveas: lordie! what a heart attack to give someone! :p20:59
Seveasczajkowski, what would you say is declanmg's most valuable contribution to date?20:59
forumsmatthewagain, well done with the testimonials!20:59
declanmgthanks forumsmatthew20:59
czajkowskiSeveas: he just turns up and starts helping out, I don't need to ask him to do anything20:59
Riddelldeclanmg: how can Kubuntu and LoCos work better together?20:59
czajkowskiSeveas: he;s also quick to take pointers and get people motivated20:59
popeyuhoh, someone woke the Riddell21:00
Seveasooh, nice question Riddell, that's something we have problems with here in NL as well21:00
declanmgRiddell: I think currently it works fine.21:00
declanmgWhat I really want to do is...21:00
Riddellit does?  we (kubuntu devs) don't do anything with locos21:01
popeywe're over-running and there's a cc meeting up next21:01
declanmg... get the the python guys i know into  ubuntu development21:01
Seveasok, finishing up then, +1 for declanmg21:01
FFEMTcJcc isn't for another hour isnt it?21:01
forumsmatthew+121:01
forumsmatthewand I'm afraid that with that, I need to leave21:02
MenZaFFEMTcJ: correct21:02
popey+1 also21:02
popeydeclanmg: feel free to ping me if you want to talk about podcasting :)21:02
declanmgRiddell: i feel that there is always a good kubuntu representation here on the dublin scene21:02
stgraber+121:02
czajkowskiwhooo another Irish Ubuntu Member, great stuff outta declanmg and ebel tonight :D21:02
fagan_congrats declanmg21:02
Seveasthat's +4, welcome aboard!21:02
Mean-Machinedeclanmg: congrats! now party time in #ubuntu-ie \o/21:02
ebel:D21:02
forumsmatthewbest wishes all21:02
SeveasBlackZ, Ioneye, FFEMTcJ, asanchez, MenZa: looks like we'll have to disappoint you for now. Please come to the next meeting!21:02
ebelcongrats declanmg21:02
MenZaSeveas: Shall do.21:02
declanmgpopey: cheers. will do.21:02
fagan_thats 6 -ie ubuntu members awesome21:02
lau1congrats declanmg21:02
airurandoBrillian.t congrats declanmg21:02
* popey adds declanmg to ~ubuntumembers21:02
declanmgthanks guys!21:02
Ioneyeit's ok Seveas :)21:03
declanmgmuch appreciated!21:03
itnet7congrats declanmg !!21:03
Mamarokcongratulations declanmg :)21:03
fagan_:)21:03
* czajkowski loves her Irish LoCo 21:03
BlackZSeveas, ok.21:03
SeveasMenZa, oh, and remind me to write something on your wikipage :)21:03
popeypleia2 / Technoviking / sabdfl when's this cc meeting? dholbach said 21:00 UTC to me21:03
MenZaSeveas: Appreciated. Will do :)21:03
asanchezthanks for your time everybody21:03
Mean-MachineIrish LoCo ROXX!21:03
MenZapopey: According to the Fridge calendar, another hour from now21:03
pleia2popey: it's in an hour, I think21:03
MenZai.e. 22 UTC21:03
popeyhmm21:03
pleia2yeah21:03
pleia2but maybe fridge is messed up :) it should be at 21:0021:04
Seveaspopey, but without matthew there's only three of us, and it looks like I need to pop out as well21:04
* fagan_ needs to go good job guys and gals21:04
MenZaSort it out among yourselves; the plan was an hour's meeting, and, well, it is getting late in most timezones21:04
makoare you counting me?21:04
makoMenZa: where most is european/african?  :)21:04
* MenZa hates having his planning screwed up, so completely understands the decision to #endmeeting21:05
popeyso i guess dholbach just messed his time up21:06
MenZanight all - and congrats to all who were picked :)21:06
Seveasnight MenZa21:07
popeys/were picked/earned it/ :)21:07
pleia2popey: it should be now, the fridge is wrong21:07
popeyah21:07
MenZaWell, one is picked, *if* one has earned it, aye popey?21:07
TechnovikingThe fridge is never wrong21:07
Technoviking:)21:07
popeyALL HAIL THE FRIDGE!21:07
popeyetc21:07
MenZaLanguage barrier + fatigue = bad outcome21:07
pleia2fridge gets confused by DST :\21:08
popeyok, so cc'ers are back in 50 mins ya?21:08
SeveasALL HAIL THE BEER IN THE FRIDGE21:08
makoyeah, i can be back in 5021:08
popeythanks mako21:09
Ioneyeso the meeting for the EMEA is over?21:09
popeyyes21:09
pleia2popey: yep21:09
popeymaybe we should schedule another EMEA for 2 weeks time21:10
popeySeveas: i see you removed czam and IngForigua from the emea wiki page...21:10
Technovikingso CC in 50 mins21:10
popeyshould we not leave them on for next meet21:10
popeyyes Technoviking21:11
Seveaspopey, we haven't done that for the last few months21:11
IngForiguaSorry21:11
Seveas(iirc)21:11
popeyoh21:11
IngForiguaSeveas thanks21:11
IngForiguaGoodbye21:11
MenZapopey: I was rejected back when CC took care of membership applications; I didn't return the following month, instead deciding I'd keep my contributions going for a while longer before re-applying21:12
MenZa(so, now)21:12
Seveaspopey, I'm all for an extra meeting in 2 weeks time21:13
Seveasstgraber?21:13
popeycool21:13
Seveasok, need to leave now21:13
Seveasbye!21:13
MenZaI trust this'll be added to the Fridge if one is planned, popey?21:13
MenZaSeveas: night!21:14
popeyyup21:14
MenZaexcellent21:14
nizarusthe cc meeting is over ?21:20
popeycc in 40 mins21:20
nizarushi popey21:21
jarlenhm, I didn't even get the chance to impress with the picture of MenZa playing chess in a roller coaster :/21:21
* nizarus still waiting for popey replay to my mail (you remember)21:21
popeyerk, really?21:33
=== bjf-afk is now known as bjf
Technovikinghello22:02
popeyHi!22:02
pleia2hi22:02
Raidsonghowdy22:02
Technovikingis mako and mario around?22:03
popeyjust poked superm122:04
makoi'm around22:04
drubinmeeting22:07
drubin?22:07
pleia2drubin: CC meeting, just gathering folks22:08
drubinpleia2: I thought it was a beginners meeting.22:08
pleia2drubin: that's being held over in -beginners22:08
drubinthey are both scheduled for 22:00 guess we moving to #ubuntu-beginners22:08
makoseems to be scheduled for the same time :)22:09
drubinno worries we have another channel.22:09
=== TuxPurple is now known as Calvin
=== Calvin is now known as TuxPurple
popeynot looking good22:17
pleia2shame22:17
makoso we have a pretty short aenda?22:17
pleia2yeah22:17
makowhat is the problem22:17
pleia2folks we need to discuss agenda items with aren't around22:18
Technovikingwe could discuss and vote on the Dell blog on the Planet on the mailing list22:19
popeywe're not quorate though are we?22:19
popeyso can't realistically vote22:19
=== fader_ is now known as fader|away
makopopey: well, i'd be happy to talk about the dell blog22:24
makoor we can do it over email22:24
popeyI'm easy.22:24
makoyeah, lets do it over email them and then publish something22:24
pleia2sounds good22:24
popeyok22:24
makoit's just important that it happens22:24
popeyindeed22:24
makosince we have a policy that corporate blogs aren't supposed to be on unless they're discussed22:24
Technovikinganyone else got anything for the CC22:25
makoyeah, we're all here22:25
makoFSVO all :)22:25
TechnovikingHas Dell been removed for the planet feed for now?22:25
* popey had to google fsvo :)22:25
popeyno22:25
popeythe feed is still there22:25
TechnovikingI will remove it till we have a change to discuss22:26
makoTechnoviking: awesome, thanks22:28
Technovikingdone and done22:31
superm1popey, Daviey i'm here22:31
superm1hopefully not too late?22:31
popeyhi superm122:31
popeywe've removed the rss feed for the dell blog from the ubuntu planet subject to it being discussed by the cc22:32
superm1isn't that what's on this meeting's agenda?22:32
popeyyes, but that discussion hasn't happened yet22:33
popeybefore you arrived we decided to take the discussion to the mailing list given the required people weren't here22:33
superm1what kind of discussion does there need to be?22:34
popeyhttps://wiki.ubuntu.com/PlanetUbuntu#Corporate%20Blogs22:34
popeywell the criteria is detailed on that page22:34
popeyi guess the most pertinent one is "the CommunityCouncil must give permission "22:34
popeythe rest seem to be pretty well covered :)22:35
popeydoes that sound fair?22:36
* Daviey feels it's a shame that it won't be discussed in the open.22:37
pleia2now that superm1 is here, do we want to?22:37
pleia2we don't have quorum to vote, but it can be discussed22:38
popeyI'm happy to22:38
pleia2given the criteria for corporate blogs, I think dell's blog is acceptable22:39
popeyheh, I agree22:41
Technovikingi agree also22:41
popeymako: ?22:42
Technovikingapparently mako has left the building22:48
popeyuh-huh-huh22:48
pleia2is there anyone who would like to raise any objections for us to concider?22:48
pleia2consider too, need sleeep22:48
popeythe only objection I have seen is a misguided blog post22:49
superm1which one?22:51
superm1there's a team of probably about 10 people who can comment to that blog, but the only stuff that should be showing up there is consumer linux related things22:51
popeyhmm, cant find it now22:52
popeywe (ubuntu uk podcast) have a feed on the planet, which I'll grant you isnt corporate, but equally isn't an individual. We as a group decided that only those of us who are Ubuntu members (thats me and Daviey) should hit the button that posts to the planet22:53
popeythe only concern I have is that there may be people who a) haven't signed the CoC, b) aren't members, may post to that blog22:54
popeyin our case it's technically possible for non-members to post to the planet (from the podcast feed) we don't do it as a matter of principle22:54
superm1"# the company must have at least one Ubuntu member who can take responsibility for the blog "22:55
popeyexactly22:55
superm1so that's me22:55
popeybut any of the 10 could post22:55
popeyfact is though as a corporate blog I'm guessing that your internal controls would prevent any of those 10 doing something monumentally stupid :)22:56
superm1no, there's actually a peer review process for any blog post22:56
popeyand you hit the final button?22:56
superm1i'm generally one of the peers who sees it, but lionel manchaca (sp) makes the final call22:57
Technovikingsuperm1: can your blog you tags and only allow post tag Ubuntu to the planet, and you would be the one to add that tag?22:57
superm1he's the big social guy for dell, and manages the presence on blogs, twitter, fb22:57
popeyTechnoviking: it's tagged "Linux"22:58
popeywhich seems sensible to me22:58
popeyhttp://en.community.dell.com/blogs/direct2dell/archive/tags/Linux/default.aspx22:58
superm1there might be a moblin or chrome thing that comes up every so often, but that's all ubuntu based anyway22:59
popey.. and I'd say is interesting to the audience of planet ubuntu22:59
popey(although everyone has their own opinion on that)22:59
Technovikingsuperm1: can you pull the plug on a post if you think the Ubuntu community would not be interested23:00
Technovikingor does what Lionel say goes23:01
superm1posts can be pulled23:01
superm1but they would be pulled from the blog as a whole, not just from planet syndication23:01
popeyOk, so those of us here seem to agree that the dell blog is a +1 for inclusion on the planet23:02
popeyI'll mail this log to the cc and see if we can get a quick +1/-1 from everyone and re-enable the blog promptly23:02
popeythat sound okay?23:02
popeyI doubt there will be much in the way of discussion, so Davieys concerns about open discussion shouldn't manifest23:03
pleia2thanks popey23:03
TechnovikingI'm still +1 if superm1 does see the posts first23:04
popeysure, me too23:04
popeyso thats 3 of the 8 members of the cc, but that's not really enough23:04
popeythat okay superm1 ?23:05
popeyDaviey: ?23:05
superm1sounds fine to me23:05
popeyDaviey is clearly busy upgrading his htc handset to android 2.123:06
popeysent23:09
Technovikingok, is there anything else for the CC23:12
popeyno23:12
Davieypopey: heh23:12
superm1okay thanks guys, cya23:12
=== robbiew_ is now known as robbiew-afk
Technovikingok, I think we will see people in two weeks23:14
Davieysounds good to me \o/23:15
Daviey(the scrollback)23:16
garrythefishnot enough real drilling23:26
garrythefishthat's what's the problem with the lesbos at #ubuntu-women23:26
Daviey!ops | garrythefish23:26
garrythefishbye23:27

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