[05:34] <swook> Has anyone managed to compile appmenu-gtk on Debian?
[08:03] <tsdgeos> hmmm
[08:04] <tsdgeos> what does this mean?
[08:04] <tsdgeos> model: previewData.infoMap["more-screenshots"] != null ? previewData.infoMap["more-screenshots"].value : [previewData.image]
[08:04] <tsdgeos> what is  [previewData.image] ?
[08:04] <Saviq> tsdgeos, it's an array with previewData.image in it
[08:04] <Saviq> tsdgeos, aka a stringlist
[08:05] <tsdgeos> oh
[08:05] <tsdgeos> right
[08:17] <Wellark> dednick: hi
[08:17] <Wellark> https://code.launchpad.net/~ubuntu-sdk-team/ubuntu-ui-toolkit/unity-theme-icon-provider/+merge/180805
[08:17] <Wellark> dednick: so, there are other changes in qmenumodel tree?
[08:17] <Wellark> could you merge them to that branch?
[08:18] <dednick> Wellark: hi. surecan/.
[08:19] <dednick> eh. stupid keyboard.
[08:19] <Wellark> dednick: do you have anything else I need to know about? :))
[08:19] <Wellark> I'm trying to get the theme icon loader forward
[08:20] <dednick> Wellark: only that it's currently set in qmenumodel. probably need to remove it at the same time?
[08:20] <Wellark> dednick: yeah.
[08:21]  * Wellark branches upstream qt..
[08:21] <Wellark> need to fix QIcon::fromTheme() .. ;(
[08:22] <Wellark> or strictly speaking.. I don't have to as I'm not needing it :P
[08:23] <mzanetti> Wellark: hi.
[08:23] <mzanetti> Wellark: I wrote a summary of what's left to do in your launcher-backend branch
[08:24] <Wellark> mzanetti: where is it?
[08:25] <mzanetti> https://code.launchpad.net/~kaijanmaki/unity8/launcher-backend/+merge/179663/comments/408616
[08:25] <mzanetti> Wellark: ^
[08:25] <Wellark> mzanetti: thanks!
[08:25] <Wellark> mzanetti: I have couple of things I need to discuss with you
[08:25] <Wellark> let me get the icon loader rolling just first
[08:47] <tsdgeos> hmmmm
[08:47] <mzanetti> hmmmm?
[08:47] <tsdgeos> after one hour of charging the nexus4 with the wall charger its still dead
[08:47] <mzanetti> tsdgeos: did you press the power buggon for like a minute?
[08:47] <mzanetti> button
[08:49] <didrocks> (while being plugged)
[08:49] <didrocks> and a real 60s :p
[08:51] <tsdgeos> yeah, just did
[08:51] <tsdgeos> no luck
[08:54] <Cimi> seb128, hey :)
[08:55] <tsdgeos> Saviq: do you think you'll have time to look at https://code.launchpad.net/~aacid/unity8/lvwph_weirdness2/+merge/180613 ?
[08:55] <Saviq> tsdgeos, yeah
[08:56] <tsdgeos> Saviq: do you know if that code for not using invalid filters/something in unity should be there already?
[08:56] <Saviq> tsdgeos, jenkins död, though :/
[08:56] <Saviq> tsdgeos, yes
[08:56] <tsdgeos> i think it is what's causing stuff like the jenkins fail i have
[08:56] <Saviq> tsdgeos, yes it was
[08:57] <tsdgeos> i..e the thing just vanishes
[08:57] <tsdgeos> Saviq: ah you mean jenins in general, not in this case, ok
[08:57] <Saviq> tsdgeos, yes
[08:57] <seb128> Cimi, hey
[09:00] <Cimi> seb128, I need wifi things n the wizard… which are your plans for that?
[09:04] <seb128> Cimi, as said last week, ted is working on it
[09:04] <Cimi> seb128, i'll wait for it
[09:04] <seb128> Cimi, the plan is to load the UI through unitymenumodel
[09:04] <Cimi> seb128, last question
[09:05] <Cimi> seb128, I need set the real name of the user
[09:05] <seb128> Cimi, the indicator is going to provide the list of aps over gmenumodel so indicators/settings should be able to load that through unitymenumodel easily
[09:05] <Cimi> (I think the username will be phablet maybe, but not the real name)
[09:07] <Cimi> seb128, so question is how would you do it? :)
[09:07] <Cimi> seb128, there is a console app, but maybe a library too
[09:07] <Cimi> command line is chfn
[09:11] <seb128> Cimi, yeah, seems like you need a cpp plugin for the wizard
[09:12] <Cimi> seb128, yep, but using that command line tool?
[09:12] <seb128> Cimi, let me look, my gut feeling says "use accountsservice for that"
[09:13] <Cimi> ok
[09:20] <seb128> Cimi, org.freedesktop.Accounts CreateUser()
[09:20] <Cimi> seb128, is there a plugin that already uses dubs?
[09:21] <Cimi> seb128, to have a base to work...
[09:21] <seb128> Cimi, or if the account exists already org.freedesktop.Accounts.User SetRealName()
[09:21] <seb128> Cimi, yes, background and power and datetime and system-updates
[09:41] <jamesh> sil2100: hi.  I noticed that https://bugs.launchpad.net/ubuntu/+bug/1212993 is marked fixed committed, but mediascanner doesn't show up in the archive yet.  What is its status?
[09:45] <sil2100> jamesh: I poked the guys now, it's in the NEW queue still
[09:45] <sil2100> jamesh: someone has to move it out of it ;/
[09:46] <jamesh> sil2100: thanks!
[10:05] <Wellark> dednick_: thanks for the merge!
[10:05] <dednick_> Wellark: no worries
[10:07] <Wellark> dednick_: now, can you fix QIcon::fromTheme() for me ;)
[10:07] <dednick_> Wellark: lol. doubtful
[10:08] <Wellark> blah.. I will do it myself then :)
[10:13] <dednick_> always a good way to get things done ;)
[10:14] <tsdgeos> woooo
[10:14] <tsdgeos> magic
[10:14] <tsdgeos> after hours of charging and pressing random buttons
[10:14] <tsdgeos> i've got the red light back
[10:15] <tsdgeos> the nexus4 may still be alive
[10:15] <nic-doffay> Guys, trying to pass Scope into the PageHeader from GenericScopeView.qml it's logging null though. Any ideas why? Just doing this from GenericScopeView.qml: https://pastebin.canonical.com/95998/
[10:16] <Saviq> nic-doffay, onScopeChanged: console.log(scope) ?
[10:17] <nic-doffay> Saviq, giving it a go now. I was only printing onCompleted
[10:17] <Saviq> nic-doffay, that might be too early indeed
[10:17] <nic-doffay> Saviq, looks good actually.
[10:17] <Saviq> good
[10:21] <mzanetti> Saviq: hmm... seems the fact that all our popover's text is white on white is an issue from the shell
[10:21] <Saviq> mzanetti, theme
[10:21] <mzanetti> Saviq: doesn't happen with "make trySomething"
[10:21] <Saviq> mzanetti, https://bugs.launchpad.net/ubuntu-ui-toolkit/+bug/1205094
[10:24] <nic-doffay> Saviq, upon accessing scope.filters I get this error: https://pastebin.canonical.com/95999/ Assuming it's something C++ side I'm not aware of.
[10:26] <Saviq> nic-doffay, indeed, it wasn't added to plugin.cpp
[10:26] <Saviq> nic-doffay, you need to qmlRegisterUncreatableType<Filters> for it
[10:26] <Saviq> nic-doffay, in plugins/Unity/plugin.cpp
[10:28] <nic-doffay> Saviq, should I prep another branch for that fix?
[10:28] <Saviq> nic-doffay, nah, will be fine in the same
[10:33] <Saviq> mzanetti, sorry, I seem to be really good at breaking things https://code.launchpad.net/~mzanetti/unity8/dnd-and-quicklists/+merge/176653/comments/408930
[10:33] <greyback> sil2100: ping
[10:33] <sil2100> greyback: pong!
[10:33] <greyback> sil2100: hey, tsdgeos is kindly working on some integration tests for unity-mir
[10:34] <sil2100> greyback: awesomeness!
[10:34] <greyback> sil2100: but we need to check where the tests are run. Are they executed on a actual phone device, or in a VM?
[10:34] <greyback> sil2100: are there examples of Mir integration tests we could use as reference?
[10:35] <dednick_> eh. my internet is fooked.
[10:38] <sil2100> greyback: hmm, sadly, we're running unity tests for mir integration ;)
[10:39] <sil2100> greyback: so, currently we're running desktop tests on the desktop machines
[10:40] <Wellark> Saviq: could you explain what is the X-Ubuntu-Touch key in .desktop files
[10:40] <Saviq> Wellark, it's there to say whether the app is supposed to show up for Touch or not
[10:41] <Saviq> Wellark, it's a temporary solution, for lack of a spec, TBH
[10:41] <Wellark> Saviq: in the app lense or something?
[10:41] <Saviq> Wellark, yes, in Installed category of Apps scope
[10:41] <greyback> sil2100: okay, so we'll have to target the same.
[10:41] <Wellark> Saviq: ok.
[10:58] <nic-doffay> Saviq, any idea what the combinedfilteroption.cpp is used for?
[10:59] <Saviq> nic-doffay, ugh it's still there?
[11:00] <nic-doffay> Saviq, no but it's still in the CMakeLists
[11:00] <Saviq> nic-doffay, right - should be dropped
[11:00] <nic-doffay> Saviq, combinedfilteroptions too?
[11:00] <Saviq> nic-doffay, yes, combined* is gone
[11:01] <nic-doffay> Saviq, genericlistmodel too?
[11:02] <Saviq> nic-doffay, I believe so, yes, failure on my part for not cleaning that up during review
[11:02] <nic-doffay> Seems like that was the last missing source file.
[11:05] <Saviq> nic-doffay, interesting how CMake went through it with no complaints..
[11:41] <tsdgeos> Saviq: do you know if we require extra entries in the desktop file?
[11:41] <Saviq> tsdgeos, what extra entries?
[11:42] <tsdgeos> i'm getting "not a valid desktop file, missing mandatory entries in the standard group header" for what to me seems a valid desktop file
[11:42] <Saviq> Wellark, ↑
[11:42] <tsdgeos> http://paste.kde.org/~tsdgeos/pd08f2e28/ is what i'm using
[11:43] <Saviq> tsdgeos, I think Description is mandatory, too
[11:43] <tsdgeos> not according to the spec
[11:43] <tsdgeos> actually not even Exec is mandatory
[11:44] <tsdgeos> http://standards.freedesktop.org/desktop-entry-spec/desktop-entry-spec-latest.html
[11:44] <Saviq> tsdgeos, right, Type and Name
[11:45] <tsdgeos> oh didn't realize the desktop reader code is in unity-mir
[11:45] <Saviq> tsdgeos, " The Exec key is required if DBusActivatable is not set to true. Even if DBusActivatable is true, Exec should be specified for compatibility with implementations that do not understand DBusActivatable. "
[11:45] <tsdgeos> i'll check the code later
[11:45] <tsdgeos> lunch!
[11:57] <mzanetti> Saviq: fixed your last findings
[11:57] <mzanetti> except one which I'm again quite sure its a but in ListView
[11:57] <mzanetti> bug
[12:00] <didrocks> mzanetti: Saviq: stupid QML question, I have http://paste.ubuntu.com/6002606/ (an icon, then a line with 2 texts and then a line with one text)
[12:01] <didrocks> this layout set the icon on the same "line" than the line with 2 text (the Row)
[12:01] <didrocks> any idea why and how to avoid that?
[12:04] <didrocks> I think it's the inner Label, I don't do the right way to align them (even if it visually works)
[12:05] <Wellark> tsdgeos, Saviq: ubuntuqt atm requires certain set of keys to be in the .desktop file or it refuses to load it
[12:06] <Wellark> and this set has nothing to do with fdo spec :)
[12:06] <mzanetti> didrocks: in Row {}, do: height: childrenRect.height
[12:07] <mzanetti> didrocks: in Row {}, do: height: childrenRect.height
[12:07] <didrocks> mzanetti: in fact, parent.anchors doesn't exist (a Row don't have anchors?)
[12:07] <didrocks> so parent.anchors.left is invalid
[12:07] <mhr3> saviq, are html tags in previews supposed to work in current pending image?
[12:08] <mhr3> cause they kinda don't
[12:08] <mzanetti> didrocks: and remove the anchors.left and anchors.right in your row
[12:08] <mzanetti> didrocks: this is conflicting as the row tries to position the labels and you're also doing that manually
[12:08] <mzanetti> which is what breaks the row and makes the height calculation fail
[12:09] <mzanetti> didrocks: ?
[12:09] <mzanetti> didrocks: well, this row doesn't have anchors, you haven't set any
[12:09] <mzanetti> didrocks: also, you shouldn't because you have the Row inside a Column which takes care about the positioning
[12:10] <didrocks> mzanetti: ok, I think I'm not in the right direction then :) I just want to have 2 labels in a row, one aligned left, another aligned right
[12:10] <didrocks> the Row {} doesn't seem to be the right container then
[12:10] <mzanetti> didrocks: remove the anchors from the labels
[12:10] <mzanetti> row is ok
[12:10] <didrocks> mzanetti: so, with that, I have foobar
[12:11] <didrocks> not "foo          bar"
[12:11] <mzanetti> didrocks: you can right-align the text in the second label
[12:11] <mzanetti> didrocks: and set the label's widths to parent.width/2
[12:12] <didrocks> mzanetti: ah ok, that's the right way to do it then? :)
[12:12] <mzanetti> didrocks: yes
[12:13] <mzanetti> didrocks: if you don't break the Row by manually setting anchors, it should also automatically fix the height problem you've seen
[12:16] <didrocks> mzanetti: so, this should have worked? http://paste.ubuntu.com/6002657/
[12:16] <mzanetti> didrocks: well, you have a Row. inside the row, the items are placed next to each other, from left to right
[12:17] <mzanetti> so if you want the second item to move more towards the right, you have to increase the first item's width, no?
[12:17] <didrocks> ok, so first label needs to be wider
[12:17] <mzanetti> didrocks: set both item's width to parent.widht/2 then the space will be distributed equally
[12:18] <didrocks> mzanetti: indeed, makes sense. I just need to find how to align the text label to the right (current method doesn't work)
[12:19] <mzanetti> didrocks: you could also do it with anchors like before, in that case wrap them in an Item instead of a Row. But I still think its better this way because in the end (when you want to make sure they don't overlap each other etc) it'll be less code with the row
[12:20] <didrocks> mzanetti: yeah, makes totally sense, I didn't see the Row being just a flow widget, but once that's in the mind, it's normal
[12:20] <mzanetti> didrocks: regarding the alignment: https://qt-project.org/doc/qt-5.0/qtquick/qml-qtquick2-text.html#horizontalAlignment-prop
[12:21] <didrocks> ah, AlignLeft
[12:21] <didrocks> or AlignRight in my case :)
[12:21] <mzanetti> right, but yes
[12:22] <didrocks> mzanetti: perfect! thanks a lot and sorry for the stupid questions, first real time in QML :)
[12:22] <mzanetti> hehe. no worries
[12:35]  * greyback using somebodies 30 inch screen in his workspace, is loving it
[12:42] <Saviq> mhr3, no, not released yet
[12:42] <Saviq> mhr3, qaternourly is (was?) blocked for us due to NEWing unity-mir
[12:43] <mzanetti> greyback: at nokia I had 2*24" screens next to each other... now I'm back to 15" notebook screen :D
[12:44] <greyback> mzanetti: yeah, that must've been nice
[12:46] <Saviq> kgunn, welcome back!
[12:46] <kgunn> Saviq: thanks!
[12:47] <mzanetti> hi kgunn
[12:48] <greyback> hey kgunn!
[12:48] <kgunn> hey guys o/
[12:49] <tsdgeos> Saviq: so we are requiring Name, Comment, Icon, Exec and X-Ubuntu-StageHint
[12:49] <tsdgeos> seems a bit excessive to me tbh
[12:50] <tsdgeos> greyback: there?
[12:50] <mzanetti> tsdgeos: not to forget X-Ubuntu-Touch
[12:50] <greyback> tsdgeos: yep
[12:50] <tsdgeos> mzanetti: not required in the unity-mir desktop parser
[12:51] <Saviq> tsdgeos, +1, X-StageHint should not be required, for one (default to Main)
[12:51] <mzanetti> tsdgeos: altough I'm not sure if the X-Ubuntu-StageHint is still there. It seems to have disappeared from all our app's desktop files
[12:51] <tsdgeos> mzanetti: the ones above are required and simply ignores the .desktop file if not there
[12:51] <greyback> tsdgeos: I wouldn't waste much time fixing it up, Wellark will have a desktop file parsing library ready soon
[12:51] <Saviq> tsdgeos, Comment is probably excessive, too
[12:51] <tsdgeos> greyback: ah it's not that that i wanted you
[12:51] <tsdgeos> greyback: it was about how to stop a QMirServer
[12:51] <kgunn> mzanetti: nice work...dnd/quicklists!
[12:52] <greyback> tsdgeos: that's an excellent question, one which I've not a clear answer for.
[12:52] <mzanetti> Saviq: when you're done with approving my dnd branch, here comes the next one https://code.launchpad.net/~mzanetti/unity-api/launcher-quicklist-add-hasAction/+merge/180864
[12:52] <tsdgeos> greyback: i've this http://paste.ubuntu.com/6002766/
[12:52] <mzanetti> kgunn: :) the drag'n drop really was a tricky one
[12:52] <tsdgeos> but even if i return from startShell the process never finishes
[12:52] <tsdgeos> maybe it hard to have a proper unittest :D
[12:53] <greyback> tsdgeos: hmm, it is supposed to. Lemme look
[12:53] <mzanetti> tsdgeos: btw... are you writing a .desktop file parser?
[12:53] <tsdgeos> mzanetti: me? no
[12:53] <mzanetti> ok
[12:53] <tsdgeos> mzanetti: Wellark is it seems
[12:53] <Saviq> mzanetti, k
[12:53] <mzanetti> tsdgeos: yeah.... he's actually mostly done... just needs to fix comments from reviews
[12:53] <mzanetti> tsdgeos: just wanted to make sure we don't start a second one
[13:13] <kgunn> greyback: was just seeing what all transpired...i saw sergio's bootstrap merge on unity-mir...so we're in  ?
[13:14] <greyback> kgunn: yes, unity-mir in main.  I need to double-check
[13:18] <greyback> kgunn: gah, I was wrong. It's not in main yet. Must find out why
[13:18] <kgunn> greyback: np...
[13:18] <Saviq> greyback, not yet, it's being NEWed
[13:18] <Saviq> greyback, sil2100 is handling, right? unity-mir NEW?
[13:19] <greyback> Saviq: yep
[13:19] <Saviq> greyback, there were some packaging comments, I think sil2100 is tackling those
[13:19] <greyback> Saviq: yep, I'm reviewing a MR from him now
[13:20] <Saviq> good
[13:20] <sil2100> Saviq: yes, I'm handling it, but I see that due to the merger problems one important merge did not get in
[13:20] <Saviq> kgunn, won't make standup, queueing for insurance prior to holidays...
[13:21] <Saviq> kgunn, wanna make a catchup later in the afternoon
[13:21] <Saviq> ?
[13:21] <kgunn> Saviq: sounds good
[13:21] <Saviq> kgunn, I should be available on the hour
[13:21] <Saviq> kgunn, and then we have a review with JohnLea an hour later
[13:22] <Saviq> kgunn, so your call when
[13:24] <Saviq> mzanetti, I wonder... s/hasAction/active/? or s/hasAction/activatable/? not really sure if that's better...
[13:24] <Saviq> "active" could probably mean something else (has action, but is inactive)
[13:24] <mzanetti> Saviq: not "active"...
[13:24] <mzanetti> exactly
[13:24] <Saviq> so would conflict
[13:24] <mzanetti> Saviq: activateble... maybe
[13:25] <mzanetti> otherwise "clickable" might do
[13:25] <mzanetti> no strong opinion there
[13:25] <Saviq> that might be the best (most obvious) actually
[13:25] <Saviq> mzanetti, let's go with that, then
[13:25] <mzanetti> whcih one?
[13:25] <mzanetti> clickable?
[13:25] <mzanetti> Saviq: ^
[13:26] <Saviq> mzanetti, yes
[13:26] <mzanetti> ok
[13:26] <Saviq> mzanetti, I like what you did to the blueprint :D
[13:26] <Saviq> we need more of that ;D
[13:26] <mzanetti> indeed :D
[13:27] <mzanetti> well, with the quicklists I'm hoping to ship a second batch of that this week still
[13:27] <Saviq> :)
[13:28] <kgunn> Saviq: lets try to chat exactly 1 hr from now
[13:28] <Saviq> kgunn, +1
[13:29] <mzanetti> Saviq: updated the MR
[13:29] <Saviq> mzanetti, thanks
[13:30] <Saviq> mzanetti, approved
[13:30] <mzanetti> Saviq: cool, thanks
[13:31] <mzanetti> Saviq: standup
[13:31] <Saviq> mzanetti, yeah, not gonna make it, on 3G again
[13:31] <nic-doffay> Saviq, btw getting loads of undefined references to GenericOptionsModel now.
[13:31] <nic-doffay> I'm not sure what's supposed to be here still and what's supposed to be removed.
[13:31] <nic-doffay> Re the filters.
[13:31] <Saviq> nic-doffay, GenericOptionsModel.{h,cpp} are there
[13:32] <Saviq> lowercase that
[13:32] <Saviq> nic-doffay, so this shouldn't be removed at all (and not from CMakeLists either)
[13:51] <nic-doffay> Saviq, there were some other issues, but I've resolved them. I'm assuming the model of the OptionSelector ListView should be scope.categories ?
[14:17] <mhall119> Saviq: I'm still setting unity8 and SurfaceFlinger using a lot of CPU when the phone should be idle, has that issue been tracked down yet?
[14:18] <Saviq> nic-doffay, no, scope.filters
[14:18] <Saviq> mhall119, if you're seeing it - obviously not, but it must be a separate issue, then, can you please file a bug with as much info as possible?
[14:19] <mhall119> sure, what can I do to get better info for you?
[14:19] <nic-doffay> Saviq, there are two ListViews though, what about the other one. Eg it's looking similar to this atm: https://pastebin.canonical.com/96010/
[14:21] <Saviq> nic-doffay, no, that's wrong
[14:21] <nic-doffay> Saviq, how so?
[14:21] <Saviq> nic-doffay, values: options
[14:22] <Saviq> nic-doffay, where "options" is the role from Filters model
[14:22] <Saviq> nic-doffay, categories are completely not what you want to be looking at there
[14:22] <nic-doffay> Saviq, scope.options are undefined.
[14:22] <Saviq> nic-doffay, read
[14:22] <Saviq> nic-doffay, everything you need is in scope.filters
[14:22] <Saviq> nic-doffay, read the .h
[14:22] <nic-doffay> Saviq, I'll take a look.
[14:23] <nic-doffay> Saviq, filters.h?
[14:23] <Saviq> nic-doffay, filters.h, filter.h, there's a bunch
[14:23] <Saviq> nic-doffay, everything is here http://bazaar.launchpad.net/~unity-team/unity8/trunk/revision/203
[14:27] <tedg> dednick|lunch, Hey I noticed a couple of merges for indicators, curious how the new ones are working for you.  Don't interrupt lunch though :-)
[14:29] <Saviq> kgunn, ready when you are
[14:30] <kgunn> Saviq: just getting a link
[14:38] <Cimi> where do I find API for org.freedesktop.Accounts ?
[14:39] <Cimi> http://cgit.freedesktop.org/accountsservice/tree/data/org.freedesktop.Accounts.User.xml ?
[14:49] <Saviq> tedg, was thinking about the url dispatcher... any reason why we wouldn't build it *into* the new app manager?
[14:49] <Saviq> tedg, looking at lp:url-dispatcher it's pretty thin, not sure if it's big enough to warrant its own project / binary / library
[14:49] <Saviq> tedg, as it will be exposed via the platform api anyway
[14:50] <tedg> Saviq, I figured it'd get more complex when it has to have things like click package hooks, etc, etc.  But certainly today it is tiny.
[14:50] <tedg> Saviq, About being part of the app manager is interesting, I'm not sure how I feel about that.
[14:51] <Saviq> greyback, tsdgeos, how about you guys ↑?
[14:51] <Saviq> url-dispatcher built *into* app manager?
[14:51] <tedg> Saviq, The part that would concern me there is about the secondary activation aspects, would you guys want to implement all that in the application manager?
[14:52] <Saviq> tedg, "secondary activation aspects"?
[14:52] <tedg> Saviq, Application is already running and you need to pass it the URL.
[14:52] <tedg> Second time.
[14:52] <Saviq> tedg, right
[14:52] <Saviq> tedg, or activate an action, for that matter
[14:54] <Saviq> tedg, ok, let's leave it be for now
[14:54] <greyback> how are we planning to do these secondary activations then?
[14:54] <greyback> tedg: ^^
[14:54] <tedg> Saviq, Do you guys have a design for when two apps register for the same type?  (i.e. choose which app to do this action with)  I think perhaps that UI should drive some of this.
[14:54] <fginther> kenvandine, hello :-)
[14:55] <fginther> kenvandine, is lp:qtcreator-plugin-ubuntu ready for daily release?
[14:55] <dednick> Saviq: when you were testing indicators on friday, you mentioned that it was starting the settings when you activated the menu option. was that on desktop, or device?
[14:55] <tedg> greyback, I was expecting to handle that in upstart-app-launch... it's not done, so I'm happy to have someone else do it :-)
[14:55] <Saviq> tedg, no design
[14:55] <Saviq> dednick, both
[14:55] <tedg> Saviq, \o/  ;-)
[14:55] <Saviq> dednick, but on device it won't show up
[14:55] <Saviq> dednick, 'cause it doesn't have --desktop_file_hint
[14:56] <dednick> Saviq: ic. how are we to fix that?
[14:56] <tedg> We need to throw them through upstart-app-launch or url-dispatcher
[14:56] <Saviq> ↑ that
[14:56] <dednick> ok
[14:57] <Saviq> or short-term add --desktop_file_hint
[14:57] <tedg> Not sure what is best there...
[14:57] <tedg> Seems like we should try to use URLs for everything.
[14:57] <Saviq> tedg, probably url-dispatcher, yeah
[14:58] <tedg> Saviq, When is Unity-mir supposed to land?  Not dependent on a particular day, more curious to have an idea.
[14:58] <Saviq> tedg, last Friday
[14:58] <Saviq> ;)
[14:59] <tedg> Woot!  It's done!
[14:59] <Saviq> tedg, but other than that - asap
[14:59] <tedg> K
[14:59] <mhr3> saviq, do we have a bug for the limitproxy issue i showed you last time? if not, i'm opening it
[14:59] <Saviq> mhr3, no, no bug, tsdgeos was looking into
[15:00] <Saviq> mhr3, but yes, please open
[15:00] <Saviq> tedg, we built a temp workaround for session authorization into app-manager (based on --desktop_file_hint)
[15:00] <tsdgeos> i was, then gerry snatched me
[15:00] <Saviq> yes
[15:00] <Saviq> tedg, but would be nice to get to the real solution in soon, too
[15:00] <tedg> Saviq, Yup, got a bunch of fires right now though... it might be a bit :-/
[15:01] <Saviq> tedg, that's why we built the easy - temporary - solution :)
[15:02] <dednick> tedg: which new indicators were you refering to? datetime/sound/battery?
[15:02] <greyback> tedg: note that AppMan will be suspending/resuming/hibernating apps soon, we're gonna have to figure out how that works with upstart-app
[15:02] <tedg> dednick, Yup
[15:03] <tedg> greyback, Do the PIDs stick around?
[15:03] <greyback> mhr3: he's mine!
[15:03] <greyback> tedg: not if app is killed, and respawned again later
[15:03] <mhr3> greyback, but my bug will have High priority!
[15:03] <tedg> greyback, So I think that's the only case we care about.  Do you start it differently in that case?
[15:03] <tedg> greyback, Or does the app handle those internally?
[15:04] <greyback> tedg: it's internal
[15:04] <dednick> tedg: most things seem to be ok. The battery indicator seems to be showing a critical icon whenever my phone is plugged in. Sound volume changing rarely works (although we had issues in old as wel.) Otherwise the app start is the only thing that isnt working.
[15:04] <greyback> mhr3: he's mine, mwahahah!
[15:04] <mhr3> greyback, no bug, no tsdgeos, haha!
[15:05] <tedg> greyback, So I don't see any thing we need to do different, do you?
[15:05] <dednick> tedg: we're also missing a few widgets for the sound, but they wont be hooked up for awhile anyway
[15:05] <tedg> dednick, K, sounds reasonable.
[15:06] <tedg> dednick, There is an indicator-messages branch called "consolidate" that updates to the new indicator format.
[15:06] <greyback> tedg: well where it concerns me is with these secondary activations. Will upstart know the app we want to activate is suspended, and resume it. But then will shell know it has been resumed?
[15:06] <mhr3> tsdgeos, https://bugs.launchpad.net/unity8/+bug/1213959
[15:06] <tedg> dednick, pete-woods is looking at it today, hopefully it'll work and we can get that merged to trunk.
[15:06] <mhr3> ;)
[15:06] <tedg> dednick, If you want a head start, you can see it there.  But it seems to work for me.
[15:07] <tedg> greyback, Uhm, good point.  Hadn't thought of that.
[15:07] <nic-doffay> Saviq, GenericOptionsModel* options() is overridden in the classes which inherit filter.h surely surely scope.filters.option would be enough to access the model?
[15:07] <tedg> greyback, I thought we were going to stop SIGSTOP'ing apps and move to just killing them?  Or is that still in the plan?
[15:08] <Saviq> nic-doffay, no, filters is a *list* of filter objects
[15:08] <dednick> tedg: yeah, i've been taking a look today. I need to update unity8 for it
[15:08] <Saviq> nic-doffay, or a list model of them
[15:09] <tedg> dednick, Just to not have two entries?  Or something else?
[15:09] <dednick> tedg: to use unitymenumodel
[15:09] <greyback> tedg: You're at my knowledge limit. ricmm knows more.
[15:10] <nic-doffay> Saviq, so how do I get the role? I'm not sure what I'm looking for here.
[15:11] <Saviq> nic-doffay, there isn't (should be) a "filter" role in Filters
[15:11] <Saviq> nic-doffay, that should return the Filter object (as getFilter does)
[15:12] <Saviq> nic-doffay, and that object has an .options property
[15:12] <Saviq> pstolowski, can you help nic-doffay on that ↑ ?
[15:12] <Cimi> can I have a little help with quake?
[15:12] <Cimi> lp:~cimi/ubuntu-system-settings/welcome-wizard
[15:12] <Cimi> not sure the account plugin is installed...
[15:13] <pstolowski> Saviq, nic-doffay: sure
[15:13] <Saviq> pstolowski, nic-doffay or well, I wonder if "options" shouldn't be a role straight away
[15:13] <Saviq> pstolowski, nic-doffay in Filters
[15:15] <nic-doffay> pstolowski, I'm trying to access the options model.
[15:16] <mhr3> saviq, the touch image contains libunity-scopes-json-def-desktop instead of -phone, where do we fix that?
[15:16] <pstolowski> nic-doffay: give me a sec, trying to grasp your discussion
[15:18] <pstolowski> nic-doffay, Saviq: right, an omission on my side
[15:18] <Cimi> mzanetti, ^ :)
[15:18] <Cimi> qmake not quake
[15:18] <mzanetti> Saviq: did you understand this one? https://bugs.launchpad.net/ubuntu-ux/+bug/1213153
[15:18] <mzanetti> Cimi: ?
[15:18] <Cimi> mzanetti, lines above
[15:19] <mzanetti> Cimi: yeah... haven't played Quake in ages, but I'll do my best :P
[15:19] <Cimi> hah
[15:20] <pstolowski> nic-doffay, Saviq: I'm going to add a role that gives you options right away
[15:20] <Saviq> mzanetti, yes, let's talk in 10, k?
[15:20] <mzanetti> sure
[15:20] <Saviq> pstolowski, I think it's best indeed
[15:21] <mzanetti> Cimi: what's the issue?
[15:21] <Cimi> mzanetti, wizard doesn't work..
[15:21]  * mzanetti is on a merging spree today: https://code.launchpad.net/~mzanetti/unity8/quicklists/+merge/180894
[15:21] <Cimi> mzanetti, page of AboutYOu
[15:21] <Cimi> mzanetti, what0s the dir?
[15:22] <mzanetti> Cimi: building...
[15:23] <mzanetti> Cimi: when I start it I get 3 pages
[15:23] <Cimi> mzanetti, then crash?
[15:24] <Cimi> it's because it cannot find the plugin I think
[15:24] <mzanetti> Cimi: not a crash... but this: module "Ubuntu.SystemSettings.AccountPlugin" is not installed
[15:24] <Cimi> yeah
[15:24] <Cimi> mzanetti, I added the module...
[15:24] <mzanetti> Cimi: where?
[15:24] <Cimi> mzanetti, created account folder under plugins
[15:24] <Cimi> copied some project file and edited...
[15:25] <Cimi> but I don0t think it is installed or I don't know
[15:25] <mzanetti> Cimi: it's installed to /ubuntu-system-settings/private/Ubuntu/SystemSettings/Account/
[15:25] <Cimi> mzanetti, in root /
[15:25] <Cimi> yeah
[15:26] <mzanetti> Cimi: but you're trying to import Ubuntu.SystemSettings.AccountPlugin
[15:26] <mzanetti> which doesn't match that dir
[15:26] <Cimi> mmm ok
[15:27] <nic-doffay> pstolowski, how do I access that role? Is there a getter function in filters.h? All I see is an enum with Roles.
[15:28] <pstolowski> nic-doffay: standard way of accessing qt data models in qml - use role name in the delegate
[15:30] <Saviq> nic-doffay, http://qt-project.org/doc/qt-5.0/qtquick/qtquick-modelviewsdata-modelview.html#qml-data-models
[15:30] <Saviq> nic-doffay, and http://qt-project.org/doc/qt-5.0/qtquick/qtquick-modelviewsdata-cppmodels.html
[15:31] <Saviq> mzanetti, can you mumble?
[15:31] <mzanetti> Saviq: sure
[15:31] <nic-doffay> pstolowski, are you pushing something for this regarding the options?
[15:32] <pstolowski> nic-doffay: I'm currently working on it
[15:32] <pstolowski> nic-doffay: should have it soonish
[15:32] <nic-doffay> pstolowski, cool
[15:33] <Saviq> greyback, can you mumble?
[15:33] <Cimi> mzanetti, ok works good...
[15:33] <mzanetti> Saviq: so, here are the quicklists: https://code.launchpad.net/~mzanetti/unity8/quicklists/+merge/180894
[15:33] <Saviq> mzanetti, cool
[15:33] <mzanetti> vesar: ^^
[15:37] <mzanetti> Cimi: what did you mean with works good?
[15:37] <Cimi> mzanetti, that the plugin loads and shows me my name..
[15:37] <mzanetti> Cimi: did it fix your plugin problem, or did you test my quicklist branch?
[15:37] <mzanetti> ah ok
[15:37] <kenvandine> fginther, not sure
[15:37] <kenvandine> fginther, i need to look at it still
[15:38] <fginther> kenvandine, no problem, it's in the stack file with daily-release false
[15:39] <kenvandine> fginther, Mirv had emailed me about it, i haven't had time to sponsor it
[15:39] <kenvandine> he mentioned it was daily-release False, but i don't recall if he said why
[15:41] <Cimi> 28815
[15:54] <Saviq> Cimi, is that your high score from quake or?
[15:54] <Cimi> hah
[15:54] <Cimi> Saviq, think it was my yubikey
[15:54] <Luzbelito> Hello. Days ago I crashed my Unity and compiz; lefting my ubuntu 13.04 unoperable. I-ve searched the net, followed tutorials, and the help given to me in different irc channels <thank you very much, bschaeffer> but the problem remains,
[15:55] <Cimi> Saviq, wrong app focused...
[15:56] <Luzbelito> my question now is if there could be some kind of command or script that allows mw return my 13.04 to it initial state, like reinstalling it, without affect my /home folder
[15:56] <Luzbelito> any idea?
[15:57] <pstolowski> nic-doffay: lp:~stolowski/unity8/add-options-role
[15:57] <pstolowski> nic-doffay: can you give it a shot before I MP?
[16:08] <nic-doffay> pstolowski, yeah taking a look now...
[16:13] <Cimi> Saviq, I add i18n and then I'll wait the wifi plugin before continuing...
[16:13] <Cimi> Saviq, just finished the username page and sets correctly
[16:14] <Cimi> so I'm only missing wifi and assets
[16:19] <nic-doffay> pstolowski, can I access it from the delegate using scope.filters.RoleOption
[16:20] <pstolowski> nic-doffay: you need to use role names that are mapped in roleNames(), so - "options"
[16:20] <pstolowski> nic-doffay: scope.filters.options I suppose
[16:20] <pstolowski> nic-doffay: and options is yet another model, that has own roles
[16:21] <Cimi> nic-doffay, ETA for the option selector?
[16:22] <nic-doffay> Cimi, when JP comes back from holiday. He needs to look at an autopilot issue.
[16:22] <nic-doffay> Neither me nor Christian had any luck.
[16:22] <nic-doffay> He's back this week, I'll check when.
[16:23] <nic-doffay> Cimi, you can use the branch in the mean time without issue.
[16:23] <Cimi> nic-doffay, using list items in the meanwhile no problem...
[16:27] <nic-doffay> pstolowski, it doesn't seem to be doing the job. I see the string was added to the switch case in the cpp too...
[16:28] <pstolowski> nic-doffay: what are you doing with options value? do you get values of other roles?
[16:29] <nic-doffay> pstolowski, this is a rough idea of what it looks like currently.
[16:29] <nic-doffay> https://pastebin.canonical.com/96020/
[16:29] <nic-doffay> Or what I'm attempting.
[16:33] <mhr3> ehm, what can cause scrolling down to switch between dash pages instead?
[16:33] <pstolowski> nic-doffay: how is "delegate: optionSelector" matching OptionSelector { ..} below?
[16:33] <nic-doffay> pstolowski, it's passed using a the id.
[16:33] <nic-doffay> It's just omitted from the pastebin.
[16:33] <nic-doffay> That all works without an issue if the model is an integer.
[16:36] <pstolowski> nic-doffay: and how are you accessing actual values of options model (in options selector.values I guess)?
[16:37] <nic-doffay> pstolowski, values is a model.
[16:37] <nic-doffay> So that should be a drop down of Value 1, Value 2 etc
[16:38] <pstolowski> nic-doffay: yeah, I know, can you pastebin how it's handled?
[16:39] <Wellark> hah!
[16:39] <Wellark> I fixed Qt.
[16:39] <Wellark> kinda. :)
[16:39] <Wellark> mzanetti: I now have a patch that allows loading thunderbird icon properly
[16:40] <mzanetti> Wellark: great.
[16:40] <mzanetti> how about the others? :P
[16:40] <Wellark> Qt patch that it is.
[16:40] <nic-doffay> pstolowski, what do you mean by how it's handled?
[16:41] <Wellark> we need it for the theme icon loader which we need for the launcher and the whole shell
[16:41] <pstolowski> nic-doffay: I mean, the qml snippet where you iterate over all the values of options model
[16:41] <Wellark> mzanetti: wanna sponsor my patch when I get it upstreamed? :)
[16:42] <mzanetti> ?
[16:42] <Wellark> mzanetti: aren't you a qt contributor? :)
[16:42] <Wellark> this is my first qt patch
[16:42] <nic-doffay> pstolowski, if I understand correctly that should be handled by the ListView delegate.
[16:43] <mzanetti> Wellark: ah... I can review it, yes, but I don't have approver right in Qt either
[16:44] <Wellark> review would be great
[16:44] <Wellark> maybe I show the patchet to you first before embarassing my self in the public :P
[16:44] <pstolowski> nic-doffay: not really, the delegate needs to reffer to proper role names
[16:45] <pstolowski> nic-doffay: so, in the delegate that handles options rendering, you need to access 'name' and 'active' roles at the very least
[16:45] <nic-doffay> pstolowski, what exactly is the role?
[16:46] <mzanetti> Wellark: hehe. feel free
[16:46] <nic-doffay> pstolowski, the name role is for each filter, correct?
[16:46] <pstolowski> nic-doffay: you can think of it as column of a model row (but in reality it's more than that)
[16:46] <Wellark> mzanetti: ok, I will ping you tomorrow
[16:46] <mzanetti> Wellark: ok.
[16:46] <Wellark> mzanetti: I still have one bug to fix on the QIcon theme code
[16:47] <nic-doffay> pstolowski, so how can I access the name role from options then?
[16:49] <pstolowski> nic-doffay: just use role names in the delegate of your ListView (that has reference to options model)
[16:50] <pstolowski> nic-doffay: see this example - http://qt-project.org/doc/qt-5.0/qtquick/qtquick-modelviewsdata-modelview.html#models
[16:51] <nic-doffay> pstolowski, I've read through that before. But I'm still not sure what a role name is.
[16:52] <pstolowski> nic-doffay: role name is just a column index
[16:53] <mpt> larsu, hi. In bug 1186181 could you please describe, or link to the code that defines, how the choice of icon relates to the battery percentage? I want to know whether it's a visual design bug or a logic bug.
[16:54] <pstolowski> nic-doffay: (in reality it's a "virtual" columns, as it's up to the data(...) implementation in my model what value to return for given role)
[16:54] <nic-doffay> pstolowski, right. I'm still lost. If values is a model, and scope.filters.options returns a model too, surely passing scope.filters.options should be enough?
[16:56] <pstolowski> nic-doffay: not really, depends what roles 'values' model supports. you need to look at the delegate that renders it, and update it to use correct roles
[16:58] <nic-doffay> pstolowski, the optionSelector delegate displays text: modelData
[17:00] <pstolowski> nic-doffay: ok, afaict this is only correct for some specific models (http://harmattan-dev.nokia.com/docs/platform-api-reference/xml/daily-docs/libqt4/qdeclarativemodels.html); can you change it to "text: name" ?
[17:01] <nic-doffay> pstolowski, it's an SDK component.
[17:01] <nic-doffay> So not really.
[17:02] <pstolowski> nic-doffay: hmm. how does know if option is active?
[17:02] <nic-doffay> pstolowski, currently there's nothing for that in the option selector.
[17:02] <nic-doffay> pstolowski, if it's required I'll add it though.
[17:03] <pstolowski> nic-doffay: we definately need to mark selected filter option
[17:04] <larsu> mpt: done. [this is an automated reply because I'm on vacation]
[17:05] <nic-doffay> pstolowski, ok cool. Question is what to use instead of modelData since the OptionSelector is an SDK class.
[17:05] <nic-doffay> I'm not aware of anything else.
[17:08] <pstolowski> nic-doffay: it seems to me that this is currently very limiting in the SDK, but maybe I'm missing something. we need to check with sdk huys
[17:08] <pstolowski> guys
[17:09] <pstolowski> Kaleo: ping?
[17:58] <sil2100> tedg: hi!
[17:58] <sil2100> tedg: I need to jump out now, but: https://bugs.launchpad.net/ubuntu/+source/indicators-client/+bug/1214065
[17:58] <sil2100> tedg: could you comment?
[17:58] <sil2100> See you tomorrow guys!
[17:59] <tedg> Sure
[17:59] <mhall119> Saviq: is "Home Scopes" going to be the text for the Dash header?
[18:15] <Saviq> mhall119, sounds like a bug against unity-scope-home
[18:18] <tedg> mardy, Hey, are you still awake?  :-)
[18:20] <tedg> Oh, no, I updated my phone and all the videos are gone!  Am I going to have to purchase these movies to get their covers now?
[18:24] <mhall119> Saviq: so it's not likely it'll have "Scope" in the header?
[18:28]  * greyback eod
[19:05] <mhall119> alecu_: ping
[19:08] <mhall119> alecu_: http://ubuntuone.com/58AA6ZWyYlN6iQbB0SuhqK see the last screenshot
[19:08] <mhall119> it was a landscape image, something's gone wrong in the resizing/thumbnailing
[19:31] <Saviq> mhall119, I don't believe it's meant to say "Scope" indeed
[19:32] <Saviq> mhall119, but it's there in the home.scope file from unity-scope-home
[19:32] <Saviq> mhall119, so that's where it needs to be fixed
[19:46] <mhall119> Saviq: ok, thanks
[20:16] <kgunn> Saviq: you were saying earlier...gerry hoping to get osk wrapped up this week ? (meaning, beside mir this would be hold up item #2 in landing?)
[20:17] <Saviq> kgunn, he was hoping today/early tomorrow, not only this week
[20:17] <Saviq> mzanetti, first of all, GO AWAY
[20:18] <Saviq> mzanetti, second, did you get designs for count / progress like those?
[20:18] <kgunn> Saviq: ok...cool, so mir N4 is really going to be long poll
[20:18] <Saviq> kgunn, :/
[20:18] <mzanetti> Saviq: sort of
[20:19] <mzanetti> Saviq: I got the assets and I got a mock for the progressbar. I placed the count emblem according to screenshots of unity7
[20:22] <Saviq> mzanetti, they ugly! :D
[20:22] <mzanetti> :D
[20:23] <mzanetti> Saviq: could be the assets are temporary until we get the new UbuntuShape
[20:24] <mzanetti> Saviq: this would need some input from you I guess: https://bugs.launchpad.net/bugs/1206941
[20:35] <Saviq> mzanetti, on another note, I've seen on designs before
[20:35] <Saviq> mzanetti, that apps which are during installation
[20:35] <Saviq> mzanetti, their icons should "fill up" with colour
[20:36] <mzanetti> Saviq: yep. app install animation is still todo
[20:36] <mzanetti> actually also missing in the API still
[20:36] <Saviq> mzanetti, do we have backend for that?
[20:36] <Saviq> mzanetti, yeah, we should use the same progress sources the Scopes use
[20:36] <Saviq> mzanetti, take a look at AppPreview
[20:37] <mzanetti> Saviq: is that already working in the dash?
[20:37] <Saviq> mzanetti, only in the preview
[20:37] <mzanetti> Saviq: how do I test that?
[20:37] <Saviq> mzanetti, and not the "filling" part, but the progress reporting - yes
[20:37] <mzanetti> ah ok
[20:38] <mzanetti> Saviq: my unity8 is spinning btw
[20:38] <mzanetti> :/
[20:38] <Saviq> mzanetti, description for https://code.launchpad.net/~unity-team/unity8/app-preview-data/+merge/179348 has pointers on how to enable the click scope
[20:38] <Saviq> mzanetti, :(
[20:38] <Saviq> mzanetti, surfaceflinger, too?
[20:38] <Saviq> mzanetti, then you can just go through the installation procedure
[20:38] <mzanetti> Saviq: yes, 9% surfaceflinger, 50% unity
[20:39] <Saviq> mzanetti, so it's redrawing most probably
[20:39] <Saviq> we'll have to investigate
[20:39] <mzanetti> Saviq: wow! it happens only when the greeter is shown
[20:40] <Saviq> mzanetti, with launcher it might be slightly trickier on where to get the data from (scopes tell us what "progress source" we're to look at)
[20:40] <mzanetti> infographics most likely
[20:40] <Saviq> mzanetti, interesting, but nothing changed there
[20:40] <mzanetti> Saviq: take a picture with the camera
[20:40] <mzanetti> Saviq: then you'll get real data in there
[20:40] <mzanetti> and it draws bubbles
[20:41] <Saviq> mzanetti, yeah, that's old
[20:41] <Saviq> mzanetti, 2-3 weeks at least
[20:41] <mzanetti> I discovered it 3 days ago
[20:41] <Saviq> mzanetti, doesn't mean it wasn't there ;)
[20:42] <Saviq> mzanetti, but infographics is kind of meant to be like that - surprising :D
[20:42] <Saviq> but we need more surprises ;)
[20:42]  * mhall119 was surprised when he first saw it
[20:43] <mhall119> btw, people really liked the infographics idea at the XDA conference, the idea of an always-changing, always-unique welcome screen was a hit
[20:46] <mzanetti> Saviq: from what I see, I'd just need that DownloadListener
[20:46] <Saviq> mzanetti, yeah, but the arch of it isn't yet correct
[20:46] <Saviq> mzanetti, i.e. it will get more generic
[20:46] <mzanetti> Saviq: tracks only downloads, not installations, or?
[20:46] <Saviq> mzanetti, yeah, for example
[20:47] <Saviq> mzanetti, and is just too limited
[20:47] <Saviq> mzanetti, scopes will report which dbus name/path to connect to for a given category
[20:47] <mzanetti> Saviq: is it on someones blueprint to extend this?
[20:47] <Saviq> mzanetti, kind of, mhr3 and pstolowski know about it and are working towards it
[20:47] <mzanetti> ok.
[20:48] <mzanetti> the "make trySomething" is just the best thing ever :)
[20:58] <Saviq> +1
[22:27] <veebers> mterry: ping, are you still around?
[22:29] <mterry> veebers, hi
[22:30] <veebers> mterry: how's things? I had a question re: the ubuntu-keyboard packaging that I notice you had recent dealings with
[22:31] <veebers> mterry: I'm working on the autopilot tests etc. for the ubunut-keyboard, initially (before it was split off into ubuntu-keyboard) I noticed that it only built for arm, and that's changed now?
[22:31] <mterry> veebers, yeah, I didn't see anything arm-specific about it, so I changed it
[22:31] <veebers> I just built and installed it, but it doesn't seem to work for me on my desktop (where it works fine on the device)
[22:31] <veebers> mterry: hmm ok, perhaps there is something else afoot then
[22:32] <mterry> veebers, ah, I didn't actually test.  Maybe it needs touch/qtubuntu layers?
[22:32] <mterry> veebers, with latest packaging changes, the tests work fine on amd64...
[22:32] <mterry> (mostly)
[22:33] <veebers> mterry: I'm not sure to be honest, my small amount of debugging was: have maliit-framework and ubuntu-keyboard installed, try to start maliit server: I see this failure:
[22:33] <veebers> open /usr/lib/arm-linux-gnueabihf/libpinyin/data/pinyin_index.bin failed!
[22:33] <veebers> Segmentation fault (core dumped)
[22:34] <mterry> veebers, ah
[22:34] <mterry> veebers, try lp:~mterry/ubuntu-keyboard/run-tests
[22:35]  * veebers looks
[22:35] <mterry> veebers, notably the changes to src/lib/logic/pinyinadapter.cpp
[22:35] <mterry> https://code.launchpad.net/~mterry/ubuntu-keyboard/run-tests/+merge/180941
[22:35] <veebers> mterry: ah ok :-)
[22:37] <veebers> mterry: sweet, I'll build that and give it a try, see where I get to
[22:37] <veebers> mterry: would you have a couple of moments to have a look at some minor packaging changes I have in a MR for the autopilot pieces?
[22:38] <mterry> veebers, ok
[22:38] <veebers> mterry: awesome thanks: https://code.launchpad.net/~veebers/ubuntu-keyboard/adding_autopilot_tests_and_emulators/+merge/180480
[22:53] <veebers> heh, thanks for reviewing that mterry, I'll make those changes re sorting the depends. Unfortunately I can't easily change the other comment :-)
[22:58] <mterry> veebers, ah well
[22:59] <veebers> mterry: sweet, with that branch of yours I can build it and it runs without segfaulting. I can also sometimes get the keyboard up on my screen, however it's on its side
[22:59] <mterry> veebers, progress!


