[07:06] <dholbach> good morning
[07:30] <davidcalle> bzoltan_, ping
[07:30] <bzoltan_> davidcalle: yo
[07:30] <davidcalle> bzoltan_, hey, very nice post on duc blog!
[07:31] <davidcalle> bzoltan_, I'm wondering why there is no sdk-ide package for wily in the PPA, is it something we can expect soon-ish?
[07:31] <bzoltan_> davidcalle:  thanks :) have you tried the new SDK?
[07:31] <bzoltan_> davidcalle:  so you want the wily edition?
[07:32] <bzoltan_> davidcalle:  I can do that for you today ...
[07:32] <davidcalle> bzoltan_, no rush, will there be an issue with the vivid package on wily?
[07:34] <didrocks> zsombi_: hey! I have a probably stupid question on QML and transitions
[07:34] <didrocks> zsombi_: http://doc.qt.io/qt-5/qtquick-modelviewsdata-modelview.html#using-transitions sounds promising to tell that you can have "removal" animation even on Flow or Grid when you remove an item from a model
[07:35] <didrocks> zsombi_: however, reading http://doc.qt.io/qt-5/qml-qtquick-flow.html, I only see add and move animation hooks, no removal
[07:35] <didrocks> I'm probably missing something very obvious
[07:36] <zsombi_> didrocks: yes, there's no removal animation on Flow
[07:36] <didrocks> ah, so that doc is a lie? :)
[07:36] <didrocks> (like the cake ;))
[07:36] <zsombi_> at least according to the doc
[07:37] <zsombi_> let me check the component
[07:37] <didrocks> yeah, I was thinking reading from http://doc.qt.io/qt-5/qtquick-modelviewsdata-modelview.html#using-transitions that there were a generic thing for it, but couldn't find any example
[07:37] <bzoltan_> davidcalle:  I am creating the wily packages and dput them in a sec
[07:38] <bzoltan_> davidcalle:  there could be compatibility issues yes ... you know gcc
[07:39] <zsombi_> didrocks: indeed, the QQuickPositionerBase has no remove
[07:39] <davidcalle> bzoltan_, thanks, also kudos for using the opportunity to rename to ubuntu-sdk-ide :)
[07:40] <didrocks> zsombi_: ok, thanks for checking! I should maybe open a bug against Qt for the other doc to tell it's not available on each components using a model. Thanks!
[07:40] <bzoltan_> davidcalle: LOL :) that was a long pending issue
[07:40] <zsombi_> didrocks: sure!
[09:16] <TheNumb> o/
[09:28] <popey> bzoltan_: does your email which includes "sudo apt-get install ubuntu-sdk-ide ubuntu-sdk-api-tools ubuntu-sdk-api-15.04-armhf ubuntu-sdk-api-15.04-i386" - presume I'm on amd64 machine? (given the names of those packages) ?
[09:30] <popey> bzoltan_: also - [M#qRE: Unable to locate package ubuntu-sdk-ide
[09:30] <popey> http://paste.ubuntu.com/12251947/ bzoltan_
[09:36] <davidcalle> popey, wily?
[09:38] <CaptainHeavy> ogra_: just posted a review for your KiwiIRC app, hopefully that should give you a few more downloads :)
[09:38] <popey> davidcalle: yes
[09:38] <davidcalle> popey, building -> https://launchpad.net/~ubuntu-sdk-team/+archive/ubuntu/tools-development/+build/7869878
[09:38] <popey> hah
[09:38] <ogra_> CaptainHeavy, wheee ! thanks !
[09:38] <CaptainHeavy> ogra_: no problem, thanks for building the app in the first place!
[09:38] <popey> everyone is running wily, surely! :)
[09:38] <ogra_> popey, probably they switched from ide to sata, try ubuntu-sdk-sata :P
[09:39] <davidcalle> wily + xenial overlay
[09:40] <popey> hah
[10:16] <bzoltan_> popey:  No, I put extra effort to support rare people who are on i386
[10:18] <bzoltan_> popey: and I assume that you are on wily. So the wily IDE package is being published right now ... so please wait for few ten minutes
[11:35] <nik90> bzoltan_: wow I didnt notice that Qtcreator we used was stuck at 3.1. Happy to read about the next-generation SDK. aquarius will be really happy to hear about this.
[11:39] <bzoltan_> nik90: aquarius: Yes, this forwarda and backward porting was limiting us a lot.  I hope that this solution will help.
[11:41] <aquarius> I properly am happy to hear about it
[11:41] <aquarius> being able to test phone apps on my 14.04 desktop will make my life a lot, lot easier :)
[11:43] <nik90> aquarius: so this 500 MB package will contain the entire Ubuntu Toolkit APIs, Qt Libraries necessary for app development. Would we be able to run it on the desktop to test it since from the blog post I read it provides the armhf 15.04 chroot.
[11:43] <nik90> bah...that was supposed to be addressed to bzoltan_ ^^
[11:44] <bzoltan_> nik90: aquarius: to avoid misunderstanding :) the latest SDK runtime will come later to the LTS ... the UITK is already sneaked in ... if you look around the /usr/ubuntu-sdk-ide
[11:46] <nik90> ah ok
[12:29] <aquarius> bzoltan_, how will I know when it's beyond testing and ready to be used? Will this stuff all end up in the normal ubuntu sdk ppa?
[12:32] <bzoltan_> aquarius:  yes, that is the plan. You will know if you follow the phone ML. Right now it is testing time...
[12:32] <bzoltan_> For example i am pushing an update right now as the first itteration was not installing perfectly in some case
[12:32] <aquarius> bzoltan_, cool. I have enough to do testing the apps I build without testing the infrastructure as well, but I'll be a happy user of it once it's stable :)
[12:33] <bzoltan_> aquarius:  I mean it is rock stable ... the IDE code is way much better then the one from the PPA
[12:34] <aquarius> ahem. "the first itteration was not installing perfectly in some case" and " it is rock stable" are directly contradictory ;)
[12:37] <aquarius> but it's cool, whatever happens -- really looking forward to being able to run apps on my lts desktop!
[12:38] <bzoltan_> aquarius: two different beast ... the IDE package is complete and stable. it is the API package what can act up ... but that is just the chroot, can be disposed or recreated manually
[13:24] <didrocks> kenvandine: hey! So, I'm using the ContentStore uri (I set the scope). This one isn't set before getting a transfer done (and the m_store being set)
[13:24] <didrocks> kenvandine: as I have a databinding setting the uri to another object, I'm getting: Accessing ContentStore uri with NULL internal store
[13:24] <didrocks> is there any way I can know if an internal store have been instantiated? (or even better, getting the .uri even before, as this just depends on the scope that is set, isn't it?)
[13:25] <kenvandine> i don't think uri should be able to be null
[13:25] <kenvandine> that should be set when instantiated
[13:25] <kenvandine> oh... you're binding to it
[13:26] <kenvandine> so the binding gets null before it's instantiated
[13:26] <didrocks> exactly!
[13:26] <kenvandine> i don't think there's anything you can do about that
[13:26] <kenvandine> it'll get set as soon as it's instantiated
[13:26] <kenvandine> it just makes noise in the logs :/
[13:26] <kenvandine> but that's a qml thing
[13:27] <kenvandine> if you find away around that, i'd love to hear it :)
[13:27] <didrocks> yeah, I was wondering how to reduce this
[13:27] <kenvandine> we have quite a few places in system-settings that suffers from this
[13:27] <didrocks> kenvandine: I don't understand conceptually why you need a transfer to be instantiated to get the uri, doesn't it just depends on the scope?
[13:27] <kenvandine> not the transfer
[13:27] <kenvandine> the ContentStore
[13:27] <kenvandine> has to be instantiated
[13:27] <didrocks> I have:
[13:27] <didrocks>     ContentStore {
[13:27] <didrocks>         id: appContentStore
[13:27] <didrocks>         scope: ContentScope.App
[13:27] <didrocks>     }
[13:28] <didrocks> appContentStore.uri returnts that warning
[13:28] <kenvandine> in the binding
[13:28] <didrocks> before I initiate a transfer with it
[13:28] <didrocks> yeah, but ContentStore is instantiated, isn't i?
[13:28] <didrocks> it*
[13:28] <kenvandine> because you are accessing it before it's instantiated
[13:28] <kenvandine> not necessarily at startup
[13:28] <kenvandine> it is
[13:28] <didrocks> oh
[13:28] <kenvandine> but briefly it isn't :)
[13:28] <didrocks> you think it's even before that
[13:28] <kenvandine> yeah
[13:28] <kenvandine> it happens a lot in qml
[13:29] <didrocks> and appContentStore isn't null, just not init()
[13:29] <kenvandine> right
[13:29] <didrocks> I think I got it
[13:29] <didrocks> ok, so in pure-qml I have some "ready" flags for this
[13:29] <kenvandine> so if you print appContentStore.uri in Component.onCompleted
[13:29] <kenvandine> you'll get it
[13:29] <didrocks> I doubt you want to implement that in c++ :p
[13:29] <didrocks> yep
[13:29] <didrocks> let me check
[13:30] <didrocks> hum
[13:30] <didrocks> doesn't seem to be the case
[13:30] <didrocks> I just added Component.onCompleted: console.log("uri now: " + uri)
[13:30] <kenvandine> not sure how that could be
[13:30] <didrocks> and the print is "uri now: "
[13:31] <kenvandine> hang on... phone ;)
[13:31] <didrocks> :)
[13:34] <kenvandine> didrocks, back
[13:34] <kenvandine> i'm still puzzled, the uri is set in the constructor
[13:34] <kenvandine> oh
[13:35] <kenvandine> console.log("uri now: " + appContentStore.uri)
[13:35] <kenvandine> uri isn't in the same scope as the page or whatever
[13:37] <didrocks> kenvandine: I'm on the onCompleted for that component
[13:37] <didrocks> let me add the id, but I doubt that will change
[13:38] <didrocks> yep, that didn't change, still blank
[13:38] <didrocks> I just have http://paste.ubuntu.com/12253258/
[13:38] <kenvandine> try doing it on your outer component
[13:38] <didrocks> the uri isn't set on component's completion (from the C++ code, you only set the uri on when it has a setStore())
[13:38] <kenvandine> page or whatever
[13:39] <didrocks> same on the page
[13:39] <kenvandine> that's on the transfer though
[13:39] <kenvandine> ok, let me check the source
[13:41] <kenvandine> didrocks, in cpp, the store requires a uri for the constructor
[13:41] <kenvandine>     Store(const QString& uri, QObject* parent = nullptr);
[13:41]  * kenvandine checks the qml bindings
[13:43] <kenvandine> weird, the qml bindings do something different
[13:43] <didrocks> in the opposite order, right? the store assign the uri
[13:44] <kenvandine> didrocks, well ContentStore qml binding doesn't actually set a cuc::Store internally until it's used in the transfer
[13:44] <kenvandine> Elleo, ^^ do you recall if that was intentional?
[13:45] <kenvandine> Elleo, or was that maybe left over from the first version of the bindings :)
[13:45] <kenvandine> when the store is set on the transfer in qml, then the internal store is set on the ContentStore
[13:45]  * kenvandine thinks that should happen in the constructor
[13:45] <didrocks> kenvandine: you get now why I was telling "empty until I set a transfer ;)"
[13:46] <kenvandine> didrocks, yeah, it doesn't make sense :)
[13:46] <didrocks> kenvandine: I'm sure you know are really eager to get a bug on this! :)
[13:46] <kenvandine> didrocks, i'm more familiar with the backend and cpp stuff :)
[13:46] <didrocks> (and at least, I understand why it didn't make sense to me to wait for a transfer to get the uri)
[13:46] <didrocks> that forced me in some interesting "workarounds"
[13:46] <kenvandine> yeah, the ContentStore api should be more useful
[13:47] <kenvandine> didrocks, please file a bug
[13:47]  * didrocks walks/jumps/runs to file one :)
[13:47] <didrocks> thanks for confirming kenvandine :)
[13:51] <Elleo> kenvandine: don't remember it being intentional, not sure much has changed in the ContentStore for quite a while though
[13:52] <kenvandine> Elleo, ok, i'm going to look at refactoring that a bit to ensure it's set in the constructor
[13:52] <didrocks> Elleo: kenvandine: bug #1491411 FYI
[13:53] <kenvandine> Elleo, i suspect that is leftover from the first iteration of the bindings
[13:53] <kenvandine> looks like gunther's code :)
[14:01] <kenvandine> Elleo, didrocks: i see why... it needs the ContentType of the transfer
[14:01] <kenvandine> so this is intentional
[14:01]  * kenvandine does want the ContentStore to be more generally useful
[14:02] <kenvandine> maybe we should add a contentType property to the ContentStore
[14:02] <kenvandine> didrocks, so basically not a bug, but could be made to be more generally useful for more than just transfers
[14:02] <Elleo> kenvandine: when you get a chance could you take a look at: https://code.launchpad.net/~michael-sheldon/content-hub/fix-initial-peer-list/+merge/269917 it allows us to avoid making an extra look up when creating a contentpeermodel, and fixes the browser incorrectly showing up in the contentpeerpicker for unknown types
[14:03] <kenvandine> Elleo, sure
[14:03]  * nemo pokes mcphail again
[14:03] <Elleo> kenvandine: I've added an "Undefined" type on the QML bindings to allow for the check, but I've only added it there and not also in the service, not sure if it's useful to add it everywhere or not
[14:08] <didrocks> kenvandine: yeah, that would be good, I'm still leaving it opened then
[14:08] <kenvandine> yeah
[14:08] <kenvandine> i'm commenting
[14:17] <Elleo> kenvandine: added a comment to that MR with info about the browser branch
[14:17] <kenvandine> thx
[14:20] <nik90> ahayzen: Hey , can you request QA to start testing music-app since it has all the necessary translations ready. Unless you guys were planning for additional fixes to land. While it waits in the QA queue, in parallel it will get further translations.
[14:23] <kenvandine> Elleo, how would you feel about adding that branch to silo 17?
[14:23] <kenvandine> it'll make it easier to test :)
[14:23] <kenvandine> the code looks good
[14:24] <kenvandine> but i haven't approved it yet
[14:25] <Elleo> kenvandine: sure thing
[14:25] <kenvandine> Elleo, cool, thanks!
[14:43] <kenvandine> Elleo, i see 17 is building, but without content-hub
[14:43] <kenvandine> i think you forgot to reconfigure it
[14:43] <Elleo> kenvandine: ah, will fix that now
[14:43] <Elleo> kenvandine: thanks for spotting it
[14:43] <kenvandine> np
[15:04] <Elleo> kenvandine: what do I need to do with the new system to get it to reconfigure? I'd thought just re-running assign would do it, but that doesn't seem to have worked
[15:30] <kenvandine> Elleo, that's all you need to do
[15:30] <kenvandine> Elleo, i'll look at it
[15:33] <kenvandine> Elleo, i assigned again and building, looks like it's going to build content-hub
[15:33] <kenvandine> had you specified the browser in the packages to rebuild before?
[15:34] <Elleo> kenvandine: I'd just selected the generic force rebuild option, rather than specifying anything individually
[15:34] <kenvandine> ah
[15:34] <kenvandine> i bet that meant rebuild existing packages
[15:34] <kenvandine> i didn't check anything
[15:34] <Elleo> ah
[15:34] <kenvandine> so it looks for changes to build
[15:34] <Elleo> okay, cool; will know for next time :)
[15:35] <kenvandine> you don't need to force when there are new revisions or new branches
[15:35] <kenvandine> it'll figure it out
[15:35] <Elleo> ah, okay
[17:08] <pmcgowan> popey, do you know if any progress was made on notifications for dekko mail
[17:08] <pmcgowan> or DanChapman,
[17:12] <ahayzen> nik90, yup, was just about to ping popey :-)
[17:57] <popey> pmcgowan: only updates from niklas updates, and some discussions with chipaca and rsalveti, no code
[17:59] <pmcgowan> popey, ok
[18:48] <mcphail> If anyone looks after http://unity.ubuntu.com/mir/ , can you fix it please? Hard to hack with Mir when the API docs are missing :) . Tempted to give up for the evening and pour a whisky instead
[18:57] <popey> mcphail: might be better off asking in #ubuntu-mir - kgunn specifically
[18:57] <mcphail> popey: kdub is helping there. Thanks


