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