[10:52] <ochosi> morning everyone
[10:58] <elfy> morning ochosi - and a glorious one it is too :)
[10:58] <ochosi> you mean weather-wise?
[11:00] <ochosi> or is there any other reason that i'm not aware of that this would be a glorious one
[11:22] <elfy> weather wise :)
[15:03] <bluesabre> morning folks
[15:06] <elfy> hi bluesabre 
[15:08] <bluesabre> hey elfy
[15:08] <bluesabre> how are things?
[15:10] <ochosi> hey bluesabre 
[15:10] <bluesabre> hey ochosi
[15:10] <elfy> good thanks bluesabre 
[15:11] <ochosi> bluesabre: do i remember correctly that your ll branch was ready for testing?
[15:11] <bluesabre> ochosi: correct
[15:11] <ochosi> got a sort of test-case for it?
[15:11] <ochosi> i mean anything in particular that should be tested and if so, how?
[15:12] <elfy> if it's ll for lightlocker I would suggest - testing it in as many different ways, on as many different setups for the whole of the cycle ;)
[15:13] <bluesabre> ochosi: clone the branch, make and run.  Without the dconf bindings there should be a warning on the terminal that settings will not be stored
[15:13] <bluesabre> then make install
[15:14] <bluesabre> run again, with different parameters, the settings should change (and can be viewed from dconf-editor: /apps/light-locker
[15:14] <bluesabre> and then while its running, if you change the settings in dconf-editor, they should take effect immediately
[15:14] <ochosi> elfy: it is, it's just about merging a branch into git master and subsequently doing a development release. that dev-release can then be tested by a broader audience ;)
[15:15] <ochosi> bluesabre: ok, will do
[15:15] <bluesabre> in dconf-editor, the settings have descriptions, if that helsp
[15:16] <elfy> ochosi: shall wait patiently for it then
[15:16] <bluesabre> *helps
[15:16] <ochosi> bluesabre: i suppose i need gsettings/master?
[15:16] <ochosi> or just master?
[15:17]  * ochosi is confused
[15:17] <bluesabre> https://github.com/bluesabre/light-locker/tree/master
[15:17] <bluesabre> git forks/merges make extra messes when not careful
[15:17] <elfy> ochosi: you got any opinion on changing package testing this cycle, from what we've done previously, to just letting people get on if they want to - and then when -team want something specific testing asking only for that during the cycle?
[15:19] <ochosi> you mean as opposed to always testing a fixed set of apps?
[15:19] <elfy> yep
[15:19] <elfy> mmm
[15:19] <elfy> no
[15:20] <ochosi> bluesabre: so no compile-options?
[15:20] <elfy> 1 - call for testing - point testers at tracker - then leave that as done
[15:20] <elfy> 2 - when someone pushes something in -team that needs more testing - calling for that as required
[15:20] <elfy> 3 - making use of staging ppa in (2)
[15:20] <bluesabre> ochosi: I think I mentioned that I would add them if I didn't suck at makefiles, was hoping Corsac would add that (or you)
[15:20] <ochosi> bluesabre: 1) run from git tree and get the warning: check.
[15:21] <ochosi> elfy: yeah, that makes sense to me
[15:21] <elfy> cool - it's on agenda for meeting - will want that agreed and tied up quite quickly
[15:22] <ochosi> indeed
[15:23] <ochosi> i might be travelling that day, so can't guarantee i'll be there
[15:23] <ochosi> so here's an early +1 from me
[15:23] <elfy> :)
[15:23] <elfy> that's why I ask these things when I see you - just in case :)
[15:24] <ochosi> good thinking :)
[15:25] <ochosi> bluesabre: 2) running with different parameters takes immediate effect (as seen in dconf-editor): check.
[15:26] <ochosi> how would i see whether changes made from dconf take effect other than by suspending/locking/trying them?
[15:31] <elfy> bluesabre: when you've finished this discussion, if you've got 5 ping me please
[15:35] <bluesabre> ochosi: that's the only way to tell
[15:35] <bluesabre> elfy: what do you need?
[15:37] <ochosi> bluesabre: hmm, so late-locking didn't really work. threw me into a nasty cycle of the greeter failing until i disconnected the external monitor
[15:37] <elfy> just a couple of - 1 vivid still gets the black background, 2nd - what's your opinion on the search direction in mousepad - defaults to down, wonder if both would be better?
[15:37] <ochosi> bluesabre: could also be quite unrelated to your branch though
[15:37] <elfy> ochosi: and does vivid is still pink - need a bug or at least be on blueprint?
[15:37] <bluesabre> ochosi: that would not be because of my branch...
[15:37] <ochosi> vivid shouldn't be pink anymore i though
[15:37] <ochosi> t
[15:37] <elfy> is is
[15:38] <elfy> with today's daily
[15:38] <ochosi> i thought bluesabre had pushed the x-d-s update already which reset that part
[15:38] <bluesabre> today's daily iso... or today with everything updated?
[15:38] <elfy> mmm - probably just the slideshow
[15:38] <elfy> actually - doing half a dozen things at once here
[15:38] <ochosi> :)
[15:38] <bluesabre> we blew away the pink... definitely shouldn't be tehre
[15:39] <elfy> yea - sorry, just the slideshow 
[15:39] <ochosi> bluesabre: guess i gotta check again with lock on suspend if late locking doesn't work so great
[15:39] <ochosi> elfy: ah you mean the images of the slideshow?
[15:39] <ochosi> hm, depends on who updates the slideshow
[15:39] <ochosi> so far knome has been doing that
[15:39] <ochosi> i'd hope he'd do it again
[15:39] <elfy> yea - that'll be late in cycle I'd guess
[15:40] <bluesabre> the slideshow won't be non-pink until after UIF probably :)
[15:40] <elfy> yep ^^
[15:40] <ochosi> would be good to add a workitem for him or -artwork or -docs
[15:41] <elfy> docs probably - I'll add it now 
[15:41] <ochosi> bluesabre: would be cool to add a command to light-locker-command to print the current settings
[15:43] <bluesabre> ochosi: yeah, that makes sense
[15:52] <ochosi> bluesabre: lock on suspend test worked fine
[15:53] <bluesabre> ochosi: also make sure you've killed any running instances of light-locker while you are testing
[15:53] <ochosi> yeah
[15:53] <ochosi> only had the newly installed one running
[15:53] <bluesabre> oh, and elfy, I agree that mousepad should search in both directions
[15:54] <ochosi> and ten started with non-standard option lock-on-suspend, then after updating the settings via dconf-editor
[15:54] <ochosi> so looks good to me
[15:54] <ochosi> brb
[15:54]  * ochosi needs coffee
[16:09] <elfy> bluesabre: do you want me to raise a bug for it?
[16:22] <elfy> bluesabre: assumed so - bug 1390933
[16:23] <elfy> linked with upstream bug
[16:24] <bluesabre> thanks elfy
[16:24] <elfy> off for a while now - have a good Sunday bluesabre :)
[16:24] <bluesabre> thanks, have fun elfy
[16:24]  * bluesabre gets back to getting ready to move
[16:24] <elfy> ooh - moving house?
[16:25] <elfy> good luck with that one ... 
[16:25] <bluesabre> soonish.  Got a new job in another city, getting things together now
[16:26] <elfy> well - as I said - good luck with that :)
[16:26] <bluesabre> thanks :)
[16:26] <knome> elfy, updated the blueprint work item :)
[16:26] <knome> bluesabre, good luck!
[16:26] <bluesabre> knome: I prefer "depinkify"
[16:26] <bluesabre> ;)
[16:27] <elfy> :(
[16:27] <elfy> depinkify was a special word :D
[16:28] <knome> yes, was
[16:28] <elfy> heh
[16:28] <knome> anyway, i plan to do a bigger update than just make it blue again
[16:28] <knome> so the new description fits better
[16:28] <elfy> I assume as much, just got it on the blueprint :)
[16:29] <knome> yep
[16:29] <knome> just came home
[16:29] <elfy> anyway ... 
[16:29] <elfy> turquoise ... 
[16:29] <knome> i'll keep that in mind
[16:29] <elfy> lol
[16:29] <knome> maybe we can make the slideshow/wallpaper more towards that scheme
[16:30] <knome> whether ochosi wants to make the greybird highlights speicifically match that is a different thing
[16:30] <elfy> then back to reddish for vampire ;)
[16:30] <knome> hah
[17:21] <dkessel> bluesabre: had any time to look after the GUI item IDs for catfish yet?