[02:51] -lugito:#lubuntu-devel- [rMANUAL68fa86cf7048: fix mangled date and time checkbox] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL68fa86cf7048
[02:55] -lugito:#lubuntu-devel- [rMANUALc81750a80153: Major reword of changing time] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALc81750a80153
[03:09] -lugito:#lubuntu-devel- [rMANUAL13b52f64cef2: Properly style RTC is in local time checkbox] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL13b52f64cef2
[03:14] -lugito:#lubuntu-devel- [rMANUALdf447bb68aed: Properly label timezone tab] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALdf447bb68aed
[03:29] -lugito:#lubuntu-devel- [rMANUAL9a9042465f09: Add cancel button to date and time] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL9a9042465f09
[03:54] -lugito:#lubuntu-devel- [rMANUAL0bc797834762: Label open button in libreoffice impress] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL0bc797834762
[04:01] -lugito:#lubuntu-devel- [rMANUAL140d78a55fe8: Add how to sort slides in slidesorter mode] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL140d78a55fe8
[04:11] -lugito:#lubuntu-devel- [rMANUAL6dab92636b75: Style keyboard shortcuts of loimpress] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL6dab92636b75
[04:20] -lugito:#lubuntu-devel- [rMANUAL40824c1d98bf: Add loimpresss toggle bullets] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL40824c1d98bf
[04:33] -lugito:#lubuntu-devel- [rMANUAL691ac19e2f3f: Add loimpress bulleted list] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL691ac19e2f3f
[04:46] -lugito:#lubuntu-devel- [rMANUALe2dcf5111bbe: Add paste unformatted text] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe2dcf5111bbe
[05:11] -lugito:#lubuntu-devel- [rMANUAL425f30b96dd3: Add menu for paste unformatted text] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL425f30b96dd3
 wxl @tsimonq2 we should include qapt-deb-installer for deb packages
 it's already in the repositories
 Ok
 after that we should change the mimeapp list
 @HMollerCl [after that we should change the mimeapp list], Noted.
 Cool
 @The_LoudSpeaker [Noted.], 👍
