=== nhandler_ is now known as nhandler [07:56] good morning [08:06] morning dholbach [08:07] hey nigelbabu [08:08] dholbach: at the time that you folks are conducting the class, its my last hour at work, but I might be around [08:08] nigelbabu: I thought we could do one of the next bug days as a patch review day [08:08] sure, we can, just to give a kick off [08:08] nigelbabu: no worries - I'm sure bobbo will do a great job :) [08:08] yep, I'm sure too [08:09] I wish I had free time like him to do this stuff. How I envy him [08:09] nigelbabu: you're talking to people while at work. i have little pity :p [08:10] nigelbabu: I put your name in here: https://wiki.ubuntu.com/UbuntuBugDay/Planning :-) [08:10] ddecator: I'm only talking about stuff that's important, user days, patch review, etc [08:10] nigelbabu: all the same, a lot of people can't even have IRC open at work :p [08:10] well, i'm lucky. so far [08:11] also, I get work done [08:11] no doubt [08:11] you multitask like no other [08:14] dholbach: No problem. I'll talk to pedro and get that going [08:14] awesome [08:14] let me know when it's scheduled [08:42] dholbach: morning! [08:42] heya vish, hey seb128 [08:42] dholbach: check out https://code.launchpad.net/~adnane002/+junk/ubuntu-reviews [08:42] seb128: Operation Cleansweep kicked off - time to blog about it! :) [08:43] the idea is that i write some line of javascript that parse http://daniel.holba.ch/review/in-the-queue.txt and total.txt, calculate the percent then print it to the screen [08:43] and people will just have to put a javascript file like this : [08:43] hey dholbach [08:43] how are you? [08:43] nice! [08:43] good good :) [08:44] vish: but it says percentage=75? [08:44] vish: where's the javascript? [08:44] dholbach: just the image for now , he hasnt yet written it :) [08:44] gotcha [08:45] vish: can we merge that into ubuntu-review-overview somehow? so that the countdown.py generates all that stuff? [08:45] vish: it could write out the .css file with the correct percentage [08:45] vish: so we don't have to mess with javascript [08:46] oh , which ever you prefer [08:46] it looks easier to me :) [08:46] vish: what is the necessary HTML going to be to display the thing bar afterwards? [08:47] dholbach: i'm not really sure. we can poke daker about it [08:48] I'll go and poke it a bit [08:50] morning all [08:52] heya bobbo [08:52] hey dholbach :) [09:09] good morning! [09:16] is there a tag for patches that aren't suitable to be sent anywhere (only apply in Ubuntu)? I've noticed a couple but just left them alone for now, but if there's no tag they're still going to show up as needing reviewed [09:19] bobbo: that's an interesting question, nigelb and bdmurray might know if there's something [09:24] Right now, none. I generally poke the person responsible directly in those cases [09:24] bobbo: what do you propose in that case? [09:25] nigelb, I'm not too sure, tbh, in some cases it'll be up to universe-sponsors to touch, so there's nothing we can really do about it [09:25] but I don't think we want to slap a "patch-exempt" or similar tag on it because then -sponsors may ignore it [09:27] bobbo: I was thinking of something like patch-reviewed to say that this works and ready for packaging [09:28] nigelbabu, that makes sense [09:28] so we can have low hanging tasks for people who want to package for ubuntu [09:29] I'll talk to brian. My "talk to brian about" list is big enough to bug him one of these days :) [09:29] awesome :) [09:35] what would stop it to get it into sponsoring? [09:58] dholbach: it might be simple patches instead of debdiffs [09:58] AFAIK sponsors don't like simple patches [09:59] brb, lunch [10:02] nigelbabu: sponsors should just write the changelog entry and be done with it [10:07] dholbach: talk to them :D [10:07] if sponsors are okay with it, simple patches after testing can make it to sponsor queue [10:08] alternatively, we test patches by packaging them and then installing. It would only be trivial to have us send the debdiffs for sponsoring [10:08] vish: http://daniel.holba.ch/review/example.html [10:08] vish: the HTML in there is relatively short and might be interesting for others [10:08] vish: the .css is created by a cronjob every now and then [10:08] dholbach: wow, that looks awesome! [10:08] nigelbabu: daker's work [10:09] +1 on awesome :D [10:09] hm, I have to find him and thank him today :) [10:09] vish: I didn't find a way to put in the percentage, but I don't know anything about css [10:09] so people have to use something like what's in example.html to use it [10:10] if they need a static picture, they should go with meter.png / meter.horiz.png [10:10] who's scheduled to blog today? jono? jcastro? [10:10] * dholbach dunno [10:10] I have to prepare two talks for Saturday [10:10] I'll be busy with other stuff today [10:11] I'll poke jono as soon as he wakes up :) [10:11] 'bout time he helped :D [10:14] dholbach: i dunno either , lets hope daker knows :D [11:07] ugh, maverick hates me, just crashed for a second time and now it's fscking my Home drive but taking forever :( [11:24] @patchcount [11:24] bobbo: Total: 2290 Left in Queue: 2091 8.7% complete [11:25] @total [11:25] bobbo: Total patches: 2290 [11:25] @queued [11:25] bobbo: Patches in queue: 2091 [11:25] @percent [11:25] bobbo: 8.7% complete [11:25] [11:25] bobbo: cool! well done :) [11:25] * nigelbabu hugs bobbo [11:26] dholbach: ^ we haz new bot! [11:26] bobbo: ugh, that's probably why I still have it running in a VM [11:26] nice [11:26] well done [11:26] @queued [11:26] nigelbabu: Patches in queue: 2091 [11:26] that doesn't seem right [11:27] the url is int the topic has still some 270 bugs [11:27] where are the other 1800 hidding? [11:27] I'll update that topic one now [11:27] what list should be used for review? [11:27] nigelbabu, thanks [11:27] the big list [11:28] I'm grabbing these numbers from dholbach's server, total.txt and in-the-queue.txt [11:28] the second url in the topic? [11:28] it lists patches already reviewed [11:28] http://tinyurl.com/2u7kf3b [11:28] seb128: ^ [11:28] oh, nicer [11:28] thanks nigelbb [11:28] thanks nigelbabu [11:29] seb128: no problem. actually, I should have done that ages ago! === ChanServ changed the topic of #ubuntu-reviews to: Welcome to the Ubuntu Reviews IRC Channel : https://wiki.ubuntu.com/ReviewersTeam || Patches yet to be reviewed : http://tinyurl.com/2u7kf3b || http://qa.ubuntu.com/reports/patches/ [11:30] * nigelbabu bows [11:30] bobbo: can you make patchbot show only the number corresponding to the link? [11:31] err.. the link I just put on topic [11:31] hmm , could the pathbot update the topic everyhr or everyday? [11:31] with the count [11:31] yes, good idea, but we need permission for that. I'll talk to jussi or nhandler [11:32] nigelbabu, I'm getting the numbers off dholbach's server, so you'd need to ask him, I don't know what code he's running to get the numbers [11:32] who what? [11:32] :D [11:32] hehe ;) [11:32] talk of the devil [11:32] jussi: we have patchbot with that plugin bobbo wrote. we were wondering if it could be given topic changing permissions to change the topic every day [11:32] bobbo: I'll look at dholbach's code. I have that one [11:33] nigelbabu: is it headding for ubottu? [11:33] nigelbabu: that's countdown.py [11:33] hourly would work as well [11:33] jussi: I'm not sure yet. Is it okay to have this in ubottu? I'm hoping it makes it there [11:33] vish: too much spam [11:33] trihourly then :p [11:34] vish: trihourly would mean thrice every hour right? :D [11:34] nigelbabu: I think so... ubot4 in anycase. best to have a chat in #ubuntu-bots-devel about it [11:34] nigelb: yup [11:34] jussi: ah, ugh, later today. Work. [13:26] dholbach, http://bobbo.me.uk/index.php/planet-ubuntu/operation-cleansweep [13:32] bobbo: that's awesome! [13:32] well done [13:33] dholbach, thanks :) [13:34] * bobbo returns to Launchpad ... timeout :D === txwikinger2 is now known as txwikinger [15:30] woot, number of bugs in the queue is now <1800 :D [15:47] * dholbach hugs bobbo [15:48] bobbo: http://daniel.holba.ch/review/example.html doesn't look that bad, does it [15:48] we still have a few days left until release :) [15:48] dholbach, looks pretty awesome :D [15:59] bobbo, ping? [15:59] jono, pong :) [16:00] bobbo, hey! [16:00] bobbo, we are about to have our team call, would you like to join us? [16:00] dholbach can give you the dial in details [16:00] bobbo: hang on [16:01] jono, sure :) [16:01] cool [16:01] ok dialing in now [16:19] * nigelb waves [16:29] * dholbach hugs bobbo [16:31] hey bobbo, thanks for the awesome work! [16:32] dholbach: re: blueprint, I think my WI on the "lead activity" can be done or in progress [16:32] but, I'm unsure as of now [16:32] nigelb: maybe rephrase? [16:33] I'll rephrase to "Initiate activity"? [16:35] ok [16:35] sounds good to me [16:35] I'll make the change now [16:35] super [16:37] bdmurray: If you've got the time today, please PM me. Quite a bit of things to talk to you about the script. [16:37] I'll mail you if you're not around today [16:38] dholbach: done! [16:52] nigelb: "dd more documentation to make the decision if it needs to go upstream or to debian easier (add examples)" - do you think that's done already? [16:53] yeah, but not by me, hence I'm not sure what to do there [16:55] nigelb: if you consider it done, set it to done :) [16:55] dholbach: ah, ok. setting. [16:55] it's just this way because at UDS you, stefanlsd and I said "yeah, we'll work this out" [16:56] and it it's done, it's done [16:56] I should probably set stefan's to done too :) [16:56] yea, you rock :) [16:56] and assign it to bobbo because he put some good work into the docs [16:57] okay ! [16:57] nigelb: otherwise it'll feel like we make no progress :) [16:58] dholbach: the bug numbers is all I look for progress [16:58] nigelb: yeah, but the organisational stuff too :)( [16:58] I'm going to remove a bunch of linux ones that got into the list [16:59] that should bring the numbers further down [16:59] ugh, Maverick died for the 5th time today :( [17:00] dholbach: I think brian's task of publishing the script can be marked done too [17:00] he did that before uds, but jml (or whoever took notes) didn't know that I think [17:00] nigelb: which one was that? [17:01] [brian-murray] Brian to publish bzr branch where script it is in ubuntu-qa-tools: [17:01] its on the qa team's trunk [17:01] but perhaps we can ask him to use the branch that we dump the scripts in [17:02] I'll mark it as done [17:02] awesome [17:02] time for me to go home and call it a day [17:02] have a great rest of your day everyone and see you tomorrow! === yofel_ is now known as yofel [19:04] Just an announcement! We were at 1952 bugs at launch, down to 1687 bugs now! [19:05] @status [21:09] vish, i need a logo of the ubuntu reviewers team 32*32 pls [21:20] daker: hi.. [21:20] just a sec. i dont have one ready yet. I'll try to get one done now. [21:20] take your time [21:20] daker: dholbach was mentioning he would prefer the css rather than a js [21:21] daker: http://daniel.holba.ch/review/example.html [21:22] : the HTML in there is relatively short and might be interesting for others [21:23] : the .css is created by a cronjob every now and then [21:24] daker: : can we merge that into ubuntu-review-overview somehow? so that the countdown.py generates all that stuff? [21:24] vish, i'll show you what i have done then we can discuss [21:31] cool [21:43] vish, you host it for now to see the result [21:43] https://code.launchpad.net/~adnane002/+junk/ubuntu-reviews [21:47] daker: could you just post a screenshot ;) [21:48] oki [21:48] daker: also , dholbach had a few questions. i think the two of you need to get together and dish it out. he was here till a few hrs ago. [21:50] http://imagebin.org/100664 [21:52] daker: neat! [21:52] daker: http://dl.dropbox.com/u/1325768/Review-team-32.png [21:52] daker: the 32px icon is for? [21:57] vish, i want to put it on the left [21:57] brb [22:05] daker: it would get too crowded with too many icons [22:05] we can just replace the ubuntu logo with the review logo [22:06] daker: on the left we can have the raw numbers. "1231 Done" [22:06] or maybe a "123 remaining" [22:10] and no need the tiny review logo in the bottom either [22:12] the Done count would be easier/saner , since it would always increase , but the remaining count will always vary up or down and confuse [23:02] vish, http://imagebin.org/100680