[20:41] <Unit193> Temp: 76 F (24 C) ~ Mostly Cloudy ~ Humidity: 58% ~ Alert: Severe Thunderstorm Warning ~ Observed: Tue 05, 15:52
[20:41] <Unit193> :D
[20:43] <yano> for where?
[20:43] <yano> you can do .wx-wg <location>
[20:43] <yano> .nws Crawford, OH
[20:43] <jenni> Severe Weather Statement issued May 05 at 4:35PM EDT until May 05 at 5:30PM EDT by NWS
[20:43] <jenni> Severe Thunderstorm !WARNING! issued May 05 at 4:34PM EDT until May 05 at 5:30PM EDT by NWS
[20:43] <jenni> Complete weather watches, warnings, and advisories for Crawford, OH, available here: http://alerts.weather.gov/cap/wwaatmget.php?x=OHC033&y=1' -- You may also PM the bot to get more details.
[20:43] <yano> aww, they had a Tornado Warning earlier
[20:43] <Unit193> /weather -cot  is easy too though.
[20:43] <Unit193> Yeah, saw several did.
[20:44]  * Unit193 is in ##weather(-us-oh) too.
[20:44] <yano> sweet
[20:45] <Unit193> Yeeep, I like it.  I get the weather in conky, but doesn't help if not looking.  I've yet to properly set up pings, but meh.
[22:10] <Unit193> Well if that was it, quite disappointing...


[05:20] <Unit193> If lm-sensors doesn't find anything and there is no /proc/acpi/thermal_zone, is acpi -t Thermal 0: ok, 59.5 degrees C correct?  It's been a little bit
[05:28] <BiosElement> Yeah, I still haven't gotten around to re-installing quassel on my server after I wiped it to setup a Minecraft server.
[05:36] <Unit193> Thoughts on going to OLF?
[05:36] <BiosElement> Already planning on it.
[05:42] <BiosElement-gOS> Well IRCCloud isn't bad either heh
[06:13] <BiosElement> exit
[06:13] <BiosElement> Bleh
[06:34] <BiosElement> And yay, weechat no longer looks horrid
[12:09] <BiosElement> Wow, Mozilla really doesn't know what they're doing anymore. They're now making thier own ChromeOS.
[13:49] <thafreak> BiosElement: what's wrong with mozilla competing in the chromeos arena?
[14:24] <jrgifford> Well, looks like we've got enough interest for a ReLoCo, just nobody to run it.
[14:25] <Cheri703> Whoever wants to hop up and take it, go for it
[14:25] <Cheri703> or have a few people that cycle through
[14:26] <Cheri703> it's really pretty darn informal, at least mansfield's is
[14:27] <Cheri703> and honestly "running it" is...not terribly time consuming, perhaps I should put more time into ours (probably should), but...it doesn't take much effort
[14:27] <jrgifford> Sweet.
[14:28] <Cheri703> (I'm going to be in and out for about the next 30 min and then gone for 45, but type stuff and I'll respond when I can :) )
[14:29] <jrgifford> (OK. :) )
[14:29] <jrgifford> So what kind of things do you do at a meeting? I've never been to one. :P
[14:42] <Cheri703> we just kind of hang out, talk computers or other things that are interesting, and help out if someone is having difficulty with something. Or have someone talk (very informally) about a new thing they've been working on. ours are more social than structured
[14:42] <Cheri703> scooter2: hola!
[14:50] <jrgifford> Awesome.
[14:51] <scooter2> Cheri703: Hi!
[14:52] <Cheri703> how have you been?
[14:52] <scooter2> Pretty well, how about you?
[14:55] <Cheri703> doing alright, CRAZY busy this week
[14:55] <Cheri703> actually have to leave in about 5 minutes, but will be back on in about an hour
[14:55] <Cheri703> scooter2: do you ever make it over to ubuntu-women?
[14:55] <Cheri703> well #ubuntu-women
[15:03] <scooter2> Oh no! I didn't get back in time (my cat was doing cute things). I hope you're week gets better!
[15:05] <scooter2> I have #ubuntu-women open, but I never have really interacted with the group.
[15:53] <Cheri703> scooter2: you should :) it's a great group
[15:54] <scooter2> Cheri703: Cool! I'll check out their website.
[16:21] <paultag> hello, world!
[16:21] <paultag> How goes, me'friends?
[16:25] <Cheri703> hola paultag
[16:26] <paultag> Cheri703: howdy :)
[16:26] <paultag> How's life in the big O-H ?
[16:26] <Cheri703> how's bawstin?
[16:26] <Cheri703> it's going alright
[16:26] <paultag> Cheri703: sickkkkk. As usual. Loving loive ATM
[16:26] <paultag> life *
[16:26] <Cheri703> good good :)
[16:27] <paultag> Cheri703: I could use a nap, though :)
[16:27] <Cheri703> my husband got a job (FINALLY) and is enjoying it, AND after just under a week, has probably moved to a position that will pay $5 more /hour
[16:27] <Cheri703> I know the feeling
[16:30] <paultag> Cheri703: wooo :) congrats :)
[16:31] <Cheri703> not 100% positive he'll get a raise right away, but it's probable :)
[16:32] <paultag> Cheri703: :D
[16:33] <Cheri703> yeah, it's wonderful, especially since this week would have been his LAST unemployment payment unless he got another extension (almost a year of being unemployed)
[20:53] <Unit193> We got our pizza back!
[20:56] <cosmicpizza> hi there howdy ?
[20:57] <Unit193> Howdy!
[20:57] <Unit193> Welcome to the Ubuntu Ohio LoCo!
[20:57] <cosmicpizza> thanks
[20:58] <cosmicpizza> what means loco ?
[20:59] <Unit193> Local Community
[21:00] <cosmicpizza> ok
[21:42] <paultag> wanadoo.fr -- initeresting
[21:42] <paultag> cosmicpizza: are you french or using a proxy? :)
[21:50]  * BiosElement waves
[22:21] <canthus13> crazy.