[18:48] -lugito:#lubuntu-devel- [rMANUAL3e9eb7554743: Add screenshot for images in loimpress] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL3e9eb7554743
[19:05] -lugito:#lubuntu-devel- [rMANUALe4c20b8822fe: Add images bullet point to loimpress] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe4c20b8822fe
[19:12] -lugito:#lubuntu-devel- [rMANUALe88b4d792338: Add changing line spacing to libreoffice_impress] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe88b4d792338
 @HMollerCl i believe you wanted to relay something here of some importance regarding LibreOffice?  :P
[19:23] <wxl> @HMollerCl re: https://bugs.documentfoundation.org/show_bug.cgi?id=122752 but isn't that going to mean bad looking UX? or am i confused?
 https://bugs.documentfoundation.org/show_bug.cgi?id=122752
 Yes, filepicker or file save dialog
 Only that is affected
[19:26] -lugito:#lubuntu-devel- [rMANUAL18c66fe35b7f: Add increase/decrease paragraph spacing] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL18c66fe35b7f
 The problem is that kde5 file save dialog is incomplete in non-plasma, it doesn't add file extension and other small things
 Gtk3 works ok
[19:28] <wxl> didn't that bug say they'd be using qt5 for non-plasma?
[19:29] <wxl> oic nevermind it's "not really usable"
 Yes, it's buggy
