[12:16] <kiko> where's stub?
[12:18] <salgado> kiko, want me to ping him?
[12:18] <kiko> salgado, in the next break, if you can.
[12:18] <jordi> kiko: are you available for a tiny admin task?
[12:19] <SteveA> salgado: is BjornT around?
[12:19] <BjornT> hi SteveA 
[12:20] <kiko> jordi, always.
[12:20] <SteveA> hi BjornT 
[12:20] <SteveA> I have a question about a test I'm debugging on the ui branch
[12:20] <SteveA> the test hasn't changed, but the page it is testing has
[12:20] <SteveA> do you have a couple of minutes to explain one part of the test to me?
[12:21] <BjornT> sure
[12:21] <SteveA> thanks
[12:21] <jordi> kiko: in short, translation team owner is MIA, the only active translator's membership expired a few months ago, bringing Bulgarian translations to a complete halt
[12:21] <SteveA> the test is pagetests/bug-also-affects/xx-bug-requestdistrofix.txt
[12:21] <kiko> jordi, I can fix it. /msg me what and who
[12:21] <SteveA> there is a part:
[12:21] <SteveA> The ubuntu task is in the task list.
[12:21] <SteveA> >>> print browser.contents <... ...>Ubuntu</a>... ...
[12:21] <jordi> I sent an email to the current owner asking to reenable his membership, and warning that no actuion would get the other dude promoted to admin
[12:21] <SteveA> over several lines
[12:21] <jordi> I assume you're ok with this hpapening after a week with no action
[12:22] <jordi> kiko: will do
[12:22] <SteveA> as far as I can see, this should have started failing when there was a UI change to duplicate bugs so that the table of targets was no longer shown
[12:22] <SteveA> but it co-incidentally continues to work on the devel branch because <... ...>Ubuntu</a>... ... appears in the breadcrumbs
[12:22] <SteveA> even though it doesn't appear in the task list
[12:23] <SteveA> so, my question is, can I just delete that part of the test, or is there something better I can replace it with?
[12:24] <lifeless> SteveA: pong
[12:24] <BjornT> SteveA: right, it's an old test, and it doesn't test things well.
[12:25] <BjornT> SteveA: i think it's ok to simply delete it, it's not important to know whether the task is visible or not
[12:25] <SteveA> ok thanks, I'll do that
[12:27] <kiko> salgado, are ou participating in dynamic mirror updates?
[12:27] <salgado> kiko, I was. the session finished half an hour ago
[12:27] <kiko> salgado, cool. I saw a discussion about screen-scraping which shouldn't be necessary right?
[12:27] <salgado> right
[12:28] <kiko> ok
[12:35] <kiko> hey stub 
[12:46] <WebMaven> SteveA: still awake?
[01:15] <Ubugtu> New bug: #70665 in malone "Allow searching in comments" [High,Confirmed]  http://launchpad.net/bugs/70665
[01:32] <ehazlett> greetings all...  i was wondering if there is a way to remove a product series in launchpad?
[01:54] <lifeless> jamesh: can you please assign reviews for me this week ? 
[02:22] <carlos> spiv: ping
[02:22] <carlos> ehazlett: I think you cannot
[02:22] <carlos> ehazlett: but you can rename it
[02:23] <SteveA> lifeless: ping
[02:23] <lifeless> pong
[02:23] <SteveA> I'm having a bit of bzr / pqm trouble
[02:23] <SteveA> I'm trying to merge the latest ui work into rf/lp/ui-one-zero
[02:23] <SteveA> and it fails, in pqm, with 13 conflicts
[02:24] <SteveA> I just resolved the conflicts locally, merged and pushed
[02:24] <spiv> carlos: pong
[02:25] <carlos> spiv: hi, would be possible to get an urgent review for carlos/launchpad/bug-68014-step2 ?
[02:25] <carlos> it's a three steps fix for a bug that is producing data lose in Rosetta
[02:25] <kiko> SteveA, and then?
[02:25] <SteveA> well
[02:26] <SteveA> I just merged from ui-one-zero again
[02:26] <SteveA> and I got the conflicts again
[02:26] <carlos> as you can see in the name, that's step #2
[02:26] <carlos> spiv: https://devpad.canonical.com/~jamesh/pending-reviews/carlos/launchpad/bug-68014-step2/full-diff
[02:26] <SteveA> the same ones
[02:26] <spiv> carlos: ok, I'll get straight on that.
[02:26] <SteveA> the same ones I spent a while resolving just before
[02:26] <carlos> spiv: thank you
[02:27] <spiv> carlos: (although perhaps I'll need lunch first... I'll see how much stomach goes)
[02:27] <lifeless> SteveA: this is midday for pooloe, and I'm in bofs. Can you please chat with him about diagnosing this. If you need me to look at what PQM thinks is going on I can do that, but at this point it sounds like pure bzr.
[02:27] <SteveA> ok
[02:27] <carlos> spiv: don't worry, if you can get it done before you leave today, that's enough
[02:27] <spiv> carlos: ok
[02:28] <carlos> we will leave soon to the hotel so I don't think I will be able to handle the review until tomorrow morning
[02:28] <ehazlett> carlos: thanks 
[02:28] <carlos> np
[02:28] <kiko> SteveA, sure this isn't a pilot error?
[02:29] <carlos> stu1: would you approve and give me a patch number for the DB patch at https://devpad.canonical.com/~jamesh/pending-reviews/carlos/launchpad/bug-68014-step2/full-diff ? 
[02:31] <stu1> carlos: You appear to be adding rows to poselection and we just discussed dropping that table
[02:31] <carlos> yeah, that patch is not new from today
[02:32] <carlos> stub: anyway, we would need to collapse it inside posubmission
[02:32] <carlos> as the active and published fields
[02:32] <SteveA> kiko: if it is, I want a parachute
[02:32] <carlos> stub: btw, where are you ? I need to talk with you about the DB optimisation
[02:33] <stub> carlos: same room. I'll come out - people having a meeting in here
[02:33] <carlos> ok
[02:41] <salgado> kiko, BjornT, have you guys seen bug 68290 (https://launchpad.net/products/launchpad/+bug/68290)
[02:41] <Ubugtu> Bug 68290 on http://launchpad.net/bugs/68290 is private
[02:41] <kiko> I don't look at people's private parts
[02:42] <salgado> not even when they ask you to?
[02:42] <kiko> ok
[02:42] <kiko> so I think the first part is an actual bug
[02:42] <kiko> but I thought it was fixed
[02:42] <kiko> maybe not rolled out yet
[02:42] <kiko> the second is a real bug
[02:42] <kiko> you are the assignee
[02:43] <kiko> how the HELL can you not be in the portlet?
[02:43] <kiko> BjooooooornT
[02:43] <salgado> he's right beside me and seems to be looking at the bug now
[02:43] <salgado> :)
[02:47] <BjornT> kiko, salgado: i'm guessing it has something to do with the fact that assignees don't actually get notified on private bugs
[02:47] <kiko> yeah, good point
[02:48] <kiko> it may actually be intentional
[02:48] <kiko> BjornT, if it is intentional, I think it's worth putting text in the subscription box saying that "This bug is in private mode, and that's why the bug assignee and contacts are not also notified"
[02:48] <kiko> in <small>
[02:49] <salgado> I don't get notified but I can see the bug
[02:49] <BjornT> salgado: you can see the bug because you are in Launchpad Developers
[02:50] <salgado> I don't quite like that, I think... what's the point of having an assignee of a private bug?
[02:50] <stub> carlos: Need to add comments to comments.sql
[02:51] <BjornT> salgado: to indicate that someone will fix the bug?
[02:51] <BjornT> salgado: there's a bug open on that it should be possible to subscribe the assignee at the same time you assign him.
[02:51] <carlos> stub: oh, right, I forgot it....
[02:52] <BjornT> usually you want the assignee to get notified about the bug.
[02:53] <kiko> BjornT, at any rate, the bug is/was that the implicit subscribers should become real subscribers when the bug is made private.
[02:53] <kiko> BjornT, salgado: I believe that bug is now fixed. can somebody confirm?
[02:54] <kiko> salgado, ah I see, if you are marked as assignee after the bug is reported, right?
[02:54] <kiko> after the bug is marked private, I meant
[02:54] <kiko> doh
[02:57] <salgado> my concern is that if we don't notify the assignee he may never get to know about the bug
[02:57] <salgado> and whoever assigned that bug may not know about that
[02:57] <salgado> this is the case here, since matsubara thought I'd get notified about that bug, but I didn't
[02:58] <lifeless> surely the assignee should always be notified
[02:58] <stub> carlos: patch-67-30-0.sql
[02:58] <kiko> yeah
[02:58] <lifeless> and  if the reason for privacy should not let the assignee see the bug, *change the assignee*
[02:59] <BjornT> kiko: implicit subscribers become explicit when a bug is marked private
[02:59] <carlos> stub: ok, thanks
[02:59] <kiko> BjornT, right, so that's fixed.
[02:59] <lifeless> if you assign someone, d they become a subscriber ?
[03:00] <BjornT> kiko: yeah. and there's a bug open on that the  assignee should become subscribed to the bug
[03:00] <lifeless> put another way, is it possible for someone to be the assignee on a bug that is private,and not be able to see it, or not be notified ?
[03:00] <kiko> yes
[03:00] <BjornT> bug 757
[03:00] <Ubugtu> Malone bug 757 in malone "Assignee should be CC'd when assigneed to a private bug" [Medium,Needs info]  http://launchpad.net/bugs/757
[03:01] <lifeless> but why cc? surely that is conflating 'notify me on changes' with 'let me see this bug I am assigned to work on'
[03:03] <BjornT> lifeless: why special case private bugs? on public bugs the assignee will get notified, he can't choose not to get notified
[03:14] <lifeless> BjornT: I see, no problem.
[10:50] <Ubugtu> New bug: #70709 in malone "Can't search for bugs without a milestone set" [Undecided,Unconfirmed]  http://launchpad.net/bugs/70709
[11:05] <Ubugtu> New bug: #70712 in malone "Adding a "change comment" without change should equal adding a comment" [Undecided,Unconfirmed]  http://launchpad.net/bugs/70712
[12:01] <PecisDarbs> hi there, anyone knows what is happening to this translations issue - https://lists.ubuntu.com/archives/rosetta-users/2006-October/001897.html
[12:18] <PecisDarbs> anyone?
[12:19] <spiv> PecisDarbs: carlos has written a fix, I'm doing a code review of it atm.
[12:19] <spiv> PecisDarbs: when it's reviewed, I expect it will be cherry-picked onto production ASAP
[12:20] <PecisDarbs> ohh
[12:20] <spiv> Given that it's a Critical bug
[12:20] <PecisDarbs> great
[12:20] <PecisDarbs> thanks :)
[12:20] <spiv> And that carlos has been pestering me to review it urgently :)
[12:20] <spiv> You're welcome.
[06:22] <kiko> hello hello hackers
[06:22] <lifeless> hey kiko
[06:22] <kiko> how's it going 
[06:22] <lifeless> good good
[06:22] <lifeless> yourself ?
[06:22] <kiko> great
[06:23] <kiko> just back in
[06:41] <SteveA> stub: you up for an irc chat sometime?
[06:42] <kiko> stub!
[06:42] <stub> Yo
[06:42] <kiko> how's it going
[06:42] <kiko> stub, have time for a short voice call?
[06:42] <stub> Now is fine. Nothing happening at the moment.
[06:43] <kiko> stub, what number can I reach you at?
[06:43] <stub> I don't know if I can do voice here - SIP or Skype might work
[06:43] <kiko> hmmm
[06:43] <stub> No mobile as wee haven't had an opportunity to pick up sim cards
[06:43] <kiko> skype might work for me
[06:44] <SteveA> you need to pay to receive calls in the US anyway I think
[06:44] <kiko> you do not
[06:44] <kiko> stub, what's your skype id?
[06:45] <SteveA> stub: I'm going to take a break, but please ping me when you've finished talking with kiko
[06:45] <SteveA> I have news about beta, edge and domain names, among other things
[06:45] <stub> SteveA: ok
[06:47] <stub> kiko: stuartbishop
[06:48] <kiko> dialing in
[06:48] <malcc> Looking at a random US cell provider, it looks like receiving calls for free is still an extra not all deals have
[06:49] <kiko> oh, on cell phones
[06:49] <malcc> Hmm, and even the one here with "unlimited call-me minutes" only lets you receive calls for free if you're sufficiently near your "home area"
[06:49] <kiko> I hadn't picked that part up
[06:49] <kiko> in that case apologies SteveA 
[06:49] <kiko> I thought you meant for fixed lines
[06:50] <stub> kiko: What is your skype id?
[06:50] <kiko> stub, kiko-async
[06:51] <kiko> stub, can't seem to connect
[06:53] <kiko> stub, "Reason unknown"
[06:53] <kiko> if you can fathom
[06:54] <kiko> stub, let's do IRC then
[06:54] <stub> kiko: I get that when I try to connect to you too
[06:54] <stub> ok. The others can join in too hen
[06:54] <stub> erm... then.... I'm not actually calling you poultry
[06:54] <kiko> you just hurt my feelings
[06:55] <stub> eggscruciating
[06:55] <kiko> stub, so I wanted to check on two things
[06:56] <kiko> a) that people checked out the list of topics, if they have any questions or comments on them, and whether they want to suggest things for the allhands instead
[06:56] <kiko> b) how the work yesterday went, if the write-ups went well, if people are blocked on input, and what the main good/bad ideas that came up were
[06:57] <stub> a) check out which list of topics in particular? UDS topics do you mean?
[06:57] <salgado> I guess it's the topics kiko sent by email
[06:58] <stub> b) Fine. Not much for us to do here. Malcolm has a couple of specs to draft which he is doing. I got a rosetta one up to pending-approval.
[06:58] <kiko> stub, a) salgado's right.
[06:58] <salgado> in my case, the https discussion seem to have been postponed to allhands
[06:59] <kiko> stub, b) whoa, the list I sent had plenty of items that needed plenty of discussion... hopefully there should be enough to do. did you read the message?
[06:59] <stub> bugworkflow is being specced
[06:59] <salgado> I created https://wiki.ubuntu.com/ForumKarma, listing some other reasons why I think it doesn't look like a good idea
[06:59] <kiko> salgado, yeah, SteveA has suggestions for that
[06:59] <stub> cve tracking has not been discussed, and I don't think it is on the agenda
[06:59] <kiko> salgado, aha. 
[06:59] <stub> bug reporting tool has not been scheduled yet (I hope, or I missed a session)
[07:00] <kiko> stub, bugworkflow was an old spec.. what needed to be done was a catch-up on it
[07:00] <kiko> lol
[07:00] <stub> (bjorn says bug reporting tool is scheduled today)
[07:00] <stub> kiko: sflaw is drafting the spec last I heard
[07:00] <kiko> stub, so some of the statuses suggested were good ideas (I think the wontfix/invalid) split
[07:00] <kiko> and some of them were weird 
[07:00] <salgado> I had some discussions with mako about some membership issues and filed bug 70519
[07:00] <Ubugtu> Malone bug 70519 in launchpad "Need to allow team members to renew their own membership once it gets close to the membership's expiration date" [Undecided,Unconfirmed]  http://launchpad.net/bugs/70519
[07:00] <kiko> or perhaps too-distro-centric
[07:00] <BjornT> kiko, stub: i'll try do discuss cve tracking today
[07:01] <kiko> BjornT, or at least try scheduling a chat with pitti
[07:01] <salgado> I'm waiting on input from mako but I think on the bug report there's enough information to implement the fix
[07:01] <kiko> if you don't manage to start discussion 2day
[07:01] <kiko> salgado, so the idea is that a person can re-apply?
[07:01] <salgado> no, that's another bug
[07:01] <salgado> the person can renew his own membership
[07:02] <kiko> salgado, if it's an open membership team?
[07:02] <salgado> kiko, no, even if it's restricted
[07:02] <BjornT> kiko: yeah. i'll also going to discuss BugWorkflow with mark tomorrow
[07:02] <kiko> BjornT, ah, cool. be careful. :)
[07:03] <stub> carlos had translation team scheduled yesterday
[07:04] <kiko> how did that go? mdke_ wrote today saying that he thinks that for at least some teams just more care is necessary.
[07:04] <kiko> I think that having privileges inside the teams or two teams is probably the way to go
[07:04] <carlos> stub: that spec is superseded
[07:04] <carlos> it was handled by othre 
[07:04] <carlos> by other Ubuntu specs
[07:05] <kiko> carlos, how did it go
[07:05] <carlos> and Mat said that we will see what's needed in Launchpad once they collect the information
[07:05] <carlos> so we didn't get any conclusion for Launchpad modifications
[07:06] <kiko> carlos, what information? and which Matt?
[07:06] <carlos> kiko: that's unrelated with current thread about QA issues
[07:06] <carlos> https://features.launchpad.net/distros/ubuntu/+spec/language-teams
[07:06] <carlos> I'm talking about that spec
[07:07] <carlos> kiko: mdz
[07:07] <malcc> Soyuz specs are going well; two are mostly drafted, need to resolve a couple final issues, which I'll do when I've got the guys this afternoon for the other two
[07:07] <malcc> The other two specs we've got so far are up for discussion this afternoon, and we'll also discuss then what else we want to discuss
[07:07] <kiko> malcc, ah, what issues? which ones are drafted?
[07:08] <malcc> kiko: The ones we discussed yesterday, soyuz-buildd-improvements and soyuz-privilege-separation
[07:08] <malcc> kiko: No big issues, just some things where I didn't get every detail needed down in my notes, so I need a reminder of some things to complete the specs
[07:09] <kiko> right
[07:09] <kiko> any really novel ideas in those, or just underlining of things we knew were important?
[07:10] <malcc> In other news, footlong subs with pastrami and extra chillis are just as nice as I remembered, and there's DDR within walking distance of the hotel
[07:10] <kiko> malcc, heh
[07:10] <stub> DDR?
[07:10] <malcc> A couple useful ideas; some really simple things like changing some sorting on some UI pages which it sounds like will make a fair bit of difference to the usability
[07:10] <kiko> DANCE DANCE REVOLUTION
[07:10] <kiko> malcc, ah, awesome -- for the smaller things be sure to file bugs and we can get them in piecemeal
[07:11] <malcc> kiko: Yup, will do
[07:11] <kiko> awesome
[07:12] <kiko> malcc, BjornT, salgado, carlos: anything from the list of topics I sent that was a surprise?
[07:12] <kiko> or anything you'd like to ask about or discuss with me
[07:12] <stub> LanguagePackUI handling was also scheduled yesterday. carlos?
[07:13] <carlos> kiko: just that DB schema changes fro Rosetta are quite trivial and that we are not going to change anything there to reduce the amount of rows to copy with a new distrorelease opening (it would require another table with more or less the same amount of information.... so no wins)
[07:13] <kiko> I see
[07:14] <carlos> It was quite fast
[07:14] <carlos> Martin and we had more or less the same idea about whether it should be implemented
[07:14] <kiko> do you think it'll improve things significantly?
[07:14] <stub> re: karma for forums, it wouldn't be difficult to provide an API. The main work required would actually be at the forums end, and the mailing list end as it would be rather rude to award karma to the forums and not the mailing lists.
[07:14] <carlos> I'm drafting it
[07:14] <carlos> kiko: what? language pack UI ? or db schema?
[07:14] <BjornT> kiko: no, not really. although i don't think i'll discuss email interface improvments, since we already discussed that in paris.
[07:15] <kiko> BjornT, and there are things to do there that are still pending?
[07:15] <carlos> oh, mixed conversations... how confusing....
[07:15] <kiko> carlos, db schema.
[07:15] <cprov> malcc: hi, have you already got some feedback about Xen-based buildd + ppa-buildd ?
[07:15] <carlos> kiko: yeah, we are removing a table with 40Million of rows
[07:15] <malcc> cprov: Just re-iteration that ppa's will only be built on Xen, and that this needs to be done at some point.
[07:16] <carlos> so we will save to join with such a huge beast
[07:16] <kiko> carlos, that's awesome
[07:16] <kiko> malcc, is that a soyuz team task?
[07:16] <stub> re: karma scaling, I think logarithmic scaling would be good. We can play with scaliing algorithms as much as we want, as we are only messing with cached values and any changes will be easily cherry pickable because they would be isolated to the karma-cache building script.
[07:17] <BjornT> kiko: yeah
[07:17] <malcc> kiko: I think what it is is another good thing to discuss this week, to ensure we know who has to do what. My impression is that it's mostly not us, but this could do with being confirmed
[07:17] <kiko> stub, that's my idea
[07:17] <kiko> malcc, please put that on your todo list and let's sort it out -- it's an infinity/james question
[07:17] <cprov> malcc: well, and the specific ppa parameters ?  did you confirm that "ppa=http://l.n/people/cprov" or so will be enough for building ppas ?
[07:17] <kiko> stub, great, let's see if you and I sit down at allhands and code up a rogue patch
[07:17] <kiko> just to see how it does
[07:18] <malcc> cprov: I'll raise that too
[07:19] <stub> I think we have covered everything
[07:19] <kiko> stub, cool.
[07:19] <kiko> guys, thanks a lot for the time
[07:19] <kiko> be sure to update your spec statuses and have your write-ups in good shape for review time
[07:19] <cprov> malcc: very good ! flacoste also suggested *vserver* kernel-level-isolation technology instead of Xen, can you mention that in BOF and see what infinity & elmo thinks about it.
[07:19] <kiko> I can give input as necessary, just ping or email me
[07:20] <salgado> kiko, stub, I just updated https://launchpad.canonical.com/KarmaCalculation
[07:20] <malcc> cprov: Any idea what vserver might solve? Is it faster, or available for more platforms?
[07:20] <cprov> malcc: basically, faster
[07:20] <flacoste> malcc: it is faster and requires less resource
[07:20] <malcc> cprov: flacoste: The fact that Xen is only some supported platforms is a pain, as it blocks us using PPA directly for lots of distro team requirements, unless we have some kind of trusted PPA flag which uses the regular builders
[07:21] <malcc> Ok, I'll mention it and see what the guys say
[07:21] <flacoste> malcc: if by platform you mean architecture, it supports quite a few
[07:22] <malcc> flacoste: Yes, I meant arch
[07:22] <kiko> cool
[07:22] <flacoste> in theory it could be easily ported to any arch, since it doesn't need any special hardware support
[07:23] <flacoste> it's kind of a high powered chroot (or BSD jail), really worth a look
[07:24] <malcc> Sounds good
[07:24] <stub> Bleh. I'm still jetlagged :-P
[07:24] <stub> 10:20 am and I need a nap...
[07:30] <salgado> kiko, have you seen my updates to the KarmaCalculationSpec? if you think it's okay I'll go ahead and schedule some time to discuss it with stub
[07:30] <kiko> yeah, I did
[07:30] <kiko> they look good!
[07:31] <stub> I couldn't see what changed apart from the inline comment
[07:31] <salgado> the last comment at the bottom
[07:32] <salgado> in the "Future discussion" section
[07:42] <stub> salgado: I think we will need the normalization forever, but we have the choice of using hard coded values and tweaking them occasionally or the automatic algorithm (or similar) that is currently implemented.
[07:43] <stub> salgado: If the 'wobble' is the issue, there are alternatives such as rounding the scaling factor to the nearest 50 or somesuch, so it doesn't change every day.
[07:45] <Ubugtu> New bug: #70765 in launchpad "Following my person link from a features page doesn't work" [Undecided,Unconfirmed]  http://launchpad.net/bugs/70765
[07:45] <stub> With normalization, we only have to make sure that the karma values make sense within their category. Without scaling, we have to make sure they make sense globally which is a lot more difficult since you have to take into account changing variables such as how busy that particular bit of launchpad is
[07:46] <salgado> yeah, that's true
[07:53] <stub> SteveA: scheduled ping
[07:54] <SteveA> stub: hallo
[08:04] <ddaa> lifeless: your opensync import is ready
[08:06] <lifeless> danke
[08:58] <kiko_> is danilo at UDS?
[08:58] <kiko_> that I did not know
[08:59] <salgado> yes, he's here, kiko 
[08:59] <salgado> I'm talking with Znarl right now, kiko, and looks like DirectPersonCreation will be useful for mirror owners
[09:00] <salgado> since the mirror admins are not registering their mirrors in launchpad, we can create "placeholder" profiles for them and make them the owners of their mirrors
[09:06] <kiko> salgado, hmmm, interesting indeed
[09:06] <kiko> we can't email them though
[09:07] <salgado> that just means they won't get notified when their mirrors have problems
[09:07] <kiko> yeah
[09:07] <kiko> which is the case already anyway.
[09:13] <SteveA> stub: ping
[09:16] <salgado> Znarl, can you see any problem with that approach?
[09:16] <salgado> kiko, this would also be a good testbed for DirectPersonCreation
[09:17] <Znarl> salgado : Sounds fine to me.
[09:18] <SteveA> kiko: do me a review?
[09:24] <flacoste> kiko, salgado: got a few minutes for a simple "Extract Class" refactoring review?
[09:24] <flacoste> SteveA: ^^^
[09:25] <flacoste> it's almost trivial
[09:26] <SteveA> flacoste: ok
[09:27] <flacoste> SteveA: thanks! The diff is available at https://devpad.canonical.com/~jamesh/pending-reviews/flacoste/launchpad/refactoring-2/full-diff
[09:27] <SteveA> what's it about?
[09:27] <flacoste> (been unassigned for three days and I'm about to upload a branch that depends on it)
[09:28] <flacoste> SteveA: It  extracts identical ITicketTarget implementation in SourcePackage and DistributionSourcePackage into SourcePackageTicketTargetMixin.
[09:29] <SteveA> ok
[09:31] <SteveA> > +        if person not in self.support_contacts:
[09:31] <SteveA> > +            return False
[09:31] <SteveA> is that safe?
[09:31] <flacoste> support_contacts is a list so it should be
[09:34] <SteveA> only when we have spiv's sqlobject __eq__ stuff landed
[09:35] <SteveA> https://devpad.canonical.com/~andrew/paste/file7rVYcm.html
[09:35] <SteveA> rest of my review
[09:35] <SteveA> r=me, if you check out the sqlobject comparison stuff, and consider the other things I mentioned
[09:35] <flacoste> ok, you mean if person comes from another cache, it might fail
[09:37] <flacoste> SteveA: that conditional is tested so it kind of works
[09:38] <flacoste> but I'll do an explicit query there to be on the safe side
[09:38] <SteveA> it's tested somewhat... sqlobject can be unpredictable in practice when you have many threads, and long-running stuff with caches etc.etc.
[09:41] <Hogi> hello! can i seach for a specific term in my LP translations?
[09:43] <matsubara> Hogi: not yet, that's bug 44
[09:43] <Ubugtu> Malone bug 44 in rosetta "Translations should be searchable" [High,Confirmed]  http://launchpad.net/bugs/44
[09:43] <flacoste> SteveA: thanks for the review!
[09:44] <Hogi> matsubara: ok, thx
[10:34] <ddaa> BjornT: ping
[10:54] <ddaa> SteveA: https://launchpad.net/people/vcs-imports/+branch/silva/trunk
[10:54] <j-a-meinel> Is there a specific 'New User Guide to Using Launchpad' document out there?
[10:55] <j-a-meinel> Or is that part of a 1.0 rollout?
[10:55] <ddaa> Some snippets on https://help.launchpad.net/
[10:56] <ddaa> Generally, we do not have a dedicated documentation guy, so I do not think we'll ever have an extensive separate documentation. It would be too hard to keep up-to-date.
[10:59] <ddaa> also, users don't read doc... so we'd better spend our resources making useful integrated documentation (that's planned for 1.0) and fixing the confusing stuff.
[11:02] <SteveA> ddaa: hey, excellent!
[11:02] <SteveA> I'll tell the silva guys
[11:02] <ddaa> note that there's no rename support yet
[11:06] <BjornT> ddaa: pong
[11:07] <ddaa> BjornT: can you update the status of the cscvs/partial-copy branches in review?
[11:07] <ddaa> they are all needs-reply, and I'm not clear which are approved, and which are just waiting for you to reply to my reply.
[11:09] <BjornT> ddaa: sorry, i've been really busy lately. i'll take a look at them now.
[11:15] <kiko> salgado, "finish your launchpad registration"?
[11:22] <BjornT> ddaa: i've replied to the email. i used the same status for all branches, so all are basically approved
[11:35] <Ubugtu> New bug: #70807 in launchpad "Properly redirect people when creating new accounts" [Medium,Confirmed]  http://launchpad.net/bugs/70807
[11:36] <kiko> oh Ubugtu stop complaining
[11:36] <kiko> Seveas, all this bot does is whine about bugs in launchpad!
[11:42] <ddaa> Seveas: it would be nice if it also said something when a bug is closed
[11:48] <mpt> "Bug 12345678 changed status from In Progress to Committed. Hooray!"
[11:52] <ddaa> BjornT: okay, I'll do the various renaming and documentation adjustments tomorrow
[12:05] <Seveas> kiko, for #launchpad that actually may be a good thing
[12:05] <kiko> heh
[12:05] <Seveas> maybe after the conference or in a dead hour (of which there have been none so far)
[12:08] <kiko> dead hours are my favorites
[12:09] <kiko> BjornT, ping?
[12:10] <kiko> BjornT, ping me when you have a sec