[19:08] <Letozaf_> balloons, hey :)
[19:10] <balloons> Letozaf_, howdy!
[19:11] <Letozaf_> balloons, how are you ?
[19:11] <Letozaf_> balloons, If you got time I got a mp
[19:11] <balloons> Letozaf_, of course! Link me
[19:12] <Letozaf_> balloons, https://code.launchpad.net/~carla-sella/ubuntu-calendar-app/calendar-management-tests/+merge/256202
[19:23] <balloons> Letozaf_, commented
[19:23] <Letozaf_> balloons, ok let me take a look thanks


[11:43] <tony-smlr> SMLR Live going live soon Video: http://youtu.be/ZV2NZX9I1mY Audio: http://live.smlr.us:8000/streaming
[13:41] <cmaloney> apparently dnf is replacing yum
[13:42] <cmaloney> further proving that programmers don't know how to name things


[03:36] <darkxst> infinity, the i386 is stuck  for some reason
[03:36] <darkxst> (ubuntu GNOME build)
[03:36] <infinity> darkxst: It's being sorted.
[03:37] <darkxst> infinity, k, thanks
[03:38] <infinity> darkxst: There's just two fresh builds going, so the amd64 one from two hours ago will invalidate.  Didn't notice that one, sorry.
[03:39] <darkxst> doesnt matter, not like anyone started testing it
[03:40] <infinity> darkxst: Right, these builds will actually show on the milestone now, I fixed that.  So, should be good to go in ~30m or whatever.
[03:44] <darkxst> hopefully its not to broken!
[04:04] <darkxst> infinity, can you increase the size limits on images, to get rid of the oversized messages? we have a nominal 1.5GB limit now
[04:07] <darkxst> atleast that is what our teams decided, clearly the servers don't know this yet!
[07:41] <flexiondotorg> infinity, Awake or sleeping?
[07:55] <flexiondotorg> didrocks, Can you do me a favour? Please can you update the ubuntu-mate-meta package?
[07:56] <didrocks> flexiondotorg: sure, doing that
[07:56] <didrocks> flexiondotorg: you pushed your changes to your seed?
[07:56] <flexiondotorg> I've got a couple of packages missing.
[07:56] <flexiondotorg> I have pushed seed changes.
[07:56] <flexiondotorg> didrocks, Thanks.
[07:56] <didrocks> flexiondotorg: yw, running the update :)
[07:56] <flexiondotorg> 3 new packages should turn up.
[07:56] <flexiondotorg> Cheers.
[07:56] <didrocks> I'll send you the diff
[07:57] <doko> Riddell, looks like a lot of my fixes for kde stuff were overridden again, and gcc-5 hangs again for kde issues :-/
[07:58] <flexiondotorg> Laney, unblock ubuntu-mate-meta/1.131
[08:09] <Laney> ok
[08:23] <didrocks> flexiondotorg: looking good to you? http://paste.ubuntu.com/12197794/ (got 4 new packages, not 3)
[08:23]  * flexiondotorg checks...
[08:25] <flexiondotorg> didrocks, Yes, that's exactly what I expected to see. Thank you.
[08:25] <didrocks> flexiondotorg: yw! uploading
[08:25] <didrocks> (done)
[08:26] <flexiondotorg> didrocks, Cheers. I've spent weeks negotiating with Debian Legal about the MATE documentation. More weeks adding it all in. Then forget to include the damn package in the seeds ;-)
[08:27] <didrocks> ahah ;)
[10:44] <sil2100> Hello release team! I would need to disable the importer for a short while
[11:02] <flexiondotorg> Laney, ^^^^^^^
[11:02] <Laney> yes?
[11:05] <flexiondotorg> Does the request from sil2100 mean anything to you?
[11:06] <sil2100> I'll reenable it in a moment, just the image copies take ages
[11:06] <sil2100> Delta creation is slow
[11:07] <sil2100> Laney: I can actually leave the importer running if you want, just my copy-image calls might block if from time to time
[11:07] <Laney> I don't think it affects me, do what you want :)
[11:08] <sil2100> Ok, thanks :) In case you guys need to re-spin some flavor images, I can enable the importer then if needed
[11:08] <sil2100> Since I usually disable it as otherwise it can block my copy-image from happening if it starts running
[11:16] <infinity> sil2100: The importer has no relation to flavour images (or anything other than system-image).
[11:19] <sil2100> Ah, right, ubuntu-core/ubuntu-personal are not affected by this, nvm then ;)
[11:19] <sil2100> infinity: btw. did you get my pokes with questions about britney?
[11:20] <infinity> sil2100: I did, I need to respond soon.  Sorry, was out all last week.
[11:20] <sil2100> infinity: no worries, just hope you got some sleep yesterday at least
[11:22] <infinity> sil2100: Sort of. :/
[11:26] <ogra_> flexiondotorg, importer means phones, snappy and the ubuntu-pocket-desktop that use system-image ... we developed  habit of announcing here when we disable it so in case i forget to switch it on again someone can poke me about it ... there is no other easy way to let others that depend on it know why or who disabled it
[11:27] <flexiondotorg> ogra_, Thanks for explaining :-)
[11:29] <infinity> ogra_: One could, I dunno, leave their name in a comment when they comment it out. ;)
[11:29] <ogra_> details :P
[11:31] <ogra_> infinity, if sil2100 announces it in advance i can intercept if i'm just waiting for an important snappy import ;)
[11:31] <ogra_> (not that i would though ...)
[11:31] <ogra_> (waiting i mean)
[11:31] <infinity> (At this point, I think you're just talking to yourself)
[11:32] <ogra_> haha
[11:32] <sil2100> ;)
[11:33] <infinity> I need to pick a new timezone for the week, mine's not working out.
[11:33] <infinity> Anyone have anything good to say about theirs?
[11:34] <ogra_> it is sunny and warm in mine
[11:34] <infinity> Beats smokey and warm in mine.
[11:34] <infinity> s/warm/hot/
[11:35] <infinity> It seems every tree in a 200km radius is committing suicide, with no regard whatsoever to my need to breathe.
[11:35] <infinity> s/to my/for my/ ... I need coffee.  Or sleep.  *flips coin*
[11:36] <Shinikake> EST is pretty nice this time of day.
[11:36]  * Shinikake sips a Brazilian blend.
[11:37] <ogra_> infinity, decaf *and* sleep ?
[11:37] <infinity> ogra_: I don't understand that first word.
[11:37] <ogra_> lol
[11:37] <infinity> ogra_: Silly German.
[11:39] <infinity> I guess it'll be a coffee and glibc rebase sort of morning.
[11:39] <infinity> No one wants me actually awake when I do that.
[11:40] <infinity> ogra_: Are you still of the opinion that no one in the phone world cares about wily (other than if we completely break it, of course)?
[11:40] <ogra_> infinity, i am ... but then i'm a snappy dude now :)
[11:41] <infinity> ogra_: ie, should I give them N days to play with glibc 2.22 and report back to me, or just trust the desktop/server/autopkgtest QA is good enough?
[11:41] <ogra_> wily wont end up on any phones ... and gcc5 breaks all store apps
[11:41] <infinity> Righto.  Then I'm inclined to not give them control over my QA. :P
[11:41] <ogra_> but people landing stuff in wily like to at least test on a semi working image ...
[11:42] <ogra_> so breaking it completelly might cause an outcry
[11:42] <ogra_> -l
[11:42] <infinity> ogra_: I have no intention of *breaking* glibc, I just don't want a repeat of when I landed 2.21 with, literally, one bug anyone cared about, and it spawned more meetings and specs than UDS.
[11:43] <ogra_> yeah, no worries ... phones are and stay vivid based
 Riddell: looks like it's much more than modemmanager: all of dbus looks messed up
