=== _thumper_ [n=tim@tpsoft.gotadsl.co.uk] has joined #launchpad-meeting === ddaa [n=ddaa@nor75-18-82-241-238-155.fbx.proxad.net] has joined #launchpad-meeting === jamesh [n=james@203-59-208-48.dyn.iinet.net.au] has joined #launchpad-meeting [11:00] Good morning [11:00] SteveA: jamesh: spiv: lifeless: MEETING STARTS [11:00] Good evening. [11:00] lifeless: hello limited IRC client [11:00] hi [11:01] == Agenda == [11:01] Next meeting Monday 6 November, 10:00-10:45 UTC. [11:01] * production status [11:01] * status reports [11:01] * Singapore meeting [11:01] == Roll call == [11:01] _thumper_ is on leave until start of December. [11:01] ddaa: hello impersonation [11:01] lifeless: whut? [11:01] hi [11:01] I'm identified, I'm no impersonation. [11:01] I'm teasing you back [11:02] okay, poolie is "gone away for a bit" [11:02] its now 9pm here [11:02] I'm going to ask the reviewers meeting to move, and I'd like to ask this one to move back one hour too. [11:02] maybe he should change his away message to "gone away for a byte", though [11:02] == Production status == [11:03] this is applicable to the 'next meeting' topic. [11:03] you mean one hour earlier? [11:03] yes [11:03] hu... 10am is harsh [11:03] 10pm start for a meeting is harsher [11:04] :) === poolie [n=mbp@ppp112-44.static.internode.on.net] has joined #launchpad-meeting [11:04] (hi, excuse me) [11:04] I disagree, but I guess it's a matter of style [11:04] ddaa: harsh for people who keep normal hours :) [11:04] poolie: hi. I've just been saying, that I'd appreciate it if this meeting could move to 0900 UTC [11:04] I'm okay to give it a try [11:05] I'm fine with that (unsurprisingly). [11:05] though I might have a hard time showing up and being useful that early in the morning [11:05] SteveA: any objection? [11:06] I'm indifferent -- the meeting is still 6pm for me [11:06] i'd like that too [11:06] Okay: Next meeting Monday 6 November, 09:00-09:45 UTC. [11:06] be the coffee be with me [11:06] thank you [11:07] I object to your not being useful in the morning. [11:07] I'm fine with the new time [11:08] SteveA: one of the good things with this job for me, is that it's compatible with this congenital problem I have with mornings. [11:08] your genitals do not rise well in the mornings ? [11:08] I really did not need to know that. [11:08] lifeless: let's not go there [11:08] you're working closely with antipodeans [11:08] so, I think you should find a way to work effectively in european mornings [11:08] lifeless: you should know about that, we slept long enough in the same room [11:09] Let's move on. Waking up early has been a problem for me all my life. [11:09] == Production status == [11:10] try to go more for existentialism than fatalism [11:10] Nothing much new this week. I have been testing some new code in importd-autotest. [11:10] jamesh: anything new in production from you? [11:10] "the morning exists, and it isn't fatal" [11:10] I have a new agenda item too, please be sure to ping me at the end. Right now, I'm partially here, partially busy. sorry. [11:10] ddaa: stub ran the product-release-finder in production, so we have a bunch of new ProductRelease records [11:11] Haha! [11:11] I don't think I've got anything else new launchpad-bazaar related in production this week [11:11] This is sort of related to production status: what's the status of the bzr webserve on devpad? [11:11] any plan to run it on a regular basis? [11:11] ddaa: I think he's got it running regularly, but I will check [11:11] spiv: I thought you were in charge of this sort of thing :) [11:11] the bzr webserver is running on devpad, we need to get it RTed to be hooked up to an external server. [11:12] I think there may be an RT issue on this already [11:12] it should be protected with a certificate, perhaps, or a password [11:12] SteveA: you meeting setting a http proxy so it's accessible from outside the DC? [11:13] its running, stevea pout in a rt reuqest [11:13] can't parse that [11:13] A glance at the devpad apache config suggests it's there, and protected by needing certificate, but I don't seem to have the client cert it needs. [11:13] I need to pout in an RT request? [11:13] you did [11:13] at the time [11:13] It's elmo's hidden weakness. [11:13] lifeless: looking at the apache config on devpad, https://devpad.canonical.com/code/rf/launchpad/devel requires a cert and passes through to localhost:8088 [11:13] jamesh: yes [11:13] as spiv said :) [11:13] "we need to get it RTed to be hooked up to an external server.", you mean hooking up to allow people to access it without setting up their own ssh tunnel? [11:14] and we tried last week. But the cert seems to be unknown [11:14] jamesh: nearly, except that it needs a trailing slash ;) [11:14] Or did last week... [11:14] ddaa: start over. There is a bzr webserve accessible at https://devpad.canonical.com/code/rf/launchpad/devel/ but no-one has the certificate needed. [11:14] ack [11:14] someone needs to rt a certificate replacement [11:14] Ok, so it's with the admins, and there is RT request floating about somewhere. [11:15] And SteveA owns the RT? [11:15] well [11:15] the preior RT would have been done. We need a new one to fix its access :) [11:17] spiv: care to follow up on this? [11:17] Ok. [11:17] Oh something else. I put a RT to get up-to-date pysvn bindings on import slaves. [11:17] needed for current rocketfuel code [11:17] will talk with SteveA about this later [11:18] Moving on. [11:18] == Status reports == [11:18] * spiv: supermirror-smart-server. [11:18] * jamesh: product-release-finder. [11:18] * ddaa: python import. [11:19] nothing more to report on p-r-f than it having been run in production [11:19] so, I tested the python import with the new cscvs/partial-copy code, found a flaw in my initial design, will fix soon. After this there are very good odds that python and silva are going to work. [11:19] sweet [11:19] I have no news on the supermirror-smart-server. [11:20] ddaa: awesome [11:20] There are also some other random importd bugfix in importd-autotest ATM, so it might be that they helped a bit too. See you soon on PendingReviews. [11:20] * jamesh: spec-branches. [11:20] * ddaa: pyrex. [11:20] * poolie: bzr-lp features. [11:21] I uploaded my current work on pyrex bindings to devpad, and put in pending reviews. The good stuff is going to depend on the partial-copy landing, but the current work probably needs a fair amount of review polish first. [11:21] I didn't get round to discussing spec-branches with you, so haven't got anything to report on it [11:22] oh right [11:22] jamesh: let's set up a time to discuss spec-branch. Say, tomorrow 10:00 UTC? [11:22] okay [11:22] or later if that's okay with you :) [11:23] poolie: anything new from the bzr-lp soap-box that you wish to mention before talking about the Singapore meeting? [11:23] can do 11 UTC if that's better for you [11:24] jamesh: by all means [11:24] Tomorrow 11:00 UTC [11:24] poolie: hello? [11:25] ddaa: tim has written up a good number of bzr-lp features [11:25] from our meeting in singapore [11:25] okay, so let me start the next item and the stage is yours [11:25] ok [11:25] == Singapore meeting == [11:25] * poolie: Report on outcome of the Singapore meeting. [11:26] ok, we had a good meeting [11:26] please, tell us what went on down there! [11:26] our effort is in three main areas [11:26] ddaa: I'm still in the office of the silva people, so I'd like to know when there's something for them to play with [11:26] bzr by itself; bzr with launchpad; and bzr for the distro [11:26] a summary might be better done in email; i can do that later [11:26] SteveA: barring emergencies, that could be up in production within a week. [11:27] but, there are no major changes of direction [11:27] for lp some of the top priorities are going to be [11:28] tim alluded to the fact that he got a nice full plate [11:28] - getting more value out of attaching branches to bugs - show badges to indicate this; let people get the diff to the landing target; a simple review interface [11:28] we want to work on having private branches and products so that launchpad can dogfood more of this [11:28] also to get a code browser up [11:29] and to move jamesh's review and merge analysis tools into being launchpad features [11:29] I like the sound of all this. [11:29] I noticed that you'd marked the braindump spec I wrote about that as obsolete [11:29] spiv, ddaa, when i've checked they're all recorded as specs i'd like to let you grab things from the feature buffet [11:29] jamesh: the one about bug-branch metadata? [11:29] poolie: PendingReviews in launchpad [11:29] only because there are several specs in the same area and they should merge [11:30] poolie: so you'd like use to do some spec gardening, obsoleting superceded specs in favor of the new ones? [11:31] jamesh: i don't remember changing that - maybe someone did from my machine? [11:31] or you mean you'd like us to start implementing stuff? [11:31] ddaa, jamesh, spiv: yes, i would like if you could quickly garden the specs [11:31] poolie: https://features.launchpad.net/products/launchpad-bazaar/+spec/pending-reviews-on-launchpad [11:31] i meant i'd like to talk about what you'll each be doing in the next while, and which features you might want to work on [11:32] ACTION: ddaa, spiv, jamesh: garden launchpad-bazaar specs [11:32] poolie: I'd like to focus on making vcs-imports not suck... [11:32] poolie: this should wait until you've checked the singapore specs are all recorded, I assume? [11:32] spiv: yes, that's what i meant [11:32] Good, just making sure. [11:33] and fixing some other infrastructure issues, before adding new features [11:33] ddaa: ok, let's talk about that later - say 0900 UTC tomorrow? [11:33] 1000 UTC? [11:33] i sympathize, i just want to understand what the roadmap is [11:34] let's start on mail first [11:34] ok [11:34] lifeless: any other notable points from singapore for you? [11:34] yes [11:34] one of the goals of the singpore meeting was hct planning [11:34] cause we still want to achieve hct! [11:35] so I'd like to give a little status update on hct. [11:35] lifeless: before you do [11:35] some of the discussion there is canonical-specific [11:35] and this is not a canonical-specific channel [11:36] yeah, this is a bit awkyard [11:36] can we lock it or something? [11:36] who's the channel operator? [11:36] uhm [11:36] note that the channel is being logged [11:36] ubuntulog is probably the problem. [11:36] so let met say some vague things instead. [11:37] my primary goal of having a path forward has been achieved. [11:37] and this is tied into our long term plans as usual. [11:37] lets talk on #canonical-meeting about the specifics [11:38] also, edgy++. [11:39] ok [11:39] we can go to #launchpad-basement [11:39] several package maintainers are now keeping their packaging info in bzr [11:39] we want to encourage more of this [11:39] ddaa: in general, #launchpad-xxx channels are public, #canonical-xxx channels are private [11:39] there are grey areas here though [11:40] poolie: right. [11:40] so there is a wiki page [11:40] wiki.ubuntu.com/BzrMaintainedPackages [11:40] I think we agreed to try and move that into launchpad [11:41] right - move this into something that's supported by launchpad, and also improve the tool experience for distro developers [11:42] ok, so, next? [11:45] helo? [11:45] poolie: we're in #canonical-meeting [12:05] are we done? [12:05] we're done [12:05] finito === jamesh [n=james@203-59-208-48.dyn.iinet.net.au] has joined #launchpad-meeting