[10:09] <akxwi-dave> morning
[12:25] <flocculant> davmor2: are you the oem whizzkid? if so - do you test oem and encryption? 
[12:26] <davmor2> flocculant: no due to the fact that an oem would have to set an encryption key password which would null and void the whole point of the encryption :)
[12:26] <davmor2> flocculant: oem is a mode that is used as stand alone, you can test with encryption it's just not the typical way it would ship
[12:27] <flocculant> that was what I thought - just checking :)
[12:27]  * flocculant toddles of out again
[17:10] <flocculant> knome: when you've got 30 minutes ish :)
[17:49] <flocculant> bluesabre: something occurs to me - 14.04 goes EOL, I assume 3years after release, which is in ~2 months - do we start telling users soon? 
[19:35] <knome> flocculant, yes?
[19:35] <knome> :)
[19:36] <knome> my take on EOL is that we can wait until the EOL date as the core system is supported anyway
[19:36] <knome> it's not like the world collapses 3 years after the release
[19:36] <knome> but we should probably start preparing the news etc.
[19:38] <flocculant> ack on core being supported
[19:38] <flocculant> so we wait till it's EOL - then tell people at the same time as it being EOL - instead of giving some warning?
[19:39] <flocculant> that's friendly ;)
[19:39] <knome> heh
[19:39] <knome> well, i'll happily hear other opinions
[19:39] <knome> i just don't know if it's sensible to shout that 14.04 will be EOL very early either
[19:39] <knome> at least before we have a new thunar SRU on 16.04
[19:40] <flocculant> well it's LTS - and it goes EOL in ~2 months
[19:40] <flocculant> and yea - would be goot to sru thunar for 16.04 absolutely
[19:41] <flocculant> just got my head in taskmanager for a few minutes for ochosi 
[19:42] <knome> part of my rationale is that we don't support releases for 3 years because we don't have the manpower to do more
[19:42] <knome> but in case we don't feel like the next LTS is quite ready (which is unforunate), we still *can* as the core is supported to
[19:42] <knome> it would be different IMO if the ubuntu core was also only supported for 3 years
[19:43] <knome> then we would definitely want to make sure people upgrade soon
[19:48] <flocculant> ochosi: so played about with columns add yea as you saw - all over the place http://paste.ubuntu.com/23942957/
[19:48] <flocculant> knome: yea I would agree with that sentiment
[19:48] <knome> so maybe schedule an article a few weeks before the EOL date and another one on EOL, or sth
[19:49] <flocculant> 4 would be the week prior to beta 1 freeze
[19:50] <flocculant> final beta
[19:50] <knome> so we don't want 3 weeks at least
[19:50] <flocculant> nearly had kittens then - cos that's next week :D
[19:51] <flocculant> 3 weeks would be final beta week
[19:51] <flocculant> but yea - some time before then again on eol makes sense
[19:52] <flocculant> anyway - was a passing thought mostly brought on by me remembering the last couple of eol's ' oh - we're eol now - best tell people'
[19:52] <knome> mhm
[19:52] <knome> yep
[19:53] <flocculant> so - and I think we've possibly had this discussion previously ...
[19:53] <flocculant> anyway to have some sort of freeform text box at http://dev.xubuntu.org/#tab-qa
[19:54] <flocculant> bit sort of blueprint whiteboardish
[19:54] <knome> right'o
[19:54] <knome> will look at that
[19:55] <flocculant> knome: reasoning for that is things like the folder/image issue we're seeing in desktop settings
[19:56] <flocculant> someone mentioned it to me - I looked - asked ochosi where to report it - then it got forgotten by everyone - then Simon mentioned it - then Sean did - but nothing had been written down anywhere
[19:57] <flocculant> now - seems that we just need somewhere to note qa/dev issues to me until reported 'somewhere'
[19:57] <knome> yep, that seems all fair and doable
[19:57] <flocculant> if it's loads of work then qa blueprint whiteboard will suffice
[19:57] <knome> nah
[19:59] <flocculant> ok - ta :)
[19:59] <flocculant> I'd rather it was on the tracker - and on the qa tab - seems best place for it till it's properly reported
[20:28] <flocculant> ochosi: moving columsn - seems to be no specific pattern to what works and what doesn't
[20:28] <ochosi> yeah, it's fairly random in my experience too
[20:28] <flocculant> same with hiding/adding - though at some point task disappears and then comes back 
[20:28] <ochosi> but it's sorta broken i guess
[20:29] <ochosi> as far as i can tell it's even broken in the current release
[20:29] <ochosi> restarting the taskmanager fixes the visible columns i think
[20:29] <flocculant> ochosi: well - I didn't manage to break current
[20:32] <ochosi> oh
[20:32] <ochosi> humm
[20:32] <ochosi> btw, any news from robert on the greeter issue?
[20:32] <flocculant> ochosi: noticed something else - in current - box for the tick, in git - no box
[20:32] <ochosi> box for the tick?
[20:32] <flocculant> ochosi: nope - waiting for him to wake a bit then ping him
[20:32] <ochosi> i guess i need a screenshot for that
[20:33] <flocculant> ochosi: where you choose which columns 
[20:34] <flocculant> http://i.imgur.com/MxPoE67.png is current
[20:34] <flocculant> http://i.imgur.com/Ph77Svs.png is git
[20:40] <ochosi> that's just gtk3 (current) vs. gtk2
[20:41] <ochosi> you could build git with "./autogen.sh --enable-gtk3" then they would look the same
[20:41] <flocculant> ochosi: aah ok :)
[20:55] <flocculant>  ochosi bluesabre - reply from robert in -desktop re locking bug
[20:56] <ochosi> well if he has it on his "to fix" list, i'm happy
[20:56] <ochosi> i trust him
[20:56]  * flocculant wonders if a mail to our testers re that and maybe replacing with gnome-screensaver or something in the interim would be an idea 
[20:56] <flocculant> ochosi: yea :)