[19:31] <wxl> ok well i guess we need to watch the progress of qt5 then. sigh.
[19:31] <lynorian> With 19.04 coming out I will need to figure out how to do mutliple versions of the manual
[19:32] <wxl> there's a ticket for that. it's going to take some custom work
[19:33] <wxl> la
[19:33] <wxl> oops
 ECHAAAN
[19:33] <wxl> nope
[19:34] <wxl> you ECHAN'd the wrong chan XD
 @wxl [<wxl> you ECHAN'd the wrong chan XD], XD
[19:40] -lugito:#lubuntu-devel- [rMANUAL070f12d014d2: Add menu way to insert image] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL070f12d014d2
 @wxl [<wxl> ok well i guess we need to watch the progress of qt5 then. sigh.], Yes, and adjust seed repository accordingly (add/leave lo-gtk3 remove lo-kde5). Btw I uploaded a change to seed https://phab.lubuntu.me/D58 to add qapt-deb-installer
[19:42] -lugito:#lubuntu-devel- [Needs Review] added qapt-deb-installer: https://phab.lubuntu.me/D58
[19:42] <wxl> i saw, briefly.. busy weekend for me (swim meet)
 Should I wait for his approval before making the lo changes? Or I can do it now?
[19:46] -lugito:#lubuntu-devel- [rMANUAL2ed64a94a8dd: Add 1.5 line spacing and how to get back to single line spacing] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL2ed64a94a8dd
[20:08] -lugito:#lubuntu-devel- [rMANUALe9312fe20ff6: Fix warning] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALe9312fe20ff6
[20:59] -lugito:#lubuntu-devel- [rMANUAL62c32f6885a0: Add libreoffice impress format --> character screenshot] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL62c32f6885a0
[21:05] -lugito:#lubuntu-devel- [rMANUAL5a516752f7d0: Add print to libreoffice math] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUAL5a516752f7d0
[21:31] <wxl> hey can anyone check bug 1799855 and see if they also get the same results as Chris, with the 6 packages changed? his results are a little bit weird because of his mirror requirements and i want to double check.
 I sent you a message over the weekend. I can dig it up when I get home.
[21:33] <wxl> oh yeah i was kind of half paying attention this weekend
[21:33] <wxl> if you have any results, even if they're confusing, i'd post them on the bug report
[21:33] <wxl> helps when everything is in the same place XD
 Yeah on my phone right now. I have it on my desktop at home.
[21:34] <wxl> no prob.
 The only weird thing I remember was the onscreen keyboard was present on the sddm login.
[21:36] <wxl> oh thta's right
[21:36] <wxl> you're using english and all that?
[21:36] <wxl> standard keyboard layout?
 Yes I am.
[21:37] <wxl> i've seen that pop up occassionally in the past (with lxde) and i've never been able to reproduce so i don't know :/
 America/New York
[21:37] <wxl> did you happen to capture the results of the process? i'm really curious about the number of packages changed
 Not sure what I have, I can pull the log.
 Still have the VM.
[21:38] <wxl> k. stick it on the bug report
 Will do.
[21:38] <wxl> thx :)
 I was just wondering why does lubuntu has featherpad as default text editor and not gedit? I the later one is more popular and many users would love to have a familiar app in lubuntu. Also, leafpad was also nice why changed from it?
