[01:52] <chikilis> buenas tardes como c encuentran
[01:52] <chikilis> una pregunta, que formato de disco debo tener para instalar ubuntu??
[01:54] <chikilis> hola
[03:30] <willian> NESECITO AYUDA CON UBUNTU
[03:30] <willian> ALGUIEN QUE ME OUEDA AYUDAR
[03:30] <willian> POR FAVOR
[03:31] <willian> AYUDAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAA
[03:32] <maco> para español, va a #ubuntu-es por favor
[03:32] <willian> POR DONDE NO SE
[03:32] <maco> escribe:  /join #ubuntu-es
[03:33] <easter_egg> o.o
[03:34] <maco> y usa pequeño letras
[03:34] <maco> doh gone
[03:34] <maco> had to look up "letters"
[03:34] <ajmitch> for some reason -meeting tends to attract people using a web-based client, is there some page that has it set as the default channel?
[03:36] <persia> ajmitch, I think #ubuntu is just really busy, and lots of pages indicate #ubuntu-meeting is where various groups gather (yes, at specific times, but that's not always clear to newcomers to IRC)
[14:01] <NCommander> #startmeeting
[14:01] <MootBot> Meeting started at 08:01. The chair is NCommander.
[14:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[14:02] <NCommander> (sorry for being slightly late, had some issues getting it to assiocate with my AP)
[14:02] <davidm> G'day
[14:02] <mpoirier> o/
[14:03] <NCommander> [link] https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100921
[14:03] <MootBot> LINK received:  https://wiki.ubuntu.com/MobileTeam/Meeting/2010/20100921
[14:03] <NCommander> Who's about?
[14:03] <dyfet> where about everyone's whereabouts?
[14:03]  * rsalveti waves
[14:04]  * GrueMaster groans lifelessly.
[14:04]  * NCommander pokes ogra
[14:04] <ogra> ouch
[14:05] <NCommander> [topic] Action Items from last meeting
[14:05] <MootBot> New Topic:  Action Items from last meeting
[14:05] <NCommander> [topic] NCommander to smash antimony's crontab's with a big large golden brick
[14:05] <MootBot> New Topic:  NCommander to smash antimony's crontab's with a big large golden brick
[14:05] <NCommander> Did it, crontab is normal, and all dove images are being ubilt again
[14:05] <NCommander> [topic] EVERYONE to put their status on the wiki
[14:05] <MootBot> New Topic:  EVERYONE to put their status on the wiki
[14:06]  * NCommander did it
[14:06]  * rsalveti just did it
[14:06] <rsalveti> for this week :-)
[14:06]  * ogra did it
[14:07] <ogra> dyfet, ugh
[14:07] <ogra> dyfet, where do you see telepathy-glib fail again ?
[14:07] <NCommander> right, everyone make sure its there for last week, and do it for this week too
[14:07] <ogra> (its not on the ftbfs list)
[14:07] <NCommander> moving on
[14:07] <NCommander> [topic] Standing Items
[14:07] <MootBot> New Topic:  Standing Items
[14:08] <NCommander> [topic] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:08]  * ogra notes that "this week" means last monday to last friday
[14:08] <MootBot> New Topic:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile.html
[14:08] <ogra> by an old definition we had
[14:08] <ogra> (just for the new guys on the team :) )
[14:08] <dyfet> ogra: I saw it in the bug report you commented on
[14:08] <NCommander> [topic] http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10.html
[14:08] <MootBot> New Topic:  http://people.canonical.com/~pitti/workitems/maverick/canonical-mobile-ubuntu-10.10.html
[14:09] <ogra> dyfet, i asked you about 2 months ago to talk to upstream and pointed you to the bug i just commented on (and now assigned to you)
[14:09] <ogra> to make sure it gets fixed upstream
[14:09] <ogra> please read what i wrote again
[14:09] <ogra> on that bug
[14:09] <dyfet> ok
[14:10] <ogra> rsalveti, EDID starts getting urgent if you still want to have it in the release
[14:10] <ogra> RC freeze will be soon
[14:10] <NCommander> [action] dyfet to talk with upstream to merge fix and work with ogra on it
[14:10] <MootBot> ACTION received:  dyfet to talk with upstream to merge fix and work with ogra on it
[14:10] <rsalveti> ogra: yep, I know, I'm working on it just for this week
[14:10] <ogra> and i'm about to switch to linaro u-boot
[14:10] <rsalveti> or go for release, or postponed with a solution
[14:10] <ogra> NCommander, no
[14:10] <rsalveti> ogra: don't worry
[14:10] <ogra> NCommander, dyfet has a bug task for it, i'm not involved
[14:11] <NCommander> [action] dyfet to talk with upstream to merge fix
[14:11] <MootBot> ACTION received:  dyfet to talk with upstream to merge fix
[14:11] <ogra> NCommander, no
[14:11] <NCommander> no?
[14:11] <ogra> just dont make any action item for that
[14:11] <NCommander> ok
[14:11] <NCommander> [action] disregard last two actions
[14:11] <MootBot> ACTION received:  disregard last two actions
[14:11] <ogra> there is a bug with a request from upstream to test their fix
[14:11] <ogra> thats all
[14:12] <ogra> bugt is assigned with a clear reqest what to do ... no need for an action
[14:12] <NCommander> [topic] Assigned Bugs (http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html)
[14:12] <MootBot> New Topic:  Assigned Bugs (http://qa.ubuntu.com/reports/team-assigned/canonical-mobile-assigned-bug-tasks.html)
[14:12]  * NCommander has a few for dove installer issues, but nothing critical
[14:13] <ogra> how about the assigned bugs
[14:13] <NCommander> anything else on this topic or can I move on?
[14:13] <ogra> you had an action to clear that up
[14:13] <ogra> for the vintage thumb2 issues you dont plan to work on
[14:13] <NCommander> ogra: gah, whoops.
[14:13] <ogra> :)
[14:14] <NCommander> [action] NCommande rto clear out assigned bugs (c/o)
[14:14] <MootBot> ACTION received:  NCommande rto clear out assigned bugs (c/o)
[14:14] <ogra> everyone else ... please look over that list
[14:14] <ogra> unassign bugs you wont work on
[14:14] <ogra> (and leave a comment )
[14:14] <ogra> rsalveti, i belive bug 626795 should be fix released
[14:15] <ogra> not sure why it didnt get autoclosed
[14:15] <NCommander> can I move onto kernel status?
[14:15] <rsalveti> ogra: sure, me neither
[14:15] <ogra> oh, because its filed against linux-ti-omap4 not against linaros u-boot :)
[14:15] <ogra> NCommander, go for it
[14:15] <NCommander> [topic] Kernel Status (cooloney, mpoirier, lag)
[14:15] <MootBot> New Topic:  Kernel Status (cooloney, mpoirier, lag)
[14:16] <ogra> mpoirier, got your panda working ?
[14:16] <mpoirier> yes,
[14:16] <mpoirier> got the board going yesterday.
[14:16] <mpoirier> got sound
[14:16] <ogra> how ?
[14:16] <ogra> just out of the box ?
[14:17] <mpoirier> running the scipts in the bug.
[14:17] <ogra> or with patches/changes
[14:17] <mpoirier> that is step 1.
[14:17] <ogra> ah, k
[14:17] <rsalveti> ogra: but we had a bug for kernel and another for u-boot :-)
[14:17] <ogra> you cant revert the alsa changes
[14:17] <rsalveti> anyway
[14:17] <ogra> so you need to re-flash to get it virgin again
[14:17] <mpoirier> next is to put the default setting in the kernel.
[14:17] <ogra> (just as a note)
[14:18] <mpoirier> ogra: I'll touch base with you after on that "note".
[14:18] <ogra> k :)
[14:18] <mpoirier> got GSX working with rsalveti's help.
[14:18] <mpoirier> work postponed to N.
[14:18] <ogra> with the default packages and no manual work ?
[14:19] <ogra> (from the PPA)
[14:19] <rsalveti> ogra: what should be postponed is to get the kernel modules at our kernel
[14:19] <ogra> if that works we can pull them into the archive
[14:19] <ogra> rsalveti, right
[14:19] <ogra> but the DKMS version should be fine
[14:19] <rsalveti> ogra: sure
[14:20] <ogra> if that works OOTB and we hear back from all testers we can request inclusion
[14:20]  * ogra only waits for alf
[14:20] <NCommander> alf?
[14:20] <mpoirier> lag is in taipei - I didn't have time to get the omap4 status from him.
[14:20] <rsalveti> ogra: yep, alf seems to be testing right now
[14:20] <mpoirier> ..
[14:20] <ogra> right
[14:20] <ogra> mpoirier, no worries :)
[14:20] <NCommander> argh, brain fart ;-/
[14:20] <ogra> ansthign from cooloney ?
[14:20] <ogra> NCommander, we have a direct line to melmarc now
[14:21] <ogra> :P
[14:21] <ogra> just use the red phone for requests :P
[14:21] <NCommander> neat
[14:21] <NCommander> can I move on?
[14:21] <ogra> mpoirier, anything from cooloney wrt any changes in TI land upstream ?
[14:22] <mpoirier> nop - not that I'm aware of.
[14:22] <ogra> and i also think we should have the SRU request for the final kernel ready in advance
[14:22] <ogra> (for omap4)
[14:22] <ogra> given that we might get it on hard freeze day or some such
[14:22] <ogra> please forward that as a discussion point in your teasm
[14:22] <ogra> *team
[14:23] <mpoirier> yes.
[14:23]  * ogra will care for the bootloader side
[14:23] <ogra> its not clear yet when the final silicon will be there
[14:23] <ogra> not sure davidm wants to elaborate on that here and now
[14:24] <davidm> current date is a little less then 2 weeks away
[14:24] <ogra> (i suppose we can release with a buggy kernel as long as it boots and push fixes into post release SRUs)
[14:24] <ogra> but it needs to boot and be able to connect to the net for updating
[14:25] <ogra> NCommander, move if nobody else has any kernel related bits
[14:25] <mpoirier> ogra: do you see a problem with connecting after installation ?
[14:25] <ogra> mpoirier, no, but i havent seen the future HW yet :)
[14:25] <mpoirier> ah.
[14:25] <rsalveti> I fixed yesterday an issue with IGEPv2
[14:25] <mpoirier> ok.
[14:26] <ogra> if there are changes that break USB or some such ...
[14:26] <rsalveti> should now have a working display, but still waiting someone who has the board to test it, before pushing to the kernel team
[14:26] <ogra> i think i saw it being discussed somewhere
[14:26]  * ogra look sat the kernel ML
[14:27] <ogra> hmm, no, not there
[14:27] <ogra> anyway
[14:27] <ogra> NCommander, ?
[14:28] <ogra> NCommander, what about the new audio bugs i saw for dove today ?
[14:28] <ogra> are they anyhow kernel related ?
[14:28] <ogra> (or probably GrueMaster knows since he filed ...)
[14:29] <rsalveti> it seems now we have audio issues with every board we work on :-)
[14:29] <GrueMaster> I was just getting ready to report on it as part of my report (next topic).
[14:29] <persia> The dove audio bugs were reported as *regressions*
[14:30] <ogra> GrueMaster, well, if there are no kernel bits, lets wait for NCommander to move on :)
[14:30] <ogra> if he didnt fall asleep
[14:30] <GrueMaster> yes, they were.  I retested Beta and basic audio works.  It fails on 20100920 image.
[14:30] <ogra> NCommander, WAKEUP !!!
[14:30]  * ogra lokks for a trumpet
[14:30] <ogra> honk honk
[14:31]  * davidm wonders if NCommander disconnected from his AP again
[14:31]  * davidm is checking
[14:31] <ogra> bad, he owns the bot ... :)
[14:31] <NCommander> back
[14:31] <NCommander> internet hates me
[14:32] <ogra> hate it back :)
[14:32] <NCommander> [topic] ARM Porting/FTBFS status (NCommander, dyfet)
[14:32] <MootBot> New Topic:  ARM Porting/FTBFS status (NCommander, dyfet)
[14:32] <GrueMaster> sigh
[14:32] <GrueMaster> fail
[14:32] <davidm> NCommander, did you miss info on Marvell regressions? (Audio)
[14:32] <ogra> GrueMaster, yeah, who needs QA :P
[14:32] <ogra> NCommander, ^^^
[14:33] <NCommander> davidm: oh,I saw that, was working with GrueMaster on it last night somewhat
[14:33] <ogra> NCommander, can you fix the topic ?
[14:33] <ogra> you skipped tobin
[14:33] <NCommander> [topic] QA Status (GrueMaster)
[14:33] <MootBot> New Topic:  QA Status (GrueMaster)
[14:34] <ogra> :)
[14:34] <GrueMaster> Found some regressions in alsa on dove from beta to recent, going to retest on Beagle as well to see if there are regressions there.  Bug 644028 & bug 644037
[14:34] <GrueMaster> BeagleXM (prerelease version) is now unstable for me as of Friday morning.
[14:34] <GrueMaster> Getting overwhelmed with outside-of-image test requests.
[14:34] <ogra> oh, 644037 looks liek fun
[14:34] <ogra> *like
[14:34] <GrueMaster> The regressions in the kernel are that basic audio worked in Beta and now does not in 20100920.
[14:34] <ogra> i wonder if its introduced by persia's changes to pulse
[14:34] <ogra> since default.pa uses omap4 settings on armel
[14:35] <ogra> i wonder if tehy also work on dove
[14:35] <GrueMaster> The regression in Pulse Audio is that it used to have controls available to switch from speakers to headphone, now it doesn't.
[14:35] <persia> Wouldn't, as ALSA is broken.
[14:35] <ogra> oh, on dove as well ?
[14:35] <ogra> tahts bad
[14:35] <persia> Anyway, the changes I made for armel aren't board-specific: reducing the number of in-flight samples and using a fixed-point codec will be better for all current-generation ARM chips.
[14:36] <ogra> ok
[14:36] <ogra> thats what i wanted to hear :)
[14:37] <ogra> GrueMaster, anything for omap4 ?
[14:37]  * persia wouldn't push hardware-specific patches to packages into the archive, and would probably do something odd to them even if pushing to a PPA so that they didn't work in the archive
[14:37] <GrueMaster> I have not been successful geting audio working on omap4 yet, but have not applied any external scripts yet either.
[14:38] <ogra> well, did you test the images lately ?
[14:38]  * ogra wasnt referring to audio
[14:38] <GrueMaster> I got as far as booting omap4 on 20100920 image, and then focused on audio issues on dove & beagle.
[14:38] <GrueMaster> I was also spending some time trying to get my beagleXM working again.
[14:38] <ogra> hmm, k
[14:39] <ogra> please test the new favorites stuff on omap4 ...
[14:39] <ogra> specifically the PPA icon
[14:39] <GrueMaster> Since Thursday, I have received 4 out-of-image test requests that take a lot of time.
[14:39] <ogra> also if anyone still sees something in the launcher we can assign to devilshorns, please dont hesitate :)
[14:40] <NCommander> can we move on?
[14:40] <GrueMaster> That brings up some other issues I discovered last week.
[14:40] <ogra> i'm pondering if we shouldnt drop the film reel completely
[14:40] <ogra> we have the apps in the panel anyway
[14:40] <ogra> seems pointless to have an emblem on the icon
[14:40] <GrueMaster> Working with devilhorns, I discovered a disparity between une and une-efl in the font handling.
[14:41] <ogra> and doesnt looks very good non-animated imho
[14:41] <ogra> GrueMaster, do we have a separate bug for that ?
[14:41] <ogra> oh, and could you teach devilshorns a bit about bug filing ?
[14:41] <GrueMaster> Spent several hours tracking that one, and yes there is a bug filed. (don't have the # offhand).
[14:41] <ogra> he tends to attach all his fixes to the same bug
[14:41] <ogra> would be better to have them separate
[14:42] <GrueMaster> I'll try.
[14:42] <ogra> since not all fixes apply to freeze exceptions
[14:42] <ogra> thanks :)
[14:42] <NCommander> can I move on?
[14:42] <GrueMaster> Go
[14:42] <ogra> ++
[14:42] <NCommander> [topic] ARM Porting/FTBFS status (NCommander, dyfet)
[14:42] <MootBot> New Topic:  ARM Porting/FTBFS status (NCommander, dyfet)
[14:42] <ogra> nothing in main \o/
[14:43] <ogra> well, nothing *we* have to touch
[14:43] <NCommander> :-)
[14:43] <ogra> openoffice requires testing
[14:43] <NCommander> :-(
[14:43] <ogra> please, everybody who has some spare time, install it and test
[14:43] <ogra> its in the archive now
[14:43] <ogra> but untested yet
[14:44]  * persia would appreciate someone testing krita also
[14:44] <ogra> also doko created a ton of bugs for universe packages
[14:44] <ogra> for ftbfs'es
[14:44] <ogra> i assigned some to dyfet but there are likely more
[14:44] <ogra> so if you feel like investing some time, look over them please
[14:45] <NCommander> [topic] ARM Image Status (ogra, NCommander)
[14:45] <MootBot> New Topic:  ARM Image Status (ogra, NCommander)
[14:45] <ogra> failed tonight
[14:45] <ogra> thanks to antiomony being upgraded to lucid
[14:45] <ogra> but its fixed now
[14:46] <ogra> the current omap images create swap again
[14:46] <ogra> which takes about 3 minutes
[14:46] <ogra> i'm still pondering how to do it during image creation without having to fiddle with the partitioning
[14:46] <ogra> jasper should also spawn a getty on serial consoles if you have set console= on cmdline
[14:47] <rsalveti> cool
[14:47] <ogra> please someone test that (requires editing boot.scr twice)
[14:47] <rsalveti> saw that
[14:47] <ogra> it will only put it in plce if boot.scr on firstboot has it
[14:47] <ogra> and for second boot you need to edit /boot/boot.script and re-run flash-kernel to add it again
[14:48] <ogra> still looking into ho i fix that issue best
[14:48] <GrueMaster> ogra: I have a few ideas.  Will discuss after meeting.
[14:48] <ogra> beyond that the favorites have an apturl icon for TI PPAs now
[14:48] <ogra> that exposes some bugs in software-center :)
[14:48] <ogra> which got fixed today by the tireless mvo
[14:49] <ogra> davidm, i will need an icon from TI for that
[14:49] <ogra> davidm, as well as a list of binary packages and eula text
[14:49] <ogra> currently it just uses the unknown app icon
[14:50] <ogra> beyond that, the omap4 images are ready for release i think
[14:50] <rsalveti> ogra: regarding eula, is it needed to access the ppa or to install the packages?
[14:50] <rsalveti> or both
[14:50] <ogra> oh, and i also plan to work on fixing the "all armel headers installed" issue before release
[14:50] <rsalveti> cool
[14:51] <ogra> rsalveti, no, its just a descriptive text shown when you enable the PPA
[14:51] <ogra> its nbot really an "accept/cancel" thing
[14:51] <rsalveti> ogra: hm, ok, so it should be a huge text with all licenses for all packages
[14:51] <ogra> sw-center doesnt have that yet
[14:51] <ogra> for packages that require a real eula it still should happen in preinst
[14:51] <ogra> like java does
[14:52] <rsalveti> ogra: oh, got it
[14:52] <rsalveti> makes sense
[14:52] <ogra> it would be great if we could just do everything in the sw-center eula
[14:52] <ogra> but i doubt that can happen in time for maverick
[14:52] <ogra> since lawyers will be involved in any change here
[14:52] <rsalveti> probably only for N
[14:53] <ogra> or N+1
[14:53] <ogra> depends on the lawyers :)
[14:53] <rsalveti> could be, if we involve lawyers
[14:53] <rsalveti> yep :-)
[14:53] <ogra> hehe
[14:53] <ogra> NCommander, dove status ?
[14:53] <ogra> any release blockers there ?
[14:53] <rsalveti> NCommander: ?
[14:53] <ogra> fell asleep again :)
[14:53] <GrueMaster> For the most part, dove image is looking good.
[14:54] <GrueMaster> Missing icon for installer from live image.  And of course audio issues.
[14:54] <NCommander> argh
[14:54] <NCommander> what Tobin said
[14:54] <GrueMaster> :P
[14:54] <ogra> bootloader issues are fixed now ?
[14:54] <GrueMaster> That is on Avenger only, which is not supported.
[14:55] <ogra> i thought ubiquity messed it up in the past on dove too
[14:55] <ogra> trying to install grub or something
[14:55]  * ogra was rather referring to that one
[14:55] <GrueMaster> Oh, yea that was fixed wit hthe recent ubiquity.
[14:55] <ogra> not to avenger
[14:55] <ogra> awesome !
[14:55] <ogra> NCommander, move !
[14:56] <GrueMaster> Yesterday's image installed w/o error (other than no icon to launch it)
[14:56] <ogra> pfft icons are overrated
[14:56] <ogra> they are for your mom !
[14:56] <ogra> *g*
[14:56] <NCommander> [topic] ABO
[14:56] <MootBot> New Topic:  ABO
[14:56] <ogra> GrueMaster, persia ... your reports are still missing
[14:56] <GrueMaster> Well, I feel like my mom when I am low on caffeine.
[14:56] <ogra> heh
[14:57] <GrueMaster> Yea, will get to it later today.
[14:57]  * persia doesn't participate in that sort of thing
[14:57] <GrueMaster> Meeting post was at 12:33am my time.
[14:57]  * ogra slaps persia 
[14:57] <ogra> we should make sure to have them on the wiki before the meeting next week
[14:57] <GrueMaster> (needs to be 24 hours earlier).
[14:58] <ogra> (indeed that requires that NCommander sends out the announcement early enough and that the wikipage exists)
[14:58] <GrueMaster> I have requested time and again that the meeting notice with wiki attachment goes out 24 hours before the meeting.
[14:58] <ogra> NCommander, can we make it 24h earlier so tobin doesnt suffer?
[14:58] <persia> NCommander, Go make a wiki page now :p
[14:58] <ogra> ++
[14:59] <ogra> yeah, creating it right after the meeting would surely be best
[14:59]  * NCommander coughs
[14:59] <davidm> NCommander, at the conclusion of this meeting you need to wrap the page and make the next one please
[14:59] <NCommander> k
[14:59] <NCommander> can I close it?
[14:59] <NCommander> er, the meeting?
[15:00] <persia> Please.
[15:00] <NCommander> #endmeeting
[15:00] <MootBot> Meeting finished at 09:00.
[15:00]  * ogra applauds 
[15:00] <ogra> if my clock isnt wrong that was on the point :)
[15:00] <rsalveti> yup :-)
[15:00] <kees> \o
[15:01] <pitti> o/
[15:01] <pitti> mdz, cjwatson?
[15:01] <pitti> Keybuk?
[15:03] <Keybuk> yup am here
[15:03] <Keybuk> hmm, xchat isn't notifying me again *sigh*
[15:04]  * pitti SMSed mdz and cjwatson
[15:04] <pitti> ♩ communication breakdown ♪
[15:04] <mpoirier> rsalveti: in the meeting you talked about "a bug for the kernel and another for u-boot", it this related to sound ?
[15:05] <rsalveti> mpoirier: #ubuntu-arm please
[15:05] <mpoirier> ya - wrong window.
[15:06] <cjwatson> here
[15:06] <pitti> hello Colin
[15:07] <pitti> ok, 4 people, let's start then
[15:07] <pitti> #startmeeting
[15:07] <MootBot> Meeting started at 09:07. The chair is pitti.
[15:07] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[15:07] <pitti> [TOPIC] Action review
[15:07] <MootBot> New Topic:  Action review
[15:07] <pitti> pitti to follow up with kees on-list (re: Chromium security updates)
[15:07] <pitti> there was some further discussion, so from the scope of this action item this was done
[15:07] <pitti> it's not done in the "find a solution" yet
[15:07] <kees> can we discuss it further today?
[15:08] <pitti> I added it to the agenda, yes
[15:08] <kees> as in, at this meeting at the end of the agenda?
[15:08] <kees> okay, cool
[15:08] <pitti> mdz to implement brainstorm reviews as proposed
[15:08] <pitti> he sent a proposal to the list, which from my POV reflects what we discussed yesterday
[15:09] <pitti> so I think we should add that to https://wiki.ubuntu.com/TechnicalBoardAgenda with the next target date
[15:09] <pitti> which should be about two weeks after UDS
[15:09] <pitti> any objections to that?
[15:09] <Keybuk> none
[15:09] <kees> sounds good
[15:10] <pitti> then we can keep it on the agenda and pick it up when it's due
[15:10] <pitti> I'll add it as part of the meeting post-processing
[15:10] <pitti> mdz to respond to jono re: application review board
[15:10] <pitti> this happened AFAICS
[15:10] <pitti> [ACTION] pitti to add brainstorm review to TB agenda
[15:10] <MootBot> ACTION received:  pitti to add brainstorm review to TB agenda
[15:11] <pitti> [TOPIC] Micro-release exception for bzr
[15:11] <MootBot> New Topic:  Micro-release exception for bzr
[15:11] <pitti> Martin Pool sent a request for this, and a description how these updates usually look like
[15:12] <pitti> I already replied on list, any further comments to that?
[15:12]  * pitti looks at cjwatson with his SRU hat
[15:12] <cjwatson> I was fine with the summary on-list, though as I noted I would prefer the test suite to be turned on
[15:13] <cjwatson> (if possible; maybe some tests need to be xfailed or similar, but it's better than nothing)
[15:13] <pitti> I think that's reasonable
[15:13] <kees> I'm good with it, but would also like to see the tests in the build.
[15:13] <pitti> I think we shuold do the tests on the installed package as part of the verification
[15:13] <pitti> to avoid packaging errors, etc.
[15:13] <pitti> (read: "in addition", not "instead")
[15:14] <kees> documenting the test procedure in qa-regression-testing tree then would be how to do that?
[15:14] <cjwatson> pitti: agreed
[15:14] <pitti> kees: that sounds good; although it shuold by and large just be "$ bzr selftest"?
[15:14] <cjwatson> --no-plugins
[15:15] <kees> pitti: obvious to someone who knows it, but not to someone new :)
[15:15] <cjwatson> well, probably
[15:15] <pitti> kees: yes, I didn't want to say "we shouldn't do it", just "it should be easy once we know how"
[15:16] <kees> yup, totally
[15:16] <pitti> kees: since you know this well, could you add that call, once mbp explains us what to call exactly?
[15:16] <pitti> [ACTION] pitti to ask mbp about self test instructions on installed system
[15:16] <MootBot> ACTION received:  pitti to ask mbp about self test instructions on installed system
[15:17] <pitti> [ACTION] kees to add bzr self test to qa-regression-testing
[15:17] <MootBot> ACTION received:  kees to add bzr self test to qa-regression-testing
[15:18] <pitti> (please complain if not)
[15:18] <pitti> [VOTE] bzr microrelease SRU exception once build/runtime tests get enabled
[15:18] <MootBot> Please vote on:  bzr microrelease SRU exception once build/runtime tests get enabled.
[15:18] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[15:18] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[15:18] <pitti> +1
[15:18] <MootBot> +1 received from pitti. 1 for, 0 against. 0 have abstained. Count is now 1
[15:19] <kees> +1
[15:19] <MootBot> +1 received from kees. 2 for, 0 against. 0 have abstained. Count is now 2
[15:19] <cjwatson> +1
[15:19] <MootBot> +1 received from cjwatson. 3 for, 0 against. 0 have abstained. Count is now 3
[15:19] <kees> pitti: so it's not literally "selftest" then?
[15:19] <pitti> Keybuk: ?
[15:20] <pitti> kees: something like it, though
[15:20] <pitti> $ bzr selftest
[15:20] <pitti> bzr: ERROR: No module named testtools
[15:20] <kees> ah, python-testtools
[15:20] <pitti> kees: like, that and an additional dependency, and perhaps some extra options for plugins
[15:20] <pitti> kees: I'll ask mbp on the thread before
[15:20]  * kees nods
[15:20] <pitti> hm, seems we might have lost Keybuk
[15:21] <Keybuk> sorry
[15:21] <Keybuk> +1
[15:21] <MootBot> +1 received from Keybuk. 4 for, 0 against. 0 have abstained. Count is now 4
[15:21] <pitti> Keybuk: thanks
[15:21] <pitti> [ENDVOTE]
[15:22] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[15:22] <pitti> [TOPIC] Chromium security updates
[15:22] <MootBot> New Topic:  Chromium security updates
[15:22] <pitti> this got some more replies on the thread, but it currently seems to be stuck on a dead end
[15:22] <kees> so, I think what we should do is give a direction
[15:22] <kees> MRE seems okay for them
[15:23] <pitti> it seems the only real option that we have is to throw out these updates pretty much blindly and hope for the best?
[15:23] <kees> but, probably changes in debian/ should be minimized for stable releases.
[15:23] <kees> right
[15:23] <pitti> yes, from the results it seems that it's MRE or not having the package at all
[15:23] <kees> and we need resolution on what to do when builddeps keep getting added. presently, it seems that just adding them to the orig is the way to go, since everything else in bundled anyway
[15:24] <pitti> but personally I still find this highly unsatisfying for something that's aspiring to get into main and default installs
[15:24] <kees> it's pretty horrible, but it's the same state firefox is in. :(
[15:25] <pitti> kees: firefox has rather predictable and fewer releases, and we have some time to test prereleases
[15:25] <kees> right, but they're still bundling stuff, etc
[15:25] <pitti> kees: I think for build deps like gyp it was okay to update the package in the archive
[15:26] <pitti> but if they need a commonly used library which we don't want to update, then bundling it is, sure
[15:26] <pitti> was there ever another case of a new build dep except gyp?
[15:27] <jdstrand> libvpx
[15:27] <jdstrand> (introduced as a new package in lucid)
[15:27] <kees> (bzr already doesn't pass its own selftest fully...)
[15:27] <pitti> ah, which would also affect gstreamer0.10-plugins-bad
[15:27] <jdstrand> also chromium-codecs-ffmpeg needed an update
[15:27] <jdstrand> pitti: in maverick, yes for sure, and iirc ffmpeg
[15:27] <pitti> jdstrand: right, but I'd consider -codecs and -l10n as part of chromium, somehow
[15:28] <jdstrand> pitti: re chromium-codecs-ffmpeg> at least from the package name, yes :)
[15:28] <pitti> jdstrand: so for those it's probably a case-by-case decision, whether it's appropriate to update it for gstreamer, too?
[15:28] <pitti> jdstrand: it's the chromium specific fork, anyway
[15:29] <pitti> so, does anyone still see something to discuss for chromium updates, under the assumption that it stays in universe for now?
[15:29] <jdstrand> I just worry about giving a blanket "it's ok to update system libraries as needed for chromium" when other packages depend on them. testing just explodes on that sort of thing
[15:29] <pitti> jdstrand: no, we shouldn't; but it might be better in some cases
[15:29] <jdstrand> (so I am in favor of bundling when the system one can no longer be used or updated appropriately)
[15:30] <jdstrand> pitti: yes, agreed. have to look at it case by case
[15:30] <jdstrand> ie, it is possibly an option to update the system lib
[15:31] <pitti> [TOPIC] Administrativa
[15:31] <MootBot> New Topic:  Administrativa
[15:31] <pitti> I scanned the ML for topics
[15:31] <pitti> no new community bugs
[15:32] <pitti> I keep forgetting, what's the order for chairs? IRC nick?
[15:32] <pitti> i. e. sabdfl?
[15:32] <Keybuk> yus
[15:32] <kees> it's been nick, yes
[15:32] <pitti> ok
[15:32] <pitti> [TOPIC] AOB
[15:32] <MootBot> New Topic:  AOB
[15:32] <pitti> anything else on your mind?
[15:33] <pitti> 5 secs
[15:33] <cjwatson> not I
[15:33] <pitti> ok, thanks everyone then!
[15:33] <pitti> #endmeeting
[15:33] <MootBot> Meeting finished at 09:33.
[15:34] <pitti> will send out notes etc. after my next meeting
[18:58]  * mathiaz waves
[18:58]  * kirkland is here for a moment, boarding a plane during the course of this meeting, though ....
[18:59] <jiboumans> o/
[18:59] <hallyn> \0
[19:00] <ttx> o/
[19:00] <SpamapS> o/
[19:00] <zul> gday
[19:01] <JamesPage> o/
[19:01]  * mathiaz waits a bit for people to show up
[19:01] <ScottK> \o
[19:02] <hggdh> ~ô~
[19:02] <zul> mathiaz: how cold is it montreal today?
[19:02] <mathiaz> zul: cold - montreal? this is non-sense!
[19:03] <mathiaz> allright - let's the ball rolling
[19:03] <zul> mathiaz: heh are you still wearing shorts outside?
[19:03] <mathiaz> #startmeeting
[19:03] <MootBot> Meeting started at 13:03. The chair is mathiaz.
[19:03] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[19:03] <mathiaz> today's amazing refreshing exciting mind-blowing agenda:
[19:03] <mathiaz> ttps://wiki.ubuntu.com/ServerTeam/Meeting
[19:03] <smoser> o/
[19:03] <mathiaz> [TOPIC] Review ACTION points from previous meeting
[19:03] <MootBot> New Topic:  Review ACTION points from previous meeting
[19:04] <mathiaz> jib to check with kim0 if he can attend meetings regularly ro not
[19:04] <jiboumans> mathiaz: done - he's here today and will be mostly going forward
[19:04] <jiboumans> some other commitments stood in his way last few weeks
[19:04] <RoAkSoAx> o/
[19:04]  * mathiaz waves at kim0
[19:04] <mathiaz> #
[19:04] <mathiaz> RoAkSoAx to email ubuntu server mailing list with update of cluster stack progress
[19:04] <mathiaz> I think I saw the email
[19:05] <mathiaz> RoAkSoAx: thanks for following up on that!
[19:05] <RoAkSoAx> mathiaz: i emailed yesterdayy :)
[19:05] <mathiaz> that's all for last meeting minutes
[19:05] <mathiaz> anything else to add wrt to last meeting?
[19:06] <mathiaz> nope - let's move on
[19:06] <mathiaz> [TOPIC] Maverick development (jib)
[19:06] <MootBot> New Topic:  Maverick development (jib)
[19:06] <mathiaz> # Daily triage work items
[19:07] <jiboumans> so far so good still; as mentioned last week very little feature development left
[19:07] <jiboumans> only things not affecting freezes
[19:07] <jiboumans> one thing to note though, our burndown charts don't look very healthy, and that's mostly due to people not ticking off their daily triage items
[19:07] <jiboumans> so on your triage day, when you're done, please tick them off
[19:07] <jiboumans> request for everyone to take a look at the tracker and mark those as done that they'd forgotten
[19:08] <jiboumans> other than that, no red flags at the moment... calm before the storm :)
[19:08] <mathiaz> https://blueprints.launchpad.net/ubuntu/+spec/server-maverick-dailytriage
[19:08] <jiboumans> ttx, floor's yours
[19:08] <mathiaz> ^^ is the link to the BP to tick off
[19:08] <jiboumans> thanks mathiaz
[19:08] <ScottK> New clamav release today.  Working with Debian to get it packaged and tested and in before RC.  The more significant of the two security issues it fixes is already patched in Maverick.
[19:08] <ttx> RC bugs status looks reasonably good
[19:08] <mathiaz> # Status for identified RC bugs (ttx)
[19:09] <ttx> ScottK: ack
[19:09] <ttx> We don't have any milestoned bug left, 3 high/critical maverick bugs
[19:09] <ttx> and 8 Maverick-targeted bugs
[19:10] <ttx> If you know of any bug we really shouldn't be releasing with, please let me know
[19:10] <mathiaz> ttx: where can I find the list of these bugs?
[19:10] <ttx> as it sounds suspeciously calm right now
[19:10] <ttx> https://wiki.ubuntu.com/ServerTeam/MaverickReleaseStatus
[19:10] <ttx> or a more dynamic list by searching for tag server-mrs
[19:10] <ttx> since we can't make LP return distroseries bugs where ubuntu-server is supervisor
[19:11] <mathiaz> ttx: it may worth linking the server-mrs tag search from the MaverickReleaseStatus wiki page
[19:11] <ttx> mathiaz: ack
[19:11] <mathiaz> ttx: so that I can just click on it to have a real time view of the world...
[19:11] <ttx> mathiaz: do you know if searching by package set is/will be an option
[19:11] <mathiaz> ttx: I don't know
[19:11] <ttx> mathiaz: well, "real time"... not really
[19:12] <ttx> since when I tag I update the page as well :)
[19:12] <mathiaz> ttx: well - the tag search is more accurate that the wiki page
[19:12] <ttx> but once it's in the list, the status is more accurate :)
[19:12]  * mathiaz nods
[19:12] <ttx> I'm done ;)
[19:12] <mathiaz> [ACTION] ttx to add link to server-mrs tag search from the releasestatus wiki page
[19:12] <MootBot> ACTION received:  ttx to add link to server-mrs tag search from the releasestatus wiki page
[19:13] <mathiaz> # RC bugs suggestions ?
[19:13] <ttx> That's what I just covered
[19:13] <mathiaz> if I find one in the coming hours/days - what should I do?
[19:13] <ttx> Hit me with anything YOU think should be on that list
[19:13] <ttx> mathiaz: nominate against maverick, ping me so that I add it to our radar
[19:14] <SpamapS> I have a quick question regarding universe..
[19:14] <SpamapS> it seems that drizzle is FTBFS...
[19:14] <SpamapS> and the release we have is really, really old
[19:14] <ttx> mathiaz: in doubt, ping me first
[19:14] <mathiaz> ttx: ok - you'll be online 24h?
[19:14] <ttx> mathiaz: absolutely. I received the box of pills you sent me
[19:14] <SpamapS> seeing that drizzle is still alpha-quality.. how hard would it be for monty (the debian maintainer) to upload a new version to be included in maverick at this late stage?
[19:14] <mathiaz> ttx: :)
[19:15] <mathiaz> ttx: I meant IRC connected... ;)
[19:15] <ScottK> SpamapS: Not very since it's demonstrably broken as is.
[19:15] <mathiaz> SpamapS: if it's totally broken - things can't get worse
[19:15] <SpamapS> agreed. :)
[19:15] <mathiaz> SpamapS: so anything is an improvment
[19:15] <SpamapS> its failing its own unit tests
[19:15] <ttx> mathiaz: in the next days, yes
[19:15] <ScottK> SpamapS: Also he hasn't bothered to upload to Debian either.
[19:15] <ttx> mathiaz: I'll delegate if I'm not.
[19:16] <SpamapS> ScottK: agreed, so if he uploaded to experimental, could we do a sync?
[19:16] <ttx> SpamapS: if it builds ship it ?
[19:16] <ScottK> SpamapS: It should go to Sid.  It's not in Squeeze, so there's no reason to go to experimental.
[19:16] <ttx> that rings a bell.
[19:16] <SpamapS> ScottK: ahh Ok
[19:17] <ScottK> SpamapS: If he uploads to Debian and it builds on Ubuntu I'll approve the FFe.
[19:17] <ScottK> (that deal is good this week only)
[19:17] <mathiaz> SpamapS: so you'll look into the state of drizzle?
[19:17] <SpamapS> mtaylor: welcome
[19:17] <SpamapS> ScottK: say that again please :)
[19:17] <mtaylor> hi guys
[19:17] <ttx> SpamapS: hit me with a bug number for that.
[19:17] <mathiaz> SpamapS: could this be taken somewhere else?
[19:18] <mathiaz> SpamapS: like defer the discussion to #ubuntu-devel?
[19:18] <ScottK> SpamapS: If drizzle gets updated in Sid, I'll approve a sync this week as long as you can build it on Ubuntu too.
[19:18] <SpamapS> yes I just wanted to assure Monty that if he uploads it will get done. :)
[19:18] <ttx> mtaylor: o/
[19:18] <SpamapS> mtaylor: ^^ thats all I wanted you to see. :)
[19:18] <mtaylor> done. thanks!
[19:18] <ScottK> If it needs further discussion --> #ubuntu-server
[19:18] <SpamapS> ttx: actually it doesn't seem that there is a bug
[19:19] <mathiaz> [ACTION] SpamapS to look at the state of drizzle in maverick - if it build this week ScottK to accept FFe
[19:19] <MootBot> ACTION received:  SpamapS to look at the state of drizzle in maverick - if it build this week ScottK to accept FFe
[19:19] <ScottK> ttx: Typically FTBFS bugs only get filed for Main.
[19:19] <ttx> SpamapS: it could use one. I like traceability.
[19:19] <SpamapS> filing now as part of that action item.
[19:19] <mathiaz> anything else related to RC bugs?
[19:20] <mathiaz> nope - let's move on
[19:20] <mathiaz> [TOPIC] # Natty development (jib)
[19:20] <MootBot> New Topic:  # Natty development (jib)
[19:20] <jiboumans> With feature development unwinding and only a handful of bugs targeted to release, this is a great time to put your thinking caps on for Natty if you have some spare time. Like last round, we'll use the IdeaPool wiki page to gather thoughts: https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool. There's no rush at this point, but I'd like to stress we'd love to get your input
[19:21] <mathiaz> jiboumans: should BP already be filed?
[19:21] <mathiaz> jiboumans: or an item on the NattyIdeaPool wiki page is enough for now?
[19:21] <jiboumans> mathiaz: they're welcome to be filed *if* you're willing to lead a session at UDS for it
[19:21] <jiboumans> like last time, we have both sections: ideas & uds sessions
[19:21] <jiboumans> blueprints only desired for the latter right now
[19:22] <mathiaz> how about sending an email to ubuntu-server@ and/or a blog post for call of ideas?
[19:22] <jiboumans> that's a fantastic idea
[19:22] <jiboumans> thanks for volunteering!
[19:22] <jiboumans> ;)
[19:22] <RoAkSoAx> lol
[19:23] <jiboumans> on a serious note: it's on my todo, but if you beat me to it, i'd be thankful
[19:23] <mathiaz> [ACTION] jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas
[19:23] <MootBot> ACTION received:  jiboumans to send an email to ubuntu-server@ and/or blog post for call for ideas
[19:23] <jiboumans> .... jiboumans vs meetings cair. 0 - 1
[19:23] <jiboumans> *chair
[19:23]  * mathiaz <-- big smile
[19:24] <mathiaz> on related note
[19:24] <jiboumans> alright, that's all from me about natty at this point
[19:24] <mathiaz> it may be interesting to do something similar in each upstream community someone is connected to
[19:24] <mathiaz> I may send a note to the puppet folks to get your input
[19:25] <mathiaz> I may send a note to the puppet folks to get *their* input
[19:25] <jiboumans> agreed
[19:25] <mathiaz> if someone has strong connection with other communities a targeted call for ideas could be useful
[19:26] <mathiaz> [ACTION] mathiaz to send out a call for ideas on ubuntu to the puppet community
[19:26] <MootBot> ACTION received:  mathiaz to send out a call for ideas on ubuntu to the puppet community
[19:26] <mathiaz> any questions related to Natty development?
[19:26] <kim0> do we have any guides on what kind of ideas are needed
[19:26] <smoser> do you mean good ones? or great ones ?
[19:26] <mathiaz> kim0: well - I'd say - any ideas
[19:27] <kim0> what's ok and what's not basically
[19:27] <mathiaz> kim0: well - we'll sort things out afterwards
[19:27] <kim0> cool
[19:27] <RoAkSoAx> are these ideas have to be cloud related only? :)
[19:27] <zul> of course not
[19:27] <ttx> RoAkSoAx: no, but they need to have the word "cloud" in them.
[19:27] <mathiaz> kim0: the begining phase is when we put back everything on the table
[19:28] <ttx> RoAkSoAx: kidding :)
[19:28] <mathiaz> kim0: so anything is welcomed
[19:28] <kim0> sounds good
[19:28] <RoAkSoAx> ttx: :P I do have one for the cloud though :P
[19:28] <jiboumans> kim0: a good thing to keep in mind is that we're targeting things that can be implemented in a cycle with these ideas
[19:28] <Daviey> erk
[19:28] <mathiaz> a good idea may gather some strong support and things can move forward
[19:28] <RoAkSoAx> but dunno if i'd have the time to code it
[19:28] <jiboumans> and things that you (or the suggester) can contribute to are much more likely to be accepted
[19:29]  * SpamapS files idea for renaming upstart to cthulu so the narwhal can stop ctuhulu eating ye.
[19:29] <mathiaz> the call for idea is mainly a brainstorm session
[19:29] <mathiaz> so go for quantity
[19:29]  * ScottK suggests SpamapS file one for moving to systemd.
[19:29] <mathiaz> afterwards ideas will be sorted out
[19:30] <kim0> systemd probably too volatile at now
[19:30] <RoAkSoAx> SpamapS: how do you feel of launching VM's and powering them off baserd on the load :)
[19:30] <RoAkSoAx> in the cloud of course
[19:30] <mathiaz> all right let's move on
[19:30] <mathiaz> and not discuss actual ideas here
[19:30] <RoAkSoAx> sry for OT :)
[19:30] <mathiaz> the page to capture them is: https://wiki.ubuntu.com/ServerTeam/NattyIdeaPool
[19:31] <mathiaz> any other questions related to Natty develpment?
[19:32] <mathiaz> nope - let's move on
[19:32] <mathiaz> #
[19:32] <mathiaz> Weekly Updates & Questions for the QA Team (hggdh)
[19:32] <mathiaz> [TOPIC] Weekly Updates & Questions for the QA Team (hggdh)
[19:32] <MootBot> New Topic:  Weekly Updates & Questions for the QA Team (hggdh)
[19:32] <hggdh> no news, except I am still hammering on euca.
[19:32] <mathiaz> hggdh: what's up in the QA team?
[19:32] <Daviey> \o/
[19:32] <zul> hggdh: heh what else is new?
[19:32] <mathiaz> hggdh: noticed the new QA blog
[19:32]  * hggdh hopes next cycle will leave time for other tasks
[19:32] <mathiaz> hggdh: that's really great!
[19:32] <hggdh> mathiaz: yeah, cool... kudos for ara
[19:33] <mathiaz> hggdh: agreed - ara did a great job
[19:33] <hggdh> apart from that, no news
[19:33] <mathiaz> hggdh: anything else on the QA front?
[19:33] <hggdh> no
[19:33] <mathiaz> Anything to tell to the QA team?
[19:34] <zul> keep up the good work
[19:34] <ttx> no rest for the braves
[19:35] <mathiaz> ok - let's move on
[19:35] <mathiaz> ... to the kernel team
[19:35] <mathiaz> [TOPIC] Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:35] <MootBot> New Topic:  Weekly Updates & Questions for the Kernel Team (jjohansen)
[19:36] <mathiaz> jjohansen: how is the  kernel team doing these days?
[19:36] <jjohansen> the team in general or me
[19:36] <ttx> both!
[19:36] <kim0> :)
[19:36]  * jjohansen is pulling out hair, the rest of the team is vacationing in taipei
[19:37]  * kim0 hugs jjohansen 
[19:37] <jjohansen> well thats not really true, some of the team is at the hardware summit in taipei
[19:37] <jjohansen> kim0: thanks, its not been a good day
[19:39] <mathiaz>     *
[19:39] <mathiaz>       Bug 613083 - user-data is corrupted inside metadata service
[19:39] <mathiaz> status: ^^?
[19:39] <jjohansen> it is not an Ubuntu bug, and Amazon is aware of it and working on the issue
[19:39] <mathiaz> jjohansen: ok
[19:39] <ttx> jjohansen: pulling out hair --> anythign server related ?
[19:40] <mathiaz> jjohansen: any other bugs that should brought to the -server team attention?
[19:40] <jjohansen> ttx: half of it
[19:40] <ttx> that corruption bug is the only one I have on my list, so I was wondering if you had anything for us in yours :)
[19:40] <jjohansen> mathiaz: there aren't any high priority ones that I am aware of
[19:41] <mathiaz> jjohansen: great!
[19:41] <smoser> well, the java bug would be nice.
[19:41] <jjohansen> there the regular set of reported crashes etc.
[19:41] <mathiaz> anything to bring to the kernel team attention?
[19:41] <smoser> and there is one other crash bug
[19:41] <jjohansen> ah, yes.  Sadly I haven't gotten to that yet
[19:41] <mathiaz> smoser: bug numbers?
[19:41] <smoser> bug 634487
[19:41] <ttx> smoser: that's a kernel issue ?
[19:42] <smoser> yes.
[19:42]  * ttx adds magic tag
[19:42] <SpamapS> smoser: is it a host kernel or guest kernel issue?
[19:42] <smoser> and bug 613273
[19:42] <smoser> SpamapS, there is no such thing as a host kernel issue ;)
[19:42] <jjohansen> hahaha
[19:42] <zul> riiiiight
[19:42] <smoser> but seriously, the guests go awol in both those cases.
[19:43] <ttx> ack
[19:43] <jjohansen> yep, there are certainly guest kernel issues involved
[19:43] <smoser> and in both cases in xen specific path
[19:44] <ttx> smoser: regressions in Maverick ?
[19:44] <jjohansen> ttx: yes
[19:44] <smoser> well, the java hang is better on maverick than on lucid
[19:44] <smoser> (both ill)
[19:45] <jjohansen> oh right, I got that one backwards
[19:45] <smoser> and the system_call_fastpath (which i think is actually the wrong function name) i think i've seen in both.
[19:45] <ttx> ok, I think we loaded jjohansen's plate enough
[19:45] <mathiaz> jjohansen: smoser: anything specific we can help to fix this?
[19:45] <mathiaz> or it just needs more investigation?
[19:45] <jjohansen> a good reproducing test case
[19:46] <mathiaz> ttx: are you tracking both bugs above?
[19:46] <smoser> 613273 is apparently only maverick.
[19:46] <ttx> mathiaz: I am now
[19:46] <mathiaz> ttx: great
[19:46] <mathiaz> so I think we'll come back to these next week
[19:46] <mathiaz> to review them
[19:46] <ttx> mathiaz: yes, I don't let go easily.
[19:46] <mathiaz> in the meantime both jjohansen and smoser are looking into it?
[19:46] <jjohansen> mathiaz: not atm
[19:47] <jjohansen> mathiaz: or lets say they are lower priority on the queue atm
[19:47] <smoser> yeah, that one is hard to reproduce. i guess i'll poke with jjohansen on that.
[19:47] <ttx> with the cloud image release policy it's slightly less annoying to release with those
[19:47] <mathiaz> jjohansen: works for me
[19:47] <smoser> on the t1.micro / java, we are actually getting some help from amazon.
[19:47] <mathiaz> ok - anything else for the kernel team?
[19:48] <mathiaz> nope - let's move on
[19:48] <mathiaz> [TOPIC] #
[19:48] <MootBot> New Topic:  #
[19:48] <jjohansen> mathiaz: as usual I know there is something else but I can't remember what it is
[19:48] <mathiaz> [TOPIC] Weekly Updates & Questions for the Documentation Team (sommer)
[19:48] <MootBot> New Topic:  Weekly Updates & Questions for the Documentation Team (sommer)
[19:48] <mathiaz> sommer: around?
[19:49] <mathiaz> anything that should be brought up to the attention of the doc team?
[19:49] <mathiaz> jjohansen: for the next meeting you might wanna put your ideas in the Meeting wiki page
[19:50] <mathiaz> well - nothing for the documentation team
[19:50] <mathiaz> let's move on
[19:50] <jjohansen> mathiaz: yes, that has been the plan, then I got busy chasing other things
[19:50] <jjohansen> I've got it
[19:50] <mathiaz> [TOPIC] Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[19:50] <MootBot> New Topic:  Weekly Updates & Questions for the Ubuntu Community Team (kim0)
[19:50] <kim0> hey folks, sorry for not being able to attend a few past meeting. Had some obligations, however all is clear now .. Yaay
[19:50]  * mathiaz pulls the break!
[19:50] <kim0> I'll mention a couple of points, then we can discuss the 10.10 ec2 party thing
[19:50] <kim0> The last couple of weeks I had been busy getting the cloud portal in shape. I am contacting IS to start deploying this week
[19:50] <kim0> Other than that, on a more long term matter
[19:51] <mathiaz> jjohansen: ok - let's get back to it after kim0 is done
[19:51] <kim0> I had emailed the ubuntu-devel team asking for suggestions on growing the ubuntu cloud community
[19:51] <kim0> oh sorry .. didn't notice the break thing
[19:51] <kim0> should I stop ?
[19:51] <kim0> mm ..
[19:51] <mathiaz> kim0: nope - go ahead
[19:51] <kim0> okie
[19:51] <mathiaz> kim0: it's your turn
[19:51] <kim0> Most of the feedback received was asking for technical guides or white-papers on "best practices" on how to write cloud apps, how to deploy services in the cloud, and how to build your own private cloud (storage
[19:51] <mathiaz> kim0: we'll get back to jjohansen later
[19:52] <kim0> concerns, network concerns and best practices ...etc)
[19:52] <kim0> For that, and since we're planning work for 11.04 right now, I'm adding tasks on myself, to start and grow technical content around these areas
[19:52] <kim0> We wont be writing book on these "vast" areas of new knowledge, rather starting something that the community can contribute to and grow
[19:52] <kim0> Any suggestions on what content needs to go there exactly are most welcome right now, please email the hell out of me :)
[19:52] <kim0> that's all atm ..
[19:53] <mathiaz> kim0: great - any address for the preview of the cloud portal?
[19:53] <kim0> I only have my development server
[19:53] <ScottK> kim0: I'd recommend chatting with sommer about that since he's been leading our server documentation effort for some time.
[19:53] <kim0> once I had a public copy I'll ping
[19:53] <mathiaz> kim0: ok
[19:53] <kim0> ScottK: awesome .. noted
[19:54] <mathiaz> kim0: that seems like a great plan
[19:54] <kim0> again .. suggestions and details are welcome
[19:54] <kim0> once I've defined a solid plan I'll discuss
[19:54] <kim0> if that's all .. can we talk to the 10.10 ec2 party ?
[19:55] <mathiaz> kim0: sure - what's the 10.10 ec2 party?
[19:55] <kim0> how about for the release part of 10.10
[19:56] <kim0> the server community is allowed ec2 instance access
[19:56] <kim0> we can probably get funding for that
[19:56] <Daviey> kim0: Shall we take that out of meeting?
[19:56] <kim0> okie
[19:56] <kim0> well that's all for me
[19:59] <mathiaz> anything else to note to the community team?
[19:59] <mathiaz> since we're running out of time I'll wrap up
[20:00] <mathiaz> [TOPIC] Announce next meeting date and time
[20:00] <MootBot> New Topic:  Announce next meeting date and time
[20:00] <mathiaz> next week, same place, same time?
[20:00] <ttx> yes
[20:00] <JamesPage> good with me!
[20:00] <ttx> crazy europeans
[20:00]  * SpamapS alerts the media
[20:00] <kim0> hehe
[20:00] <mathiaz> ok - so next week, same place, same time!
[20:00] <mathiaz> #endmeeting
[20:00] <Daviey> "okay" with me
[20:00] <MootBot> Meeting finished at 14:00.
[20:01] <jjohansen> mathiaz: one more thing Bug #493156, it would be good if some people can try the test kernels, verify that they work and add that to the bug report
[20:01] <jjohansen> for Lucid of course
[20:01] <mathiaz> jjohansen: is that the item you wanted to add?
[20:01] <jjohansen> yes
[20:01] <mathiaz> jjohansen: ok - I'll make sure their included in the meeting
[20:01] <mathiaz> jjohansen: minutes
[21:00] <popey> BONG!
[21:00] <popey> Ubuntu LoCo Council meeting time!
[21:00] <jfalco> woohooo
[21:00]  * popey pings czajkowski itnet7 huats and paultag (who is missing)
[21:00] <itnet7> \o/
[21:00] <huats> Hello popey !
[21:01] <huats> popey, don't forget leogg
[21:01] <popey> oops
[21:01] <huats> (who is missing too:)
[21:01] <popey> hmm
[21:01] <popey> so we're down to 3 of 6
[21:01] <czajkowski> i'm here
[21:01] <popey> 4 of 6
[21:01] <czajkowski> so we're able to vote
[21:01] <popey> #startmeeting
[21:01] <MootBot> Meeting started at 15:01. The chair is popey.
[21:01] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[21:01] <czajkowski> just waking to pub
[21:01] <popey> hah
[21:02] <popey> shall we start with the loco teams?
[21:02] <huats> sure popey !
[21:03] <czajkowski> ok
[21:03] <popey> #topic Turkish LoCo Team reapproval
[21:03] <popey> bah
[21:03] <popey> i can never drive this thing
[21:03] <czajkowski> :)
[21:03] <popey> [TOPIC] Turkish LoCo Team reapproval
[21:03] <MootBot> New Topic:  Turkish LoCo Team reapproval
[21:03] <popey> oops
[21:04] <popey> [LINK] https://wiki.ubuntu.com/LoCoCouncil/Agenda
[21:04] <MootBot> LINK received:  https://wiki.ubuntu.com/LoCoCouncil/Agenda
[21:04] <popey> [LINK] https://wiki.ubuntu.com/TurkishTeam/ReapprovalApplication
[21:04] <MootBot> LINK received:  https://wiki.ubuntu.com/TurkishTeam/ReapprovalApplication
[21:04] <popey> anyone here from Turkish LoCo?
[21:04] <bytan> Hi all
[21:04] <bytan> I am :)
[21:04] <popey> hey bytan
[21:04] <huats> hello bytan
[21:05] <bytan> hello popey huats
[21:06] <popey> ok, lets take some time to look at the application, do any of the loco council have any questions?
[21:06] <itnet7> Hey there bytan
[21:06] <huats> bytan, can you please talk to us a little more on what you did since your approval ?
[21:06] <czajkowski> the wiki application is very bare to be honest
[21:06] <huats> because I must say it isn't very explaining it
[21:06] <popey> http://sudo.ubuntu-tr.net/ is very smart
[21:07] <MootBot> LINK received:  http://sudo.ubuntu-tr.net/ is very smart
[21:07] <itnet7> Doesn't appear to be much activity since 2008, at least by looking at the Wiki's and Re-approval page
[21:07]  * itnet7 goes to look at 
[21:07] <itnet7> sudo.ubuntu-tr.net
[21:08] <bytan> Yes, thats true, i aggre abt our wiki page. but in shortly, we have created E-zine, SUDO for our users, and a team for that E-zine. We created a team for Turkish Translation and you may see how hard they work on launchpad
[21:09] <itnet7> bytan: are any of the ezine's published or translated in other languages?
[21:10] <bytan> We have a team for FCM ezine to translate turkish
[21:11] <czajkowski> is heartsmagic about?
[21:11] <popey> you have an active wiki I see
[21:12] <popey> anyone else here for turkey?
[21:12] <bytan> Heartsmagic is working now. and I talked to him today, if he could, he would like to come us later
[21:12] <bytan> but probablly he cant.
[21:16] <popey> bytan: is there any reason it's just you here representing the team?
[21:17] <bytan> i am one of the leaders too,
[21:17] <bytan> http://forum.ubuntu-tr.net/index.php/topic,12295.0.html
[21:17] <MootBot> LINK received:  http://forum.ubuntu-tr.net/index.php/topic,12295.0.html
[21:17] <huats> bytan, I think the question was more, why are you alone, since you have quite a team...
[21:17] <popey> wow
[21:17] <popey> thats quite a team structure
[21:19] <bytan> why only me? i think i am the only one who is available :)
[21:19] <popey> heh, everyone busy translating huh? :D
[21:19] <popey> are we ready to vote itnet7 czajkowski huats ?
[21:19] <bytan> The last edition of SUDO has published yesterday, thats why they cant come here.
[21:19] <czajkowski> aye
[21:19] <huats> yep
[21:20] <popey> [VOTE] Turkish LoCo Team Re-Approval
[21:20] <MootBot> Please vote on:  Turkish LoCo Team Re-Approval.
[21:20] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[21:20] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[21:20] <popey> only loco council vote please
[21:20] <popey> +1
[21:20] <MootBot> +1 received from popey. 1 for, 0 against. 0 have abstained. Count is now 1
[21:20] <itnet7> +1
[21:20] <MootBot> +1 received from itnet7. 2 for, 0 against. 0 have abstained. Count is now 2
[21:20] <czajkowski> -1
[21:20] <MootBot> -1 received from czajkowski. 2 for, 1 against. 0 have abstained. Count is now 1
[21:20] <huats> 0
[21:20] <huats> +0
[21:20] <MootBot> Abstention received from huats. 2 for, 1 against. 1 have abstained. Count is now 1
[21:20] <popey> [ENDVOTE]
[21:20] <MootBot> Final result is 2 for, 1 against. 1 abstained. Total: 1
[21:20] <popey> hmm, so whats that mean? :)
[21:21] <bytan> i wonder? :)
[21:21] <popey> thats yes surely, it's positive
[21:21] <czajkowski> i'd like to see turkey come back next month with a bit more detail and preferably more people present or we can take it to email
[21:21] <popey> <- mathematics fail
[21:21] <czajkowski> or does it mean 2 and a pass....
[21:21] <huats> bytan, I am clearly pleased by your team work.I am just a bit disapointed by the application that is not presenting your great work :(
[21:22] <bytan> i understand that.
[21:23] <popey> bytan: can you build up that wiki page with some more detail?
[21:23] <popey> and then email the loco council when done and we can disucss over email?
[21:23] <bytan> ReapprovalApplication wiki page?
[21:23] <popey> yes
[21:24] <popey> add detail about the things the loco does, activities?
[21:25] <popey> is that okay?
[21:25] <bytan> of course, we can do that and we inform you again
[21:25] <itnet7> bytan: according to the re-approval wiki it seemed as though you were in pause since like 2008
[21:25] <itnet7> and we know that's not the case
[21:25] <popey> bytan: just update the wiki with what's been happening in the loco over the last year, and then email loco-council@lists.ubuntu.com and we'll take a look and let you know right away.
[21:26] <popey> no need to attend another meeting
[21:26] <bytan> i understand what exactly you want, and we will email again
[21:26] <popey> magic!
[21:26] <czajkowski> thanks
[21:26] <popey> thanks!
[21:26] <itnet7> Thanks bytan !
[21:27] <popey> ok, lets move on to Peru
[21:27] <bytan> thanks all
[21:27] <popey> [TOPIC] Peru LoCo Approval Application
[21:27] <MootBot> New Topic:  Peru LoCo Approval Application
[21:27] <popey> Anyone here from Peru!?
[21:28] <huats> popey, I have just pinged nxvl on another channel without answer yet
[21:28] <popey> heh, ditto :)
[21:29] <popey> ok, lets move on then
[21:29] <popey> [TOPIC] Tamil Nadu LoCo Re-Approval Application
[21:29] <MootBot> New Topic:  Tamil Nadu LoCo Re-Approval Application
[21:29] <popey> Anyone from the Tamil Nadu team here?
[21:30] <nxvl> here
[21:31] <huats> ah nxvl finally !
[21:31] <popey> aha
[21:31] <nxvl> sorry, was picking my sister from school
[21:31] <popey> nxvl: are you / your team ready?
[21:31] <huats> popey, may be we can go again to Peru since noone shows up from Tamil Nadu
[21:31] <nxvl> i'm just asking michael to join us
[21:31] <popey> sure, if they're ready
[21:32] <nxvl> he was the one in charge of putting the missing web page together
[21:32] <nxvl> since he is in charge of the events
[21:32] <popey> [TOPIC] Peru LoCo Approval Application
[21:32] <MootBot> New Topic:  Peru LoCo Approval Application
[21:32] <nxvl> which was the part missing last time
[21:32] <nxvl> here he is
[21:32] <nxvl> xander21c: your audience
[21:32] <xander21c> Hi
[21:33] <popey> hi
[21:33] <popey> can you tell us a bit about what the Peru LoCo has been doing this year?
[21:34] <xander21c> Well
[21:34] <xander21c> we have participated on many events
[21:34] <nxvl> pictures!
[21:35] <xander21c> also work on improved colaboration between Ubuntu Peru and other Local communities
[21:35] <nxvl> http://picasaweb.google.com/xander21c
[21:35] <MootBot> LINK received:  http://picasaweb.google.com/xander21c
[21:36] <nxvl> wait, that's outdated
[21:36] <nxvl> but you have a couple of end of last year events
[21:36] <nxvl> like this one: http://picasaweb.google.com/xander21c/FESOLI2009#
[21:37] <popey> do the loco council have any questions?
[21:38] <itnet7> xander21c: Has your team done team reports?
[21:38] <huats> popey, where is the app link ?
[21:38] <popey> oops
[21:38] <popey> [LINK] https://wiki.ubuntu.com/PeruvianTeam/ApprovalApplication
[21:38] <MootBot> LINK received:  https://wiki.ubuntu.com/PeruvianTeam/ApprovalApplication
[21:38] <huats> :)
[21:38] <huats> (I was just asking for mootbot)
[21:39] <popey> good man
[21:39] <huats> xander21c, is it normal that there is nothing under experiences ?
[21:39] <xander21c> no
[21:40] <huats> xander21c, the wiki page is quite outdated to me (since I know nxvl is a MOTU for almost 2 years)
[21:40] <popey> Where does most of the team communication happen? The mailing list seems quite idle.
[21:40] <nxvl> huats: 2 years an a month actually
[21:40] <nxvl> but we forgot to update that exact part
[21:40] <xander21c> actually we are working on the website and other services (list, wiki update, etc)
[21:41] <nxvl> wait
[21:41] <xander21c> a new website and stuff
[21:41] <nxvl> that's the app aplication
[21:41] <nxvl> we are on re-aproval
[21:41] <nxvl> xander21c: isn't that in a different page?
[21:42] <nxvl> oh no that's the page, they forgot to update that part :S
[21:42] <nxvl> we also have a second MOTU
[21:42] <nxvl> well, had
[21:42] <nxvl> not Florida loco steal him from us
[21:42] <nxvl> :P
[21:42] <itnet7> We stole him
[21:42] <nxvl> now*
[21:42] <itnet7> :-)
[21:43] <nxvl> itnet7: you evil!
[21:43] <popey> how come the website is down?
[21:43] <nxvl> is it down?
[21:44] <nxvl> the wiki is up
[21:44] <nxvl> http://www.ubuntu-pe.org/
[21:44] <MootBot> LINK received:  http://www.ubuntu-pe.org/
[21:44] <nxvl> it's up
[21:44] <nxvl> works here at least
[21:44] <xander21c> yes
[21:44] <xander21c> was down yesteardy :)
[21:44] <popey> Mantenimiento
[21:44] <popey> Volveremos pronto!
[21:44] <popey> is all I see
[21:44] <nxvl> that's weird
[21:44] <xander21c> refresh
[21:44] <jfalco> working here
[21:45] <etank> i see it too
[21:45] <popey> ok now
[21:45] <popey> how odd
[21:46] <nxvl> viperhood have had a couple of issues with the page AFAIK, since canonical doesn't give him enough permissions to edit stuff, i'm assuming he is asking for to much
[21:46] <nxvl> and we are moving to a new server soon
[21:46] <nxvl> own controled server so he can play a bit more with it
[21:46] <popey> sorry, i didnt hget an answer to my question earlier i think
[21:46] <nxvl> but he is in classes right now, IIUC
[21:47] <popey> 21:40:05 <@popey> Where does most of the team communication happen? The mailing list seems quite idle.
[21:47] <nxvl> i didn't saw it
[21:47] <nxvl> we have a channel on freenode
[21:47] <nxvl> where people come an ask
[21:48] <nxvl> in peru there are a lot of ML, and they have a really bad (forgot the word, but people think really bad about MLs)
[21:48] <itnet7> nxvl: does the team do team minutes? Or any team reporting?
[21:48] <nxvl> not that i'm aware of
[21:48] <nxvl> i need to admit i'm to busy lately to be really involved
[21:48] <xander21c> popey: usually gets more traffic after a release
[21:48] <nxvl> i try to help with what i can, but it's not much
[21:49] <nxvl> reputation, the work was reputation!
[21:49] <itnet7> the word!
[21:49] <itnet7> gotcha!
[21:49] <nxvl> yeah, that
[21:49] <itnet7> :-)
[21:49] <nxvl> it's afternoon
[21:50] <nxvl> my brain is tired at this time of the day
[21:50] <nxvl> :P
[21:50] <popey> ok, time to vote (LoCo Council members only)
[21:50] <popey> [VOTE] Approval of Peru LoCo Team.
[21:50] <MootBot> Please vote on:  Approval of Peru LoCo Team..
[21:50] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[21:50] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[21:50] <xander21c> itnet7: actually I was working with Dante Diaz (vipehoot) in order to refresh the site, an planning ways to keep everything update
[21:51] <huats> +0 since I'd like  as for the Turkish team a real application...
[21:51] <MootBot> Abstention received from huats. 0 for, 0 against. 1 have abstained. Count is now 0
[21:51] <czajkowski> -1
[21:51] <MootBot> -1 received from czajkowski. 0 for, 1 against. 1 have abstained. Count is now -1
[21:51] <popey> +0
[21:51] <MootBot> Abstention received from popey. 0 for, 1 against. 2 have abstained. Count is now -1
[21:51] <itnet7> +0 I would like to some team reporting, I know that the Peru team is very active
[21:51] <MootBot> Abstention received from itnet7. 0 for, 1 against. 3 have abstained. Count is now -1
[21:51] <popey> I too would like to see team reports, and more evidence of activity over the last year.
[21:51] <popey> [ENDVOTE]
[21:51] <MootBot> Final result is 0 for, 1 against. 3 abstained. Total: -1
[21:51] <popey> Sorry guys, not this time.
[21:53] <popey> ok, last team
[21:53] <itnet7> xander21c: it's hard to vote a +1 when you can't see any currrent events documented easily on the Re-Approval page
[21:53] <popey> [TOPIC] Kentucky LoCo ReApproval
[21:53] <MootBot> New Topic:  Kentucky LoCo ReApproval
[21:53] <xander21c> don't worry
[21:54]  * etank is here from Kentucky
[21:54]  * jkeyes0 is here from Kentucky as well.
[21:54]  * jfalco too
[21:54] <Garon> here from Kentucky as well
[21:54] <etank> Hi all. As a team we have been working to communicat about the existance of Linux our local area about the existance of Linux. We have done this through having regular meetings that are open to the public. Our goal is to have beginner level information at each meeting so that we do not talk over anyones head. At the same time we try to have some more advanced topics so the members that have been
[21:54] <etank> using Linux for a long time do not get bored. https://wiki.ubuntu.com/KentuckyTeam/ReApprovalApplication
[21:54] <itnet7> https://wiki.ubuntu.com/KentuckyTeam/ReApprovalApplication
[21:55] <etank> should have used the spell check in gedit for that :)
[21:55] <itnet7> [LINK] https://wiki.ubuntu.com/KentuckyTeam/ReApprovalApplication
[21:55] <MootBot> LINK received:  https://wiki.ubuntu.com/KentuckyTeam/ReApprovalApplication
[21:55] <itnet7> SOrry
[21:55] <popey> thanks :)
[21:55] <popey> Would it be fair to say you're more a LUG than a LoCo?
[21:56] <etank> i think so
[21:56]  * volci is here from kentucky
[21:56] <jfalco> Well kinda of, we've merged the LoCo into the lug to ease the admin duties
[21:57] <jkeyes0> in the beginning, a majority of our users were using Ubuntu only, but as we've grown, a lot of members use other distros, and we don't want to exclude anyone.
[21:57] <etank> we are focused on spreading Linux and the resources that the LoCo provides us helps that effort a great deal
[22:00] <itnet7> Does your team do team reports? and archive minutes of LoCo IRC meetings?
[22:00] <etank> we spoke to paultag (think that is his proper nick) about being a lug before applying again
[22:00] <etank> we do archive our meeting logs
[22:01] <etank> but we have not done team reports
[22:01] <jfalco> http://bglug.net/meetings/bglug/2010/
[22:01] <MootBot> LINK received:  http://bglug.net/meetings/bglug/2010/
[22:01] <jfalco> http://bglug.net/irc/irc-meetings/
[22:01] <MootBot> LINK received:  http://bglug.net/irc/irc-meetings/
[22:02] <etank> we changed hosting providers not too long ago and have not updated some of the log information
[22:02] <jfalco> http://bglug.net/wiki/Main_Page
[22:02] <MootBot> LINK received:  http://bglug.net/wiki/Main_Page
[22:02] <etank> but the majority is available
[22:02]  * jfalco looks for old logs
[22:02] <etank> and some of our old meeting logs are on the ubuntu wiki (or should be)
[22:03] <etank> https://wiki.ubuntu.com/KentuckyTeam/Meetings
[22:03] <etank> it was in January of 2009 that we merged into a LUG
[22:03] <itnet7> [LINK] https://wiki.ubuntu.com/KentuckyTeam/Meetings
[22:03] <MootBot> LINK received:  https://wiki.ubuntu.com/KentuckyTeam/Meetings
[22:03] <jfalco> MootBot must not like etank
[22:04] <etank> we have been working hard to have regular IRL meetings on a monthly basis
[22:04] <itnet7> it's the s in https I believe that causes you to require the square bracket LINK
[22:04] <etank> we normally have 1 or 2 irc meetings each month as well
[22:05] <itnet7> I would like to see all of you put a little more effort into Team Reports. It's important to share with the rest of the community what you are doing
[22:05] <itnet7> It doesn't take that long, and I would be happy to help you set up an easy way to manage it thanks to nhandler !
[22:06] <jfalco> Hoe bout our blog? http://bglug.net tons of info there
[22:06] <etank> itnet7: do the reports get added to the wiki
[22:06] <etank> or is it through email?
[22:06] <itnet7> etank: it is part of the wiki
[22:06] <etank> itnet7: so after regular meetings just update a Team Report?
[22:07] <itnet7> I am in your channel I can show you afterwards how the Florida team is doing it
[22:07] <etank> that is something that we can do
[22:07] <etank> sounds good
[22:07] <itnet7> it takes less than 5 minutes
[22:07] <itnet7> a month
[22:07] <jfalco> cool
[22:07] <itnet7> but it's worth it's weight in Gold!
[22:07] <czajkowski> team reports are very important!!!!
[22:07] <popey> [ACTION] itnet7 to show Kentucky how AWESOME team reports are
[22:07] <MootBot> ACTION received:  itnet7 to show Kentucky how AWESOME team reports are
[22:07] <czajkowski> it makes myself and nhandler happy to see them
[22:08] <itnet7> they are included in each month's UWN
[22:08] <jfalco> lots of good discussion here too: http://groups.google.com/group/bglug
[22:08] <itnet7> do you have any member's in the LoCo that are Ubuntu Members?
[22:08] <etank> i am
[22:08] <etank> and bkingx is as well
[22:08] <itnet7> cool!
[22:08] <Garon> I am
[22:08] <itnet7> Nice!
[22:09] <etank> Garon: really? :)
[22:09] <jfalco> me too
[22:09] <itnet7> gj jfalco
[22:09] <popey> ok, I think we're set to vote..
[22:09] <popey> [VOTE] Kentucky Fried LoCo Re-Approval
[22:10] <MootBot> Please vote on:  Kentucky Fried LoCo Re-Approval.
[22:10] <MootBot> Public votes can be registered by saying +1/-1/+0 in the channel, private votes by messaging the channel followed by +1/-1/+0  to MootBot
[22:10] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[22:10] <popey> only loco council vote please
[22:10] <popey> +1
[22:10] <MootBot> +1 received from popey. 1 for, 0 against. 0 have abstained. Count is now 1
[22:10] <itnet7> +1
[22:10] <MootBot> +1 received from itnet7. 2 for, 0 against. 0 have abstained. Count is now 2
[22:10]  * popey pokes huats and czajkowski 
[22:10] <popey> *tension*
[22:10] <huats> +1
[22:10] <MootBot> +1 received from huats. 3 for, 0 against. 0 have abstained. Count is now 3
[22:10] <czajkowski> +1
[22:10] <MootBot> +1 received from czajkowski. 4 for, 0 against. 0 have abstained. Count is now 4
[22:10] <popey> \o/
[22:10] <popey> nice one
[22:10] <czajkowski> sorry lag
[22:10] <popey> [ENDVOTE]
[22:10] <MootBot> Final result is 4 for, 0 against. 0 abstained. Total: 4
[22:10] <jfalco> w00t
[22:10] <itnet7> \o/
[22:10] <jkeyes0> thanks guys. :)
[22:10] <etank> thank you all for your input
[22:11] <volci> thanks!
[22:11] <popey> keep up the great work!
[22:11] <volci> we look forward to implementing it :)
[22:11] <jfalco> ok got a plane to catch, thanks guys
[22:11] <Garon> thanks guys
[22:11] <volci> i have another appt to get to myself... bfn!
[22:11] <itnet7> bye jfalco ttys
[22:11] <popey> nhandler: you about?
[22:14] <popey> thats a no
[22:14] <czajkowski> short meeeting
[22:14] <czajkowski> ish
[22:14] <huats> indeed
[22:14] <popey> ok, so thats all
[22:15] <popey> [TOPIC] AOB?
[22:15] <MootBot> New Topic:  AOB?
[22:15] <czajkowski> rest of teams need to be done before end of october
[22:15] <czajkowski> should we mail them all and process them via mail
[22:15] <czajkowski> ones that were unapproved need following up
[22:15] <popey> yup
[22:16] <popey> czajkowski: you around for a conf call tomorrow evening?
[22:16] <popey> and anyone else interested?
[22:16] <itnet7> So no one had replied to my e-mail, what is our goal to finish the pending expirations or the original agreed upon list
[22:16] <popey> ah, missed that
[22:16] <itnet7> what time popey?
[22:16] <popey> same time as this meeting?
[22:16] <popey> 20:00 UTC?
[22:17] <popey> just leave mumble/skype connected and work through this stuff
[22:17] <itnet7> uhm, I don't know if I can pull that off, I was only able to make this full meeting as I'm home sick
[22:17] <popey> awww
[22:17] <itnet7> I can try to leave early
[22:17] <popey> get off to bed dude!
[22:17] <czajkowski> popey: i am indeed
[22:18] <popey> well, if you're on irc/mail we can use that too to keep everyone up to speed
[22:18] <czajkowski> ok
[22:18] <popey> i just happen to have an empty evening tomorrrow
[22:19] <huats> sorry I won't be able tomorrow
[22:19] <itnet7> cool, I will try to get off early
[22:19] <popey> ok, we'll keep the wiki updated and use the irc channel too
[22:19] <popey> just so everyone knows whats happening
[22:19] <popey> cool?
[22:20] <czajkowski> sure
[22:20] <popey> shall we arrange for next meeting in two weeks?
[22:20] <czajkowski> yup
[22:20] <popey> 5th October 20:00 UTC ?
[22:21] <popey> week before release! eek!
[22:21] <czajkowski> we;re not having to release anything
[22:21] <czajkowski> :)
[22:21] <czajkowski> right i need to leave the pub now
[22:21] <czajkowski> toodles
[22:21] <popey> heh
[22:21] <popey> #endmeeting
[22:21] <MootBot> Meeting finished at 16:21.
[22:22] <jkeyes0> later guys. :)
[22:23] <popey> o/