[08:56] <slickymasterWork> knome: you around?
[09:00] <slickymasterWork> knome, do you think it's worth to file a new bug against ubiquity-slideshow referring that the Utopic ISO welcome slide still referrers to 14.04 and that the last slide still holds a goat image?
[09:02] <ochosi> meh, we'll change the slideshow rather late in the cycle as usual
[09:02] <ochosi> and it'll probably need more work than those two things
[09:03] <slickymasterWork> yes, I know ochosi, just asking if it's worth to do it, so to sort of having some kind of paper trail 
[09:03] <ochosi> i guess i'd rather add an item to a blueprint saying "Update slideshow for 14.10" :)
[09:03] <ochosi> depends a bit on how we want to track our things this cycle
[09:04] <ochosi> from my pov, the blueprints worked fine in 14.04
[09:04] <gry> how do I add a blueprint item?
[09:04] <gry> and why do you mention .10 while the other one of you mentions .4?
[09:05] <slickymasterWork> yeah, agree ochosi It would serve the same purpose 
[09:05] <slickymasterWork> even though we're still going to decide if we're going to be working with Trello
[09:07] <ochosi> you mean trello over blueprints?
[09:07] <ochosi> i'm generally okayish with that, but the whole process-tracking and buglinking can't really be done in trello
[09:07] <slickymasterWork> yes ochosi
[09:07] <ochosi> imo we can use trello within teams, but for the overall performance the blueprints provide a good overview
[09:08] <slickymasterWork> I'm referring to use Trello to keep track of the workflow progress
[09:09] <ochosi> i guess you have to give me an example for that
[09:11] <slickymasterWork> https://trello.com/b/IV66JCHl/xubuntu-qa <- ochosi, this what elfy and I use during the T cycle
[09:12] <slickymasterWork> that's what I was referring to
[09:12] <knome> depends if there is a branch for utopic for the slideshow already or not
[09:13] <slickymasterWork> I think there's already one knome. Let me confirm it
[09:13] <knome> gry, you don't, the team does that
[09:14] <knome> slickymasterWork, would need to log in to trello to see that pad ;)
[09:14]  * knome shrugs
[09:14] <slickymasterWork> knome, yes there is -> https://launchpad.net/ubuntu/utopic/+source/ubiquity-slideshow-ubuntu
[09:15] <knome> good, then i could land that change in today
[09:15] <slickymasterWork> knome, ochosi, give me a sec and I'll add you both to that pad
[09:16] <ochosi> thanks slickymasterWork 
[09:16] <ochosi> i'm already on trello, so it should be straightforward
[09:16] <knome> i'm not on trello though ;)
[09:16] <slickymasterWork> what's your username on Trello ochosi?
[09:17] <ochosi> my realname
[09:17] <slickymasterWork> knome, can you please check your mail?
[09:17] <slickymasterWork> ochosi, Simon or full name?
[09:17] <ochosi> full realname :)
[09:18] <ochosi> don't you think the username "simon" would already have been taken? ;)
[09:18] <slickymasterWork> ochosi: Simon Steinbeib or am I way off :P
[09:18] <ochosi> (note: i wasn't among the first ten users to register on trello )
[09:19] <knome> slickymasterWork, ss or ß
[09:19] <ochosi> s/b/ss
[09:19] <ochosi> it should be Ã anyway
[09:19] <ochosi> err, weird keyboard encoding
[09:19] <knome> yes
[09:19] <slickymasterWork> ok, you're both in
[09:22] <slickymasterWork> knome, another think I wanted to discuss with you is https://bugs.launchpad.net/ubuntu/+source/xubuntu-docs/+bug/1299286
[09:22] <ochosi> that's how i'd imagine it
[09:23] <ochosi> but yeah, the buglinks etc are missing a bit
[09:23] <ochosi> i had a similar board with bluesabre towards the end of 14.04
[09:23] <ochosi> as i said, i think it works well for smaller entities, like teams, to manage the workflow
[09:23] <knome> i think trello can be helpful
[09:23] <slickymasterWork> the only way to do that in trello would be to add full url's to them ochosi 
[09:23] <knome> but the work items are pretty much the same
[09:23] <knome> and they track bug statuses automatically
[09:24] <knome> and everything is linked in to launchpad
[09:24] <slickymasterWork> but on otho you can mail directly the users with tasks pending in Trello
[09:24] <slickymasterWork> s/otho/otoh
[09:25] <slickymasterWork> and that's a good work asset imo
[09:26] <slickymasterWork> knome: when you marked that bug as Wishlist your intention was just to postponed it until .1 cycle or was it something else?
[09:27] <knome> slickymasterWork, both. it's generally not something we *need* to add, or anything critical
[09:27] <knome> people can subscribe to blueprints in launchpad as well
[09:27] <knome> and they get more meaningful mails
[09:27] <knome> from what i've understood
[09:30] <slickymasterWork> yes, they can knome, but with trello you can set deadlines to particular tasks/members within the same 'project/blueprint' which is something that LP blueprints doesn't allow
[09:31] <slickymasterWork> and this feature provides a better control of the workflow within a specific project
[09:32] <knome> actually, LP work items *do* allow specific deadlines...
[09:42] <sidi-valencia> light-locker just failed to lock
[09:42] <sidi-valencia> and prevented me from going to any tty
[09:42] <sidi-valencia> except my X session's
[09:42] <sidi-valencia> which got opened directly
[09:42] <sidi-valencia> scary!
[09:44] <slickymasterWork> damn connection
[14:02] <knome> slickymasterWork, did you see my reply...
[14:02] <knome> "launchpad allows settings deadlines to specific time"
[14:06] <slickymasterWork> yes knome, I had to consult the logs
[14:06] <slickymasterWork> but I did saw it
[14:07] <slickymasterWork> didn't knew about that, tbo, the team have never used before as much as I can remember
[14:07] <knome> no, we haven't used that feature
[14:07] <knome> the limitation in it is the milestones set by the release team in LP
[14:08] <knome> but that's hardly a limitation
[14:08] <slickymasterWork> we should as it permits a rigorous control on the workflow per item of any givem project 
[14:08] <slickymasterWork> * givem
[14:08] <slickymasterWork> *given
[14:08] <knome> again, if people think it brings any additional value... we can start doing it
[14:10] <slickymasterWork> well, at least it's an added point to the discussion
[14:10] <knome> i understand why trello is good for some teams and for some projects
[14:10] <knome> while you've been using trello, i've used the pad a lot with other things
[14:11] <slickymasterWork> elfy and I did found productive in -qa last cycle
[14:11] <slickymasterWork> + it
[14:11] <knome> then by all means use it ;)
[14:12] <slickymasterWork> on a different subject, that Whishlist bug in docs, about VirtualMachines, in your opinion we should leave it for the time being?
[14:12] <knome> the status just means it's very low priority :)
[14:13] <slickymasterWork> my only doubt about it would be where to put it
[14:13] <knome> it it's potentially more FAQ material than something for the docs
[14:13] <slickymasterWork> I mean, I can write something addressing the issue, but in what section should it be added? 
[14:13] <slickymasterWork> exactly
[14:14] <knome> -it
[14:14]  * knome sucks at typing today
[14:14] <knome> also, i should go out
[14:14] <slickymasterWork> lol, join the club ;)
[16:01] <elfy> mornafternooneveight everyone
[16:02] <knome> hey elfy 
[16:02] <ElderDryas> g'day (it's shorter:)
[16:02] <elfy> ElderDryas: indeed :)
[16:04] <knome> bbl
[17:51] <brainwash> light-locker article ready for the public audience?
[17:53] <elfy> brainwash: appears to still be waiting images 
[17:53] <brainwash> waiting images?!
[17:54] <elfy> seems so
[17:54] <elfy> nothing to do with me 
[17:54] <brainwash> mmh ok
[18:30] <knome> waiting some css...
[18:37] <elfy> knome: any reason not to do the QA blueprints that you can think of? 
[18:39] <knome> the new project lead does not wish to use blueprints at all :P
[18:41] <elfy> mmm 
[18:41] <elfy> I'm going to use bits of paper and e-mail the new XPL my address - door's usually open ... 
[18:42] <knome> lol
[18:42] <knome> practically, feel free to set up the blueprints :P
[18:42] <elfy> :)
[18:43] <elfy> knome: so - quick question is the Name box - the bit that sets the url - e.g. xubuntu-t-qa
[18:44] <knome> "it doesn't matter"
[18:44] <knome> but do xubuntu-u-*
[18:44] <elfy> yea 
[18:45] <elfy> that was how I thought it worked
[18:45] <knome> yep
[18:45] <elfy> ty :)
[18:45] <knome> the only name that matters is the umbrella blueprint
[18:45] <knome> the others are pulled in automatically as long as they are linked to that
[18:45] <elfy> yep - I'm not doing that :)
[18:45] <knome> so the only thing we want to have is a consistent scheme ;)
[18:46] <elfy> yea - well I'm just going to do the 2 QA ones -bugs and -qa
[18:46] <knome> wondering who should be the approver...
[18:47] <knome> put yourself for now, then change that to the XPL when we know who it is
[18:47] <elfy> ok
[18:47] <elfy> just want to get them done so I can throw away another scrap of paper :p
[18:48] <knome> ;)
[18:55] <elfy> https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-u-qa https://blueprints.launchpad.net/ubuntu/+spec/xubuntu-u-bugs
[18:56] <elfy> knome: ask in -release to get them registered? or leave till we have them all?
[18:57] <knome> leave them until we have the correct approver
[18:58] <elfy> yep - I thought so 
[18:58] <elfy> also - should -team be the assignee for the QA one - I would have thought -qa - but I don't know if this some bizarre LP thing :)
[21:35] <ochosi> brainwash: it still depends on some css changes that knome asked IS to land...
[21:35] <ochosi> the article has been ready for a while now
[21:38] <knome> he he :P