=== statik` is now known as statik === mrevell is now known as mrevell-lunch [17:48] * Rinchen checks to ensure his ntp is functioning. === mrevell-lunch is now known as mrevell [17:56] ooops, it wasn't that long a lunch, honestly :) [17:58] me [17:59] nice an orderly queues now please [17:59] :) [17:59] what? like the pqm one? [17:59] me [18:00] #startmeeting [18:00] Meeting started at 18:00. The chair is Rinchen. [18:00] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [18:00] Welcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development. [18:00] * Agenda [18:00] * Roll call [18:00] * Next meeting [18:00] * Actions from last meeting [18:00] * Oops report (Matsubara) [18:00] * Critical Bugs (Rinchen) [18:00] * Bug tags [18:00] * Operations report (mthaddon) [18:00] me [18:00] * DBA report (stub) [18:00] * Sysadmin requests (Rinchen) [18:00] me [18:00] * New packages required (salgado) [18:00] me [18:00] * A top user-affecting issue (mrevell) [18:00] * Blockers [18:00] me [18:00] [TOPIC] Roll call [18:00] New Topic: Roll call [18:00] me [18:00] me :-) [18:00] me [18:00] me [18:00] me [18:00] me [18:00] me [18:00] me [18:00] me [18:00] Rinchen: we usually used to do a roll call first :) [18:00] me [18:00] me [18:00] me [18:00] me [18:00] me [18:00] danilos, I changed the agenda :-) [18:01] me [18:01] carlos: you? [18:01] me [18:01] me [18:01] ;-) [18:01] me [18:01] me [18:01] me [18:01] me [18:01] me [18:01] me [18:01] me === kiko-fud is now known as kiko [18:02] BjornT, ? [18:02] me [18:02] EdwinGrubbs? [18:02] ah [18:02] sorry [18:02] ok, moving on [18:03] [TOPIC] Next meeting [18:03] New Topic: Next meeting [18:03] Thursday the 21st, same time, same channel? [18:03] Holiday in Thailand. [18:03] me [18:03] kiko? [18:03] same time same channel! [18:03] [AGREED] Thursday the 21st, same time, same channel [18:03] AGREED received: Thursday the 21st, same time, same channel [18:04] [TOPIC] Actions from last meeting [18:04] New Topic: Actions from last meeting [18:04] we had a lot [18:04] rock on MootBot [18:04] herb! welcome [18:04] I'll skip the ones marked done in the agenda [18:04] * intellectronica to investigate Bug 185135 [18:04] Launchpad bug 185135 in blueprint "+roadmap page still times out" [Undecided,Confirmed] https://launchpad.net/bugs/185135 [18:05] * Salgado and Kiko to discuss recent 404s [18:05] statik: danke [18:05] Rinchen: haven't had the time to. tonight or tomorrow, hopefully [18:05] 3me mumbles something about batching [18:05] Rinchen, done [18:05] [ACTION] repost: intellectronica to investigate Bug 185135 [18:05] ACTION received: repost: intellectronica to investigate Bug 185135 [18:05] Rinchen, we did! [18:05] * jtv to investigate OOPS-764F1198 [18:05] https://devpad.canonical.com/~jamesh/oops.cgi/764F1198 [18:05] * matsubara to file a bug about the DateTimeWidget oops [18:05] Rinchen: done and fixed. [18:05] flacoste: won't work. we can discuss later, elsewhere [18:05] Rinchen: that wasn't necessary [18:05] * matsubara to investigate a bunch of oopses [18:06] * Steve to arrange a call sometime next week with stub and some people from the Foundations team to talk over AuthPersonSplit [18:06] there's a call arranged for monday [18:06] Rinchen: the datewidget bug was fixed on r5616 [18:06] that's been SteveA and stub's favorite subject this week ;) [18:06] Rinchen: the bunch of oopses are now properly reported bugs [18:06] * kiko hi 5s SteveA [18:06] * mrevell to ping Rinchen about new blog spam [18:06] * SteveA hi5s [18:06] blog spam? [18:06] I raised that in priority [18:06] yeah [18:06] We get quitea bit of comment spam [18:07] would getting openid used with the blog help? [18:07] I think I see that [18:07] I also fixed the existing undelete-able spam somehow [18:07] SteveA: and who from the Foundations team will join that call? [18:07] SteveA, yes [18:07] Rinchen: Yeah, rock on :) [18:07] SteveA, er no [18:07] openid! we can't even get our moin instances running that!!! [18:07] flacoste: salgado and stub arranged it together [18:07] mrevell: it's wordpress, innit? why don't we use the akismet service? [18:07] SteveA, the problem is that we allow anyone to post comments [18:07] SteveA, for moderation [18:07] intellectronica: Ask IS :) It calls home. [18:07] the spam is in the moderated comments [18:07] SteveA: nice! [18:07] Rinchen: if we allowed only launchpad users to post comments [18:07] Rinchen: would that help? [18:07] SteveA, yes [18:08] so, openid with directed identity to lp would help [18:08] In that vain, yes [18:08] * salgado to investigate adding turbogears for codebrowse and germinate [18:08] Rinchen, vein. [18:08] The akismet plugin for wordpress makes it almost a nonissue [18:08] Yes, that would solve everything we get right now. [18:08] Rinchen, and the moin stuff? [18:08] Rinchen, not done [18:08] Rinchen: let's tie off that vain [18:08] hehe [18:08] Rinchen: blow that weather vain [18:08] kiko, would fix bzr's spam [18:08] * flacoste to discussing adding launchpad-dependencies inside the sourcecode tree with salgado [18:09] * danilos to investigate profiling and Rosetta team to prepare proposal for next week to fix remaining timeouts [18:09] Rinchen: done, report sent to list [18:09] I prepared a script to extract most of the data for rosetta timeouts statistics based on oops-tools used for OOPS weekly summaries, but haven't yet prepared a nice report (please carry on to next meeting) [18:09] [ACTION] repost: salgado to investigate adding turbogears for codebrowse and germinate [18:09] ACTION received: repost: salgado to investigate adding turbogears for codebrowse and germinate [18:09] * abentley hopes in vane that SteveA will stop [18:09] [ACTION] repost: danilos to investigate profiling and Rosetta team to prepare proposal for next week to fix remaining timeouts [18:09] ACTION received: repost: danilos to investigate profiling and Rosetta team to prepare proposal for next week to fix remaining timeouts [18:09] danilos, okay, thanks for doing this, though -- the timeouts are a big deal [18:09] last one [18:09] * matsubara to get last week +translate timeouts OOPS ids for danilo [18:10] Rinchen: I gave the pointers to danilo so he could hack the oops scripts himself [18:10] kiko: what I can get right now is this: https://pastebin.canonical.com/2433/ (though, I also have data by the query, and as I suspected 'get external' suggestions is 10x what get local is) [18:10] k, [18:10] thanks for the updates [18:10] [TOPIC] Oops report (Matsubara) [18:10] New Topic: Oops report (Matsubara) [18:10] Rinchen: yeah, matsubara helped with this [18:10] Rinchen: http://wordpress.org/extend/plugins/openid/ [18:10] Today's oops report is about bugs 191887, 191891, 191899 [18:10] Launchpad bug 191887 in rosetta "Translation import queue filter displays inactive projects" [High,Confirmed] https://launchpad.net/bugs/191887 [18:10] Launchpad bug 191891 in launchpad "OOPS accessing +expiringmembership for a person." [Undecided,Confirmed] https://launchpad.net/bugs/191891 [18:10] Launchpad bug 191899 in launchpad "OOPS renaming a team with a mailing list activated " [Undecided,New] https://launchpad.net/bugs/191899 [18:10] Talked with jtv already about #191887. [18:10] Talked with salgado about #191891. Seems to be a low importance bug since one [18:10] needs to manually craft the URL to trigger the oops. [18:10] matsubara, agreed [18:11] barry re #191899, can you get that one fixed for this release? [18:11] matsubara: I added a comment for #191887 too [18:11] thanks carlos and salgado [18:11] matsubara: not this week. i'm on leave until tuesday [18:11] I'm not seeing any OOPSes on edge, which is good [18:12] I still see the same old same old nonsense on production though [18:12] UDE/UEE [18:12] feeds stuff [18:12] @@ nonsense [18:12] barry: I guess that's ok, since the +review page doesn't seem to be linked anywhere and only lp admins can access it [18:12] barry: can I set it to the next milestone though (1.2.3)? [18:12] danilos, this is very very cool [18:12] matsubara: right. maybe we can do it as an rc next week? [18:13] barry: and assign to you, etc. [18:13] matsubara: +1 [18:13] I don't think that's worth a RC [18:13] for the reason outlined above [18:13] matsubara: cool. 1.2.3 is fine [18:13] barry: great, thanks! [18:13] done here Rinchen, back to you [18:13] if it's critical it should be done now. If not, then it's not worth of an RC [18:13] np, thanks! [18:13] [18:13] Rinchen: not critical [18:13] :-) [18:13] kiko: thanks, and there should be more coming :) [18:13] Thanks matsubara [18:13] [TOPIC] Critical Bugs (Rinchen) [18:13] New Topic: Critical Bugs (Rinchen) [18:14] well, I was all excited to talk about [18:14] [LINK] https://bugs.edge.launchpad.net/rosetta/+bug/190145 [18:14] LINK received: https://bugs.edge.launchpad.net/rosetta/+bug/190145 [18:14] Launchpad bug 190145 in rosetta "Last translator credit is not updated on export time" [Critical,Fix committed] [18:14] but it seems carlos has fixed it [18:14] ha ha ha [18:14] as the swede says OLD NEWS [18:14] Rinchen: [18:14] Rinchen: I did, yes [18:14] Thanks carlos. [18:14] Rinchen: and it's in rocketfuel already [18:15] I have nothing further on critical bugs other than to thank everyone for continuing to fix them in a very timely manner [18:15] [TOPIC] Bug tags [18:15] New Topic: Bug tags [18:15] We have one [18:15] mailing-lists by flacoste [18:15] [LINK] https://help.launchpad.net/TaggingLaunchpadBugs [18:15] LINK received: https://help.launchpad.net/TaggingLaunchpadBugs [18:15] is 'lists' descriptive enough? [18:15] +1 for mailing-lists [18:16] lists would also probably work, unless we have lists of other things [18:16] it's very generic. [18:16] we have lists of bugs [18:16] could be intrepreted as listing [18:16] well, we have lists of everything :) [18:16] lists is too generic [18:16] we have wishlist bugs too [18:16] no [18:16] mailing-lists [18:16] mailing-tuples [18:16] hehe [18:16] j/k [18:17] +1 for mailing-lists [18:17] HOW CAN THAT BE A JOKE Rinchen??? [18:17] I'm +1 for mailing-lists [18:17] +1 for mailing-lists [18:17] +1 for mailing-lists [18:17] mailing-lists [18:17] although, if they're bugs [18:17] it should be failing-lists [18:17] (bada-ching) [18:17] ok. So carried. flacoste do the honours with the web page please [18:17] * barry says, knowing that there's no possibility mailing lists will ever actually have a bug [18:17] [AGREED] mailing-lists tag approved [18:17] AGREED received: mailing-lists tag approved [18:17] fucking clowns [18:18] [TOPIC] Operations report (mthaddon) [18:18] New Topic: Operations report (mthaddon) [18:18] and herb? [18:18] yes [18:18] First of all, would like to introduce our new OSA - herb - Herb started at the beginning of this week and will take a while to ramp up, but any OSA requests that you would normally have sent just to me, please cc Herb as he gets up to speed. [18:18] Rollout next week will be a little longer than usual due to new DB server being put in place. Exact timing TBD as it will involve people in a few different timezones :) (should be able to finalise in the next day or two) [18:18] That's it from me unless there are any questions [18:18] herb: welcome! [18:18] were any legs cut off with leathermen this week? [18:18] welcome herb! [18:18] or is that herb's first task! [18:18] thanks all [18:19] why do we send OSA requests to you, rather than to a functional mail address? [18:19] (like rt or something) ? [18:19] herb: which timezone are you usually in? [18:19] SteveA, presumably because there's only been one of me til now :) [18:19] US/Eastern [18:19] mthaddon: let's change that, now herb is here [18:19] SteveA, sounds good - will do and will email the list with the appropriate info [18:19] thanks mthaddon [18:19] good show, chaps [18:19] herb, good to have you closeby then! [18:19] [IDEA] Find a better way to communicate with our OSAs now that there are two. [18:19] IDEA received: Find a better way to communicate with our OSAs now that there are two. [18:20] [TOPIC] DBA report (stub) [18:20] New Topic: DBA report (stub) [18:20] When I looked this morning, the rocketfuel archives on devpad where not packs. What time frame do we have for switching them over too? [18:20] New hardware coming next rollout. Woot. [18:20] I think we are on top of this cycle's DB patches. One more of my branches to land, a test suite update from cprov and a late submission from Elliot that should land tomorrow. [18:20] Interested parties should look over the AuthPersonSplit spec. Talk to me or the mailing list about any issues you think it raises or changes it needs. [18:20] [LINK] https://launchpad.canonical.com/AuthPersonSplit [18:20] I want devs running PostgreSQL 8.3 as soon as possible. I think this just involves updating our tsearch2 index maintenance tool. We won't worry about a timeline for switching PQM, staging or production though until we have kicked the tires locally. [18:20] LINK received: https://launchpad.canonical.com/AuthPersonSplit [18:20] Think that is all. [18:21] topic on #bzrlp claims they're packs now. [18:21] I'm all for running on 8.3 [18:21] stub: I'm fixing that test right now. [18:21] as soon as that script is fixed [18:21] stub, packs for devpad would be down to lifeless - I believe we're using packs on praseodymium, but not devpad yet [18:21] but it also requires a change in the developer-dependencies package [18:21] as that specifies 8.2 right now [18:21] that could be awkward [18:21] stub, do you have some documentation about how to upgrade anything that needs upgrading from 8.2 to 8.3 on dev machines? [18:22] statik: maybe it's possible to install them side-by-side? [18:22] as I think the production dependencies and developer dependencies are linked somehow [18:22] You can happily specify both 8.2 and 8.3 - they coexist [18:22] hmm, perhaps I did something weird when I installed in hardy [18:22] of course only one is going to be at TCP port 5432... [18:22] Rinchen: That will come when I know how we will do it [18:22] I saw that the configs co-existed, but I thought that 8.3 uninstalled 8.2 [18:22] nevermind [18:23] statik, no, a big migration happened after dapper to allow parallel installs [18:23] statik, pitti is a master [18:23] awesome [18:23] [IDEA] devs should upgrade to postgres 8.3 as soon as we are ready [18:23] IDEA received: devs should upgrade to postgres 8.3 as soon as we are ready [18:23] anything else for stub? [18:24] stub, how are the DB patches looking? [18:24] stub, statik: you guys sorted out your pending issues? [18:24] stub, salgado: ditto? [18:24] kiko: all set [18:24] cprov, anything left from you apart from the test failure fix? [18:24] 01:20:48) stub: I think we are on top of this cycle's DB patches. One more of my branches to land, a test suite update from cprov and a late submission from Elliot that should land tomorrow. [18:24] just making sure [18:24] cool! [18:24] Oh.... [18:25] kiko: no, I have a fix for it [18:25] And the CodeReviewVoting stuff needs to be finalized, but it is probably too late in the cycle to get that new design approved [18:25] stub: maybe it is [18:26] stub: I've talked through with sabdfl about it [18:26] thumper, stub: is there a point to landing this early? [18:26] kiko: it would help work for the next cycle [18:26] that's all [18:26] "We'd like to get these changes landed for 1.2.2 in order to work and land the code review work during 1.2.3 without worrying about the database." [18:27] well... don't really see that much of an issue [18:27] kiko: it isn't critical, just handy [18:28] land early instead of having to wait for the DB to open [18:28] I'll see what we can do anyway. [18:28] flacoste, just base work on the same branch and get them reviewed in steps.. I dunno. [18:28] is there an interest in disclosing this in parts? [18:29] ready to move on? [18:29] kiko: it makes manageing conflits easier [18:29] [TOPIC] Sysadmin requests (Rinchen) [18:29] New Topic: Sysadmin requests (Rinchen) [18:29] Hi! Is anyone blocked on an RT or have any that are becoming urgent? [18:30] pas moi [18:30] RTs have continued to see good progress lately due to the addition of additional IS staff, so I'm excited about that. [18:30] although we have a lot in the queue still [18:30] last call.... [18:31] Rinchen: ah, fyi, dpkg LZMA is being rolled out in production as we talk, and the soyuz fix is already in PQM [18:31] (slightly related with blocking RT) [18:31] cprov, rock on! is it in lp-deps already? [18:31] great stuff, thanks. [18:31] that's a good lead in.... [18:31] [TOPIC] New packages required (salgado) [18:31] New Topic: New packages required (salgado) [18:31] if any of the branches you're working on right now depends on any library which is not part of the launchpad-dependencies package, come talk to me ASAP. [18:31] kiko: no, gutsy version already supports it [18:31] cprov, ah, cool. [18:32] any takers? [18:32] salgado, what's the latest you've added to lp-deps? [18:32] py-lxml, simplejson [18:32] and tickcount [18:32] see... codebrowse would answer that question for us, if this was in a bzr branch [18:33] just sayin' [18:33] it's faster for salgado to reply than to wait for codebrowse... just sayin' [18:33] ooh [18:33] getting ugly now [18:33] flacoste, that's not a nice thing to say [18:33] so I think apt-cache works fine for me [18:33] I just wanted to hear salgado's voice [18:34] right then.... [18:34] [TOPIC] A top user-affecting issue (mrevell) [18:34] New Topic: A top user-affecting issue (mrevell) [18:34] flacoste: oy [18:34] howdy [18:34] Recently, I've noticed a number of licence project submissions come in as "Other/Proprietary". [18:34] The wording we use to state which licences are acceptable is a little vague right now: [18:34] "Launchpad.net is free to use for software projects that comply with these licensing policies." [18:34] mrevell, I have been good at KILLING THOSE very quickly when statik isn't looking [18:34] That's linked to http://www.ubuntu.com/community/ubuntustory/licensing [18:34] heh [18:34] There's also been some confused messages sent using the "Description of additional licenses:" box. One person selected every licence available and wrote, "I need at least one licence, please". [18:34] * kiko pimps "apt-cache show launchpad-dependencies" [18:34] I propose we add an introductory sentence above the licence check-boxes. Something like: [18:35] "Select the licence(s) under which you release your project." [18:35] And also strengthen the wording below to say, "Launchpad.net is free to use for software projects that share their source code and comply with these licensing policies. Contact us if your project uses a proprietary licence." [18:35] Unless people have objections or suggestions, that's me done. [18:35] mrevell: I like that suggestion, that is an action for me or EdwinGrubbs [18:35] mrevell++ [18:36] Cool. We can link "contact us" to help.launchpad.net/Feedback [18:36] yes, action for EdwinGrubbs [18:36] statik: want me to file a bug? [18:36] [ACTION] statik/EdwinGrubbs - add introductory sentence above the license check-boxes for clarification. [18:36] ACTION received: statik/EdwinGrubbs - add introductory sentence above the license check-boxes for clarification. [18:36] Or perhaps have Other/proprietary produce a "contact us" page? [18:36] abentley: Are you channeling mpt? :) [18:36] abentley: I'm not so sure about that [18:36] it may encourage people to just to back [18:37] and then, um, lie [18:37] I think it's important people complete a process [18:37] the same process in each case [18:37] and then we contact them [18:37] (without fibbing) [18:37] taking them to a "contact us" page [18:37] means they haven't completed the process of registering [18:37] I guess my experience has been that documentation is not always effective, especially as the amount of it increases. [18:37] and if their goal is to register, they may well find some other way to achieve that end [18:37] and btw, I am pretty quick to nuke those projects. :) [18:38] finger on da button [18:38] abentley, I agree with your experience. :-) [18:38] anything else for mrevell ? [18:38] But it's always a matter of taste. [18:38] abentley, you're right. the thing is that these people /already/ contact us [18:39] nope, that's me. thanks. [18:39] abentley, this is really a big project -- we get a /lot/ of public requests [18:39] it's quite unlike running your own software project [18:39] I had never expected this [18:39] but we get hundreds of bogus requests a week [18:39] requests in random languages [18:40] people asking for Ubuntu CDs on a list whose mailman page says in RED LETTERS no ubuntu cds please [18:40] etc [18:40] I've no doubt. [18:40] yeah, being popular sucks [18:40] Rinchen, movin' on.. [18:40] There are no submitted additional topics. You know what that means! [18:40] We need RED LETTERS in random languages then [18:40] [ACTION] mthaddon - discuss updating devpad rocketfuel archives to packs and do so if lifeless approved. [18:40] * barry invokes the pinball machine rule [18:40] [TOPIC] Blockers [18:40] New Topic: Blockers [18:41] Releases Team: Not blocked. [18:41] Foundations: not blocked [18:41] Translations: Not blocked. [18:41] Bugs: not blocked [18:41] hwdb: not blocked [18:41] [ACTION] mthaddon - discuss updating devpad rocketfuel archives to packs and do so if lifeless approved. [18:41] Soyuz: not blocked [18:41] [ACTION] mthaddon - discuss updating devpad rocketfuel archives to packs and do so if lifeless approved. [18:41] Code: Not blocked [18:41] * flacoste wonders what th pinball machine rule is [18:41] ACTION received: mthaddon - discuss updating devpad rocketfuel archives to packs and do so if lifeless approved. [18:41] lpcomm: not blocked [18:41] SC: not blocked [18:41] * jtv wonders like flacoste does [18:41] stub, action is restricted to mtg chair unlike LINK and IDEA [18:41] facist [18:41] not my code :-) [18:42] * SteveA channels kiko [18:42] stub: "fascist" [18:42] SteveA: He may have meant "faeces" [18:42] oh oh i'm being oppressed! [18:42] right [18:42] Thank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs. [18:42] #endmeeting [18:42] Meeting finished at 18:42. [18:42] * Rinchen laughs [18:42] thank you everyone! [18:42] thanks Rinchen ! [18:42] Rinchen: thanks for a on-time meeting! [18:42] thanks [18:42] barry: what's the pinball machine rule? [18:42] Rinchen: thank you [18:43] barry: yeah, what's the pinball machine rule? [18:43] kthxbye [18:43] thank you, guys [18:43] no tilts? [18:43] google warsaw's fourth law :) [18:43] flacoste: The Pinball Machine Rule is the observation that it doesn't matter a wit if the instructions are printed clearly for all to see, nobody will read them. They'll just drop their quarter(s) and start pushing buttons like a Tommy. -- Barry Warsaw [18:43] barry: Isn't that something to do with international flight? [18:43] :) [18:43] opressors rock [18:43] :) [18:43] lol [18:44] Tommy? [18:44] rock opera [18:44] Where where you in the 60s? [18:44] jtv, the who? [18:44] about a pinball wizard [18:44] jesus [18:44] kiko: No, Tommy. [18:44] I hear he was quite good with pinball. levitated the obstacles out the way [18:44] ♬ Sure plays a mean pinball ♬ [18:45] Damn, it's been a while since I heard that... === salgado is now known as salgado-phone === salgado-phone is now known as salgado === salgado is now known as salgado-afk