[21:57] <wxl> because it requires gtk libs
[21:57] <wxl> in both cases
[21:57] <wxl> remember, lx*qt*
 @wxl [<wxl> because it requires gtk libs], 👍🏻
 I personally prefer featherpad over gedit.
[21:58] <wxl> i really like kate, but i really don't use graphical text editors
 @wxl [<wxl> in both cases], And so does sublime i guess. But you anyway can't put it coz license issues
[21:59] <wxl> sublime is yucky XD
 @wxl [<wxl> i really like kate, but i really don't use graphical text editors], I use sublime mostly but if in a hurry then nano.
[21:59] <wxl> oh god don't get me started on nano
 @wxl [<wxl> sublime is yucky XD], Sublime is louuuvv!!
[21:59] <wxl> but to each their own :)
 @wxl [<wxl> but to each their own :)], Yup! Agreed.
 For graphical editors Kate is pretty nice. I typically use vim because it is everywhere and comfy at this point.
[22:01] <wxl> ^^^
[22:01] <wxl> you can ssh anywhere and use vim
 For me nano is for small edits and stuff. I use sublime when I write long stuff. And as it also keeps files open across restarts, I keep a running file called random.txt and put in all my ideas, to-dos, etc.
 @wxl [<wxl> you can ssh anywhere and use vim], I can't exit vim 😂😂
