[13:16] <gary_poster> danilos, ah, I think I just understood why you said those ec2 test errors were not spurious--the server branch hadn't successfully landed yet, right, so you had to fix that in the "parent" branch?
[13:16] <danilos> gary_poster, that's right
[13:16] <danilos> gary_poster, sorry if I put it so that it confused you :)
[13:17] <danilos> (and the same for the above sentence ;)
[13:17] <gary_poster> Cool, thanks.  heh, np
[13:18] <bac> hi gary_poster -- i'm not feeling well and have a dr appt at 11:15.  i'm going to take at least the morning off
[13:19] <gary_poster> bac, understood, and thanks for the heads up.  hope you feel better soon.
[13:19] <bac> gary_poster: thanks.  i'll be on the call.
[13:19] <gary_poster> oh, ok
[13:25] <gary_poster> bac, benji, danilos, gmb, please take a look at the cards in Quick Jobs: Tasks.  I will delete all of them except "get rid of feature flags" (which ought to be in progress by benji, yeah?) unless told otherwise
[13:26] <gmb> BURN THEM.
[13:26] <gmb> (I mean, fine by me - ther's nothing there that worries me overmuch)
[13:27] <gary_poster> cool :-)
[13:27]  * benji appears from nowhere in a cloud of smoke.
[13:28] <gary_poster> heh
[13:29] <gary_poster> bac benji danilos gmb, to state the probably obvious, call in less than 2 minutes.  To state the less obvious but not particularly important to anyone else, I need to go get my headset
[13:57] <gary_poster> bac benji danilos gmb, deryck and sinzui were supposed to be my chr guides, but they are not around.  I'm updating https://dev.launchpad.net/MaintenanceRotationSchedule with our details and doing as much as possible about it now.  That page has links to describe everything we are supposed to be doing.
[13:57] <gary_poster> We can talk about how to divide it up once I have my head around it more, or I'll describe a "what we'll do today, until we renegotiate tomorrow" or something
[13:58] <gmb> Ok.
[13:58] <benji> k
[13:58] <danilos> gary_poster, cool, thanks; one of the things we might do if we want team-wide CHR is set help contact to "yellow" and set our IRC clients to highlight that
[13:58] <gary_poster> danilos, was thinking the same thing.  bac, benji gmb, let's do it.
[14:08] <danilos> gary_poster, oh, btw, Francis upped https://bugs.launchpad.net/bugs/783595 to Critical, how do we deal with it?
[14:08] <_mup_> Bug #783595: JS controls for bug subscription are hard to use with screen readers <regression> <story-better-bug-notification> <Launchpad itself:Triaged by yellow> < https://launchpad.net/bugs/783595 >
[14:08] <gary_poster> danilos, just another critical bug.  is that what you mean?
[14:08] <gary_poster> or do you mean, how do we fix it>?
[14:09] <danilos> gary_poster, the former, i.e. do we focus on that?
[14:09] <gary_poster> danilos, no
[14:09] <gary_poster> it's just one among many
[14:09] <danilos> gary_poster, ok, fair enough, thanks
[14:10] <gary_poster> gmb, are your working hours 0800-1700 UTC right now?  and danilos, you are 0700-1600UTC?  and benji and bac, we are 1200-2100, unless you tell me otherwise
[14:10] <gmb> gary_poster: That's correct.
[14:10] <gary_poster> thanks
[14:11] <danilos> gary_poster, more like 0700-1530 UTC, but yes
[14:11] <gary_poster> ack danilos, will adjust
[14:12] <benji> gary_poster: yeah, even though I'm in central time zone, I intended on keeping the same absolute (UTC) schedule
[14:13] <gary_poster> ok cool benji.  I'm fine with a temp change too fwiw
[14:14] <benji> gary_poster: thanks, I figured you would be, but 1) this is simpler and 2) my body clock will wake me up anyway so I might as well go with it ;)
[14:14] <gary_poster> cool :-)
[14:17] <gary_poster> danilos, I have a bug to triage uniquely suited to you, within the yellow squad :-) : https://bugs.launchpad.net/launchpad/+bug/785805
[14:17]  * gmb discovers the problem of having his client highlight on "yellow"
[14:17] <gary_poster> I marked it incomplete and was about to ask for English, when I realized we could do better
[14:17] <gary_poster> ah yes
[14:17]  * benji hacks on perl to make "yellow" beep.
[14:18] <gmb> STOP IT.
[14:18] <benji> heh
[14:18] <gary_poster> what, say yellow?
[14:18] <gary_poster> :-P
[14:18] <gmb> Oh, my sides.
[14:18] <gmb> :D
[14:18] <danilos> heh, it's all yellow in my xchat now!
[14:18] <gary_poster> heh
[14:18] <gmb> :)
[14:19] <danilos> gary_poster, one thing we might not have taken into consideration: what about the other team CHR, they might want to do it as well :)
[14:19] <gary_poster> danilos, we swap weeks
[14:19] <danilos> ah, ok
[14:19] <gary_poster> this is our week
[14:19] <danilos> sounds good, thanks
[14:19] <gary_poster> np
[14:23] <gary_poster> danilos, I triaged it with Google translate :-P
[14:23] <gary_poster> feel free to change it as you will
[15:07] <gary_poster> OK, for anyone who wants to know, here are my notes from my conversation with deryck
[15:08] <gary_poster>  * Consider setting up beep on message for #launchpad rather than using the "yellow" beep
[15:08] <gary_poster>  * Consider setting up two or three hour daily shifts for monitoring IRC
[15:08] <gary_poster>  * Everyone should choose an hour per day for running down the action lists @ https://dev.launchpad.net/MaintenanceRotationSchedule
[15:08] <gary_poster>  * When triaging critical bugs, they are either security, or you should add one of these three tags: timeout, oops, regression. (Make sure you review https://dev.launchpad.net/BugTriage btw)
[15:08] <gary_poster>  * If a bug is not clearly critical (which is usually easy to determine), default the triage to low unless you are pretty sure that it is important.
[15:08] <gary_poster> We can set that up tomorrow
[15:08] <gary_poster> Or discuss it or whatever
[15:09]  * benji drowns in beeps as he realizes that his beep-on-yellow perl script also matches #launchpad-yellow.
[15:11] <benji> gary_poster: by "beep on message for #launchpad" do you mean that every message in #launchpad would cause a beep?
[15:11] <gary_poster> benji, right
[15:11] <benji> that seems a little... agressive :)
[15:11] <gary_poster> deryck said it wasn't very heavy channel
[15:12] <gary_poster> it also may have been in line with his "two or three hour daily shifts for monitoring IRC"
[15:12] <benji> oh, maybe just for our prescribed periods of paying attention?
[15:12] <gary_poster> right
[15:12] <benji> that makes sense
[15:14] <benji> btw, if anyone needs to test their beep-o-trons you can go to #test and do "#say this is a yellow test" and the bot will echo you
[15:16] <gary_poster> deryck is working on the project review list now, btw, so we don't need to do that until, say, tomorrow
[16:05] <gary_poster> danilos, is reviewing the translations queue as involved as https://wiki.canonical.com/Launchpad/Translations/ImportQueueReview suggests?  There are a lot of things to check, and a lot of different options.  I personally would love some hand-holding through this.  Would you be willing to do this for us tomorrow, or do you have another suggestion?
[16:06] <danilos> gary_poster, I have a different suggestion :) I file and fix a bug that allows project maintainers to self-review translations as part of my translations hand-off objective
[16:06] <danilos> (or translations "hands-off!" objective :)
[16:06] <gary_poster> heh
[16:07] <gary_poster> danilos, sure, +1
[16:07] <danilos> gary_poster, fwiw, that was one of the first things I wanted to do, and in the meantime, you can perhaps relay to me for all the translation imports stuff
[16:07] <gary_poster> ok, thank you danilos, that would be great
[19:47] <benji> gary_poster: do you know the scenarios in which a bug won't have at least one bug task?
[20:14] <gary_poster> benji, no
[20:15] <benji> gary_poster: thanks; some how our tests do it; I /think/ I have a sane work-around.