[00:05] <akiva-thinkpad> balloons, cool thanks /late reply
[00:48] <josharenson> Is there an easy to install an unsigned click package?
[02:17] <Randy_O> Is there something special about the SDK I need to do to make offline scopes? It's not in my dropdown list when making a new scopes project.
[02:30] <akiva-thinkpad> Randy_O, good question
[02:31] <akiva-thinkpad> Randy_O, are you going to the UOS? There is going to be a session on scope development
[02:31] <akiva-thinkpad> Randy_O, also; are you entering the competition?
[02:33] <Randy__O> akiva-thinkpad, I am going to try and follow the UOS, so far I've watched the 3 videos they put on ubuntu on air, and they only show how to do online scopes
[02:33] <akiva-thinkpad> Randy__O, still there?
[07:15] <dpm> good morning
[07:23] <dpm> good morning all
[07:31] <rpadovani> dpm, ping :-)
[07:33] <dpm> morning rpadovani
[07:36] <rpadovani> dpm, morning to you :-) So, a question about tags. The branch was ready, but then mzanetti arrived and rewrite all the code for the edit page, I'm waiting the merge of his branch to merge mine too. So, There is no space anymore to list all tags in the editview. Do you want a user could edit the tags of a note in the noteview, or you prefer I add a button in the new toolbar of EditNoteVitew to edit tags? The second one IMO makes mor
[07:36] <rpadovani> e sense, but on Android you can edit tags without editing a note
[07:37] <rpadovani> Dunno if the wall of text above makes sense, if you want I can provide you some screenshots
[07:38] <dpm> rpadovani, it does make sense, thanks :) I was trying the prerequisite caching branch last night, so I've not yet tested the new edit mode page. I can do that now, but if you've got some screenshots, it would help me seeing your proposals on top of that
[07:39] <rpadovani> dpm, sure, just give me some  minutes
[07:46] <dholbach> good morning
[07:57] <rpadovani> dpm, ok, I'll focus on uriHandler but, anyway, I show you how things are going with tagsUI branch. So, this is the NoteView, as you can see there are tags at bottom: http://postimg.org/image/z6h1psh1b/ This is the EditNoteView: http://postimg.org/image/40scfauyn/ there is also a "+" near the tags, so you can add tags. When you click on + button, you have this popup to edit tags: http://postimg.org/image/4azuyn9kv/
[07:57] <rpadovani> But, with new mzanetti branches you have this EditNoteView: http://postimg.org/image/61iw04r3z/
[07:57] <dpm> rpadovani, awesome, thanks. This makes it a lot easier to review
[07:59] <rpadovani> dpm: So, there is no more space for tags in EditNoteView. My question is: should I move the "+" button to the NoteView or I have to create a new icon to insert near mzanetti' s buttons for formatting? I think 2nd is better, but (a) the branch is blocked until mzanetti' s branch lands and (b) evernote on android use 1st
[08:03] <dpm> rpadovani, ok, I understand it now. I've taken a note and I'll try to get a designer to look at this. For now, I'll move both the new edit view and the tags UI bugs to the next milestone, so that we can concentrate on the essential only for the current milestone
[08:04] <rpadovani> dpm, ok :-)
[08:05] <mihir> popey: ping !!
[08:09] <popey> mihir: pong!
[08:09] <mihir> popey: what would you suggest to track down new design stuffs?
[08:09] <popey> dpm: rpadovani mzanetti did you get evernote marketing (spam) today showing off the new UI?
[08:09] <popey> mihir: I don't understand the question.
[08:10] <mihir> popey: shall we create new trunk , or we can merge in existing only?
[08:10] <rpadovani> popey, we use it since a while, but I didn't receive any mail from them
[08:10] <popey> mihir: I would continue on trunk
[08:10] <mihir> popey: okay :)
[08:10] <popey> rpadovani: it was general marketing spam to everyone "Take a tour of the all-new Evernote for Android!"
[08:11] <mihir> popey: also , i'll update the Pad as per our discussion last night.
[08:11] <popey> mihir: excellent, thanks!
[08:11] <mihir> popey: is there anyway we can push sync things less buggy ?
[08:12] <rpadovani> popey, ah, gotcha: but yes, dpm and I use it since a while, and I provided to mzanetti screenshots of all features of the app :-)
[08:12] <mihir> popey: during sprint , we were able to make EDS likely more stable with help of renetu
[08:12] <popey> heh
[08:12] <mihir> popey: just a thought :D
[08:12] <popey> mihir: we need to file bugs if you find them
[08:12] <mihir> popey: hmmm okay :)
[08:12] <mihir> i'll make sure that now onwards.
[08:14] <dpm> popey, I've not checked my personal e-mail today yet, but I probably got it too
[08:15] <popey> k
[08:27] <popey> mzanetti: gonna revert that change I made about unlocking, tested enough, and whether it's placebo or real, it felt like I didn't have the same issue.
[08:42] <mzanetti> good mornging...
[08:42]  * mzanetti catching up with the completely red channel
[08:43] <popey> mzanetti: great
[08:47] <mzanetti> popey: 1st: no, didn't get evernote spam, but yeah, rpadovani sent me some screenies
[08:48] <mzanetti> popey: 2nd, cool, thanks for testing the change. I'll prepare a branch and get it landed then
[08:49] <mzanetti> rpadovani: we still could add the tags feature to the toolbar in the noteeditview. I think in the middle section (add things sections) there's still space, especially now that I removed the <hr/> icon
[08:50] <mzanetti> rpadovani: or. even better, we add it to the panel section (rightmost) and bring in a new toolbox line containing the tags ;)
[08:54] <rpadovani> mzanetti, I love the idea to create a toolbox line for tags
[09:04] <ahayzen> popey, FYI Victor found a massive speed improvement in thumbnailer last night, so we're going to try tweaking the new columnflow implementation as stated here https://code.launchpad.net/~andrew-hayzen/music-app/remix-rewrite-column-flow/+merge/241338/comments/593564 and there is a minor bug fix that needs to be landed, hopefully we should have it by EOD
[09:04] <popey> ahayzen: the fix is upstream in thumbnailer?
[09:05] <ahayzen> popey, no us sortof workaround ish bug 1391368
[09:05] <popey> ok
[09:06] <popey> excellent.
[09:06] <ahayzen> popey, basically we were requesting the size 330 if we request the size 512 and scale ourselves it is much faster
[09:06] <popey> well that sounds counter intuitive!
[09:07] <ahayzen> popey, i'll ping you if we are clear to build a click :) i know right, i guess the QML scaling is faster is faster than what ever they are using
[09:07] <popey> ok
[09:09] <dpm> mzanetti, o/ - let me know when you've got a few minutes to talk
[09:10] <mzanetti> dpm: hey, now is good
[09:12] <dpm> mzanetti, cool, so on https://code.launchpad.net/~mzanetti/reminders-app/caching/+merge/241136 I added a comment. Not a blocker or anything, it was mostly curiosity. Other than talking about that one, I tested it at worked very well
[09:14] <mzanetti> dpm: right, yeah... that's actually QML... the scopes have the same "issue"
[09:15] <mzanetti> dpm: so qml builds delegates from bottom up, so the bottom-most is the first one to be queried, so the first one to be fetched
[09:16] <mzanetti> dpm: not really sure what I can do about it. Saviq had the idea of putting lpotter onto the issue to fix it in the qml listview directly. but no idea yet how feasible that is
[09:17] <dpm> mzanetti, ok, thanks for the context, nothing critical, and I see we cannot fix it in the app, it just looked a bit unexpected. mzanetti, ok, in that case, I think I'll approve it
[09:18] <mzanetti> dpm: thanks :)
[09:21] <mzanetti> dpm: replied to your mail
[09:24] <dpm> mzanetti, awesome, thanks! I think even if the new edit view could happen today, I think I'd like to limit the number of features we land on this milestone. In particular for this one, I'd like to try to find a designer to look at it, as it's a big change (and an awesome one!) from the previous UI
[09:25] <dpm> and it'd be good to coordinate it with the tags UI too
[09:32] <JamesTait> Good morning all; happy Origami Day! \o/
[09:37] <mzanetti> I wonder if there's some instructions around for the origami unicorns we had a the sprint
[09:37] <dpm> I thought there were some online, but I've not looked very hard :)
[09:38] <mzanetti> http://www.youtube.com/watch?v=QVSgrAl3CyU
[09:38] <dpm> nice!
[09:39] <mzanetti> rofl: http://www.youtube.com/watch?v=Qzeaw7UXscw
[09:39] <dpm> the internet will never cease to amaze me
[09:40] <dpm> mzanetti, do you see anything obvious that might need fixing in https://code.launchpad.net/~reminders-app-dev/reminders-app/uriHandler/+merge/239961 ? rpadovani had a look at it this morning, but after doing a change and debugging it, it seems it requires more investigation
[09:41] <mzanetti> dpm: no... just reading the code I'd say it's looking good.  means, I'd need to run it and hammer in some debug prints to figure what's happening
[09:41] <mzanetti> dpm: what's the timeline?
[09:42] <dpm> mzanetti, I'd like to see if it's something we can get into this milestone, as it'd make the scope integration easier, but if not possible, it's nothing critical and I'd move it to the next
[09:42] <mzanetti> relase happening Thu, so having a working branch by tonight ok?
[09:42] <mzanetti> so you can review tomorrow the whole day
[09:43] <dpm> mzanetti, yeah, that'll work nicely if you think it's possible.
[09:43] <mzanetti> I'm sure it is, unless we hit weirdness in the platform
[09:43] <dpm> excellent
[09:49] <kalikiana> t1mp: another look, please https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/ignoreExpectedWarnings/+merge/237280 I responded and pushed some changes
[09:51] <t1mp> ok
[09:58] <mzanetti> popey: hey, as you did quite extensive testing, can you leave some review comment here please? https://code.launchpad.net/~mzanetti/unity8/keep-suspended-while-locked/+merge/241387
[09:58] <popey> mzanetti: sure
[10:06] <JamesTait> mzanetti, I also wondered about the unicorns - thanks for the link!
[10:06] <mzanetti> :)
[10:06] <dpm> mzanetti, could you give me some more context on this one: https://code.launchpad.net/~mzanetti/reminders-app/fix-clone-tags/+merge/241190 - I'm adding it to the list of bugs fixed in the milestone
[10:07] <mzanetti> dpm: this is a bugfix for tags not getting saved to evernote when saving a note
[10:07] <dpm> ah, cool, thanks
[10:40] <dpm> mzanetti, it seems that Jenkins choke on some merge conflicts. Could you merge with trunk and re-push on https://code.launchpad.net/~mzanetti/reminders-app/caching/+merge/241136 ?
[10:41] <mzanetti> dpm: sure
[12:43] <mihir> popey: can you trigger Jenkins https://code.launchpad.net/~pkunal-parmar/ubuntu-calendar-app/IncubteObject/+merge/241166 ?
[12:43] <popey> i cdan
[12:43] <popey> -d
[12:43] <popey> running
[12:49] <dpm> mzanetti, another question: that scrollbars MP for Reminders - am I supposed to see scrollbars in the notes list on the phone, or was it only for desktop? As I don't seem to see any scrollbars atm
[12:50] <mzanetti> dpm: they are there, but the grey on grey doesn't work that well :D
[12:50] <mzanetti> dpm: you *can* see them if watching closely
[12:50] <mzanetti> dpm: but their real value is on the desktop, where they expand when the mouse is hovering them
[12:50] <mihir> popey: thanks.
[12:51] <mzanetti> dpm: maybe we should file a bug against uitk, stating that scrollbar color and default MainView color is pretty much the same
[12:51] <dpm> mzanetti, oh, yes, they're there, but indeed, you need to watch *extremely* closely
[12:51] <dpm> +1
[12:53] <mzanetti> dpm: hmm... actually, we're not using the default bg color
[12:54]  * mzanetti tries how it looks like with defaults
[12:56] <mzanetti> dpm: well, its marginally better, still you only see it if you're actively looking for it
[12:57] <mzanetti> dpm: I'll file a bug
[12:57] <dpm> cool, thanks
[13:01] <mihir> popey: you got few mins?
[13:01] <popey> mihir: wassup?
[13:01] <mihir> popey: need some design clarification :P
[13:01] <mihir> popey: if you go to presentation , and slide num 8
[13:01] <mzanetti> dpm: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1391503
[13:01] <mihir> number*
[13:01] <popey> mihir: ok, one mo
[13:02] <popey> mihir: ok
[13:02] <dpm> thanks mzanetti!
[13:02] <mihir> popey: in that , if you see the border should be white , that's what gorigio has written i couldn't understand that.
[13:03] <popey> mihir: line between events
[13:03] <popey> to separate one event from the next
[13:03] <mihir> popey: yup that is what i have understood.
[13:03] <popey> k
[13:03] <mihir> so that should be white correct?
[13:03] <popey> yes
[13:03] <mihir> popey: okay :)
[13:03] <mihir> gotcha
[13:03] <popey> thanks
[13:20] <mihir> ahayzen: ping
[13:20] <ahayzen> mihir, pong
[13:21] <mihir> ahayzen: i noticed that in listView , the divider never shows in full width , is it how it behaves ?
[13:21] <ahayzen> mihir, maybe? .. i can't remember what ours looked like when we had it?
[13:22] <mihir> ahayzen: this is how it looks , http://i.imgur.com/aoIsPq5.png
[13:22] <mihir> i have no margins in header though.
[13:22] <ahayzen> mihir, looks possibly right? probably best to ask the SDK folks what to expect...or look at the docs
[13:23] <mihir> zsombi: ping
[13:23] <mihir> ahayzen: i thought you would have used it in Music app , so pingged directly to you.
[13:23] <zsombi> mihir: whatsup?
[13:23] <ahayzen> mihir, i think we *did* use it...not anymore i don't think
[13:23] <mihir> hey zsombi doing great
[13:23] <mihir> zsombi: got some sdk question.
[13:24] <mihir> zsombi: got few mins ?
[13:24] <zsombi> mihir: few :)
[13:24] <zsombi> mihir: shoot 'em
[13:24] <mihir> zsombi: i am using ListIItemHeader , and i just noticed that it draw line with margins.
[13:24] <mihir> http://i.imgur.com/aoIsPq5.png
[13:24] <mihir> is it intended ?
[13:25] <zsombi> mihir: the image doesn't tell me your question :)
[13:25] <mihir> zsombi: if you see first Item with the date , and it has line below that.
[13:25] <zsombi> mihir: are you using two items there?
[13:26] <mihir> yes , one is Header another is ListItem.Standard
[13:26] <zsombi> mihir: ok, both of them have a ThinDivider, right? the line you see is the one from Header
[13:27] <mihir> zsombi: in ListItem.Header ThinDivider is by default , and in ListItem.Standard  i have set showDivider to false.
[13:27] <mihir> but what i want is , the ThinDivider in ListItem.Header should be of full width instead of having it with margins.
[13:28] <mihir> zsombi: like here you see, http://i.imgur.com/otZrlVY.png
[13:28] <mihir> the second full width line, which is ListItem.ThinDivider.
[13:29] <zsombi> mihir: yes... there should be an MR landed in staging which fixes that, so if you need to get them edge-to-edge, you shoudl try to access it... but I guess it's not doable from Header...
[13:29] <mihir> zsombi: hmmm so what would be the workaround for that, will it contains property for that ?
[13:29] <mihir> bydefault it will be full width ?
[13:30] <zsombi> mihir: the Header won't :(...
[13:30]  * zsombi hates the ListItems :/
[13:30] <mihir> zsombi: :( then what would be the workaround ?
[13:30] <mihir> zsombi: i can use the ListItem.ThinDivider, but i can't set Header property to false as i can do with standerd list item
[13:30] <zsombi> mihir: unfortunately teh only way would be to create a component of your own...
[13:31] <mihir> zsombi: ahhhh , too much work would be needed just for a line :(
[13:31] <zsombi> mihir: or we raise the thin divider bug so we can land in RTM
[13:31] <zsombi> mihir: we must talk to popey
[13:31] <popey> uhoh
[13:31] <mihir> popey: read the conversation
[13:31] <popey> yes sir!
[13:32] <mihir> zsombi: let me raise bug to track this atleast :)
[13:32] <zsombi> mihir: https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1380766
[13:32] <zsombi> mihir: no need yet another bug
[13:33] <zsombi> mihir: you better comment on this
[13:35] <mihir> zsombi: okay  done
[13:36] <DS-McGuire> Helllo all o/  Can somebody help me with this? : askubuntu.com/questions/548108/what-framework-to-use-for-my-web-app
[13:36] <mihir> zsombi: shall i re-open the status ?
[13:36] <zsombi> mihir: yes
[13:37] <mihir> popey: to summarize , we don't have way to show full width thindivider in ListeItem.Header.
[13:37] <mihir> zsombi: done :)
[13:37] <popey> right
[13:37] <zsombi> mihir: ok, thx, let's hope will get picked up as top priority one
[13:37] <mihir> zsombi: thank you.
[13:38] <popey> zsombi: not sure how I can do that? isn't that an SDK/toolkit thing? Do you just need me to say "hey bzoltan please can the priority of bug 1380766 be raised"?
[13:38] <mihir> zsombi: atleast showDivider property should help I believe ( Just a guess)
[13:38] <popey> I mean, it's ota-1 already, which seems pretty good?
[13:39] <zsombi> popey: it is fixed, but you know that we cannot land anything not "wanted" to RTM...
[13:39] <popey> well, we can, we have the wishlist
[13:39] <zsombi> popey: should I put the bug to the list?
[13:39] <popey> i would.
[13:40] <popey> please ☻
[13:40] <zsombi> popey: ok, on teh way
[13:40] <popey> whether pat & olli agree, is another matter ☻
[13:40] <popey> DS-McGuire: looks like http://askubuntu.com/questions/548108/what-framework-to-use-for-my-web-app needs jdstrand or lool to help
[13:40] <mihir> thanks zsombi popey :)
[13:40] <zsombi> popey: right..
[13:44] <DS-McGuire> popey, Are 'lool' and 'jdstand' suppose to be links? Nothing opens.
[13:44] <popey> DS-McGuire: no, they are people
[13:44] <DS-McGuire> OH! LOL
[13:44] <popey> :D
[13:45] <DS-McGuire> jdstrand, what do you think about this?
[13:45]  * lool opens
[13:46]  * lool 404s
[13:46] <ogra_> fix your proxy :P
[13:46] <lool> DS-McGuire: I bet you're using "devel" or some utopic based image
[13:47] <DS-McGuire> On my machine?
[13:47] <ogra_> the 14.10 framework isnt supported in the 14.04 archive, make sure to have the SDK PPA enabled
[13:48] <ogra_> that will get yo the right framework support
[13:48] <lool> DS-McGuire: on the target (emulator or phone)
[13:48] <lool> DS-McGuire: and in the chroot
[13:48]  * lool gtg
[13:48] <DS-McGuire> lool, Thank you!
[13:50] <nik90> popey: shouldn't the core apps bump the framework version from ubuntu-sdk-14.10-qml-dev3 to ubuntu-sdk-14.10-qml?
[13:51] <popey> I don't think the store enforces that yet for updates to apps (right beuno ?)
[13:52] <beuno> popey, nik90, https://myapps.developer.ubuntu.com/dev/api/click-framework/
[13:52] <beuno> is the current status of the store
[13:53] <beuno> so -dev3 is still available
[13:53] <beuno> lool gets to decide when that becomes obsolete
[13:53] <nik90> ok
[13:53] <beuno> nik90, it's likely coming though, I'd prepare  :)
[13:54] <nik90> :)
[13:59] <jdstrand> beuno: where can I file a bug to get this resolved: https://code.launchpad.net/~jdstrand/akari/akari-fixes/+merge/240667/comments/593718
[13:59] <jdstrand> beuno: and hi! :)
[14:08]  * beuno looks
[14:09] <beuno> jdstrand, I saw that over the weekend, but it looks fixed, no?
[14:09] <beuno> https://myapps.developer.ubuntu.com/dev/api/click-framework/
[14:09] <beuno> jdstrand, you can edit what the store supports here: https://myapps.developer.ubuntu.com/dev/click-frameworks/
[14:11] <jdstrand> beuno: hmmm, that json does look fixed
[14:12] <jdstrand> beuno: I'm not sure how to account for https://code.launchpad.net/~jdstrand/akari/akari-fixes/+merge/240667/comments/593632
[14:12] <jdstrand> beuno: that comment was from 3 hours ago
[14:12] <jdstrand> beuno: is the store preferring the old cache over the new version?
[14:12] <beuno> jdstrand, maybe he had submitted it before?  either way, I'll check, maybe the review scripts are old on the server and they are overriding the api
[14:13] <beuno> right
[14:13] <jdstrand> beuno: thanks
[14:14] <beuno> jdstrand, FWIW, this is the project to file bugs for that: https://launchpad.net/software-center-agent
[14:15] <jdstrand> ah perfect. thanks!
[14:15]  * jdstrand jots that down for later
[14:18] <beuno> jdstrand, indeed it is using the old cache, we'll fix
[14:18] <jdstrand> hmm
[14:19] <jdstrand> beuno: the code is designed to update the cache though, right? istr that was part of the requirements. I also stole the frameworks code for apparmor, so it might be affected too
[14:19] <beuno> jdstrand, it is, the server isn't updating it
[14:19] <beuno> so we need it to start doing that  :)
[14:22] <nik90> balloons, fginther: hey, I proposed a MP for the clock-app which failed in jenkins like few seconds later..https://code.launchpad.net/~nik90/ubuntu-clock-app/bump-framework/+merge/241414 Can you take a look and check what's wrong pls?
[14:22] <jdstrand> beuno: which brings up another point-- I feel like the apparmor json should live somewhere more official
[14:22] <jdstrand> beuno: but I don't know that it needs a full on form
[14:23] <beuno> jdstrand, is it simple enough for it to be represented in the store like frameworks?
[14:23]  * beuno steps out for a quick bite
[14:23] <jdstrand> beuno: it is simple, but not that simple: http://bazaar.launchpad.net/~click-reviewers/click-reviewers-tools/trunk/view/head:/data/apparmor-easyprof-ubuntu.json
[14:35] <mihir> popey: does this make sense , with respect to new Agenda Design , http://i.imgur.com/egawrCX.png ?
[14:38] <popey> mihir: nice one!
[14:38] <popey> thats pretty much exactly as the spec
[14:38] <mihir> popey: i just made work around for dividers :|
[14:38] <mihir> used ListeItem.Standared instead of Header.
[14:38] <mihir> zsombi: ^^
[14:39] <zsombi> mihir: well... doable, however teh font weight will not be the same...
[14:40] <mihir> zsombi: yes i noticed that , but i did with Label inside listItem , it seems solved issue.
[14:40] <zsombi> mihir: nice :)
[14:44] <mzanetti> dpm: merged https://code.launchpad.net/~mzanetti/reminders-app/caching/+merge/241136
[14:45] <mzanetti> dpm: wait... need to update translation
[14:45] <mzanetti> s
[14:49] <mzanetti> dpm: I'm not sure what happened... now the branch is just 4000 lines of translations changes
[14:50]  * mzanetti votes for not doing the pot update in the make step
[14:50] <mzanetti> this is really annoying when developing
[14:51] <ajalkane> mzanetti: it is and every new developer makes the mistake of pushing changed pot files because of that
[14:51] <mzanetti> I'd go as far as saying it happens to most experienced devs too :D
[14:59] <rpadovani> mzanetti, because launchpad truncates diff longer than 4000 or 5000 lines on the web interface, if you use bzr diff/log or look to mail it works well
[15:00] <dpm> mzanetti, yeah, let's disable the "build POT always" thing in the cmake
[15:00] <mzanetti> dpm: on it
[15:00] <dpm> ok, cool. mzanetti, I think it's just a matter of removing the ALL in the rule
[15:01] <mzanetti> dpm: yeah, I also renamed the target so we can easily do "make translations" instead of make com.foo.bar.bar.whatnot
[15:02] <mzanetti> dpm: https://code.launchpad.net/~mzanetti/reminders-app/dont-always-build-translations/+merge/241424
[15:04] <mzanetti> dpm: jenkins is happy again with this one: https://code.launchpad.net/~mzanetti/reminders-app/caching/+merge/241136
[15:04] <mzanetti> I reverted the translation update as it confused me  and we have to do it manually anyways starting now
[15:05] <beuno> jdstrand, if you think the store would be a good place, I could either give you a similar UI than for frameworks
[15:05] <beuno> or straight up uploading a json
[15:05] <jdstrand> I think straight up uploading a json would be good
[15:06] <jdstrand> I have a script to generate it somewhere
[15:06] <beuno> I'll sneak that in soon
[15:06] <jdstrand> cool, thanks
[15:08] <dpm> mzanetti, reviewed https://code.launchpad.net/~mzanetti/reminders-app/dont-always-build-translations/+merge/241424
[15:09] <mzanetti> dpm: done
[15:09] <dpm> :)
[15:10] <dpm> approved
[15:10] <mzanetti> thanks
[15:11] <dpm> mzanetti, on https://code.launchpad.net/~mzanetti/reminders-app/caching/+merge/241136 - can you make it so the po/ folder is the same as in trunk? I.e. revert any changes to .po files?
[15:11] <mzanetti> I can try at least
[15:13] <dpm> mzanetti, all .po files are overwritten daily by Launchpad, so it's not worth merging them or fixing merge conflicts. After your other branch lands, we should stop having conflicts. But on this one, I think it'd be good to have a diff reflecting only the code changes with less noise
[15:13] <dpm> cool, thanks
[15:14] <mzanetti> dpm: yep, done. I just copied the whole po/ folder from a fresh checkout into that branch
[15:14] <dpm> ah, nice
[15:15] <dpm> mzanetti, approved, then
[15:15] <mzanetti> cool :)
[15:17] <mzanetti> dpm: think we could get this one out of the WIP queue? https://code.launchpad.net/~dpm/reminders-app/debian-copyright/+merge/225646
[15:17] <mzanetti> shouldn't be hard to fix
[15:23] <mihir> popey: whenever you get time , could you test this MP with multiple calendar on your branch ---->https://code.launchpad.net/~mihirsoni/ubuntu-calendar-app/AgendaViewFix-newDesign/+merge/241426
[15:24] <pindonga> jdstrand, hi there... can I ask you for some review?
[15:24] <pindonga> https://code.launchpad.net/~ricardokirkner/click-reviewers-tools/fetch-framework-data/+merge/241427
[15:26] <jdstrand> pindonga: I think that is going to cause a problem on the buildds when the testsuite is run
[15:26] <pindonga> jdstrand, why?
[15:26] <pindonga> it's not fetching anything during tests
[15:26] <pindonga> it's mockedout
[15:27] <jdstrand> let me read it more carefully
[15:27] <jdstrand> pindonga: you ran the testsuite on that?
[15:28] <pindonga> yep, using ./run-tests
[15:28] <jdstrand> I'm surprised it passed
[15:28] <pindonga> why? I'm mocking out the call to read_cr_file :)
[15:28] <pindonga> ah, but only in a single place
[15:28] <jdstrand> not cause of anything you did, but because I thought there were more tests for that
[15:28] <pindonga> yep, still passes
[15:29] <pindonga> k
[15:29] <pindonga> it passed bc I had the frameworks.json file cached in my home
[15:29] <pindonga> when I removed that, the test hung for a sec, while fetching the file, then continued, and passed
[15:29] <jdstrand> ah
[15:29] <pindonga> that could be a prolem
[15:29] <jdstrand> right, so it did fetch
[15:29] <pindonga> it did
[15:30] <pindonga> I'll update the mp to mock all places where fetching is done
[15:30] <jdstrand> pindonga: curious what prompted this mp?
[15:30] <pindonga> jdstrand, there was a pkg that failed automated reviews bc of an invalid framework, however the store displays the framework as available and valid
[15:31] <pindonga> the problem here was that the scripts prefer to use the local data/frameworks.json file
[15:31] <pindonga> instead of fetching the latest from the server
[15:31] <jdstrand> and it is because data/frameworks.json exists?
[15:31] <pindonga> l. 8-10 of the mp
[15:32] <jdstrand> right
[15:32] <pindonga> if we pass no local_copy to the Frameworks obj, it will fetch from the remote server if the local cached is outdated
[15:32] <jdstrand> well, the deb packaging is going to need to be adjusted too
[15:32] <pindonga> ?
[15:33] <jdstrand> debian/rules:
[15:33] <jdstrand> -$(shell python3 ./bin/update-frameworks ./data/frameworks.json)
[15:33] <pindonga> ack
[15:33] <jdstrand> it is doing that for the testsuite
[15:34] <jdstrand> on the buildd (to make sure it is up to date)
[15:58] <popey> akiva-thinkpad: nik90 when do you want http://summit.ubuntu.com/uos-1411/meeting/22319/roundtable-creating-a-theming-standard-for-qml/ in the schedule?
[16:00] <nik90> popey: that's being hosted by akiva-thinkpad, I am personally fine with with anything
[16:01] <popey> ok
[16:14] <pindonga> jdstrand, alright, pushed changes .. I've removed the local frameworks file from the cache, run the tests and verified it's not fetched
[16:22] <dpm> mzanetti, I'll try, but I'm not sure I'll manage this week. It's a trivial change, but it requires some time looking into the files and the copyrights
[16:22] <mzanetti> dpm: ok. no worries then... I just was a bit in house-keeping mood today
[16:23] <dpm> mzanetti, sure, it's good to go into that mode every now and then. The caching branch landed, btw :)
[16:26] <mzanetti> \o/
[16:39] <Biju> k
[16:52] <nik90> popey: Can you top approve https://code.launchpad.net/~nik90/ubuntu-clock-app/bump-framework/+merge/241414.. simple framework bump
[16:52]  * popey looks
[16:52] <popey> done
[16:53] <nik90> cool, thnx
[16:53] <sergiusens> nik90: simple is always an invitation for issues! don't jynx it :-D
[16:54] <jdstrand> pindonga: ok, so you probably saw I committed the MP (thanks!)
[16:54] <jdstrand> pindonga: but I have a question
[16:54] <nik90> sergiusens: lol
[16:55] <jdstrand> pindonga: if I modify ~/.cache/click-reviewers-tools/frameworks.json and remove one of the frameworks, then do 'touch -d 20141010 ./frameworks.json', then run click-review /path/to/click, the frameworks.json is not getting updated
[16:56] <jdstrand> pindonga: I was expecting it to get updated since the mtime was out of date and the contents changed
[17:00] <jdstrand> pindonga: so, I think that your change, while needed, won't fix the issue...
[17:00] <jdstrand> an additional change may be needed
[17:01] <pindonga> jdstrand, ack, will check
[17:14] <fginther> nik90, it failed due to a transient error that even failed after a couple of automatic retries. I rebuilt it again and it passed.
[17:15] <nik90> fginther: yeah I saw it pass and got it also top approved. Thnx for looking into it.
[17:17] <pindonga> jdstrand, I just checked the refresh of the frameworks file
[17:18] <pindonga> jdstrand, it uses the ctime, instead of mtime, so touching the file has no effect
[17:18] <pindonga> I've modified my system time to be over 1 wk in the future and run the click checks and the file was properly updatd
[17:26] <jdstrand> pindonga: is ctime the right check for this?
[17:27] <pindonga> that I don't know
[17:28] <pindonga> according to the docs: Return the system’s ctime which, on some systems (like Unix) is the time of the last metadata change, and, on others (like Windows), is the creation time for path
[17:28] <pindonga> while mtime is: Return the time of last modification of path.
[17:28] <pindonga> maybe mtime is better? (more consistent)
[17:29] <pindonga> jdstrand, I think mtime might be better here
[17:30] <pindonga> ctime changes when the inode changes, but if the file is completely rewritten, without changing it's name, the inode might not change, but the data will
[17:30] <jdstrand> pindonga: I think it probably is
[17:30] <pindonga> jdstrand, I'll submit an mp to use mtime
[17:30] <jdstrand> awesome, thanks!
[18:20] <pindonga> jdstrand, mp is ready: https://code.launchpad.net/~ricardokirkner/click-reviewers-tools/check-file-using-mtime/+merge/241443
[19:20] <mihir> rpadovani: ping !!
[19:21] <mihir> to add bottom edge is it mandatory to use custom component , or we do have an option in SDK ?
[19:27] <nik90> mihir: you will need to use the custom component
[19:27] <mihir> nik90: hmm okay , thank you :)
[19:28] <mihir> is it same across the all apps , like contacts/messaging/clock?
[19:28] <nik90> mihir: yup
[19:29] <nik90> mihir: https://bazaar.launchpad.net/~phablet-team/address-book-app/trunk/view/head:/src/imports/Ubuntu/Contacts/PageWithBottomEdge.qml
[19:30] <mihir> nik90: great , thanks :)
[20:19] <rpadovani> mihir, pong
[20:50] <rpadovani> dpm, about uriHandler, I'm not able to debug it, hope mzanetti could. Do you know who other can I ask to?
[20:50] <rpadovani> https://code.launchpad.net/~reminders-app-dev/reminders-app/uriHandler/+merge/239961/comments/593904
[20:55] <dslul> ciao sei italiano? posso chiederti un paio di cose?
[21:16] <rpadovani> dslul, se vuoi paralre italiano pingami su #ubuntu-it-dev
[21:17] <dpm> rpadovani, sorry, about to call it a day, perhaps tomorrow?
[21:17] <dpm> I think this will need some of mzanetti's magic touch, not sure if I can help much on that one
[21:18] <rpadovani> dpm, yes, of course, it was only to keep you informed
[21:21] <dpm> no worries, thanks!
[21:36] <daker> ogra_: it did fail again :/ http://paste.ubuntu.com/8948794/
[21:53] <akiva-thinkpad> akiva-thinkpad: nik90 when do you want http://summit.ubuntu.com/uos-1411/meeting/22319/roundtable-creating-a-theming-standard-for-qml/ in the schedule?
[21:54] <akiva-thinkpad> popey, yah any time is fine for me
[22:06] <t1mp> akiva-thinkpad: note that we also have theming (and a color palette) in the UITK
[22:07] <t1mp> akiva-thinkpad: but it can be improved, and the documentation is not up-to-date yet
[22:07] <akiva-thinkpad> t1mp, yah I saw that recently
[22:07] <akiva-thinkpad> t1mp, one of the main issues I see is around people manually colouring the backgrounds and all that jazz.
[22:08] <t1mp> akiva-thinkpad: most components have a Style associated with it that implement the whole looks and behavior of the component
[22:08] <t1mp> akiva-thinkpad: the "problem" with our current styles, for apps that simply want to change some colors, is that they are quite complicated and contain a lot
[22:08] <t1mp> not just colors
[22:08] <t1mp> although you could create a new theme based on our theme and change only the colors in the derivatives of the styles
[22:09] <akiva-thinkpad> t1mp: do you know how the showcase is doing the theme change?
[22:09] <t1mp> akiva-thinkpad: so the roundtable makes a lot of sense :)
[22:09] <t1mp> uhm, I can look it up
[22:09] <akiva-thinkpad> I have only briefly looked at the code.
[22:09] <akiva-thinkpad> t1mp, Yah I hope you will join us.
[22:12] <t1mp> akiva-thinkpad: http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/examples/ubuntu-ui-toolkit-gallery/Styles.qml
[22:12] <akiva-thinkpad> t1mp, Yah i have seen this; but the question for me is how is it binding the changes to everything in the app?
[22:13] <akiva-thinkpad> t1mp, there is also another project in the core apps that dedicates an entire qml file to theming, and you just reference that
[22:14] <akiva-thinkpad> And the other question is whether theming should extend to Divider, ThinDivider, and UbuntuShape
[22:15] <t1mp> akiva-thinkpad: no, those things are not stylable
[22:15] <t1mp> neither are the new listitems (work in progress)
[22:15] <akiva-thinkpad> t1mp, but they could be.
[22:15] <t1mp> because you need a lot of those, and using styling would slow it down
[22:15] <t1mp> each StyledITem uses a loader to load its style
[22:15] <t1mp> see http://bazaar.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/trunk/view/head:/modules/Ubuntu/Components/StyledItem.qml
[22:15] <akiva-thinkpad> t1mp, couldnt you just replace the ubuntu components import though?
[22:16] <t1mp> all the components set their style property using a function call that returns the proper style from the theme
[22:16] <t1mp> akiva-thinkpad: you mean import a theme?
[22:16] <akiva-thinkpad> t1mp, yes; effectively
[22:16] <akiva-thinkpad> if you wanted a metro theme for example that had hard corners
[22:16] <akiva-thinkpad> instead of the ubuntu curve
[22:17] <t1mp> then you would have to add the import to each component?
[22:17] <t1mp> that means you cannot change the theme on the fly any more
[22:17] <akiva-thinkpad> t1mp, no
[22:17] <akiva-thinkpad> so what I mean
[22:18] <akiva-thinkpad> err theorizing
[22:18] <t1mp> sure :)
[22:18] <akiva-thinkpad> is that you would change the package, "import ubuntu.components 1.1"
[22:18] <akiva-thinkpad> you would literally change the ubuntu.components package.
[22:18] <t1mp> by the way, this is a good session to ask questions and make suggestions: http://summit.ubuntu.com/uos-1411/meeting/22358/ubuntu-ui-toolkit-feedback/
[22:19] <akiva-thinkpad> t1mp, sec; I think I may have committed to something else
[22:19] <t1mp> akiva-thinkpad: uhm. You can create your own components and import your.components 1.1 instead. If they have the same API (but different theme) it will work
[22:19] <t1mp> but then you have your own components and you have to keep them API-compatible with Ubuntu.Components
[22:20] <akiva-thinkpad> t1mp, I am speaking more from a systemwide side.
[22:20] <akiva-thinkpad> So instead of changing the theme of every app individually
[22:20] <akiva-thinkpad> you could impliment a system wide theme
[22:20] <t1mp> ah
[22:20] <t1mp> we don't have system themes
[22:20] <akiva-thinkpad> t1mp, but you could do it, because we do for example
[22:20] <akiva-thinkpad> have UbuntuColors.green
[22:20] <akiva-thinkpad> etc
[22:21] <akiva-thinkpad> and we do have UbuntuShape {}
[22:21] <akiva-thinkpad> If you could get people to bind every single theming colour to say one of the packages, such as
[22:21] <t1mp> if UbuntuColors.green = "yellow" and UbuntuShape returns a triangle, then their names don't really make sense any more ;)
[22:22] <akiva-thinkpad> color: UbuntuTheme.darkTextOnLightBackground
[22:22] <akiva-thinkpad> t1mp, agreed
[22:22] <akiva-thinkpad> lol; triangle
[22:23] <t1mp> we plan to put the settings for each of the components at the top of their style file
[22:23] <t1mp> see for example the changes I did this week to CheckBoxStyle
[22:23] <akiva-thinkpad> so my suggestion would not be to touch that, but to create a standard , and then put it on the back burner for a developer to impliment all these theming standards.
[22:24] <t1mp> all the colors are there at the top of the file now. So you could create your own theme with your CheckBoxStyle derived from the one in Ubuntu.Components.Themes.Ambience and then have CheckBoxStyle.qml: import Ubuntu.Components.Themes.Ambience ; CheckBoxStyle { checkedBackgroundColor: "red" } }
[22:24] <t1mp> and you have a new theme where the checkbox is red when checked instead of green
[22:25] <akiva-thinkpad> t1mp, yah I have seen that; the music app did that with the progress bar
[22:25] <t1mp> yeah, having a standard is also a good idea. Lots of work though :)
[22:25] <akiva-thinkpad> lots
[22:25] <akiva-thinkpad> t1mp, but I would imagine, if we want to have this option as a bullet feature of Ubuntu, that we should do it now
[22:26] <t1mp> I'm not against it, but it is something we would need to discuss more
[22:26] <akiva-thinkpad> yah
[22:26] <t1mp> if we can find the time to work on it :)
[22:26] <akiva-thinkpad> t1mp, well I think getting the standard would be the only thing that would need to be done. Actually implimenting the stuff well...
[22:26] <akiva-thinkpad> that is sort of like whitespace maintaining on the linux kernel
[22:27] <akiva-thinkpad> that sort of stuff is dead easy.
[22:28] <akiva-thinkpad> btw t1mp http://summit.ubuntu.com/uos-1411/meeting/22319/roundtable-creating-a-theming-standard-for-qml/
[22:28] <t1mp> to make it more concrete (and easier to discuss), perhaps you can write down the idea and include some code examples how you would use it?
[22:28] <akiva-thinkpad> i'm going to try to sign up for yours.
[22:28] <akiva-thinkpad> t1mp, will do.
[22:29] <t1mp> akiva-thinkpad: zsombi is doing most of the work in our theming engine, try to catch him too :)
[22:29] <akiva-thinkpad> I'll see
[22:29] <t1mp> akiva-thinkpad: yes, they made me track lead for the app developers track.. so I try to be there for a lot of the meetings (although some of them that are later in the day I will have to miss)
[22:29] <akiva-thinkpad> I sent a mail to the sdk team but
[22:30] <akiva-thinkpad> well who knows; we will see
[22:30] <t1mp> hmm, I didn't see that
[22:30] <t1mp> where did you send the e-mail?
[22:30] <akiva-thinkpad> t1mp, it was to the admins
[22:31] <akiva-thinkpad> I don't know how to send the whole team a message on LP
[22:31] <akiva-thinkpad> although I hear its possible :P
[22:31] <t1mp> probably it is best to use the mailing lists (touch-coreapps), or catch us on irc :)
[22:31] <t1mp> akiva-thinkpad: even better, come to the feedback sessions in the online summit :)
[22:31]  * t1mp gotta go now
[22:31] <akiva-thinkpad> later