[22:02] <wxl> the problem with nano is: messy interface, not very productive
 That is the meme
[22:02]  * wxl facepalms
[22:02] <wxl> last time i used nano i had the same problem
 For bulkier editors I prefer Geany
[22:02] <wxl> sometimes easy is.. too easy
 @HMollerCl [For bulkier editors I prefer Geany], Will surely look it up.
[22:03] <wxl> i like emacs........ when working with lisp
[22:03] <wxl> (and with vim keybindings)
 It turns into muscle memory at some point.
[22:03] <wxl> btw @The_LoudSpeaker [Esc] ZZ is your way to save and quit
 @wxl [<wxl> i like emacs........ when working with lisp], I had tried it somewhere, i don't remember exactly but didn't like it.
 @wxl [<wxl> btw @The_LoudSpeaker [Esc] ZZ is your way to save and quit], Yup! Had to Google that after trying for an hour!
[22:04] <wxl> most real editors require some effort to get configured the way you want. i've never seen a single one that came out of the box just right4
[22:04] <wxl> next time: `man vim` XD
 @The_LoudSpeaker [Will surely look it up.], it's gtk also, but has all this things like showing all the functions on the sidebar
 @wxl [<wxl> most real editors require some effort to get configured the way you want. …], Yup! But for me sublime is almost perfect, just needs the git gutter.
 in my redhat 6.1 days I used plain vi esc:q! and other
[22:05] <wxl> yeah.. plain vi is tough when you get used to heavily tweaked vim
 ^^
[22:05] <wxl> of course to be consistent you mean [Esc] :wq! :)
 hahhaa, right!
 On a more bulkier side, ms vs code is also good.
[22:06] <wxl> really the only thing to understand with vim is that there are the different modes. once you get that, the rest is kind of easy.
[22:06] <wxl> wuzzat?
[22:06] <wxl> (btw we should probably take this convo to offtopic)
 @wxl [<wxl> really the only thing to understand with vim is that there are the differe …], Yup! I will surely give vim a fair chance.
 @wxl [<wxl> (btw we should probably take this convo to offtopic)], Yup!
 why in seeds some packages are between parenthesis () and some with exclamation sign !  before?
[23:36] <wxl> for which?
[23:36] -lugito:#lubuntu-devel- [rMANUALfe8e7fe01ec1: Add symbols dialog box] lynorian (Lyn Perrine) committed: https://phab.lubuntu.me/rMANUALfe8e7fe01ec1
[23:45] <wxl> oh didn't see the word seeds
[23:45] <wxl> if i remember correctly ! is an exclude and () is a recommend
[23:49] <wxl> yep https://manpages.ubuntu.com/manpages/cosmic/en/man1/germinate.1.html
[23:49] <wxl> ^^ @HMollerCl
[23:50] <teward> wxl: can i bother you to help me test something?
[23:50] <wxl> probably
[23:50] <teward> see secret room where I pinged you


[07:55] <jpetersen> hey
[09:49] <kitallis> hi :)
[12:18] <vish> kitallis: hi.. you need to ask Mac_Slow ;)
[12:30] <kitallis> vish, yeah, i know :)
[13:23] <jpetersen> I am offline for some hours, will be back later
[13:25] <jpetersen> hi tedg
[13:26] <tedg> Good morning jpetersen
[13:27] <jpetersen> tedg, there is a patch for https://bugs.launchpad.net/bugs/528527 in the linked branch
[13:27] <ubot4> Launchpad bug 528527 in indicator-application (Ubuntu Lucid) (and 2 other projects) "should respect the gtk "always-show-image" property (affects: 2)" [Low,In progress]
[13:28] <tedg> jpetersen: Sweet, I'll look at that.
[13:30] <jpetersen> tedg, thanks, i am just going to be away, will be back later
[14:31] <jcastro> seb128: fyi Nafai will be in and out today due to some doctor appointments
[14:32] <seb128> jcastro, ok
[14:32] <seb128> hey jcastro
[14:46] <jcastro> qense: I think someone still needs to connect the monochrome icons in banshee.
[14:46] <jcastro> wrt. your question this weekend
[14:50] <qense> jcastro: It turned out that the wrong icon name was used for the monochrome icon.
[14:51] <qense> jcastro: Banshee's icon name is media-player-banshee, so the applet looks for media-player-banshee-panel, logically it can't find banshee-panel that way.
[14:51] <jcastro> ah excellent, so now all we need is the app indicator and we're all set. :D
[14:54] <qense> jcastro: indeed
[15:17] <jcastro> qense: does that icon thing have a bug, is hyperair aware?
[15:19] <qense> jcastro: dashua brought it up and warned vish who warned me. I sent the problem back to vish since he manages the icons in humanity-icon-theme, which is where the fault lies.
[15:19] <qense> the icon name needs to be changed there
[15:19] <jcastro> oh ok, just making sure someone's on it!
[15:19] <jcastro> vish is very thorough though so we're good. :D
[15:20] <qense> yeah, it will turn out richt
[15:33] <vish> ;)
[15:42] <vish> jcastro: Bug 538725 , i wasnt sure if seb128 would do an update for this renaming , if he is free we can push it today ;)
[15:42] <ubot4> Launchpad bug 538725 in humanity-icon-theme (Ubuntu) (and 1 other project) "Banshee monochrome icon needs renaming (affects: 2)" [Undecided,New] https://launchpad.net/bugs/538725
[15:43] <seb128> vish, no, that can wait after beta
[15:43] <seb128> banshee is not used in the default installation
[15:43] <vish> yeah, my thoughts too :)
[15:43] <seb128> and it's only a minor graphical issue
[15:47] <seb128> jcastro, the bluetooth applet icon issue has been fixed by jpetersen, fix in bzr and uploaded to lucid for beta if they accept it now
[15:47] <seb128> jcastro, it looks slick without those 2 icons ;-)
[16:48] <kitallis> https://lists.launchpad.net/ayatana/msg01012.html
[16:52] <kitallis> MacSlow|errand ^
[16:59] <kitallis> vish ^
[17:01] <vish> kitallis: 2 - is forbidden ;)  notify-osd allows click-thorough
[17:01] <kitallis> yeah, i know
[17:01] <kitallis> just a thought
[17:02] <vish> kitallis: for more ideas , have a look at brainstorm and wishlist bug reports on launchpad
[17:03] <vish> kitallis: for notify-osd  , MacSlow is the main guy you need to be talking to and mpt who controls the design
[17:03] <vish> s/controls/specifies
[17:04] <kitallis> yeah, well, i just put it up there
[17:04] <kitallis> i doubt design manipulations in a gsoc project
[17:04] <kitallis> cause, well it takes a lotta time and planning
[17:05] <kitallis> but, don't we all need a little configuration ability
[17:59] <jcastro> seb128: I knew they would look better without the icons!
[18:00] <seb128> ;-)
[18:16] <MacSlow> kitallis, I know and read this... but I'm not the once deciding about that sort of thing.
[18:17] <MacSlow> kitallis, do you know the reasoning behind notify-osd being _not_ customizable? Just wondering about the scope of your initial research
[18:20] <kitallis> MacSlow: probably because apps may have different configurations?
[18:22] <MacSlow> kitallis, no... first notifications are just that... notifications (no full dialogs), second... defaults should be so well chosen that the majority of users don't feel the need to be changing them, third every configuration option add code-paths that neede to be covered by test (automated ones and test be users actually using them)
[18:23] <MacSlow> "just add this option, it's not much work" has the very nasty potential to cause code-paths that may rot and quickly become unmaintained... we want to avoid that... also a kind of anti-bloat-ware attitude :)
[18:24] <davidbarth> kitallis: hi
[18:24] <MacSlow> kitallis, I don't want to go into further detail as all of this is either stated on the spec or has been discussed already in the ayatana-list
[18:24] <kitallis> well, a "defaults should be so well chosen" doesn't seem like the best approach either?
[18:24] <davidbarth> kitallis: i think you're proposed gsoc project is actually going in the opposite direction of what i think our design team was going to
[18:25] <davidbarth> ie, not having user settings at all
[18:25] <kitallis> well, i just figured that, because me, i find hard coded defaults kinda annoying
[18:26] <davidbarth> and that's mostly by design
[18:26] <MacSlow> kitallis, notify-osd is OpenSource... you can go ahead and create a fork for you own needs... and then let community-popularity decide :)
[18:27] <davidbarth> the idea at the start is that notifications should be so basic to the interface, that just one version would be needed
[18:27] <MacSlow> kitallis, I am not sure why you made this into a GSoC-propsal
[18:27] <davidbarth> and if that doesn't work in certain circumstances, to change apps or adopt a different approach, instead of going "oh well, i'll add an option then"
[18:27] <davidbarth> it may sound a bit surprising at first
[18:28] <kitallis> i obviously didn't know about the strong devotion for that strict design rules
[18:28] <MacSlow> kitallis, that's the beauty of OpenSource... if you don't like something... change it... I do that with a couple of tools, libraries I use myself
[18:28] <kitallis> and defaults
[18:28] <davidbarth> kitallis: no worries
[18:28] <kitallis> oh, well
[18:28] <MacSlow> kitallis, np... just grab the code and hack away
[18:28] <kitallis> i'll just dump the gsoc idea atleast.
[18:28] <davidbarth> kitallis: but that's been a topic of discussions quite a few times on the list
[18:29] <davidbarth> kitallis: i think there are other ubuntu project that you could help with
[18:30] <davidbarth> kitallis: projects
[18:30] <davidbarth> kitallis: for the desktop aspects we're working on, you really want to check opportunities with mpt on the design team
[18:30] <kitallis> i really love the OSD
[18:31] <davidbarth> kitallis: hey ;) thanks
[18:32] <kitallis> see, that.
[18:32] <kitallis> i just wish i could change that irssi ping notif up there :P
[18:32] <MacSlow> kitallis, irssi? What's that?
[18:33] <kitallis> IRC client?
[18:34] <MacSlow> kitallis, irssi pushes a notification if you've been addressed on an IRC-channel?!
[18:34] <MacSlow> kitallis, that sounds rather like a candicate to get support for the messaging-menu
[18:34] <kitallis> yeah, it's just a little perl script
[18:35] <kitallis> it's not officially supported if i'm not wrong
[18:35] <MacSlow> kitallis, this really feels like it should integrate with the messaging-menu instead of directly pushing a notification via libnotify
[18:36] <MacSlow> kitallis, tedg will gladly point you to the right document-pages on the wiki, if you're interested in this
[18:37] <kitallis> yeah, sure.
[18:37] <kitallis> wait, just a second, i was eating dinner all this while, kinda immobile :P
[18:37] <tedg> kitallis: MacSlow: Yeah the problem with libindicate is that it requires the process to keep running, while libnotify is more "fire and forget"
[18:38] <tedg> So for things like irssi it can't just be a triggered perl script.
[18:40] <MacSlow> tedg, ah... right... forgot that detail for a bit.


