=== Guest78115 is now known as jose === jose is now known as Guest38423 === Guest38423 is now known as jose === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === nudtrobert1 is now known as nudtrobert === maclin1 is now known as maclin === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === chihchun is now known as chihchun_afk === chihchun_afk is now known as chihchun === nudtrobert1 is now known as nudtrobert === chihchun is now known as chihchun_afk === Ursinha_ is now known as Ursinha [15:21] flocculant, wxl, you may notice I'm adding you to a few tasks in GCI === barry` is now known as barry_ [15:26] balloons: mmm - looking at one now - how is one of these students supposed to work out that to run tests for a flavour - the download link you gave is no good? [15:27] example - how can I test mousepad on an ubuntu install ;) [15:28] flocculant ? [15:28] I don't doubt there may be an issue. can you edit it and fix the description? [15:28] well [15:29] what *I* was going to do was point at xubuntu daily current - then point at xubuntu package tests [15:29] I'd assume wxl would do the same [15:29] well - almost - Lubuntu instead :p [15:32] balloons: any documentation about instance count and time to complete - or is it as easy as we want this done 50 times and you get 3 days to do your one? [15:32] https://codein.withgoogle.com/dashboard/tasks/6233079207165952/ [15:33] flocculant, yep that's correct [15:33] check that now - Ubuntu specific [15:33] impossible to make them generic I Think [15:33] ok. So shall we just add ones for xubuntu and lubuntu as well then? [15:33] I was going to [15:34] great, thanks [15:34] wasn't doing anything today - not working tomorro [15:34] w [15:34] well then.. :-) You can join me in writing tasks if you wish [15:34] so was going to bung a bunch of X specific things [15:34] yes, specific is good. You are right [15:34] better to be specific [15:34] well - tomorrow I will - today I'm doing r/l things ;) [15:35] * balloons laughs when flocculant tags balloons as mentor for all of them [15:35] ha ha ha [15:35] I assume that the mentee's mail mentors? [15:35] well, the key to the mentor bit is you agree to review the work at the very least [15:36] ofc [15:36] so ... [15:36] and yes, in general, you will provide help if needed [15:36] what we need to do is set anything using the tracker to a date AFTER someone fixes the tracker filtering \o/ [15:38] balloons: as long as you don't add me to something I'm just going to say 'What?' to I'm fine [15:48] flocculant, I like that idea! We need to get those tracker issues added [15:48] it's on the list, but I can only braindump and type so fast [15:48] yea ofc [15:49] balloons: why don't you concentrate on those - I'll fill QA qa tracker things up fast enough when I get going tomorrow [15:49] thank you flocculant, I appreciate it. I am indeed saving QA stuff for last, as I'm trying to brainstorm and get the tasks already pending in other areas in [15:50] I won't do tracker code tasks - not a clue :p [15:50] other than I know what I would like to *see* :) [15:52] balloons: quick question - on the iso test task - you gave it 3 days? reason for that? I'd be suprised it took longer than an hour ... [15:52] or is that time between someone saying I'll do that and finishing? [15:53] flocculant, the idea is after 3 days if the person who said 'i want to do this' hasn't completed it, the task resets [15:54] since we have a high instance count, this actually doesn't matter too much in this case [15:54] ok - thanks [15:54] but it's intended I believe to prevent people from blocking all the tasks [15:54] and never finishing :-) [15:54] right [15:54] yea - that makes sense [15:56] I'll have done a bunch by the time you get around to waking up tomorrow [16:21] Heh. Magic while i sleep. Tis nice