/srv/irclogs.ubuntu.com/2010/11/16/#ubuntu-meeting.txt

=== jjohansen1 is now known as jj-afk
* persia peers about10:11
* davidm wonders what persia is looking for?13:00
NCommander#startmeeting13:00
MootBotMeeting started at 07:00. The chair is NCommander.13:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]13:00
NCommanderbot is laggy this morning13:00
ogra_acroll call ?13:00
NCommander[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010111613:00
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010111613:00
NCommanderIf your not here, say I13:00
* ogra_ac added some topics today13:00
GrueMasterI13:00
ogra_acthe indentation of bullet lists is broken :'-(13:01
ogra_acwith the new theme ...13:01
rsalveti:-(13:01
* NCommander didn't notice13:01
davidmI am not here13:01
NCommander<- *doesn't use the standard theme :-(*13:01
NCommanderoh good, davidm is not here, we can skip the meeting :-)13:02
* NCommander runs13:02
ogra_acnah, we cant13:02
* NCommander pokes persia 13:02
NCommanderdamn it, I was tlaking with him less than an hour ago13:02
NCommandermeh13:02
NCommanderanyway13:02
NCommander[topic] Action Item Review13:02
MootBotNew Topic:  Action Item Review13:02
NCommander[topic] ogra to track down why NCommander's specs aren't on the tracker and to have that fixed13:03
MootBotNew Topic:  ogra to track down why NCommander's specs aren't on the tracker and to have that fixed13:03
NCommanderResolved. ogra told me I have to have them set for Approved13:03
ogra_acdone, davidm needs to approve for natty13:03
ogra_ac(i would have done it but i dont have the lever)13:03
rsalvetiI also have one that I just noticed that needs to be approved for natty13:03
ogra_acapprover needs to do it13:03
rsalvetidavidm: https://blueprints.edge.launchpad.net/ubuntu/+spec/multimedia-arm-gles-in-ubuntu :-)13:04
rsalvetididn't got on my list when i send you to approve because asac created it just before uds13:04
NCommanderdavidm: https://blueprints.edge.launchpad.net/ubuntu/+spec/other-arm-n-userland-subarch-detection & https://blueprints.edge.launchpad.net/ubuntu/+spec/other-arm-natty-improved-subarch-detection13:04
NCommander:-)13:04
NCommanderanyway13:05
ogra_acuserland is fine13:05
NCommander[topic] NCommander to supervise pre-installed omap4 images for Alpha 113:05
MootBotNew Topic:  NCommander to supervise pre-installed omap4 images for Alpha 113:05
NCommanderWe hav eimages!13:05
* ogra_ac did that13:05
NCommanderindeed13:05
NCommandernice work :-)13:05
ogra_acyes, but only through an evil hack lool did13:05
rsalvetiheheh13:05
NCommanderogra_ac: there's another type of hack?13:06
ogra_aci hope we can keep it until the bug is fixed13:06
NCommanderogra_ac: what's the hack for reference sake?13:06
ogra_acBug 67414613:06
ubottuLaunchpad bug 674146 in dpkg (Ubuntu Natty) "dpkg segfaults during debootstrap on natty armel" [High,In progress] https://launchpad.net/bugs/67414613:06
NCommanderugh13:06
NCommanderI saw that one13:06
ogra_acyes13:06
rsalvetiugly one13:06
NCommanderthat's a hack13:06
rsalvetiinteresting compiler behavior13:06
ogra_acimages build now though13:06
NCommanderx-loader is also FTBFS. I looked at it for a bit but didn't get anywhere13:06
ogra_acNCommander, my job13:07
davidmrsajdok, NCommander BP taken care of13:07
rsalvetiI can help fixing x-loader too13:07
NCommanderQt should get resolved sometime this week.13:07
* NCommander is thorugh most of his email and is just summerizing13:07
NCommanderso I think we're actually on track to meet alpha 113:07
ogra_acrsalveti, would you take that, and also re-integrate lools changes to the packaging ?13:07
rsalvetiogra_ac: no news from qt with full neon support13:07
NCommander(that's a first)13:07
rsalvetiogra_ac: sure, np13:07
ogra_acrsalveti, i'll re-upload the static no-NEON build on friday13:07
rsalvetiogra_ac: nice13:08
ogra_acScottK, ^^^^13:08
rsalvetiunfortunately the neon automatically detection is broken upstream13:08
ogra_acyes13:08
rsalvetinobody ever tested it13:08
ogra_acand likely in natty as well13:08
rsalvetiso it's not something that will be easily backported13:09
rsalvetisure13:09
NCommanderrsalveti: qt has a few growing pains when dealing with various ARM configuraitons.13:09
ogra_acthough i hope upstream will have fixed it within natty timeframe13:09
ogra_acwhat do we do about natty though ?13:09
rsalvetiNCommander: interesting that nokia pays to be well supported at arm :-)13:09
ogra_ackeep it broken or do the same static fix until upstream tells us its fixed ?13:09
NCommanderrsalveti: no comment.13:09
ogra_acdavidm, ^^^ any suggestion ?13:10
NCommanderogra_ac: static fix? (I'm blanking on what your referring to)13:10
ogra_acNCommander, read the bug :P13:10
rsalvetiogra_ac: for natty I'd say we could go with a similar fix13:10
rsalvetiwe don't have the post release regression on it13:10
ogra_acBug 66443113:10
ubottuLaunchpad bug 664431 in qt4-x11 (Ubuntu Maverick) "QT on armel is built with NEON by default" [High,In progress] https://launchpad.net/bugs/66443113:10
NCommanderoh13:10
NCommanderthat bug13:10
NCommanderugh13:11
ScottKogra_ac: Can we publish NEON .debs somewhere for the people wher are using Qt on NEON devices?13:11
rsalvetiso we're ok to disable it for now, and then enable it as an additional feature13:11
NCommanderexplains why KDE segfaulted on Dove13:11
* NCommander coughs13:11
ogra_acScottK, as soon as davidm's PPA spec is implemented we can offer a PPA13:11
rsalvetiScottK: I can put it on a ppa and post the link13:11
ogra_acor what rsalveti says13:11
rsalvetican get that action13:11
ogra_acScottK, plan for natty is to have public arm PPAs for everyone13:11
davidmThe PPA spec is in progress but it's going to take a couple of months to get the hardware all in13:12
ogra_acso you should then just be able to do it yourself13:12
ogra_acdavidm, what about neon ?13:12
ogra_ac(see above)13:12
ScottKogra_ac: I understand, but I'm concerned about the regression for people with NEON devices running Qt (of which I know there are some).13:12
ogra_acScottK, yes, understood, rsalveti will do a build in our team PPA and make that public13:12
ogra_acNCommander, action ^^^13:13
NCommanderdavidm: I looked at the spec, and I have some places where I need to make changes, but I need to talk with IS and the LP gearheads to make sure all my ducks are in a row before I'll have the implementation part finalized for you13:13
ScottKBTW, my latest Qt build finished in less than 12 hours with three systems sharing the build via icecc.13:13
NCommander[action] rsalveti to create NEON enabled Qt build and post it publicly13:13
MootBotACTION received:  rsalveti to create NEON enabled Qt build and post it publicly13:13
NCommanderScottK: Qt works great with icecc. OO.o, not so much :-(13:13
rsalvetiogra_ac: then lets push the same fix for natty, at least for now13:14
ogra_acgah, i had another point i missed to add to the meeting page13:14
rsalvetiwe'll have more people using it as ac100 is all around13:14
ogra_acrsalveti, yes, i wanted to hear that from davidm13:14
ogra_ac:)13:14
ogra_aci think we both agree, but i want some higher authority to blame ;)13:14
rsalvetihaha :-)13:15
rsalvetifair enough13:15
* NCommander coughs andmoves on13:15
NCommander[action] ogra_ac and rsalveti to talk to davidm on proper approach to fix Qt13:15
MootBotACTION received:  ogra_ac and rsalveti to talk to davidm on proper approach to fix Qt13:15
NCommander[topic] Special Items13:16
MootBotNew Topic:  Special Items13:16
NCommander[topic] canonical-mobile was completely deleted and replaced by canonical-arm13:16
MootBotNew Topic:  canonical-mobile was completely deleted and replaced by canonical-arm13:16
NCommanderwhy is this on here?13:16
NCommanderThis is the Ubuntu Mobile meeting, not the Canonical ARM one.13:16
rsalvetiwell, we can change ;-)13:16
NCommander(incidently, the work item tracker needs to be changed to track ubuntu-armel, and NOT canonical-arm)13:16
ogra_acNCommander, ubuntu-mobile doesnt exist anymore13:17
NCommanderogra_ac: so the name of the meeting is an artifact13:17
NCommanderthat can be fixed, its the Ubuntu ARM Meeting now :-P13:17
ogra_acthe next two points would have been indended suppoints13:17
ogra_ac*sub13:17
GrueMasterThat's how they appear here.13:18
ogra_acand are the actual bulletpoints13:18
ogra_acGrueMaster, not with the new theme13:18
NCommanderogra_ac: some of us have custom themes set13:18
NCommanderanyway13:18
davidmogra, neon needs to be in libs not hard compiled in13:18
ogra_acdavidm, thanks !13:18
ogra_acso: there might be some fallout, please everyone check if i.e. PPA access for important PPAs is missing etc.13:18
NCommanderGrueMaster: can you look at the bug lists, and make sure we have ubuntu-armel properly subscribed?13:18
davidmuntil there is no hardware that does not support neon that is how it has to be13:18
NCommander(it should be in all places, since that team wasn't renamed, but ...)13:19
ogra_acright13:19
ogra_acplease everyone check their PPA accresses etc13:19
ogra_acsince there might have been team PPAs we could access through canonical-mobile membership13:19
ogra_acif you find anything, please ping me13:19
ogra_acNCommander, action for all ^^^13:19
NCommanderogra_ac: wrong venue for ~canonical-mobile/~canonica-arm stuff.13:19
NCommanderSeriously13:19
NCommander[topic] cloosing down of the ubuntu-mobile mailing list13:20
MootBotNew Topic:  cloosing down of the ubuntu-mobile mailing list13:20
NCommanderdo we have an ubuntu-arm(el) mailing list?13:20
ogra_acno13:20
loologra_ac: [ Ain't a hack and ain't that evil! ]13:20
rsalvetino yet13:20
ogra_aclool, heh13:20
loolJust a taste thing13:20
ogra_acwe wont have an arm ML13:21
ogra_acdoesnt make sense13:21
ogra_acadn with the vanishing of ubuntu-mobile the ML needs to go13:21
NCommanderlool: I'm guessing evil in France is different than evil in the rest of the world ;-)13:21
ogra_acdavidm wants to close it down soon13:21
* NCommander runs13:21
rsalvetiwhy don't we have a m-l?13:21
rsalvetiI mean, an arm one13:21
NCommanderogra_ac: I'd like a mailing list for armel (or at least ports in general)13:21
davidmthere is virtually no traffic except spam on the ML13:21
ogra_acwhat for would we need one ?13:21
NCommanderdavidm: well, that and the mailing annoucements13:21
ogra_acwe dont have an amd64 one either13:21
ogra_acnora a sparc or hppa one13:22
NCommanderogra_ac: cause amd64 is a mainline arch13:22
davidmthe ubuntu-devel is more then good enough13:22
NCommanderpowerpc has one13:22
ogra_acubuntu-devel and ubuntu-devel-discuss should serve our needs13:22
davidmso?13:22
NCommanderfair enough13:22
NCommanderWho's tasked with shooting the u-mobile list dead?13:22
ogra_acdavidm13:22
davidmI can file the rt ticket to kill it13:22
ogra_acNCommander, just make sure to send the meeting announcements to -desvel now13:23
NCommander[action] davidm to archive the ubuntu-mobile mailing list13:23
MootBotACTION received:  davidm to archive the ubuntu-mobile mailing list13:23
NCommanderogra_ac: will do13:23
ogra_acaction ?13:23
NCommander[action] NCommander to send mailing list annoucements to u-devel13:23
MootBotACTION received:  NCommander to send mailing list annoucements to u-devel13:23
ogra_ac:)13:23
* NCommander doesn't quite type that fast13:23
NCommander:-P13:23
ogra_acbtw, i added another bullet point after meeting time13:23
NCommander[topic] New meeting time13:23
MootBotNew Topic:  New meeting time13:23
ogra_ac(please reload wiki if you havent)13:23
NCommanderSince we've recently had some regulars in this change and/or relocated, I think we should look at moving the metting13:24
ogra_acthe metting ;)13:24
ogra_ac(mett is chopped meat in german ;) )13:24
NCommander(plus those of us on the pacific time or further west have been shafted now for the last 6 months, someone else needs this pain)13:24
NCommanderI'm proposing we simply move the meeting by 12 hours13:25
* rsalveti doesn't like that13:25
ogra_acwell, lets ask persia13:25
davidmNCommander, I recomend we shelf this untl next week13:25
ogra_ac12h ?!?13:25
NCommanderdavidm: fair enough13:25
ogra_acthats 2am in europe13:25
NCommanderogra_ac: yeah, that would be 17:00 here13:25
davidmAnd we need to look at all times not a 12 hour shift13:25
GrueMasterpersia is looking into available timeslots with the idea of being more TI friendly.13:25
* ogra_ac refuses to have two nightly meetings13:25
NCommanderright, so here's what we do13:26
ogra_acGrueMaster, TI is mainly Nice nowadays13:26
GrueMasterWe had a discussion about this last night.13:26
NCommander[action] everyone to put proposals of new times (and days) on the wiki13:26
MootBotACTION received:  everyone to put proposals of new times (and days) on the wiki13:26
ogra_acso it should be european workhours13:26
NCommander[action] davidm + persia to get input from TI on recommended times13:26
MootBotACTION received:  davidm + persia to get input from TI on recommended times13:26
NCommanderAnd then next week we're determine when is the best time.13:26
NCommanderk?13:26
ogra_ac++13:26
NCommandermoving on :-)13:27
NCommander[topic] the return of openoffice on arm images due to desktop team merging the seeds13:27
MootBotNew Topic:  the return of openoffice on arm images due to desktop team merging the seeds13:27
ogra_acjust a warning ;)13:27
* NCommander goes to cry in the corner with this topic13:27
ogra_acfor the OO.o lovers among us13:27
NCommanderPlease, don't let Oracle touch me. It burns!13:27
ogra_ac-desktop team will merge the seeds13:27
ogra_acand only build a single image13:27
ogra_acwe might or might not differ in that13:27
NCommanderogra_ac: sounds like we need to get spice seeds this cycle then to prevent this. OO.o + ARM sucks13:27
ogra_aci have a workitem on their spec to research that13:28
NCommanderor at least an architecture specific exclusion13:28
GrueMasterI believe it was announced that we will be moving to LibreOffice.13:28
davidmSounds like we are going to need an ARM seed to me13:28
ogra_acNCommander, we might need to build desktop images this cycle13:28
NCommanderogra_ac: well persia came up with a possible lead to find the missing notes so we might get lucky13:28
ogra_acdavidm, i wouldnt like that if we can avoid it13:28
NCommanderogra_ac: *wince*. Bad things happen when we try and remove OO.o from desktop13:28
ogra_acnot anymore13:28
NCommanderogra_ac: would or wouldn't?13:28
ogra_acwouldnt13:28
davidmI don't want OO back on the build it takes to much room13:28
ogra_aci'd like to go with one seed13:29
NCommanderI don't want OO.o cause we're almost out of cows to sacirife to keep it going13:29
davidmI'd love to go with one seed if it meets our needs, which OO does not13:29
ogra_acbut the question is how technically hard that is13:29
NCommanderogra_ac: I'll take this action item13:29
ogra_acdavidm, on desktop images ?13:29
davidmAlso we don't have mono working still13:29
NCommanderand research if we can sanely exclude OOo if we build desktop in fair of something (anything) else13:29
NCommanderdavidm: OOo doesn't depend on mono (yet), just java13:29
davidmogra, not at the moment13:29
ogra_acNCommander, preferably i dont want us to have the extra work to keep seeds in sync13:29
NCommanderthough I think openjdk is kinda foobar'ed13:29
ogra_ac??13:30
davidmNCommander,  but the new audio player for desktrop does I think13:30
ogra_acopenjdk is fine13:30
NCommanderogra_ac: what I'm hoping is we can do one seed, but get OOo off our images13:30
ogra_acwe can13:30
ogra_acthats no prob13:30
NCommanderogra_ac: I'll look into it, I have to touch germinate anyway for other stuff13:30
ogra_acwe fixed that in lucid13:30
NCommanderogra_ac: oh, is it more of a question "do we want to exclude it?"13:30
* GrueMaster shudders at the QA implications of OO.o on the images.13:30
ogra_acNCommander, right13:30
ogra_acNCommander, and accroding to davidm we dont want OO.o13:30
NCommanderGrueMaster: we'll have to sacrifice one of the bodies to keep the beast happy13:30
davidmand we don't want mono apps13:31
ogra_acwe need to take care for OO.o anyway13:31
ogra_acif its on the images or not13:31
davidmseperate problem but a problem non the less13:31
ogra_acso i dont see the issue why it matters if we have it on the desktop images13:31
NCommanderIf there is no contractual requirement for Canonical-provided images, and if there's no demand for it on community-provided images, then I'm happy to leave it off13:31
NCommanderogra_ac: out of site, out of mind ;-)13:31
ogra_acNCommander, we still need to take care for it13:31
NCommanderogra_ac: although granted, with the migration to libreoffice, at least we can drop most of the patches since we won't have issues with upstream13:32
ogra_acits a main app we are bound to make sure works13:32
NCommanderogra_ac: yes, but if its on the image, we have to make sure it works well :-P13:32
* ogra_ac doesnt see much difference between libre and openoffice yet13:32
ogra_aci assume for natty the code wont much differ13:32
NCommanderogra_ac: its more that we won't have issues with getting upstream to accept patches13:32
ogra_acwe always have to make sure it works well13:33
NCommanderSun's upstremaing guidelines were ... painful13:33
ogra_acah, yeah, patching should be easier13:33
NCommanderogra_ac: indeed13:33
NCommanderI'm of leaving it off the images13:33
ogra_aci dont really care13:33
NCommander*for13:33
ogra_aci wouldnt mind having it on desktop images13:33
ogra_acnot on netbook though13:34
NCommanderdavidm: do we care about OOo being shipped? We can exclude it on a per-architecture basis and re-add it on a per image basis (if spice seeds materialize) if we need it13:34
davidmCurrently we are not planning on desktop images13:34
ogra_ac(its not clear yet if we *will* build desktop at all)13:34
ogra_acright13:34
davidmFor ARM netbooks OO was overkill13:34
ogra_acyes13:34
NCommanderogra_ac: I think we should stick a pin in this discussion and only revisit of desktop images materialize13:35
NCommanderdavidm: s/was/is/g13:35
ogra_aci just would like to sick as close to the desktop seed as possible for images13:35
ogra_acNCommander, good idea13:35
NCommanderI think we're all agreed that we're not putting OO.o on the netbook images short of a contractual requirement to do so (or strong community demand which I consider unlikely)13:36
NCommanderBTW13:36
NCommanderIn response to earlier feedback13:36
ogra_acno, no OO.o on netbook, in any case13:36
NCommander[action] NCommander to eBay his soul to fix mono on ARM13:36
MootBotACTION received:  NCommander to eBay his soul to fix mono on ARM13:36
NCommander:-)13:36
ogra_acheh, who would bid on that ?13:36
NCommanderouch.13:36
rsalvetiheheh, true13:36
ogra_acor do you plan a buy now offer ?13:37
rsalvetiand you're brave to try to fix mono13:37
NCommanderWith friends like you, who needs enemies?13:37
NCommander:_p13:37
ogra_acheh13:37
ogra_acwe love you, you know that :)13:37
NCommanderrsalveti: meh. mono isn't a re-implementation of Windows COM. It at least has comments in the code base13:37
ogra_acin any case rhythmbox will stay in the supported set of apps13:38
rsalvetiNCommander: but is a pain :-)13:38
NCommanderogra_ac: all abusers say that :-P *runs*13:38
ogra_acso we can happily go on shipping it13:38
NCommanderrsalveti: I did some work on mono on ARM last time it blew up13:38
NCommanderso I have a general idea of what might be going wrong13:38
rsalvetioh can, I'm happy I'm not the one to fix it13:38
ogra_actomboy is the only mono app we currently have13:38
rsalveti*oh, ok13:38
NCommanderoh crap13:38
NCommanderdamn it13:38
ogra_acin our images13:38
ogra_achmm, and gwibber possibly13:38
NCommanderwhy didn't I drink coffee earlier, I just enlisted for a world of pain :-/13:38
NCommanderogra_ac: we want it fixed anyway :-/13:39
ogra_acwe do13:39
ogra_acthough13:39
NCommandermono been mostly foobar'ed since karmic(?)13:39
ogra_acplease coordinate with linaro13:39
NCommandernone of us could really look into it lucid13:39
ogra_acspecifically with slangasek's team13:39
NCommanderogra_ac: has anyone in linaro looked into it?13:39
ogra_acno, but the linaro platform team cares for such stuff13:39
rsalvetino one is interested, I believe13:39
ogra_acso work together with them13:39
ogra_aci pointed slangasek to it last release, but i think nobody had time over there13:40
ogra_acso i guess they appreciate if you work on it13:40
NCommanderogra_ac: where's the existing mono is broken bug13:40
ogra_acuse their resources if you need to though13:40
ogra_acno idea from the top of my head13:40
ogra_aclet me look that up after meeting13:41
* GrueMaster looks.13:41
ogra_acor that ;)13:41
NCommanderright13:41
NCommanderanyway13:41
NCommandermoving on, I don't want to run over13:41
NCommander[topic] Standing Items13:41
MootBotNew Topic:  Standing Items13:41
NCommander[link] http://people.canonical.com/~pitti/workitems/natty/canonical-arm.html13:41
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/natty/canonical-arm.html13:41
GrueMaster(mono) Bug #56187413:41
ubottuLaunchpad bug 561874 in f-spot (Ubuntu) "NULL Reference exception in F-Spot" [Undecided,New] https://launchpad.net/bugs/56187413:41
NCommander[link] http://people.canonical.com/~pitti/workitems/natty/canonical-arm-alpha-1.html13:41
MootBotLINK received:  http://people.canonical.com/~pitti/workitems/natty/canonical-arm-alpha-1.html13:41
ogra_acdid GrueMaster take the action for fixing the assigned bugs list above ?13:41
ogra_acthe WI list isnt complete yet13:42
ogra_acneeds another tracker run13:42
GrueMasterWill do.  Actually I need to ping marjo for this.13:42
ogra_acGrueMaster, thanks13:42
ogra_acNCommander, action ^^^13:42
NCommander[action] GrueMaster to fix assigned bugs13:42
MootBotACTION received:  GrueMaster to fix assigned bugs13:42
GrueMaster(mono) Bug #61998113:42
NCommanderhrm13:42
ubottuLaunchpad bug 619981 in banshee (Ubuntu Maverick) "Banshee crashed while sitting idle on omap4" [High,Confirmed] https://launchpad.net/bugs/61998113:42
NCommanderThat action item seems like it could be worded better :-)13:42
ogra_aclol13:42
ogra_acwell, i dont mind13:43
ogra_acyou should say "assigned to ubuntu-armel" ;)13:43
GrueMasterYea, and you want them fixed...when?13:43
ogra_acalpha 1 please13:43
NCommanderGrueMaster: tonight preferable ;-)13:43
ogra_ac:P13:43
NCommander[topic] http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html13:43
MootBotNew Topic:  http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html13:43
ogra_acthat will break with the next run13:43
NCommanderk13:43
* GrueMaster increases rent, decreases heat upstairs.13:43
NCommander[topic] Kernel Status (cooloney, mpoirier, lag)13:43
MootBotNew Topic:  Kernel Status (cooloney, mpoirier, lag)13:43
ogra_accanonical-mobile doesnt exist anymore13:44
ogra_acNCommander, that needs cleanup13:44
NCommanderGrueMaster: don't worry, I have all your hatred aimed at me to keep me warm13:44
ogra_acno mpoirier or lag anymore13:44
NCommanderyay, we fixed the issue of lag on the internet!13:44
ogra_acwe moved the lag to linaro ;)13:44
NCommanderthat explains so much13:45
NCommander[topic] QA Status (GrueMaster)13:45
MootBotNew Topic:  QA Status (GrueMaster)13:45
GrueMasterNothing to report.  Checkbox customization is WIP.13:45
NCommander[topic] ARM Porting/FTBFS status (NCommander)13:45
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander)13:45
NCommandernot quite a diaster as when I left on VAC, thanks ogra13:45
ogra_acI don't have time to wait for the right point in the meeting as I'm about to leave here.  I wanted to make sure people knew that Bug #675347 is now the blocker for Qt/KDE stuff on arm and hopefully you can convince someone to fix it soon.13:46
NCommanderOnce Qt is fixed, KDE should just build with a few minor whacks. ScottK is handling this mostly13:46
ubottuLaunchpad bug 675347 in gcc-4.5 (Ubuntu Natty) "volatile int causes inline assembly build failure" [High,Confirmed] https://launchpad.net/bugs/67534713:46
ogra_acfrom ScottK13:46
ogra_ac(he pinged me in PM)13:46
NCommanderogra_ac: thanks13:46
ogra_acso thats one biggie13:46
NCommanderRight, other than that, the list is pretty simple, and not too many ARM specific in main13:46
NCommanderOnce Qt/KDE gets fixed, I'm going to ask for a universe mass-giveback as theirs a lot of breakage there that's just archive skew13:47
ogra_acnothing blocks image builds atm at least13:47
NCommanderindeed13:47
NCommanderso, moving on13:47
ogra_acwe need to look into it nontheless13:47
NCommander[topic] ARM Image Status (ogra, NCommander)13:47
MootBotNew Topic:  ARM Image Status (ogra, NCommander)13:47
ogra_acwe have omap413:47
NCommanderWE HAVE IMAGES! (thanks ogra)13:47
ogra_acfor omap3 the kernel status isnt clear yet13:47
ogra_ac(see my discussion on the MLs)13:48
ogra_acsomeone needs to take security responsibility for omap313:48
ogra_acthen we can use linaros kernel13:48
ogra_acuntil thats clear we wont have omap313:48
NCommander[action] ogra to follow up on omap3 situation with Linaro's kernle team13:48
MootBotACTION received:  ogra to follow up on omap3 situation with Linaro's kernle team13:48
ogra_ac(sorry for the image build mails until then)13:48
rsalvetiactually this needs to be followed with ubuntu's kernel and security team13:49
ogra_acNCommander, has nothing to do with linaros kernel team13:49
ogra_acplease remove that action13:49
NCommanderstriken13:49
ogra_ac(and read the ML thread first :P )13:49
NCommanderogra_ac: I did, I thought Linaro was saying they were going to take the kernel.13:49
ogra_acubuntus kernel and security teams have the ball atm13:49
ogra_acas rsalveti said13:49
NCommanderd'oh13:49
NCommander[action] ogra_ac to follow omap3 kernel situation13:50
MootBotACTION received:  ogra_ac to follow omap3 kernel situation13:50
ogra_acand nobody but manjo answered the thread yet13:50
ogra_ac(with an unrelated comment)13:50
ogra_acthe kernel team is well aware13:50
ogra_aci raised it in their last meeting13:51
ogra_acbut dont have a solution either yet13:51
ogra_acand no manpower13:51
rsalvetiprobably only after getting those 2 new guys around13:51
ogra_acyes13:51
rsalvetiogra_ac: and about the newer guy from our team?13:51
ogra_acno idea when he starts13:52
ogra_acdavidm will know soon i guess13:52
ogra_acand tell us then ;)13:52
rsalvetioh :-)13:52
rsalvetiand just a note, I'll be at vacation next week13:52
ogra_ack13:52
ogra_acslacker !13:52
NCommander[topic] Any Other Business13:52
MootBotNew Topic:  Any Other Business13:52
ogra_aceveryone: finish workitems !13:53
ogra_ac:)13:53
rsalvetiogra_ac: haha, and you'll be forced to be out during december ;-)13:53
ogra_acyeah, i guess13:53
NCommanderanything else13:53
NCommanderwill close in 313:53
NCommander213:53
NCommander1 1/213:53
NCommander113:53
NCommander#endmeeting13:53
MootBotMeeting finished at 07:53.13:53
ogra_acpfft13:53
davidmThanks NCommander13:53
ogra_acyou wasterd 7 min we had13:53
ogra_ac:P13:53
* NCommander whacks ogra_ac 13:54
* GrueMaster considers crawling back to bed for a few hours.13:54
ogra_ac:)13:54
ogra_acdamned13:55
ogra_aci forgot to mention merges13:55
ogra_acplease finish them if you still have any13:55
=== xfaf is now known as zul
keeso/14:56
pittiI sent a SMS to sabdfl, not sure whether he can make it14:56
=== chrisccoulson_ is now known as chrisccoulson
pittiso, no Keybuk, no sabdfl?15:00
cjwatsonI'm here15:01
* Chipaca waves15:01
cjwatsonalbeit swearing at gcc15:01
* thisfred lurks15:02
cjwatsonit's not a good day when I have to grep gcc source15:02
keescjwatson: owchy15:02
* wendar lurks, to answer any ARB-related questions15:03
cjwatsonis mdz expected to be absent?15:03
cjwatsonsabdfl is supposed to be chairing today15:03
pittinot on the holiday calendar, so I suspect meetings?15:05
cjwatsonor timezone confusion ...15:06
pittiso, I volunteer for doing the writeups etc., but we don't think we have a quorum for decisions15:06
pittiTZ> but if at all (UTC based), it would have been an hour earlier15:06
cjwatson3/6 should be quorate15:07
pittiso, let's start15:07
pitti#startmeeting15:07
MootBotMeeting started at 09:07. The chair is pitti.15:07
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:07
pitti[TOPIC] action review15:08
MootBotNew Topic:  action review15:08
pittiColin to ensure that documentation on nature of extras.ubuntu.com archive makes it into process docs, and ensure that ARB legality checks are synchronised with those of ubuntu-archive.15:08
pittiI've seen your recent mail about license checks15:08
pittiso once that gets ack'ed by ARB, it should become part of the official wiki docs15:09
wendarI have a reply in the moderation queue on that15:09
pitticjwatson: is the first part ('nature of extras') something else?15:09
cjwatsonyes, that was an attempt to quickly clear my actions before the meeting15:09
cjwatsonpitti: I added a link to ArchiveAdministration to resolve that15:09
wendarthe intention of the ARB is to synchronize with the ubuntu-archive legality checks15:09
cjwatsonmoderated wendar's mail15:10
pittiwendar: moderated15:10
pitticjwatson: so, let's keep it on the list to check next time?15:11
cjwatsonI was about to say that we no longer needed to carry that action forward :)15:11
cjwatsonbut as you like15:11
pittiok15:11
pittiif the NEW checks were the main point here -> done15:11
pittiMatt to write up Quarterly Brainstorm review and send to TB mailing list15:11
pittithat happened15:11
cjwatsonit sounds like it is already essentially in hand on the ARB side15:11
pittiI have to admit I didn't follow up on that yet15:11
pitti[TOPIC] KDE micro version update exception15:12
MootBotNew Topic:  KDE micro version update exception15:12
pittiScottK: ^15:12
ScottKHello15:13
ScottKLost track of time.15:13
pittiso, http://techbase.kde.org/Policies/Minor_Point_Release_Policy/Draft is a tad more permissive than our SRU policy15:13
ScottKhttps://lists.ubuntu.com/archives/technical-board/2010-November/000525.html is where to start on this.15:13
pittibut pretty much matches what we are doing in SRUs in practice15:14
ScottKIt is.15:14
ScottKWe aren't asking to take all point releases, just ones that we can test and have some confidence are regression free.15:14
ScottKWe currently have KDE 4.4.5 tested and ready for Lucid if we get permission.15:15
pittiFYI, in GNOME we usually deliver .1, selected stuff from .2, and further microreleases only on demand15:15
pittisince the cost/benefit factor quickly gets worse15:15
ScottKWe have been doing these in a PPA and they are very popular.15:15
ScottKAllowing this into the archive would actually reduce our workload somewhat since we'd no longer have to keep an eye on two sets of packages.15:16
pittiScottK: these updates still need to refer to at least one "representative" LP bug where the testing and progress gets documented; does that sound acceptable?15:16
keesI'm fine with it; it's getting even more testing than a usual SRU too15:16
ScottKpitti: Yes.  There are a lot of packages and one bug per package is just confusing to people.15:16
pittithe upstream policy draft and https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy look fine to me as well, I'm just pretty adamant about the LP bug reference with ubuntu-sru@ subscription, since not doing so woudl complicate the SRU process a lot15:18
ScottKI've no problem at all with that.15:18
pittiScottK: oh, you mean you don't want one bug per package?15:18
pittione bug "KDE 4.4.5 for lucid" with all the necessary bug tasks works equally well15:18
pittiif you prefer that15:18
cjwatsonright, it just needs to be something that can be represented on pending-sru.html15:18
pittiwell, it's a bit harder to track for individual package verification15:19
ScottKI'd prefer one bug for the set.  They'll only be moved into -updates as a set and I think it's easier to track.15:19
cjwatsonyeah, the tags don't work right15:19
pittiScottK: ok, then we need to track the component verification in the bug comments, and set it to v-done with the last one15:19
pitti(we can do that in the description)15:19
ScottKThat would be my plan.15:19
ScottKSince done is irrelevant until the set is done.15:20
cjwatsonok15:20
pittino further questions from me, we already discussed that several times15:20
pitticjwatson, kees: further questions/discussions?15:20
cjwatsonno, I'm happy with ths15:20
ScottKYou all saw Mark's resonse on the list, right?15:20
cjwatson*this15:20
ScottKresponse ...15:20
* kees nods15:20
cjwatsonI did, he said +115:20
pitti[VOTE] https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy15:21
MootBotPlease vote on:  https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy.15:21
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot15:21
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:21
pitti+115:21
MootBot+1 received from pitti. 1 for, 0 against. 0 have abstained. Count is now 115:21
cjwatson+115:21
MootBot+1 received from cjwatson. 2 for, 0 against. 0 have abstained. Count is now 215:21
* pitti brings the ballot box to kees15:21
kees+115:22
MootBot+1 received from kees. 3 for, 0 against. 0 have abstained. Count is now 315:22
pitti[ENDVOTE]15:22
MootBotFinal result is 3 for, 0 against. 0 abstained. Total: 315:22
pittiScottK: good end to a looong story :)15:22
ScottKYes.  Thank you everyone.15:22
pitti[ACTION] pitti to link https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy from SRU page15:22
MootBotACTION received:  pitti to link https://wiki.kubuntu.org/Kubuntu/UpdatesPolicy from SRU page15:22
ScottKI'll modify the UpdatesPolicy to mention how to do the bug tracking for the SRU.15:23
pitti[TOPIC] couchdb lucid backport SRU15:23
MootBotNew Topic:  couchdb lucid backport SRU15:23
Chipacahi15:23
pittiChipaca:15:23
Chipacai sent a second email because the first one was broken (?)15:23
Chipacabut maybe you got it ok15:23
cjwatsonwe got both :)15:24
pittifirst one went through, too15:24
Chipacathe archive mangled the first, or my mua did :)15:24
pittiI can't approve this under the normal SRU policy, so this requires an exceptio15:24
pittin15:24
cjwatsonwhere is the upgrade procedure implemented?15:25
pittiChipaca: the thing I don't understand is how the lucid version coudl suddenly get incompatible with our cloud servers?15:25
pittidid we change our server API and knowingly break lucid clients?15:25
keesso, just to certain, this is a one-time exception, not a standing exception?15:25
Keybukargh, sorry15:25
pittihey Keybuk, welcome15:26
Chipacakees: yes, one time15:26
Keybukmy calendar is completely screwed and just gave me the alarm for the TB meeting15:26
Keybuk*hate timezone issues*15:26
Chipacapitti: we had to upgrade the servers for several of the issues fixed by the newer ones15:26
pittiChipaca: so I guess by doing this you pretty much forced the upgrade on lucid15:27
* cjwatson looks at https://launchpad.net/~ubuntuone/+archive/stable to see if he can discover the answer to his question above15:27
Chipacapitti: without the fix, it didn't work on anything15:27
pittibut 0.10->1.0 changes are very extensive, so for the same reason why we can't backport patches that version jump also has a high regression potential for current lucid users15:27
Chipacapitti: so it was either don't work on nothing, or work on only maverick15:28
pittiI see that you did extensive testing, which mitigates this concern quite a bit15:28
cjwatsonalso, is this only the couchdb package, or also the many other packages in ~ubuntuone/stable?15:28
ScottKIt could go in lucid-backports.15:28
pittiChipaca: it didn't work at all on lucid when we released?15:28
james_whow has the problem that all your data "disappears" with the upgrade been handled?15:28
cjwatsonScottK: if it's actually broken in lucid right now ("it" being U1 I suppose) then I'm not sure -backports is appropriate; seems like more than new features15:29
Chipacacjwatson: only couchdb15:29
cjwatsonChipaca: and that was tested in isolation from the other stuff in the PPA?15:29
thisfredpitti: It worked but not under increasing load, it just didn't scale15:29
ScottKcjwatson: Agreed.  Just suggesting that as an alternative if -updates was deemed not suitable or risky.15:29
pittimy main concern is here that couchdb isn't just used for U115:30
Chipacacjwatson: yes, just the couch packages15:30
pittiand we indeed promote it more and more for quickly apps, etc.15:30
pittiso if it introduces any incompatibility with the unknown set of programs, we will get a very easy data loss regression15:30
cjwatsonok, so I can't quickly find the answer to my question from the source - where is the data upgrade procedure implemented?  is it in a maintainer script, or is it just when you load the file in couchdb?15:31
Chipacathat's a question for thisfred i think, but AFAIK the incompatibility only really affects replication15:31
thisfredcjwatson: yes opening an existing db in couchdb migrates it. This is a one way process, unfortunately15:32
cjwatsonright, I just wanted to know that it wasn't in maintainer scripts15:32
cjwatsonI'm more comfortable with it in couchdb itself, since doing this in maintainer scripts can be hard to get right15:32
* kees nods15:32
thisfredThere aren't many API changes, mainly new API rather than removal or change of behavior of existing API. Replication was fixed so that it works better over SSL, but the calls are still the same.15:33
pitti(or impossible, with desktopcouch and per-user instances)15:33
cjwatsonquite so.15:33
pittithisfred: ah, so the main trap here is shared home directories over the network, where some clients upgrade to 1.0, and some not (yet); the latter then coulnd't access the DB any more, right?15:34
thisfrednope15:34
james_wI think the proposed change may have a poor user experience. couchdb uses versioned directories for the databases, so on upgrade all your data appears to vanish. Anything u1 synced would then probably be re-downloaded rather than using the local version, and any local databases will be inaccessible until they are migrated manually.15:34
thisfredpitti what it sends over the wire is json, not the dbs, so it would be happy to replicate against a 0.10 db locally, as long as it's not over SSL which was badly broken.15:35
thisfredpitti sry misread that15:35
pittithisfred: "the wire" also includes local apps? they just talk over the localhost TCP port?15:35
thisfredpitti: yes shared home directories would not work for the 0.10 clients15:35
thisfredpitti: they would error until they upgraded to 1.0.x as well15:36
pittijames_w: where does it appear vanished then? I thought couchdb would auto-upgrade it on demand?15:36
=== dholbach_ is now known as dholbach
james_wpitti, that wasn't my experience15:37
thisfredonce a db is in 1.0 format it can't be read by 0.10 any more, is the short of it15:37
james_wpitti, see README.Debian15:37
thisfredjames_w: the versioned data directories is true, but not for anything synced with u1, since those dbs live in users' home directories15:38
cjwatsonREADME.Debian: http://paste.ubuntu.com/533059/15:38
thisfredI wish couchdb didn't do that15:38
cjwatsonthisfred: ok, but we have other things using couchdb15:38
thisfredright15:38
pittithisfred: we need to be concerned about general database useage here, though, not just u115:38
james_whas the server team been consulted?15:39
thisfredI know15:39
cjwatsonis it worth considering an ubuntuone-couchdb temporary fork?15:39
cjwatsonjust for lucid15:39
pitticjwatson: nice idea15:39
pittithen we could change lucid's u1 packages to use that instead?15:39
cjwatsonor maybe couchdb-1.0 would be a better name15:39
cjwatsonYKWIM though15:39
Chipacai'd call it couchdb-ssl :)15:39
Chipacayeah15:39
thisfredShould be doable15:39
pittiquestion is what to do with desktopcouch then15:40
cjwatsonI'm not familiar enough with that to be able to comment15:40
pittithisfred: I take it we couldn't leave desktopcouch to use the 0.10 version?15:40
thisfredpitti: I think the old desktopcouch would continue working, this was tested15:41
thisfredso that doesn't need an SRU15:41
keesit'd be nice to not fork, since there are outstanding CVEs in couchdb...15:41
thisfredAFAIK15:41
pittithisfred: but wouldn't the per-user DBs have the same per-version directory probleM?15:41
keeshttp://people.canonical.com/~ubuntu-security/cve/pkg/couchdb.html15:41
MootBotLINK received:  http://people.canonical.com/~ubuntu-security/cve/pkg/couchdb.html15:41
cjwatsonkees: I know, but the tension seems hard to break15:42
thisfredpitti: no they don't they live in userland, and don't have this issue15:42
pittithisfred: could you extend your wiki page to point out the consequences for system-wide couchdb, per-user couchdb instances, and how to retain full API compatibility with quickly apps, so that we can revisit that next time?15:43
thisfredWell, we'd have to change its dependency in case of a temporary fork of course15:44
pittimy feeling is that we don't yet have enough confidence in this15:44
thisfredpitti: will do15:44
pittiI'll keep it on the agenda for revisiting in two weeks15:44
pittithisfred: thanks15:44
cjwatsonI'd be grateful if somebody could at least explore the fork suggestion and see how well it works out; I expect there are a number of small issues to solve there15:44
thisfredquickly uses desktopcouch btw, so since desktopcouch works, quickly apps should also15:45
thisfredif they don't poke through the API15:45
pittithisfred: right, but I'm not quite clear what kind of changes we'd need to do to desktopcouch if we have a counchdb and couchdb-1.0 pacakge in lucid15:45
thisfredpitti: yeah, it would be the dependency and the startup machinery, at least (and at most, I think)15:46
pittiif we left desktopcouch to use 0.1, then we still wouldnt' have replication, and thus miss what you try to do for U1, or did I misunderstand?15:46
thisfredthat is correct15:46
thisfredno replication to U115:46
pittiwell, since we didn't have that ever in lucid, this doesn't seem like a pressing issue to me15:47
pittibut the security issues seem more worthwhile to consider15:47
thisfredwe did, until the 0.10 couch on the server buckled under the load15:47
pittithisfred: this is just for contacts etc. sync, not for U1 file sync, right?15:47
thisfredpitti: correct15:48
keesthey're low, except for 1 medium which doesn't apply to desktopcouch (just the not-installed-by-default server side)15:48
Chipacaright, so no contact sync, no bookmarks sync, no notes sync15:48
thisfrednotes sync is special15:48
pittiChipaca: perhaps you can add some more details about the affected servicese as well, and which ones actually regressed15:48
thisfredso yes notes sync15:48
Chipacathisfred: right, no notes sync *back*15:48
pittiChipaca, thisfred: so, can we reiterate that in two weeks, and extend the wiki pages with above info, and explore the feasibility of a couchdb-1.0 package? that okay for you?15:49
Chipacawe can work with that15:50
thisfredyep15:50
pittiok, thanks15:50
Chipacait's not *ideal*, but, yes15:50
pitti[TOPIC] ARB exception proposal - Allison Randal15:50
MootBotNew Topic:  ARB exception proposal - Allison Randal15:50
pitti[LINK] https://wiki.ubuntu.com/PostReleaseApps/MaverickExceptionsProposal15:50
MootBotLINK received:  https://wiki.ubuntu.com/PostReleaseApps/MaverickExceptionsProposal15:50
pittiwendar: some questions to that15:51
pittiwendar: how many python libraries" do such packages actually ship?15:52
pittithe odd mini application should presumably only use private libraries or just programs?15:52
wendarthey shouldn't ship any general-purpose libararies, only private libraries15:52
pittimy main concern there would be namespace clobbering/shadowing15:53
pittiwendar: private libraries coudl live in the app directory, as long as the program sets sys.path properly, couldn't they? or is that impractical for some reason?15:53
wendar(on namespace clobbering) yes, the suggestion there is to require the libraries to use a subpath "extras"15:53
wendar(on sys.path) the applications can run fine, but the packaging tools can't generate the .pyc files15:54
cjwatsonthis may be bikeshedding, but the mentions of /opt/extras looked odd to me15:54
pitti.pyc isnt' strictly required, though15:54
cjwatsonI realise it's probably because you don't know all the paths in advance15:54
cjwatsonthere's a technique in man-db which might help - infer the paths you need from $PATH15:55
cjwatsoni.e. if /opt/foo/bin is on $PATH then you want /opt/foo/site-packages or whatever15:55
cjwatsonis that practical?  I'm not sure how you arrange for things in /opt to be executd15:55
cjwatson+e15:55
wendarcjwatson: the idea there is to pick some unique path under /opt for all applications, before the package name15:55
cjwatsonright, it's just kind of contrary to the way /opt is normally used and has essentially the same potential conflict problems as putting things in /usr15:56
pittiwendar: hm, usually they should use /opt/<appname>?15:56
cjwatsonthe idea of /opt is to have everything have a completely separate tree, and I wanted to explore whether that could be preserved15:57
cjwatsonfor example things could iterate over all subdirectories of /opt, if inferring from $PATH isn't feasible15:57
pittiI think we can probably make an exception for maverick to put desktop files under /usr/local/share/applications/15:57
cjwatsonI realise it's sort of nitpicking, just wanted to see if we could get this right from *cough* nearly the start15:57
pittito avoid heavy patches to many libraries to also consider /opt/*15:57
cjwatsonpitti: agreed15:57
pittithe "python binaries" should be mostly a non-issue IMHO15:58
wendarfrom the FHS: /opt/<provider>/<appname> is the other option (to further protect the general namespace)15:58
cjwatsonoh, huh15:58
pittithe .desktop file will point to the right path, and that's mostly what we are interested in15:58
wendarso we're looking for a unique "provider"15:58
pittiso I think the main concern are the python libs here15:58
cjwatsonwendar obviously knows the FHS better than I do15:58
wendarwe first suggested "SoftwareCenter", but that doesn't seem to fit with the general naming scheme for providers15:59
cjwatsonwell, you're supposed to register things with the LANANA, per the FHS15:59
cjwatsonif that's still operating ...15:59
cjwatsonit was H. Peter Anvin last I checked15:59
keesadding the glue for things in /usr to use /opt seems silly -- just use /usr. The whole point of /opt was to keep things separate.15:59
pittiwendar: for maverick, could we fix quickly to automatically add the binary's directory to sys.path, and ask app authors to do the same?16:00
cjwatsonLANANA provider list last changed 2010-11-0516:00
wendaryes, we should register, once we settle on a name16:00
=== jj-afk is now known as jjohansen
cjwatsonhttp://www.lanana.org/lsbreg/providers/providers.txt16:00
MootBotLINK received:  http://www.lanana.org/lsbreg/providers/providers.txt16:00
pittikees: for desktop files?16:00
cjwatsonexamples of names16:00
cjwatsonhow about just /opt/ubuntu then?16:00
keespitti: right, it seems like .desktop would live in /usr and the core would be in /opt16:00
pittikees: it shouldn't be the final solution of course, but I think for maverick it'd be an acceptable compromise; you don't?16:01
pittiafter all, these packages still get a review for sanity16:01
cjwatsonNo other package files may exist outside the /opt, /var/opt, and /etc/opt16:01
keespitti: yeah16:01
cjwatsonhierarchies except for those package files that must reside in specific16:01
cjwatsonlocations within the filesystem tree in order to function properly. For16:01
cjwatsonso the FHS does have a get-out clause16:01
cjwatsonexample, device lock files must be placed in /var/lock and devices must be16:01
cjwatsonlocated in /dev.16:01
cjwatsonI dunno though, I feel that if we used that get-out too much there's precious little point in using /opt at all16:02
cjwatsonso I'd like us to have at least some glue16:03
pittiI'd really avoid that for python libs16:03
cjwatsonyes16:03
wendarcjwatson: /opt/ubuntu would work, if you're comfortable with possible namespace collisions between some other (potential future) apps using the same namespace (nothing uses it now, so it's safe)16:03
* SpamapS coughs and looks over at the clock16:03
robbiew:)16:04
pittiSpamapS: you have a meeting here now?16:04
SpamapSme? no not me.16:04
kirklandpitti: server team meeting16:04
pittioops16:04
cjwatsonwendar: you mean other apps in extras.u.c?16:04
SpamapSjust coughing, wondering what time it is. ;)16:04
robbiewpitti: no worries...recent move ;)16:04
pittiwendar: so, seems we have to move that to email16:04
pittiwendar: I'll summarize the discussion here and reply to your mail16:05
pittiwendar: and we can pick it up again next time if needed (or resolve by email)16:05
ScottKSince these apps are specifically not part of Ubuntu, that namespace choice seems odd.16:05
ScottKwendar: ^^^16:05
* pitti taps gavel, need to wrap up16:05
pittithanks everyone!16:06
pitti#endmeeting16:06
MootBotMeeting finished at 10:06.16:06
pittirobbiew, kirkland: sorry for running over16:06
robbiewpitti: np16:07
kirklandpitti: ;-)16:07
SpamapSactually your discussion was probably a lot more interesting than what we're going to discuss.. ;)16:07
hallyn(oh my, quitting mumble just killed my unity sidebar)16:07
smbhallyn, You shall not leave unpunished16:08
SpamapSlol16:09
hallynsmb: for not running wmii?  :)16:09
smbhallyn, Just for trying to leave that lovely mumble arena16:09
hallynyeah, i always hate to do it16:10
zulhave we started yet?16:10
hallynno16:10
SpamapSDaviey: I think you have the honors sir.16:11
robbiewno...who's chairing this week?16:11
hallynis Daviey running the show?16:11
JamesPagewho's up for chair this week?16:11
robbiewah16:11
SpamapSrobbiew: feel free to throw yourself into the chair/scribe list for great happiness.16:11
robbiewSpamapS: no thanks...I have enough busy work as it is ;)16:12
hallynDaviey: around?16:12
smoserso, we do have a meeting16:12
smosercool16:12
zulhow convient :016:12
hallyn(one last ping) Daviey ?16:13
hallyn#startmeeting16:13
MootBotMeeting started at 10:13. The chair is hallyn.16:13
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]16:13
hallynTOPIC Review ACTION points from previous meeting16:13
hallyn#TOPIC Review ACTION points from previous meeting16:13
hallyn[TOPIC] Review ACTION points from previous meeting16:13
MootBotNew Topic:  Review ACTION points from previous meeting16:13
hallynmathiaz: to verify SRU bug 66602816:14
ubottuLaunchpad bug 666028 in openldap "apt-get install slapd => Can't locate object method "new" via package "Debconf::Element::Noninteractive::Booleam"" [Undecided,New] https://launchpad.net/bugs/66602816:14
hallynmathiaz isn't here though.  carry over?16:14
SpamapSindeed16:15
* hallyn feels lonely16:15
hallynmoving on,16:15
JamesPageNot sure whether mathiaz did this but it has been verified16:15
hallynALL: please check the SRU tracker for verification-needed bugs and help out with verification16:15
hallynJamesPage: oh, ok, thanks16:15
SpamapSThere are 2 bugs needing verification in the SRU tracker right now16:15
hallynso, i've personally done more to add sru requests than verify them this week, i'm afraid16:15
SpamapSThe unassigned list is .. crazy though16:16
SpamapSSeems like we could all stand to attack the lucid ones with a vengance before 10.04.216:16
hallynwhich is when exactly?16:16
zulsoon i think but robbiew has a probably better idea16:17
SpamapSJanuary 2716:17
kirklandhttps://wiki.ubuntu.com/LucidReleaseSchedule16:17
robbiewfyi - the dates are tentative ;)16:17
hallynSpamapS: for simplicity, do you have a link to the sru tracker?16:17
hallyn(simplicity, and for the logs)16:17
SpamapShttp://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html#verified_bugs16:18
MootBotLINK received:  http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html#verified_bugs16:18
hallyncool, so i recon' we carry that one over?16:18
SpamapSYes indeed.16:18
robbiewso is this link obsolete: https://wiki.ubuntu.com/ServerTeam16:18
hallyn[ACTION] ALL: please check the SRU tracker http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html#verified_bugs and help out with verification16:18
MootBotACTION received:  ALL: please check the SRU tracker http://people.canonical.com/~chucks/SRUTracker/sru-tracker-bugs.html#verified_bugs and help out with verification16:18
robbiewhttps://wiki.ubuntu.com/ServerTeam/SRUTracker16:18
robbiewthe 2nd one...1st isn't...hopefully :P16:19
SpamapSI've not seen that wiki page until just now.16:19
SpamapSwas that manually maintained?16:20
robbiew[ACTION] robbiew to review /ServerTeam wiki16:20
robbiew:)16:20
zulrobbiew: yeah that one is *really* old16:20
hallyn[ACTION] robbiew to review /ServerTeam wiki16:20
MootBotACTION received:  robbiew to review /ServerTeam wiki16:20
hallynwhich is really old?16:20
zulthe ServerTeam/SRUTracker16:20
hallynhm. ok. good to know, thx16:20
hallynany more need to be said about sru's?16:21
hallyn(last week we deferred a conversation about making them a daily activity)16:21
hallynall right then, moving on16:22
hallynSpamapS: change kernel team representative from jjohansen to smb in meeting agenda going forward16:22
SpamapSlets have that SRU talk during Open Discussion16:22
hallynok16:22
SpamapShallyn: done16:22
hallynrobbiew: update the fridge calendar with new ubuntu server meeting time16:22
hallyn(i saw this morning that was done :)16:22
hallyn(as i looked in a panick for the right time)16:22
hallynhggdh: contact Ubuntu Developers asking for packages which run test suites during build.16:22
hggdhdone -- I asked in devel-discuss. My track record for having emails accepted in -devel sucks16:23
hallynhaha, yeah easy way to feel rejection16:23
hallynthanks16:23
hggdhI got some more packages to build, and they are already on the process16:23
hallyn[TOPIC] Natty Development16:24
MootBotNew Topic:  Natty Development16:24
hallynanything to discuss here?16:25
=== You're now known as ubuntulog
robbiewoh16:25
robbiewso I'm reviewing/approving blueprints16:25
SpamapSyou said that last week. ;)16:26
robbiewyep16:26
robbiewit's a slow process16:26
hallynrobbiew: is it safe to say that if we should be worried, you'd have talked to us by now?16:26
robbiewespecially when folks are missing work items and milestone targets ;)16:26
robbiewnothing to worry about16:26
robbiewit's a fluid process anyway16:26
robbiewI could approve every single one16:27
robbiewbut we know they won't all be done16:27
robbiew:)16:27
hallyn\o/16:27
robbiewmy main focus is on eliminating work we KNOW we can't do16:27
robbiewand prioritizing the res16:27
robbiewrest16:27
SpamapSits basically whether you crush our dreams now, or the work crushes them later.16:27
robbiewso we know what to drop come review in Alpha 2 and Alpha 316:27
robbiewwelcome to time-based releases !16:27
hallynSpamapS: except this lets us stay excited awhiel longer :)16:27
robbiewSpamapS: the priority of the blueprint will indicate dream-crushing probability :P16:28
SpamapShallyn: its like wrapping up hunks of coal for christmas..16:28
robbiewas I'm out next week...I hope to have it all sorted by Friday16:28
robbiewespecially since the 1st release mtg is quickly approaching16:28
* SpamapS resolves to submit his remaining 3 BP's for review today16:29
robbiewand I don't want skaet to kick my ass ;)16:29
skaet:)16:29
SpamapSskaet: aim for the knees16:29
robbiewhallyn: that's it from me16:29
hallyncool, thanks16:29
hallyn[TOPIC] Maverick SRUs16:29
MootBotNew Topic:  Maverick SRUs16:29
hallynBug 661547 - Existing patch gssapi.diff makes guess_service_principal produce garbage16:29
ubottuLaunchpad bug 661547 in openldap (Ubuntu) "Existing patch gssapi.diff makes guess_service_principal produce garbage" [High,Triaged] https://launchpad.net/bugs/66154716:29
* hallyn picks someone at random to point to16:30
hallynzul: ^16:30
JamesPagePending release of bug 666028 which is holding things up16:30
ubottuLaunchpad bug 666028 in openldap "apt-get install slapd => Can't locate object method "new" via package "Debconf::Element::Noninteractive::Booleam"" [Undecided,New] https://launchpad.net/bugs/66602816:30
* smoser will have BPs submitted for approval also16:30
hallynJamesPage: ah, thanks16:30
hallynJamesPage: any estimated resolution date on that?16:31
zulhallyn: ack16:31
JamesPagepatched version had been verified so now pending release16:31
hallyn<nod>  thanks16:32
hallynBug 657149 - squid fails to upgrade (incomplete)16:32
ubottuLaunchpad bug 657149 in squid (Ubuntu) "package squid 2.7.STABLE9-2ubuntu5 failed to install/upgrade: subprocess installed post-installation script returned error exit status 1" [High,Incomplete] https://launchpad.net/bugs/65714916:32
hallynuh, i'll try that again:  zul ^  :)16:33
zulhallyn: *sigh*16:33
SpamapShow is that an SRU for maverick at this point? It still doesn't even look Confirmed16:33
hallynso it should be taken off that list?16:33
zulyes its incomplete16:34
hallynall right, will pull that from the list for next mtg16:34
hallynBug 658227 - openldap fails to upgrade (in -proposed)16:34
ubottuLaunchpad bug 658227 in openldap (Ubuntu Natty) "upgrade process does not upgrade underlying BDB format from 4.7 to 4.8 (so slapd aborts with "Program version 4.8 doesn't match environment version 4.7" error message)" [High,Fix released] https://launchpad.net/bugs/65822716:34
hggdhit should. And it has not even been nominated16:34
JamesPagehallyn: 658227 released to -updates16:35
hallynanything needed for lucid on that?16:35
hallynoh no - i think coffee shop lady is about to reset my connection16:35
hallynall right so 658227 i'll take off the list too16:36
hallynBug 660227 - php5-pgsql crash on getting an error back from postgres (in -proposed)16:36
ubottuLaunchpad bug 660227 in php5 (Ubuntu) "php5-pgsql crash on getting an error back from postgres" [High,Fix released] https://launchpad.net/bugs/66022716:36
hallynfix released in maverick - remove from list?16:36
zulyes16:37
hallynBug 600174 - axis2c fails to build from source on maverick/i38616:37
hallyn(last one)16:37
ubottuLaunchpad bug 600174 in axis2c (Ubuntu Natty) "axis2c fails to build from source on maverick/i386" [High,Confirmed] https://launchpad.net/bugs/60017416:37
hallynnot fix released in natty...16:37
hallynnot viable for sru?16:37
SpamapSI wonder if we need to keep handling Maverick SRU's in the meeting after this meeting?16:38
hallynSpamapS: ?16:38
zulhallyn: its not a viable SRU16:38
hallynzul: thanks.  will pull that one as well16:39
SpamapSI think the reason they were discussed was to handle the OMG bugs that needed fast turn around after the release. We're over a month out.. they should probably join lucid bugs in the big SRU list.16:39
hallynsounds good to me.  let's discuss in open discussion16:39
robbiewSpamapS: agree...also (fwiw) skaet plans to have a bi-weekly meeting to cover SRUs16:39
robbiewseparate from the weekly release meeting16:39
hallynoh, that'd be good.  where will it be announced?16:39
SpamapSsign me up16:39
skaetyup.   email will be oming out soon...16:39
hallynditto16:39
hallyncool, thanks16:40
hallynmoving on16:40
hallyn[TOPIC] Weekly Updates & Questions for the QA Team (hggdh)16:40
MootBotNew Topic:  Weekly Updates & Questions for the QA Team (hggdh)16:40
hggdhI am starting to work with zul to take over part of the SRU process16:40
zulyay!16:40
hallyn:)16:41
hggdhapart from that, finishing up my own BPs, and starting to work on them. No news, except we will try to review the current bug management process16:41
hallynany questions for hggdh ?16:41
hallynmoving on, then16:42
hallyn[TOPIC] Weekly Updates & Questions for the Kernel Team (smb)16:42
MootBotNew Topic:  Weekly Updates & Questions for the Kernel Team (smb)16:42
smbI had prepared a list of bugs currently on our radar with comments. Since16:42
smbthose are a few I am wondering whether I should bore everybody by quickly16:42
smbgoing over all of them or try to make a best of?16:42
SpamapSsmb: I'd be interested in any that you need feedback/testing on.16:43
hallynand i'd be interested in any you're working on, i think (might end up affecting me)16:43
smosersmb, if you have prepared list, pastebin it16:43
hallynthat smoser, always thinking16:43
smoserand then give us the greatest-hits16:43
smbHm, there would be mostly one for ext416:43
smbok, a second16:43
=== You're now known as ubuntulog_
* smoser finds it almost annoying how always prepared smb is :)16:44
hallynsmoser needs more annoying neighbors or something16:44
=== You're now known as ubuntulog
smbhttp://pastebin.ubuntu.com/533098/16:44
MootBotLINK received:  http://pastebin.ubuntu.com/533098/16:44
smbFor a lot of things I am finding myself wondering whether there could be any setup that would give us a dom0 similar to amazons16:45
hallyncrimey longer list than i expected :)16:45
smbhallyn, It just the many non-commiting comments16:46
hallynsmb: so which ones of those did you defiantely want to discuss?16:46
smosersmb, well, you can crawl logs and see reported xen versions16:46
smosersomewhat consistent results can be found with centos 5.X (where X is variable)16:47
smbI guess the one that might be about loosing interrupts, but iirc nobody from us could recreate the problems there16:47
smoserbut many of hte ones that are hitting us now are race and or new-hardware16:47
hallynsmb: purely out of curiosity - for suspected kernel bugs involving bridging, who would likely end up being assigned?16:47
smbhallyn, If it looks any server related I seem to be the point of dumping lately16:48
smbhallyn, Though I probably try to get advice from tgardner on networking stuff16:48
hallynsmb: thanks16:49
smoserso, smb, my comments on above. lines 1-3, thank you thank you thank you.16:49
hallynis everyone still following the links, or does noone have further questions for smb?16:49
smoserbug 614853, for 10.04, on 'linux-ec2' (which is no longer active), i really would like a solution, and am not terribly concerned about it being a hack.16:49
ubottuLaunchpad bug 614853 in linux-ec2 (Ubuntu) "kernel panic divide error: 0000 [#1] SMP" [Medium,Confirmed] https://launchpad.net/bugs/61485316:49
smosermaybe we should just put a BUG_ON statement there, so if we see fallout later we'll see messages in the console log that this was possibly related16:50
smbsmoser, i think jj wanted to look into the chance of upstream16:50
smbWanted to ask him today, but he had power issues earlier on as well16:50
smoserah. ok. we'll i'll leave you to it.16:50
* hallyn chuckles at the patch16:51
smoseryeah16:51
hallyni wouldn't call that a hack, per se...16:51
hallynany action for that bug then?16:51
smbOnly because apparently those values should never be zero16:51
smbSo I heard the checks just avoid the problem16:51
smbor hide it16:52
smbpersonally I would not care as long as there is no real solution and the system does not crash anymore16:52
smbI guess thats all so far16:52
hallynif someone cares they can trace where avg_load gets set to 0 :)16:52
hallynok, any more q's for smb?  going once...16:52
smosersmb, so i guess i should poke at the natty boot bug16:53
smoseras we really really want to have that fixed by alpha116:53
hallynsmoser: which # is that?16:53
smoseras we'd like to have an alpha that does more than send amazon money16:53
smoserhttps://bugs.launchpad.net/ubuntu/+source/linux/+bug/66949616:53
smbsmoser, It feels likesomething crashes very early on. But without seing anything its hard to say16:53
smoserwell, yeah, other than there are messages in those logs. something goes amuck in kernel and it remounts ro16:54
smbsmoser, We probably should clarify when there are messages or not. The t1.micro did not produce anything for me16:54
smbAnd the larger instance just booted fine16:55
smoserwell, running natty kernel on maverick user space is less an immediate concern16:55
smoserthan running natty kernel and natty user space16:55
* SpamapS coughs... and looks at the clock ... again16:56
smoserin natty-natty, we get kernel messages in all cases (as far as I understood)16:56
hallynany actions?16:56
hallyn[TOPIC] #16:56
hallyn#16:56
MootBotNew Topic:  #16:56
SpamapSseems like you guys should continue this discussion in #ubuntu-(devel|server|?)16:56
hallynWeekly Updates & Questions for the Documentation Team (sommer)16:56
hallyndoh16:56
hallyn[TOPIC] #16:56
hallyn#16:56
MootBotNew Topic:  #16:56
hallynWeekly Updates & Questions for the Documentation Team (sommer)16:56
hallyngrr16:56
* SpamapS likes # cake16:57
hallyn[TOPIC] Weekly Updates & Questions for the Documentation Team (sommer16:57
MootBotNew Topic:  Weekly Updates & Questions for the Documentation Team (sommer16:57
smoserthanks smoser16:57
smoserthanks smb16:57
SpamapSsommer's not here again16:57
hallynsommer is not here16:57
hallyn[TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)16:57
MootBotNew Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)16:57
smbsmoser, Damn completion. ;-)16:57
hallynkim0 is not here16:57
hallyn[TOPIC] Open Discussion16:57
MootBotNew Topic:  Open Discussion16:57
zuli still like turtles16:58
hallynSpamapS: you wanted to bring something up?16:58
SpamapSCan we discuss doing SRU verification and/or assignment on bug triage days? Seems like we're getting *way way way* behind on the SRU list.16:58
Davieyack16:58
hallynSpamapS: in the one sru tracker list, i only saw two pending...16:58
SpamapShallyn: for verification yes16:59
hallynSpamapS: for me, what i'm behind on is actually nominating kvm bugs for lucid sru!16:59
hallynsorry to say16:59
DavieySpamapS: With much of the team being at UDS, and the event last week - i imagine many of us are behind on our duties for thaty16:59
SpamapSbut I mean the actual unassigned bugs accepted for a release16:59
zulSpamapS: its also that way so the community can get involved that way as well16:59
hallynSpamapS: do you want to come up with a concrete proposal?16:59
hallyn(since we're out of time) and email it?16:59
Davieysounds like a good starting point!!17:00
hallyn[ACTION] SpamapS to email a concrete proposal for addressing SRU verification backlog17:00
MootBotACTION received:  SpamapS to email a concrete proposal for addressing SRU verification backlog17:00
SpamapSYeah I'll email ubuntu-server with my ideas.17:00
hallyncool, thanks17:00
hallynanything else to discuss?17:00
hallyn[TOPIC] Announce next meeting date and time: Tuesday 2010-11-23 at 1600 UTC - #ubuntu-meeting17:00
MootBotNew Topic:  Announce next meeting date and time: Tuesday 2010-11-23 at 1600 UTC - #ubuntu-meeting17:00
hallynthanks, all17:00
hallyn#endmeeting17:00
MootBotMeeting finished at 11:00.17:00
SpamapShallyn: thanks!!17:00
Daviey\o/17:01
kirkland\o/17:01
SpamapSM17:02
skaetthanks!17:02
SpamapSC17:02
SpamapSA17:02
bjf#startmeeting17:03
MootBotMeeting started at 11:03. The chair is bjf.17:03
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:03
smb\o17:04
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting17:04
bjf[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick17:04
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting17:04
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick17:04
ckingo/17:04
bjf#17:04
bjf# NOTE: '..' indicates that you are finished with your input.17:04
bjf#17:04
JFoo/17:05
sconklin\o/17:05
bjf[TOPIC] ARM Status (bjf)17:05
bjf* TI - They are still stabilizing 2.6.35 based kernel for omap4. And they will probably skip 2.6.36 and move to 2.6.37 directly, but it won't happen before December.17:05
bjf..17:05
MootBotNew Topic:  ARM Status (bjf)17:05
smbJFo, Long time no see :)17:05
JFo:)17:05
=== yofel_ is now known as yofel
bjf[TOPIC] Release Metrics (JFo)17:06
MootBotNew Topic:  Release Metrics (JFo)17:06
JFoRelease Meeting Bugs (0 bugs, 12 Blueprints)17:06
JFo==== Alpha 1 Milestoned Bugs (14 across all packages) ====17:06
JFo * 0 linux kernel bugs (no change)17:06
JFo * 0 linux-fsl-imx51 bugs (no change)17:06
JFo * 0 linux-ec2 bugs (no change)17:06
JFo * 0 linux-mvl-dove bugs (no change)17:06
JFo * 0 linux-ti-omap bugs (no change)17:06
JFo * 0 linux-meta-ti-omap bug (no change)17:06
JFo==== Release Targeted Bugs (86 across all packages) ====17:06
JFo * 3 linux kernel bugs (no change)17:06
JFo * 0 linux-fsl-imx51 bugs (no change)17:06
JFo * 0 linux-ec2 bugs (no change)17:06
JFo * 0 linux-mvl-dove bugs (no change)17:06
JFo * 0 linux-ti-omap bugs (no change)17:06
JFo * 0 linux-meta-ti-omap bug (no change)17:06
JFo==== Milestoned Features ====17:06
JFo * 1 blueprints (Including HWE Blueprints)17:06
JFoThis number is wrong. The only blueprint I see on the list is mine.17:06
JFo==== Bugs with Patches Attached:138 (up 14) since the last meeting 1 month ago ====17:06
JFo * [[https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on | Bugs with Patches]]17:06
JFo * [[http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/ | Breakdown by status]]17:06
JFoAs these are now one of my main focus points. I will begin working specifically on them this week.17:06
JFoThe goal is to beat this number back to zero and then maintain as close to that as possible going forward.17:06
JFoI'll be asking some of you to review bugs as needed to assess their viability and to improve my work on the overall17:06
JFolist over time. Once I have the hang of it, I hope to submit those patches that make sense to the list for review.17:06
JFo..17:06
JFooh17:07
JFoplease note the blueprint note17:07
JFo<JFo>  * 1 blueprints (Including HWE Blueprints)17:07
JFo<JFo> This number is wrong. The only blueprint I see on the list is mine.17:07
JFo..17:07
bjf[TOPIC] Blueprints: Natty Bug Handling (JFo)17:07
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling17:07
MootBotNew Topic:  Blueprints: Natty Bug Handling (JFo)17:07
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-bug-handling17:07
JFonothing to report17:08
JFo..17:08
bjfIs apw around? I know this is a day off for him but I'm just wondering.17:08
JFothink he is gone now17:09
bjf[TOPIC] Blueprints: Enhancements to the firmware test suite (cking)17:09
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements17:09
MootBotNew Topic:  Blueprints: Enhancements to the firmware test suite (cking)17:09
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-firmware-test-suite-enhancements17:09
ckingChanges to fwts (natty development branch):17:09
cking * remove need for sudo when loading ACPI tables from file (bug fix)17:09
cking * initial ACPI tables field checking - on common fields that give most issues17:09
cking * move kernel log tables into json format data17:09
cking * remove --fwts-debug17:09
cking * --stdout-summary outputs FAILED levels, e.g FAILED_HIGH, FAILED_LOW, etc17:09
cking * adjust log width to match tty width when logging to stdout17:09
cking * add aborted and skipped test to summary17:09
cking * cpufreq: make this an experimental test as it's not fully validated yet17:09
cking * check for non-compliant brightness levels17:09
cking * working on AML method sanity checking17:09
cking..17:09
bjf[TOPIC] Blueprints: Handling of Deviations from Standard Kernels (smb)17:09
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance17:09
MootBotNew Topic:  Blueprints: Handling of Deviations from Standard Kernels (smb)17:09
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-frankenkernel-maintenance17:09
smbSmall progress in the documentation17:10
smbWill do the in tree doc next and try the tooling17:10
smb..17:10
smbo17:10
smbForgot: for the drm33 upstream kernel I finished the scripting and have sent out the first patch queued notice17:11
smb..17:11
bjf[TOPIC] Blueprints: Review of the Stable Maintenance Process (sconklin)17:11
bjf[LINK] https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review17:11
MootBotNew Topic:  Blueprints: Review of the Stable Maintenance Process (sconklin)17:11
MootBotLINK received:  https://blueprints.launchpad.net/ubuntu/+spec/hardware-kernel-n-stable-process-review17:11
sconklinWe're roughly half way through the first trial of the new stable kernel process, which is outlined here;17:11
sconklinhttps://wiki.ubuntu.com/Kernel/StableReleaseCadence17:11
sconklinYesterday, we reverted commits for bugs without verification, and uploaded the resulting kernels this morning.17:11
sconklinAs soon as they are built, they will require QA and Cert testing before being released.17:11
sconklinFor Maverick, The following bugs had commits reverted due to lack of verification:17:11
sconklin598938   [Realtek ALC269] ALSA test tone not correctly played back17:11
sconklin637291   [Realtek ALC269] ALSA test tone not correctly played back; no audio on laptop speakers but17:11
sconklin648871   [Realtek ALC269] ALSA test tone not correctly played back17:11
sconklin642892   [Realtek ALC269] ALSA test tone not correctly played back17:11
sconklin655386   no audio playback except with headphones but it is extremely quiet17:11
sconklin546769   no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E17:11
sconklin663642   DVI doesn't work at BeagleBoard xM rev A317:11
sconklin580749   Pulseaudio is not running VT170817:11
sconklinFor Lucid, The following bugs had commits reverted due to lack of verification:17:11
sconklin598938   [Realtek ALC269] ALSA test tone not correctly played back17:11
sconklin637291   [Realtek ALC269] ALSA test tone not correctly played back; no audio on laptop speakers but17:11
sconklin642892   [Realtek ALC269] ALSA test tone not correctly played back17:11
sconklin655386   no audio playback except with headphones but it is extremely quiet17:11
sconklin546769   no sound with Realtek ALC269 - on Sony Vaio VPCEB1S1E17:11
sconklin580749   Pulseaudio is not running VT170817:11
sconklin605047   Internal Microphone on Dell Lattitude e6410 does not work17:11
sconklin628776   HP NC511i Driver (be2net and be2scsi) is missing in kernel module udebs17:11
sconklin580749   Pulseaudio is not running VT170817:11
sconklin465942   Hardware device disappearing from Sound Preferences on ASUS 0x104381b317:11
sconklin587546   Pulseaudio fails after several seconds17:11
sconklinGeneral comments on the new stable cadence process:17:11
sconklin* Thanks for all the help and understanding. This first test run through the process17:12
sconklinsteps has been very labor intensive, slow, and error prone.17:12
sconklin* We are refining the process as we go. Details are being maintained on the wiki page linked above.17:12
sconklin* Martin Pitt has agreed to change the verification tagging for bugs to "verification=[needed|failed|done]-<release>"17:12
sconklin  in order to help us track verification in different released kernels within the same bug.17:12
smberr would the alsa one not be probably be stabel?17:12
sconklin..17:12
smbupstream stable I meant17:12
sconklinit may be queued in upstream stable, we wouldn't know17:12
sconklin(unless we looked)17:12
smbI would have thought most of anything touching alsa came through a upstream stable update...17:13
smbJust a feeling...17:13
bjfsmb, no, we've taken patches from diwic for example17:13
sconklinwe took some of these as prestable17:13
sconklinand one caused a regression17:13
smbok, so those were just more than I could remember17:13
smbI be quiet then17:14
JFowill those get put back in for verification of the next kernel?17:14
sconklinthere are fewer patches that there are bugs listed17:14
JFoof/in17:14
bjfJFo, only if the request is made to do so via the bug17:14
JFook, thanks bjf17:14
JFo..17:14
sconklin..17:14
bjfJFo, it will not happen automagically17:14
JFoI see17:14
bjf[TOPIC] Status: Natty (tgardner)17:15
MootBotNew Topic:  Status: Natty (tgardner)17:15
bjfguess not17:16
bjf[TOPIC] Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin)17:16
MootBotNew Topic:  Security & bugfix kernels - Maverick/Lucid/Karmic/Hardy/Dapper (sconklin)17:16
tgardnerapw just uploaded -4.13 yesterday. the 2.6.37-rc2 is in the works.17:16
tgardner..17:17
sconklin||                         || Upd./Sec.     || Proposed      || TiP || Verified    ||17:17
sconklin|| Dapper: Kernel          || 2.6.15-55.89  ||               ||     ||             ||17:17
sconklin|| Hardy:  Kernel          || 2.6.24-28.80  ||               ||     ||             ||17:17
sconklin|| =       LRM             || 2.6.24.18-28.7||               ||     ||             ||17:17
sconklin|| Karmic: Kernel          || 2.6.31-22.68  ||               ||     ||             ||17:17
sconklin|| =       mvl-dove        || 2.6.31-214.30 || 2.6.31-214.32 ||     ||             ||17:17
sconklin|| =       ec2             || 2.6.31-307.21 ||               ||     ||             ||17:17
sconklin|| Lucid:  Kernel          || 2.6.32-25.45  || 3.6.32-26.47  || 14  ||  6 / 24     ||17:17
sconklin|| =       LBM             || 2.6.32-25.24  || 2.6.32-26.25  ||     ||             ||17:17
sconklin|| =       mvl-dove        || 2.6.32-209.25 || 2.6.32-211.27 ||     ||             ||17:17
sconklin|| =       fsl-imx51       || 2.6.31-608.19 || 2.6.31-608.20 ||     ||             ||17:17
sconklin|| =       ec2             || 2.6.32-309.18 ||               ||     ||             ||17:17
sconklin|| = lts-backport-maverick || 2.6.35.22.34  ||               ||     ||             ||17:17
sconklin|| Maverick: Kernel        || 2.6.35-22.35  || 3.6.35-23.38  || 14  ||  12 / 30    ||17:17
sconklin|| =       mvl-dove        || 2.6.32-410.27 ||               ||     ||             ||17:17
sconklin|| =       ti-omap4        || 2.6.35-903.18 ||               ||     ||             ||17:17
sconklin..17:17
bjf[TOPIC] Incoming Bugs: Regressions (JFo)17:18
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)17:18
JFoIncoming Bugs17:18
JFo12 Natty Bugs17:18
JFo1025 Maverick Bugs (up 304 since the final maverick meeting)17:18
JFo1082 Lucid Bugs (up 68 since the final maverick meeting)17:18
JFoCurrent regression stats (broken down by release):17:18
JFo==== regression-potential ====17:18
JFoAs this tag is deprecated, this listing is only to ensure that I keep it on my radar until17:18
JFochanges to the apport hooks and my processing of the currently tagged bugs is completed.17:18
JFo  * 3 natty bugs17:18
JFo  * 396 maverick bugs (up 32 since the final maverick meeting)17:18
JFo  * 177 lucid bugs (up 14 since the final maverick meeting)17:18
JFo==== regression-update ====17:18
JFo  * 20 maverick bugs17:18
JFo  * 77 lucid bugs (up 13)17:18
JFo  * 6 karmic bugs (no change)17:18
JFo  * 0 hardy bugs (no change)17:18
JFo==== regression-release ====17:18
JFo  * 147 maverick bugs17:19
JFo  * 193 lucid bugs (up 16)17:19
JFo  * 40 karmic bugs (up 3)17:19
JFo  * 2 hardy bugs (no change)17:19
JFo==== regression-proposed ====17:19
JFo  * 13 maverick bugs17:19
JFo  * 7 lucid bugs (up 1)17:19
JFo  * 1 karmic bug (no change)17:19
JFoPlease note that I have removed Jaunty from the listing above.17:19
JFo 17:19
JFo..17:19
bjf[TOPIC] Incoming Bugs: Bug day report (JFo)17:19
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)17:19
JFoThe next Kernel Bug Day will be next Tuesday. The focus will be on bugs with patches attached17:19
JFoin order to begin the serious amount of work to be done there. I am planning to work with Andy17:19
JFoand Tim this week to see how we will handle Team Bug Days since we are changing the way we do17:19
JFothe Top Bugs each week. I will also begin working up a weekly report of the major bugs we are looking at.17:19
JFoChances are I will make some of that data available during this meeting going forward.17:19
JFo..17:20
bjfplease note that if we take any of those patches, we either need the HW to verify them or have a commitment from the community to verify them or they weill be reverted17:20
bjf..17:20
JFoyep, noted..17:21
bjf[TOPIC] Triage Status (JFo)17:21
MootBotNew Topic:  Triage Status (JFo)17:21
JFoI talked with a number of the folks we work with to triage bugs during UDS, but, other than that,17:21
JFoI have nothing to report on as far as status. I am, however, interested in your thoughts on holding17:21
JFoanother Kernel Triage Summit. We could do our own again, or we can make it a part of one of the17:21
JFocommunity events such as Ubuntu Developer Week, Open Week, etc.17:21
JFo..17:21
bjfbased on all the effort that you've put into getting community involvement, did we get any value or would you have been better off just doing that amount of effort in triaging yourself?17:22
JFowe saw some benefit, but I think it is too early to tell the impact17:22
JFoI'd have to defer to those who presented and attended as to the usefulness17:23
JFoI felt it was a success17:23
JFomore so than I had hoped for17:23
JFoogasawara, what did you think?17:23
bjfi'm asking about community triaging in general17:23
JFoah,17:23
JFowe saw some improvement, but I don't know if it was commensurate with the effort involved17:24
JFoin organizing our own I mean17:24
JFoI think we could do one session at one of the other planned events17:24
JFoand get the same level of return17:24
JFoeither that17:25
JFoor we can generate some documentation on various areas and make it available online17:25
JFoso as to limit the impact on everyones already limited free time17:25
JFo I'm open to suggestion offline17:25
JFo..17:25
JFoin summary17:26
JFoI think I could have just done the triage effort myself17:26
JFo..17:26
JFo:)17:26
bjf..17:26
bjf[TOPIC] Open Discussion or Questions: Raise your hand to be recognized (o/)17:26
MootBotNew Topic:  Open Discussion or Questions: Raise your hand to be recognized (o/)17:26
bjfthanks everyone17:27
bjf#endmeeting17:27
MootBotMeeting finished at 11:27.17:27
JFothanks bjf17:27
kamalthanks bjf17:27
sconklinthanks bjf!17:27
jjohansenthanks bjf17:28
smbbjf, thanks17:29
SergioMeneseshi o/17:29
mdeslaurhello18:03
jjohansenhi18:03
SergioMenesesmdeslaur, jjohansen \o18:05
jdstrando/18:07
* sbeattie waves18:09
kees\o18:11
jdstrandkees: are you running the meeting, or shall I?18:13
keesjdstrand: you can, I'm still trying to collect my status report to email out18:15
jdstrand#startmeeting18:16
MootBotMeeting started at 12:16. The chair is jdstrand.18:16
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]18:16
jdstrandwelcome to the ubuntu-security team meeting, postponed from yesterday18:16
jdstrandI guess I'll start, but I have several items to discuss at the end18:16
jdstrandso far this week I have been finishing up things so I can focus on dbus/apparmor integration18:17
jdstrandI uploaded the iptables merge and did the libnfnetlink MIR done18:17
jdstrandI am reviewing some sponsored libvirt uploads as well18:18
jdstrandonce that is done, I will dive into dbus, and then finally be able to talk to jjohansen about it18:18
jjohansen\o/18:19
jdstrandlater in the week I hope to finish my merges and test thunderbird for the 3.0 -> 3.1 migration on lucid18:19
jdstrandI have a sneaking suspicion another firefox is coming, so I may need to do that some18:19
jdstrandmdeslaur: you're next (let's let kees go after sbeattie)18:20
mdeslaurI'm going to be doing some merges this week18:20
mdeslaurand I have a quagga update coming out18:20
jdstrandoh, I forgot, I need to follow up on the lucid apparmor SRU18:20
jdstrandmdeslaur: (sorry for interrupting)18:20
mdeslaurI'll be investigating a way to test python-paste18:21
mdeslaurand I have a virt-manager SRU to do18:21
mdeslaurI think we're releasing flash updates today, so I have that to package18:21
mdeslaurthat's it for me18:21
mdeslaursbeattie?18:21
* sbeattie is on community this week.18:22
sbeattieas part of that,I'm working on sponsering a proftpd upload.18:22
sbeattieI also have an openssl update to push out.18:22
sbeattiebeyond that, I want to poke more than the token amount that I have on the maverick apparmor sru.18:23
sbeattieand will help out with the lucid one, as well.18:23
sbeattieI think that's all I've got.18:23
sbeattiekees?18:23
keesokay, did a bunch of kernel work last week18:24
keesthe XD_DISABLE patches are in a tip branch for testing18:24
keesI'm going to try to get them into Ubuntu too, for full happiness18:24
jdstrandsbeattie: are you aware of report-todo-sponsoring from UCT and security-fake-sync from security-tools?18:24
keesdrosenbe's dmesg_restrict went in upstream, so I'm going to try to get that enabled by default in Ubuntu (see ubuntu-devel email)18:24
keesthis week, I'm on triage, and I'll be continuing to chase up upstream constification work18:25
sbeattiejdstrand: not so much; I'll look at them, thanks.18:25
jdstrandsbeattie: feel free to ping me when you are ready to look at them (esp security-fake-sync)18:25
keesI've got lvm2 to review for mdeslaur, and a stack of PHP audits to do too.18:25
keesthat's it from me.18:25
jdstrandcool18:26
jdstrandare there any non-status update items from anyone before I dive in?18:26
* jdstrand takes that as a no18:27
jdstrandso first off...18:27
jdstrandkees, mdeslaur, sbeattie: if you guys haven't already done so, we need to retartget any maverick (and lucid) bps to natty18:28
keesjdstrand: oh, fun, yes.18:28
jdstrandthis needs to be done by Nov 18 (thursday), so really tomorrow eod18:28
sbeattieah, right, thanks.18:28
jdstrandpitti is going to redo the reports or somethings, and I think the hard deadline for the bps is the 18th18:29
jdstrandI have the list we discussed that I can provide outside of this meeting if needed18:29
mdeslaurjdstrand: that would be nice, yea18:29
jdstrand(and all that applies to me too-- I haven't already done any of this)18:29
jdstrandk18:29
mdeslaurdo we need to recreate the blueprints, or can we just switch them over?18:30
jdstrandalso, at UDS we were asked by wendar to discuss and put in the wiki a sort of security checklist for ARB18:30
jdstrandmdeslaur: there should be a way to just retarget them18:30
jdstrandmdeslaur: we can talk to robbiew about it-- he indicated it should be easy18:30
mdeslaurok, I'll try18:30
mdeslaurARB?18:31
keesApplication Review Board, iirc?18:31
jdstrandI have put our discussion (and a couple of extra things I thought of) in https://wiki.ubuntu.com/PostReleaseApps/SecurityChecklist18:31
jdstrandApplication Review Board, yes18:31
robbiewmdeslaur: jdstrand yeah...send me a list and I can do it18:31
mdeslaurETOOMANYACRONYMS18:31
jdstrandif each of us could review that wiki page that would be great18:32
jdstrandwe can discuss in #ubuntu-hardened18:32
jdstrandI'd like to get that to wendar soon since they are moving forward in various ways18:32
jdstrandlastly, I'd like to encourage us to strive to be more transparent18:34
sbeattiejdstrand: re ARB recommendations, what about long term suggestions to ease sandboxing mediation?18:34
jdstrandeg, send activity reports to the whole team, and perhaps announce on a "dailyish" basis what we are working on18:34
jdstrandsbeattie: I think that is definitely worth discussion, but not sure that document is where it should happen. perhaps talk to wendar about that18:35
jdstrandsbeattie: I know some discussion is happening in ubuntu-devel@18:35
mdeslaurjdstrand: sounds like a good idea18:36
jdstrandwe talked about being more transparent a bit last week (ad-hoc)18:36
mdeslaurjdstrand: do we not send our activity reports to security@ right now?18:36
mdeslaur(and robbiew)18:36
jdstrandI know I find it all too easy to get my nose in my work and forget to communicate what I am working on18:36
sbeattiemdeslaur: not all of us (looks sternly in mirror) are strict about doing that.18:36
jdstrandmdeslaur: yes, that is what we all should be doing18:36
mdeslaursbeattie: oh :)18:37
robbiewwell.../me stopped collating them for ubuntu-devel18:37
mdeslaurok, so how about we announce what we're going to do when we arrive in the morning?18:37
jdstrandmissing a week or sending it late isn't an issue. it is just nice that we know what each other is working on so we know what to help with or pick up18:37
jdstrandrobbiew: it seems a lot of teams are not doing that any more... I'm not sure it should go to ubuntu-devel@, but I certainly find it useful to see what the others are doing18:38
jjohansenerr, I would suggest checking mail before announcing what you are going to do18:38
keesyeah18:39
robbiewyeah...I'm a +1 on the team knowing18:39
jdstrandmdeslaur: I am not sure it has to be even that formalized18:39
robbiewas for ubuntu-devel...seems to get lost in the noise, imo18:39
jdstrandI just want to make sure we are coordinating appropriately and in general being a team18:39
jdstrandI know that mdeslaur and sbeattie picked up the same update some time recently18:39
mdeslaurI sure am curious what you guys are doing sometimes :P18:39
mdeslaurso I'm all for it18:40
jdstrandplus, you guys are so awesome I like to feel awesome by proxy by knowing what you are working on :)18:40
mdeslaurhehe18:40
jdstrandI feel pretty strongly that we shouldn't feel like just a bunch of individuals working totally independently. we should foster a sense of team and a great way of doing that is sharing our work18:41
jdstrand(ie, sharing with others what we are doing as well as workload)18:41
mdeslaurthat, and bringing in a box of donuts to work once in a while18:41
jdstrandanyway, my two cents :)18:41
jdstrandmdeslaur: I like chocolate with sprinkles and jelly. at least for next time :)18:42
mdeslaurjdstrand: ugh, you can have those ones :)18:42
jdstrandI might surprise you after that18:42
jdstrandhehe18:42
jdstrandkees, sbeattie, mdeslaur: what do you think about being more vocal with the team on what we are working on?18:43
jjohansengenerally I think its a good idea18:43
jjohansenbut its easy to over do it18:43
jdstrand(some concensus would be nice and our ad-hoc discussion last week didn't really come to a conclusion)18:43
jdstrandjjohansen: not suggesting twitter :)18:44
sbeattiejdstrand: +1 from me, I'm just not very good at doing that.18:44
jdstrandI don't think I am either18:44
jjohansenjdstrand: oh, so the new fb messaging? :P18:44
jdstrandbut if we strive for it, I think we'll figure out the right balance18:44
jdstrandit isn't about being overly chatty or unproductive... just a little sharing witht the team18:45
jjohansenmy only suggestion is that I think it works better if its kept informal18:45
jjohansenyep18:45
jdstrandjjohansen: I would agree18:45
keesI'm for it; informal is good.18:45
sbeattiejjohansen: I plan to broadcast updates via fingerd.18:45
jjohansenawesome!18:45
* jdstrand is just trying to encourage a little sharing which might lead to cool/productive discussion18:45
mdeslaurwell, how about this: if I forget to mention what I'm working on, a simple "Hey, mdeslaur, what you up to?" to remind me would be cool18:46
jdstrandthat sounds good18:46
jdstrandthat goes for me too18:46
jdstrandwe can see how it goes and if we are bugging each other it is ok to say so :)18:46
jdstrandalrighty, seems we've probably beat that horse enough18:47
jdstrandanything else for the security team?18:47
jdstrandgoing once18:48
jdstrandgoing twice18:48
mdeslaursold! to the lady with the hat18:48
jdstrand#endmeeting18:49
MootBotMeeting finished at 12:49.18:49
jdstrand:)18:49
jdstrandthanks everyone!18:49
mdeslaurthanks jdstrand!18:49
mdeslaurthanks everyone18:49
sbeattiejdstrand: thanks!18:49
jdstrand\o/18:49
huatssorry I am late20:11
highvoltagefor?20:12
PontusOhmanhuats: > The meeting will begin in +45 min20:12
huatsrrrggg thanks to the daylight savings...20:12
huatsPontusOhman, thanks20:12
huatshighvoltage, Loco Council meeting20:13
PontusOhmanhuats: Check: http://fridge.ubuntu.com/calendar20:13
huatsPontusOhman, yeah I know20:14
Nafallohuats: well, to be fair, the fridge calendar and the Agenda says different times.20:14
huatsjust my memory20:14
huats:)20:14
=== RCua is now known as CoconutCrab
PontusOhmanczajkowski: When will the meeting begin?! The agenda says 21.00 for me, that's 20 minutes ago! The fridge says 22.00 for me, thats about 40 minutes?!20:21
popeyola20:24
PontusOhmanpopey: =)20:24
popeyLoCo Council meeting is in 35 mins yes?20:24
Nafallopopey: depends... are you following the calendar or the agenda? :-)20:25
PontusOhmanpopey: I dunno! The agenda says it should started about 25 minutes ago, the fridge says in the next 35 minutes20:25
popeyah20:25
popeyoops20:25
Nafalloobviously it should be :30! :-D20:25
itnet7I'll fix the agenda, I'm there20:25
highvoltageI wish people in countries with DST would pest their government to do away with it!20:25
Nafallohi itnet7 :-)20:25
itnet7highvoltage: we've tried20:25
itnet7hey there Nafallo !20:25
huatspopey, I arrived 15 minutes ago saying "sorry I am late"20:26
huats:)20:26
popeyhaha20:26
popeysorry I'm late20:26
huatsand hello popey and itnet7 btw :)20:26
Nafallohighvoltage: but but... not being on the timeline for half a year is such fun...20:26
Nafallopopey: you're late and early at the same time :-P20:26
PontusOhmanO_o :D20:26
popeywhats the plan then? shall we start at :30 ?20:26
popeyor bump to the next hour?20:27
popeyI'm happy either way20:27
PontusOhmanIf we will start in 30 minutes, I will pass it over to my chairman Farmfield20:27
Nafallopopey: we are missing people though?20:27
popeywho?20:27
popeyczajkowski is standing next to me :)20:28
popeyjust getting her to get her laptop out20:28
popeystart in 2 mins huats / itnet7 ?20:28
Nafallopopey: hah. fair enough. paultag and leogg then? :-)20:28
itnet7fine with me20:28
huatspopey, euh 32 minutes I think20:29
PontusOhmanCan I get an answer on, why was it two diffrent times for this meeting?! The Agenda told me 20.00 UTC (For me it was 30 minutes ago) and the fridge tells me it's 21.00 CET (In about 30 minutes)20:29
popeyPontusOhman: daylight savings time20:29
huatspopey, since there is something that is not really fixed I would be in favout of the latest20:29
PontusOhmanpopey: > That's s*cks20:30
popeyok,that would suit me and czajkowski too given I'm just bringing lasagne out of the oven :)20:30
popeyPontusOhman: sorry, we'll fix it20:30
popeyit happens every 6 months unfortunately20:30
huats(my meat balls are just going to the oven to be honnest :))20:30
PontusOhmanIt's ok :)20:30
huatspopey, have a nice meal my friend :)20:30
popeyok, so in 29 mins20:31
mghg__popey: you can not blame it on daylight savings time. It is 20:00 UTC according to https://wiki.ubuntu.com/LoCoCouncilAgenda, and 21:00 GMT according to http://fridge.ubuntu.com/calendar.20:32
popeyI can't ?20:34
itnet7mghg__: refresh20:34
popeythat link shows 21:00 LoCo Council Meeting here.20:34
FarmfieldI think someone is missing that it's changed this year. Did UK even have daylight savings before?20:34
popeyyes, we've had DST for about 50 years or so20:34
czajkowskiwell these things happens20:35
czajkowskiand it's only happened once20:35
czajkowskiand the agenda has only 2 items. so not the end of the world20:35
FarmfieldNo prob's folks20:35
Farmfield:)20:35
NafalloFarmfield: yes. we have BST every year :-)20:36
FarmfieldWe as in we Swedes? ;)20:36
FarmfieldTo long ago I lived in UK to remember...20:37
mghg__Two different sources gives different meeting starting times. Neither UTC and GMT change depending on seasons, i.e. daylight savings do not apply20:37
FarmfieldThere's a point where things are what they are and we passed that point a while back now, hehe... The meeting is in 20 minutes and the 'why' or 'which time is correct' isn't really important... ;)20:40
NafalloFarmfield: well said20:42
FarmfieldNafallo: When you takn as much as I do you're bound to say something intelligent once and again... ;)20:43
Farmfield(t a L k)20:43
Nafalloheh20:44
PontusOhmanWill be here in a few seconds... Darn thé :)20:58
PontusOhmanTime for GO GO GO?! It's 5 minutes late :D21:03
czajkowskialoha21:03
czajkowskiPontusOhman: 3 mins in fact21:03
czajkowskilets not get ahead of ourselves21:03
PontusOhman:)21:03
popeyyes, lets be behind by about an hour21:03
Nafalloczajkowski: 3:30 at the time he said it ;-)21:04
czajkowskiNafallo: lets not be a brat shall we21:04
peetra_o/21:04
Nafalloheh21:04
PontusOhmanO_o21:04
czajkowskialoha21:04
huatshello21:05
czajkowski#startmeeting21:05
MootBotMeeting started at 15:05. The chair is czajkowski.21:05
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]21:05
czajkowskialoha to tonights meeting21:05
czajkowski[topic] Sweden loco re approval21:05
MootBotNew Topic:  Sweden loco re approval21:05
czajkowski[link] https://wiki.ubuntu.com/SwedishTeam/ReApprovalApplication21:06
MootBotLINK received:  https://wiki.ubuntu.com/SwedishTeam/ReApprovalApplication21:06
popeyWho's here form Sweden?21:06
czajkowskihuats: leogg itnet7 popey evening folks21:06
* Nafallo looks for Farmfield 21:06
peetra_o/ I am a Swesish speaking Finnish girl, active in the Swedish LoCo. _o/21:06
* PontusOhman Is from Sweden and I'm the Team Contact for Ubuntu Sweden21:06
FarmfieldI'm the TeamLeader21:06
leogghi all21:06
Farmfield...for the Swedish LoCo21:07
czajkowskiPontusOhman: Farmfield nice arrangement21:07
czajkowskiFarmfield: so care to tell us a bit about your team please21:07
HundIm here to. Im one of the admins.21:07
ameliaI'm also from the Swedish LoCo, but i'm one of the serveradmins so i'll keep my mouth shut for most of the evening. :)21:08
NafalloIRC channel founder and ubuntu-se.org host ←21:08
czajkowskiamelia: heh21:08
itnet7Hey there!21:08
huatsfinally itnet7 :P21:09
czajkowskiFarmfield: ???21:09
Nafallomeh, arrow on wrong side of the text :-P21:09
itnet7Sorry :-P looking at the re-approval21:09
FarmfieldThe team. We have a TL and a TC, a quite new combo. Before that (18 months ago) there was 2TC's.  We run phpBB as forum and have 3 active admins there. We also have about 5 active moderators. Then we have HakanS - who is here - who's in charge of our Drupal Portal.21:09
czajkowskiFarmfield: sounds great from the admin side of things, what about your community21:10
* HakanS is here21:10
FarmfieldWe have a stabile community but is lacking in growth.21:11
czajkowskiFarmfield: how many active members do you have21:11
* Nafallo shims in and says the irc channel has about 120 people most of the time21:11
FarmfieldWe've been speculating about the 'why' but it might be Ubuntu is to good.21:11
FarmfieldGrowth come from new visitors seeking support and then engaging as enthisiasts. That's in decline21:12
FarmfieldWe have 200 active members.21:12
peetrappl don't need the support in the same way any  more, most stuff can be solved with google.21:12
* PontusOhman Is a good example, 2009 new to Ubuntu, 2010 sleeping admin and active Team Contact for Ubuntu Sweden :)21:13
Farmfield200 people is exluding 50-100 active on IRC. I'm not much of an IRC'er så forgot that. Sry.21:13
czajkowskiFarmfield: well you have 59 members on launchpad but 16000 people on forums21:13
czajkowskimassive difference21:13
czajkowskican you perhaps tell us why there is a lack of interest in becoming part of the team21:13
peetraBut with an average of 3000-4000 visitors/day i think it is a very needed site, even if the community is not spamming it all the time/ every five minute.21:13
Farmfieldpeople register to ask how to change the background picture and then they don't need more support, they won't register at Launchpad21:14
Farmfield;)21:14
peetraLaunchpad is difficult and hard to find anything at all in especially for newbies (like me)21:14
* Nafallo wasn't aware we had a launchpad group...21:15
PontusOhmanhttps://launchpad.net/~ubuntu-se21:15
itnet7Farmfield: I see you have an irc channel, do you do monthly meetings?21:15
FarmfieldI gotta go for 2 minutes - my son is having a breakdown.21:15
czajkowskiwell most members sign up on lp21:15
peetraNo monthly meetings21:16
czajkowskiPontusOhman: can you tell us about events you run21:16
czajkowskiwhat do you do for face to face events21:16
Nafallonow we have 60 people on LP :-P21:16
PontusOhmanWill try to do my best here so...21:16
peetrai signed up on lp by mistake. ^^ It came with the Ubuntu One thingy?21:16
PontusOhmanWe got some ppl on different places over Sweden that have release parties in the spring and in the autumn21:17
czajkowskiPontusOhman: thanks21:17
FarmfieldCondoms people. Use them.21:17
FarmfieldAnd yes, I'm back.21:17
peetra*6121:17
PontusOhmanAnd if you ask us about monthly meetings in the LoCo, no not at this moment we have it.21:18
PontusOhmanBut I have plans to bring it up for us in the future :)21:18
peetra[IDEA] Monthly meetings at the IRC channel21:19
MootBotIDEA received:  Monthly meetings at the IRC channel21:19
czajkowskiPontusOhman: any regular meet ups or life outside of the forums21:19
czajkowskii'm not saying forums are bad21:19
czajkowskijust 16000 v 61 people is a massive differene21:19
PontusOhmanczajkowski: Yes, we have!21:19
peetraThe forums rules!21:19
PontusOhmanAs a fact I'm running a GNU/LUG in my town that's meets up every month21:20
NafalloI believe part of the trouble here is awareness of the launchpad group.21:20
czajkowskiPontusOhman: a GNU/LUG isn't a loco21:20
NafalloI've been with the LoCo from the very very very beginning, and I didn't know about such a group.21:20
Farmfield czajkowski: The Swedish LoCo is focused on support - even though everything else is there. But focusing on support equals phpBB and that's why we're 16.000 + members in phpBB21:20
peetraI can't see why we need new Ubuntu users in the lp-team? That is the problem, can czajkowski tell us why?21:21
leoggpeetra: for translations and bug reports?21:21
huatsWhat about Team reports ?21:21
huatsare you doing them ? if not do you plan to ?21:22
czajkowskipeetra: for being a part of the ubuntu community21:22
peetraokej, so we should get all the windows emigrants directly involved with bug reports and translating? :O21:22
Nafalloleogg: translations is mostly handled directly upstream. we have some great guys working on that. we tend to not use launchpad, but commit straight.21:22
popey16000 is a significant chunk of people21:22
itnet7Peetra no one said to get all of them into LP, even though that would be awesome for a 16k+ team in LP21:23
peetra:D21:23
itnet7but as people get involved with the team, the natural thing would be to encourage them to join your LoCo and help the team contribute, even teach them how21:23
NafalloI'm not sure how bug reports would tie in to a launchpad group specifically? also, most of peoples problems can be solved in forums/on irc. it's very seldom I've seen people with genuine bugs on the IRC channel21:23
PontusOhmanczajkowski: If we lock beyond the the release parties... Some groups (cities / towns) from the LoCo meets up21:23
leoggNafallo: bug reporting is a nice and easy way to contribute back to the community :)21:24
Nafalloleogg: yes, if the problems are genuine bugs... :-)21:25
FarmfieldI must ask  czajkowski and popey; What about 16.000 people? It's the abount of registered members - many of them not more than casual visitors asking 1-3 questions - generated since fall 2004. It's not a massive amount of people, it's a long time.21:25
NafalloI'm not debating the importance of bug reports here :-)21:25
czajkowskiFarmfield: as i said it's not a bad thing, i just wonder why they are not part of your loco21:26
czajkowskibeing on a forum isn't the same thing21:26
leoggNafallo: me neither, I just don't understand why there are so few people on lp :)21:26
popeyWe have plenty of documentation detailing how people can get involved in Ubuntu - I don't think this meeting should be trying to cover all of that21:26
* peetra helps the Swedish community with phpBB and is shore that Ubuntu will manage w/o her raporting bugs21:26
popeyWhat I would like to see is more documentation from the Swedish team of advocacy and other ubuntu community 'work' done over the last year.21:27
czajkowskipeetra: if everyone took that attitude we'd have no bugs reported though21:27
peetraI haven't time to do everything21:27
Nafalloleogg: because if me, as one of the first three loco members, doesn't know about such a group.. I can assure you Mr Member doesn't know about it either :-)21:27
Farmfielditnet7: For us, joining the team doesn't involve lp, it involves projects within the LoCo. We havent been good utulizing lp for organizing the LoCo, we've used out own forum.21:27
popeyWhilst forum based support and discussion is fantastic (and you've clearly got a significant number of people using the forums) a LoCo team is also about advocacy, bug jams, triaging, translating.. building the community around the team and encouraging people to get involved in the project.21:28
czajkowskiFarmfield: do you use the loco directory ?21:28
popeyIMO21:28
popeyFarmfield: when you say 'organizing the loco' what does that mean?21:28
Farmfield czajkowski: I say as 'Bones' on TV: I don't know what that meens.21:28
PontusOhmanpopey: > We got documentation for 8.04 LTS, 9.04, 9.10 and 10.04 LTS, and 10.10 is comming up! Both the Desktop and the server is coverd in there :)21:28
itnet7Farmfield: What happens if you lose your hosting?21:29
czajkowskiFarmfield: you've never heard of the loco directory?21:29
czajkowskihttp://loco.ubuntu.com/teams/ubuntu-se21:29
MootBotLINK received:  http://loco.ubuntu.com/teams/ubuntu-se21:29
Farmfieldczajkowski: Noops. But I guess I should be really ashamed.21:29
itnet7Or if you happen to burn out, does everyone in the team have all the administrative details?21:29
Farmfielditnet7: Whi os 'you'?21:30
Nafalloitnet7: I'm hosting them... :-)21:30
Farmfielditnet7: Who is 'you' in that question?21:30
* peetra likes Nafallo21:30
itnet7Farmfield: are you the leader?21:30
Farmfielditnet7: TeamLeader, yes.21:31
cmpitgA TeamLeader never heard of the Team?21:31
itnet7Well, teams use launchpad to help manage their LoCo's21:31
itnet7for the most part21:32
FarmfieldIn general: We have 2 backups made daily to external servers, backup server admins a.s.o... That's not an issue at all.21:32
ameliaitnet7: we're hosting the server in UK (nafallo takes care of that), within the serveradmin group i can assure we could have another server up an running within a day and we also keep backups in two different locations in sweden.21:32
leoggFarmfield: IMO as a team leader you should be more aware of what's going on outside the LoCo21:32
czajkowski[vote] please vote on the re approval of the Swedish loco reapproval. ONLY COUNCIL MEMBERS VOTE PLEASE.21:32
MootBotPlease vote on:  please vote on the re approval of the Swedish loco reapproval. ONLY COUNCIL MEMBERS VOTE PLEASE..21:32
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot21:32
MootBotE.g. /msg MootBot +1 #ubuntu-meeting21:32
czajkowski-121:32
MootBot-1 received from czajkowski. 0 for, 1 against. 0 have abstained. Count is now -121:32
MootBotPrivate -1 vote received. 0 for, 2 against, 0 have abstained. Count is now -221:32
huats-121:32
MootBot-1 received from huats. 0 for, 3 against. 0 have abstained. Count is now -321:32
popeyI'd like to see more real life events, and other community contribution to the project21:32
popey-121:33
MootBot-1 received from popey. 0 for, 4 against. 0 have abstained. Count is now -421:33
leoggsame here21:33
leogg-121:33
itnet7+021:33
Farmfieldleogg: I am, but it's all a question about the subject. Which subject are you referring to?21:33
MootBot-1 received from leogg. 0 for, 5 against. 0 have abstained. Count is now -521:33
MootBotAbstention received from itnet7. 0 for, 5 against. 1 have abstained. Count is now -521:33
czajkowski#endvote21:33
popeySorry guys and gals..21:33
czajkowski[endvote]21:33
MootBotFinal result is 0 for, 5 against. 1 abstained. Total: -521:33
leoggFarmfield: are you subscribed to the locoteams mailing list?21:33
czajkowski[agreed] sweden loco un approved21:33
MootBotAGREED received:  sweden loco un approved21:33
Farmfieldinsane. Show me one loco who match us21:33
PontusOhmanleogg: > I am21:33
popeyWe can certainly help to get you moving in the right direction.21:33
FarmfieldAnd we have 6 years running now21:33
NafalloFarmfield: actually no. 5 at the most.21:34
leoggPontusOhman: that's great21:34
PontusOhmanI'm the TC for Ubuntu Sweden21:34
czajkowski[topic] Vietnam  loco re approval21:34
MootBotNew Topic:  Vietnam  loco re approval21:34
czajkowskianyone here from Vietnam21:34
FarmfieldNafallo: Founded fall 2004 according to the wiki?21:34
czajkowski?21:34
ptkhanho/21:34
afterlastangelyes21:34
afterlastangel1+21:34
CoconutCrabI am here21:34
cmpitgMe, too21:35
CoconutCrabo/21:35
czajkowski[link] https://wiki.ubuntu.com/VietnameseTeam/ReApprovalApplication21:35
MootBotLINK received:  https://wiki.ubuntu.com/VietnameseTeam/ReApprovalApplication21:35
ducgiang_8888me21:35
cmpitgI'm a new secretary for Ubuntu-VN21:35
czajkowskiok welcome21:35
afterlastangelHello, everyone.21:35
czajkowskiso who is the team leader or point of contact for this meeting ?21:35
PontusOhmanWe will come back :)21:35
afterlastangelaccording wiki this is CoconutCrab21:35
czajkowski[link] http://www.ubuntu-vn.org/21:36
MootBotLINK received:  http://www.ubuntu-vn.org/21:36
afterlastangelczajkowski: this is our portal, for news and local activity21:36
cmpitgczajkowski: The portal is being very general21:36
czajkowskiok21:37
czajkowskiCoconutCrab: so care to tell us about your team ?21:37
afterlastangelczajkowski: we also provide support for new user via web-based IRC form the portal21:37
CoconutCrabczajkowski: I am the team contact but currently busy with my schoolwork, so I will ask my friend to do the talking21:37
CoconutCrabczajkowski: afterlastangel will do it21:38
afterlastangelCoconutCrab: thanks.21:38
CoconutCraband I will aid him, together with cmpitg and ptkhanh21:38
cmpitgSure21:38
czajkowskiok can someone please tell the council about the team please21:38
cmpitgafterlastangel represents team from the South, me from the North21:39
cmpitgOkay, me first21:39
cmpitgThe Ubuntu-VN community has around 16,000 members, current ~50 most active members21:39
afterlastangelczajkowski: did you mean how many people are their in out council?21:40
czajkowskiafterlastangel: no the loco council.21:40
cmpitgWe have 1,300 active members per months21:40
cmpitgczajkowski: Okay, I see21:40
peetraOkey folks, I checked some facts and over 10 000/ 16 000 users have actually logged in  to the forum the last year, I am very suprised to find such a great user rate.21:40
cmpitgThe local council have ~20 members21:41
cmpitg15 members active every week21:41
czajkowskipeetra: we've moved onto another team please21:41
peetraoh, shit21:41
czajkowskicmpitg: what council is this21:41
peetrasrry21:41
cmpitgczajkowski: Ubuntu-VN Loco Administration Team21:41
CoconutCrabczajkowski: ptkhanh, afterlastangel, cmpitg, excrypf and me are from #ubuntu-vn21:41
CoconutCrabczajkowski: I will take over the talking from here21:42
CoconutCrabczajkowski: is that okay with you?21:42
popeyif it's difficult we could do the approval via email?21:43
popeyif the translation is difficult we can give more time21:43
CoconutCrabUbuntu-vn is around 6 years old Loco21:43
CoconutCrabwe have a forum, and irc channel #ubuntu-vn and a mailling list21:44
CoconutCrabbut the forum is the most active21:44
czajkowskiCoconutCrab: can you tell us why so there are activities only going back to september this year listed http://wiki.ubuntu-vn.org/index.php/LocoTeam_Activities21:44
CoconutCrabbecause it is the most popular way of communicating on the internet21:44
CoconutCrabczajkowski: because before that, us student have to do the exam :), also summer vacation21:45
CoconutCrabI know that isn't a good answer21:45
czajkowskiCoconutCrab: but you've said you're active for 6 years21:45
CoconutCrabbut most of ubuntu-vn members are students and pupil21:45
cmpitgThat's right21:45
CoconutCrabczajkowski: the old people has moved away, like the founder21:45
CoconutCrabwe haven't heard from him for more than one year21:45
cmpitgAlso21:46
CoconutCrablike me, I have only joined ubuntu-vn for 2 years21:46
afterlastangelczajkowski: the /LocoTeam_Activities are log since the first approval21:46
czajkowskiright but you were approved 2 years ago and only list event since september 201021:46
cmpitgBecause we consist of mostly students, offline activities are prefered21:46
afterlastangelczajkowski: no21:46
afterlastangelczajkowski: just about months.21:46
czajkowskiafterlastangel: well the wiki page is then not up to date.21:46
CoconutCrabanother reason is that before september, we didn't have a secretary to do the reporting21:47
leoggafterlastangel: you were approved a couple of months ago?21:47
CoconutCrabczajkowski: we were approved April this year21:47
afterlastangelczajkowski: their are some misunderstanding21:47
CoconutCrabczajkowski: semi-approved :)21:47
CoconutCrabczajkowski: with a condition to re-approve in the next few months21:47
leoggCoconutCrab: yes, I remember... we asked you to come back21:47
cmpitgczajkowski: As you see, the wiki page was created recently, but it already has plenty of information21:48
CoconutCrableogg: :)21:48
cmpitgczajkowski: Since we now have a secrectary21:48
czajkowskiit's a wiki page, you don't need a secretary to update a wiki page.21:48
czajkowskianyone can do it21:48
cmpitgczajkowski: But we need some one who do the report and summarize them21:48
cmpitgczajkowski: Make statistics, strategies, ...21:49
cmpitgczajkowski: This has to be done in a centralized way21:49
cmpitgczajkowski: So that the activities could be more effective21:49
czajkowskicmpitg: hmm not really tbh.21:49
cmpitgczajkowski: This could be improved21:50
cmpitgczajkowski: In a very rapid period of time21:50
afterlastangelczajkowski: we have just  run as a Approved Loco team for 7 months and had 4 activities offline21:51
cmpitgActually 4 "big" activities21:51
cmpitgWe have weekly and monthly meetings an AUF/CNF centers21:52
cmpitgWhere we provide support, trial, ... everything related to LP and Ubuntu21:52
afterlastangelczajkowski: I mean we want to have more activity out the forum and the Internet, could bring ubuntu to more people in Vietnam where the Internet access maybe luxury21:52
cmpitgFrom OOo.org training, Ubuntu tips and tricks, installing and using, ...21:53
cmpitgWe have constantly 2 people working on it every Saturday afternoon21:53
cmpitgSo every one could find us anytime21:53
czajkowskiok think we're ready to vote21:54
cmpitgOkay21:54
afterlastangelczajkowski: we forgot adding the 10.04 Release party .. I think this is the fifth activity21:54
czajkowski[vote] please vote on the re approval of the Vietnamese loco.  ONLY UBUNTU LOCO COUNCIL MEMBERS VOTE.21:54
MootBotPlease vote on:  please vote on the re approval of the Vietnamese loco.  ONLY UBUNTU LOCO COUNCIL MEMBERS VOTE..21:54
MootBotPublic votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot21:54
MootBotE.g. /msg MootBot +1 #ubuntu-meeting21:54
czajkowski-121:54
MootBot-1 received from czajkowski. 0 for, 1 against. 0 have abstained. Count is now -121:54
huats021:54
MootBotPrivate +1 vote received. 1 for, 1 against, 0 have abstained. Count is now 021:54
leogg021:55
popey021:55
popey+021:55
MootBotAbstention received from popey. 1 for, 1 against. 1 have abstained. Count is now 021:55
leogg+021:55
MootBotAbstention received from leogg. 1 for, 1 against. 2 have abstained. Count is now 021:55
huats+021:56
MootBotAbstention received from huats. 1 for, 1 against. 3 have abstained. Count is now 021:56
czajkowskiitnet7: ping21:56
czajkowskiwell 4/6 of us have voted21:57
czajkowski[endvote]21:57
MootBotFinal result is 1 for, 1 against. 3 abstained. Total: 021:57
Nafallo5/621:57
popeyyes, 5/621:58
cmpitgAnd...?21:58
czajkowski[agreed] vietnamese team not approved21:58
MootBotAGREED received:  vietnamese team not approved21:58
CoconutCrabokay, thank you all21:58
afterlastangelis this a new mechanism of voting?21:58
huatsI would expect a better applications that put more highlight on the great work I am sure you are doing21:58
popeyafterlastangel: no21:59
cmpitgIt's just the matter of "showing", IMO21:59
czajkowski#endmeeting21:59
MootBotMeeting finished at 15:59.21:59
czajkowskithanks folks for coming21:59
huatsWe would like to come back at the next meeting21:59
huatswith a new application21:59
CoconutCrabwell, we haven't created a habit of reporting everything we do yet21:59
cmpitgMay I have a question?21:59
huatscmpitg, sure22:00
cmpitgWhat did the meeting time change?22:00
leoggi got to run... sorry :( good evening all22:00
cmpitgIt changed 2 minutes after the last fixed time?22:00
popeyit was a mistake22:00
popeywe had an inconsistency between the calendar and the wiki22:00
popeysome of us go by the wiki, some by the calendar22:00
cmpitgThat causes a lot of problems for us22:01
popeyso some turned up at 20:00 UTC and others thought it was 21:0022:01
popeyyeah, it should not have happened, sorry about that22:01
czajkowskithis is the first meeting since dst and it was just unfortunate will be fixed for next month22:01
cmpitgOkay, I see22:01
cmpitgSo if our team is not approved, would we have a chance to do it again?22:02
itnet7sorry... family issues22:02
popeyAbsolutely22:02
cmpitgNext month, right?22:02
czajkowskicmpitg: i'd give it a few monthws22:03
czajkowskimonths22:03
popeyWe generally recommend 3 months22:03
cmpitgI see22:03
cmpitgThank you22:03
cmpitgNext time, we will definitely get it22:03
popeyawesome!22:04
popeyteam reports would help22:04
cmpitgThere is a sort of reorganizing our LocoTeam22:04
popeyregular meetings..22:04
popeyif you need any help, do get in contact with the loco council22:04
cmpitgSo, everything is kind of a mess at the moment22:04
cmpitgpopey: Thank you :-). I will22:04
cmpitgIt's 5:05 AM our local time, probably night at your time.  Good night and see you later!22:06
popeyreally sorry about the time mess up!22:06
=== ptkhanh is now known as ptkhanh|zzz
=== _Tux_ is now known as AWAY|_Tux_
j_baerHello :-)  I have a meetbot question.23:57
persia#ubuntu-bots might be a good place to ask it.23:57
j_baerThanks ... I will switch.23:58

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