[15:16] -SwissBot:#ubuntu-news- ::Planet:: Scarlett Gately Moore: KDE Snaps, Debian uploads and much more in the works! @ https://www.scarlettgatelymoore.dev/kde-snaps-debian-uploads-and-much-more-in-the-works/


[08:34] <flocculant> jjfrv8: https://bugs.launchpad.net/ubuntu-manual-tests/+filebug make sure testcase id# is there somewhere :)
[11:41] <bluesabre> hey flocculant
[13:09] <flocculant> hi bluesabre
[13:22] <jjfrv8> flocculant, bug 1514417 opened and merge proposal submitted.
[13:22] <jjfrv8> I forgot to link the bug to the MP :(
[13:28] <flocculant> jjfrv8: thanks jjfrv8 - I linked it - approved it - merged it - updated tracker
[13:29] <jjfrv8> :D
[13:30] <flocculant> jjfrv8: big thanks - so much better when someone does the fiddling first :p
[13:32] <jjfrv8> now if I can just remember which settings I've screwed up before I file bugs :|
[13:32] <flocculant> ha ha ha
[13:33] <flocculant> why do think I've got about 6 billion vm's in different states :D
[13:35] <akxwi_dave> lol not just me then.. :-)
[13:37] <knome> for anybody interested, the tracker code is now in a branch under the website project in LP
[13:37] <knome> Unit193, pleia2, bluesabre, ochosi: ^
[13:38] <flocculant> nice :)
[13:39] <flocculant> even nicer if the one who turned up the other day wanting to help does that :)
[13:52] <akxwi_dave> knome : Nice bit of coding there.. :-)
[14:23] <knome> akxwi_dave, ta
[14:23] <knome> ok, time to go grocery shopping
[14:23] <knome> hf
[14:27] <akxwi_dave> enjoy...
[14:28] <flocculant> akxwi_dave: was talking to someone the other day - who was a bit all at sea with testing
[14:29] <flocculant> suggestion was running a session for people - wonder if you'd like to take that as a work item to set up and advertise for us
[14:29] <flocculant> you can use the social media stuffs
[14:29] <flocculant> I'd suggest an irc session - people can connect easily via the tracker
[14:39] <akxwi_dave> Yep, I can do...
[14:39] <flocculant> excellent - just shout when you need something :)
[14:39] <akxwi_dave> will do..  I'll get some ideas set up and let you know.
[15:26] <akxwi_dave> When are we wanting to start testing in situe upgrade from 14.04 to 16.04?
[15:38] <flocculant> akxwi_dave: I'd not point people at that till at least a beta
[15:39] <akxwi_dave> No worries, was thinking more about myself for the testing
[15:39] <flocculant> if someone's brave enough or foolhardy enough to do it - then I'd not stop them
[15:39] <flocculant> but currently we're really half and half
[15:55] <akxwi_dave> :-)
[17:58] <pleia2> knome: thanks re: tracker, I don't even remember how we got it put on the server XD
[20:51] <knome> pleia2, i pushed it :P
[20:52] <knome> pleia2, it *should* be safe now to pull the branch there on updates too, configuration files have only examples on tracker
[21:00] <flocculant> evening knome
[21:03] <knome> hey flocculant
[21:04] <flocculant> I even looked at the tracker stuff :p
[21:05] <flocculant> just looked you understand ;)
[21:06] <knome> ;)
[21:08] <flocculant> one thing to try and get my head around is enough
[21:09] <knome> heh
[21:12] <slickyma1ter> knome, ack the automatic translations export
[21:12] <flocculant> hi slickyma1ter
[21:12] <slickyma1ter> hey flocculant
[21:23] <slickyma1ter> krytarik, go ahead and change those two directories names
[21:23] <slickyma1ter> it makes perfect sense
[21:23] <slickyma1ter> knome ^^
[21:28] <ochosi> evening all
[21:28] <slickymaster> hey ochosi
[21:29] <flocculant> hi ochosi
[21:29] <ochosi> how're things?
[21:29] <flocculant> good here
[21:30] <ochosi> jjfrv8: thanks - an update for xfpm 1.4.4 would be very welcome indeed! (although the changes shouldn't be too dramatic)
[21:43] <knome> slickymaster, ack
[21:44] <slickymaster> will you be around tomorrow knome?
[21:44] <knome> mm, at some point of the day or evening, yes
[21:45] <slickymaster> I'll ping then. I was thinking that we could have a talk about the ubiquity translations
[21:46] <knome> or we can have it today if you have time
[21:46] <slickymaster> little one is with me, today knome
[21:46] <slickymaster> and it's about time to start the all bed time fight
[21:47] <slickymaster> and tbh I'm a bit tired also
[21:47] <knome> lol
[21:47] <knome> good luck then
[21:48] <slickymaster> thanks knome
[22:14] <flocculant> knome: any thoughts on when we'll get the contributor docs live?
[22:15] <knome> pleia2, ping
[22:19] <flocculant> ochosi: any thoughts on getting the poll done before the next meeting?
[22:19] <flocculant> knome: one more :P
[22:20] <knome> yes?
[22:20] <flocculant> so if we're not doing team updates anymore in a meeting
[22:20] <knome> yep
[22:20] <flocculant> what do we do about people wanting to tell things in the meetings?
[22:20] <knome> they can tell them in the updates section
[22:20] <knome> let me explain the idea once more
[22:21] <knome> the "team updates" part i wanted to drop was the mechanical copy-paste of done work items into the meeting
[22:21] <flocculant> so still doing updates - just not blurbing what's a bp task?
[22:21] <knome> because now with the tracker, they are there already
[22:21] <knome> and sure, if any of those items affect many people, it's probably a good idea to tell you did that
[22:21] <flocculant> yep - that was what I thought - just making sure
[22:21] <knome> or if you need comments
[22:22] <flocculant> oic the meeting page has changed
[22:22] <knome> and yes, we can/should still do updates if they are relevant past the "this work item is done" level
[22:22] <knome> so the idea was not to stop people from doing any communication
[22:22] <knome> but to save their time in having to collect these mechanical updates
[22:23] <flocculant> don't know if you caught the backlog - akxwi is going to set up a session in here for 'testers'
[22:23] <knome> and instead let them have a bit more time to update them in the blueprints
[22:23] <flocculant> yep
[22:23] <knome> where they are always live
[22:23] <knome> well, at least ideally live
[22:23] <flocculant> yea :)
[22:23] <knome> re: session, that must have slipped
[22:23] <flocculant> been trying to put task things on there - even if I then mark it done
[22:23] <knome> yeo
[22:24] <knome> yep*
[22:24] <flocculant> knome: yea - someone was talking to me the other night about that
[22:24] <knome> and then if you think what is relevant for a BP work item or not
[22:24] <flocculant> yea
[22:24] <knome> i think the line is about "if it's something people outside team might be interested or it might affect them, it's suitable for a work item"
[22:25] <knome> and yeah, i just added an item that was straight done today - the tracker code being in a branch
[22:25] <flocculant> I've been putting testcase bugs on mine - if for no other reason that it's easy to see what's going on internally
[22:25] <knome> yep
[22:26] <knome> i haven't noticed that the amount of work items would have been too big yet to actually find what you are looking for
[22:26] <knome> once we have 3000 items, then we might be off the rails...
[22:26] <flocculant> yep :D
[22:26] <knome> but yeah, listing more stuff there isn't a bad idea
[22:26] <flocculant> and really really tired too
[22:26] <knome> at the end of the cycle it also provides as a list on who did what
[22:26] <knome> and a place for personal evaluation as well
[22:27] <flocculant> yea I guess so
[22:27] <flocculant> for those that would do that
[22:27] <knome> i mean i do look at a cycles BPs and see what i have accomplished in the last 6 months
[22:27] <flocculant> yep
[22:27] <flocculant> what you do is different to last cycle :)
[22:27] <knome> and think whether my time contribution was in level with that
[22:28] <flocculant> what qa does is re-rinse
[22:28] <knome> or if i should start using less time but be more effective when i do work on stuff
[22:28] <flocculant> yea
[22:28] <knome> and also if i met enough of the goals set
[22:28] <flocculant> tracker is certainly a really useful tool
[22:28] <knome> usually 10-20% of the work items on a team level are left undone
[22:29] <flocculant> right
[22:29] <knome> so if i personally hit that level, i guess i've done well enough
[22:29] <flocculant> :)
[22:29] <knome> but yeah, there are a lot of good things in tracking
[22:29] <knome> and i'm kind of happy that we built our own
[22:30] <flocculant> I think it's awesome tbh
[22:30]  * knome bows
[22:30] <flocculant> kudos :)
[22:30] <knome> i like the event markers in the burndown
[22:30] <knome> they are more useful than you might think
[22:30] <flocculant> and I don't even remember now what it was that I was missing :D
[22:31] <knome> http://status.ubuntu.com/ubuntu-v/group/topic-v-flavor-xubuntu.html
[22:31] <flocculant> I find them useful - if no more than a visual cue that a milestone is soon
[22:31] <knome> yep
[22:31] <ochosi> knome: oh right, thanks for the reminder. i'll try to set something meaningful up asap
[22:31] <ochosi> just have been really busy at work and at home
[22:31] <knome> ochosi, i think you mean flocculant
[22:31] <flocculant> :)
[22:31] <flocculant> cos I had that annoying itch :D
[22:32] <ochosi> oh well, there you go, sleep deprivation
[22:32] <flocculant> ochosi: if it helps I'm off all week and could do it if you wanted :)
[22:32] <ochosi> oh, actually that'd be great. let me quickly take a peek at that spec again..
[22:33] <flocculant> ochosi: and after 26 years - I am just getting out of that deprivation cycle :p
[22:33]  * knome looks at the v status page, notes the amount of work items per person and sighs
[22:33] <flocculant> tomorrow \o/
[22:33] <ochosi> well, lucky you... :)
[22:33] <flocculant> :)
[22:34] <flocculant> last one hits 16 tomorrow
[22:34] <knome> cool, congrats
[22:35] <ochosi> hehe
[22:35] <ochosi> nice
[22:35] <ochosi> flocculant: so yeah, that page looks right. please just make sure that you mention that there's no "Option C: Advocate your player of choice from the list on that page" in the poll text
[22:36] <ochosi> i'd prefer to avoid that, and frankly, having that list on that page somehow suggests that
[22:36] <flocculant> ochosi: I could edit
[22:37] <flocculant> build new page and just have it on the choice page as a link
[22:37] <ochosi> yeah, or use the old W page as a reference there
[22:37] <flocculant> that said I will probably doodle poll it - and it will just be A or B
[22:37] <flocculant> with the link
[22:37] <ochosi> oh ok, so no mailinglist?
[22:37] <ochosi> but the doodle doesn't allow for real authentication, right?
[22:38]  * ochosi hasn't doodled much in his time
[22:38] <knome> i would go with ML, it's then archived forever there
[22:38] <flocculant> well
[22:38] <flocculant> I really didn't want to ml it
[22:39] <knome> ;)
[22:39] <flocculant> but will if I had to
[22:39] <flocculant> I could do it with condorcet :D
[22:39] <knome> i won't force anybody to do that if they don't want to, but i would say it would be the simplest
[22:39] <knome> and the archival thing is great, then we don't rely on anybody else keeping the data up
[22:39] <flocculant> simplest to run yea :D
[22:39] <flocculant> I guess so
[22:39] <knome> and isn't too hard to figure out the results either
[22:39] <knome> it's 14 people at max voting
[22:40] <knome> one of them being you :P
[22:40] <flocculant> yea
[22:40] <flocculant> oh noes
[22:40] <flocculant> that tips me over the balance ...
[22:40] <knome> oops, did i just talk you into it :P
[22:40] <flocculant> can count to 13 with some forks :p
[22:40] <knome> yup
[22:41] <knome> and you can use your legs too!
[22:41] <flocculant> all three?
[22:41] <knome> :X
[22:41] <knome> i didn't say that!
[22:42] <flocculant> :)
[22:46] <flocculant> ochosi: I'll get that sorted out tomorrow then - do you want to see before I send it to list?
[22:48] <ochosi> flocculant: nah, that's ok, i trust you with that
[22:48] <flocculant> okey doke :)
[22:48] <knome> ochosi, MISTAKE
[22:48]  * knome hides
[22:48] <flocculant> too late
[22:48] <flocculant> in the logs :p
[22:49] <ochosi> and also, i don't take these "default application xy" things as serious anymore as i used to
[22:49] <flocculant> :)
[22:49] <ochosi> i mean yeah, it's good to have good defaults
[22:49] <flocculant> ochosi: LO took it out of you did it?
[22:49] <flocculant> did me :p
[22:49] <ochosi> but especially with this one, there is no pleasing people
[22:49] <flocculant> yea for sure
[22:49] <flocculant> the only way I could be pleased would be if we QT'd
[22:50] <flocculant> personally ofc
[22:50] <ochosi> LO might actually be for the better, i think it's useful for many and the alternatives were bug-plagued and not comparable feature-wise
[22:50] <flocculant> yea
[22:50] <ochosi> yeah, well, meh :)
[22:50] <flocculant> I think that was wise all in all
[22:50] <flocculant> ha :)
[22:50] <ochosi> we already have FF and LO which don't use our toolkit
[22:50] <flocculant> yep
[22:50] <ochosi> let's not go overboard on that one
[22:51] <flocculant> ochosi: ha ha ha
[22:51] <ochosi> ;)
[22:52] <flocculant> I might argue personally that if you want to use foo then do so - but I'd not argue that point for Xubuntu :)
[22:52] <flocculant> unless we need Muon
[22:52] <bluesabre> well, they do use our toolkit to a point
[22:52] <bluesabre> firefox is certainly built on gtk
[22:52] <flocculant> bluesabre: good evening :)
[22:52] <bluesabre> hey hey
[22:52] <ochosi> oh wow, the bluesabre sneaks out of the shadows
[22:52] <flocculant> he's been doing that lately
[22:52] <bluesabre> always watching from the shadows once I get home
[22:53] <flocculant> I think it's the loss of summer time :p
[22:53] <bluesabre> and turn the lights on
[22:53] <ochosi> bluesabre: i know, LO uses gtk as well, but in a very very very old-fashioned (and partly weird) way
[22:53] <flocculant> bluesabre: cos it's dark ...
[22:53] <bluesabre> ochosi: its getting better though with each release
[22:53] <ochosi> bluesabre: yeah, well the gtk3 version still looks like crap tbh ;)
[22:53] <ochosi> i tested it on the LO hackfest
[22:54] <ochosi> cause obviously i had to make sure my patch worked with 2 and 3 (which it did ofc)
[22:54] <ochosi> but they're very busy with all their platforms
[22:54] <ochosi> anyway, no problem for us, we're gtk2 mostly anyway
[22:54] <bluesabre> mhm
[22:54] <ochosi> (i should really re-consider my overuse of the word "anyway")
[22:55] <knome> nope
[22:55] <ochosi> btw, one more thing for the poll (just a personal note): if we would still pour resources into gmusicbrowser then dropping it would free those up so we could further improve parole
[22:55] <ochosi> but since we don't do that anymore, i guess this advantage is gone :)
[22:56] <bluesabre> :)
[22:56] <ochosi> (and ofc if we still poured resources into gmb, we might not want to drop it anymore)
[22:56] <ochosi> s/anymore//
[22:56] <SwissBot> ochosi meant: "(and ofc if we still poured resources into gmb, we might not want to drop it )"
[22:56]  * ochosi really needs some sleep
[22:56] <bluesabre> :D
[22:56] <ochosi> bluesabre: don't get kids, they eat your sleep!
[22:57] <knome> SwissBot, seriously?
[22:57] <flocculant> :)
[22:57] <bluesabre> ochosi: you'd probably be jealous that I've been getting 8-9 hours of sleep a night lately
[22:57] <bluesabre> :p
[22:57] <knome> i slept 14 hours two nights ago
[22:58] <bluesabre> :o
[22:58] <flocculant> bluesabre: I have been assiduously ignoring that I get lie-ins now
[22:58] <flocculant> didn't think it would be fair
[22:58] <bluesabre> :)
[22:59] <ochosi> yeah well, otoh she has that "awwwwh, look at the baaaaby!" effect, so i guess the higher endorphine level makes up for *some* of the sleep deprivation...
[22:59] <flocculant> :)
[22:59] <flocculant> they do that for sure
[23:00] <flocculant> ochosi: do you want me to edit the xx spec to lose the list of media players?
[23:00] <ochosi> well that'd only be my suggestion, what do the others here think?
[23:00] <flocculant> might be better
[23:00] <flocculant> is my thought
[23:00] <flocculant> bluesabre knome ^^
[23:01] <knome> fine with that
[23:01] <bluesabre> go for it
[23:01] <flocculant> k
[23:04] <flocculant> ok did that
[23:04] <flocculant> I'll get the mail out tomorrow sometime
[23:05] <bluesabre> nice
[23:11] <ochosi> bluesabre: btw, i agree we should offer to launch light-locker if it isn't running
[23:11] <ochosi> e.g. with a nice infobar
[23:11] <bluesabre> yup
[23:11] <ochosi> could be the last new feature before making 1.5 stable
[23:11] <bluesabre> I'll see about getting something together for that this week
[23:12] <ochosi> that'd be awesome!
[23:12] <bluesabre> I've been more busy than lately, so that might slip, but will *try*
[23:12] <bluesabre> s/than//
[23:12] <SwissBot> bluesabre meant: "I've been more busy  lately, so that might slip, but will *try*"
[23:13] <bluesabre> :D
[23:14] <flocculant> heh
[23:16] <flocculant> not that I mean this at all personally, but if team is going to vote on this - lderan has been off doing life for a cycle
[23:17] <flocculant> maybe that team should have expiry dates
[23:19] <ochosi> flocculant: good point, i've actually discussed this with him specifically repeatedly
[23:20] <ochosi> i'll send him an email now and deactivate him so he has to take some action to get back on the team and voting rights
[23:20] <flocculant> just seems a bit unfair when there are people constantly about not in team - but 'about'
[23:20] <flocculant> k
[23:20] <knome> then what about jackson/micah? not sure what their actual contributions have been
[23:21] <knome> if we go this path, that is...
[23:21]  * flocculant feels a bit like someone with a pitchfork :(
[23:21] <ochosi> knome: yeah, arguably i haven't had any PMs with them about this yet
[23:21] <ochosi> so i wouldn't want to go straight ahead and deactivate them
[23:22] <knome> of course not
[23:22] <ochosi> but i agree that i/we should talk to them
[23:22] <flocculant> then perhaps expiry dates would help - not 6 months as that's how long the processes gives, so someone could be active at start of a cycle
[23:22] <knome> i think that's a bit meh for -team
[23:22] <flocculant> perhaps so
[23:23] <knome> it is a community after all and everybody should judge their own contributions
[23:23] <flocculant> just putting the hat on
[23:23] <flocculant> yep of course
[23:24] <ochosi> yeah, we're still in a range where we can discuss things with people individually
[23:24] <ochosi> i mean we're actually not that many
[23:24] <knome> yep
[23:24] <ochosi> i wouldn't want to enforce too much of a policy here
[23:24] <flocculant> good
[23:24] <knome> and i'd rather encourage people to pick up contributing again than felt excluded
[23:24] <flocculant> was just bringing it up
[23:25] <knome> yep
[23:25] <knome> good to talk about stuff
[23:25] <flocculant> cos - I'm about to send a mail saying only team can vote :)
[23:25] <flocculant> which made me think about it
[23:25] <knome> inactive members are problematic also for the quorum
[23:26] <flocculant> yea
[23:27] <bluesabre> yup
[23:28] <ochosi> i'm sending this email privately fwiw
[23:28] <flocculant> ofc
[23:28] <ochosi> but just so you know, i naturally invited him to just pick up contributing again - i really think re-earning your once held membership should be very easy and i think we should always emphasize that
[23:29] <knome> ++
[23:29] <bluesabre> yes, that sounds very reasonable
[23:29] <flocculant> ochosi: yep totally
[23:30] <ochosi> ok, so now we're 12
[23:30] <flocculant> doesn't the bit in the 'processes' say that?
[23:30] <ochosi> what a biblical number...
[23:30] <flocculant> oh man - so what's quorum? 7?
[23:30] <knome> yes
[23:30] <ochosi> i'll let you figure that out and get some sleep instead ;)
[23:30] <flocculant> \o/
[23:30] <ochosi> (it's really not a hard math problem anyway)
[23:30] <knome> so 7 people need to vote, 4 on the same side... :P
[23:30] <flocculant> ochosi: good night :)
[23:30] <ochosi> night y'all!
[23:31] <flocculant> knome: ha ha
[23:31] <knome> nighty ochosi
[23:31] <Unit193> knome: Nice.
[23:31] <flocculant> evening Unit193
[23:31] <knome> hullo Unit193
[23:32] <flocculant> while we've got people awake - and Unit193 will hate me now ... who's going to prod about core next?
[23:33] <pleia2> knome: hey
[23:33] <knome> pleia2, hai
[23:33] <pleia2> another airplane in 9 hours, so kind of chaos day x_x
[23:33] <knome> so we've been preparing this contributor documentation in the docs branch for some time
[23:33]  * pleia2 nods
[23:34] <knome> could we sit down some time and see how we want it done in the docs subdomain?
[23:34] <flocculant> pleia2: I hope you have shares :D
[23:34] <pleia2> knome: I'm around next week, starting Tuesday
[23:34] <knome> pleia2, oki, ping me then :)
[23:34] <knome> flocculant, ^ also
[23:34] <pleia2> knome: so we can talk about that, and some other thing that's on our list (something about social media or somethin?)
[23:35] <knome> yeah
[23:35] <knome> is tuesday good or fo you want a buffer of some days
[23:35] <flocculant> knome: yep - I'd like to be about too if I'm awake :)
[23:35] <flocculant> just to nose in ofc
[23:35] <knome> what did i write
[23:35] <knome> :P
[23:35] <knome> ... good for you or do ...
[23:35] <flocculant> :)
[23:40] <bluesabre> nighty ochosi
[23:41] <bbrawner> Hey knome, you around?
[23:41] <knome> bbrawner, i am
[23:41] <bbrawner> How's it going?
[23:42] <knome> no complaints
[23:42] <bbrawner> Haha that's always good
[23:42] <bbrawner> I've been looking around here: http://tracker.xubuntu.org/#tab-details/spec=xubuntu-x-web
[23:42] <bbrawner> And I haven't been able to find the code haha
[23:42] <bluesabre> flocculant, Unit193: if we know what needs to be asked, I can start poking folks
[23:42] <bbrawner> Am I missing something?
[23:43] <knome> https://code.launchpad.net/~xubuntu-website/xubuntu-website/tracker
[23:45] <bbrawner> Thanks knome!
[23:45] <knome> np
[23:46] <Unit193> bluesabre: Well they *were* supposed to review it, but that never happened.  We fixed it to be more like what they wanted, as far as we can tell.  I'm pretty sure it's out of sync now, but I have no intention on fixing it now.
[23:46] <flocculant> bluesabre: afaik - we did what they wanted us to - just needs pushing
[23:46] <flocculant> that ^^
[23:48] <bluesabre> Unit193: cool, I'll take a look at it and see how far behind we are. Then we can give ochosi the stabbing stick
[23:49] <flocculant> well - I'm off now
[23:49] <flocculant> night all
[23:49] <bluesabre> night flocculant
[23:49] <flocculant> and hi bbrawner :)
[23:49] <knome> nighty flocculant
[23:49] <bbrawner> Hey flocculant!