[11:43] <Riddell> no upgrades I guess for beta 1 ^^
[11:43] <ogra_> Riddell, didnt it always ?
[11:44] <Riddell> ogra_: always mess up?
[11:44] <ogra_> dbus looking mssed up :)
[11:44] <ogra_> +e
[11:47] <flexiondotorg> Mirv any chance you can help me out?
[11:47] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/1488930
[11:47] <flexiondotorg> Laney, unblock ubuntu-mate-settings/15.10.1
[11:50] <Laney> flexiondotorg: anyone on the team can do these, you don't need to ask me directly
[11:51] <Laney> but done
[13:25] <flexiondotorg> Laney, any chance you could sponsor a couple of uploads for me?
[13:55] <Laney> infinity: slangasek: stgraber: anyone: Any of you able to do the B1 publishing tomorrow in my stead?
[13:55] <Laney> I'll be at BF & probably not available
[13:56] <Laney> (but if I am then I'll let you know)
[14:06] <flexiondotorg> Laney, I am going to be unavailable from 13:30 till 15:00 tomorrow. Hopefully that won't impact my chasing.
[14:07] <flexiondotorg> Riddell, any chance you could sponsor a couple of packages for me please?
[14:09] <Riddell> flexiondotorg: in a bit, I'm in a meeting now
[14:10] <flexiondotorg> Riddell, Thanks. When you're free please take a look at:
[14:10] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-settings/+bug/1488930
[14:10] <flexiondotorg> https://bugs.launchpad.net/ubuntu/+source/ubuntu-mate-welcome/+bug/1488968
[15:11] <stokachu> infinity:just confirming you saw the openstack package upload?
[16:06] <coreycb> hello, can an archive admin please promote python-pymysql to main? this will help get some of our openstack packages out of dependency waits.
[16:11] <cjwatson> coreycb: I'll take care of it, and a few others I see in the queue
[16:11] <coreycb> cjwatson, thanks
[16:26] <cjwatson> coreycb: all done
[16:27] <coreycb> cjwatson, thanks, appreciate it
[17:47] <infinity> Laney: If all the paperwork is covered and I have to do nothing but pull the trigger, I'm down.  I don't have the time to crack any whips.
[18:40] <sil2100> Dear release team! The importer is now re-enabled and the daily-builds of rc-proposed (vivid touch) as well
[18:40] <sil2100> (just a heads up)
[18:46] <flexiondotorg> infinity, Please can you unblock ubuntu-mate-welcome/1.0.3
[19:23] <flexiondotorg> unblock ubuntu-mate-welcome/1.0.3
[19:23] <flexiondotorg> unblock mate-netbook/1.10.0-1
[19:24] <flexiondotorg> unblock eom/1.10.3-1
[19:24] <coreycb> hi, can an archive admin please promote python-taskflow and python-oslo.db to main?  that'll fix some of our openstack dependency waits.  also we have an FFE ( bug 1489096 ) for python-troveclient that is also needed to fix some openstack packages that are ftbfs.
[19:25] <infinity> flexiondotorg: Done * 3.
[19:25] <flexiondotorg> infinity, Thanks very much :-)
[19:26] <cyphermox> flexiondotorg: some of that wasn't built yet ;)
[19:27] <flexiondotorg> cyphermox, I learned yesterday that that doesn't matter :-)
[19:27] <infinity> coreycb: We can never sync that package from Debian unless Debian bumps the epoch in the version (which you could ask them nicely to do).
[19:27] <coreycb> infinity, I was wondering.. ok
[19:27] <cyphermox> flexiondotorg: well, it's just that sometimes things don't build :)
[19:27] <infinity> coreycb: Versions can't go back in time. :P
[19:27] <coreycb> infinity, yeah, I'll cancel it and update our package
[19:28] <infinity> coreycb: However, if you find that a merge ends up identical in every way except the version number, please do ask the Debian maintainer to add the epoch to paper over our oops.  If you ask nicely, I'm sure he won't mind.
[19:29] <coreycb> infinity, maybe that's an option.  I'll check with zigo.  thanks.
[19:30] <infinity> coreycb: Bleh.  There's exactly zero mention in the changelog as to WHY we even added the epoch.  Oh well.
[19:30] <infinity> coreycb: Our packaging seems quite different, but it would be nice for that to not be true.
[19:31] <coreycb> infinity, I've compared our package with debian's and it's ok to sync, assuming the version issue is settled
[19:32] <coreycb> infinity, yeah I think it was just a mistake
[19:37] <cjwatson> Initial release with an epoch *blink*
[19:37] <cjwatson> Probably should have been caught in NEW review.
[19:54] <infinity> cjwatson: It may have been a case of "our users have this installed already due to $random_ppa, and we want to support upgrades", but I don't think I'm the one who reviewed it.
[19:54] <infinity> (And if it was me, I don't remember. :P)
[22:18] <flexiondotorg> infinity, I see ubuntu-mate-settings failed to build while trying to parse the time?
[22:18] <flexiondotorg> infinity, Can you shed any light on this for me?
[22:20] <infinity> flexiondotorg: Huh.  Can't say I've ever seen that failure mode before. :P
[22:21] <flexiondotorg> infinity, dpkg-genchanges -S -sa works fine here.
[22:21] <infinity> flexiondotorg: I've retried it to see if it was some weird cosmic ray thing.
[22:21] <flexiondotorg> infinity, Thanks.
[22:21] <flexiondotorg> infinity, Just out of interest, what "time" is it parsing?
[22:22] <infinity> flexiondotorg: Dunno, you'd have to follow the code.
[22:24]  * flexiondotorg is suddenly very tired and thinks it might be time for bed ;-)
[22:26] <infinity> flexiondotorg: Huh, no, it really does hate you.
[22:26]  * infinity grabs the source.
[22:26]  * flexiondotorg is curious.
[22:27] <flexiondotorg> cyphermox, Sponsored that upload and encountered the same issue initially. But used a different machine to do the build in the end.
[22:27] <infinity> Err, that's not a good sign. :P
[22:28] <infinity> And, indeed, same thing here.
[22:29] <cyphermox> it's the changelog timestamp from the previous upload
[22:29] <flexiondotorg> OK.
[22:30] <infinity> dpkg-genchanges has no business parsing old entries..
[22:30] <infinity> Though, I don't see anything wrong with that one either.
[22:30] <cyphermox> *shrugs*  if I kept just the latest it was happy
[22:30] <flexiondotorg> debuild -S works on the machine I have access to.
[22:31] <flexiondotorg> The previous change log time stamp have July rather Jul and June rather than Jun.
[22:31] <infinity> flexiondotorg: Yuo're not using the latest dpkg, I assume.
[22:31] <flexiondotorg> Could that be the issue.
[22:31] <flexiondotorg> infinity, I'm on 15.04.
[22:31] <infinity> Oh, could be, yes.
[22:31] <flexiondotorg> This machine at least.
[22:31]  * infinity hacks a bit.
[22:31] <flexiondotorg> infinity, Thanks.
[22:37] <infinity> Okay, it's fixed in git.  Lemme rev dpkg and retry your build.
[22:38] <flexiondotorg> infinity, Many thanks.
[22:38] <infinity> flexiondotorg: You'll probably want to go and correct history sometime, but the new dpkg will actually tell you which lines are broken, making that easier.
[22:39] <infinity> flexiondotorg: Like so: http://paste.ubuntu.com/12202661/
[22:40] <flexiondotorg> infinity, Thanks.
[22:41]  * flexiondotorg is a bit puzzled why lintian is not spitting out errors when dpkg is clearly upset.
[22:42] <infinity> Oh, embarrassing, it trips on some of my lines in the dpkg changelog. :P
[22:42] <infinity> flexiondotorg: dpkg very recently switched to a newer/stricted timedate parsing module to drop a dependency (the new one is from perl itself, not a module).
[22:43] <infinity> flexiondotorg: Like many such things that Just Worked for ten years, changing it has been entertaining.
[22:43] <flexiondotorg> :-D
[22:43] <flexiondotorg> infinity, Any chance you could sponsor a sync for me?
[22:44] <flexiondotorg> https://bugs.launchpad.net/bugs/1489185
[22:44] <infinity> Hrm.  Not convinced the new implementation is quite sane yet either.
[22:44] <flexiondotorg> I have a howling bug in mate-tweak 3.5.1
[22:44] <flexiondotorg> So I had 3.5.2 uploaded to Debian unstable earlier.
[23:03] <flexiondotorg> infinity, I realise you're busy but if you can find the time to sponsor the following syncs I'd be most grateful.
[23:04] <flexiondotorg> infinity, Both fix signifcant issues I'd really prefer to not be in 15.10 Beta 1 tomorrow.
[23:04] <flexiondotorg> mate-tweak      https://bugs.launchpad.net/bugs/1489185
[23:04] <flexiondotorg> caja-extensions https://bugs.launchpad.net/bugs/1489186
[23:05] <infinity> flexiondotorg: Hold on, I'm still fixing dpkg.  The rabbit hole went deeper. :P
[23:05] <flexiondotorg> infinity, Oh. Sorry to hear that.
[23:14] <sil2100> flexiondotorg: I could sponsor those, but it's already a bit late here, not sure if I wouldn't fall asleep before doing that
[23:15] <flexiondotorg> sil2100, If you're able to stave off sleep I'd really appreciate.
[23:15] <flexiondotorg> sil2100, I'd like to respin the isos first thing so I can run through the tests.
[23:15] <flexiondotorg> sil2100, Where are you?
[23:16] <sil2100> flexiondotorg: let me see what I can do here, maybe I can pick it up before infinity has time - since those are universe packages
[23:16] <sil2100> Poland, EU
[23:16] <flexiondotorg> sil2100, England.
[23:16] <flexiondotorg> So, yes. Past your bed time ;-)
[23:20] <sil2100> flexiondotorg: did you check if the mate-tweak builds correctly on wily? Do you have any build-logs handy?
[23:21] <flexiondotorg> sil2100, One sec...
[23:22]  * sil2100 wonders if this requires a FFe
[23:22] <flexiondotorg> https://launchpadlibrarian.net/215553291/buildlog_ubuntu-wily-amd64.mate-tweak_3.5.2-1~wily1.1_BUILDING.txt.gz
[23:22] <sil2100> In theory new upstream versions should, but on the other hand it has only bugfixes it seems?
[23:22] <flexiondotorg> sil2100, The is no new features.
[23:22] <flexiondotorg> It is just fixes.
[23:23] <sil2100> flexiondotorg: thanks for the log, looks good
[23:24] <flexiondotorg> sil2100, You're welcome.
[23:24] <sil2100> Will just double-check something and I'll sponsor it, one moment
[23:30] <sil2100> Ok, sync request submitted, it's in wily-proposed
[23:30] <sil2100> Now let me take a look at caja-extensions and what's up with that one...
[23:31] <flexiondotorg> sil2100, https://launchpadlibrarian.net/213463416/buildlog_ubuntu-wily-amd64.caja-extensions_1.10.0-1~wily1_BUILDING.txt.gz
[23:32] <sil2100> flexiondotorg: do you have a build-log for caja-extensions maybe? And maybe a list of changes introduced in this release? Since the changelog only mentions 'new upstream release' basically
[23:32] <flexiondotorg> sil2100, The issue here is that Caja (the MATE file manager) is already at version 1.10
[23:32] <flexiondotorg> sil2100, See up a couple of comment for build log.
[23:32] <sil2100> Thanks :)
[23:33] <flexiondotorg> sil2100, caja-extensions in the 15.10 are 1.8. So there are some significant regressions.
[23:33] <flexiondotorg> sil2100, See my comment in the sync request where I dicussed this (and other MATE 1.10 sync) with several devs.
[23:33] <sil2100> hm, indeed, and you mentioned that didrocks and Laney agreed on this sync, yes?
[23:33] <flexiondotorg> sil2100, Ultimately, Laney ack'd it.
[23:34] <flexiondotorg> sil2100, Yes, it was discussed with those in my comment.
[23:35] <flexiondotorg> sil2100, Here is a transcript - http://paste.ubuntu.com/12201355/
[23:39] <sil2100> flexiondotorg: yeah, I see the discussion, it seems to be fine - caja-extensions anyway is only seeded in ubuntu-mate
[23:39] <flexiondotorg> sil2100, Yep.
[23:39] <sil2100> Let me just do a final check and do iiit
[23:39] <flexiondotorg> Sure. Thanks for help me out.
[23:42] <flexiondotorg> unblock mate-tweak/3.5.2-1
[23:43] <sil2100> flexiondotorg: what worries me a bit with caja-extensions is that it failed to build for armhf in the PPA
[23:44] <flexiondotorg> sil2100, All the armhf stuff has failed in my PPAs for months.
[23:44] <flexiondotorg> But always builds "for real".
[23:44] <flexiondotorg> I think something is not setup quite right in my PPAs.
[23:45] <flexiondotorg> https://launchpad.net/~ubuntu-mate-dev/+archive/ubuntu/crazy-mate/+packages
[23:45] <sil2100> Indeed I see there's something strange going on, ok, let's sync it - if it fails building in -proposed then we'll know
[23:45] <flexiondotorg> You can see there all the armhf fails in the PPA. But those that have made it to the archive all built correctly.
[23:45] <sil2100> But then we wouldn't be able to sync it anyway, not without patching, so +1 from me
[23:46] <sil2100> Yeah, just checked a few of those
[23:47] <sil2100> flexiondotorg: ok, both packages now in -proposed, there's not much more I can do now
[23:47] <sil2100> :)
[23:47] <flexiondotorg> sil2100, Many thanks!
[23:48] <sil2100> yw!
[23:48] <flexiondotorg> unblock caja-extensions/1.10.0-1
[23:53] <infinity> flexiondotorg: Alright, once the dpkg testsuite passes here, I'll upload this hideous hack.
[23:55]  * infinity feels icky.
[23:58] <flexiondotorg> infinity, Go you :-)


