#ubuntu-reviews 2010-06-01 <dholbach> good morning <nigelbabu> dholbach: Sorry about yesterday. Got stuck in a bad traffic jam on the way back. Got too late. <nigelbabu> I'll probably have to take a peak at the results of the script today <nigelbabu> BlackZ: Great to see on the debian-mentors list :) Good going! <BlackZ> nigelb: thanks! :) <dholbach> nigelbabu: don'T worry <nigelbabu> dholbach: I'm already worried. We were supposed to launch 2 weeks back. <nigelbabu> Today, I'll just make a list of the bugs that failed with the script and do those manually <dholbach> nigelbabu: let's talk about that later today <dholbach> we'll figure it out <nigelbabu> Ok. I should be available in around 5 hours from now. <nigelb> dholbach: around? <dholbach> nigelb: yes, but I need a few minutes <nigelb> sure :) <dholbach> nigelb: I updated our documentation a bit <dholbach> (and generalised it too, so it can be used in other places in the wiki) <nigelb> Awesome :) <nigelb> ew, I can't access the server on which the script was running. <dholbach> nigelb: what's the main blocker for kicking off project babu? <dholbach> I mean cleansweep :-) <nigelb> haha <dholbach> is it just fixing the bug subscriptions? <nigelb> Well, as of now the blocker is that not all bugs with patches are subscribed. Some are, some aren't <nigelb> Yup <nigelb> Can you run the script overnight today without the try catch and see what error turns up? <dholbach> basically we'll subscribe the team to every ubuntu bug that is not on the blacklist that has a patch attached, right? <dholbach> or did I forget anything? <nigelb> Yep <dholbach> can do <dholbach> I'll start now <nigelb> Same as from the branch. <nigelb> Only difference is you remove the try catch for "Launchpad hates me and bug #" foo <dholbach> nigelb: did you have a look at the merge I proposed? <nigelb> nope, will do that now <dholbach> nigelb: that script could well be a bit quicker <dholbach> (because it does less loops) <nigelb> oooh. then I'll merge it in 10 minutes <xnox> can launchpad.net/ubuntu/+source/usb-creator be added to the blacklist? it's ubuntu native package? =) <nigelb> lemme get the code <nigelb> xnox: ubuntu native packages are not automatically blacklisted <nigelb> unless you're the maintainer and you don't want us helping you <dholbach> oops, there's a bug in what I proposed * dholbach goes and fixes it <xnox> nigelb, fair enough =) I just though there were blacklisted by default =) so far we have 3 patches hanging but all of them patch-needswork ;-) <nigelb> xnox: We only blacklist kernel and docs and a particular X package at the suggestion of the old X team lead <dholbach> nigelb: resubmitted <nigelb> I spottd a potential bug, lemme see if thats what you fixed. <nigelb> dholbach: why did you remove the try catch for looping through subscribers <nigelb> ? <dholbach> nigelb: because I didn't think it was necessary - the way I did it should be quicker, no? <nigelb> dholbach: well, the script fails every time it hits a subscriber who has a suspsended account without that try catch <dholbach> aha <dholbach> hang on <dholbach> I have an idea <nigelb> something that paces us even more? * nigelb is all ears :) <dholbach> I just look at launchpad people who are is_valid <nigelb> aha, that works too <nigelb> If I'm making it to this UDS, *big* hug for you! :) <dholbach> resubmitted <dholbach> :-) <nigelb> dholbach: merged and pushed :) <nigelb> You can run it now. Will take a few hours to run though <dholbach> nigelb: rock on <dholbach> I'll let you know how it goes <nigelb> awesome, thanks :) <nigelb> hyperair: figured out my sid pbuilder problems <hyperair> nigelb: oh cool. what were they? <nigelb> hyperair: some sid package trouble. built a testing chroot and upgraded to hardy <nigelb> err sid <xnox> nigelb, yeap it's been like that for a while now <nigelb> xnox: I spent 2 weeks trying to figure that out <xnox> nigelb, =)))))) lol I've tried once with one mirror, tried second time with another mirror and then tried doing squeeze -> sid =) with local apt-cacher-ng it took me about 30min ;-) <xnox> nigelb, I wonder if I can bet more verbose output from deboostrap to see which package is failing to configure though <xnox> s / bet / get <nigelb> I think i have that one <nigelb> Always fails with e2fsprogs <xnox> aha =) google employee the one that bashed ubuntu about the bug reporting mess on lp.net => lwn.net <xnox> well well =) <nigelb> xnox: what? where? <xnox> nigelb, https://bugs.edge.launchpad.net/ubuntu/+source/linux/+bug/543617/comments/20 <ubot4> Launchpad bug 543617 in linux (Fedora) (and 3 other projects) "Unmount of an fs with dirty cache buffers causes pathological slowdown (affects: 7) (dups: 2) (heat: 82)" [Unknown,Unknown] <xnox> nigelb, http://www.outflux.net/blog/archives/2010/05/17/yay-for-barriers/ <xnox> nigelb, looking at https://edge.launchpad.net/ubuntu/+source/debootstrap we might need newer deboostrap in lucid there were a lot of changes <nigelb> xnox: I have the latest debootstrap from debian <xnox> =( <nigelb> lool linked me to a debian bug earlier though. Its clearly an upstream problem. <dholbach> nigelb: there are private bugs :) <nigelb> dholbach: um, you need to use your credentials <nigelb> I used my credentilas on the server. <dholbach> sure, some are even more private :) <dholbach> I'll ignore those <dholbach> those break the script <nigelb> yeah, another try catch <dholbach> no, just "if bug.private: continue" <nigelb> ah, that works too :) <dholbach> I'll keep it running and if it works out, I'll propose another merge <nigelb> okay :) <dholbach> nigelb: the script also dies trying to add jfo as subscriber if he's already subscribed <dholbach> fixed that locally too <dholbach> we're slowly getting there :) <dholbach> I'll leave it running through the night <nigelb> dholbach: ok :) Thank you :) <dholbach> anytime :) #ubuntu-reviews 2010-06-02 <nigelbabu> vish: poke <vish> nigelbabu: hey o/ <nigelbabu> vish: you know about user days right? <vish> hmm , not sure <nigelbabu> It is supposed to be this weekend but we might postpone to some time next month <nigelbabu> I was wondering you'd be interested in taking a class about using launchpad <nigelbabu> I took it last time, so most of the stuff is there and you can add a few if you'd like <vish> oh , I'm bad at teaching :( <nigelbabu> oh come on! <nigelbabu> I'm not going to leave you alone :D <nigelbabu> vish: I'm not that great either, you'll learn with time how to teach ;) <vish> nigelb: no , seriously.. somehow i have never been able to do that, in real and it is worse on irc :( <nigelbabu> its the other way around. Trust me. <nigelbabu> I've never been able to stand in front of 5 people, learned slowly after IRC-ing <vish> nigelbabu: nope , i can stand in front and talk , but remote somehow remote i totally fail , realtime phone or anything like that :s <nigelbabu> vish: well, learn for this one. <nigelbabu> its a small crowd <vish> nigelbabu: sorry dude , i'm gonna -1 that . ;p <nigelbabu> vish: No -1-ing this ;) <nigelbabu> I'll hunt your down till you agree! <nigelbabu> I wonder what happened to persia, his server seems down too. <dholbach> good morning <nigelbabu> dholbach: how did the script go? <dholbach> nigelbabu: exploded again, but now I let it write a list of bugs to the disk which it touched already <nigelbabu> dholbach: awesome! <dholbach> nigelbabu: so it should skip a lot more bugs before touching them, so speeds everything up <nigelbabu> At what point did it explode? <nigelbabu> I have a sneaking suspicion it was at the subscriber thing <dholbach> unfortunately it didn't get very far <dholbach> oh, no <dholbach> again it was something to do with invalid accounts <dholbach> but I have a try: except: there now <nigelbabu> yep, the subscriber try catch that we removed <dholbach> I'll show you later on - need to dash now <nigelbabu> sure :) <dholbach> it's running again :) <nigelbabu> \o/ <dholbach> see you in a bit <effie_jayx> names <effie_jayx> ? sorry <dholbach> nigelbabu: script is running through nicely now, subscribing lots of bugs <nigelbabu> dholbach: yay! <BlackZ> nigelbabu: something has been modified with the bot? <nigelbabu> BlackZ: the script? <BlackZ> nigelbabu: yeah <nigelbabu> BlackZ: yep, daniel is running it now. Should be subscribing aggresssively <BlackZ> dholbach: \o <dholbach> hi BlackZ * dholbach goes and makes some more tea <BlackZ> heh <dholbach> nigelbabu: I'll re-run the script once it is done, just to make sure it's all fine <nigelbabu> dholbach: awesome thanks! <dholbach> LP read-only now :) <nigelbabu> oh yeah, grr <nigelbabu> how many hours more to go? <dholbach> not much I think <dholbach> oh, maybe it will be a bit longer: http://identi.ca/launchpadstatus :) <nigelbabu> hm, if we can kick of by friday, I'll be jumping with joby <nigelbabu> joy <dholbach> yeah, we'll figure it out :) <nigelbabu> 5 hours.. sigh <dholbach> nigelbabu: 2h45m <nigelbabu> dholbach: can you have a text file have the total number of bugs in cleansweep queue every hour? In that case we could probably have a plugin to ubot to give the number on the channels <nigelbabu> I talked to jussi and the coding part is not that hard. should take only some hacking time tonight <jussi> if there is a way to access that number via the LP API, it should be a simple plugin to write... <nigelbabu> there is, but thats going to take more time <nigelbabu> oh, wait, no <nigelbabu> there is a simple way to do it! <jussi> :D <nigelbabu> I talk to you folks in the evening when I get home about getting that number :) <nigelbabu> Its easier to get folks to review when I say !foo is the number of patches in review queue ;) <jussi> nigelbabu: likely it can be modelled on another plugin. <nigelbabu> jussi: you already have something like this? <dholbach> nigelbabu: isn't this what we do in one of the scripts already? <dholbach> nigelbabu: you just want something like http://project-babu.org/in-the-queue.txt to read 1523? <dholbach> nigelbabu1: you just want something like http://project-babu.org/in-the-queue.txt to read 1523? <nigelbabu1> dholbach: no, no. jussi says we don't have to go via text file <dholbach> nigelbabu1: it'd be trivial to spit it out as part of the countdown script <nigelbabu1> actually I want something like "!numberpatches" to give out exact number of patches remaining <dholbach> nigelbabu1: so the bot just needs to read that file from urllib <dholbach> I can make the change easily <nigelbabu1> dholbach: we can either have the bot do it from a text file or a wadl representation <dholbach> nigelbabu1: I'll make the change in countdown.py to write out a file <nigelbabu1> awesome! <dholbach> nigelbabu1: I'll test it in 2h21m :) <nigelbabu1> dholbach: haha <jussi> lol <nigelbabu1> dholbach: is the script that you use to generate the countdown in the ubuntu-review-overview branch? <dholbach> yes <dholbach> I'll push a new branch up once LP is read-write again <nigelbabu1> dholbach: m4v is looking at generating the data directly from LP live instead of using a text file. Lets see where it goes. <dholbach> considering that it's just a import urllib; number = urllib.urlopen(url).read().strip() I wouldn't try putting a lot of work into it <dholbach> but that's just me :) <nigelbabu1> hehe <dholbach> nigelbabu: sent merge proposal <nigelbabu> dholbach: I'll look at it as soon as I get home <nigelbabu> btw, the bot thing, can be done directly by the bot, so we don't have to do it. <dholbach> nigelbabu: and the script is rerunning now - I'll let you know how it goes <nigelbabu> I'll poke at it today and let you know how it goes ;) <dholbach> the code is written, it'll just write out a tiny text file <nigelbabu> I know. m4v thinks its better to do this via a supybot plugin querying LP directly <nigelbabu> dholbach: Also, you need to modify the coutdown.py - hang on, I'll modify and propose a merge you can take a look at today <dholbach> nigelbabu: <dholbach> http://daniel.holba.ch/review/meter.png <dholbach> http://daniel.holba.ch/review/in-the-queue.txt <dholbach> nigelb: proposed the merge <nigelb> dholbach: pushed <nigelb> err.. merged <dholbach> nigelb: awesome <nigelb> dholbach: so 2017 looks like the right number? * nigelb gulps <dholbach> nigelb: I'll run it again, just to be sure :) <nigelb> dholbach: ok :) <nigelb> I like the new improvements <dholbach> great <dholbach> glad you like it <nigelb> it only looks for ones without the tag so its a smaller queue :) <nigelb> dholbach: can you get the image to point to https://bugs.launchpad.net/ubuntu/+bugs?field.subscriber=ubuntu-reviewers&orderby=datecreated&&ield.tag=-patch-needswork+-patch-forwarded-upstream+-patch-forwarded-debian+-patch-accepted-upstream+-patch-accepted-debian+-patch-rejected-upstream+-patch-rejected-debian+-patch-rejected&field.tags_combinator=ALL ? <nigelb> Its a big query, but I think it makes ssnese <nigelb> this gives us a better idea of if we've worked on the bug <dholbach> it's the countdown.py script <dholbach> what needs to be changed there? <nigelb> lemme take a peak <nigelb> *peek <nigelb> dholbach: apparently you already rock ;) Its already in :) <dholbach> ok good :) #ubuntu-reviews 2010-06-03 <nigelbabu> eww, while we were not watching, review queue jumped from 50s to 60s to 293 <hyperair> whoa <hyperair> that's large. <nigelbabu> well, compared to cleansweep project, no <nigelbabu> total number of patches awaiting review by ubuntu-reviewers is 1955 <hyperair> ._. <hyperair> wha <nigelbabu> yeah <nigelbabu> 1955 patches to be reviewed in 6 months - possible/ <nigelbabu> ? <hyperair> well, if we try very hard... <hyperair> i think...? <nigelbabu> I think if we can go 1 patch a day and gather lots of people to do that <nigelbabu> entirely possible <hyperair> once i get my new kernel and btrfs working, i'll start poking the review queue <hyperair> yaeh it's possible. <hyperair> but the queue will also grow. <nigelbabu> There has been really steady growth this month. <nigelbabu> I'll be keeping track of new patches coming in, so we can get the exact progress <nigelbabu> hyperair: oh joy! I'm PM-ing myself to keep track of things to do <hyperair> nigelbabu: lol! <hyperair> use tomboy notes =p <hyperair> or some todo list or other, say gtg, evolution's calendar, rainlendar, or sunbird/lightning <nigelbabu> and sync them? No thanks <nigelbabu> This is easier, whatever I have to do in the evening, PM my usual nick <ajmitch> nigelbabu: that's quite a few new patches <nigelbabu> ajmitch: we're having project clean sweep - to clean all the old patches against ubuntu <nigelbabu> so one patch a day and mobilize large number to do it <nigelbabu> before maverick release, we want the 1955 number to 0 <ajmitch> good luck with that :) <nigelbabu> ajmitch: well, obviously, I want you to help out too <ajmitch> trying to check that old patches can be applied to newer versions can be tedious <nigelbabu> ajmitch: well, then patch-needswork and move on ;) <ajmitch> but that requires me to do work :P <nigelbabu> step 1 though is to make sure that the bug is reproducible <ajmitch> you may end up with a lot in patch-needswork, and noone willing to refresh the patch <ajmitch> if someone submitted a patch 3 years ago & we're only just getting to it, they probably won't be motivated to pick it up again <nigelbabu> yes, have to write a lot of standard replies for a lot of use cases <nigelbabu> ajmitch: I just saw a patch workflow which might help us <nigelbabu> want to take a look at it <nigelbabu> ? <nigelbabu> Its the workflow used by the drupal community for their patches. I just saw it when I was opening a ticket there for some issues I was facing http://drupal.org/node/156119 <dholbach> good morning <nigelbabu> dholbach: also, I'd like to show you http://drupal.org/node/156119 <nigelbabu> this is what drupal community uses for their patch review thing <dholbach> looks a bit like what we'd have if we had proper patch statuses in Launchpad :) <dholbach> but at least we have it for code reviews <nigelbabu> yup ;) <nigelbabu> vish: can you modify my time from 16:30 to 15:30 UTC? 1530 = 2000 IST right? <nigelbabu> (I'm at work, can't play with wiki <nigelbabu> ddecator: poke <vish> nigelbabu: 15:30 = 21:00 IST <nigelbabu> vish: no, I want it to be 2000 to 0000 UTC <nigelbabu> err <nigelbabu> IST <vish> nigelbabu: IST - 5:30 UTC <vish> err , + <vish> +5:30 <nigelbabu> nope <nigelbabu> on UTC, its +4:30 <vish> hmm , oh well , IST = +5:30 GMT <vish> utc you can figure out ;p <nigelbabu> oh, I wish there was a desktop TZ converter <nigelbabu> @now <vish> nigelbabu: see , +5:30 ;p <nigelbabu> vish: agreed, but whole of uds, i calculated +430 and thats what worked <nigelbabu> ok, then I've calculated correct right? <nigelbabu> I mean on the wiki <vish> nigelbabu: nope , 16:30 - 20:30 UTC = 22:00 - 02:00 IST <nigelbabu> vish: ewww.. change that to 2000 to 0000 IST please? <vish> nigelbabu: k <dholbach> I always use: "date; date -u" to check :) <dholbach> nigelbabu: is there anything we should get done from the blueprints before the announce? <dholbach> nigelbabu: or just go and do it=? <dholbach> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-initiative <dholbach> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-process <dholbach> (probably rather the other way around :-)) <nigelbabu> dholbach: publish the workflow perhaps? wiki.ubuntu.com/OperationCleansweep <dholbach> nigelbabu: publish in which way? what did you have in mind? <nigelbabu> well, there's nothing there, we have to write <nigelbabu> same as the workflow in reviewguide, except there won't be a patch tahg <nigelbabu> tag <nigelbabu> Also, need to work on standard replies for use cases that we hit <dholbach> nigelbabu: I included the graph on https://wiki.ubuntu.com/OperationCleansweep <dholbach> nigelbabu: I personally wouldn't copy the docs again <dholbach> either link to it very prominently or use Include()s <nigelbabu> dholbach: just linking up would be fine <dholbach> ok great <nigelbabu> dholbach: Also, can you make the image horizontal instead of vertical? <nigelbabu> A lot of people would be putting it on the side bar of their blog, its nicer if its horizontal <dholbach> nigelbabu: I'll have a look into it <nigelbabu> dholbach: nothing urgent. Just came across it when I was looking into putting it on my blog <nigelbabu> dholbach: you can't merge into the ubuntu-review-overview trunk? <dholbach> nigelbabu: I prefer to use merge proposals <dholbach> I think there's a lot of worth others looking over my changes :) <nigelbabu> but you know python and launchpadlib better than me :) <vish> dholbach: nigelbabu : is there some way to make/review papercut patches faster? could we ping here to get them through quicker? <vish> do note , those would be smaller/simpler patches <nigelbabu> vish: *glee* or your could do them youself <dholbach> still, if there's stuff in there where you go "what the hell? this doesn't make any sense! none of the variable names make sense", etc. then that's useful <nigelbabu> dholbach: haha <vish> nigelbabu: well , i dont know all the packages do i ;) <dholbach> vish: what do you mean by "get them through"? <vish> dholbach: getting the review done for those bugs faster <vish> clearing them out of review queue <dholbach> vish: so get them upstream and stuff? <vish> yup <dholbach> vish: then yes <vish> dholbach: cool , thanks :) <dholbach> I hope the reviewers team can help with that once we have a few more people on board <dholbach> and make cleansweep happen <nigelbabu> yeah, we need to work on getting the patches that we carry back to upstream and debian too <dholbach> first let's get cleansweep done :) <nigelbabu> well, first lets get it started! <dholbach> nigelbabu: proposed the merge <nigelbabu> dholbach: awesome, i'll look at it when I get home <nigelbabu> its raining like crazy today though, so it might be some time :/ <dholbach> nice <dholbach> take it easy <dholbach> nigelbabu: https://wiki.ubuntu.com/OperationCleansweep <nigelbabu> dholbach: yay! <dholbach> glad you like it :) <nigelbabu> Also, I need to correct a lot of stuff on that wiki page. I've but in a lot of blunders <nigelbabu> s/but/put <ddecator> nigelb: ouch #ubuntu-reviews 2010-06-04 <ddecator> nigelb: à² _à² <nigelbabu> ddecator: I poked you about taking a class for UUD, looks like I needn't have bothered ;) <ddecator> nigelbabu: nope, haha, now that it's postponed i'll be able to help if i'm needed <nigelbabu> ddecator: oh yes, you can take the 'Using Launchpad' one <ddecator> sure, if that's what the board needs <dholbach> good morning <nigelbabu> dholbach: thanks for merging that code. I was struggling to get it to work and got an OOOPs too <dholbach> no worries <nigelbabu> also, sorry about last night. That storm caused a tree to fall on power lines. Was out of power till late night <nigelbabu> Were you able to merge back those corrections to cleansweep.py? <nigelbabu> It might be nice to have them for future reference. <dholbach> yeah, they're all in the branch <dholbach> and don't worry - having no power must have sucked :/ <nigelbabu> yep, big time <nigelbabu> forced candle-lit dinner alone is not fun <dholbach> no chat with the neighbours who were out of power too? <nigelbabu> We're launching today whatever, if I'm not around, you can go ahead and blog about it announcing the launch :) <nigelbabu> I came home first, everyone else got stuck in the traffic <dholbach> oh ok <dholbach> there's always something going on in India :) <nigelbabu> haha, true <dholbach> I so need to get back to India <nigelbabu> a few of the roads were flooded and I drove on the foothpath <dholbach> but I've said this a hundred times already :) <nigelbabu> say that to jono and say you're suicidal unless you have a vacation <nigelbabu> or say you're feeling particular homicidal to your boss :p <dholbach> haha <dholbach> nigelbabu: I'm afraid that "only a holiday in India can rescue me" might be a tad too melodramatic for somebody who produces death metal albums <nigelbabu> dholbach: lol, he might torture you to listen to is songs <nigelbabu> I should perhaps hide from jono :p <nigelbabu> dholbach: I'm making a list of things that we should be doing. I'll get around to it in the evening or night. At least before 0000 UTC Jun 5 http://pad.ubuntu-uk.org/Cleansweep <nigelbabu> Add things you want me to fix there <dholbach> ok cool <dholbach> looking forward to it! :) <nigelbabu> dholbach: I'm thinking of hitting the planet every day from today till next with clean sweep project. Can you pick a day and blog about it? I'll ask more people for help. <hyperair> woo planet spam <nigelbabu> hyperair: wanna join in? <hyperair> i don't have a blog =) <nigelbabu> hyperair: well, what are ya waiting for? <nigelbabu> go to wordpress.com and sign up for one :D <hyperair> but i'm lazy.. =p <hyperair> well i *micro*blog =p <nigelbabu> hyperair: microblog is for the lazies :P <nigelbabu> anyway, whats your twitter/identi.ca handle? <dholbach> nigelbabu: definitely - just pencil me in for some day <dholbach> nigelbabu: might be good if you write something up and ask folks, maybe in #ubuntu-community-team, to re-blog <dholbach> and expand on the topic <nigelbabu> dholbach: I'll get to work on something when I get home <nigelbabu> I wonder what happened to persia <dholbach> nigelbabu: awesome <dholbach> I don't know either <hyperair> nigelbabu: hyperair2. someone took hyperair first. =( <nigelbabu> hyperair: where? twitter? then switch to identi.ca <hyperair> nigelbabu: why switch? <nigelbabu> identi.ca is open source :) <hyperair> er besides that reason? =p <hyperair> i honestly don't really care about web services being open source or not -- they host it, it's not like i could dive into the source code and change anything i want even if i wanted to. <nigelbabu> my main reason is, I need not bother following people, I just follow groups that I care about <hyperair> ah. i see. <hyperair> groups. that sounds interesting, i suppose. <nigelbabu> so, I follow ubuntu, debian, linux, and few others and I get all the news around it <hyperair> so it's like planet for microblogging eh <nigelbabu> Similar to planet, yes :) <hyperair> well i still don't have any strong feelings about it <nigelbabu> hahaha <hyperair> my gwibber's off half the time anyway =D <nigelbabu> I dont use gwibber, it doesn't play nice with identi.ca <nigelbabu> choqok is my only kde vice. I can't live without it. <nigelbabu> Its got some memory leaks, but thats okay. I still love it <hyperair> speaking of memory leaks, chromium sure has a lot of them =\ <hyperair> just when i start thinking firefox's lousy, sluggish, and a memory hog, chromium sends my machine into swapping hell. <nigelbabu> lol <nigelbabu> I sometimes use epiphany when I don't want all the bells and whistles <nigelbabu> when I go really extreme, lynx :p <hyperair> okay, i haven't gone all the way to that extreme before. <hyperair> eh actually i might have, once, when i really needed a browser and X wouldn't coem up <nigelbabu> haha <nigelbabu> I like lynx and w3m. Its faster and avoids the drag of pictures, flash, etc. Fun when your X crashed and you're trying to find fixes on wiki.ubuntu.com :p <nigelb> dholbach: how long more will you be online? <dholbach> nigelb: not very long <nigelb> dholbach: gimme 10 minutes to finish the last minute wiki edits and we'll launchd :) <dholbach> nigelb: awesome <dholbach> :) <nigelb> dholbach: How do you want to do the query? shall I remove the old query away? <dholbach> nigelb: which one? <nigelb> there is the patch-<reviewedtags> and the -<reviewed-tags> <nigelb> the -<reviewedtags> would be around 1995 bugs and the other one around 293 <nigelb> The query in Review guide <dholbach> nigelb: we should have them all there <nigelb> ok,I'll write it up <dholbach> so if somebody wants to go and work on the stuff that was accepted upstream for example, they can go and do it <dholbach> or stuff that was forwarded upstream and not touched for alonger while <nigelb> What I'm talking about is not that <nigelb> We have a query in https://wiki.ubuntu.com/ReviewersTeam/ReviewGuide#Workflow <nigelb> This query is for all open bugs - ones with reviewed tags <nigelb> but it has only the new ones, can I change that to have both old and new? <dholbach> oh yeah <nigelb> Shall I change that to have both old and new and then have all the different queries in the Knowledge base page? <dholbach> that sounds good to me <nigelb> one momment <nigelb> dholbach: https://wiki.ubuntu.com/ReviewersTeam/ReviewGuide <dholbach> nigelb: great <nigelb> dholbach: shall we go for it? I'll write up the post? :) <dholbach> YES <dholbach> maybe I'll write something up over the WE <dholbach> if not then at least something on Monday <dholbach> so we'll keep the message on Planet :) <nigelb> yes, planet spam :P <nigelb> I'm writing up here http://pad.ubuntu-uk.org/Cleansweep <nigelb> Feel free to add <nigelb> dholbach: ok, thats the best I can do. Can take a look? <dholbach> sure, hang on <dholbach> nigelb: shall I add a quick paragraph about how the team works? <dholbach> or the process rather <nigelb> please do! <dholbach> just a little bit <dholbach> alright <dholbach> nigelb: looks OK? <nigelb> dholbach: yep :) <dholbach> awesome <nigelb> dholbach: gimme 2 minutes to get the formatting on wordpress right <dholbach> sure sure <dholbach> yeeeeeehaw <nigelb> dholbach: http://justanothertriager.wordpress.com/2010/06/04/operation-cleansweep-launched/ <nigelb> We're away! <dholbach> awesome <dholbach> good work! <dholbach> and with that I'll start into the weekend :) * dholbach hugs nigelb <dholbach> rock on, have a good time over there in India! :) <nigelb> dholbach: thank you for all the work you've done over the week! We've finally launched <nigelb> :) <dholbach> you too <bencrisford> nigelb: congratz :) <nigelb> bencrisford: you can congratulate me when the number of bugs in the queue is 0 :D <bencrisford> nigelb: heh :) i'll try and review as much as I can between now and november ;) <nigelb> October! <bencrisford> oh yeah :S <bencrisford> nigelb: so I review as much as possible and thats it? no other ways I can contribute as well? :) <bencrisford> as well as obviously spreading the word about the project :) <nigelb> bencrisford: well, you can write a plugin for ubottu or a facebook app to show the image <bencrisford> nigelb: hmm, that does sound like fun, but i'm not sure how great i'd be at that, ive never looked at facebook apps properly <bencrisford> I guess i'll be concentrating my efforts on the reviewing then :D <nigelb> me neither. I ahve to catch hold of whoever wrote the facebook countdown #ubuntu-reviews 2010-06-05 <milkfish2k> /msg nickserv register 44425 zstrickland@example.net <m4n1sh> nigelb, You there <nigelb> m4n1sh: partly. In a discussion with the accessibility folks <m4n1sh> nigelb, carry on. <nigelb> I have the connection from LP perfectly <nigelb> Its the only hooking to bts thats going wrong so far <m4n1sh> yeah. probably Debian BTS uses newer version <m4n1sh> so the web service fails <m4n1sh> and bugz is for older versions <nigelb> I'm using reportbug that's supposed to hook up with the thing, but the authors have written back to me. I'll peek in later. <m4n1sh> nigelb, oh. then it's fine <m4n1sh> nigelb, let me know when the problem gets solved. Even I want to know how to get it done. <nigelb> m4n1sh: heh,sure :) <nigelb> if nothing works, I 'll just send a mail to the mail ID #ubuntu-reviews 2010-06-06 <nhandler> nigelb: Team Reports go out today. Not sure if you wanted to add something about Operation Cleansweep or anything else to the Reviewers Team report <penguin42> It was suggested that I point out my patch in bug 483833 here, there are patches in the upstream as well but it looks like neither set have been applied in a while - they're pretty trivial <ubot4> Launchpad bug 483833 in lsof (Debian) (and 1 other project) "lsof manpage is garbled (affects: 3) (heat: 18)" [Unknown,New] https://launchpad.net/bugs/483833 <nigelb> nhandler: I do want to. I'll do it in a few <nigelb> nhandler: I forget how they're organized now :/ #ubuntu-reviews 2010-06-07 <dholbach> good morning <hyperair> dholbach: i think you could benefit from a script that sends "good morning" to every channel you've joined just after you've connected ;-) <dholbach> haha <dholbach> hey hyperair <hyperair> hi dholbach =) <dholbach> nigelbabu: meet bobbo <dholbach> bobbo: meet nigelbabu <dholbach> :) <nigelbabu> hello bobbo :) <bobbo> hello nigelbabu :) <dholbach> bobbo: basically we don't want to expect patch submitters to do all the leg work, but give them a good experience of getting their patch somewhere <dholbach> bobbo: we might have submitters there who know about upstream, debian and all the rest of it already and they'll surely help out if they can <dholbach> but I wouldn't expect that to be the majorit <dholbach> y <bobbo> yeah, it took me a while to understand that when I first started contributing <nigelbabu> since you're fairly new to the process, you can perhaps look at our docs and give us feedback on what's missing <dholbach> it's tough, particularly with all the different upstream bug trackers and all the rest of it <nigelbabu> or what's confusing - it helps a *lot* <bobbo> nigelbabu, okay, I'm reading over them now, I'll say if I see anything :) <nigelbabu> bobbo: awesome! thanks :) <nigelbabu> I'm at work, so I may respond a bit late <bobbo> nigelbabu, ping <nigelbabu> bobbo: yes? <bobbo> nigelbabu, those docs are pretty good, there seems to be enough there to fully explain the process to a newbie and get them ready to start reviewing :) <nigelbabu> bobbo: awesome :) <dholbach> bobbo: these are the plans for this cycle for the patch reviewers team: <dholbach> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-initiative/ <dholbach> https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-process <dholbach> maybe you can see if there's anything on there you'd like to help with that looks particularly good or important to you? <bobbo> dholbach, looking now :) <dholbach> cool :) <bobbo> dholbach, maybe one of the more "technical" ones, I'm not the greatest documentation writer, the edit-patch feature (Bug #586787) was one that immediately stood out <ubot4> Launchpad bug 586787 in ubuntu-dev-tools (Ubuntu) "edit-patch should take an existing patch as an argument and apply it (affects: 1)" [Undecided,New] https://launchpad.net/bugs/586787 <dholbach> bobbo: sure, if you want to have a look at it, that'd be awesome <dholbach> bobbo: mvo wrote most of edit-patch so it'd might be worth talking to him <dholbach> bobbo: also there's james_w who wrote some kind of "test patches from bug X for sponsoring" tool, stefanlsd was interested in that task too <dholbach> that's all the info I can dump on you :) <bobbo> dholbach, so I should take a look at edit-patch and report in if I hit any brick walls? <dholbach> bobbo: sure, just try having a chat with the others if they have an immediate idea or a piece of code you can use and see how far you get with the tool :) <dholbach> good luck :) <bobbo> dholbach, great :D <dholbach> nigelbabu: http://daniel.holba.ch/blog/?p=689 * nigelbabu hugs dholbach * dholbach hugs nigelbabu back <dholbach> if you all can blog about it too, that'd be sweet <dholbach> ALL: ^ <nigelbabu> dholbach: Also, I'm writing a script all report-debian, takes an LP bug as input and forwards that bug through report-debian to debian! <nigelbabu> s/all/called <dholbach> nigelbabu: isn't the LP team working on something like that? <nigelbabu> dholbach: I haven't heard of them working on that <nigelbabu> I heard bryce working on a pedro button <dholbach> also it might be worth wrapping it around submittodebian (from ubuntu-dev-tools) <nigelbabu> but submittodebian is when we have a patch already in a package and want to forward it <nigelbabu> at least thats the impression I got when I tried it last <dholbach> nigelbabu: yes, so you just want to forward bugs to debian? <nigelbabu> dholbach: yep, seb128 asked if we had something for it and I started writing <dholbach> nigelbabu: I'd have a chat with the LP folks first <nigelbabu> I already talked to bryce, he helped me a bit when I got stuck <dholbach> just in case they're working on it so we don't duplicate work :) <nigelbabu> hm, I should perhaps talk to jml today <BlackZ> hey dholbach <dholbach> hi BlackZ <nigelbabu> BlackZ: btw, you guys should think of taking a class at developer week ( when it happens ) <BlackZ> dholbach: I'm following up your e-mail <BlackZ> nigelbabu: will be done <nigelbabu> :) <BlackZ> currently we're re-working to the program <vish> dholbach: hmm , whats up with the countdown meter? [on the blog] it just shows a black strip with red patch on the side <vish> or is it a progress bar? <vish> oops , it is a progress bar :D , for some reason i was expecting a number there ;) <dholbach> vish: progress bar <dholbach> vish: if you can improve the script to make it prettierâ¦ :-) <vish> dholbach: yeah , i'm trying to find a pretty progress bar , we used it for the -manual <dholbach> I use python-imaging <dholbach> it's very primitive <vish> dholbach: hmm , the guy who did the progressbar for the manual site isnt around right now. I'll hook you up with the good stuff soon ;p <dholbach> awesome <dholbach> bobbo: how are things looking? do you think the process will be easy enough for my mom and dad to make use of? ;-) <bobbo> dholbach, yeah, the instructions are pretty good, I've worked through quite a few of the bugs and not really hit any problems <dholbach> cool, that's how we like it <bobbo> one thing I'm not sure about though is that the instructions tell you to remove the "patch" tag whenever we add "patch-forwarded-upstream" etc. <dholbach> nigelb, bdmurray: ^? * dholbach doesn't know about the state of the discussions and I don't particularly care either way <bobbo> haha, I struggled with that when I was forwarding a patch to gwibber because I know they use the patch tag to identify patches in their bugs and didn't want to trample all over their project <bobbo> dholbach, should I just keep working through these bugs or is there anything else you'd like me to do? <dholbach> let me have a look at the blueprints again and see if there's something <dholbach> bobbo: what do you think about "add documentation about how to turn a patch into a merge proposal if it's a project maintained in Launchpad"? it might be interesting for cases like gwibber and I wrote up a few bits for that already <dholbach> bobbo: if you have a look at https://wiki.ubuntu.com/Bugs/HowToFix - there's a few reusable bits <bobbo> dholbach, branch merge proposal? <dholbach> yep <bobbo> I could have a look at it, basically grabbing the project's trunk, applying the patch, (testing it?), then committing, pushing and merge requesting? <dholbach> yep, there might be something on help.launchpad.net too <dholbach> I don't think you need to write a lot of docs yourself <dholbach> just string those bits nicely together, so people can work on that if they hit such a case <bobbo> sure I'll give that a go, you say you've already written up some stuff for it? <dholbach> https://wiki.ubuntu.com/Bugs/HowToFix <bobbo> great, thanks :) <dholbach> if you could blog about the operation cleansweep some time this week that'd be nice too <dholbach> so we keep the message on everybody's radar <dholbach> bobbo: where do you think we should post the message too? <bobbo> my domain name has just expired :( too poor to buy it again :D <dholbach> I think right now we just covered planet ubuntu, maybe ubuntu-devel@ <bobbo> twitter/identi.ca covered? <dholbach> bobbo: nevermind - that's fine - I just saw you were listed on planet <dholbach> might be worth mentioning it there too <dholbach> bobbo: do you think we have enough examples in the docs and stuff that explains when to forward upstream and when not to? <dholbach> bobbo: somehow I get the feeling that's what's probably most complicated to newcomers <dholbach> nigelb, stefanlsd and I agreed to have a look at the docs again and I already did a few bits <bobbo> dholbach, actually yeah, I think that could be expanded, I can imagine people not knowing when to send it up (and whether to go to Debian or straight to upstream) <dholbach> bobbo: if you have an idea what else to add there in terms of indication or documentation, that'd be nice <dholbach> bobbo: some times it's just 2 or 3 bullet points that make a difference <dholbach> â¦ when you're new <bobbo> dholbach, cool, I'll give it a think :) <dholbach> thanks muchly :) <bobbo> dholbach, how does https://wiki.ubuntu.com/DavidFutcher/PatchMergeRequests look? <dholbach> bobbo: I'll take a look in a sec <bobbo> dholbach, it's just a "first draft", I've never written any (decent) technical docs before :) <dholbach> bobbo: it's great <dholbach> bobbo: I'd probably add a link to general bzr docs somewhere and put "bzr lp-open" somewhere too, because I like it so much <dholbach> bobbo: other than that it's in a perfectly mergable state <dholbach> maybe Mr nigelb can take another look <dholbach> bobbo: very awesome <bobbo> dholbach, great, thanks alot, I'd never head of lp-open before <dholbach> bobbo: opens the lp page of the branch <dholbach> bobbo: so you just need to click on "submit for merge" or whatever it's called <bobbo> dholbach, yeah, it's awesome, don't know why more people don't use it :D <dholbach> bobbo: you're there to improve things: you documented it :-D <bobbo> heh :D <nigelb> bobbo: yes, there should only be one tag at a time patch or patch-* <bobbo> nigelb, what if the upstream actively uses the patch tag to identify bugs with patches? Or should we tell them to just use the "Bugs with patches" filter instead? <nigelb> bobbo: upstream using LP? <nigelb> then its a mess :p <bobbo> hehe :D <bobbo> are the LP team going to implement a patch status system or are we stuck using tags for a long time? <nigelb> bobbo: in that case, you can have both. I see no other way, sadly :( <dholbach> bobbo: I think we'll get it at some stage, people should be using branches :-D <bobbo> awesome :) <dholbach> bobbo: or we should auto-reflow-patches-into-branches <dholbach> patches, interdiffs, .diff.gz, tarballs *SHUDDER* <bobbo> hehe :P <bobbo> I've added some more links in my merge request docs (one to BZR's own docs site and one to help.lp's code review page :) <nigelb> dholbach: I think there was some talk of having the code review workflow for patches too <dholbach> nigelb: yep <nigelb> that would rock! <bobbo> that'd be awesome :D <dholbach> bobbo: awesome - are you going to merge it into the guide? <dholbach> nigelb: you happy with that? <nigelb> dholbach: what? where? <bobbo> :D <dholbach> nigelb: the document bobbo wrote <bobbo> nigelb, https://wiki.ubuntu.com/DavidFutcher/PatchMergeRequests <dholbach> nigelb: bobbo is totally rocking it <nigelb> I got busy with work and missed what was happening here <dholbach> no worries - take it easy :) <nigelb> bobbo: ROCK! <dholbach> seems we're all a pretty excitable bunch :-) <nigelb> you can make it part of the knowledge base <nigelb> dholbach: there is a low hanging task for anyone intrested <dholbach> make it part of the ReviewersTeam namespace and link it from the reviewguide and the knowledge base? <nigelb> hunt through the linux packaging that we're subscribed, confirm that kernel patch is required and unsubscribe the team <nigelb> dholbach: yep <nigelb> bobbo: so, it would be ReviewersTeam/PatchMergeRequests and you can link both to review guide and knowledge base :) <bobbo> nigelb, great, I'm on it now :) <dholbach> nigelb: hemanth wants to get involved too <nigelb> dholbach: get in and get participating :) <hemanth> :) <dholbach> nigelb: eh? <nigelb> ah, I did see him join <hemanth> nigelb, hi <nigelb> hemanth: hello, thanks for helping out! <hemanth> nigelb, my pleasure, was blogging the same, wanted more info on involvement, more related info rather, i went through the wiki <bobbo> okay, that's the merge proposals guide linked from the Knowledge Base and review Guide and prettied up a bit :) * hemanth going through the Workflow <bobbo> dholbach, any more jobs to offload to me today? I'm working through some more patch bugs but if there're any other things you'd like me to do? <dholbach> bobbo: is there anything in the patch review blueprint work items that's glaring at you? <bobbo> dholbach, documentation to help make the decision whether to go upstream or Debian looks do-able? <dholbach> bobbo: sure, if you have some additional thoughts for it, that'd be fantastic <bobbo> dholbach, okay, I'll give it a closer look, first idea is a subsection of the page linked to from the workflow that explains it in more detail but won't bulk up the workflow paragraph, maybe gives some example bug reports etc <dholbach> that sounds like music to my ears <bobbo> haha, I'll get looking at it then :D <dholbach> bobbo: https://blueprints.edge.launchpad.net/ubuntu/+spec/community-m-patch-review-process has your name on it twice now :) <dholbach> you just went and took over for somebody else :) <bobbo> wooot :D <bobbo> dholbach, is there an official Canonical time to stop working? <dholbach> bobbo: I guess that depends on what your contract is ;-) <nigelb> bobbo: how much of coding do you do? <nigelb> if you'd like to code, I have a task you might want to take over <dholbach> nigelb: bobbo's gone for today I think <dholbach> and I'm just about to leave too so I'll make it home before the rain starts <dholbach> see you tomorrow <bobbo> nigelb, ping <ajmitch> greetings #ubuntu-reviews 2010-06-08 <nigelb> ajmitch: Greeting alien from australia :p <nigelb> bobbo: pong <ajmitch> nigelb: oh that's just nasty, evil & wrong <nigelb> ajmitch: haha <nigelb> seriously though, good morning :) <ajmitch> good afternoon, for it is afternoon here in *new zealand* :) <nigelb> I just woke, my internal time clock is not yet synchronized <ajmitch> nor your world map :) <ajmitch> so have you cut down the 2000 patches down to a manageable number? <nigelb> not yet. It was 1952 at launch, now its closer to 1930 <nigelb> I'll work on a few today <ajmitch> I'm surprised that there are still the main/universe sponsors on the graphs on the qa.u.c/reports/patches page <nigelb> poke brian <nigelb> he'll fix it :) <ajmitch> not really important <nigelb> lazy :P <ajmitch> it's called prioritising workloads :) <nigelb> Now I just struck me it might be there for historical purposes <ajmitch> maybe, but the lines are just noise at the bottom at the moment :) <nigelb> I'll talk to brian tomorrow <dholbach> good morning <bobbo> good morning everyone :) <bobbo> nigelb, ping <bobbo> I've written up some docs on deciding whether to send a patch to Debian or original upstream if anyone has the time to look at them (https://wiki.ubuntu.com/DavidFutcher/UpstreamOrDebian) <dholbach> bobbo: I'll have a look in a bit <bobbo> dholbach, thanks, I'm just working through some patch reviews right now, if that's okay? <dholbach> bobbo: sure, go ahead - that's awesome <dholbach> it'll give us more experience and a head-start :) <BlackZ> . <BlackZ> ops, sorry <BlackZ> damn keyboard! <BlackZ> dholbach: is the review script running? <dholbach> BlackZ: which one? <BlackZ> the bug subscriber <dholbach> BlackZ: bdmurray would know <dholbach> or nigelb <BlackZ> oh, ok <dholbach> bobbo: looks great to me - do you think it could be merged into https://wiki.ubuntu.com/PackagingGuide/Intro/PatchesForwarding somehow? <dholbach> bobbo: because that's what used in the reviewguide and other places <bobbo> dholbach, yeah, it could merge in there fine, I'm currently sending a bug up to Debian but I'll do it when I've finished that <dholbach> bobbo: awesome, take it easy <bobbo> dholbach, :D that's the unreviewed bug count under 1900, too :P <dholbach> bobbo: man - that's awesome <bobbo> nigelbabu, ping <nigelbabu> bobbo: pong <nigelbabu> bobbo: <nigelbabu> jussi: poke <jussi> hrm? <bobbo> nigelbabu, you mentioned a programming task you may have for me? <nigelbabu> jussi: can you introduce bobbo to m4v. He's going to write the plugin for us. <nigelbabu> jussi: I'm at work, not much time on hands <jussi> bobbo: please join #unbuntu-bots-devel <jussi> err <jussi> bobbo: please join #ubuntu-bots-devel <jussi> typos ftw <nigelbabu> bobbo: so the task is to write a plugin for ubottu that will give the output as total of bugs in review queue <bobbo> awesome :) <nigelbabu> most of the code that you might want are in launchpad.net/ubuntu-review-overview <nigelbabu> you can just reuse that code for the launchpad related stuff :) <nigelbabu> vish: err, where you able to get in touch with the person you'd talk to about pretty progress bars? <vish> nigelb: i havent seen him around yet , i'm keeping an eye out for him , no worries <vish> nigelbabu: ^ <nigelbabu> vish: awesome thanks :) <dholbach> bobbo: blog test successful <dholbach> bobbo: if you don't get the bot sorted out, don't worry too much <dholbach> nigelb: you could talk to tsimpson for the bot stuff too <dholbach> nigelb: he has quite some experience <bobbo> dholbach, I've got the bot going, it's just been a hack so far :D <dholbach> bobbo: as I said: don't throw yourself into neverending misery :) <bobbo> dholbach, I'll try :D have a good lunch? <dholbach> bobbo: yeah, met a good friend, had some good Vietnamese food, went for a walk with the dog in the park afterwards <dholbach> now I should probably go and make some tea <bobbo> awesome :D <dholbach> nigelb: can you review all the work items for the patch-review blueprints again - I think we can consider some of them done with the work that bobbo has done <dholbach> (and we all did in the last few days) <daker> hi @all <vish> dholbach: daker is the one i was telling you about for he progressbar <vish> the* <dholbach> hey daker <dholbach> daker: what kind of progressbar did you work on? <vish> dholbach: he did the progressbar for the -manual , not sure if he has a screenshot lying around <dholbach> nigelb: also I think it'd make sense to try to transform some of the work items into something that can actually be done as part of "doing something" <dholbach> for example "Lead activity to clear backlog and generate identity for team" is a bit like a neverending task <dholbach> I'd prefer if we could get some of this stuff sorted out and worked on, then go and move on to the next thing that needs doing <dholbach> vish, daker: this is what I currently have for drawing those primitive progressbars: http://bazaar.launchpad.net/~ubuntu-reviewers/ubuntu-review-overview/trunk/annotate/head:/countdown.py <dholbach> basically a lot of im.putpixel((x,y), (255,0,0)) :) <daker> dholbach, i was reading the wiki <daker> can you explain more what this progressbar should do ? <dholbach> nigelb: how is 12:00 UTC on Thursday for you? I was thinking of giving a session for the Packaging Training session <dholbach> daker: we have two numbers: one is number of total patches that need handling, the other one how much we dealt with already <dholbach> daker: what you can see right now is: "the red part" is what we dealt with <dholbach> bobbo: or we'd give a quick irc session on Thursday about it - what do you think? <dholbach> bobbo: just go through the process, explain it and answer questions <dholbach> bobbo: maybe look at a nice example together <bobbo> dholbach, I'd be up for that :) <dholbach> bobbo: awesome - I'll pencil it in and write an announce in a bit * dholbach hugs bobbo <daker> dholbach, this PB should be displayed on the blogs ? right <daker> so we will use html & css <dholbach> daker: the way it works right now is simply a .png file that is created and that people can integrate by just using it in an <img> tag <dholbach> daker: if there's a more beautiful and cleverer way to do it, I'm totally up for it <daker> oki <vish> daker: its basically a
{'channel': 'ubuntu-reviews', 'month': 6}