[11:33] <jasonjang> Good morning~ Mr. Lamont
[11:33] <lamont> so far
[11:33] <jasonjang> ^^
[11:35] <jasonjang> 11:34 am ?
[11:40] <jasonjang> lamont: A day ago, I mailed U.           If U feel free, please read my mail. rt #18364. THX C ya~
[11:41] <lamont> jasonjang: does this really want to be in #ubuntu-meeting, maybe you want #ubuntu-mirrors?
[11:42] <jasonjang> Hmmm.. Web site DNS fixing of LoCo team, ubuntu-kr.org
[12:26] <jasonjang> Oh~ Mr. LaMont jones. I realized Ur location LATEY, I'm sorry if i disturded sleep.
[12:26] <jasonjang> I'm sorry if i disturbed sleep.
[12:26] <lamont> I'm actually in UK this week, and focused on other things atm
[12:27] <jasonjang> OK. THX.
[12:28] <jasonjang> C U later all~
[16:01] <smoser> o/
[16:01] <smb> \o
[16:02] <hallyn> \o
[16:06] <hallyn> Daviey, yo
[16:08] <zul> hi
[16:08] <Daviey> hey hallyn
[16:08] <hallyn> Daviey, ready to roll?
[16:09] <hallyn> its past 1600 utc
[16:09] <Daviey> hallyn: good point.. Who is chairing?
[16:09]  * hallyn points at Daviey
[16:09] <Daviey> hallyn: i did week before last.. Ursinha is next on the list.
[16:09] <hallyn> haha, i just put her on there 2 mins ago :)
[16:09]  * Daviey is to blame for not updating the wiki.
[16:09] <hallyn> Ursinha, ready?
[16:09] <Daviey> Sorry for being absent, on a call.
[16:10] <hallyn> jamespage, want to take your turn?
[16:10] <Daviey> jamespage is sprinting..
[16:11] <Daviey> smoser: can you drive?
[16:11] <hallyn> perhaps we should adjourn
[16:11] <smoser> i can drive.
[16:11] <smoser> although i'd jsut as well second the motion to adjourn
[16:11] <smoser> :)
[16:11] <smoser> #start-meeting Ubuntu Server Team
[16:11] <soren> (no dash)
[16:11] <hallyn> since the only action item is regarding jamespage who isn't here
[16:11] <smoser> #start meeting Ubuntu Server Team
[16:12] <smoser> gah
[16:12] <soren> (no space either)
[16:12] <smoser> #startmeeting Ubuntu Server Team
[16:12] <meetingology> Meeting started Tue Nov 15 16:12:14 2011 UTC.  The chair is smoser. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[16:12] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[16:12] <jamespage> o/
[16:12] <smoser> ok
[16:12] <jamespage> around but am at a sprint :-)
[16:13] <hggdh> ~ô~
[16:13] <smoser> #TOPIC Review ACTION points from previous meeting
[16:13] <smoser> ACTION: smb, jamespage, hggdh to work on triaging bug #790712 (carry over)
[16:13] <smoser> smoser, jamespage hggdh ? anything there?
[16:14] <smb> hggdh has closed it after verifying it did not occur on precise
[16:14] <hggdh> smoser: done, I closed the bug fixreleased on Precise, wontfix on oneiric and natty (after talking with smb)
[16:14] <smoser> thank you sir.
[16:14] <Daviey> smb: accidental fix, or something resolved it?
[16:14] <hggdh> unknown fix
[16:14] <smb> smb, magic
[16:14] <hggdh> act of god?
[16:14] <smb> Daviey, ^
[16:14] <Daviey> \o/
[16:14] <Daviey> It's fixed, that is the main thing. :)
[16:14] <smoser> #TOPIC Precise Development
[16:15] <Daviey> Blueprints, Blueprints, Blueprints.
[16:15] <smoser> The thing to be aware of is that feature definition freeze is coming up
[16:15] <smoser> https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule?action=show&redirect=PreciseReleaseSchedule
[16:15] <Daviey> Many of the blueprints are not fully spec'd out.  They need to be final by EoW..  Please keep in mind that robbiew and myself need time to review before this.
[16:15] <smoser> bad url.
[16:15] <smoser> https://wiki.ubuntu.com/PrecisePangolin/ReleaseSchedule
[16:15] <hallyn> smoser, and what exactly does that mean?  all 'actions' must be in the blueprints?
[16:16] <robbiew> All workitems need to be in the blueprints
[16:16] <hallyn> k
[16:16] <smoser> well, realistically it means someone (robbiew) has to end up saying "yes we're going to work on this" for this cycle
[16:16] <roaksoax> o/
[16:16] <robbiew> so we can effectively track our progress and workload
[16:16] <Daviey> Are there any questions regarding blueprint process?
[16:16] <smoser> and you have to provide him with enough info to actually make that decision
[16:16] <robbiew> smoser: exactly...thx
[16:17] <utlemming> as a point of clarification, are work items just little "TODO" labels in the blueprint?
[16:17] <Daviey> If anyone does have any questions, please raise them in #ubuntu-server after the meeting.
[16:17] <Daviey> utlemming: err, TODO is appended to the end
[16:17] <smoser> utlemming, https://wiki.ubuntu.com/WorkItemsHowto
[16:18] <smoser> moving on
[16:18] <Daviey> Next on development... zul, cobbler merge.. any progress?
[16:18] <smoser> moving back
[16:18] <zul> still waiting for 2.2.2 but we are closer
[16:18] <Daviey> zul: can we not get a snapshot in this week?
[16:18] <roaksoax> zul: did they merge your patches yet?
[16:19] <zul> Daviey: yeah we can..
[16:19] <zul> roaksoax: not yet
[16:19] <Daviey> Really want to land Clint and rbasak's security fixes asap.
[16:19] <Daviey> hallyn: libvirt merge from sid?
[16:19] <zul> Daviey: will do it this afternoon
[16:19] <hallyn> Daviey, haven't started it
[16:19] <hallyn> should be trivial
[16:19] <Daviey> bug 890036 fyi
[16:19] <hallyn> yeah yeah yeah :)
[16:19] <hallyn> i think we want 7-3 by now
[16:19] <hallyn> they're moving fast
[16:20] <Daviey> bug 607039 needs an assignee.
[16:20] <Daviey> anyone keen to work with NFS, please sign up to it.
[16:20] <zul> *snicker*
[16:20] <hallyn> hm, well the automount part, i am going to have to look at autofs wrt namespaces real soon now
[16:21] <Daviey> i think bug 888671, just needs a final review and sponsor.. smoser, i'd quite like your thoughts on that
[16:22] <smoser> i have no expertise there, but i'll take a look after meeting
[16:22] <Daviey> adam_g: cobbler-enlist.. have you been able to touch it?
[16:22] <Daviey> smoser: it's more that i'd like a second opinion.
[16:23] <smoser> k.
[16:23] <Daviey> zul: bug 871278, will land this Friday in Precise right?
[16:23] <zul> Daviey: yeah
[16:23] <Daviey> zul: can you, or walk someone through the SRU process if required?
[16:24] <zul> Daviey: ack
[16:24] <Daviey> mcollective.. switching to activemq.. any concerns?
[16:24] <Daviey> via bug 874981
[16:24] <Daviey> make them known on the bug if so.
[16:25] <Daviey> zul: bug 879853, missing patches still?
[16:25] <zul> Daviey: yeah
[16:25] <Daviey> jdstrand: would you be happy to do a MIR review of bug 889243? :)
[16:26]  * Daviey will follow up with koolhead regarding bug 875262
[16:26] <jdstrand> Daviey: I wasn't sure how appropriate it would be for me to do that. if you guys have dotted all the Is and crossed the Ts already, then I can talk a look
[16:26] <Daviey> roaksoax: bug 880339? :)
[16:27] <Daviey> zul: Do you consider the I's and T's dotted?
[16:27] <zul> Daviey: i think so
[16:27] <roaksoax> Daviey: again, I tested this in two oneiric machines and didn't see any issues
[16:27] <Daviey> bug 887410, needs an assignee... seemingly biteish-size if someone wants to grab it.. anyone?
[16:28] <Daviey> roaksoax: can you mark it invalid if you believe so, and state what you did to test?
[16:28] <zul> Daviey:  clint should probably look at the plymouth one
[16:28] <Daviey> hallyn: Progress to get bug 876768 fixed in Debian?
[16:28] <Daviey> zul: good idea.
[16:29] <hallyn> Daviey, none.
[16:29] <Daviey> ok
[16:29] <hallyn> Need to find a sponsor.
[16:29] <Daviey> utlemming: need a hand with bug 881464?
[16:29] <hallyn> (the one i asked is too busy)
[16:29] <Daviey> hallyn: Ah, if that is all you are blocked on.. we can get that fix0rd!
[16:29] <hallyn> yes, that's all.
[16:29] <hallyn> packaging is done from my pov
[16:32] <smoser> Daviey, anything else ?
[16:32] <Daviey> I don't think so
[16:33] <Daviey> Anything from anyone else?
[16:33] <Daviey> Any other bugs that should be tracked?
[16:33] <Ursinha> (sorry guys, I forgot today would be a national holiday)
[16:33] <Daviey> (please do raise them)
[16:33] <Daviey> Ursinha: No problem, we'll catch up tomorrow.
[16:33] <smoser> #TOPIC Ubuntu Server Team Events
[16:34] <smoser> anyone ?
[16:35] <smoser> #TOPIC Weekly Updates & Questions for the QA Team (hggdh)
[16:35] <Daviey> hey hallyn !
[16:35] <Daviey> err, hggdh
[16:35] <hggdh> heh
[16:35] <smoser> hggdh, you have anything ? anyone have anything for hggdh ?
[16:35] <hggdh> OK
[16:35] <Daviey> hggdh / jamespage: how is the sprint going?
[16:35] <Daviey> Any outcomes so far?
[16:35] <hggdh> still on its infacy, I think (I am remote, due to family illness)
[16:36] <hggdh> please do not forget the tests...
[16:36] <jamespage> TBH first half of week is tear down and rebuild the Ubuntu QA test lab :-)
[16:36] <Daviey> hggdh: The human based testing needs a serious refresh, right?
[16:36] <jamespage> OpenStack testing servers are now racked - power and network in progress
[16:36] <Daviey> (methodology.)
[16:36] <hggdh> yes, it does, and we are looking at them
[16:36] <Daviey> jamespage: That is great to hear!
[16:37] <Daviey> hggdh: Okay.. are you drafting a list of areas that need fixing?
[16:37] <hggdh> Daviey: and the unittests we currently have need beefing up
[16:38] <hggdh> Daviey: yes, we will be doing it. Meanwhile, please remember to start adding tests to the patches
[16:38] <robbiew> jamespage: \0/
[16:38] <Daviey> hggdh: Okay, will you be able to report next week where we need improvement?
[16:38] <hggdh> Daviey: most certainly
[16:38] <Daviey> hggdh: 'tests to the patches'?
[16:38] <hggdh> Daviey: well, if a patch changes something (which usually happens), then it would be nice to have an unit test for it
[16:39] <Daviey> hggdh: a package derived unit test, if the package supports it's own unit testing?
[16:40] <hggdh> Daviey: EVEN better!
[16:40] <hggdh> then we can run it anytime
[16:40] <Daviey> Hmm.. We don't yet have a framework for external unit tests, do we?
[16:40] <Daviey> other than the lp:qa-regression-suite , right?
[16:40] <hggdh> no, not yet. By end-of-week we should have directions
[16:41] <Daviey> hggdh: great
[16:41] <hggdh> and this is it from me
[16:41] <hggdh> ..
[16:41] <Daviey> thanks hggdh !
[16:41] <smoser> #TOPIC Weekly Updates & Questions for the Kernel Team (smb)
[16:41]  * smb has two things...
[16:41] <smb> First bug 881076: Workaround (idle=halt) proposed and smoser has build images. Upstream still discussing how to really fix this.
[16:42] <smoser> smb, well, imags have not successfully been built as a result of a perl issue at the moment.
[16:42] <smb> So s/has/will/ :)
[16:43] <Daviey> smoser: since when?
[16:43] <smb> Anyway, the "right" fix seems to be highly debatable. I follow it upstream
[16:43] <smoser> perl transition.
[16:44] <smoser> so once that gets sorted out, we'll get images iwith that ahck around.
[16:44] <Daviey> great
[16:44] <smb> The second thing is that I have been reading my work item about openvswitch today (this time with my brains actually turned on). And somehow I remember the request a bit differently. IMO it was to bring the package into main, not the module into the kernel...
[16:44] <Daviey> smb: is bug 854050 fixed in Precise?
[16:45] <smoser> smb, i would think we'd need both.
[16:45] <Daviey> smb: I don't see why it should be in the kernel, dkms makes more sense until it's mainline upstream, right?
[16:45] <smb> Daviey, I need to check, this has been a bit of a fail on the maintainer submission
[16:45] <smb> smoser, I'd be with Daviey there
[16:45] <smoser> ah. yeah, dkms is fine.
[16:45] <smoser> i thought you were implying it was in kernel just not enabled.
[16:45] <smb> It just makes things prone to bit rot in any part
[16:46] <smb> Ah k. No the package provides a dkms binary
[16:46] <smb> But the package is in universe right now, so I think that need an mir
[16:46] <smoser> right.
[16:47] <smoser> Daviey, we want an action for mir of openvswitch?
[16:47] <smoser> at least to open bug. if its agreed, then i'll take action
[16:48] <smoser> smoser, just fyi, i'd like bug 890447 addressed.
[16:48] <smb> Daviey, After looking quickly the patch for 854050 is not upstream yet
[16:48] <Daviey> smoser: Hmm, are we MIR'ing NaaS componet?
[16:48] <Daviey> Quantum
[16:48] <smoser> i think no
[16:48] <zul> no
[16:48] <smb> smoser, Noted as I think you meant me :)
[16:48] <zul> its not part of core project so it stays in universe
[16:48] <Daviey> So what part needs openvswitch?
[16:49] <smoser> smb i did indeed.
[16:49] <Daviey> Don't you need Quantum for openvswitch?
[16:49] <smoser> you need neither for neither explicitly
[16:49] <smoser> but likely quantum would use openvswitch, at least in the open source paths.
[16:49] <zul> why is openvswitch getting MIRed again?
[16:49] <smoser> but anyway, it i think it is not. i'm not sure why this came up, and i responded poorly.
[16:50] <Daviey> zul: that is what i am trying to find out
[16:50] <smoser> anyone have a reason as to why openvswitch should be MIRd?
[16:50] <Daviey> Are we MIR'ing a a non openstack option, or something to use as openstack?
[16:50] <zul> i dont
[16:50] <smoser> ok. unless someone provides one, we are not.
[16:50] <medberry> will Quantum have any usefulness without it?
[16:50] <hallyn> i thought we wanted it for openstack i think
[16:50] <hallyn> lemme look over the mtg notes
[16:50] <smoser> ugh.
[16:51] <smoser> ok. i think this is all true:
[16:51] <Daviey> medberry: Yes, but if Quantum is in universe, there is no archive requirement for openvswitch to be in main
[16:51] <smoser>  * quantum can use openvswitch.
[16:51] <zul> quantum is *not* going into main
[16:51] <medberry> Daviey, nod.
[16:51] <Daviey> Unless there is another use-case we care about?
[16:51] <smoser>  * quantum can use other networking back ends
[16:51] <medberry> gotcha.
[16:51] <smoser>  * quantum will is not a part of openstack core (or whatever thats called) for essex
[16:51] <Daviey> smoser: table this, unti we get more info.
[16:51] <medberry> yep, quantum can use real hardware
[16:51] <smoser>  * some parties have requested we support quantum
[16:51] <smoser> moving on.
[16:52] <smoser> smb, you have ability to at least assign that depmod bug to the rigth person?
[16:52] <smb> smoser, Yes, or take it myself
[16:52] <smoser> please do.
[16:52] <Daviey> any other kernel bugs?
[16:52] <smoser> other than bugs listed, the kernel has no bugs
[16:53] <smoser> #TOPIC Weekly Updates & Questions regarding Ubuntu ARM Server (NCommander)
[16:53] <smoser> NCommander, ?
[16:53] <Daviey> (thanks smb)
[16:53] <smoser> i'm thinking this is a no-op?
[16:53] <smoser> #TOPIC Weekly Updates & Questions from the Ubuntu Community
[16:53] <Daviey> NCommander: your call starts in 7 mins.
[16:54] <smoser> Daviey, and this meeting is supposed to end in 7mins. so i say we move on.
[16:54] <smoser> any ubuntu community related stuff?
[16:54] <Daviey> Any new Ubuntu Server people here want to say hello?
[16:55] <zul> any shoutouts?
[16:55] <Daviey> no homie.
[16:55] <Daviey> smoser: next?
[16:55] <smoser> i've seen good things from a guy named Chuck Shortk
[16:55] <medberry> going going ....
[16:55] <smoser> #TOPIC Open Discussion
[16:56] <Daviey> Nothing from me.
[16:56] <smoser> #TOPIC Announce next meeting date and time
[16:57] <Daviey> rocking, thanks smoser
[16:57] <smoser> next meeting is Tuesday 2011-11-22 at 1600 UTC - #ubuntu-meeting
[16:57] <smoser> #endmeeting
[16:57] <meetingology> Meeting ended Tue Nov 15 16:57:12 2011 UTC.
[16:57] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-11-15-16.12.moin.txt
[16:57]  * smb got 3mins for a bio break...
[16:59] <ogasawara> #startmeeting
[16:59] <meetingology> Meeting started Tue Nov 15 16:59:52 2011 UTC.  The chair is ogasawara. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[16:59] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[17:00] <ogasawara> ##
[17:00] <ogasawara> ## This is the Ubuntu Kernel Team weekly status meeting.
[17:00] <ogasawara> ##
[17:00] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/Meeting
[17:00] <ogasawara> [LINK] https://wiki.ubuntu.com/KernelTeam/ReleaseStatus/Precise
[17:00] <ogasawara> # Meeting Etiquette
[17:00] <ogasawara> #
[17:00] <ogasawara> # NOTE: '..' indicates that you are finished with your input.
[17:00] <ogasawara> #       'o/' indicates you have something to add (please wait until you are recognized)
[17:00] <ogasawara> [TOPIC] ARM Status (ppisati)
[17:00] <ppisati> Besides the usual SRU kernels, there's nothing else to report.
[17:00] <ppisati> ..
[17:00] <ogasawara> [TOPIC] Release Metrics and Incoming Bugs (ogasawara)
[17:00] <ogasawara> [LINK] http://people.canonical.com/~kernel/reports/kt-meeting.txt
[17:00] <ogasawara> [17:00] <ogasawara>  * 32 linux kernel bugs (up 12)
[17:00] <ogasawara> [17:00] <ogasawara>  * 1 linux kernel bugs (up 1)
[17:01] <ogasawara> [17:01] <ogasawara>  * 0 precise linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 10 oneiric linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 10 natty linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 3 maverick linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 7 lucid linux kernel bugs (no change 0)
[17:01] <ogasawara>  * 0 hardy linux kernel bugs (no change 0)
[17:01] <ogasawara> [17:01] <ogasawara>  * 8 precise bugs (no change 0)
[17:01] <ogasawara>  * 635 oneiric bugs (down 5)
[17:01] <ogasawara>  * 1677 natty bugs (down 3)
[17:01] <ogasawara>  * 1099 maverick bugs (no change 0)
[17:01] <ogasawara>  * 979 lucid bugs (down 4)
[17:01] <ogasawara>  * 43 hardy bugs (down 3)
[17:01] <ogasawara> [17:01] <ogasawara> [17:01] <ogasawara>  * 0 precise bugs (no change 0)
[17:01] <ogasawara>  * 7 oneiric bugs (no change 0)
[17:01] <ogasawara>  * 19 natty bugs (no change 0)
[17:01] <ogasawara>  * 40 maverick bugs (no change 0)
[17:01] <ogasawara>  * 76 lucid bugs (no change 0)
[17:01] <ogasawara>  * 0 hardy bugs (no change 0)
[17:01] <ogasawara> [17:01] <ogasawara>  * 1 precise bugs (no change 0)
[17:01] <ogasawara>  * 61 oneiric bugs (up 6)
[17:01] <ogasawara>  * 434 natty bugs (no change 0)
[17:01] <ogasawara>  * 236 maverick bugs (no change 0)
[17:01] <ogasawara>  * 208 lucid bugs (no change 0)
[17:01] <ogasawara>  * 2 hardy bugs (no change 0)
[17:01] <ogasawara> [17:02] <ogasawara>  * 0 precise bugs (no change 0)
[17:02] <ogasawara>  * 1 oneiric bugs (no change 0)
[17:02] <ogasawara>  * 4 natty bugs (no change 0)
[17:02] <ogasawara>  * 0 maverick bugs (no change 0)
[17:02] <ogasawara>  * 2 lucid bugs (no change 0)
[17:02] <ogasawara>  * 0 hardy bugs (no change 0)
[17:02] <ogasawara> ..
[17:02] <ogasawara> [TOPIC] Milestone Targeted Work Items (ogasawara)
[17:02] <ogasawara> [LINK] http://status.ubuntu.com/ubuntu-precise/all-precise-alpha-1.html
[17:02] <ogasawara> I'll begin posting my nag table once the following url is generated and available - http://people.canonical.com/~platform/workitems/precise/canonical-kernel-team-oneiric-alpha-1.html is not yet available.
[17:02] <ogasawara> ..
[17:02] <ogasawara> [TOPIC] Status: Precise Development Kernel (ogasawara)
[17:02] <ogasawara> We have uploaded the 3.1.0-2.3 Ubuntu kernel which was based on the upstream v3.1 kernel. Upstream is in the early -rc releases of the v3.2 kernel, ie currently v3.2-rc1.  Given a higher likelihood for instability with an early -rc, we will hold off doing the first 3.2.0-1.1 upload until we rebase onto upstream v3.2-rc2. I would anticipate this prior to Alpha 1 (Thurs Dec 1). If there are any patches which need to land in
[17:02] <ogasawara> the 12.04 kernel, submit them now so that they receive adequate testing and feedback.
[17:03] <ogasawara> ..
[17:03] <ogasawara> [TOPIC] Status: CVE's (apw)
[17:03] <apw>  
[17:03] <apw> [LINK] http://people.canonical.com/~kernel/cve/pkg/CVE-linux.txt
[17:03] <apw>  
[17:03] <apw> Currently open CVEs for each supported branch:
[17:03] <apw>  
[17:03] <apw> || Package                                  || Open      ||
[17:03] <apw> ||                                          ||           ||
[17:03] <apw> || linux Hardy                              ||    8 (-5) ||
[17:03] <apw> || linux Lucid                              ||    5 (-2) ||
[17:03] <apw> || linux Maverick                           ||    6 (-4) ||
[17:03] <apw> || linux Natty                              ||    6 (-1) ||
[17:03] <apw> || linux Oneiric                            ||    4 (+2) ||
[17:03] <apw> || linux Precise                            ||    4      ||
[17:03] <apw> || linux-ec2 Lucid                          ||    5 (-2) ||
[17:03] <apw> || linux-fsl-imx51 Lucid                    ||    5 (-8) ||
[17:03] <apw> || linux-mvl-dove Lucid                     ||    5 (-2) ||
[17:03] <apw> || linux-mvl-dove Maverick                  ||    5 (-2) ||
[17:03] <apw> || linux-ti-omap4 Maverick                  ||    7 (-3) ||
[17:03] <apw> || linux-ti-omap4 Natty                     ||    6 (-3) ||
[17:03] <apw> || linux-ti-omap4 Oneiric                   ||    4 (+2) ||
[17:04] <apw> || linux-ti-omap4 Precise                   ||    4      ||
[17:04] <apw> || linux-lts-backport-maverick Lucid        ||    6 (-4) ||
[17:04] <apw> || linux-lts-backport-natty Lucid           ||    6 (-1) ||
[17:04] <apw> || linux-lts-backport-oneiric Lucid         ||    4      ||
[17:04] <apw>  
[17:04] <apw> We have had a fairly large number of new CVEs added since the last report.
[17:04] <apw> Progress continues well with the overall backlog remaining pretty much
[17:04] <apw> constant.  We retain a couple of stubourn CVEs which still have no fix
[17:04] <apw> upstream.  Some process fixes in the security team have brought down
[17:04] <apw> the number of pending fixes and produced USNs.
[17:04] <apw>  
[17:04] <apw> ..
[17:04] <ogasawara> [TOPIC] Status: Stable, Security, and Bugfix Kernel Updates - Oneiric/Natty/Maverick/Lucid/Hardy (bjf/herton)
[17:04] <ogasawara> bjf is sprinting and herton is on holiday.  We'll be updates next week.
[17:04] <ogasawara> ..
[17:04] <ogasawara> [TOPIC] Open Discussion or Questions? Raise your hand to be recognized (o/)
[17:05] <ogasawara> Meeting chair...I'll chair the next few meetings and then jsalisbury has graciously offered to chair indefinitely going forward.
[17:05] <ogasawara> ..
[17:05] <apw> awsome
[17:05] <ogasawara> unless anyone has anything else, I think that's a wrap.
[17:05] <apw> ..
[17:05] <ogasawara> #endmeeting
[17:05] <meetingology> Meeting ended Tue Nov 15 17:05:39 2011 UTC.
[17:05] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-11-15-16.59.moin.txt
[20:00] <czajkowski> itnet7: leogg huats
[20:00] <huats> hello everyone
[20:01] <czajkowski> #meeting
[20:01] <leogg> hey all
[20:01] <czajkowski> bah
[20:01] <kokoye2007> ya huats
[20:01] <czajkowski> #startmeeting
[20:01] <meetingology> Meeting started Tue Nov 15 20:01:22 2011 UTC.  The chair is czajkowski. Information about MeetBot at http://wiki.ubuntu.com/AlanBell/mootbot.
[20:01] <meetingology> Available commands: #accept #accepted #action #agree #agreed #chair #commands #endmeeting #endvote #halp #help #idea #info #link #lurk #meetingname #meetingtopic #nick #progress #rejected #replay #restrictlogs #save #startmeeting #subtopic #topic #unchair #undo #unlurk #vote #voters #votesrequired
[20:02] <czajkowski> #link https://wiki.ubuntu.com/LoCoCouncil/Agenda
[20:02] <czajkowski> hmm
[20:02] <czajkowski> tonights agenda https://wiki.ubuntu.com/LoCoCouncil/Agenda
[20:03] <czajkowski> kokoye2007: ready ?
[20:03] <kokoye2007> yeah
[20:03] <bonepyaesone> :)
[20:03] <czajkowski> #link https://wiki.ubuntu.com/MyanmarTeam/ApprovalApplication
[20:03] <czajkowski> ok
[20:03] <kokoye2007> we are from ubuntu-mm bonepyaesone TH_
[20:04] <czajkowski> kokoye2007: so want to tell us about your team ?
[20:04] <czajkowski> and what kind of things ye guys do in your loco please?
[20:05] <kokoye2007> http://enblog.u4mm.com
[20:05] <bonepyaesone> ok. we've done a lot of events in past 3 years
[20:05] <itnet7> here, now sorry
[20:05] <bonepyaesone> especially introduction ubuntu to public
[20:06] <TH_> now more active than before
[20:06] <czajkowski> ok, the wiki page seems a bit broken is it just my connection folks ?
[20:07] <czajkowski> you mention in your road map about a local repository, can you tell us more about this ?
[20:08] <czajkowski> bonepyaesone: TH_ kokoye2007 ?
[20:08] <itnet7> everything is looking good from me czajkowski !
[20:08] <TH_> local repository is more important for our country because our country connection
[20:08] <itnet7> Approval-wise
[20:09] <czajkowski> huats: leogg any other thoughts folks ?
[20:09] <bonepyaesone> we'll set up a repo server and syn every 2 week. And we distribute them as offline repo
[20:09] <bonepyaesone> :D
[20:09] <huats> I am quite happy to see so many pics
[20:10] <huats> seems like a good team actions
[20:10] <itnet7> I mean... wiki page
[20:10] <itnet7> but very good solid work
[20:10] <czajkowski> ok my only suggestion is for team reports folks
[20:10] <bonepyaesone> :D
[20:10] <czajkowski> are we ready to vote so ?
[20:10] <leogg> not from me, looks you guys been doing a great job
[20:10] <leogg> I'm ready
[20:11] <czajkowski> #voters leogg itnet7 huats czajkowski
[20:11] <meetingology> Current voters: czajkowski huats itnet7 leogg
[20:11] <czajkowski> #vote
[20:11] <meetingology> Please vote on:
[20:11] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (private votes don't work yet, but when they do it will be by messaging the channel followed by +1/-1/+0 to me)
[20:11] <leogg> +1
[20:11] <huats> +1
[20:11] <czajkowski> +1
[20:11] <AlanBell> vote needs a subject
[20:11]  * AlanBell goes to file a bug
[20:11] <czajkowski> itnet7: ping
[20:12] <bonepyaesone> :D
[20:12] <itnet7> +1
[20:12] <itnet7> sorry...
[20:12] <czajkowski> #endvote
[20:12] <meetingology> No vote in progress
[20:12] <czajkowski> clearly me and the bot are not going to see eye to eye
[20:13] <AlanBell> you will learn to love each other!
[20:13] <czajkowski> with 4 +1s you are now an approved loco
[20:13] <czajkowski> leogg: can you add to approved teams please
[20:13] <itnet7> Please, defintely share more of what your team is doing through team reports!!
[20:13] <leogg> czajkowski, sure!
[20:13] <czajkowski> leogg: thanks
[20:13] <czajkowski> #topic UDS blueprint
[20:13] <bonepyaesone> Thank you czajkowski  AlanBell  itnet7  and leogg
[20:13] <itnet7> Congrats!!
[20:13] <kokoye2007> Thank czajkowski AlanBell itnet7 leogg
[20:13] <czajkowski> #link https://blueprints.launchpad.net/ubuntu/+spec/community-p-lococouncil
[20:13] <TH_> thank you all
[20:13] <bonepyaesone> yeah!!
[20:13] <leogg> kokoye2007, bonepyaesone, congrats and thank you!
[20:14] <czajkowski> ok so for the remainder of the meeting we're going to look at the bp and add some of the action items to it
[20:14] <czajkowski> and review some of the items that came up
[20:14] <czajkowski> so twinnings idea came from popey suggestion
[20:14] <czajkowski> and I think it went down well at UDS
[20:14] <czajkowski> the idea being that an Approved loco would be twinned with an unapproved loco and help them in how to get started
[20:15] <czajkowski> and give them ideas
[20:15] <czajkowski> so we needed to come up with teams
[20:15] <czajkowski> which I think we more or less have done so ?
[20:15] <czajkowski> Ubuntu UK
[20:15] <czajkowski> Ubuntu France
[20:15] <itnet7> Ubuntu Florida
[20:15] <czajkowski> aye
[20:15] <czajkowski> Ubuntu Italy
[20:15] <czajkowski> leogg: what team did you suggest?
[20:16] <leogg> czajkowski, Ubuntu Nicaragua with Ubuntu Costa Rica
[20:16] <AlanBell> Ubuntu UK is up for it (no idea who to twin with)
[20:16] <AlanBell> bug 890843 has been reported
[20:16] <czajkowski> ok so that's 5
[20:17] <czajkowski> did we habe a 6th in mind ?
[20:17] <czajkowski> is there an approved team we think that has the time to help on this ?
[20:17] <czajkowski> or should we stick with 5 for this cycle and see how it works out
[20:17] <itnet7> I think we should stick with 5
[20:17] <czajkowski> ok
[20:18] <itnet7> just my opinion though
[20:18] <leogg> itnet7++
[20:18] <czajkowski> so we're agreed on thos teams and we need to contact their team contacts which I think we have done bar Italy to make sure they are up for it
[20:18] <czajkowski> and then create the bugs so we can track this during the cycle
[20:18] <itnet7> Yup
[20:18] <czajkowski> I really think this could work and then expand for furture cycles
[20:18]  * AlanBell wonders if itnet7++ makes itnet8
[20:18] <itnet7> ;-) AlanBell !
[20:19] <czajkowski> itnet7: do you have a team in mind for the Florida loco ?
[20:19] <leogg> AlanBell, ;)
[20:19] <itnet7> czajkowski: I was doing a bit of research, but haven't really decided
[20:19] <itnet7> I would like to try and pick a newer team
[20:20] <czajkowski> itnet7: ok, we'll create the bugs this week at least for those teams that are menotoring and then add the unapproved teams to it
[20:20] <czajkowski> itnet7: ok
[20:20] <czajkowski> need to find a team for Ubuntu UK also
[20:20] <czajkowski> #topic LTP renaming the main team page for teams
[20:20] <czajkowski> #link http://loco.ubuntu.com/teams/
[20:21] <czajkowski> this topic has been bouncing around for some time
[20:21]  * AlanBell wants to replace it with a second level of maps
[20:21] <czajkowski> if you land here on this page  looking for a team, it's hard to find the team you are looking for as they all have their own way of naming themselves
[20:21] <czajkowski> which is fine
[20:22] <czajkowski> what was proposed and agreed at UDS was the *display name* on this page alone would be changed by the developers
[20:22] <czajkowski> so it would read Team name loco
[20:22] <czajkowski> making it easier to find your team name if you are looking for infomation on one
[20:23] <czajkowski> so I think we should do a joint blog post with the LTP developers and explain in more detail the benfit of doing so
[20:23] <czajkowski> and to make it clear that nothing else is changing on the team name
[20:23] <itnet7> Sounds good to me
[20:23] <czajkowski> just the display name on the one page
[20:23] <czajkowski> itnet7: can you take an action item to work with the dev team to start that this week please
[20:24] <itnet7> Sure
[20:24] <czajkowski> #action itnet7  work with the dev team to start that this week please
[20:24] <meetingology> ACTION: itnet7  work with the dev team to start that this week please
[20:24] <czajkowski> #action itnet7  work with the dev team to start a blog post re team name display on loco.ubuntu.com/teams
[20:24] <meetingology> ACTION: itnet7  work with the dev team to start a blog post re team name display on loco.ubuntu.com/teams
[20:24] <czajkowski> ok
[20:24] <czajkowski> thanks
[20:25] <itnet7> I will add that to the blueprint after work today
[20:25] <czajkowski> #topic Larger teams to follow the example led by USA and follow state/provence break down
[20:26] <czajkowski> This was discussed again at UDS and the thought behind it was that counteries which are rather large such as Australia, Canada and possibly Brazil who have already done this should follow the example of USA
[20:27] <czajkowski> one main team and sub teams can be created depending on the level of activity in an provence/state like USA
[20:27] <czajkowski> It would benefit if some areas are very active so cd allocation would go to one state if they were approved rather that one country
[20:27] <czajkowski> in the future as teams grow it would be harder to then do this
[20:28] <czajkowski> so planning for team growth now for 2+ years and being pro active rather than being re active would make more sense
[20:28] <czajkowski> huats: itnet7 leogg any comments?
[20:28] <huats> I agree
[20:28] <itnet7> I agree that it would be a good idea, but I think you've pretty much covered the whys
[20:29] <leogg> me too, it makes perfectly sense to me
[20:29] <czajkowski> ok so we need to again explain this carefuly and clearly to teams so they don't get upset or worry. the reasons for this and the benefits for doing so
[20:29] <czajkowski> huats: leogg care to take an action item to draft this blog post please ?
[20:30] <leogg> sure
[20:30] <czajkowski> leogg: thanks
[20:30] <czajkowski> #action legg to draf blog post on larger teams being broken down into smaller teams like USA
[20:30] <meetingology> ACTION: legg to draf blog post on larger teams being broken down into smaller teams like USA
[20:31] <czajkowski> ok
[20:31] <czajkowski> #topic loco teams reappoval
[20:31] <czajkowski> status update on this, huats created the teams for re approval for this cycle
[20:31] <czajkowski> already we have teams applying which is great to see!
[20:31] <itnet7> +1
[20:31] <czajkowski> and we'll keep working on that this cycle
[20:32] <czajkowski> we only have 9 for re approval, but hopefully with mentoring and twining of teams we can see more approvals coming up through the ranks in the near future.
[20:32] <czajkowski> anyone have anything else to comment on ?
[20:33] <itnet7> I don't really have any
[20:33] <czajkowski> nope ok
[20:33] <czajkowski> #endmeeting
[20:33] <meetingology> Meeting ended Tue Nov 15 20:33:21 2011 UTC.
[20:33] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2011/ubuntu-meeting.2011-11-15-20.01.moin.txt
[20:33] <czajkowski> thanks for coming folks I know some of ye are at work
[20:34] <itnet7> Thanks czajkowski for running the meeting!
[20:34] <leogg> thanks czajkowski
[20:34] <AlanBell> thanks all, and thanks for finding that bug czajkowski :)
[20:34] <czajkowski> np
[20:34] <czajkowski> AlanBell: me and the bot are going to have to work togehter :)
[20:35] <AlanBell> I am going to schedule a meetingology sprint
[20:35] <AlanBell> please file bugs at https://bugs.launchpad.net/ubuntu-bots/+filebug and tag them meetingology
[20:43] <AlanBell> https://bugs.launchpad.net/ubuntu-bots/+bugs?field.tag=meetingology any more to add?
[21:04] <popey> AlanBell: like that idea!
[21:05] <czajkowski> AlanBell: you rock!
[21:07] <bonepyaesone> czajkowski: AlanBell itnet7 leogg  You all rock! :D