[00:00] <wgrant> I just uploaded and downloaded an attachment named 'huh?'
[00:00] <sinzui> wgrant, https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/983116/+attachment/3077581/+files/HUD-to-do-what%3F-de.png
[00:00] <_mup_> Bug #983116: [Component: Keyboard] HUD is <Alt> not <Alt L> <amd64> <apport-bug> <hud> <precise> <gnome-control-center (Ubuntu):New> < https://launchpad.net/bugs/983116 >
[00:00] <wgrant> Yeah, prod strips them
[00:00] <wgrant> Compare the exception on https://launchpad.net/huh%3F and https://launchpad.dev/huh%3F
[00:01] <wgrant> https://dogfood.launchpad.net/huh%3F shows the correct behaviour
[00:01] <wgrant> qastaging is bad
[00:01] <wgrant> So something on the prod/qas frontend configs is molesting our URLs; there's no LP bug here.
[00:01] <sinzui> yes, jcsackett confirmed that qa and prodct beahve the same
[00:02] <wgrant> So I would suggest replacing that MP with an RT
[00:02] <wgrant> Who knows what else the frontends are doing :/
[00:02] <sinzui> and watch it for 5 years?
[00:03] <wgrant> Nah, I'll coerce APAC webops to give me the configs next week and then give them a diff :)
[00:03] <wgrant> Diffs are a good way to accelerate RTs
[00:03] <wgrant> I am glad it is reproducible on qastaging; that makes things much easier.
[00:04] <wgrant> Since there's no squid or haproxy, AIUI
[00:05] <StevenK> steven@undermined:~% wget -Sq https://qastaging.launchpad.net 2>&1 | grep X-Cache
[00:05] <StevenK>   X-Cache: HIT from arsenic.canonical.com
[00:05] <wgrant> Oh
[00:05] <wgrant> So *that's* what arsenic does...
[00:05] <wgrant> s/Oh/Oh god why/
[00:06]  * wgrant files the RT
[00:06] <StevenK> arsenic for staging too
[00:07] <wgrant> We may need to do the same tweak we did to get the restricted librarian working
[00:08] <wgrant>     # nocanon per RT#42560, woe with LP's handling of eg %2B
[00:08] <wgrant>     ProxyPass / balancer://launchpad-librarian-cluster/ nocanon
[00:08] <_mup_> Bug #42560: /var is mounted over /var/run and /var/lock <sysvinit (Ubuntu):Invalid> < https://launchpad.net/bugs/42560 >
[00:08] <wgrant> That shouldn't be it, since decoding the %3F is not a legal part of canonicalization, but it's possible.
[00:09] <wgrant> Whatever it is, either apache or squid is in the wrong here, not LP
[00:12] <wgrant> It looks like it's probably our squid config, but I don't think I have a copy.
[01:05]  * StevenK glares at DF
[01:06] <StevenK> With no builder how am I supposed to QA? :-(
[01:25] <wgrant> StevenK: DB hacking or qa-meh
[01:25] <StevenK> Yeah, qa-meh might be the way
[01:50] <StevenK> wgrant: I wonder if bug 834293 is fixed, we did a bunch of work on branch privacy
[01:50] <_mup_> Bug #834293: Product:+code-index times out <timeout> <Launchpad itself:Triaged> < https://launchpad.net/bugs/834293 >
[02:07] <wgrant> StevenK: No
[02:07] <wgrant> We made it better, but not much better
[02:07]  * wgrant finds data
[02:08] <wgrant> https://devpad.canonical.com/~lpqateam/ppr/lpnet/latest-monthly-pageids.html
[02:08] <wgrant> 99% under 7.26s
[02:11]  * StevenK made the mistake of searching OOPS on neem with 'AssertionError'
[02:12] <StevenK> 1648 OOPSes later ...
[02:13] <StevenK> Almost all of them appear to be AssertionError: Bug #504291: Store left in a disconnected state.
[02:13] <wgrant> StevenK: Why?
[02:13] <_mup_> Bug #504291: DisconnectionErrors (already disconnected) happening again <fastdowntime> <lp-foundations> <oops> <Launchpad itself:Incomplete by stub> <Storm:Invalid> < https://launchpad.net/bugs/504291 >
[02:13] <wgrant> We know the precise circumstances around +edit-dependencies
[02:13] <wgrant> So we don't need to grep for it
[02:13] <StevenK> I wasn't
[02:13] <StevenK> That grep was for bug 808950
[02:13] <_mup_> Bug #808950: AssertionError: You exported name as an IChoice based on an SQLObjectVocabularyBase, you should use lazr.restful.fields.ReferenceChoice instead <api> <oops> <Launchpad itself:Triaged> < https://launchpad.net/bugs/808950 >
[02:14] <wgrant> Ah
[02:15] <StevenK> But doesn't seem to show up
[02:23] <wgrant> StevenK: Have you tried to reproduce it?
[02:25] <StevenK> I was looking for an OOPS as the first step.
[02:26] <wgrant> "AssertionError: You exported milestone_assignment as an IChoice based on an SQLObjectVocabularyBase, you should use lazr.restful.fields.ReferenceChoice instead." on Product:EntryResource:searchTasks
[02:26] <wgrant> is pretty clear
[02:26] <wgrant> And the fix is obvious
[02:28] <wgrant> (hint: grep the entire tree for the field name)
[02:31] <StevenK>         # The vocabulary should be HWBus; this is fixed in
[02:31] <StevenK>         # _schema_circular_imports to avoid circular imports.
[02:31] <StevenK> Didn't you kill that?
[02:31] <wgrant> _schema_circular_imports continues to live
[02:31] <wgrant> Its death will come only from lazr.restful's demise, or being split up into app-specific _schema_circular_importses.
[02:32] <StevenK> wgrant: Hmm, I don't get it. Since bugtasksearch has assignee as a Choice
[02:32] <wgrant> StevenK: Look at the other places that use it, and it should become clear
[02:33] <StevenK> Hah. Assignee is a Reference
[02:33] <StevenK> In bugtarget
[02:33] <wgrant> That's fine.
[02:33] <StevenK> But milestone_assignment isn't
[02:33] <wgrant> We only care about milestone_assignment, don't we?
[02:33] <StevenK> We shouldn't use copy_field, but use Reference?
[02:34] <wgrant> I'd look at how the other code that goes near that field uses it.
[02:35] <StevenK> wgrant: What other code? milestone_assignment turns up in two places.
[02:35] <wgrant> You're on the right track.
[02:36] <StevenK> That wasn't the answer I was expecting. :-)
[02:37] <StevenK> wgrant: Oh, it isn't used at all./
[02:38] <StevenK> search params never assigns it in __init__
[02:38] <wgrant> Bingo
[02:39] <StevenK> Should I drop it entirely then?
[02:39] <StevenK> It's obviously exported, but use of it will return 500s
[02:39] <wgrant> Right, it's probably in 1.0, but it's also likely that any attempt to use it crashes
[02:39] <wgrant> Check that, and if it always crashes then obliterate it
[02:39] <wgrant> If it doesn't always crash, think about it a big and then obliterate it anyway.
[02:40] <wgrant> bit
[02:41] <StevenK> Hah
[02:41] <StevenK> So it wants a milestone name ?
[02:41] <wgrant> I think it wants a milestone reference.
[02:41] <wgrant> Given that it's using the Milestone vocab
[02:42] <wgrant> But it's exported as a Choice, which means it wants an enum value
[02:42] <wgrant> Which is why it crashes
[02:42] <wgrant> Try giving it references and names and see if there's anything that doesn't OOPS
[02:44] <StevenK> OOPS-a8ab241f5057264be5073a00263b04fb and OOPS-2c4ba13f50161b4d3ae38ccb94059308
[02:49] <wgrant> Ah... ha...
[02:49] <wgrant> The archeology of this is interesting
[02:49] <wgrant> It actually dates back to batch edit functionality added in mid-2005.
[02:50] <wgrant> In r1860
[02:50] <wgrant> If milestone_assignment was set in search parameters, it looks like it set the milestone of the found bug tasks.
[02:51] <StevenK> HAHAHA
[02:51] <StevenK> It's only referenced in a doctest that has been disabled since 2005
[02:51] <wgrant> Ah, no, there was a separate batch assignment form on the search page, but it all used that same "search" schema
[02:51] <StevenK> # XXX Bjorn Tillenius 2005-08-01:
[02:51] <StevenK> # This test is disabled in wait for SQLObject being fixed to accept
[02:51] <StevenK> # both distinct=True and an orderBy argument.
[02:52] <wgrant> xx-bugattachments.txt is disabled?
[02:52] <StevenK> No, just the last test of it
[02:52] <wgrant> Ah
[02:52] <StevenK>   XXX print http(r"""
[02:52] <StevenK>   ... GET /bugs/fir...
[02:53] <StevenK> wgrant: What about name in that bug? Or is that long dead?
[02:54] <wgrant> StevenK: It may still exist, but the pageid is bad
[02:54] <wgrant> Perhaps search the apidoc for parameters named name
[02:54] <wgrant> 'cause the method mentioned in the bug doesn't have onje
[02:54] <wgrant> And I don't think it ever did
[02:55] <wgrant> Huh
[02:55] <wgrant> That code persisted until June 2006
[02:55] <wgrant> But I'm pretty sure the bulk edit form was long gone by then, or I'd remember.
[02:57]  * StevenK ignores name
[04:02] <StevenK> wallyworld__: Read https://code.launchpad.net/~stevenk/launchpad/obliterate-milestone_assignment/+merge/128158 and weep
[04:06]  * wallyworld__ reads
[04:08] <wallyworld__> there were some cobwebs there
[04:08] <StevenK> I think the cobwebs are covered in dust
[04:09] <StevenK> Maybe this branch will land now
[04:13] <StevenK> wallyworld__: Did you want to approve that MP, or are you afraid of the spiders that own said cobwebs?
[04:15] <wallyworld__> StevenK: i'll aprove it, i just thought you wanted me to read it
[04:16] <StevenK> wallyworld__: The reading was first, yeah
[04:16] <StevenK> wallyworld__: I was curious about your reaction before you reviewed it
[04:16] <wallyworld__> StevenK: so, you saying that if the api is used now, as it, it oopses?
[04:16] <wallyworld__> as is
[04:17] <StevenK> wallyworld__: searchTasks() works fine. If you pass in milestone_assignment as one of your arguments, you will get an OOPS.
[04:17] <wallyworld__> ok, so no harm in removing it then
[04:17] <StevenK> Right, and I doubt any one is using it
[04:17] <StevenK> If they are, they move from a 500 to what, 404 or a lazr.restful error?
[04:18] <wallyworld__> you may have won the prize for removing the oldest code
[04:18] <wallyworld__> 40x for sure, not sure what
[04:18] <wgrant> 400
[04:19] <wgrant> Well, actually, once the WADL updates launchpadlib will probably tell them they're wrong before even sending the request
[04:19] <wgrant> But still, if they were relying on getting a 500 from that then they're pretty strange :)
[04:20] <StevenK> Let's find out in about an hour
[04:20] <wgrant> Hm?
[04:20] <wgrant> Why an hour?
[04:20] <StevenK> buildbot and qas updating
[04:21] <wgrant> Ah
[04:21] <StevenK> Current run has 15 minutes to go
[04:21] <StevenK> Unless wallyworld__ breaks it again
[04:21] <wallyworld__> it was only once :-(
[04:21] <StevenK> Twice
[04:22] <wallyworld__> once
[04:22] <wallyworld__> the other was suprious
[04:22] <StevenK> Once this morning and the feature flag related changes a few days ago
[04:22] <wallyworld__> same old thing we'vebeen seeing lately
[04:22] <wallyworld__> i thought you meant today
[04:37] <StevenK> Why did we add rf-setup-certs to LP?
[04:37] <wallyworld__> curtis said to
[04:37] <StevenK> I thought it was supposed to go into lp-dev-utils ?
[04:37] <wallyworld__> oops, maybe, let me check
[04:37] <wallyworld__> StevenK: the email said utilities
[04:38] <StevenK> Hmmm
[04:38] <wallyworld__> i can move it
[04:38] <StevenK> wgrant: What do you think?
[04:39] <StevenK> I think it should move
[04:40] <wallyworld__> wgrant: StevenK: +expirable-bugs oops on a dsp. i can't see a link so it must have been via url hacking. i guess it should return a 404 instead of a 500? or did we want to implement expirable bugs on a dsp?
[04:40] <StevenK> wallyworld__: So the ZCML has +expirable-bugs on IBugTarget
[04:41] <StevenK> A DSP is a bug target, but it doesn't support it
[04:41] <wallyworld__> ah. but there's no link on the dsp bugs page
[04:41] <StevenK> Curtis and William are of the opinion that it should support it
[04:41] <wallyworld__> ok, will look at that, thanks
[04:41] <wallyworld__> and then we can add the link to the page
[04:43] <wgrant> wallyworld__: I'm not really of the opinion that it should support it
[04:43] <StevenK> wgrant: Do you think Colin's work is far enough long to close bug 556839?
[04:43] <wgrant> I'm of the opinion that it might be easier to fix it to support it than it is to remove the page
[04:43] <wgrant> Given it's registered for IBugTarget
[04:43] <wgrant> StevenK: No
[04:43] <StevenK> We don't use async by default?
[04:43] <wgrant> wallyworld__: I'd put the cert gen script in lp-dev-utils, I think
[04:43] <wgrant> As StevenK suggests
[04:44] <wallyworld__> wgrant: why wouldn't we want to find expirable bugs on a dsp?
[04:44] <wgrant> wallyworld__: 'cause even Distribution:+expirable-bugs had only 136 hits last month
[04:45] <StevenK> Hah
[04:45] <StevenK> And how many of those were Google?
[04:45] <wallyworld__> hmmm.
[04:45] <wgrant> Most were probably search engines, yeah
[04:45] <wallyworld__> maybe we want to redo the zcml then to stop lying?
[04:45] <wgrant> +expirable-bugs was mostly introduced to show what would happen when expiration was turned on
[04:46] <wgrant> wallyworld__: Right, it's possibly best to just register it on IProduct and IDistribution
[04:46] <wgrant> Not sure if IProductSeries or IDistroSeries or IProject have it linked
[04:46] <wallyworld__> ok, i'll check that out. i think that's the better solution
[04:47] <wallyworld__> rather than doing something no one will use
[04:47] <wgrant> IProductSeries and IDistroSeries have about as many hits as I'd expect from Google
[04:47] <wgrant> But it's difficult to say
[04:47] <wgrant> wallyworld__: Right
[04:47]  * wallyworld__ first gets out the hedge trimmer
[04:47] <wgrant> In some situations like this it's a one-liner to fix it, so it's easier to just make it work
[04:48] <wgrant> But this is not one of them
[04:48] <wallyworld__> yeah, dicking eith _getTargetJoinAndClause() for dsp would be messy
[04:49] <StevenK> wgrant: So, for bug 1050191, I agree with Curtis. If it was in +junk first, we don't care.
[04:49] <_mup_> Bug #1050191: allocate-revision-karma.py is too slow to complete <branches> <karma> <lp-code> <oops> <Launchpad itself:Triaged> < https://launchpad.net/bugs/1050191 >
[04:49] <wgrant> StevenK: It's on my chopping block for the next few days
[04:49] <wgrant> As it's directly implicated in the BranchRevision drama
[04:49] <StevenK> Right
[04:49] <StevenK> I'll leave it alone then
[04:49] <wgrant> Fixing it is probably a prereq, but in which way I'm not sure
[04:49] <wgrant> Right :)
[04:50] <StevenK> Is mawson back to crying about your queries?
[04:50] <wgrant> No
[04:50] <wgrant> I have the data I need for now
[04:50] <wgrant> You can molest mawson if you so desire
[04:51] <StevenK> I have no need to, I was curious.
[04:51] <wgrant> Oh right, you qa-meh'd the PCJ thing
[04:51] <StevenK> I did, yes.
[04:51] <StevenK> Bug 1031751 is interesting. I've seen a test fail in that way too
[04:51] <_mup_> Bug #1031751: KeyError: 'primary_vars'  raised setting branch for a project <oops> <Launchpad itself:Triaged> < https://launchpad.net/bugs/1031751 >
[04:52] <wgrant> Right, some of Orange's work triggered that a week or so ago
[04:52] <wgrant> An unrelated cause, but similar exception
[04:52] <StevenK> Yeah. I'm not sure about the cause for the bug
[04:54] <StevenK> Almost at 45 revisions needing deployment
[04:54] <wgrant> StevenK: I suspect a branch was being created with a private team as the registrant
[04:55] <wgrant> StevenK: Perhaps registering a codeimport
[04:55] <wgrant> But the OOPS is gone and the traceback severely truncated
[04:55] <wgrant> Care you try what I suggested on qastaging?
[04:55] <StevenK> +new-import with a private team?
[04:56] <wgrant> That shouldn't set the registrant to the primary team, but it might
[04:56] <wgrant> So it's worth a try
[04:57] <StevenK> PrivatePersonLinkageError: Cannot link person (name=rhinos, visibility=PRIVATE) to <CodeImport for ~rhinos/launchpad/test-import> (name=None)<br />
[04:59] <wgrant> Indeed
[04:59] <wgrant> I can't see an obvious way to set the registrant to a private team
[04:59] <wgrant> And you can't log in as a team any more, so that won't work...
[05:00] <wgrant> Oh, hmmm
[05:02] <wgrant> That OOPS would make it obvious :(
[05:23] <lifeless> .oOo.
[06:01] <wgrant> StevenK: Ah, it would have helped if I'd read the summary
[06:02] <wgrant> OOPS-07a7ee485f0ae949f3e103cc1db1c082
[06:04] <StevenK> Nice.
[06:04] <StevenK> What was the cause, then?
[06:10] <StevenK> Hmmmm, I think I get it. Creating an import for a series owned by a private team
[06:11] <lifeless> is sso glitching
[06:11] <lifeless> I'm having trouble logging into oops.c.c
[06:12] <wgrant> lifeless: It's working for me
[06:13] <lifeless> I'm getting The connection was reset
[06:13] <lifeless> on
[06:13] <lifeless> https://oops.canonical.com/openid/+return?janrain_nonce= ...
[06:13] <wgrant> StevenK:                     code_import = getUtility(ICodeImportSet).new(
[06:13] <wgrant>                         registrant=branch_owner,
[06:13] <wgrant> From ProductSeriesSetBranchView.update_action
[06:15] <StevenK> wgrant: So we should croak in validate if branch_owner is private?
[06:16] <wgrant> StevenK: No
[06:16] <wgrant> You should specify the registrant
[06:16] <StevenK> Oh, registrant=self.user ?
[06:17] <wgrant> Yeah
[06:17] <StevenK> wgrant: But I thought the form was asking who should own the branch?
[06:17] <StevenK> So isn't that ignoring them ...
[06:17] <wgrant> own != register
[06:17] <wgrant> So owner != registrant
[06:18] <wgrant> I think you'll find that all the other branch creation callsites use the user as the registrant, with the provided owner as the owner.
[06:18] <wgrant> That's certainly the intent.
[06:19] <wgrant> I suspect that Registry got confused when producing this view
[06:19] <StevenK> Right
[06:19] <StevenK> Ugh, all of the tests for it are in doctests
[06:31] <StevenK>  I chose SHA-512 because everyone knows it's 512 times more secure than SHA-1.
[06:31] <StevenK> — Rusty Russell
[06:31] <wgrant> :)
[06:35] <StevenK>         obj_info["primary_vars"])
[06:35] <StevenK>     KeyError: 'primary_vars'
[06:35] <StevenK> Fantastic
[06:36] <wgrant> In a test?
[06:36] <wgrant> I wouldn't have a test for this issue directly.
[06:36] <wgrant> Rather amend an existing test to check that the registrant is the user, not the owner
[06:37] <wgrant> Making the branch approximately -1/+2
[06:39] <StevenK> But I just wrote one :-(
[06:48] <wgrant> StevenK: It may be useful for checking that the issue is really gone, but it's not something that's worth the test suite time and LoC to keep forever
[06:56] <StevenK> Raaaargh
[06:56] <StevenK> This entire test uses the product.owner as the registrant as well as the logged in the user
[06:57] <wgrant> Change one of them to be the other, I guess
[06:57] <StevenK> Changing the whole test to make a driver and set them as the owner of the series has lots of ('Invalid value', InvalidValue("token u'person-name-100001' not found in vocabulary"))
[06:57] <wgrant> StevenK: Ensure that the user is a member of the team
[06:57] <StevenK> What team
[06:57] <StevenK> ?
[06:58] <wgrant> You can only create a branch owned by yourself or a team in which you participate
[06:58] <wgrant> So the owner has to be a superteam of the user
[07:04] <StevenK> Right, large diff
[07:20] <StevenK> wgrant: Did you want to review?
[07:20] <wgrant> Sure
[07:21] <StevenK> wgrant: https://code.launchpad.net/~stevenk/launchpad/no-private-registrant-setbranch/+merge/128173
[07:26] <jpds> StevenK: Do you use ROT26 from time to time?
[07:27] <StevenK> ROT26 is the alphabet?
[07:43] <adeuring> good morning
[10:50] <rick_h_> morning
[10:54] <czajkowski> rick_h_: hey there
[10:54] <czajkowski> you're on early
[10:55] <rick_h_> czajkowski: trying to get back on time
[10:56] <czajkowski> rick_h_: can you pop into #lp please if you're free?
[11:00] <rick_h_> adeuring: ping, can you help czajkowski debug a blueprint issue? https://oops.canonical.com/?oopsid=OOPS-51c8161b2e479d7ed62ba67c1000bd19
[11:00]  * adeuring is looking
[11:01] <rick_h_> adeuring: looks like a user hit a forbidden setting it to embargoed or something.
[11:01] <adeuring> 383264
[11:04] <rick_h_> adeuring: ? typo'd bug number or something?
[11:06] <adeuring> rick_h_: PEBCAK: I tend to forget to click into a wondow before typing something. I this I wanted to add a 2-fact auth number into a browser window, while irc IRC window still had the focus...
[11:06] <rick_h_> adeuring: ah gotcha cool
[11:07] <rick_h_> thanks for looking at the oops
[11:41] <adeuring> rick_h_: https://bugs.launchpad.net/launchpad/+bug/1062207/comments/1
[11:41] <_mup_> Bug #1062207: Unable to raise blueprint <Launchpad itself:New> < https://launchpad.net/bugs/1062207 >
[13:22] <rick_h_> abentley: I missed you yesterday about setting the field value = PUBLIC
[13:22] <rick_h_> abentley: that was my doing when I setup the UI because I needed to set a value to the form field so that choicepicker stuff would pick it up
[13:22] <rick_h_> now that the field exists, model sets, etc it can probably just go away
[13:22] <deryck> adeuring, thanks for the review.  Agree on both counts.  We can hold the individual adapters until after alpha though, I think.
[13:23] <adeuring> deryck: right
[13:23] <abentley> rick_h_: I've removed it, and there seem to be no ill effects.
[13:23] <rick_h_> abentley: right
[13:23] <rick_h_> and the IProductSet checks were because there were tests that hit that View that weren't of that interface and weren't getting information_type added onto it
[13:24] <rick_h_> abentley: I had talked to deryck about that one when I thit it
[13:24] <abentley> rick_h_: Strange.  We don't seem to have any tests like that now.
[13:25] <rick_h_> abentley: it was something I hit. I had a chat with deryck about it asking if there was a better way than the interface checks
[13:26] <rick_h_> abentley: ProjectGroup perhaps gets hit in there?
[13:26] <abentley> rick_h_: I don't understand.
[13:28] <rick_h_> abentley: I'll bring it up on the call in a sec
[14:06] <abentley> After 3 years, I think I'm starting to understand buildbot's waterfall display.
[14:13] <jelmer> abentley: lol
[14:14] <abentley> jelmer: It's funny 'cause it's true.
[14:39]  * deryck switches work locations, back online shortly
[15:10] <sinzui> adeuring, bac, abentley: do either of you have time to review https://code.launchpad.net/~sinzui/launchpad/contact-new-maintainer/+merge/128273
[15:10] <adeuring> sinzui: i'll look
[15:24] <adeuring> sinzui: if the maintainer is a single person, not a team, user_address in LicenseNotification.send(), while it is a list of strings if the maintainer is a team. shouldn't a one-element list be used for "person is maintainer" case too?
[15:26] <adeuring> sinzui: never mind, i see now taht a single address worked before
[15:27] <sinzui> adeuring, indeed that is confusing. I had to read the code of our send mail helper to see that it would work
[15:29] <adeuring> sinzui: right, I an often a bit worried when a function(method argument can have different types. ANyway, r=me
[15:29] <sinzui> thank you adeuring
[15:36] <rick_h_> adeuring: branch for you if you get a sec, I noted a 'known issue' for the backend stuff that needs updating will be coming in a second branch. https://code.launchpad.net/~rharding/launchpad/edit_product_info_type/+merge/128081
[15:36] <adeuring> rick_h_: I'll look
[15:36] <abentley> adeuring: Do we have an equivalent for get_specification_privacy_filter that works for product listings?
[15:37] <adeuring> abentley: not yet...
[16:01] <adeuring> rick_h_: r=me
[16:07] <rick_h_> adeuring: ty much
[16:56] <deryck> rick_h_, abentley -- I'm going to have to leave here shortly, a little earlier than expected.
[16:56] <deryck> rick_h_, abentley -- but I'll obviously be around tonight and tomorrow as I finish tests and get my last branch landed.
[17:20] <rick_h_> deryck: rgr
[19:34] <abentley> rick_h_: I'm having trouble with a DB query-- getting duplicate results back.  Can you have a look at it with me?
[19:34] <rick_h_> abentley: sure thing
[19:35] <abentley> rick_h_: let's hangout
[19:35] <rick_h_> abentley: rgr
[19:59] <rick_h_> abentley or bac if you're still around. Would appreciate a review of https://code.launchpad.net/~rharding/launchpad/store_edit_product_info_type/+merge/128288
[19:59] <abentley> rick_h_: looking.
[19:59] <rick_h_> abentley: ty much
[20:04] <abentley> rick_h_: Where is _setLicense being invoked?
[20:05] <rick_h_> abentley: it's set by the ProductEditView when all the fields are updated.
[20:05] <rick_h_> abentley: there's an assumption there because changing the information_type changes the license I guess...
[20:06] <abentley> rick_h_: I think this change leaves a hole in the validation, because it allows information_type to change without setLicense being invoked.
[20:06] <rick_h_> abentley: yea, right
[20:07] <abentley> rick_h_: Can we do setLicense first?  Or add the subscription in _set_information_type?
[20:09] <rick_h_> abentley: thinking, really hate to call setLicense from set_information_type
[20:10] <abentley> rick_h_: Not set_license, but adding the subscription.
[20:10] <rick_h_> so maybe the best thing is to try to pull out the block that does the commerical sub generation and share it between teh two
[20:12] <rick_h_> what about a check in set_information_type that if the information_type is EMBARGOED/PROPRIETARY it sets the license manually there, overrides so that it makes sure it's getting the OTHER_PROPRIETARY value
[20:12] <abentley> rick_h_: That would make sense.  Either the license or the information_type could be seen as proprietary intent.
[20:12] <rick_h_> yea, it's just more a functino of license so trying to think of a good way to keep it there
[20:12] <abentley> rick_h_: r16102 provides make_product_form which should simplify your code.
[20:12] <rick_h_> the root issue is you can set the information type, and the license might not kick in.
[20:13] <rick_h_> abentley: cool, thanks for the heads up on that.
[20:14] <rick_h_> abentley: but can the license field ever not be supplied? It's a required field of data
[20:15] <abentley> rick_h_: The view code should never be responsible for the sanity of the data.  Especially given we have a web service API.
[20:16] <rick_h_> abentley: yea, sorry I thought it was required in the model via the validate method, but that's just worried about resetting the license review
[20:21] <abentley> rick_h_: So, I think the subscription is the key thing.  The license doesn't matter for information types.  A product could have an open source license, but not be announced yet.  Which is fine, as long as they're paying for the right to secrecy.
[20:22] <rick_h_> abentley: yea, so I'll pull that out into a new create_complimentary_subscription method and call from both places. I need to make sure it'll be safe to run twice
[20:22] <rick_h_> since it could get called via both the license setter and the information type setter
[20:23] <abentley> rick_h_: Sounds good.  We seem to be calling such methods "ensure_FOO", rather than create_ or make_.
[20:25] <rick_h_> abentley: not sure ensure fits here like it does fixing policies
[20:25] <rick_h_> it's just creating an initial compl. commercial sub
[20:28] <abentley> rick_h_: It's like it in the sense that it doesn't try to create things that already exist.
[20:32] <rick_h_> ok, fits my head strange but I can buy in :) Pushed an update to the MP when it processes
[20:33] <rick_h_> bah, I need to update the test though to verify the subscription exists as well
[20:37] <abentley> rick_h_: You don't need line 116 because it duplicates line 148.
[20:38] <rick_h_> abentley: ah true thanks.
[20:41] <abentley> rick_h_: I would do http://pastebin.ubuntu.com/1262684/ but I believe your code's equivalent.
[20:43] <rick_h_> abentley: thanks for the suggestino
[20:45] <abentley> rick_h_: r=me either way, but I'm surprised you don't have to change the view in order to solve the bug.
[20:46] <rick_h_> abentley: the view was in the first branch to get the field to show up
[20:46] <rick_h_> abentley: it's listed as a pre-req to this MP
[20:46] <abentley> rick_h_: Gotcha.
[20:47] <rick_h_> thanks for the late day review abentley
[20:47] <abentley> rick_h_: np
[20:47] <abentley> rick_h_: still before my EOD.
[20:48] <rick_h_> still, late Friday bonus reviews yay ...not :)
[20:54] <abentley> rick_h_: So thanks for the advice on debugging the privacy filter.  It turned out that the And() needed to be in a sub-select, because that Product._information_type == InformationType.PUBLIC evaluates true for most rows.
[21:00] <rick_h_> abentley: cool, glad it worked out. Is that grantee thing still an issue or was that nothing?
[21:03] <abentley> rick_h_: The grantee thing was not really part of it.  It was just generating rows where AccessPolicyGrantFlat.grantee_id != TeamParticipation.teamID but Product._information_type == PUBLIC, so such rows were being yielded in the result.


[11:54] <tony-smlr> We are Live: SMLR E213/14/15  Video:  Video http://www.youtube.com/c/SmlrUs/live Audio: http://www.podcastdetroit.com/how-to-listen/listen-to-studio-3/
[13:19] <cmaloney> morning


[13:42] <IamTrying> I have this Beagle Board which has a micro flash card. Now how can i install Ubuntu 13. or 12. on it please?
[13:51] <IamTrying> Hello? What happen to the Ubuntu ARM community. Dead, Silent !!!!!! getting worried
[13:53] <ogra_> most efforts moved to #ubuntu-touch ...
[13:53] <ogra_> (beyond the highperformance arm clusetr stuff ... )
[13:53] <ogra_> *cluster
[13:54] <IamTrying> OK - i am leaving ubuntu-arm then ogra_ , no community no fun man its like walking alone in desert.
[13:54] <IamTrying> Thank you ogra_
[13:54] <ogra_> what kind of beagleboard is that ? there are installer images for the XM and the C series iirc
[13:54] <ogra_> we never really officially dd omap3 stuff though
[13:55] <IamTrying> ogra_, http://beagleboard.org/Products/BeagleBone%20Black  - i bought this just to install Ubuntu on it
[13:55] <IamTrying> But i have no idea how to install it
[13:55] <ogra_> yeah, then talk to the beagle community in #beagle ...
[13:55] <IamTrying> OK - Thank you ogra_
[13:55] <ogra_> there are no ubuntu images for anything after the XM
[13:55] <k1l> IamTrying: see http://elinux.org/BeagleBoardUbuntu
[13:56] <ogra_> yeah, robert nelson always provided homebewed images
[13:56] <ogra_> brewed
[13:56] <IamTrying> WOW - k1l Ubuntu 13.10 ???
[13:56] <IamTrying> Man i love it, thank you
[13:58] <k1l> IamTrying: and be aware, that the arm community is not that beginner community like the desktop stuff is. you will need to read and learn alot of things and you will not get a hand by hand guide all the time. just to warn you so you are not disappointed that fast
[14:03] <IamTrying> OK - Guru k1l
[18:36] <TooLmaN> Hi guys.  I'm looking for resources for making an ARM Ubuntu image for older Wyse thin clients.  Can anyone point me in the right direction?  Thanks in advance
[18:37] <ogra_> you could start from ubuntu-core ...
[19:12] <TooLmaN> ogra:  I'll check out core.  These TCs are 1GB CPU, 1GB RAM, 1GB flash.  I have PuppyLinux running on it but I want Ubuntu.  Thanks
[19:12] <ogra_> http://wiki.ubuntu.com/Core


[16:31] <tyhicks> #startmeeting
[16:31] <meetingology> Meeting started Mon Sep 11 16:31:46 2017 UTC.  The chair is tyhicks. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[16:31] <meetingology> Available commands: action commands idea info link nick
[16:31] <mdeslaur> \o
[16:31] <tyhicks> The meeting agenda can be found at:
[16:31] <tyhicks> [LINK] https://wiki.ubuntu.com/SecurityTeam/Meeting
[16:32] <tyhicks> [TOPIC] Announcements
[16:32] <tyhicks> Gianfranco Costamagna provided a debdiff for xenial for check-all-the-things (LP: #1597245)
[16:32] <tyhicks> Simon Quigley (tsimonq2) provided a debdiff for xenial for karchive (LP: #1712948)
[16:32] <tyhicks> James Cowgill (jcowgill) provided debdiffs for xenial and zesty for mbedtls (LP: #1714640)
[16:32] <tyhicks> Thank you for your assistance in keeping Ubuntu users secure! :)
[16:32] <tyhicks> [TOPIC] Weekly stand-up report
[16:32] <tyhicks> jdstrand: you're up
[16:32] <jdstrand> This week I plan to work on:
[16:32] <jdstrand> * updating the review tools for new license yaml, better error reporting and a few smaller fixes
[16:32] <jdstrand> * continuing reviews in support of snapd layouts feature (PR 3621)
[16:32] <jdstrand> * investigate device cgroup issues in snapd
[16:32] <jdstrand> * miscellaneous policy updates for snapd as have time
[16:32] <jdstrand> * start next steps of my parts of uid/gid work in snapd as have time
[16:32] <jdstrand> that's it from me. mdeslaur, you're up
[16:33] <mdeslaur> I'm just back from vacation, so I'll be catching up on email
[16:33] <mdeslaur> I think I have qemu packages to publish tomorow
[16:33] <mdeslaur> and I'll be going down the list after that
[16:33] <mdeslaur> that's it, sbeattie, you're up
[16:33] <sbeattie> I'm in the happy place this week.
[16:33] <sbeattie> I have a couple of embargoed issues I'm looking at
[16:34] <sbeattie> I'm also working on a libxml2 update
[16:35] <sbeattie> I'll have the usual kernel triage bits to go through.
[16:35] <sbeattie> I have some apparmor stuff to review, and I think a couple of qrt tasks to investigate
[16:36] <sbeattie> that's probably it for me.
[16:36] <sbeattie> tyhicks: you're up
[16:36] <tyhicks> I'm in the happy place this week
[16:37] <tyhicks> I'm here for the first half of the week and then I'll be traveling to and attending the Linux Security Summit in the last half
[16:37] <tyhicks> I'll be working on packaging/testing fscrypt 0.2.1
[16:37] <tyhicks> I'll test the latest LSM stacking patches prior to LSS
[16:38] <tyhicks> (I quickly reviewed the patches a week or two ago)
[16:38] <jjohansen> tyhicks: I have a tree with them on artful 4.13 I'll point you at
[16:38] <tyhicks> and I'll see if I can fit any libseccomp backports/uploads in if the PR gets an ack
[16:38] <tyhicks> that's it for me
[16:38] <tyhicks> jjohansen: thanks, that'll be helpful
[16:38] <tyhicks> jjohansen: you're up
[16:39] <jjohansen> I am at Linux plumbers and the linux security conference this week, today I am prepping for presentations and discussions around apparmor, LSM stacking, and LSM namespacing
[16:40] <ratliff> if you want any reviewers, please let us know, jjohansen
[16:40] <jjohansen> that is it for me I haven't seen sarnold so back to you tyhicks
[16:40] <jjohansen> ratliff: ah, thanks that would be good
[16:42] <tyhicks> chrisccoulson: are you back around?
[16:42] <sarnold> tyhicks: i'm finally in :)
[16:42] <tyhicks> sarnold: hey - go ahead
[16:42] <sarnold> I'm on bug triage this week
[16:43] <sarnold> i'm helping jj with apparmor patch reviews as he generates them
[16:43] <sarnold> working on nghttp2 mir ATM and moving on to the python elftools one once that's finished
[16:44] <sarnold> that'll probably account for the week, so token back to chrisccoulson or ratliff?
[16:44] <ratliff> I'll give chrisccoulson a minute to pipe up, then I'll go
[16:45] <tyhicks> he had to step away for an errand and was iffy on returning in time
[16:45] <tyhicks> you can go ahead
[16:45] <ratliff> I'm on community this week.
[16:45] <ratliff> I have a number of organizational and technical documentation tasks to do.
[16:46] <ratliff> I also need to start doing sprint prep for the two upcoming sprints.
[16:46] <ratliff> leosilva: on to you
[16:46] <leosilva> I'm in CVE triage this week.
[16:47] <leosilva> Soon I finish it for today I'm planning to get gdk-pixbuf and retest the issues to see if it can or not patched
[16:47] <leosilva> also planning to hunting more pkgs to update.
[16:47] <leosilva> that is for me.
[16:47] <leosilva> tyhicks: it's back to you
[16:48] <tyhicks> thanks
[16:48] <tyhicks> [TOPIC] Highlighted packages
[16:48] <tyhicks> The Ubuntu Security team will highlight some community-supported packages that might be good candidates for updating and or triaging. If you would like to help Ubuntu and not sure where to start, this is a great way to do so.
[16:48] <tyhicks> See https://wiki.ubuntu.com/SecurityTeam/UpdateProcedures for details and if you have any questions, feel free to ask in #ubuntu-security. To find out other ways of helping out, please see https://wiki.ubuntu.com/SecurityTeam/GettingInvolved.
[16:48] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/python-jwcrypto.html
[16:48] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/libid3tag.html
[16:48] <tyhicks> [TOPIC] Miscellaneous and Questions
[16:48] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/atheme-services.html
[16:48] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/golang-github-appc-docker2aci.html
[16:48] <tyhicks> http://people.canonical.com/~ubuntu-security/cve/pkg/mxml.html
[16:48] <tyhicks> Does anyone have any other questions or items to discuss?
[16:49] <tyhicks> I'll give a quick summary of Chris' plans for the week and then we'll end the meeting:
[16:49] <tyhicks>    * finish updating rustc to 1.19
[16:49] <tyhicks>    * start on updating rustc to 1.20
[16:49] <tyhicks>    * thunderbird update
[16:49] <tyhicks>    * sponsor chromium-browser update
[16:49] <tyhicks>    * fix bugs for Firefox 56
[16:49] <tyhicks>     * menubar
[16:49] <tyhicks>     * FTBFS on Trusty
[16:50] <tyhicks>     * armhf issue
[16:50] <tyhicks> jdstrand, mdeslaur, sbeattie, jjohansen, sarnold, ratliff, leosilva: Thanks!
[16:50] <ratliff> thank you, tyhicks!
[16:50] <tyhicks> #endmeeting
[16:50] <meetingology> Meeting ended Mon Sep 11 16:50:17 2017 UTC.
[16:50] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-09-11-16.31.moin.txt
[16:50] <jdstrand> tyhicks: thanks!
[16:50] <leosilva> tks tyhicks !
[16:50] <mdeslaur> thanks tyhicks
[16:50] <sarnold> thanks tyhicks!
[16:50] <jjohansen> thanks tyhicks
[18:49] <ddstreet> 0
[18:50] <ddstreet>  typo
[19:01] <sil2100> o/
[19:01] <fossfreedom> hi sil2100
[19:02] <ddstreet> o/
[19:02] <sil2100> Hello dear applicants!
[19:02] <sil2100> I wonder if we'll get quorum
[19:02] <micahg> o/
[19:02] <jbicha> hi, I am a bit distracted today because of Irma but I'll see what I can do :)
[19:03] <bdmurray> o/
[19:03] <bdmurray> even if we don't get quorum we have some things to discuss
[19:03] <ddstreet> jbicha hope you're ok!  i'm in NC, and surprisingly it seems we'll miss the worst of it
[19:04] <jbicha> I'm south of Tampa and it seems we missed the worst of it too (except for the power outages)
[19:04] <sil2100> I guess we have quorum already
[19:04] <sil2100> Looks like we have 4 members present
[19:05] <sil2100> Who wants to chair?
[19:05] <micahg> well, we still need to certify the election results and have the TB do the same
[19:06] <bdmurray> So we need BenC?
[19:06] <micahg> yeah, would be good
[19:06] <BenC> I’m here
[19:06] <BenC> o/
[19:06] <sil2100> \o/
[19:07] <bdmurray> or rbasak
[19:07] <bdmurray> sil2100: Do you mind chairing?
[19:07] <sil2100> I could
[19:08] <sil2100> #startmeeting DMB
[19:08] <meetingology> Meeting started Mon Sep 11 19:08:10 2017 UTC.  The chair is sil2100. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[19:08] <meetingology> Available commands: action commands idea info link nick
[19:08] <sil2100> #topic Review of previous action items
[19:08] <sil2100> I guess all the action items are done
[19:08] <sil2100> Since the vote finished, we'd just need to announce the results + contact the TB
[19:08] <bdmurray> Should we talk about the vote now or during AOB?
[19:08] <sil2100> But that's a separate task
[19:09] <sil2100> Let's talk afterwards, since application handling I'd prefer prioritized
[19:09] <bdmurray> Okay.
[19:09] <sil2100> #topic SRU Developer applications
[19:10] <sil2100> #subtopic Dan Streetman
[19:10] <sil2100> ddstreet: o/ Could you introduce yourself?
[19:10] <ddstreet> hello o/
[19:10] <sil2100> https://wiki.ubuntu.com/ddstreet/UbuntuSRUDeveloperApplication <- application link
[19:10] <ddstreet> hi, i'm dan streetman, as indicated, and applying for the 'SRU developer' role
[19:10] <ddstreet> sil2100 thanks, that's my application link
[19:11] <ddstreet> i work closely with slashd, who is currently the only other SRU devel
[19:11] <ddstreet> any questions for me?
[19:12] <bdmurray> Look at the sponsorship miner I don't see very many SRU uploads. Maybe 8 is that right?
[19:12] <ddstreet> yes, not too many, around 8 is probably right
[19:13] <ddstreet> i have spent a lot of time working on kernel patches also
[19:13] <ddstreet> and my last upload, for pylint, was artful only, no SRU
[19:13] <bdmurray> That's interesting but I'm not certain its relevant to an SRU application.
[19:14] <ddstreet> no, kernel and devel uploads are not relevant
[19:14] <sil2100> ddstreet: a 'technical' question from my side - when submitting an SRU application, what info would you include in the Regression Potential field?
[19:15] <sil2100> What is the purpose of this field?
[19:15] <ddstreet> i would include any possible side-effects of the change
[19:16] <ddstreet> e.g. what area of the code does this change touch, and if that code area breaks, what would that look like?
[19:18] <sil2100> Thanks
[19:19] <ddstreet> an example of what i've put in regression potential before, from my last vlan sru: "Any modifications to ifupdown or the scripts it uses may cause wider problems with network configuration. Specifically, this could cause problems when using vlan interfaces, as it forces every vlan's raw device interface to be fully ifup'ed before the vlan interface can finish its ifup."
[19:19] <bdmurray> What prompted applying for SRU uploads today? Is not having access blocking your work even though your last SRU was in June?
[19:19] <sil2100> ddstreet: a more theoretical question - what do you think, does the lack of upload rights block your work? Will you do more uploads when having the permissions?
[19:20] <ddstreet> bdmurray mainly my application is so i can help move along sru applications into the queue to be reviewed
[19:20] <ddstreet> i.e., speed up sru's that are needed
[19:21] <ddstreet> sil2100 yes i will likely do more uploads, but probably i'll be uploading other's work
[19:21] <bdmurray> ddstreet: so it'd allow you to sponsor other SRUs?
[19:21] <ddstreet> yes
[19:21] <ddstreet> i do not think i will personally create more patches that i apply for sru's for, but i do think i will review and upload other people's sru's
[19:21] <ddstreet> obviously more than i do now, since i can't do that now ;-)
[19:22] <ddstreet> and of course, it will help me when i do have a sru to upload
[19:22] <ddstreet> personally-authored sru, that is
[19:23] <bdmurray> That's different than what *I'd* expected this application or other SRU developer applications to look like.
[19:23] <ddstreet> bdmurray what do you expect is the intention of people applying for SRU devel?
[19:23] <bdmurray> I'd expected applicants to uploading their own work not sponsoring stuff for others.
[19:23] <ddstreet> is that what you expect of core devs?
[19:23] <micahg> one of the for granting rights is significant and sustained uploads/contributions except in cases where that doesn't make sense (PPU for a mature package that needs very infrequent updates)
[19:23] <ddstreet> mainly upload their own patches?
[19:24] <micahg> *one of the criteria
[19:24] <bdmurray> ddstreet: How would you evaluate whether or not an upload is SRU ready?
[19:25] <ddstreet> bdmurray there's 2 parts to that: 1) technical change to whatever codebase it is, and 2) sru metadata like changelog format, version number, etc
[19:26] <ddstreet> for #1, the change depends on the package, and i would review the patch(es) and existing code to see how the code works, what the author is changing, if it makes sense and is done correctly, and mostly if it's upstream
[19:26] <ddstreet> if it's not accepted in the upstream code, that's a big red flag for deinal
[19:26] <ddstreet> assuming it's upstream, make sure it's in the devel release first
[19:26] <ddstreet> if upstream accepted it, and it's in devel, and the code looks good, then check #2
[19:27] <ddstreet> which involves making sure the changelog has no trailing whitespace, line length is right, includes LP: #NNN, right changelog text, author name/email
[19:27] <ddstreet> check the patch e.g. patch -p1, quilt import/push/refresh, builds ok, autpkgtest
[19:28] <ddstreet> version number is correct based on current version
[19:29] <ddstreet> rather a lot of meta-data checks (i've thought about adding a tool to ubuntu-dev-tools to automate some of that, like scripts/checkpatch.pl for the kernel)
[19:30] <ddstreet> any other q's for me?
[19:31] <sil2100> Any questions? Or should we proceed to voting?
[19:31] <bdmurray> I'm ready to vote.
[19:31] <sil2100> BenC? micahg?
[19:32] <micahg> ready
[19:32] <sil2100> I guess we're good then
[19:32] <sil2100> #vote Grant ddstreet SRU Developer
[19:32] <meetingology> Please vote on: Grant ddstreet SRU Developer
[19:32] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[19:34] <bdmurray> -1 I'd like to see more involvement in the SRU process before granting you upload rights.
[19:34] <meetingology> -1 I'd like to see more involvement in the SRU process before granting you upload rights. received from bdmurray
[19:34] <micahg> +0 , while the quality of work is good so far, it's a bit sporadic, also, I applaud your desire to sponsor uploads, but I don't feel that in and of itself is a reason to grant upload rights, I look forward to seeing you back soon with more SRUs completed when we can hopefully grant you SRU upload permissions
[19:34] <meetingology> +0 , while the quality of work is good so far, it's a bit sporadic, also, I applaud your desire to sponsor uploads, but I don't feel that in and of itself is a reason to grant upload rights, I look forward to seeing you back soon with more SRUs completed when we can hopefully grant you SRU upload permissions received from micahg
[19:34] <bdmurray> Perhaps one way to do that is looking at some things in the SRU queue and then getting an SRU team member endorsement.
[19:36] <sil2100> +0, all good skill-wise but I also think it's a bit too soon, certainly a passing vote after a short while of more uploads + endorsements
[19:36] <meetingology> +0, all good skill-wise but I also think it's a bit too soon, certainly a passing vote after a short while of more uploads + endorsements received from sil2100
[19:36] <ddstreet> bdmurray micahg sil2100 sounds good, i'm happy to reapply after adding some more sponsored sru uploads...you guys don't mind me bugging you to sponsor my uploads right? ;-)
[19:37] <sil2100> ddstreet: not at all! It would be a pleasure - I'd say keep up on uploading through sponsors and we'd gladly review you again in a month or so
[19:37] <sil2100> Or whenever you're ready
[19:37] <ddstreet> awesome.  thnx all
[19:38] <sil2100> ddstreet: thanks!
[19:38] <sil2100> #topic PPU Applications
[19:38] <sil2100> #subtopic David Mohammed (fossfreedom)
[19:38] <sil2100> fossfreedom: o/
[19:39] <fossfreedom> :)
[19:39] <sil2100> fossfreedom: could you introduce yourself? Since some of us might not know you yet!
[19:39] <sil2100> https://wiki.ubuntu.com/fossfreedom/UbuntuBudgieDevApplication <- application
[19:39] <fossfreedom> hi - my name is david mohammed - I am the project lead of ubuntu budgie
[19:39] <fossfreedom> I am applying for PPU for the packages listed in my application
[19:40] <fossfreedom> my work crosses both debian and ubuntu
[19:40] <fossfreedom> the packages I have either created myself and maintain
[19:40] <fossfreedom> or the package I have a direct interest due to Ubuntu Budgie
[19:41] <sil2100> Sorry for the interruption, but I just got reminded that we need to close the previous vote
[19:41] <sil2100> #endvote
[19:41] <meetingology> Voting ended on: Grant ddstreet SRU Developer
[19:41] <meetingology> Votes for:0 Votes against:1 Abstentions:2
[19:41] <meetingology> Motion denied
[19:41] <sil2100> Ok, please continue ;p
[19:41] <fossfreedom> ok - sorry - any Q's for me?
[19:42] <sil2100> I've sponsored some packages for you already and I remember not having any issues as to their contents, which is good
[19:42] <bdmurray> I only see one endorsement on your application, is there a reason for this?
[19:43] <jbicha> bdmurray: I see 4
[19:43] <sil2100> bdmurray: yeah, there's 4
[19:44] <jbicha> I strongly endorse his application. I haven't updated my endorsement since his last application in December
[19:45] <jbicha> I think LocutusOfBorg's endorsement might be old too?
[19:45] <bdmurray> Sorry I thought the rest were comments.
[19:46] <micahg> right ,just one new endorsement since December
[19:47] <sil2100> Well, it's all good
[19:48] <sil2100> fossfreedom: tell me, when would be the usual cut-off 'date' after which you cannot upload NEW packages (by new I mean not-existing in the Ubuntu archive yet)?
[19:49] <fossfreedom> freeze date - little late this cycle - just past in late august
[19:49] <fossfreedom> idea would be to work with debian preferably
[19:49] <sil2100> Which freeze that would be?
[19:49] <fossfreedom> but definitely a couple of months before hand
[19:50] <sil2100> Since there's a lot of different freezes in the archive ;)
[19:50] <fossfreedom> debian freeze
[19:50] <fossfreedom> the auto sync with debian to ubuntu
[19:52] <sil2100> And what would you do if Ubuntu is in Feature Freeze already and need such a brand new package released to Ubuntu?
[19:52] <fossfreedom> feature freeze is tied to debian freeze this cycle
[19:52] <sil2100> By need I mean, suddenly really need it for good reasons
[19:52] <fossfreedom> question very hard if it is really needed first of all
[19:52] <fossfreedom> usually not
[19:52] <fossfreedom> but if necessary FFE - feature freeze exception
[19:52] <sil2100> But let's assume it's really needed, can you still get it in?
[19:52] <sil2100> Yeah
[19:54] <sil2100> BenC, bdmurray, micahg: any questions?
[19:55] <bdmurray> Not from me.
[19:55] <micahg> fossfreedom: I seem to recall Budgie was mainly going through Debian and there were mostly syncs happening, did something change?
[19:56] <fossfreedom> in terms of budgie-desktop - upstream pull a rabbit out of their hat.  It came late this cycle
[19:56] <fossfreedom> debian also had lots of issues with the new queue
[19:56] <fossfreedom> so the sync would not occur before debian freeze
[19:57] <micahg> is Ubuntu the upstream for the budgie packages??
[19:57] <micahg> the ones not in Debian I mean
[19:57] <fossfreedom> upstream - budgie-desktop github.com/budgie-desktop/budgie-desktop
[19:57] <jbicha> in a way, I think Ubuntu is the upstream for the Debian packages too ;)
[19:58] <micahg> right, but what about packages like budgie-welcome, budgie-desktop-environment
[19:59] <fossfreedom> those two are specific to ubuntu - they are at the heart of ubuntu budgie.  They are written specifically for us and would not work with Debian
[20:01] <sil2100> Any other questions?
[20:01] <sil2100> I'm poking since we're again over our scheduled time here
[20:02] <BenC> I’m good
[20:02] <sil2100> micahg: you have any more questions?
[20:03] <sil2100> I assume not in this case, let's vote
[20:03] <sil2100> #vote Grant fossfreedom PPU permissions for the listed package set
[20:03] <meetingology> Please vote on: Grant fossfreedom PPU permissions for the listed package set
[20:03] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[20:04] <sil2100> Packageset list: budgie-desktop, budgie-desktop-environment, budgie-artwork, budgie-welcome, budgie-wallpapers, arc-theme, moka-icon-theme, faba-icon-theme, rhythmbox-plugin-alternative-toolbar, budgie-indicator-applet, slick-greeter and ubuntu-budgie-meta
[20:04] <sil2100> (so it's in the logs)
[20:04] <sil2100> +1
[20:04] <meetingology> +1 received from sil2100
[20:05] <bdmurray> +1
[20:05] <meetingology> +1 received from bdmurray
[20:07] <sil2100> BenC, micahg: ?
[20:08] <BenC> +1
[20:08] <meetingology> +1 received from BenC
[20:08] <micahg> +1
[20:08] <meetingology> +1 received from micahg
[20:09] <sil2100> #endvote
[20:09] <meetingology> Voting ended on: Grant fossfreedom PPU permissions for the listed package set
[20:09] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[20:09] <meetingology> Motion carried
[20:09] <sil2100> fossfreedom: congratulations!
[20:10] <fossfreedom> cheers all - much appreciated!
[20:10] <sil2100> Who will take care of creating the packageset etc.?
[20:11] <micahg> a personal package set might be useful,, needs to be a TB member to create, but then we can maintain
[20:13] <sil2100> Any volunteers to drive this? ;)
[20:13] <bdmurray> I think I'll be emailing them anyway re the election so could get it setup
[20:13] <sil2100> bdmurray: thanks!
[20:13] <sil2100> #action bdmurray to handle the PPU role for fossfreedom
[20:13] <meetingology> ACTION: bdmurray to handle the PPU role for fossfreedom
[20:14] <sil2100> #endvote
[20:14] <meetingology> No vote in progress
[20:14] <sil2100> Eh, stupid copy-paste
[20:14] <sil2100> #topic AOB
[20:15] <sil2100> bdmurray: ok, you wanted to discuss the vote results?
[20:15] <bdmurray> micahg: What did you mean by certify the election?
[20:15] <micahg> vote to acknowledge the results of the election
[20:15] <sil2100> The TB?
[20:15] <micahg> both
[20:15] <bdmurray> Why would I not vote +1?
[20:15] <micahg> it's usually a formality
[20:16] <sil2100> Is that always been like that?
[20:16] <micahg> yeah
[20:16] <bdmurray> Okay, just wondering.
[20:16] <micahg> it's just a safeguard
[20:16] <sil2100> So let's vote then
[20:16] <bdmurray> Guess what mine is!
[20:16] <sil2100> #vote Vote to acknowledge the results of the election
[20:16] <meetingology> Please vote on: Vote to acknowledge the results of the election
[20:16] <meetingology> Public votes can be registered by saying +1, +0 or -1 in channel, (for private voting, private message me with 'vote +1/-1/+0 #channelname)
[20:16] <sil2100> +1
[20:16] <meetingology> +1 received from sil2100
[20:16] <micahg> +1
[20:16] <meetingology> +1 received from micahg
[20:16] <bdmurray> +1
[20:16] <meetingology> +1 received from bdmurray
[20:17]  * sil2100 looks at BenC
[20:17] <sil2100> *stare*
[20:18] <sarnold> BenC: (some clients only highlight on the nick in the first token)
[20:19] <sil2100> micahg: hmm, but how is this vote counted then?
[20:19] <BenC> +1
[20:19] <meetingology> +1 received from BenC
[20:19] <sil2100> #endvote
[20:19] <meetingology> Voting ended on: Vote to acknowledge the results of the election
[20:19] <meetingology> Votes for:4 Votes against:0 Abstentions:0
[20:19] <meetingology> Motion carried
[20:19] <sil2100> BenC: thanks!
[20:19] <BenC> Sorry, I’m doing my best to stay focused for quorum
[20:20] <sil2100> micahg: since we don't actually need 4 + anyway, since there's only 5 people potentially that could vote
[20:20] <sil2100> So 3 + were anyway sufficient I suppose
[20:20] <sil2100> Anyway, all good
[20:20] <sil2100> Now just the TB and we can officially welcome jbicha and cyphermox at the DMB
[20:20] <sil2100> Ok, final thing from me
[20:21] <micahg> sil2100: I think we'd still need +4 since the board is 7 members
[20:21] <sil2100> BenC, micahg, bdmurray: there's an ongoing application of rbalint through e-mail
[20:21] <sil2100> micahg: yeah but how can we expect 7 peolpe to vote
[20:21] <micahg> right, I'll try to get to that later today
[20:21] <sil2100> micahg: since we're voting for the 2 people that we're missing
[20:21] <BenC> Me too
[20:21] <micahg> sil2100: we can't, but I don' t think that changes quorum
[20:21] <sil2100> micahg: this would be a bit absurd IMO
[20:21] <sil2100> But anyway
[20:22] <sil2100> Not a problem this time I guess!
[20:22] <sil2100> micahg, BenC: thanks!
[20:22] <micahg> IMHO it's the equivalent of 2 members on extended vacation
[20:22] <bdmurray> So two actions more for me?
[20:22] <bdmurray> email TB re election then announce the results?
[20:22] <sil2100> #action bdmurray to contact TB regarding the election
[20:22] <meetingology> ACTION: bdmurray to contact TB regarding the election
[20:23] <sil2100> bdmurray: if you want, we can share some of those tasks
[20:23] <sil2100> Want me to send out the result announcement?
[20:23] <bdmurray> sil2100: Sure, I'll let you know when I hear from the TB
[20:24] <LocutusO-> congrats! yes my advocacy was a little bit old, but it was still valid :)
[20:24] <sil2100> #action sil2100 to send out the results announcement after the TB decision is known
[20:24] <meetingology> ACTION: sil2100 to send out the results announcement after the TB decision is known
[20:25] <sil2100> Any other business?
[20:25] <sil2100> LocutusO-: ;)
[20:25] <bdmurray> Nope
[20:25] <sil2100> Ok, let's assume we're all good now
[20:25] <sil2100> o/
[20:25] <sil2100> #endmeeting
[20:25] <meetingology> Meeting ended Mon Sep 11 20:25:54 2017 UTC.
[20:25] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-meeting/2017/ubuntu-meeting.2017-09-11-19.08.moin.txt
[20:25] <sil2100> Thanks everyone!