/srv/irclogs.ubuntu.com/2010/05/18/#ubuntu-meeting.txt

=== pgraner-afk is now known as pgraner
lifelessis there a asia RMB tonight? persia ?07:12
* persia checks the wiki for those who don't like URLs07:12
persialifeless: I think "no", as the wiki page claims the next meeting is on the 11th.  I suspect the next meeting is really on the 25th.07:14
lifelesspersia: thanks!07:14
=== plars is now known as plars-away
=== doko__ is now known as doko
=== doko is now known as doko_
=== doko_ is now known as doko
dholbachpleia2, Technoviking, popey, nixternal: 9m?11:51
dholbachhum, I guess I'll wait with my 2 agenda items: https://wiki.ubuntu.com/CommunityCouncilAgenda :)12:01
popey:)12:02
persiaAt least the second one really ought be discussed in this timeslot, as interested folks are more likely to be around.12:02
dholbachgiven that it's just boring administrative stuff, I could also take it to email12:02
dholbachI guess it's just a matter of filing an RT ticket12:03
persiaIs it just adjustment of the subscription lists to match the recent selection process?12:03
dholbachyes12:03
persiaOh, then yeah, no point to discussion ;)12:04
dholbachamachu unfortunately didn't find the time12:04
* persia thought it was something more complicated, as it was on the agenda12:04
dholbachwho will send the RT ticket?12:04
persiaheh.  I can do the second one, but not the first, if that helps.  Might be easier to put both in one though.12:04
dholbachthe other discussion is separate12:04
dholbachpersia: thanks a bunch for taking on the rmb asia update!12:05
persiaWhich other discussion is separate?12:05
dholbachI suggested on team-council-members@lists.u.c that we move the list to LP to make updating a bit easier12:05
dholbachI'll prod the discussion again12:05
persiaYeah, that's probably best.  That does need discussion (branding, etc.)12:06
dholbachright-o12:06
dholbachIs there anything more that needs to be discussed?12:06
persiaI think you need quorum to have a meeting, and it's not present, so no point formally ending the meeting :)12:06
dholbachwell, there's people who were interested in discussing these things and we got some stuff sorted out already :)12:08
dholbachso I asked if there was anything more12:08
persiaNot from me.12:09
dholbachok cool12:09
dholbachpopey: all set?12:09
popeynothing here12:10
dholbachalright, thanks everybody :)12:10
czajkowskishort n sweet12:10
popeyI am12:11
Pendulumpopey: you're sweet. I'm not so sure about short.12:11
popeyawww12:12
popey*hugs*12:12
* Pendulum hugs popey back12:12
sabdflhello folks, sorry for being late12:14
popeynp, i think dholbach is taking it to the ml sabdfl12:21
sabdflokdokey12:21
sabdflhappy to be home?12:21
popeyoh yes!12:21
popeykids nearly exploded :)12:22
=== thekorn_ is now known as thekorn
=== txwikinger2 is now known as txwikinger
NCommander#startmeeting14:00
MootBotMeeting started at 08:00. The chair is NCommander.14:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]14:00
ograrool call first ?14:00
davidmG'day NCommander14:00
ogra*roll14:00
asaco/14:01
NCommanderwho's here?14:01
NCommanderGrueMaster: you here?14:02
GrueMasteryep14:02
davidmdyfet, you about?14:02
ograpersia, ?14:02
NCommanderno dyfet or persia :-/14:03
NCommander[link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010051814:03
MootBotLINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/2010051814:03
asac(i think cooloney also attends for kernel parts still)14:03
NCommanderThere are no outstanding action items from last week14:04
NCommander(there were all checked and completed)14:04
ograthe work item link is wrongi think14:04
ograshould be rather http://people.canonical.com/~pitti/workitems/canonical-mobile-ubuntu-10.10.html14:04
ogra(not that it matters since there isnt anything on it anyway atm)14:04
asacI think we should use QA Status standing item to talk about SRU targets or something until first milestone for maverick is out14:05
asacGrueMaster: ^^?14:05
asacwhat do you think?14:05
NCommander[topic] Kernel Status (cooloney)14:06
MootBotNew Topic:  Kernel Status (cooloney)14:06
ograoh, right, i have an action item to add for myself for next meeting14:06
GrueMasterWell, since I don't have a current image, I have nothing to report on image status.14:06
cooloneyoh, actually, nothing new from my side about fsl-imx5114:06
cooloneykernel14:06
ograi talked to slangasek at UDS, we're allowed to SRU bug #568736, NCommander please add an action item for me that i take care14:06
ubottuLaunchpad bug 568736 in netbook-meta "Having Evolution installed along with Desktop-Email is pointlessly redundant" [High,Triaged] https://launchpad.net/bugs/56873614:06
* NCommander coughs14:07
ograwe'll need it for our PPA build14:07
NCommanderStay on topic people :-)14:07
ogracooloney, i think OMAP is the kernel topic for now :)14:07
NCommander[action] ogra to SRU bug #56873614:07
MootBotACTION received:  ogra to SRU bug #56873614:07
cooloneyogra: ok, got it14:07
ograthanks14:07
cooloneyjust discussed with amitk14:07
cooloneyso we are going to use .33 based omap4 kernel code for 10.0714:08
ograright14:09
cooloneyand for 10.10, we will have one more flavor in our kernel master branch named omapmainline14:09
GrueMasterfyi 2.6.34 is out,14:09
cooloneywhich will contains upstream omap3/omap414:09
cooloneyGrueMaster: since 10.07 is critical, and we will try to use the lucid ti-omap branch code base14:09
cooloneyso .33 is much easier14:09
ogranot only that14:09
GrueMasterOk.14:09
ogra10.07 is lucid14:10
cooloneyand ti's git tree is also based on .3314:10
cooloneyyeah14:10
cooloney10.07 is lucid14:10
asaccooloney: will we use -omap (for 3) and -omap4 as subarch in kernel package names?14:10
asacor also rename to -omap3?14:10
ograu-boot uses -omap3 currently btw14:10
cooloneyasac: actually, i plan to use -omap414:10
ogracooloney, any keep -omap14:11
ogra?14:11
NCommanderIts a pain to rename for 10.07 if we do omap3 there, but we should rename the image for maverick14:11
asacright. my question was if you are going for -omap3 or still to -omap for 3 (for maverick that is)14:11
ograNCommander, 10.07 is out of discussion14:11
cooloneybut -omap or -omap4 is not a big problem for me14:11
ograasac, i think the masterplan is to have one -omap kernel in the end (maverick+1)14:11
cooloneyasac: yeah,14:12
ograso the version based fully on mainline should probably stay -omep14:12
ograheh14:12
ogra-omap14:12
cooloneyat end, the omap kernel will be in mainline supporting omap3 and omap414:12
asacok that would be a good line14:12
cooloneyit will be just a flavour14:12
cooloneynot a branch14:12
asacfine with me14:12
cooloneybut before that, we will have a topic branch named omap4patchdump for sync up with ti's patch drop14:13
asacwhat about uboot? do we need to rename that using the same rule?14:13
ografor u-boot you will have -omap3 and -omap4 packages14:13
ograno14:13
asacor will it always be -omap3 vs. -omap4 vs. -omap5?14:13
asacetc14:13
ograbecause they are completely different versioned sources14:13
asackk14:13
cooloneyso, ogra, for 10.07, is -omap4 for PPA better or just -omap14:13
ogra*if* we can have one u-boot source i'll consider calling it -omap14:13
davidmasac, OMAP 3 is planned for 10.10 if at all possible14:13
asacyep.14:14
ogracooloney, i think -omap4 might be better wrt upgrades to maverick14:14
slangasekogra: allowed to SRU> I think I suggested getting a second opinion from pitti or cjwatson, first?14:14
ograsince 10.07 will be installed from scratch we save one package transition14:14
davidmI don't want to drop the community, the Gumstix and Beagle boards are very nice and OMAP 314:14
cooloneyogra: ok, got it.14:14
asacdavidm: ++14:14
ograslangasek, yes, but i'm good at bribing :)14:14
davidmThe 512M Gumstix board is NICE14:15
cooloneycurrently, i git clone the branch from ti's git tree14:15
cooloneyand rebased to our ti-omap branch14:15
cooloneynow fixed the kernel config14:15
ograright, so name the resulting binary -omap414:15
ografor future consistency14:15
cooloneyduring the building, met some compiling issues which should be ti omap4 code's problem14:15
ogratalk to ndec about that please (and put me on CC)14:16
ograwe should probably invite him to this meeting14:16
ograNCommander, can you take an action for that ?14:16
cooloneyso now, i am closed to build a omap4 kernel package14:16
NCommander[action] NCommander to invite ndec to meeting14:17
MootBotACTION received:  NCommander to invite ndec to meeting14:17
ogramakes sense to have him around if he has time14:17
ogracooloney, cool !14:17
ograas soon as you have something to test, NCommander and i have the HW to test it ...14:17
ogracooloney, what target SoCs did you enable yet ?14:18
cooloneyogra: is the kernel and header .deb enough for your testing?14:18
ograno need for the header for now14:18
NCommandercooloney: yes14:18
ograi wont build modules14:18
cooloneyogra: i imported the omap4 defconfig14:18
ograhmm14:18
ograi wonder if there are differences between blaze and panda14:18
ograperferably we want to have both supported14:18
ogrampoirier, !!14:19
ograwelcome !14:19
mpoiriergood morning all14:19
zygahello14:19
NCommanderwelcome14:19
cooloneyomap_4430sdp_defconfig14:19
cooloneyogra: ^^14:19
ogracooloney, sounds pretty generic14:19
asacheh14:19
davidmwelcome mpoirier14:19
ogracooloney, for the omap3 kernel in maverick we seem to lack some patches btw14:20
cooloneyogra: yeah, DSS patches?14:20
ogracooloney, i tried the lucid kernel and cant get the display to work on the touchbook14:20
ograright14:20
ograthere is a bug for that14:20
cooloneyamitk added them14:20
ograbetween lucid and today ?14:20
cooloneyoh, sorry, not that14:21
ograright14:21
cooloneyok, after i build the package i will take a look14:21
ograthere might also be patches for zoom2 that we are missing14:21
cooloneyfor the omap config,14:21
ogra(also omap3)14:21
ogra(and also display related)14:21
cooloneyogra: do you have the working kernel config for your hardware?14:21
ogracooloney, nope, for the zoom i know XorA has it, we can ask him in #ubuntu-arm after the meeting14:22
ografor the touchbook i have to dig it up, but their current kernel is something like 2.6.2914:22
cooloneyogra: good. so for 10.07, which one is our target hardware?14:23
ograwe have general touchbook and zoom2 support in the lucid kernel14:23
ograboth boot fine14:23
ograits just the display14:23
ografor 10.07 its panda and blaze14:23
ograboth omap414:23
cooloneyso, we don't have the kernel configs i guess14:24
ogra10.10 omap3: beagle, zoom, gumstix, touchbook .... 10.07 omap4: blaze, panda14:24
NCommanderanything else or can I moveon?14:24
ogracooloney, we have them enabled already14:24
ogracooloney, (omap3 that is)14:24
cooloneyogra: understand14:25
ogracooloney, for omap3 only DSS2 patches seem to be missing14:25
cooloneyNCommander: i am done, nothing more now14:25
ograand probably sound14:25
ogracooloney, for omap4 we need to get them from TI14:25
NCommanderQA Status (GrueMaster)14:25
ograif there are any specific items at least14:25
NCommander[topic] QA Status (GrueMaster)14:25
MootBotNew Topic:  QA Status (GrueMaster)14:25
GrueMasterI thought we were skipping this?14:26
ograwhy should we ? :)14:26
cooloneyogra: ok, i see14:26
dyfetNCommander: sorry was late getting back14:26
GrueMasterBecause there is nothing to report at this time.14:26
ograGrueMaster, so any masterplan for omap testing ?14:27
GrueMasterGive me boards, testing will happen.14:27
asaci really think we should keep SRU stuff on topic for QA14:27
ogranote that the images will be different14:27
GrueMasterThat's the current plan.14:27
asacso nothing SRU worthy ? fine.14:27
zygawhat is your testing plan if I may ask?14:27
* zyga looks from ubuntu-on-arm qa perspective14:27
ograright, i'd like to hear about that too ... but GrueMaster is right, no testing without HW ...14:28
NCommandermsg davidm do we *really* want ubuntu-on-arm mixing with mobile right now?14:28
NCommanderargh14:28
NCommanderfuck me14:28
GrueMasterI don't know how to define "SRU worthy" wrt the bugs in Lucid.  There are a lot of bugs that need fixing, but I don't know how they affect contract status, etc.14:28
ograGrueMaster, so you should get a gumstix and we need to get you a beagle XM at least for the omap3 testing14:28
davidmNCommander, I'm not sure I understand your question14:28
GrueMasterogra: That would help, yes.14:29
ograGrueMaster, for omap4 we need to wait for the pandas14:29
GrueMasterI am going to look into the gumstix later today.14:29
ograzyga, do you have any suggestions for testing ?14:30
GrueMasterAs to SRU issues, My main issues are kernel on dove & babbage related.14:30
ograwhats open there ?14:31
GrueMasterI'll have to dig up a list, but off the top of my head, bug 559065 and bug 509006.14:32
ubottuLaunchpad bug 559065 in linux-fsl-imx51 "ifconfig eth0 down will cause system hang after fec.c driver update" [High,In progress] https://launchpad.net/bugs/55906514:32
ubottuLaunchpad bug 509006 in linux-mvl-dove "[dove] hibernation failed to resume" [High,Confirmed] https://launchpad.net/bugs/50900614:32
ograah, good14:32
ograGrueMaster, given that we wont build installer images this time, your testing will likely become a bit different14:33
GrueMasterHad I known we were going to look at SRU bugs, I would have compiled a more detailed list.14:33
ograif you work out test plans, try to take that into account14:33
GrueMasterYes, I understand that.14:33
ograyou will dd a fully installed system to SD with the new images that are coming14:33
ograthough oem-config might need special attention here14:34
GrueMasterSo, I have a new server that is currently actively mirroring ports.  I also am mirroring cdimage.ubuntu.com for daily image builds.14:34
ogragreat14:34
NCommandernifty14:34
GrueMasterThat will help immensly.14:34
ograour images will likely also be a lot bigger14:34
zygasorry I had a call14:34
ograso that should help you a lot14:35
zygaogra, not really, I'd like to see what you do currently and how it fits into our plans, perhaps there is some common effort or piece of technology14:35
GrueMasterAs to actual image testing, daily (as long as there is a new image to test) boot testing, then into deep testing with installed apps & some app testing from main.14:35
ograzyga, well, see above, i'm not sure how comparable our images will be to yours14:35
ograGrueMaster, oem-config testing too14:36
GrueMasterGive me a honey-do list, and I'll get a round to-it.14:36
ograthe image will be preinstalled, extend itself to the full SD card size on first boot and fire up oem-config to set upü the user etc14:36
zygaogra, so all testing you do is manual, correct? (unless I missed something)14:36
ograso the special code that resizes needs special attention as well as the setup14:37
ograzyga, yes, its mainly for milestone tests14:37
GrueMasterWhat is the plan for maximum image size ?14:37
* zyga has to go away now, darn14:37
ograsince for daily the archive is unreliable anyway14:37
NCommanderGrueMaster: probably 1GiB ish14:37
ograGrueMaster, we dont have one ...14:37
zygaI'll read the backlog when I get back from lunch14:37
NCommandercompressed14:37
ogra1G would be nice to have14:37
GrueMaster1G is easy.  Leaves room for language support in the image.14:38
NCommanderGrueMaster: not quite, there is no squashfs14:38
ograGrueMaster, the plan is to compress out all spare space and then to extend the system partition to max size of the SD on first boot14:38
ograwe dont know yet how well it will be compressed14:38
ograthere wont be language support beyond english14:39
ograthat will be installed by oem-config in case a network connection exists14:39
ograif not it has to stay english14:39
GrueMasterNo squashfs?  I would recommend it as it makes for easier recovery methods.14:39
ograno14:39
ograwe dont have an installer14:40
ograno squashfs14:40
NCommanderGrueMaster: this is a completely new type of image.14:40
ograits and "oem" image :)14:40
GrueMasterNot really.  This is similar to a Moblin 1.0 image.14:40
ograwhat you dd to the SD card is your install14:40
ograright14:40
GrueMasterAnd Moblin 1.0 used squashfs.14:40
ograits in some areas similar to a moblin image14:40
ograyou cant use squashfs in a sane way14:41
GrueMasterI'm just suggesting that we can still use squashfs.14:41
ografor installed systems14:41
NCommanderfolks14:41
GrueMasterNo?14:41
ograno14:41
NCommanderlets take this offline and bring it back later14:41
ograright14:41
ogralets move on14:41
NCommander[topic] ARM Porting/FTBFS status (NCommander, dyfet)14:41
MootBotNew Topic:  ARM Porting/FTBFS status (NCommander, dyfet)14:41
NCommanderNothing to report, archive still is in too much churn to really see whats broken14:42
* ogra sees libnih, apr, eglibc, kde4libs14:42
ograthe first three definately need some research14:42
ograwell, libnih and eglibc14:42
NCommanderogra: crap, those must be new from last night :-/14:42
ograthey are there since about two weeks14:42
ograeglibc failed with the first upload14:42
* NCommander sighs and thinks he's gone blind14:42
ogralibnih failed short before uds14:43
NCommanderis doko sitll maintaining the armel toolchain?14:43
ograi would hope so14:43
ograasac, ?? °°14:43
ogra^^14:43
ogrado you know ?14:43
asacyes, for now he is our contact14:43
ograok14:43
ograasac, do you know if anyone from your lside will care for things like eglibc ?14:44
ogragiven that its quite essential to have it build14:44
ograor do we need to take action here14:44
asacsame as for toolchain. things might change as we move on, but atm its doko14:45
ograok14:45
dokothe eglibc build failure can be ignored for now14:45
ograok14:45
ograthat leaves libnih14:45
ograNCommander, dyfet, can one of you contact Keybuk ?14:45
ograiirc we had a similar timeout issue before with it14:46
ogra(its hitting the 150 minutes barrier)14:46
ogranot sure why though14:46
NCommander[action] NCommander to poke Keybuk on libnih14:46
MootBotACTION received:  NCommander to poke Keybuk on libnih14:46
NCommanderanything else to bring up?14:47
ogranot here14:47
NCommander[topic] ARM Image Status (ogra, NCommander)14:47
MootBotNew Topic:  ARM Image Status (ogra, NCommander)14:47
NCommanderogra: I have livecd-rootfs voodoo for you14:47
* ogra hangs his head in shame for not having the spec ready yet14:47
NCommanderogra: which spec?14:48
ograNCommander, i saw, i need to go over it a bit deeper ... i'm not really happy with your getopts stuff14:48
ograNCommander, for the image14:48
NCommanderogra: lamont thought it was fine, but feel free to abuse it :-)14:48
ograif lamont says its fine i'm fine too :)14:48
NCommanderogra: BuildLiveCD is a manual merge anyway on the buildds14:49
ograi'm not such a big fan of getopts in shell scripts where you can solve it with a simple case14:49
NCommanderogra: the simple code was causing my eyes to bleed14:49
ograits what we use everywhere14:49
NCommanderlivecd.sh uses getopts14:49
ograsince case is fast and doesnt require external deps14:49
NCommanderer14:50
NCommandergetopts is a bash builtin14:50
ograyes, thats historically from infinity14:50
ogranope not that one14:50
NCommandermcasadevall@daybreak:/home/buildd/src/chroot-scripts$ which getopts14:50
NCommandermcasadevall@daybreak:/home/buildd/src/chroot-scripts$ getopts14:50
NCommandergetopts: usage: getopts optstring name [arg]14:50
NCommanderIts not a built-in?14:50
ogragetopt is builtin14:50
ograand getopts is a standlone prog iirc14:51
NCommanderogra: you've got it backwards14:51
NCommandergetopt is standalone, getopts is built in14:51
NCommander(do which getopt)14:51
ograhmm, k14:51
ograanyway, if lamont is happy i'm happy too14:51
NCommanderwoo, we're all happy!14:51
ograi'll write up the spec before next meeting14:52
ograso we have work items etc14:52
NCommandercool14:52
NCommanderanything else on this topic?14:52
ograbtw, you skipped the work item review14:52
NCommanderogra: bit hard to do it if the burndown charts are broken14:52
ograwe have at least three specs and i know persia was planning on more14:52
ograthey arent broken14:53
NCommanderthe main page is empty14:53
ograwe dont have any specs submitted yet14:53
NCommanderOh14:53
ogradavidm needs to approve etc etc14:53
NCommander[topic] Work Item Review14:53
MootBotNew Topic:  Work Item Review14:53
=== Ubot-Tn is now known as MaWaLe
ograbut indeed we need to have them written and workitems added etc first14:53
ograso i have three to add here14:53
ograone is the rootfs building without root permissions14:54
ograone is upanel14:54
ograand one is the new image14:54
ogradoes anyone else have any specs that will be on the tracker ?14:54
* pitti waves14:54
ograas i said i know persia had some planned14:54
NCommanderarm softbootloader14:55
keesheya piit14:55
ograbut i dont know which14:55
NCommanderimproved arm subnarch14:55
keeser, pitti14:55
ograNCommander, does that make any sense ? if we only support one arch ?14:55
dyfetwhile it was done under the arm track, I am not sure where the ofono spec will be under...14:55
ogra(softbootloader i mean)14:55
ogradyfet, arm i guess14:55
ogradyfet, talk to asac about it14:55
dyfetogra: ok, let's assume that for now then...and I will discuss with asac separately14:56
ograNCommander, also did cjwatson have a look at your plans to change the installer for subarch ?14:56
NCommanderogra: not yet, will do this week14:57
ogragreat14:57
ograso lets make sure we have them given to davidm by next meeting for approval14:57
ogracan you make an action for all of us to have all specs ready for the tracker by next week ?14:58
NCommander[action] Mobile team to have spec completed by next week14:58
MootBotACTION received:  Mobile team to have spec completed by next week14:58
NCommanderdone14:58
ograpreferct14:58
NCommanderOk, we're short on time :-/14:58
ograor so14:58
ograright, but we're done, no ?14:58
NCommander[topic] AOB14:58
MootBotNew Topic:  AOB14:59
NCommanderI wanted to discuss changing the meeting time14:59
ogra..14:59
NCommanderbut we don't have time this meeting14:59
ograright and no persia around14:59
ogralets defer that14:59
NCommanderso if you have a suggestion for a new meeting time, email it to me, and we'll vote next week14:59
NCommanderI think that's eventhing14:59
ogra++14:59
NCommanderg'night folks14:59
NCommander#endmeeting14:59
MootBotMeeting finished at 08:59.14:59
sabdflnicely timed14:59
NCommanderogra: one more + and you'll disconnect14:59
ogra:)14:59
asacheh ;)14:59
sabdfl#startmeeting15:00
MootBotMeeting started at 09:00. The chair is sabdfl.15:00
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]15:00
KeybukHey15:00
sabdflhowdy scott15:00
keeshello15:00
cjwatsonhi15:00
sabdflmdz around?15:00
pittio/15:01
mdzsabdfl: yes15:01
sabdflhi pitti, hi matt15:01
sabdfla full house15:01
mdzI was just sending you an SMS15:01
sabdfli look forward to it :-)15:02
mdzI aborted15:02
mdzhttps://wiki.ubuntu.com/TechnicalBoardAgenda15:02
sabdfl[TOPIC] Action review15:02
MootBotNew Topic:  Action review15:02
sabdflScottK, Riddell, any process on KDE update policy?15:02
pittioh, isn't that the agenda from last time?15:02
cjwatsonI suck across the board on actions.  I'll get to at least the meeting minutes this week15:03
sabdflhmm15:03
sabdflto pitti's point, i think it is, yes15:03
pittihttps://wiki.ubuntu.com/TechnicalBoard/TeamReports/Current has the actions from last time, FTR15:03
sabdflok15:04
sabdflpitti: Canonical patent licenses question, settled?15:04
pittigot a reply from Amanda and replied to Reinhard and tb@15:04
pittiso, done15:04
sabdfland soyuz sync-source?15:04
pittimy branch landed15:05
cjwatsonregarding the Kubuntu unseeded package set thing there, we discussed this at UDS and I think the conclusion was to do something different15:05
pittiand it's rolled out, so done15:05
cjwatsonoh good, I can stop explicitly saying -S unstable then15:05
sabdfland MoM is marked done in the agenda, thanks cjwatson15:05
cjwatsonyep15:05
sabdflso, does the absence of a new agenda mean there are no new items? should i resent this agenda to standing items?15:06
KeybukI added items today15:06
mdzalso, the chair should scan the mailing list as noted on the agenda15:06
pittiThere is the "release schedule" mail from Robbie15:06
KeybukStatus of sparc and ia64 ports, and status web page (Scott)15:06
Keybukis new15:06
pittiI guess the case is pretty much closed for maverick, though :)15:07
sabdflok15:07
sabdfl[TOPIC] 10.10.1015:07
MootBotNew Topic:  10.10.1015:07
sabdflrobbie makes good data15:07
sabdflthere are a couple of useful insights, i think:15:07
sabdfl - equal weeks don't make equal cycles15:07
mdzto repeat what I said on the list:15:08
mdzFor my part, I like the idea of balancing out the amount of "actual work"15:08
mdztime we have in each cycle, though I think that aligning with GNOME *does*15:08
mdzmatter to us.15:08
sabdfl - releasing very late in the month is potentially hairy15:08
sabdflagreed on the GNOME front15:08
sabdflcan we separate those two, and start with the nuanced cycle bit?15:08
mdzI also think this is a release team decision, not a tech board one15:09
sabdflinput from the tech board was solicited and is welcome15:09
mdzI'm sure input from the TB is welcome, but the release team needs to be a part of it15:09
cjwatson... I think the release team might well punt on this given in particular that we'll be changing RM this cycle15:09
pittiso, Robbie's proposal basically means to release the fall cycle earlier, and by and large keep the sprint cycle, right?15:09
pittii. e. in the spring cycle we would have a better change of fitting gnome x.y.115:10
pittiwhich is nice because LTSes are in spring15:10
sabdfl+115:10
cjwatsonwe have certainly noticed an "autumn cycles tend to produce worse releases" pattern in the past15:10
sabdfli read it as "second week in october, third week in april"15:10
pittiand for fall we would then have to SRU the lot (or cherrypick)15:10
cjwatsonI don't know that any of us had thought hard about the precise causes of that15:10
Keybukpitti: I did a bit of digging, and found that we've tended to cherry pick the bug fixes in anyway before the .115:11
Keybukat least all the ones that had LP bugs filed15:11
Keybukso that didn't worry me so much15:11
pittiKeybuk: for lucid, yes; since we knew that we got late15:12
pittiwe did a couple of git snapshots before15:12
pittias I said, it's doable, just takes some more packaging work15:12
keesI remain on the fence.  moving up from the end of the month is good, but losing time on the release makes me uncomfortable, especially due to the disconnect with the previous cadence.15:12
pittiso, Robbie's proposal sounds fine to me, and has a better balance between the cycles, too15:12
Keybukit would worry me if we released before GNOME's .0 though ;-)  but that's also why I suggested we set our cycle early, to resist the urge for GNOME to slip their cycle :p15:12
keesI do like equalizing the devel time.15:13
cjwatsonmy main position is, I think, still that we're sending a pretty mixed message about cadence; it does help that we're trying to establish a future rhythm but what happens when the next marketing opportunity comes along? :-)15:13
pittiequalizing> unless we actually want to keep the schema of having slightly more time for LTS cycles?15:13
pittimarketing opportunity> how did we miss releasing dapper on the 6.06.2006? :-)15:14
sabdflLTS cycles get the winter break, for better or worse15:14
sabdflpitti: i think certain remixes might have ;-)15:14
pittisabdfl: it already was 6.06, after all15:15
mdzI think we're spending too much time rationalizing this15:15
cjwatsonthe historical pattern that autumn releases tend to be worse seems to suggest that more development time => suckier15:15
mdzrobbie has put a lot of work into finding a reason to do what sabdfl wants to do15:15
sabdflwell, let's not spend even more time on it now, then :-p15:15
mdzexactly15:15
mdzI could come up with 10 reasons for or against15:16
pitticjwatson: I seriously doubt that it's just due to the time; we just tend to introduce more structural changes before and after LTSes15:16
mdzthis isn't a decision which is motivated by a desire to improve the release process, so let's not cloud the issue15:16
keesI can produce no good technical reason to oppose the date change, so I support it.15:16
sabdflare there any objections to framing our cadence as "2nd week in october, third week in april"? to avoid the last week issue?15:18
mdzI frankly don't see an issue with the last week15:18
pittimdz ++; it never hurt us and it gave us a good alightment with gnome15:18
sabdflit always makes me nervous, but it's not actually been a problem yet15:19
keesit offers no way to slip without changing the release version.  :)15:19
mdzkees: sure it does15:19
sabdflmdz: would you see a problem with releasing 11.04 on, say May 2nd if a wart crops up late?15:19
mdzwe choose the release numbers; they don't choose us15:19
mdzsabdfl: not even slightly15:19
sabdflit would make for very, very bad publicity15:19
mdzbeing late would make for bad publicity15:19
sabdfli think some of us are more sensitive to the potential for headlines than others15:20
mdzbut we need to be pragmatic; problems do turn up and sometimes being late is the best option15:20
cjwatsonthe only issue I see with the last week is the cost-of-bandwidth thing15:20
mdzthe release number is really a minor concern15:20
sabdflthat's true. but it would amplify the headline.15:20
cjwatsonI don't see an operational concern, given the number of times that we've had late problems and managed to deal with them one way or another15:20
sabdflagreed with cjwatson, though, there's a real benefit to fitting the release deluge inside a month15:21
mdzeven if we did want to change it, that's a repeatable process at this point15:21
cjwatsonyes, it puts stress on the release team, but given our structure the stress is not significantly reduced by the difference between one-day-late and one-day-late-and-next-month15:21
cjwatsonwe know that one-day-late is a Very Bad Thing regardless of the dates15:21
cjwatsonand it depends on how the calendar works out; 24th of April (say) wouldn't be a significant problem15:23
sabdfltrue15:23
sabdflbut third week would always have slack for the bandwidth tail to... tail15:23
cjwatsonI don't know that we need to make the definition as complex as that of the date of Easter though :-)15:23
cjwatsonI would rather that we had a little discretion either way, and were up-front about that15:24
mdzcan we rescope this discussion to the decision at hand? we don't need to re-engineer the release schedule in general in this meeting, just decide on what to do about *this* release15:24
KeybukIn a sense, since Robbie has already changed the schedule on the wiki page, and the Google Calendar15:24
Keybukthe decision is should the TB overrule him and restore the original Release Schedule15:25
Keybukno?15:25
mdzKeybuk: no15:25
mdzhe was very explicit about calling that a proposal, a draft, etc., and he also directly asked the TB to decide15:25
Keybukyes, but he's since made the Proposal the Schedule15:25
sabdflto weigh in. you made the point that 10.10.10 is a marketing issue, and the marketing team have also weighed in.15:26
mdzand the release team is apparently abstaining15:26
pittiFWIW, I have almost no problem with 10.10.10, given the rather special gnome situation this time15:26
sabdflmdz: the reason i'm pursuing the multi-release perspective, is to address your point about GNOME sync15:26
sabdfli think we should take the opportunity now to publish our release dates through till 12.0415:27
mdzsabdfl: yes, I did. I also asked what we will do with this marketing opportunity to make it worthwhile15:27
sabdflwant to settle this current matter, then take that on15:27
Keybuksabdfl: Robbie has already done so, and announced them15:27
Keybuk(as drafts)15:27
mdzsince changing the date doesn't seem like it will make a big splash15:27
cjwatsonit seems cute but I don't see it making a difference with people on the other side of the chasm15:28
cjwatsonand I still think the Sunday thing is going to be an operational issue15:29
cjwatsonis our webmaster going to be available on Sunday, for instance?15:29
pittiwe'd need to have the images ready on Friday, I think; we can't expect the full release team and testers to work over the weekend; just pushing the announcement and the web page15:30
Keybukhttps://wiki.ubuntu.com/MaverickReleaseSchedule15:30
KeybukRobbie has published the release schedule15:30
cjwatsonyeah, but we know that that last bit involves fairly significant coordination15:30
Keybukthis release schedule is *not* marked as a draft, and has the release date as 10.10.1015:30
Keybukthere is no objection from the release team15:30
Keybuk(that I can see)15:30
cjwatsonin practice, it takes a couple of hours of quite intensive work15:30
Keybukand the consensus that I'm hearing from this board appears to be that it's either not this board's decision, or the board as a whole doesn't hate it15:31
sabdflour webmaster says he's up for it, and it sounds like a cool plan :-)15:31
Keybukso I suggest we respect Robbie's decision to publish the release schedule15:31
mdzKeybuk: I'm not seeing your point. are you saying there's no decision to be made and we can go home?15:31
Keybukand move on to the next topic15:31
Keybukmdz: I'm saying someone has already made the decision, so we don't need to15:31
mdzKeybuk: that I agree with15:32
sabdflok then. 10.10.10 it is.15:32
Keybuknothing in our board's "constitution" states that once somebody has forwarded us a question, they can't decide on their own answer15:32
mdzbut those someones have made a point of bringing the issue to the TB anyway15:32
Keybukthis is on the agenda because of robbie, and robbie has clearly made up his own mind ;)15:32
sabdfland in doing so, prompted valuable discussion15:32
Keybukyeah, I fully agree the discussion is valuable15:33
sabdfl[TOPIC] Varying the cadence for slightly longer April cycles15:33
MootBotNew Topic:  Varying the cadence for slightly longer April cycles15:33
KeybukI don't want to set a dangerous precedent that the board overrules people without a stated objection :)15:33
cjwatsonnext time, perhaps we could have the discussion before announcements at UDS? ;-)15:34
sabdfli heard two objections: one, that we should sync with GNOME, and two, that a nuanced cadence weakens our sotry around cadence in general15:34
sabdfldo folks think that consulting GNOME now, and publishing a schedule for the next two years, is feasible?15:34
mdzcjwatson: or skip discussion altogether15:34
cjwatsonconsulting them is feasible, but I don't know that expecting external projects not to have their own reasons for temporary variation over the course of two years is feasible15:35
Keybuksabdfl: I think so; we have a draft for the next two years, and jcastro is a GNOME Board member, so would know who to consult with15:35
Keybukat least then they'd know our plans, so would be able to take their own decisions with a little light15:35
pittisabdfl: schedule for next two years should be fully possible, and Robbie by and large worked those out already15:36
sabdflwould GNOME be sensitive to the winter break argument too?15:36
sabdfli'm wqondering if the dynamic might be different for them, in that regard?15:36
pittiI'm happy to take the action of asking the GNOME RM about this change15:36
Keybukand I think we'd want to be flexible enough that should they have a strong reason to break their cycle (and ours), we would be willing to change ours15:36
sabdflperhaps "we get MORE done over holidays"?15:36
Keybukthe release schedule shouldn't be a rock to dash ourselves against15:36
sabdflagreed15:36
mdzI haven't looked at the 11.10 or 12.4 schedules15:36
mdzbut 11.4 looks OK to me15:37
sabdflcan i propose we approach them to have the discussion, taking Robbie's data, and seeing if they have similar or divergent forces at work?15:37
sabdflwith a view that we can, if the stars align, publish both our schedules for this next two year cycle?15:37
KeybukI imagine right now they're more worried about their current release's schedule, and how ridiculously far behind they are with it <g>15:38
sabdflthis would have a number of benefits15:38
Keybukbut it would be a good conversation to have, yes15:38
sabdflone of which would be being able to book UDS venues further in advance15:38
sabdflwe struggle, when the dates are set with less than 12 months notice, at our scale15:38
mdzI think that's more because we change the venue every time15:39
cjwatsonthe UDS dates already seem to have several weeks of slack either way, from recent memory?15:39
cjwatsonthough I agree that it would be nice to have them a bit more consistent relative to the release15:39
sabdflrepeating the venue would be appreciated by the organising team, i think, if folks are up for that. but that's a separate topic.15:40
sabdflwould Jorge be the right person to task with opening up that dialogue?15:41
cjwatsonI thought that was the organising team's decision :)15:41
mdzcjwatson: they tend to get a lot of "input" into that decision15:41
Keybukdoes anyone really mind if UDS tends to repeat venues, if the venues are good?15:42
mdzsilbs has proposed selecting the same venues for a couple of years to come, and I think that's wise15:42
* pitti notes that selecting venues isn't really TB matter :)15:42
mdzpitti: it is, however, something that needs to be considered when setting dates for UDS15:43
sabdfl[VOTE] TB invites Jorge to work with GNOME to see if a release schedule till 12.04 is feasible, and if the dynamics around April releases are similar15:43
MootBotPlease vote on:  TB invites Jorge to work with GNOME to see if a release schedule till 12.04 is feasible, and if the dynamics around April releases are similar.15:43
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:43
MootBotE.g. /msg MootBot +1 #ubuntu-meeting15:43
* persia holds the faint hope that the lack of venue preselection means UDS might happen in Asia once in a while15:43
jcastroI can take that action to GNOME15:43
macopersia: :)15:44
Keybuk+115:45
MootBot+1 received from Keybuk. 1 for, 0 against. 0 have abstained. Count is now 115:45
pitti+115:45
MootBot+1 received from pitti. 2 for, 0 against. 0 have abstained. Count is now 215:45
kees+115:45
Keybuk(on the basis jcastro just said it was ok :p)15:45
MootBot+1 received from kees. 3 for, 0 against. 0 have abstained. Count is now 315:45
mdz+115:45
MootBot+1 received from mdz. 4 for, 0 against. 0 have abstained. Count is now 415:45
sabdfl+115:45
MootBot+1 received from sabdfl. 5 for, 0 against. 0 have abstained. Count is now 515:45
sabdfl[ENDVOTE]15:46
MootBotFinal result is 5 for, 0 against. 0 abstained. Total: 515:46
sabdflok15:46
sabdflif we can, that gets us a roadmap to 12.04, and opens up the possibility for planning UDS and other sprints further in advance15:46
sabdfl[TOPIC] Sparc and IA64 status and web page15:47
MootBotNew Topic:  Sparc and IA64 status and web page15:47
sabdflscott?15:47
Keybukright, just collecting notes15:47
Keybukat UDS, there was a session on the current status of the Sparc and ia64 ports15:47
cjwatsonsorry, I missed the vote above; I'm +1 on that as well15:47
KeybukI agreed to bring the result of that discussion to the TB for a formal vote15:47
Keybuksparc is in a poor state, it has no current maintainer, and there are numerous issues with the toolchain and kernel such that it basically does not boot, etc.15:47
Keybukthe recommendation from the discussion is that the TB should send a general mail announcing this fact, and that should a maintainer team not come forwards to work on it, the port should be dropped at Maverick Feature Freeze15:48
pittiI should add that sparc caused quite some extra effort durign lucid for manually removing uninstallable binaries, cleaning up NBS/uninstallables, etc.15:48
Keybukia64 is in a better state, it's largely good, just needs an active maintainer team15:48
Keybukso in the same mail we should encourage people to work on it (but won't drop it right now if they don't)15:48
cjwatsonI'm always very cautious about dropping ports, but if we give clear and sufficient notice (as the plan seems to be) then I'm less concerned15:49
Keybukalso I agreed to put together a wiki page summarises the current state of the ports, https://wiki.ubuntu.com/ArchitectureStatus15:49
Keybukso, does the TB agree with this approach, and if so, can we vote to approve the result of the discussion?15:49
mdzI think it's important that we not underestimate the cost of ports15:49
mdza port which virtually nobody uses, even if it has an active maintainer team, is not a net benefit to the project15:50
keesdo we have any download stats for the ports?15:50
mdzthe rest of us do trip over it in various ways, e.g. archive admin as pitti mentioned15:50
cjwatsonthere are also benefits to ports which are easy to forget15:50
pittipowerpc is still fairly popular, judging by bug reports that I got15:50
mdzkees: yes15:50
cjwatsonI'm not disagreeing on the costs, but it isn't all negative15:51
Keybukpitti: powerpc was not discussed, the port is in a good state15:51
mdzwhen I want a quick summary, I usually look at http://torrent.ubuntu.com:6969/15:51
Keybuk(has active maintenance, etc.)15:51
mdzthough we can get additional data if that's desired15:51
pittiKeybuk: right, that referred to "port that nobody uses"15:51
sabdflis "armel" a special port of arm, or is it the primary one?15:51
persiaThe primary one15:51
persiaARM Extended ABI, Little Endian (I believe)15:52
mdzubuntu-10.04-desktop-ia64.isohas 3 downloads, and I believe there are two seed servers15:52
Keybuk"el" being someone's silly idea of a joke15:52
mdzcompared to 5377 for i38615:52
Keybukthough isn't el big-endian technically? :p15:52
sabdflmdz: i was going to ask for the picture version of that :-)15:52
cjwatsonsabdfl: "arm" is the old abi, and the new one required a new architecture name15:53
cjwatsonwe've never had an arm architecture in Ubuntu15:53
mdzsabdfl: just imagine a grain of sand in the irish sea15:53
sabdfl:-)15:53
Keybukradioactive sand?15:53
sabdfli have a beach on the irish sea close by. there is no sand. there is, in fact, mostly rotting seaweed :-)15:54
mdzwe also build kubuntu, xubuntu, server and alternate versions for ia6415:54
sabdflKeybuk: what would qualify for "maintainer team" for IA64, in your mind?15:55
mdzjust in case the one user wants more choice15:55
persiaThere are a number of active Ubuntu developers who run ia64: it may be worth seeking greater input on which flavours they run.15:55
sabdfli've heard no objections to putting SPARC on notice, some concern about not doing the same for IA6415:55
Keybuksabdfl: one or more people contributing patches to the toolchain and kernel, and actively helping with FTBFS issues15:56
Keybukthe concern in the discussion about putting ia64 on notice was15:56
Keybuk(a) lamont was there :p15:56
mdzI volunteer to get download data for both ia64 and sparc15:56
Keybuk(b) ia64 builds tend to pick up bugs that affected amd64 at runtime15:56
sabdflthe latter is interesting15:56
keesfor "b" I though those scripts had been bolted to the amd64 buildds too now?15:56
mdzKeybuk: what kind of bugs?15:57
Keybukkees: the theory was that building things on ia64, with its stricter ABI, means that certain runtime failures get caught at build time15:57
Keybukalignment issues and whatnot15:57
persiakees: Only based on some common issues, but not all cases.15:57
mdzsounds like something that compiler or linker flags would do more effectively than a port15:57
slangasekmissing prototypes causing implicit pointer->int casts15:57
keesokay15:57
cjwatsonia64 and amd64 both have 64-bit pointer and 32-bit int15:57
kees(but if no-one is looking at ia64 failures, it doesn't have any value...)15:58
slangasekand yes, my understanding is that the build-time check (which is a build log filter, not a compiler feature) is enabled now on am64 too15:58
mdz-Werror=implicit-function-declaration I believe15:58
slangasekif it isn't, it ought to be done ASAP15:58
cjwatsonif you have the implicit casts slangasek mentions (which are a very common bug), then they completely hose ia64 because it tends to scatter pointers liberally through the whole 64-bit space15:58
cjwatsonbut amd64 only notices sometimes, because its pointers tend to be packed down in the bottom 4GB when possible15:58
cjwatsonso you only notice once you start using enough memory15:58
mdzlet's call it an "accidental feature"15:59
cjwatsonwe've caught quite a few problems due to ia64 binaries failing during builds, AIUI15:59
cjwatsonmdz: this kind of accidental feature is rife with ports15:59
mdzit doesn't sound like a reason to maintain an entire port15:59
sabdflmdz: you mean, build images?15:59
mdzsabdfl: I mean, compile packages15:59
cjwatsonthe reason I support a reasonably rich (but not to Debian or NetBSD levels!) port ecosystem is that each port we have tends to catch an interesting set of problems of its own15:59
slangasekmdz: -Werror=implicit-function-declaration is overly broad; lamont has a script that greps the logs and detects the explicit combination of missing declaration + implicit cast15:59
mdzthough there are certainly intermediate levels we could consider15:59
cjwatsonand then, when we have to bootstrap a new port, we don't find ourselves needing to fix everything at once15:59
mdzlike compiling the packages and throwing them away16:00
mdzif we just want build testing16:00
cjwatsonI don't think this is a reason to maintain all the CD images we do maintain, say16:00
sabdflok16:00
cjwatsonthere are some explicit casts which break ia64 but aren't caught by compiler flags, btw16:00
cjwatsonIIRC it used to be fairly common to stuff pointers into ints for glib callbacks16:01
sabdfldo we need to vote, or can we simply support keybuk's proposal, modulo mdz's desire to set the bar quite high for maintainership of IA64?16:01
sabdflthere are no community bugs, ftr16:01
cjwatsonI'm entirely happy with Keybuk's proposal16:01
sabdflme too16:01
mdzI would like to suggest a different tone16:01
KeybukI'd like to find out whether the board feels that ia64 should suffer the same deadline?16:02
mdzthe message sounded like "someone please step up to maintain this thing because we want to keep it"16:02
mdzwhile I think it should be "we propose to drop this because it isn't adding enough value to the project; if you have a good reason to keep it AND are willing to step up and maintain it, please get in touch"16:02
sabdflwhat i heard was "building the packages is useful, publishing them is useful to quite a lot of people, but making images turns it into an official exercise we aren't comfortable with"16:03
KeybukI'll take an action to draft that mail, and send it to the TB list for review there16:03
sabdfl+1 to mdz's language, from me16:04
mdzKeybuk: did hppa come up at all?16:04
cjwatsonthere's probably no reason, incidentally, why people with ia64/sparc needs couldn't deal with installations by way of netboot installation16:04
Keybukmdz: hppa is not a port16:04
kees+1 on language. +1 on sparc schedule, +1 on at least dropping ia64 image builds.16:04
cjwatsonmdz: why would it?  we removed it16:04
mdzoh, right16:04
mdzfor 9.1016:05
Keybukzombie hppa?16:05
persiaIt was touched briefly in the session, but nobody wanted to consider reviving it.16:05
mdzKeybuk: no, just looking cross-eyed at the list of isos16:05
Keybukit rose from the dead crying "BRRRAAAAAAAAAINS"16:05
sabdfl:-)16:05
sabdflok16:05
sabdfl[TOPIC] Community bugs16:05
MootBotNew Topic:  Community bugs16:05
sabdflthere are none16:05
sabdflany comments?16:05
KeybukI am happy with there being no bugs16:06
sabdfl[TOPIC] Any other business?16:06
MootBotNew Topic:  Any other business?16:06
sabdfl316:06
sabdfl216:06
persiaThere was a session about flavour testing at UDS: would the TB have an interest in being a piont of approval for flavour definitions?16:06
sabdfli'd like that on my business card, yes16:06
persia(the alternative being to delegate entirely to the release team(16:06
sabdflpiont of approval16:06
sabdflthat'll get them wondering16:07
KeybukI looked that up, before I realised it was a typo16:07
persiaSorry.  New laptop this week, with very different keyboard.16:07
sabdflflavours being.... ?16:07
pittipersia: hm, not sure what you mean; xubuntu et al are already on the iso tracker, being tested, etc.?16:07
pittialthough these aren't called "flavour" usually16:07
persiapitti: Right.  So if someone wants a new one, is this a TB item, or just up to the release team?16:07
persiaWhat aren't called "flavour"?16:08
sabdfli'd say release team16:08
pittipersia: "derivatives"?16:08
pittijust want to ensure that we talk about the same thing16:08
persiapitti: That language was *supposed* to change in feisty, but communication has been weak :)16:09
cjwatsonwell, speaking of which, Lubuntu approached us asking for hosting16:09
persiaBut yeah, same thing.16:09
persiaThat would be a current example, yes.16:09
cjwatsonfor the time being, I've said that we are too pressed for space on cdimage to be able to offer hosting, but that we could perhaps e.g. accommodate them on the ISO tracker as a partial compromise16:09
persiaanother likely to approach in maverick would be liquid/kubuntu-mobile (depending on integration efforts)16:09
pittiif/once we can drop some ports images, we might have more16:10
cjwatsonbut if it came to full-blown hosting, I'd expect to be bringing it to the TB16:10
sabdfli think the bar has to be pretty high for us to provide hosting16:10
persiaimages aside: there's changes in lots of other places as well.16:10
persia(LP, cocoplum, livecd-rootfs, debian-installer, ubuntu-cdimage, etc.)16:10
* kees has to go to another appointment...16:10
cjwatsonyes, full hosting implies things such as their development processes being integrated with Ubuntu16:10
sabdflpersia: topic for next TB16:11
slangasekcjwatson: accomodating them on the ISO tracker w/o having image respins under the control of the release team on antimony poses some practical workflow problems for milestones16:11
sabdflwhich will be chaired by....16:11
KeybukI feel like I haven't chaired in a while16:11
cjwatsonslangasek: yeah, I know - it was a suggestion rather than a decision, and I'm open to exploring it16:11
sabdflalphabetical rotation, wasn't it?16:11
persiaIf it's a TB thing, then I'll draft it that way, and submit for review, and if the TB decides to delegate, we can change it.  Thanks :)16:11
KeybukI think I was on leave, when I was supposed to chair, so it went from kees->pitti16:12
sabdflok, Keybuk it is16:12
sabdfl#endmeeting16:12
MootBotMeeting finished at 10:12.16:12
sabdflthanks all and sorry for the overrun16:12
pittithanks all16:13
=== nhandler_ is now known as nhandler
=== yofel_ is now known as yofel
=== kirkland` is now known as kirkland
* manjo waves 17:58
* manjo pokes cking 17:59
* vanhoof looks in17:59
ckingmanjo, eh?17:59
* cking here17:59
* smb drags himself in17:59
apwRoll Call17:59
* ogasawara waves17:59
* jjohansen1 waves17:59
* manjo waves17:59
* cking waves17:59
=== jjohansen1 is now known as jjohansen
* tgardner is here17:59
apw#startmeeting17:59
MootBotMeeting started at 11:59. The chair is apw.17:59
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]17:59
mpoiriergood morning all17:59
kamalo/18:00
smb\o18:00
apw[LINK] https://wiki.ubuntu.com/KernelTeam/Meeting18:00
apw[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick18:00
apw#18:00
apw# NOTE: '..' indicates that you are finished with your input.18:00
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/Meeting18:00
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick18:00
apw#18:00
apw[TOPIC] Outstanding Actions18:00
apwNone from last meeting18:00
MootBotNew Topic:  Outstanding Actions18:00
apw[TOPIC] New Bodies18:00
MootBotNew Topic:  New Bodies18:00
smbI want one18:00
apwWelcome to all those new bodies who have joined us since the last meeting!18:00
apwthose of you who are here might want to say hi18:01
apw..18:01
manjowelcome18:01
mpoirierhello18:01
vanhoofhi :)18:01
* apw expects a couple more18:01
aboganihi18:01
* smb waits for lag 18:02
lagHello18:02
apwAnyhow welcome all ...18:02
apw[TOPIC] UDS/Blueprints (all)18:02
MootBotNew Topic:  UDS/Blueprints (all)18:02
apwWith UDS behind us its time to get all the discussion into the blueprints, to get the outcomes distilled out, and the work items onto the blueprint whiteboards.  Please ensure that your blueprint is assigned to someone in the team, that it is targetted to a sensible Maverick milestone, that it has a priority set, and that it has a Series Goal of Maverick.18:02
apwWe will start to expect status reporting for the open blueprints from next meeting.  If you are an assignee, you will be expected to report progress or delegate someone to do so.  Please ensure your blueprint is shown on the release status page (url below), and if not talk to ogasawara or apw so we help sort it out.18:02
apw[LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick18:02
MootBotLINK received:  https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Maverick18:02
apw..18:02
ogasawaraapw et al: I'll send a gentle reminder about blueprints/work items to the mailing list as well18:03
* apw warns you things are not in the normal order, so be ready :)18:03
apwogasawara, ack18:03
apw[ACTION] ogasawara to email out reminder regarding blueprint disposition18:03
MootBotACTION received:  ogasawara to email out reminder regarding blueprint disposition18:03
apw[TOPIC] Status: Maverick overall (ogasawara)18:03
MootBotNew Topic:  Status: Maverick overall (ogasawara)18:03
ogasawaraFor those who haven't yet heard, we'll be targetting the 2.6.35 kernel for Maverick.18:04
ogasawaraWe'll be rebasing to 2.6.34 final today and uploading.  Next will be to get the changes from the UDS config review integrated as well as changes noted from the UDS delta review.18:04
ogasawaraFor any brave souls wanting to try Maverick's current kernel, it's available at https://edge.launchpad.net/ubuntu/+source/linux/2.6.34-2.918:04
ogasawara..18:04
apw[TOPIC] Status: Security & Bugfix Kernels (smb/gnarl/sconklin)18:04
MootBotNew Topic:  Status: Security & Bugfix Kernels (smb/gnarl/sconklin)18:04
smbDapper:      2.6.15-55.83  (updates)18:04
smbHardy:       2.6.24-27.69  (updates)18:04
smbIntrepid:    --- End of Support ---18:04
smbJaunty:      2.6.28-18.60  (updates)18:04
smbKarmic:      2.6.31-21.59  (updates)18:04
smb - mvl-dove  2.6.31-213.27 (updates)18:04
smb - fsl-imx51 2.6.31-111.27 (updates)18:04
smb - ec2       2.6.31-306.14 (updates)18:04
smbLucid:       2.6.32-22.33  (updates)18:04
smb - mvl-dove  2.6.32-204.16 (release)18:04
smb - fsl-imx51 2.6.31-607.13 (release)18:04
smb - ti-omap   2.6.33-500.6  (release)18:04
smb - qcm-msm   2.6.31-800.2  (release)18:05
smb - ec2       2.6.32-305.9  (release)18:05
smbCurrently working on security updates. Following that there are quite a few18:05
smbstable updates for Lucid.18:05
smbGiven the number of topic branches I expect pain.18:05
smb..18:05
sconklin..18:05
apwsmb have we got a work-item for the slamming back of fsl-imx51 to karmic ?18:05
smbapw, action me18:05
smbI think not18:05
apw[ACTION] smb, to add work item for updating karmic fsl-imx51 in line with lucid18:05
MootBotACTION received:  smb, to add work item for updating karmic fsl-imx51 in line with lucid18:05
apw[TOPIC] Release Metrics (JFo)18:06
MootBotNew Topic:  Release Metrics (JFo)18:06
apw /me pokes JFo in the ribs18:06
tgardnerJFo is sufferuing from ubuflue, so might not be around.18:06
apwahh ... ok ...18:07
* apw will take that under advisment18:07
apw[TOPIC] Incoming Bugs: Regressions (JFo)18:07
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)18:07
* apw takes that one as well18:07
apw[TOPIC] Incoming Bugs: Bug day report (JFo)18:07
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)18:07
apwseeing the pattern ?18:07
apw[TOPIC] Open Discussion or Questions: Anyone have anything?18:07
MootBotNew Topic:  Open Discussion or Questions: Anyone have anything?18:07
tgardnergive it up, dude18:07
apw#18:07
apw# NOTE: 'o/' to indicate you have a topic, chair will call you forward18:07
apw#18:07
kamalo/18:07
apwkamal, go18:08
kamalSome of my Dell Studio 155x patches have been accepted to -stable.  Yay!   I'm sick.  :-(  UDS ----  wow!18:08
kamal..18:08
apwsounds good, we should get those shortly via smb then18:08
* smb saw something18:08
manjoo/18:08
apwmanjo, go18:09
manjoany changes to SRU policy for Maveric ?18:09
smbmanjo, no18:09
* JFo is here now18:09
apwsmb, presumably we are back to non-LTS sru policy18:09
JFoapologies for being late18:09
smbapw, Yes, though that is already documented18:09
apwJFo, ok ... will call your sections in a sec18:09
JFok18:10
apwany other, any other business ?18:10
manjo..18:10
apw[TOPIC] Release Metrics (JFo)18:10
MootBotNew Topic:  Release Metrics (JFo)18:10
JFoRelease Meeting Bugs (none yet)18:10
JFo===18:10
JFoRelease Targeted Bugs (none yet)18:10
JFo * 0 linux kernel bugs18:10
JFo * 0 linux-fsl-imx51 bugs18:10
JFo * 0 linux-ec2 bug18:10
JFo * 0 linux-mvl-dove bugs18:10
JFo===18:10
JFoMilestoned Features -18:10
JFo * 15 blueprints18:10
JFo    18:10
JFo===18:10
JFoBugs with Patches Attached:13218:10
JFohttps://bugs.edge.launchpad.net/ubuntu/+source/linux/+bugs?field.has_patch=on18:10
JFoBreakdown by status:18:10
JFohttp://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/18:10
MootBotLINK received:  http://qa.ubuntu.com/reports/ogasawara/csv-stats/bugs-with-patches/linux/18:10
JFoI plan to do a review of patch attached bugs this week18:11
JFohopefully that number will drop drastically18:11
JFo..18:11
apw[TOPIC] Incoming Bugs: Regressions (JFo)18:11
MootBotNew Topic:  Incoming Bugs: Regressions (JFo)18:11
JFoIncoming Bugs18:11
JFo1134 Lucid Bugs18:11
JFoCurrent regression stats (broken down by release):18:11
JFo==== regression-potential ====18:11
JFo  * 317 lucid bugs18:11
JFo==== regression-update ====18:11
JFo  * 26 lucid bugs18:11
JFo  * 9 karmic bugs18:11
JFo  * 5 jaunty bugs18:11
JFo  * 2 intrepid bugs18:11
JFo  * 2 hardy bug (up 1)18:11
JFo==== regression-release ====18:12
JFo  * 141 lucid bugs18:12
JFo  * 52 karmic bugs18:12
JFo  * 21 jaunty bugs18:12
JFo  * 10 intrepid bugs18:12
JFo  * 3 hardy bugs18:12
JFo==== regression-proposed (no change) ====18:12
JFo  * 1 lucid bug18:12
JFo  * 1 karmic bug18:12
JFoI've not yet removed Intrepid, but I shall as it is EOL18:12
apwsounds good, rip it out18:12
JFoplease note the large amount of regression-release bugs for Lucid18:12
JFook, will do18:12
JFo..18:12
apwyeah we need to remember to focus on lucid regression-release bugs in the early cycle18:13
JFoyep18:13
apwthis is an LTS and we care as we have to have this baby about forever18:13
apw[TOPIC] Incoming Bugs: Bug day report (JFo)18:13
MootBotNew Topic:  Incoming Bugs: Bug day report (JFo)18:13
JFoBug Days will start back after next week. I plan to send out an announcement for the next one early in the week with a reminder the business day before.18:13
smb\o18:14
apwsounds good ...18:14
manjosince we SRU kittenkillers only should we mark all lucid bugs milstone to maveric ?18:14
apwsmb, go18:14
smbJust on the Lucid release bugs, we should try to get the pending stable updates queued up into proposed and revisit then18:14
apwmanjo, we don't know if they are even in maverick18:14
JFoI agree smb18:14
JFo..18:15
manjoapw, right, so if !fixed in maveric18:15
apwwe actually do fix bugs whcih affect users in lucid too btw18:15
manjoif you looks at jfos list its huge18:15
apwyeah we have a fair few bugs in there18:16
smbapw, manjo It should be in the SRU policy for the next 3 months18:16
smbAfter that rather kitten killers but for LTS also enablement to a degree18:16
smb..18:16
apwsmb, seems the SRU message is not getting out, we should have had a session on it at UDS18:17
apw...18:17
manjo+118:17
apwi think thats everything18:17
apwshout now if you have anything more18:17
apw#endmeeting18:17
MootBotMeeting finished at 12:17.18:17
kamalthanks apw18:18
apwthanks everyone18:18
smbthanks apw18:18
JFothanks apw18:18
ckingditto18:18
lagCheers18:18
* lag runs for the door18:18
* manjo bye18:18
=== JFo is now known as JFo-afk
zulserver team meeting?18:57
ttxzul: in 3 min, yes18:57
sommero//18:57
RoAkSoAxo/18:57
Davieyo/18:58
zulyo18:58
Davieykirkland looking forward to it? :)18:58
ttxo/19:00
ttxWelcome everyone19:00
mathiaz/o//^9819:00
hggdh~o~19:01
ttxto another season of the exciting adventures of the Ubuntu Server team19:01
ttx#startmeeting19:01
MootBotMeeting started at 13:01. The chair is ttx.19:01
MootBotCommands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]19:01
DavieyOoooooo19:01
zulis it a sequal?19:01
ttxAgenda is up at https://wiki.ubuntu.com/ServerTeam/Meeting19:01
zulor a prequal19:01
smoser\019:01
ttxsmoser is the lucky scribe19:01
smoserah. joy.19:02
ttx[TOPIC] Review ACTION points from previous meeting19:02
MootBotNew Topic:  Review ACTION points from previous meeting19:02
ttxNo ACTION that I can find19:02
* mathiaz agrees19:02
ttx[TOPIC] Maverick blueprints and specs (ttx)19:02
MootBotNew Topic:  Maverick blueprints and specs (ttx)19:02
ttxSo, while we recover from 5 (10?) days away from home, it's time to start drafting specs19:03
ttxPlease have a look at specs where you are set as drafter, and set them to "Drafting" if you started drafting19:04
ttxI didn't manage to sync with Jos after UDS on potential reassignments19:04
* Daviey doesn't have any, and would be happy to volunteer some if people are overloaded.19:04
ttxso please just take what you care the most about for now (or what you think will be assigned to you anyway)à19:04
ttxDaviey: I expect kirkland to offload some of his UEC specs to the rest of the team19:05
ttxDaviey: if not, I've one for you :)19:05
DavieyOh joy :)19:05
ttxDaviey: but I'll wait for Jos to confirm first :P19:05
Davieyok.19:05
ttxSpamapS: you should get a few too19:06
ttxSpamapS: hiding won't help you19:06
zulhehe19:06
ttxAny question on the blueprint/specs side ?19:06
mathiazttx: yes19:07
mathiazttx: what's the deadline for spec writing?19:07
SpamapSttx: Jos assigned a few of the blueprints to me already19:07
mathiazttx: and how does it play with the first iteration of the cycle?19:07
* SpamapS still will attempt hiding tho19:07
ttxmathiaz: that's a good question.19:07
* ttx looks19:07
RoAkSoAxSpamapS: i'll ping you later on this week to discuss cloud-loadbalancing autoregistration. I alraedy have an idea on how to implement it :)19:08
mathiazttx: should the WI be defined for all BP?19:08
SpamapSttx: is there a good wiki page on spec writing somewhere?19:08
ttxFeature Definition Freeze is on Jun 17th19:08
SpamapSRoAkSoAx: excellent, I look forward to hearing what you have in mind.19:08
mathiazSpamapS: https://wiki.ubuntu.com/SpecTemplate19:09
ttxI'd expect specs to be filed and approved by May 27th19:09
hggdhbeing rather new, directions on spec writing are also welcome19:09
mathiazttx: when does the first iteration start?19:09
mathiazhggdh: https://wiki.ubuntu.com/SpecTemplate19:09
ttxmathiaz: but again, haven't synced with Jos on the new release schedule yet19:09
mathiazhggdh: SpamapS: use the SpecTemplate as template for the wiki page19:09
ttxmathiaz: it's already started, in a way19:10
mathiazto outline what needs to be done19:10
RoAkSoAxSpamapS: :) we'll discuss that later this week since I believe we didn't have enough time at UDS session to discuss it19:10
mathiaznot all the sections will be needed19:10
mathiazthe focus is on getting the design section written19:10
ttxmathiaz: https://wiki.ubuntu.com/MaverickReleaseSchedule shows A2 is already started19:10
hggdhmathiaz: thanks19:10
ttxmathiaz: however, we can consider being in Iteration planning this week and the next19:10
mathiazthe implementation section has been superseeded with Work Items in the BP whiteboard19:11
mathiazhggdh: SpamapS: see https://wiki.ubuntu.com/WorkItemsHowto for we're tracking work items19:11
ttxmathiaz: Pending another direction, consider they are due for approval by May 27th, which means must be submitted for review by May 25th19:11
smoserit would be nice if mathiaz would update the spec template to indicate that19:12
mathiazsmoser: that == implmentation?19:12
smoseryes19:12
mathiazsmoser: I don't think it's official yet19:12
ttxSpamapS: i'll talk you through the process offline19:12
mathiazsmoser: it's more what I've found out last cycle19:12
ttxSpamapS: after the meeting19:12
mathiazsmoser: ttx may have another opinion on the use of the implementation section19:13
mathiazsmoser: moreover the SpecTemplate is a wiki template used throughout the whole Ubuntu project19:13
ttxmathiaz: no, I agree with you.19:13
mathiazsmoser: some team may choose to still use the implementation section19:14
smoserit surely would make sense to have it mentioned there at least "You may replace this with the work item tracker <link here>"19:14
ttxmathiaz: Sometime I use that section as a tracker when things are not easily tracked by work items19:14
ttxmathiaz: but that's purely optional and depending on the work needed19:14
* ccheney is here too btw, forgot to announce earlier19:15
ttxOtherwise, this is the merging period, so please have a look at https://wiki.ubuntu.com/UbuntuDevelopment/Merging19:15
mathiazfor me, the design section == what we're trying to do (ie the end goal, the results)19:15
mathiazand the implementation section == how we get there, which step, the plan (-> Work items)19:15
ttxmathiaz: for me, the Design discusses how we'll achieve the goal technically, and Implementation/WI show the detailed step by step plan19:16
* kirkland is having irc proxy issues, but i'm here19:16
ttxkirkland: o/19:16
mathiazttx: right - I think we're in agreement here19:16
ttxOK, any other question on that ?19:17
kirklandttx: please repeat any questions that were directed at me up until now19:17
Davieymathiaz / ttx: Can you write a summary on the ML/Wiki?19:17
ttxDaviey: As soon as I have confirmed the deadlines with Jos, sure19:17
mathiazI'm planning to use diagrams this cycle (following up on my whiteboard experiement at UDS) :)19:17
Davieysuper19:17
ttx[ACTION] ttx to confirm spec submission deadlines with Jos19:17
MootBotACTION received:  ttx to confirm spec submission deadlines with Jos19:17
ttx[ACTIOn] ttx to walk SpamapS through the spec process19:18
MootBotACTION received:  ttx to walk SpamapS through the spec process19:18
mathiazDaviey: are you asking for a summary of the spec guidelines as well?19:18
Davieymathiaz: yes.. in diagram form :)19:18
ttx<ttx> Daviey: I expect kirkland to offload some of his UEC specs to the rest of the team19:18
ttx<ttx> Daviey: if not, I've one for you :)19:18
Davieymathiaz: There seems to be some confusion/agreement.. and would be nice to have something to refer to.19:18
ttxkirkland: ^ (answering Daviey asking for some drafting work)19:19
* mathiaz opens his 32nd document in Dia19:19
* Daviey hopes kirkland's irc proxy issues are continuing19:19
* sommer chuckles19:19
kirklandDaviey: yep, i'm here19:19
kirklandttx: will do19:19
ttxAny other question on specing/merging ?19:20
ttxMoving on to...19:20
ttx[TOPIC] Weekly Updates & Questions for the QA Team (hggdh)19:20
MootBotNew Topic:  Weekly Updates & Questions for the QA Team (hggdh)19:20
ttxhggdh: o/19:20
hggdhnothing new on the eastern front19:20
* hggdh still recovering19:20
ttxhggdh: are you going to be assigned the new UEC testing spec ?19:21
ttx(or expecting to be assigned)19:21
hggdhttx: I would expect so, and was considering drafting it (with help from mathiaz and smoser)19:21
ttxhggdh: ok, makes sense19:21
ttxI don't have any other questions... Team ?19:22
zulnope19:22
Davieynot here19:22
hggdhI have one19:22
hggdhmay I start looking at NTP bugs?19:22
ttxhggdh: shoot19:22
zulhggdh: im for it19:22
ttxhggdh: you may start looking at any bug :)19:22
hggdhheh. I meant I will specialise on them, if all agree19:23
hggdhand slowly take over the world19:23
zulim all for taking over the world19:23
ttxhggdh: no problem. You need to start working on package bugfixes anyway, to get exposure19:23
hggdhttx: ack19:23
ttx[TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)19:23
MootBotNew Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)19:23
jjohansenhey19:23
ttxhggdh: thanks19:23
ttxjjohansen: o/19:23
jjohansenso nothing really new on the kernel front19:24
ttxI would have been surpised if we had :)19:24
ttxI don't have questions or bugs for you yet :)19:24
mathiazI have one - but not really related to -server hw19:25
jjohansenwell smoser does, but I haven't made any progress on it since yesterday :)19:25
mathiazI just got my new x20119:25
jjohansenmathiaz: nice19:25
jjohansenwhat is the issue?19:25
mathiazand the external display isn't working19:25
ttxless nice.19:25
mathiazthere are also some issues with the graphic driver19:25
Davieywell would be a shame to let jjohansen go empty handed.. any news on the kernel issue with my "server" bug #576601?19:25
mathiazthere is a bug about it though19:25
ubottuLaunchpad bug 576601 in linux "[MacBookPro 7,1]mcp89 sata link reset fails, no disks detected" [Medium,Triaged] https://launchpad.net/bugs/57660119:25
jjohansenmathiaz: bug #19:26
mathiazjjohansen: bug 55456919:26
ubottuLaunchpad bug 554569 in linux "[lucid] Blank screen with KMS on Thinkpad X201 with Arrandale (i915)" [Undecided,Invalid] https://launchpad.net/bugs/55456919:26
jjohansenDaviey: sadly no progress I know of there19:26
mathiazjjohansen: ^^ you get a blank screen when to try to install from the iso19:27
mathiazI hope it will be fixed with 10.04.119:27
Davieyjjohansen: thanks19:27
mathiazwell - that's all I had for the kernel team19:28
jjohansenmathiaz: hrmm okay I'll look into it and get back to you with what I find19:28
* ttx moves on19:28
mathiazjjohansen: great - thanks19:28
ttx[TOPIC] Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review  (mathiaz)19:28
MootBotNew Topic:  Weekly SRU review: https://wiki.ubuntu.com/ServerTeam/KnowledgeBase#SRU%20weekly%20review  (mathiaz)19:28
ttxincluding Changes discussed at UDS on SRU tracking19:28
mathiazhm - right19:29
mathiazso bug 57594519:29
ubottuLaunchpad bug 575945 in chkrootkit "chkrootkit falsely flags files owned by Firefox 3 and Sun Java 6 valid packages" [Low,Incomplete] https://launchpad.net/bugs/57594519:29
mathiazis nominated for hardy19:29
mathiazand two bugs for lucid19:29
ttxmathiaz/zul: I propose that we move to the new model starting next week19:29
zulack19:29
ttxthough explaining it first today would be nice19:29
mathiazttx: ok - that's going to require some work though19:29
mathiazttx: ie - some WI and development19:30
ttxmathiaz: for the tracking yes, but to replace the nomination review, maybe not ?19:30
mathiazso following up on the sru-process discussion at UDS19:30
ttxI meant switching nomination review from meeting to ML19:30
mathiazwe'll move the nomination review to the ML19:30
mathiazttx: a script needs to be develop to generate the list of bugs to review for nominations19:31
ttxmathiaz: hmm, ok. Maybe we should wait before switching then19:31
mathiaz(which should also include the list of bugs closed)19:31
ttxmathiaz: and continue until the spec is written19:32
mathiazttx: that's why I think we should write a BP for the sru-process as well19:32
ttxack19:32
mathiazas there will be some development work required19:32
ttxok, let's keep the current process until we have a plan for this19:32
ttx(and resources assigned to make it work)19:32
mathiazok19:33
* ttx looks at this week's nominations19:33
ttxbug 575945 is incomplete -> decline19:33
ubottuLaunchpad bug 575945 in chkrootkit "chkrootkit falsely flags files owned by Firefox 3 and Sun Java 6 valid packages" [Low,Incomplete] https://launchpad.net/bugs/57594519:33
mathiazttx: just accepted19:34
mathiazas mdeslaur seems to have a backport ready in a PPA19:34
ttxah, ok19:34
mathiazbug 57470419:34
ubottuLaunchpad bug 574704 in munin "munin-node after update to Lucid still in /etc/rc*.d, invoked twice" [Medium,In progress] https://launchpad.net/bugs/57470419:34
ttxI'll defer to check on this one19:34
ttxto Chuck19:34
zulthat one needs more testing19:34
mathiazzul: SRU worth?19:35
ttxzul: you intend to SRU it ?19:35
zulyeah i do19:35
* mathiaz accepts the bug then19:35
mathiazbug 57691019:35
ubottuLaunchpad bug 576910 in php5 "Regression: getPathInfo() doesn't return parent info" [Undecided,Confirmed] https://launchpad.net/bugs/57691019:35
zuli havent seen that one19:35
zulyeah i can see that one being sru19:36
ttxI'd say yes19:36
Davieywould be nice if the reporter gave an example of something it broke.19:36
zulfreaking php ;)19:36
mathiazhttp://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html19:36
MootBotLINK received:  http://qa.ubuntu.com/reports/ubuntu-server-team/fixedbugs.ubuntu-server.latest.html19:36
mathiaz^^ anything SRU worth on this list?19:36
ttxmathiaz: nothing from me19:37
zulmost of those i seen sru's for already19:37
zulie dovecot19:37
mathiazalright - then that's all19:37
ttx[TOPIC] Open Discussion19:37
MootBotNew Topic:  Open Discussion19:37
ttxAnything/anyone ?19:38
Davieysommer: If you want a hand with your doc's spec, do shout out for it. :)19:38
* ttx introduces SpamapS, a new team member that will care about our Web/Ops stack19:39
DavieySpamapS: o/19:39
sommerDaviey: will do... there's some good discussion on the ubuntu-doc list at the moment19:39
* ttx doesn't introduce Daviey, a new team member that everyone already knows.19:39
Davieysommer: I'll follow it.19:39
zulboo19:39
Davieybah19:39
zulhehe19:39
mathiazand ccheney that joins the server team for some time as well19:39
ccheneyyea! :-)19:40
ttxsommer: I was wondering if, as discussed at UDS, you'd like a weekly slot in the team meeting (like QA and kernel ?)19:40
ttxmathiaz, ccheney: indeed ! Too many new people, I get lost19:40
SpamapSHi everyone. :)19:40
SpamapSsorry I was still reading list of bugs for SRU consideration.19:41
ttxSpamapS: you have to be faster :P19:41
sommerttx: maybe... I'll have more time to stay up to date this cycle so I think we'll see how it goes19:41
SpamapSttx: Thats precisely what the bus drivers were trying to teach us wasn't it?19:41
Davieyttx: can we go home now? :)19:42
SpamapSDaviey: meaning "can I take my pants off now?"19:42
smoseri think it should be clarifid that Davey and SpamapS are new members to the Canonical Server Team.19:42
smoserDaviey is by no means new to the Ubuntu Server teeam19:42
DavieySpamapS: you need to check your US to UK translations. :)19:42
ttxDaviey: ok, ok19:43
SpamapSDaviey: I'm using Benny Hill's US<->UK dictionary.. is that not a good one?19:43
ttx[TOPIC] Announce next meeting date and time19:43
MootBotNew Topic:  Announce next meeting date and time19:43
ccheneysmoser: Also, I am a member of the Canonical Desktop Team on loan to Canonical Server Team for this release cycle.19:43
ttxNext week, same time, same place19:43
Daviey:(19:43
SpamapSRoAkSoAx: do you want to chat about load balancing now or later?19:43
ttxDaviey: you can go to your dinner now :)19:43
* sommer +119:43
hggdhheh. For me, lunch19:44
Daviey\o/19:44
RoAkSoAxSpamapS: as you prefer19:44
ttx#endmeeting19:45
MootBotMeeting finished at 13:45.19:45
juancarlospaco2Holas20:51
juancarlospaco2Hello20:52
juancarlospaco2Bonjour20:52
PabloRubianeshola/hello20:52
juancarlospaco2traje mate20:53
jorgevazq1juancarlospaco2: hay forma de que me llegue hasta Mexico=20:53
jorgevazq1?20:53
jorgevazq1jajaja20:53
unimixhey PabloRubianes, juancarlospaco2, jorgevazq1 !20:54
leoggjuancarlospaco2, paselo nomas :)20:54
PabloRubianeshola unimix20:54
juancarlospaco2solo si hay forma de que unos Tacos lleguen hasta Argentina...20:54
gnunezrjorgevazq1: Lo puedes conseguir en el palacio de hierro, en la sección de "Delicatessen", si mal no recuerdo20:54
jorgevazq1juancarlospaco2: hmm20:54
jorgevazq1lo pensare20:54
juancarlospaco2:)20:54
jorgevazq1jajaja20:54
jorgevazq1gnunezr: en serio? pero no estoy en la ciudad de Mexico20:55
jorgevazq1estoy un bastante más al norte20:55
gnunezrPalacio de hierro hay en todos lados, no?20:55
jorgevazq1gnunezr: nope20:55
gnunezrUh... Prissa?20:55
jorgevazq1creo que nada más en DF, GDL y MTY20:55
jorgevazq1Prissa?20:55
jorgevazq1esa no la conozco20:55
gnunezrEllos no siempre tienen20:55
jorgevazq1hmm20:55
juancarlospaco2bienvenida sofia20:56
jorgevazq1buscaré en Sanborn's20:56
juancarlospaco2welcome sofia20:56
jorgevazq1saludos sofiavitale20:56
sofiavitalehola a todos20:56
juancarlospaco2:)20:56
gnunezrUh, buena suerte :p20:56
jorgevazq1jajajaja el juancarlospaco2 todo bilingüe20:56
jorgevazq1gracias gnunezr20:56
juancarlospaco2sep20:56
jorgevazq1PabloRubianes: y es la primera vez que intentan oficializarse?20:56
PabloRubianessi jorgevazq120:56
jorgevazq1oh, deja hago un cambio20:57
juancarlospaco2hablo español, ingles, klingon, na'vi, python20:57
juancarlospaco2XD20:57
unimixjuancarlospaco2, lol !20:57
=== jorgevazq1 is now known as jorgevazq
slangasekjuancarlospaco2: tendrás que decirnos qué tal el language-pack-gnome-tlh20:57
juancarlospaco2:)20:57
jorgevazqPabloRubianes: pues mucha suerte20:58
jorgevazqnosotros es la segunda vez, a ver cómo nos va20:58
juancarlospaco2hay que pagar derecho de piso20:58
juancarlospaco2jajjjajajaj chiste20:58
juancarlospaco2XD20:58
juancarlospaco2que fea esa palabra eh...20:58
PabloRubianesgracias jorgevazq20:59
paultagHey all21:00
jorgevazqhi paultag21:00
paultagwe will be starting in one sec -- hold on21:00
paultag:)21:00
jorgevazqpaultag: ok21:00
PabloRubianeshey paultag!21:00
jorgevazqumm21:00
paultaghowdy PabloRubianes :)21:00
jorgevazqubuntu-mx contact should be here soon21:00
PabloRubianespaultag: :S :D21:00
jorgevazqhe was literally rushing home from work21:01
paultagAs per usual Ubuntu protocol we will be starting this meeting just a few minutes late :)21:01
jorgevazqhowdy, jamesjedimaster21:01
jamesjedimasterhi jorgevazq21:01
jorgevazqpaultag: thanks, pal!21:01
juancarlospaco2lol21:02
huatswho is late ?21:02
huats:)21:02
huatsnot me:D21:02
popey:)21:03
juancarlospaco2not late, just different UTC   :)21:03
juancarlospaco2XD21:03
paultagHa!21:03
paultagUTC+001021:03
popeyok, lets get started21:03
jorgevazq'k... brb, gotta brush my teeth... I kinda feel weird to speak in public right after mealtime21:03
popeyhttps://wiki.ubuntu.com/LoCoCouncil/Agenda21:03
popeySo first item on the agenda is Uruguay LoCo Team reapproval..21:04
popeyer approval :)21:04
paultagthere it is ;)21:04
PabloRubianesHere21:04
popeyhey PabloRubianes21:04
PabloRubianeshello popey21:04
popeyanyone else here for Uruguay?21:05
efebei'm from uruguay ;)21:05
PabloRubianesyes sofiavitale and Julin digan hola21:05
Julinhola!!!!21:06
sofiavitalehola!21:06
Julinvamo arriba ubuntu uruguay!21:06
Julineso se podia?21:06
popey:)21:06
PabloRubianesmost people is working at this time here21:06
itnet7PabloRubianes: same here21:06
juancarlospaco2yeah im "working"21:07
popey:)21:07
juancarlospaco2:)21:07
popeyPabloRubianes: do you log your irc meetings?21:07
PabloRubianesthe important ones yes, and the others we provide a sumary on the website21:07
popeyI see you hold events recycling computers, how successful has that been?21:08
paultagYeah, Hardwaraiser, what's that about21:09
PabloRubianesvery nice21:09
PabloRubianeswe try to ask for unused hardware and put together computers21:09
PabloRubianesthen we give them to poor schools in the rural areas21:10
paultagPabloRubianes, about how many machines do you donate each year?21:10
PabloRubianesabout 521:10
paultagoutstanding21:10
popeyI love the Centros de Distribucion idea!21:10
PabloRubianesevery year, we are about to start this year21:10
popeythats brilliant21:10
PabloRubianespopey: the thing is here internet is not so fast21:11
PabloRubianeswe have to give alternatives to download21:11
paultagPabloRubianes, can you tell me a bit about some of your past events? Have you held installfests and the like?21:11
popeySure, but i love the idea of people burning CDs for the price of a blank disc21:11
PabloRubianesyes we been part of the last two Years "Flisol"21:12
huatsPabloRubianes, that was something I was about to ask you, if you exchange with other Locos21:12
huatsthat is great21:12
PabloRubianesthere you take your computer and a voluntary install Ubuntu for you21:12
PabloRubianeshuats: lately we start to work on #ubuntu-es-locos we are trying to work with other locos which speak english21:13
PabloRubianesspanish sorry21:13
paultag:)21:13
paultagPabloRubianes, do you guys participate in translation work?21:13
huatsPabloRubianes, yeah I have figure out21:13
juancarlospaco2i was, but the translator team rejected me :(21:14
PabloRubianesnot many people here know english that's the problem21:14
PabloRubianesjuancarlospaco2: me too21:14
paultagAh21:14
itnet7PabloRubianes: what are your teams plans for the near future?21:14
PabloRubianeswe are going to publish a magazine21:14
itnet7I see some listed, but what I mean is what are you most passionate about21:15
PabloRubianesand form a Education Team in order to give online courses21:15
juancarlospaco2mayor colaboration with Bleachbit, until translator member becomes mandatory, they reject me, cant collaborate anymore21:15
PabloRubianesand lately education institutions are asking us to give talks to parents and teachers21:16
itnet7Very cool21:16
PabloRubianesthe Plan Ceibal was a huge success for linux here21:17
huatsHave you been part of the global jam ?21:17
huatsor do you plan to ?21:18
PabloRubianesno, we have problems to find a place, without having to pay, but the next one I think we are going to join21:18
paultagPabloRubianes, how do you plan to change how you operate if you become an approved team and have access to the resources of an approved team21:18
huatsPabloRubianes, for the record I have done my first one in a bar with an internet connection21:18
huatsit might be an idea...21:18
paultaghuats, +1 !!21:18
popeyhttp://www.ubuntu.org.uy/main/?q=node/1304  who made those tutorials?21:19
PabloRubianeshuats: that's good idea21:19
huatsPabloRubianes, the idea behind jam was a group of people gathering around a pizza to ork on bugs...21:19
huatsso you can even do that in someone's house... I think efrain did that:)21:20
PabloRubianeshuats: we are weird we held the release party on a university and gave talks21:20
juancarlospaco2mmm pizza21:20
huatsPabloRubianes, why do you say weird ?21:20
PabloRubianesthere was a too formal party21:20
paultagBah!21:20
popey:)21:20
paultagI did that too. It's awesome21:20
popeyeach to their own21:20
paultagPabloRubianes, how do you plan to change how you operate if you become an approved team and have access to the resources of an approved team21:20
PabloRubianesno, I think we are gonna provide with the cds canonical send to the approved locos to the Centros de Distribucion21:21
PabloRubianesbut we set a course when we form the community council and we are gonna stick to it21:22
itnet7PabloRubianes: popey was interested in who created the videos, were you involved, or is there a part of your team that contributes through tutorials?21:22
PabloRubianesno I want't part21:23
itnet7http://www.ubuntu.org.uy/main/?q=node/130421:23
paultagPabloRubianes, do you know who created them?21:23
PabloRubianesI think Julin found them on other page and put it there,21:24
popeyuseful resource21:24
itnet7That is still really cool!!!21:24
paultagIt would be really cool to get more of those21:24
paultagPabloRubianes, being part of the Ubuntu Beginners Team, you could really help new users who es :)21:24
PabloRubianesyes they are really good21:25
paultagonly speak es *21:25
PabloRubianesthis videos are made by a member of our loco http://sites.google.com/a/ubuntu.org.uy/montevideo/tutoriales/video-tutoriales21:25
paultagwell done21:26
popeyi like the separate sites for regions of Uy21:27
popeyok we ready to vote on Uruguay team approval?21:27
itnet7yes!21:27
paultagsure am21:27
leoggyep21:27
popeyI'm going to +121:27
leogg+1 here21:27
paultag+1 here, too21:27
itnet7+1 for me as well!21:27
paultaghuats, *poke*21:28
itnet7:-)21:28
huats+1 too21:28
paultag:)21:28
huatsthanks paultag21:28
paultaghuats, sure thing :)21:28
popeywin21:28
popeycongratulations PabloRubianes21:28
huatscongrats !21:28
PabloRubianesTHanks!!!!21:28
paultagCongrats PabloRubianes! :)21:28
leoggvamo uruguay! :)21:28
jorgevazqfelicidades Uruguay!21:28
itnet7Congrulations to ubuntu-uy!!21:28
PabloRubianesbut's not only me!21:29
leoggcongrats guys21:29
jorgevazqkeep up the good work21:29
gnunezrArriba el paisito!!! :D21:29
unimixcongratulations PabloRubianes and the Ubuntu-uy team ! You deserve it ! Good work !21:29
efebecongrulations :)21:29
itnet7great job, and we look forward to the future and what your team will achieve21:29
pcapelutoQue grande Uruguay!!!!!!!!  GRACIAS PABLO!!!!!!21:29
paultagaye, we have high hopes :)21:29
PabloRubianes:D21:29
* popey has invited ubuntu-uy to locoteams-approved21:29
efebemuy bien pablo y el resto de ubuntu-uy felicidades :)21:29
popeyPabloRubianes: you should get an invite mail21:29
PabloRubianesthanks a lot to the people who help me to make the approval application21:30
magu42Gracias Pablo!!! thanks the council  :-)21:30
paultagthank you guys :)21:30
itnet7magu42: thank you21:30
magu42itnet7» :-)21:30
PabloRubianespopey: ok!21:30
pcapelutoThank you very much at all, the whole community waiting for this moment21:30
Toluxeroclap clap21:30
sofiavitalethanks!!!21:31
juancarlospaco2Uruguay pays the beer21:31
juancarlospaco2lol   XD21:31
ToluxeroxD21:31
pcapelutojajajajaj21:31
popeyright, who's up next?21:31
leoggjuancarlospaco2, +121:31
jorgevazqwiii21:31
jorgevazqMexico's next!21:31
Toluxerojorgevazq, relax21:32
popey:)21:32
rkgarciaXD21:32
* jorgevazq excited, sorry21:32
itnet7jorgevazq's excited, now worries :-)21:32
itnet7no worries21:32
itnet7I meant *21:32
jorgevazqhohoho21:32
Toluxerohahaha21:32
itnet7:-P21:32
Toluxerolalala21:34
* paultag is reading21:34
* jorgevazq is anxious21:34
paultaghold on Mexico, we're still here :)21:34
popeySo Toluxero, https://wiki.ubuntu.com/UbuntuMxTeam/Eventos/Flisol2010 can you tell us about this event?21:34
Toluxeropopey, ok, this event is the "festival latinoamericano de software libre"21:35
itnet7Toluxero: how does your team participate?21:36
popeywhat was theplan?21:36
Toluxeroin this event, me represent a the community21:36
* Toluxero is nervous21:37
juancarlospaco2:s21:37
itnet7Do you help with installations, or recruit for your LoCo, or help users with issues?21:37
itnet7Don't be nervous you are among friends :-)21:37
Toluxerook21:38
Toluxerosorry21:38
popeywe need a bit more detail I think.21:38
ToluxeroI participated in both installing and conferences21:38
Toluxeroin this event21:38
Toluxeroand distribution of CD's21:39
jamesjedimastertalking about the advantages of ubuntu21:39
Toluxero I was also part of the organization staff at one of the Sites21:39
popeycool.21:39
popeyWhere would you say most people in the community "hang out"? forums? irc? mailing list? somewhere else?21:40
jorgevazqpopey: yeah, he even designed Barcoded tickets and all21:40
popeyheh, neat!21:40
jamesjedimastermost people enters the forum for Q&A21:41
jorgevazqalthough IRC is a nice place  to socialize ;)21:41
jamesjedimasterwe provide some answers according to our experiences21:41
huatsDo you have developpers (I mean Ubuntu developpers) in your team ?21:41
jamesjedimasterand when users need faster answers, they can find us at irc21:41
popeydo you get many new people in the forums / irc?21:41
Toluxeropopey, in the forums21:42
itnet7Can you talk a little about your Podcast, and has that helped the Team to grow, and raise awareness for your LoCo and Ubuntu?21:42
jorgevazqI can talk about the podcast21:42
jorgevazqthat's the subteam I guide21:42
jorgevazqwell, we have been downloaded over 1,000 times, counting all three episodes21:42
juancarlospaco2i need to sudo reboot will be back...21:43
jorgevazqwe believe it has helped us to be known21:43
popeyany more episodes planned?21:43
jorgevazqpopey: yes21:43
jorgevazqactually21:43
jorgevazqwe're planning a special episode for Lucid Lynx21:43
itnet7Nice!21:44
leoggjorgevazq, cool21:44
jorgevazqwe plan to gather many types of "ubuntu users"21:44
jorgevazqsuch as students21:44
jorgevazqdesigners21:44
jorgevazqprogrammers21:44
jamesjedimasterengineers21:44
jorgevazqinternet-café owners21:44
jorgevazqand so forth21:44
Nuunmusicians21:44
jorgevazqso that they can actually share why they liked ubuntu (specially Lucid), and how it makes their life easier21:45
huatsAre you planning to participate in the global jam ?21:45
jlbritoHola21:46
jamesjedimasterhuats: we haven't talk about the jam, but sometime in the near future :)21:46
Toluxerohuats, it  is in our plans to do so21:46
paultagjorgevazq, What do you see as the strongest part of your team?21:46
paultagerm jamesjedimaster *21:46
jorgevazqpaultag: the loco contact is Toluxero21:47
paultagsorry! I've been reading21:47
paultagToluxero, to you, then -- What do you see as the strongest part of your team?21:47
Toluxeropaultag, the support to new users21:48
Toluxeroin the forum21:48
jamesjedimasterI think the experience of old linux users, and the curiosity of the new ones21:48
Toluxerothe forum is the door to anothers projects of the team21:48
paultag:)21:48
jorgevazqand they later join us on IRC, or other teams21:48
Toluxeroin projects: we are also planning a school-oriented project21:50
Toluxeroright now, the doc team is working on a knowledge database21:51
huatsdo you have plans to try to grow your community ?21:52
Toluxerohuats, sure!21:53
huatscan you elaborate a bit more ?21:53
huats:)21:53
Toluxerowe want to create local communities in every state21:53
Toluxeroactually a recent community was created: ubuntu-mx-df21:54
jorgevazqdf stands for "distrito federal", the official name of Mexico City21:54
Toluxero(rest 31)21:54
huatsand what will be the role of each of that local community ?21:54
juancarlospaco2:)21:56
jorgevazqwell, each local community may hold its own events21:58
huatsok21:58
jorgevazqwhich would be more succesfull, for distance is currently one of our biggest obstacles21:58
jorgevazqin that aspect21:58
huatsjorgevazq, ok21:58
jorgevazqwe would also expand and disclose ubuntu trhoughout the country more effectively, for every region would have its own strategy (according to their situation)21:59
leoggjorgevazq, Toluxero, dentro del council sentimos que han hecho un excelente trabajo como comunidad, pero pensamos que podrían necesitar algo de ayuda para fortalecer el grupo y seguir creciendo22:00
leoggesto no es un no definitivo de parte nuestra, sino que nos gustaría que trabajarán un poco más en las áreas que están débiles22:01
toluxero_sorry22:01
jorgevazqnetwork issues with toluxero_22:01
=== toluxero_ is now known as Toluxero
leoggpiensan ustedes que la comunidad ubuntu-mx se podría beneficiarcon algo de ayuda de nuestra parte?22:02
Toluxeroleogg, claro, yo no se cuales sean las observaciones. Durante el año que he estado trabajando22:03
Toluxerohe visto como crece la comunidad22:03
jamesjedimasterpor supuesto, tal vez estamos viciados y no vemos todo lo que nos falta por hacer desde dentro22:03
Toluxerocomo pide más cosas, y como necesitamos de mas ayuda22:03
leoggToluxero, están haciendo un excelente trabajo :)22:03
Toluxeroleogg, acabo de tomar el contacto y realmente mi ingles es muy malo22:04
leoggpero hay lugar para mejorar un par de cosas22:04
leoggToluxero, no hay problema22:04
leoggpodemos hablar en español :)22:04
jorgevazqleogg: como cuales? para ir aplicandonos en eso22:04
leoggToluxero has recently taken the leadership in ubuntu-mx22:04
jorgevazqla traduccion nos detuvo un poco en la junta22:05
Toluxeroleogg, de hecho es un cambio que se hizo, para empezar a quitar vicios22:05
leoggjorgevazq, necesitan un poco más de actividad sostenida22:05
Toluxerose quiere promover que haya mas ubuntu members22:05
leoggdocumentar un poco mejor el trabajo22:06
leoggToluxero, eso también, promover más el trabajo hacía afuera22:06
leoggToluxero, jorgevazq, me gustaría ayudarles en ese aspecto para ver si podemos retomar la oficialización dentro de un par de meses22:06
leoggsi a ustedes les parece bien?22:07
Toluxeroleogg, es la segunda vez q lo hacemos.22:07
Toluxeroleogg, hemos puesto mucho empeño en hacerlo22:07
juancarlospaco2:(22:07
jorgevazq2009 was a though year for us22:07
leoggToluxero, se mira que han hecho un gran trabajo22:07
Toluxeroademás de que a veces es muy complicado por la situacion em mexico22:07
leogga veces toma un poco de tiempo reconstruir las cosas22:08
jorgevazqH1N1 was a real hit to many events22:08
Toluxeroel año pasado fue muy dificil, todo el año se fue gracias a la influenza.22:08
leoggToluxero, me lo imagino22:08
Toluxeroy este año ni se diga en invierno restringieron de nuevo los eventos masivos22:08
juancarlospaco2sudo kill -9 h1n122:08
Toluxeroy quitaron la restriccion aproximadamente 6 semanas22:09
leoggToluxero, jorgevazq, yo les recomendaría que se tomen su tiempo en reconstruir el equipo22:09
leoggy que intentemos de nuevo en un par de meses22:09
leoggyo estoy a su disposición para ayudarles si lo necesitan22:09
rkgarcialeogg++22:09
itnet7Toluxero: I am here for you as well22:10
itnet7ping me anytime22:10
* Toluxero is sad, too sad22:10
jorgevazqgracias por el ofrecimiento leogg22:10
leoggToluxero, don't be... it's a great opportunity to build a new and strong team22:11
Nuun...so?22:11
leoggjorgevazq, siempre a la orden :)22:11
jorgevazqNuun: que no22:11
jorgevazqleogg: vale, dejanos asimilar todo esto, estamos en contacto22:11
jorgevazqque tenemos mucho trabajo que hacer22:11
jorgevazq:(22:11
Nuunthat's ok, it's a pleasure.22:11
leoggjorgevazq, claro... buscame en cualquier momento22:11
juancarlospaco2:)22:13
PabloRubianessi a mi tambien... estamos todos para ayudar22:13
itnet7jorgevazq: I am confident that if you take leogg up on his offer, that he can help bring to light some of the great work you have done, where it's not so obvious now22:13
popeythanks leogg and everyone else for coming.22:15
leoggthank you guys22:15
jorgevazqsee ya later someday soon22:15
paultagthanks guys!22:15
jorgevazqitnet7: probably, but again, we still need to figure out some things by ourselves before getting help from outside22:16
Toluxerojorgevazq, relax please22:16
jorgevazqI am relaxed, I'm just saying we got to strategize before jumping22:17
paultagjorgevazq, we are here to help in any way22:17
jorgevazqok22:17
jorgevazqthank you all22:17
jorgevazqreally22:17
paultagthank you guys. Keep up the good work22:18
jorgevazqpaultag: count on it22:18
juancarlospaco2:)22:19
paultagAlright. That's it. Thanks for coming everyone. Have a great day!22:19
jorgevazqci vediamo, tutti!22:20
juancarlospaco2esteeeeem...22:23
PabloRubianesBye and thanks all!!22:28
juancarlospaco2:)22:28
juancarlospaco2vuelvo a ed a escribir unas cosas...22:35
pcapelutoNuevamente gracias a todos, una alegría muy grande nos han dado esta noche, muchas gracias, estamos en contacto, Thanks again to everyone, a great joy they have given us tonight, thank you very much, we are in contact22:38

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