[16:48] <pleia2> mhall119: care to do a Unity presentation for User Days on the 14th?
[16:48] <pleia2> could be intro to Unity, or using lenses, or whatever you want
[17:05] <nigelb> OMG AlanBell
[17:05] <nigelb> CONGRATS!
[17:08]  * pleia2 hugs nigelb
[17:09]  * nigelb hugs pleia2 :)
[17:10] <mhall119> pleia2: I'd be happy to, but I'm not exactly an expert.  Have you asked any of the develoeprs?
[17:12] <pleia2> mhall119: no, I don't know many of them
[17:12] <pleia2> we just need someone :)
[17:12] <pleia2> preferably for a couple of sessions covering different things
[17:13] <mhall119> pleia2: if you put a call for presenters on G+, I'll share it
[17:13] <mhall119> if you can't find someone, though, I'll be happy to do a session from a user's perspective
[17:17] <pleia2> mhall119: https://plus.google.com/u/1/114018915395046539523/posts/2gqZuZuZfJi
[17:19] <pleia2> thank you :)
[17:19] <mhall119> nop
[17:19] <mhall119> pleia2: have you asked davidcalle to do something about Lenses?
[17:19] <pleia2> nope
[17:20] <mhall119> I'll see if I can't track him down and ask
[17:20] <pleia2> thank you :)
[17:20] <mhall119> :)
[17:29] <AlanBell> thanks pleia2
[17:31] <pleia2> AlanBell: sure, should join #ubuntu-ops! :)
[20:15] <maco> hey loco council type peoples: are free cds the difference between approved and expired teams?
[20:22] <pleia2> there are also some other benefits, sometimes jono or someone will post about publishers who will send books to approved teams, there was an approved team gift a while back, conference packs are smaller for teams who are not approved
[20:23] <maco> but its all about the swag, the mailing lists and hosting wont disappear, right?
[20:23] <pleia2> everyone gets a mailing list, canonical hosting is soft of a fuzzy area (I don't love the idea that it would be revoked, that causes problems)
[20:24] <pleia2> nothing happens immediately when you expire though, has the loco council been in contact about a reapproval? and do you intend to go for it?
[20:25] <maco> thanks
[20:25] <pleia2> if you intend to they can just extend you until the review meeting
[20:25] <maco> the loco council apparently filed a bug report that we needed to get reapproved months and months ago but nobody knew about it
[20:25] <pleia2> doh :( it would have been sent to the team contact
[20:26] <maco> so our contact got an email that we're gonna expire last week, and he has talked to laura, and they're gonna extend so we can do the application, but tbh i was surprised we got reapproved last time
[20:26] <maco> (also im surprised two years has passed since then)
[20:27] <pleia2> gotcha
[20:28] <maco> some on the team were afraid it means the team, mailing list, everything disappears and so i was telling them nahh, we just dont get free swag anymore
[20:29] <maco> user support on the mailing list wouldnt stop


[13:04] <thomi> morning
[19:17] <ibeardslee> morning
[19:43] <snail> morning
[19:47] <olly> morning
[20:07] <chilts> morning
[20:21] <ajmitch> morning
[21:35] <mwhudson> morning
[21:44] <hads> morning
[21:45] <hads> Someone posted this on Tweeter this morning; http://www.pythonapi.com/
[21:46] <chilts> interesting idea, I should do one for Node.js
[22:03] <snail> hads: the problem with that is that it's a short list, really it either needs a "long list" of APIs to second tier services, or a row of "search 'API python' on github" "search 'API python' on google code" ...
[22:04] <chilts> and also, I guess there are many libs and that shows only one for each service
[22:05] <olly> TMTOWTDI
[22:16] <chilts> speaking of which, I can't make PerlMongers tonight :(
[22:47] <thumper> morning
[23:34] <mwhudson> thumper: did you really get married the day before your birthday?
[23:34] <thumper> yes
[23:34] <thumper> and two days before Rachel's
[23:34] <thumper> so we go, 9, 10, 11 Sept
[23:35] <mwhudson> hah
[23:35] <mwhudson> very well organized
[23:36] <lifeless> thumper: LOL brilliant
[23:36] <mwhudson> thumper: should have aimed to have kid no 1 on 12 i guess?
[23:36] <thumper> mwhudson: kid no 1 was not planned
[23:36] <thumper> so that went out the window
[23:38] <snail> thumper: adopt kid #1 from yourselves, so you can pick a new 'birthday' ...
[23:38] <thumper> haha
[23:39] <thumper> kinda like not having kid birthdays around ours
[23:39] <thumper> they are jan/feb/jun
[23:40] <snail> there were people in our antenatal class who were aiming for a particular day. turns out that it's not the kind of projectile you have control over...
[23:42] <olly> an incontinental missile?


[05:58] <hyperair> sb levelclear -level clientcrap,crap,joins,parts,quits,nicks,clientnotice
[06:02] <nigelb> hyperair: did you forget a / ;)
[08:34] <hyperair> nigelb: yeah i did =((
[08:34] <hyperair> nigelb: i did /foreach window, so every channel got it >_<
[15:31] <skaet> reminder SRU/LTS meeting will start in 1/2 hour.
[15:56]  * marjo waves to skaet
[15:57] <marjo> hi pedro_
[15:57] <pedro_> hola hola
[15:58] <hggdh> oi oi
[15:59] <sconklin> \o/
[16:00] <skaet> hi all
[16:00] <skaet> #startmeeting
[16:00] <MootBot> Meeting started at 10:00. The chair is skaet.
[16:01] <skaet> SRU/LTS bi-weekly synch meeting.
[16:01] <skaet> Reminder, please follow the convention  of using ".." on a separate line when you've finished typing.    Also, If someone wants to comment on the last point, please "o/", so we know to wait.
[16:01] <skaet> .
[16:01] <skaet> [TOPIC] End of Life - Karmic, Hardy-Desktop
[16:01] <skaet> Just a reminder that April 2011 will see end of life of Karmic Koala (9.10), and Hardy Heron (8.04) Desktop.
[16:01] <skaet> Note will be going out this week, for the one month warning.
[16:01] <skaet> .
[16:01] <skaet> Dapper Drake (6.06) Server will end of life in June 2011.
[16:01] <MootBot> New Topic:  End of Life - Karmic, Hardy-Desktop
[16:01] <skaet> [LINK] https://wiki.ubuntu.com/Releases
[16:01] <MootBot> LINK received:  https://wiki.ubuntu.com/Releases
[16:01] <skaet> .
[16:01] <skaet> Any concerns or issues to flag with the approaching EOL?
[16:01] <skaet> ..
[16:02] <skaet> [TOPIC] Kernel SRU status - sconklin, bjf
[16:02] <MootBot> New Topic:  Kernel SRU status - sconklin, bjf
[16:02] <sconklin> In order to sync the kernel cadence schedule back up
[16:02] <sconklin> with the master interlock schedule, I've proposed
[16:02] <sconklin> that we take the kernels which have been in
[16:02] <sconklin> |
[16:02] <sconklin> The end result of this is that any changes to kernels which were
[16:02] <sconklin> approved after week before last will not show up in -proposed until April 29th
[16:02] <sconklin> ..
[16:02] <sconklin> did that all make it?
[16:02] <bjf> no
[16:02] <ara> no :(
[16:02] <marjo> sconklin: no
[16:03] <sconklin> ok, here goes again
[16:03] <sconklin> In order to sync the kernel cadence schedule back up
[16:03] <sconklin> with the master interlock schedule, I've proposed
[16:03] <sconklin> that we take the kernels which have been in
[16:03] <sconklin> -proposed for a week and just treat them as
[16:03] <sconklin> if they were uploaded last Friday.
[16:03] <sconklin> |
[16:03] <sconklin> This is effectively just putting the kernel cadence on hold for a week.
[16:03] <sconklin> |
[16:03] <sconklin> The end result of this is that any changes to kernels which were
[16:03] <sconklin> approved after week before last will not show up in -proposed until April 29th
[16:03] <sconklin> (five weeks from now), and will not be released until May 19th (almost
[16:03] <sconklin> eight weeks from now).
[16:03] <sconklin> ..
[16:03] <ara> o/
[16:04] <skaet> go ara
[16:04] <ara> I agree with the resync
[16:04] <ara> but I would like to keep the Maverick cadence if possible
[16:05] <ara> there are a lot of fixes the the HWE team needs to release
[16:05] <ara> and 8 weeks is too long time for them to wait
[16:06] <ara> so my proposal would be
[16:06] <sconklin> o/
[16:06] <ara> * Resync with QA schedule. This is, keeping this kernel two more weeks
[16:06] <ara> in -proposed, so QA can test it next week.
[16:06] <ara> * Keep the cadence for Maverick (uploading new ones April 8th, April 22nd)
[16:06] <ara> * Start again with the 2 week cadence after UDS (uploading kernels for
[16:06] <ara> all the releases on May 20th)
[16:06] <ara> ..
[16:06] <skaet> sconklin go
[16:07] <marjo> ara: that would work well for QA, allows us to concentrate on beta-1 this week
[16:08] <skaet> marjo,  what would be one with the April 8th kernels?   does the QA team have bandwidth to test them along with the final Natty testing?
[16:08] <sconklin> ara, that's fine with the stable kernel team. I think we can meet that, and it would serve some needs that are pretty critical. In general if we're going to split out some series for a different schedule, I;d like to have a good display of what those schedules are, but that's a different problem
[16:08] <bjf> o/
[16:09] <skaet> bjf, let ara respond and then you go.
[16:09] <ara> skaet, kernels for April 8th and 22nd would only be for Maverick
[16:10] <ara> skaet, so, if QA could test those, that would help a lot the HWE team
[16:10] <sconklin> .. (forgot)
[16:10] <ara> ..
[16:10] <bjf> does that mean the current cycle started last Thursday ? it's kind of confusing to start cycles mid week.
[16:10] <bjf> ..
[16:11] <marjo> skaet, ara: the problem w/ kernels for April 8 is conflict w/ testing for beta-2 week of April 11
[16:11] <skaet> ara, yes,   April 22 should probably work out ok  (QA testing first week of May),  but I'm a bit concerned about April 8th proposal.
[16:11] <skaet> heh
[16:11] <ara> marjo, I understand, but if they uploda the kernel on Friday, you guys have Friday, Monday and Tuesday for Maverick kernel
[16:12] <marjo> and week of april 25 is final release testing
[16:12] <ara> marjo, it is very unlikely that the Beta testing start before Tuesday
[16:12] <marjo> ara: sure, very risky imho
[16:12] <skaet> ara,  uploaded kernels are tested by week after by QA  (validation week first)
[16:13]  * JackyAlcine will be right back.
[16:13] <ara> skaet, sorry?
[16:13] <skaet> s/validation/verification
[16:13]  * skaet sorry
[16:14] <ara> skaet, then it is perfect, it is the week in between :)
[16:14] <skaet> ara,  not quite,  we've got holidays that week, and last updates.
[16:15] <ara> skaet, but, why don't we try?
[16:15] <ara> skaet, the only thing that can go wrong is that finally we don't have time for the SRU, and it does not get uploaded (as per the kernel team policy)
[16:15] <bjf> ara, +1
[16:16] <skaet> ara,  I'm just worrying about the QA team's bandwidth.
[16:16] <skaet> for the month of april.
[16:16] <marjo> skaet: thx; see above comments
[16:16] <skaet> we'll be doing one cycle already this month,  and then one in early may.
[16:17] <skaet> what is the pressure for the fixes to motivate the risk to Natty?
[16:17] <skaet> ara,  vanhoof, ^^  ?
[16:17] <marjo> skaet: i have the same question; posed to vanhoof
[16:19] <sconklin> o/
[16:19] <sconklin> (when this topic has closed)
[16:19] <skaet> ..
[16:19] <marjo> ,,
[16:20] <marjo> ..
[16:20] <ara> ..
[16:20]  * skaet looking around for comments from vanhoof?
[16:21] <ara> skaet, I think vanhoof is on swap day today
[16:21] <ara> :(
[16:21] <skaet> ahh, ok,  we'll stop waiting then.
[16:21] <skaet> sconklin go, while I try to summarize where we are with the interlock.
[16:22] <sconklin> Brad's question went unanswered - Why do schedules start mid-week? It would work much better for us if uploads to -proposed were on Monday and not Friday
[16:22] <sconklin> I meant Thursday
[16:23] <sconklin> Monday not Thursday
[16:23] <skaet> sconklin,  pattern was followed for interlock with development release schedules
[16:23] <skaet> however,  the reason for indicating the -proposed (date)
[16:24] <skaet> was to clarify when things were available
[16:24] <skaet> similarily with -update(date) which doesn't happen on thursdayse either.
[16:24] <skaet> interlock, is because testing happens with other teams work on that schedule.
[16:24] <skaet> we can certainly revisit this, and resetting expectations at UDS.
[16:25] <skaet> key is that we have to look at it from the overall viewpoint to keep things sane for the teams that have to work between stable, and development.
[16:25] <sconklin> ok, not trying to change anything today but let's open a discussion among the teams about it
[16:25] <sconklin> ..
[16:26] <skaet> ok.
[16:26] <skaet> moving on then since I was busy typing ;)  will summarize at the end.
[16:26] <skaet> [TOPIC] QA status - marjo
[16:26] <MootBot> New Topic:  QA status - marjo
[16:26] <marjo> hi folks
[16:27] <marjo> Dapper completed on March 21. No regressions. https://wiki.ubuntu.com/QATeam/KernelSRU-dapper-2.6.15-57.94
[16:27] <marjo> Hardy completed on March 25. No regressions. https://wiki.ubuntu.com/QATeam/KernelSRU-hardy-2.6.24-29.88
[16:27] <marjo> New LUB, LBM and LRM installed correctly too.
[16:27] <marjo> skaet: given the previous discussion, are you still interested in possible test plans for this week, or not?
[16:28] <skaet> marjo,  am interested in test plans for next week.
[16:28] <marjo> it's getting late on a monday...
[16:28] <marjo> ah ok
[16:28]  * skaet notes the kernel available should be in verification this week, testing next
[16:29] <marjo> so, next week (week of April 4), the QA team is available for testing Lucid and/or Maverick kernels
[16:29] <marjo> ..
[16:30] <skaet> thanks marjo.
[16:31] <skaet> any question?
[16:31] <skaet> [TOPIC] HW certification - ara
[16:31] <MootBot> New Topic:  HW certification - ara
[16:31] <ara> We are waiting for the verification phase to finish to start testing
[16:31] <ara> sconklin, when are you guys expecting the patches to be verified?
[16:31] <ara> how is the verification going?
[16:31] <ara> ..
[16:31] <sconklin> one sec
[16:33] <sconklin> it looks like we have a couple of bugs left to be verified for lucid and maverick, but if we're resetting the schedule so that verification effectively started Friday, then we should be able to easily get those
[16:33] <sconklin> I expect in the next day or so if I start harassing people
[16:33] <sconklin> ..
[16:33] <ara> sconklin, sounds good, let us know when that happens, please
[16:33] <ara> ..
[16:33] <sconklin> http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html
[16:33] <MootBot> LINK received:  http://kernel.ubuntu.com/~kernel-ppa/reports/sru-report.html
[16:33] <sconklin> latest status is always here
[16:33] <sconklin> ..
[16:34] <skaet> sconklin,  let me summarize to make sure I'm understanding...
[16:35] <skaet> you'll fiinish off the verifications in next day or two,  and then send email to the list.
[16:35] <skaet> at that time QA and HW cert (as their other schedules permit)  can start.
[16:35] <skaet> with starting no later than this Friday.
[16:36] <skaet> sconklin, ara, marjo - does that match your understanding too?
[16:36] <ara> yes
[16:36] <sconklin> Yes, that's the way I read the Nattyinterlock schedule, and that's what we're targeting.
[16:36] <marjo> skaet: why, "no later than this Friday"?
[16:37] <marjo> skaet: usually, QA testing starts on Mondays
[16:37] <skaet> marjo,  beta-1 will be out, and code will be ready.
[16:37] <marjo> skaet: ack
[16:37] <skaet> thanks marjo.
[16:37] <sconklin> ..
[16:37] <skaet> any other questions?
[16:38] <skaet> [TOPIC] general SRU status - pitti
[16:38] <MootBot> New Topic:  general SRU status - pitti
[16:38] <pitti> still need to schedule a training session with SpammapS
[16:38] <pitti> last time we had one the queues were empty, and then the beta-1 rush came in the way
[16:39] <pitti> there is a high-urgency bind9 update which we need to rush through, for bug 651875
[16:39] <pitti> (Daviey is on it now)
[16:39] <pitti> otherwise, business as usual
[16:39] <pitti> ..
[16:39] <skaet> thanks pitti
[16:40] <skaet> any one have questions?
[16:40] <skaet> [TOPIC] OEM priorities
[16:40] <MootBot> New Topic:  OEM priorities
[16:40] <skaet> any one around to represent OEM since vanhoof is out?   smagoun?
[16:40] <smagoun> skaet: I'm here
[16:41] <skaet> any issues to flag, and priorities we need to be aware of?
[16:41] <smagoun> skaet: I confess I've not been following the meeting though - is this specifically OEM priorities for Natty?
[16:41] <skaet> smagoun,  for maverick, lucid, and other stable releases
[16:41] <skaet> (everything except natty ;) )
[16:41] <smagoun> skaet: The SRU cycle has been preempted by 11.04 testing, which has caused a bit of fuss in OEM but we've worked around it.
[16:42] <smagoun> skaet: We have a couple of bugs in the -proposed kernel, we do want them to see the light of day eventually ;)
[16:43] <skaet> smagoun,  the fixes in proposed will be going through in week after this one.
[16:43] <smagoun> skaet: I think the (natural) tension of having 1 team test new development (11.04) and maintenance needs to be addressed organizationally, which makes it a good topic for the UDS timeframe
[16:43] <skaet> smagoun,  agreed
[16:44] <smagoun> skaet: Going through, as in released to -updates?
[16:45] <skaet> smagoun,  per the interlock, that's targeted for 4/7.
[16:45] <skaet> after that next window for fixes to go to updates is end of first week of may.
[16:46] <skaet> all changes for that one will need to be in -proposed by 4/22.
[16:46] <smagoun> skaet: ok, thanks. A couple people around here interpreted bjf's mail as there being nothing new into -updates from now until May. Glad to hear that's not the case.
[16:46] <skaet> https://wiki.ubuntu.com/NattyReleaseInterlock
[16:46] <smagoun> ..
[16:46] <skaet> thanks smagoun
[16:46] <skaet> any other questions?
[16:47] <smagoun> not right now, thanks
[16:47] <skaet> I meant anyone else have questions for you ;)   will move on though since I don't see any hands
[16:47] <skaet> [TOPIC] Support priorities - martins
[16:47] <MootBot> New Topic:  Support priorities - martins
[16:48]  * skaet not seeing martins in the channels though today.
[16:48] <skaet> anyone have concerns from support?  representing martin?
[16:48] <skaet> [TOPIC] New business, last chance for general questions? - all
[16:48] <MootBot> New Topic:  New business, last chance for general questions? - all
[16:49] <skaet> does anyone want me to summarize what the plan is for the next month,  or is it pretty clear now from the discussions?
[16:49] <ara> summary! summary! go skaet, go!
[16:50] <skaet> :)
[16:50] <skaet> kernel  (maverick, lucid) -> proposed  3/25
[16:50] <skaet> verification in progress this week
[16:51] <skaet> hw cert/qa   - 4/1-4/7
[16:51] <skaet> kernel (maveric, lucid) -> update 4/7
[16:51] <skaet> kernel ( maverick, lucid?)-> proposed 4/22
[16:52] <skaet> verification 4/25-4/29
[16:52] <skaet> hw cert/qa - 4/29 - 5/5
[16:53] <skaet> kernel (maverick, lucid? ) to update 5/5
[16:53] <skaet> after that we're at UDS, and revisit the cycle for the rest of Oneiric.
[16:53] <marjo> skaet: ack
[16:53] <ara> sounds good to me
[16:54] <skaet> sconklin, bjf - ok?
[16:54] <sconklin> reading
[16:55] <sconklin> yes, I think that matches everything that we talked about earlier, and I'm happy to see the possibility that Lucid will get through also
[16:55] <sconklin> ..
[16:55] <skaet> ok,  thanks all.   I think we've got this sorted then.
[16:55] <skaet> good meeting.
[16:55] <marjo> skaet: thx
[16:55] <skaet> next meeting is 4/11.
[16:56] <skaet> #endmeeting
[16:56] <MootBot> Meeting finished at 10:56.
[16:56] <skaet> thanks marjo, ara, bjf, sconklin, pitti, smagoun
[16:56] <sconklin> Thanks skaet!
[16:56] <ara> thanks skaet!
[16:58] <pitti> thanks all
[18:06] <mdeslaur> hello
[18:06] <jdstrand> hi
[18:06] <jdstrand> let's get started
[18:06]  * sbeattie waves
[18:07] <jdstrand> #startmeeting
[18:07] <MootBot> Meeting started at 12:07. The chair is jdstrand.
[18:07] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:07] <jdstrand> The meeting agenda can be found at:
[18:07] <jdstrand> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:07] <jdstrand> [TOPIC] Review of any previous action items
[18:07] <MootBot> LINK received:  https://wiki.ubuntu.com/SecurityTeam/Meeting
[18:07] <MootBot> New Topic:  Review of any previous action items
[18:08] <jdstrand> sbeattie uploaded apparmor 2.6.1. great work sbeattie, thanks!
[18:08] <sbeattie> jdstrand: thanks for sponsoring!
[18:08] <jdstrand> I (finally) got arround to looking at blackhat/defcon registration, and that is underway now
[18:08] <jdstrand> sbeattie: sure thing :)
[18:09] <jdstrand> [TOPIC] Weekly stand-up report
[18:09] <MootBot> New Topic:  Weekly stand-up report
[18:09] <jdstrand> I'll go first
[18:09] <jdstrand> so, last week I didn't get to a bunch of stuff I thought I would, and this week is a short week for me
[18:09] <jdstrand> I will be off friday and then next monday and tuesday
[18:10] <jdstrand> I am on triage this week
[18:10] <jdstrand> I hope to finish testing the openldap and libvirt updates
[18:10] <jdstrand> and I expect some archive admin work for beta
[18:10] <jdstrand> I'll try to get to the other stuff I said I'd do last week as I have time
[18:11] <jdstrand> that's it from me
[18:11] <jdstrand> mdeslaur: you're up
[18:11] <mdeslaur> I am currently testing packages for a bunch of security updates I've prepared last week
[18:11] <mdeslaur> I'll be publishing them this week if all goes well
[18:11] <mdeslaur> beyond that, I'll go down the list
[18:11] <mdeslaur> oh, and if this is beta week, I'll do some iso testing also
[18:11] <mdeslaur> that's it from me.
[18:12] <mdeslaur> -> sbeattie
[18:12] <sbeattie> I was on community last week, sponsored a couple of packages (dtc, loggerhead)
[18:12] <sbeattie> I'm in the happy place this week, so I'm looking for updates to pick up (was thinking postfix)
[18:13] <sbeattie> I think that's all for me.
[18:13] <sbeattie> Oh, yeah, iso testing.
[18:13]  * sbeattie has one system left to upgrade to natty as well.
[18:14]  * sbeattie -> micahg
[18:14] <micahg> so, as jdstrand added to the wiki, I'm cleaning up after the comodo mess
[18:15] <micahg> nss, qt4-x11, ca-certificates (maybe)
[18:15] <micahg> there's a chromium update, but we're blocked on an upstream regression
[18:15] <micahg> and I have ISO testing
[18:15] <jdstrand> micahg: is there a workaround for that? ie, can we just fallback to the previous behavior?
[18:16] <micahg> jdstrand: well, there's a workaround, but it's flaky IMHO
[18:16] <micahg> was going to discuss with you further after the meeting
[18:16] <jdstrand> micahg: right, --detect=auto or something. I meant something where we can just have the old upstream behavior
[18:16] <jdstrand> s/upstream//
[18:17] <micahg> jdstrand: well, I have to see exactly what the old behavior was to answer that :)
[18:18] <jdstrand> micahg: ok. as you know, fta can probably help there. I don't think we can publish chromium in good conscience with that regression
[18:18] <micahg> so, possibly, fta mentioned possibly working around it
[18:18] <jdstrand> micahg: alternatively, I wonder if we can snag fta's previous update for the comodo fixes and push that into the archive
[18:18] <jdstrand> micahg: then wait for upstream to fix the regressino
[18:19] <jdstrand> (assuming there isn't a good way to deal with the current version that has the additional security fixes)
[18:20] <micahg> I'll look into that
[18:21] <jdstrand> ok
[18:22] <jdstrand> micahg: did you have anything else?
[18:22] <micahg> no, I think that's it for me
[18:22] <jdstrand> thanks
[18:22] <jdstrand> [TOPIC] Miscellaneous and Questions
[18:22] <MootBot> New Topic:  Miscellaneous and Questions
[18:23] <jdstrand> Looks like self-evaluations are done. I need to do my part now (I have a couple weeks)
[18:23] <jdstrand> all work items tied to natty's release are completed. Great job everyone! :)
[18:24] <jdstrand> that's all I have
[18:24] <jdstrand> does anyone have any other questions or items to discuss?
[18:24] <micahg> o/
[18:24] <jdstrand> micahg: go ahead
[18:25] <micahg> when does the review for the testing libraries (QRT) start? next week?
[18:25] <jdstrand> https://wiki.ubuntu.com/SecurityTeam/ReleaseCycle#Regression%20Testing
[18:26] <micahg> yep, ok :)
[18:26] <jdstrand> ^ that says kernel and glibc should be happening now
[18:26] <jdstrand> the rest fall port-beta
[18:26] <jdstrand> s/port/post/
[18:27] <jdstrand> kees and/or sbeattie have traditionally done the kernel/glibc ones
[18:27] <jdstrand> and I'm pretty sure they have been done all the way along
[18:28] <jdstrand> any other questions?
[18:28] <jdstrand> ok. thanks everyone!
[18:28] <jdstrand> #endmeeting
[18:28] <MootBot> Meeting finished at 12:28.
[18:28] <micahg> thanks jdstrand
[18:30] <mdeslaur> thanks jdstrand!
[18:31] <jdstrand> sure! :)
[19:58] <SpamapS> any chance DMB will get quorum today?
[19:59] <Laney> I am partially here
[19:59]  * stgraber too
[19:59] <stgraber> just got out of a meeting and have quite a lot of stuff to do now but will follow the meeting for votes and stuff
[20:00] <stgraber> that's if we manage to get quorum
[20:00]  * bdrung_ is here, but very tired.
[20:00] <SpamapS> bdrung_: as long as you're not cranky.. thats ok. ;)
[20:01] <stgraber> maco, cody-somerville, persia, geser: ping
[20:01] <Laney> :)
[20:02] <bdrung_> SpamapS: not cranky, just slow and unemotional
[20:02] <cody-somerville> Hi.
[20:02] <ScottK> I would propose not approving SpamapS so we still get to make him do useful stuff in exchange for sponsorship.
[20:02] <ScottK> ;-)
[20:03] <Laney> :-)
[20:03] <Laney> who wants to chair?
[20:03] <cody-somerville> Wow. 8 applications? Geez. I dunno if we'll get through them all.
[20:03] <Laney> I am on my phone and in a pub so no good.
[20:03]  * geser waves
[20:04] <SpamapS> please do not pay attention to scottk he is a master extortionist ;)
[20:05] <geser> ScottK: will SpamapS do useless stuff if he gets upload rights?
[20:05] <ScottK> extorionist/efficient distorbutor of necessary work.
[20:05] <SpamapS> ScottK: all a matter of perspective. :)
[20:05] <ScottK> geser: No, but I'll lose leverage to get him to work on my stuff.
[20:06] <SpamapS> geser: I will occasionally still play Angry Birds if I have upload rights.. ;)
[20:06] <hrw> hi
[20:06] <Laney> can we get started?
[20:06] <cyphermox> hrw, hey
[20:06]  * cody-somerville volunteers to chair.
[20:06]  * hrw just arrived at home - 21:07 here
[20:07] <Laney> ty
[20:07] <cody-somerville> Do we have quorum?
[20:07] <stgraber> yep
[20:07] <Laney> yes
[20:07] <cody-somerville> #startmeeting
[20:07] <MootBot> Meeting started at 14:07. The chair is cody-somerville.
[20:07] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[20:07] <cody-somerville> [TOPIC] Review of previous action items
[20:07] <MootBot> New Topic:  Review of previous action items
[20:08] <cody-somerville> * Emmet Hikory to organise the selection process for DMB renewal
[20:08] <Laney> done
[20:08] <cody-somerville> Ack.
[20:08] <cody-somerville> [TOPIC] Administrative Matters
[20:08] <MootBot> New Topic:  Administrative Matters
[20:09] <cody-somerville> [TOPIC] Administrative Matters: Review progress of probationary period of Marco Rodrigues
[20:09] <geser> is the mailing lists admin issue now resolved?
[20:09] <MootBot> New Topic:  Administrative Matters: Review progress of probationary period of Marco Rodrigues
[20:09] <cody-somerville> So, I've unfortunately dropped the ball on this. It had been my intention to have already sent an e-mail report out weeks ago.
[20:10] <Laney> geser: mostly, I think someone from the tb sould sort out the dmb admin soon
[20:10] <Laney> mailed today.
[20:11] <cody-somerville> I still intend to send an e-mail. To summarize however, I'm unsure if the probation period has been entirely effective.
[20:11] <cody-somerville> Though there were a few occasions early on where Marco did not follow the agreement by participating in discussions in #ubuntu-motu.
[20:12] <cody-somerville> And I've not yet processed anything he has submitted to me that I was actually able to sponsor due to problems.
[20:12] <geser> what kind of problems?
[20:13] <cody-somerville> He requested a sync but did not test build it in Ubuntu. It turned out the package FTBFS in Ubuntu. I later found there was even already a bug report open regarding it.
[20:14] <cody-somerville> Furthermore, doing an actual debdiff resulted in additional delta not mentioned in the package changelog and that was not mentioned in his request.
[20:15] <cody-somerville> It appears the decision to request the sync was based entirely on examination of the package changelogs.
[20:17] <cody-somerville> [TOPIC]  Administrative Matters: Membership renewal policy for delegated teams
[20:17] <MootBot> New Topic:   Administrative Matters: Membership renewal policy for delegated teams
[20:17] <geser> how many requests from Marco did you had to review?
[20:18] <cody-somerville> oops
[20:18] <cody-somerville> geser, It submitted 5 in total. The last one sent to me was January 25th.
[20:18] <cody-somerville> *He
[20:19] <cody-somerville> He sent me an e-mail February 7th regarding one of the requests I had not yet processed. The request was sufficiently old to ping me about it.
[20:20] <bdrung_> did you had any problems besides technical issues?
[20:21] <bdrung_> did he repeat mistakes?
[20:21] <geser> I guess we can discuss this after your detailed report per mail, let's move to the next topic as the agenda is long
[20:22]  * bdrung nods.
[20:22] <ScottK> He's been involved in Ubuntu development since 2007, IIRC.  Basic stuff like test building he should know by now.
[20:22] <Laney> currently the members of delegated teams need to have their membership renewed by an admin. I don't see what the point of this is, seems to be busy work to me. I suggest we allow members of delegated teams to renew themselves.
[20:22] <Laney> sorry for being terse again, on phone
[20:22] <bdrung> i am fine with this change.
[20:23] <geser> ScottK: true, and this sound like the kind of the problems in the past
[20:23] <cody-somerville> bdrung, He participated in #ubuntu-motu a few times even after reminder that it violated the agreement.
[20:23] <Laney> shall we just vote?
[20:23] <bdrung> yes
[20:24] <ScottK> geser: Agreed.
[20:24] <cody-somerville> greping my logs I actually see he said something to Laney on the 20th of January even
[20:24] <cody-somerville> (in #ubuntu-motu)
[20:24] <cody-somerville> Jan 20 13:03:39 <Kmos>	Laney: check collab-qa for udd scripts, there is a rcbugs for debian -> ubuntu, it could be adapted easily.
[20:24] <cody-somerville> Laney, on the renewal policy?
[20:24] <Laney> yes
[20:25] <cody-somerville> Aye.
[20:25] <cody-somerville> [VOTE] Allow members of delegated teams to renew themselves.
[20:25] <MootBot> Please vote on:  Allow members of delegated teams to renew themselves..
[20:25] <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
[20:25] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[20:25] <bdrung> +1
[20:25] <MootBot> +1 received from bdrung. 1 for, 0 against. 0 have abstained. Count is now 1
[20:25] <Laney> +1
[20:26] <MootBot> +1 received from Laney. 2 for, 0 against. 0 have abstained. Count is now 2
[20:26] <stgraber> +1
[20:26] <MootBot> +1 received from stgraber. 3 for, 0 against. 0 have abstained. Count is now 3
[20:26] <cody-somerville> +1
[20:26] <MootBot> +1 received from cody-somerville. 4 for, 0 against. 0 have abstained. Count is now 4
[20:27] <geser> +1
[20:27] <MootBot> +1 received from geser. 5 for, 0 against. 0 have abstained. Count is now 5
[20:27] <cody-somerville> #endvote
[20:27] <cody-somerville> [endvote]
[20:27] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[20:27] <cody-somerville> [AGREED] Allow members of delegated teams to renew themselves
[20:27] <MootBot> AGREED received:  Allow members of delegated teams to renew themselves
[20:27] <cody-somerville> [TOPIC] Administrative Matters: New meeting time
[20:28] <MootBot> New Topic:  Administrative Matters: New meeting time
[20:28] <Laney> i'll have an action to update them
[20:28] <cody-somerville> [ACTION] Laney to update delegated teams to allow members to renew their memberships themselves.
[20:28] <MootBot> ACTION received:  Laney to update delegated teams to allow members to renew their memberships themselves.
[20:29] <Laney> we sometimes have issues achieving quorum
[20:29] <Laney> I hope someonhe else can pesent this better)
[20:29] <hrw> Laney: like 2 weeks ago?
[20:29] <cody-somerville> Particularly at the earlier meeting time, right?
[20:30] <Laney> There was a discussion on the ML about changing one or both of our times
[20:30] <Laney> cody-somerville: yeah, I believe it doesnt work so well for those of us in the americas
[20:30]  * cody-somerville nods.
[20:30] <Laney> I think there was broad approval to move the earlier meeting 1 hour later
[20:30] <cody-somerville> Agreed.
[20:31] <Laney> but this slot seems to work OK
[20:31] <cody-somerville> Agreed.
[20:31] <Laney> does anyone have a problem with that?
[20:31] <bdrung> looking at the meeting logs shows that we had problems only with the early meeting time (3x in the last half year)
[20:32] <bdrung> moving the meeting won't change anything for me
[20:32] <stgraber> moving the early meeting an hour later would make it a lot easier for me, still not perfect as it's a Monday morning and I tend to be busy with other things, but as it's once a month I should be able to make it
[20:32] <geser> I can't make the early meeting at all (if that's a problem to reach quorum)
[20:32] <cody-somerville> If anyone does have a problem, please feel free to e-mail the DMB mailing list. Otherwise I think its safe to say we'll move forward with the changes Laney described.
[20:33] <cody-somerville> [TOPIC] MOTU Application: Sylvestre Ledru - https://wiki.ubuntu.com/UbuntuDevelopment/SylvestreLedruMOTU
[20:33] <MootBot> New Topic:  MOTU Application: Sylvestre Ledru - https://wiki.ubuntu.com/UbuntuDevelopment/SylvestreLedruMOTU
[20:34] <cody-somerville> I'm not sure if Sylvestre is here or not - lp page doesn't list IRC nick.
[20:35] <cody-somerville> However, I'm happy to move forward with voting based on the contents of the application.
[20:35] <Laney> I think we ought to give him a chance to respond to the comment
[20:36] <cody-somerville> My vote would be the same even if the comment wasn't there.
[20:37] <Laney> OK
[20:37] <cody-somerville> The comment was also made on the 12th. In other cases where there was negative commentary on an application, applicants would often comment on the comment in-line.
[20:38] <Laney> I'm keen not to hold up those who are here
[20:38] <Laney> so however you wish to move forward
[20:39] <bdrung> i prefer to talk to him before voting
[20:40] <cody-somerville> [TOPIC] Ubuntu Core Developer Application: Clint Byrum - https://wiki.ubuntu.com/ClintByrum/DeveloperApplication
[20:40] <MootBot> New Topic:  Ubuntu Core Developer Application: Clint Byrum - https://wiki.ubuntu.com/ClintByrum/DeveloperApplication
[20:40] <ScottK> BTW, I'd say -1 based on reviewing a disasterous upload from him during Maverick final freeze ...
[20:40] <SpamapS> o/
[20:40] <ScottK> (that was for Sylvestre)
[20:40] <Laney> ScottK: could you elaborate on the application?
[20:41] <ari-tczew> Sylvestre doesn't build package before uploading and then he comments on bug what I should to do to fix his FTBFS - funny... his bad upload, his fix - easy.
[20:41] <Laney> SpamapS: hi
[20:42] <Laney> how are you? :-)
[20:42] <SpamapS> Very well thanks. No more jet lag this time.
[20:44] <ScottK> Laney: I'll try to remember.  I'm on the way out the door right now.
[20:44] <ScottK> +1 on SpamapS, BTW.
[20:44] <ScottK> Gotta run.
[20:45] <SpamapS> ScottK: ty!
[20:45] <Laney> I see you commented on a lack of clarity around the application criteria - do you have any suggestions on how we can improve?
[20:46] <geser> SpamapS: oh, did you accept enough tasks from ScottK that he changed his mind? :)
[20:46] <SpamapS> I'd like to see a very clear pool of mentors established. The debian mentoring process seems stronger, and its very clear that your mentor will help guide you to the next step.
[20:47] <SpamapS> geser: Yes I will have to shovel his sidewalk next time I'm in Baltimore. ;)
[20:48] <Laney> We have a mentorship programme, but I agree that it's not very active right now...
[20:48] <cody-somerville> SpamapS, Would you consider yourself familiar with Ubuntu development procedures and policies? Would you be able to advise a new contributor on them?
[20:48] <SpamapS> Its also not exactly clear if I've "done enough" for core dev. Many of my colleagues tell me that I have, but there's no authoritative source that says yes.
[20:49] <SpamapS> cody-somerville: I think in my brief time I've become quite familiar with the lower level of development; packaging, bug triage, patch forwarding, etc. With that, yes I think I would definitely be able to walk a new contributor through the process, and in fact, have been mentoring one such person just recently.
[20:49] <BlackZ> Laney: we're *slowly* reorganizing it
[20:50] <cody-somerville> SpamapS, How about in relationship to performing an SRU? Freezes? Freeze Exceptions?
[20:50] <SpamapS> cody-somerville: to the point of higher level ubuntu policies, such as releases , MIR's, SRU's, etc., I'd say I am at an intermediate level, and still have a lot to learn, especially around the actual stable release process.
[20:50]  * highvoltage wants to through in some cheerleading for SpamapS since he's very much present and involved in #ubuntu-motu and is helpful and interactive with the larger community (and in my opinion that means a lot)
[20:51] <SpamapS> cody-somerville: I've actually begun the process of training with Martin Pitt to join the SRU team. :)
[20:51] <cody-somerville> SpamapS, Are you a MOTU?
[20:51] <SpamapS> that is something I just started two weeks ago, and have not added to my developer app yet.
[20:51] <SpamapS> cody-somerville: no I am not a MOTU.
[20:51] <cody-somerville> SpamapS, Is there a particular reason you haven't applied to be a MOTU?
[20:52] <SpamapS> cody-somerville: by the time my application was ready, and I showed it to a few people, they said I should skip MOTU / server package set, and go for core dev.
[20:53] <cody-somerville> SpamapS, have you had any uploads sponsored by a community member before?
[20:54] <SpamapS> cody-somerville: Not sure I understand the question. I've had quite a few sponsored uploads to Ubuntu.
[20:55] <cody-somerville> SpamapS, Have had any uploads sponsored by someone you don't work with? :)
[20:55]  * tumbleweed has sponsored uploads for SpamapS
[20:55] <tumbleweed> ( I think)
[20:55]  * broder too
[20:55]  * micahg sponsored some pre-canonical
[20:55] <SpamapS> cody-somerville: to Ubuntu.. I don't know. Maybe ScottK has done a few uploads for me. I have had some things uploaded to Debian by people I don't work with.
[20:56]  * SpamapS is ashamed that he doesn't remember all of his sponsors. :/
[20:56] <broder> we really need a script for looking sponsorship info up
[20:56]  * broder goes to see how quickly he can throw one together
[20:56] <tumbleweed> broder: I have one somewhere
[20:57]  * cody-somerville has no further questions.
[20:57] <micahg> broder: I filed a bug to ask for it to be integrated into LP
[20:57] <Laney> me neither.
[20:57] <stgraber> I'm really sorry but I have another meeting in 3 minutes, so I'd appreciate it if we could vote on SpamapS. Then I'll have to leave you.
[20:57] <broder> tumbleweed: sounds like that would be an awesome ubuntu-dev-tools addition, but let's take this elsewhere
[20:57] <cody-somerville> [VOTE] Ubuntu Core Developer Application: Clint Byrum
[20:57] <MootBot> Please vote on:  Ubuntu Core Developer Application: Clint Byrum.
[20:57] <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
[20:57] <MootBot> E.g. /msg MootBot +1 #ubuntu-meeting
[20:57] <cody-somerville> +1
[20:57] <MootBot> +1 received from cody-somerville. 1 for, 0 against. 0 have abstained. Count is now 1
[20:57] <bdrung> broder: i agree on both points
[20:58] <Laney> +1
[20:58] <stgraber> +1
[20:58] <MootBot> +1 received from Laney. 2 for, 0 against. 0 have abstained. Count is now 2
[20:58] <MootBot> +1 received from stgraber. 3 for, 0 against. 0 have abstained. Count is now 3
[20:58] <bdrung> +1
[20:58] <MootBot> +1 received from bdrung. 4 for, 0 against. 0 have abstained. Count is now 4
[20:59] <geser> +1
[20:59] <MootBot> +1 received from geser. 5 for, 0 against. 0 have abstained. Count is now 5
[20:59] <cody-somerville> [endvote]
[20:59] <MootBot> Final result is 5 for, 0 against. 0 abstained. Total: 5
[20:59] <stgraber> congratz SpamapS
[20:59] <cody-somerville> SpamapS, Congratulations.
[21:00]  * SpamapS bows humbly
[21:00] <cyphermox> congrats SpamapS
[21:00] <Laney> \o/
[21:00] <broder> congrats
[21:00] <SpamapS> thanks so much to all. :)
[21:00]  * SpamapS does a little dance at his desk
[21:00] <cody-somerville> I also have to go now unfortunately.
[21:00] <Laney> me too.
[21:01] <Laney> We'll get through more applications next time.
[21:01] <Laney> thanks all!
[21:01] <geser> then we lost quorum?
[21:01] <bdrung> SpamapS: you can continue that dance at UDS ;)
[21:01] <cyphermox> appears so
[21:01] <stgraber> geser: with 3 of us leaving out of the 5 present at the meeting, it seems so
[21:01] <hrw> so 28 April
[21:01] <cody-somerville> #endmeeting
[21:01] <MootBot> Meeting finished at 15:01.
[21:06] <hrw> have a nice rest of day