=== kiko is now known as kiko-zzz === kiko-zzz is now known as kiko === salgado-afk is now known as salgado === mrevell is now known as mrevell-lunch === mrevell-lunch is now known as mrevell === Rinchen` is now known as Rinchen === salgado is now known as salgado-lunch === kiko is now known as kiko-afk === salgado-lunch is now known as salgado [17:20] * bigjools waves at al-maisan [17:20] bigjools: thanks! [17:20] np [17:59] meeting time? [17:59] just about [17:59] ahem [17:59] #startmeeting [17:59] Meeting started at 18:59. The chair is Rinchen. [17:59] Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE] [17:59] yea mootbot [17:59] [TOPIC] Roll Call [17:59] me [17:59] New Topic: Roll Call [17:59] me [17:59] me [17:59] me [17:59] me [17:59] me [18:00] me [18:00] meme [18:00] me [18:00] err, me [18:00] me [18:00] mrevell, ? [18:00] nw [18:00] me [18:00] er [18:00] me [18:01] me [18:01] me [18:01] I have apologies from bac, thumper, carlos, BjornT, mwhudson, mpt [18:01] al-maisan: me [18:01] me [18:01] me [18:01] herb, jtv kiko-afk ? [18:01] me [18:01] Rinchen: jtv was in just before the MootBot [18:01] me [18:01] ah see him now, thanks [18:02] Rinchen: and danilos was second [18:02] statik, EdwinGrubbs ? [18:02] me [18:02] Rinchen: thanks for the pnig [18:02] ping [18:02] me [18:02] :-) [18:02] SteveA, ? [18:03] suspect the pycon folks won't be here [18:03] well, moving on then... [18:03] [TOPIC] Agenda [18:03] New Topic: Agenda [18:03] * Next meeting [18:03] * Actions from last meeting [18:03] * Oops report (Matsubara) [18:03] * Critical Bugs (Rinchen) [18:03] * Bug tags [18:03] * Operations report (mthaddon/herb) [18:03] * DBA report (stub) [18:03] * Sysadmin requests (Rinchen) [18:03] * New packages required (salgado) [18:03] * A top user-affecting issue (mrevell) [18:04] * Doc Team report (mrevell) [18:04] * login() and "current" requests in doctest (flacoste) [18:04] * Blockers [18:04] [TOPIC] Next meeting [18:04] New Topic: Next meeting [18:04] next week, same time, same station. [18:04] I know bac will be unable to attend. [18:04] Anyone else? [18:05] and for the lurkers: Welcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development. [18:05] ok then. [18:05] [TOPIC] Actions from last meeting [18:05] New Topic: Actions from last meeting [18:05] matsubara, flacoste and stub to discuss UTF-8 safety of byName and other random attacks to launchpad.net [18:05] kiko - consider changing meeting time during next meeting (Note it was discussed to wait until NZ goes to DST which is April 6th). [18:06] Rinchen: SteveA commented on the bug and we have a kind of resolution [18:06] Rinchen: still need to be implemented though [18:06] Rinchen, I've added the discussion in the bug report and stub said byName are safe enough. the method is doing the right thing. [18:06] flacoste, matsubara - thanks. I'll drop that from the actions list then [18:06] I'm going to punt Kiko's item for a bit [18:07] [ACTION] kiko - consider changing meeting time after April 6th. [18:07] ACTION received: kiko - consider changing meeting time after April 6th. [18:07] [TOPIC] Oops report (Matsubara) [18:07] New Topic: Oops report (Matsubara) [18:07] Today's oops report is about bugs 204344, 67899, 204355 [18:07] Launchpad bug 204344 in launchpad-bazaar "OOPS merging an already merged proposal branch" [Undecided,New] https://launchpad.net/bugs/204344 [18:07] Launchpad bug 67899 in malone "Large emails do not generate error messages to users" [Undecided,Confirmed] https://launchpad.net/bugs/67899 [18:07] Launchpad bug 204355 in malone "UnicodeDecodeError decoding email header" [Undecided,New] https://launchpad.net/bugs/204355 [18:07] sorry for the delay, I was finishing filing the last one. [18:08] me [18:08] anyway, any code team representative today? [18:08] matsubara: I'll bite. [18:08] Wait [18:08] You said code, not bugs [18:08] * gmb goes back to sleep [18:08] bugs is the next one in the queue [18:08] matsubara, I think they are not around today [18:08] :-) [18:08] gmb_of_all_trades? [18:08] I'll assign the code one to thumper and he can decide later on [18:09] gmb, we do have that cross-training program ;-) [18:09] the other two are bugs in the email interface [18:09] so, gmb already volunteered to take those :-) [18:09] *theatrical sigh* [18:09] gmb: i'll take one off you [18:10] actually, I'm not sure if 67899 description is really tru [18:10] [ACTION] matsubara to email thumber the code oops [18:10] ACTION received: matsubara to email thumber the code oops [18:10] true [18:10] intellectronica: Thanks. [18:10] intellectronica, we now tell users that an OOPS happened right? [18:10] matsubara: we do in most cases (depending on the cause for the OOPS) [18:10] in any case, #67899 needs update to tell users why the email was rejected [18:11] right. I'll update the description. [18:11] thanks intellectronica and gmb [18:11] back to you Rinchen [18:11] matsubara: yes, users should get an OOPS report about this error, but a clearer message would be even better [18:11] intellectronica: I'll take 204355 in that case. [18:11] [AGREED] intellectronica and gmb to work on the two bugs oopes [18:11] AGREED received: intellectronica and gmb to work on the two bugs oopes [18:11] gmb: i'll take 67899 [18:11] Bon. [18:12] thanks guys [18:12] [TOPIC] Critical Bugs (Rinchen) [18:12] New Topic: Critical Bugs (Rinchen) [18:12] [LINK] https://bugs.edge.launchpad.net/launchpad/+bug/196936 [18:12] adeuring, how is this going? This is now about two weeks old, no? [18:12] LINK received: https://bugs.edge.launchpad.net/launchpad/+bug/196936 [18:12] [LINK] https://bugs.edge.launchpad.net/rosetta/+bug/196106 [18:12] [LINK] https://bugs.edge.launchpad.net/rosetta/+bug/201394 [18:12] danilo, jtv: how are these going? These are now about two weeks old, no? [18:12] LINK received: https://bugs.edge.launchpad.net/rosetta/+bug/196106 [18:12] LINK received: https://bugs.edge.launchpad.net/rosetta/+bug/201394 [18:12] Launchpad bug 196106 in rosetta "context menu entry "Paste File" [and other dialogs] not translated into German (anymore)" [Critical,In progress] [18:12] [LINK] https://bugs.edge.launchpad.net/rosetta/+bug/203172 [18:12] jtv: What's the plan for this one? [18:12] LINK received: https://bugs.edge.launchpad.net/rosetta/+bug/203172 [18:12] Launchpad bug 203172 in rosetta "Clashing platform-specific msgids in XPI" [Critical,New] [18:12] Rinchen: just implemented that one [18:13] Rinchen: one in pqm queue and waiting for kiko's approval to cherrypick, other only waiting for kiko's approval to cherrypick [18:13] Rinchen: I submitted a bug fix for review [18:13] excellent! [18:13] Rinchen: apparently, not talking about the same thing though :) [18:13] 196106 is in pqm and waiting for cherrypick approval [18:14] Rinchen: 201394 is still in PQM IIRC [18:14] Rinchen: bug 200499 is actually waiting for approval as well [18:14] Launchpad bug 200499 in rosetta "Imported translation from upstream not correctly importing all strings" [Critical,Fix committed] https://launchpad.net/bugs/200499 [18:14] k, that's great. thanks. [18:14] [TOPIC] Bug tags [18:14] New Topic: Bug tags [18:14] we have one [18:14] spurious-test-failure [18:15] but it's for BjornT and kiko-afk [18:15] who are both absent today [18:15] https://help.launchpad.net/TaggingLaunchpadBugs [18:15] thats not a tag it's a paragraph [18:15] :-) [18:15] statik: Yes, but we can't have "bastard" tag. [18:15] i'd be more interested in a "test" tag for all stuff related to the test system [18:15] since the sponsors are not here, I'll leave that until next week [18:16] but thats just my mild opinion [18:16] Why not? That seems a bit specific for me. [18:16] statik, we have that test-system [18:16] ok, cool. [18:16] so I'm going to move and punt this to next week [18:17] [TOPIC] Operations report (mthaddon/herb) [18:17] New Topic: Operations report (mthaddon/herb) [18:17] Two cherrypicks went in for Production last week. [18:17] One cherrypick went in on edge today. [18:17] There is one cherrypick on the LaunchpadProductionStatus page awaiting approval. [18:17] Codebrowse was restarted on Monday in response to an alert. [18:17] lpnet2 was restarted earlier today. [18:17] The help wiki was updated to fix a handful of bugs. [18:17] Unless there are questions, that's it from mthaddon and me. [18:17] err the cherry pick on edge went in on Monday not today. [18:17] herb: any idea of the load on squid? is it holding up alright? [18:18] statik: I haven't looked recently. will take a look after the meeting though. [18:18] herb: cool, thank you [18:18] [TOPIC] DBA report (stub) [18:18] New Topic: DBA report (stub) [18:18] Nothing from me this week. Don't all applaud at once. [18:18] * Rinchen applauds. [18:18] * jtv applauds first [18:18] damn [18:18] * Rinchen laughs. [18:19] stub: I've been running with PG 8.3 locally, is there anything I should be doing to help the migration? [18:19] stub: maris is also running 8.3 i think [18:19] statik: AFIK the whole test suite is passing, so nothing more to do from the devs [18:19] Just a scheduling and.... replication... issue [18:19] excellent [18:20] (hope to use replication to avoid the 3 hours downtime to migrate to 8.3) [18:20] stub, how is the replication activity going? [18:20] stub, we're all excited about it [18:21] Been working on it today [18:21] 8.3 upgrade should be no problem [18:21] The tools to do database migration for devs, staging and production is the problem [18:22] thanks [18:22] What we have is pretty bulletproof at the moment, and I'd like to keep that. [18:23] I think we all would :-) [18:23] thanks [18:23] [TOPIC] Sysadmin requests (Rinchen) [18:23] New Topic: Sysadmin requests (Rinchen) [18:23] Hi! Is anyone blocked on an RT or have any that are becoming urgent? [18:23] I know about Kiko's request for the wikis. [18:24] Rinchen: just my one for the private PPA server [18:24] bigjools, I'll look at that one again. I didn't read through the dialog that happened earlier this week. [18:25] [TOPIC] New packages required (salgado) [18:25] New Topic: New packages required (salgado) [18:25] 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:25] Rinchen: elmo said he would do it after I had a phone call with him, not sure what the status is, but it would be nice to get this for 1.2.3 [18:26] salgado: I sent you a mail: is the libx [18:26] adeuring, already replied [18:26] salgado: thanks! [18:26] [TOPIC] A top user-affecting issue (mrevell) [18:26] New Topic: A top user-affecting issue (mrevell) [18:27] howdy [18:27] I'd like to raise the issue of spam, or other inappropriate cont [18:27] oops [18:27] I'd like to raise the issue of spam, or other inappropriate content, in bug comments. This has come up on launchpad-users and mpt points to bug 45419 (Launchpad needs a way of easily flagging spam). [18:27] Launchpad bug 45419 in launchpad "Launchpad needs a way of easily flagging spam" [Medium,Confirmed] https://launchpad.net/bugs/45419 [18:27] So, I'm wondering if people have noticed more spam in bug comments. mthaddon - as one of the people that deletes spam, have you noticed a change? [18:27] I know it was driving me a bit crazy last week in mthaddon's absence. [18:28] mrevell, definitely enough to be annoying (esp. given our current process for dealing with them), but couldn't give you any real statistical evidence [18:28] basically I think herb and I would be very happy if this was made a bigger priority [18:28] Okay, cheers guys. I want to try to get a feel for whether this an increasing problem, so I'll keep checking back with you [18:28] is it possible to get this targeted - it's taking valuable OSA time? [18:29] mthaddon: maybe as a first step we can make it easier to get rid of a spammy message once it has been identified? [18:29] intellectronica, that would be a great first step [18:29] indeed. [18:29] intellectronica, allowing for administrative editing or deletion of comments would be great [18:29] Is it a big job to implement? [18:29] mrevell: I wouldn't have thought so. [18:29] it would be nice if project admins could police their own projects [18:30] herb: for the moment, we are afraid of censorship [18:30] herb: Yes, but it would be easier to make it so that Launchpad admins could do it. We could move onto project admins later. [18:30] One of the benefits of LP is... oh, flacoste made the point [18:30] herb: so that would require a workflow [18:30] [AGREED] Need to elevate the priority of allowing administrative editing / deletion of comments to help ease the removal of spam [18:30] AGREED received: Need to elevate the priority of allowing administrative editing / deletion of comments to help ease the removal of spam [18:31] thanks guys [18:31] [LINK] https://bugs.edge.launchpad.net/launchpad/+bug/45419 [18:31] LINK received: https://bugs.edge.launchpad.net/launchpad/+bug/45419 [18:31] Launchpad bug 45419 in launchpad "Launchpad needs a way of easily flagging spam" [Medium,Confirmed] [18:31] People can already censor if they are running their own trackers [18:31] I think in reality censorship isn't much of an issue (?) [18:32] especially not when LP makes it so easy to fork a project [18:32] if instead of removing comments we hide them [18:33] it would be easy for people to complain and for an admin to unflag them [18:33] +1 on that idea [18:33] +1 [18:33] ditto [18:33] +1 [18:33] our Legal information dictates a policy for this. Censorship is not something we do. https://help.launchpad.net/Legal [18:33] spam removal is. [18:33] that also solves the problem of comment index moving when removing a comment [18:33] sure, although if a project maintainer wants to 'garden' comments and we don't let 'em they will go elsewhere. [18:33] hiding would be a better solution [18:34] Rinchen: but if you give it to the project admins, it's not "us" censoring anything (should that problem arise). [18:34] indeed [18:34] Rinchen: hey, someone censored my legitimate comment offering cheap generic medicine as a solution to that bug, i protest! ;-) [18:35] :) [18:35] on that note [18:35] [TOPIC] Doc Team report (mrevell) [18:35] New Topic: Doc Team report (mrevell) [18:35] Hey now [18:35] Self medication solves many problems. [18:35] I'm both cheap and generic [18:35] Rinchen: not that kind of "doc" [18:35] I posted some projects and bugs related material to the team list for your review and would grateful for any comments. This week I've had my head down working solidly on the new user guide and some work on new tour material. I know everyone's busy, but if you could take a look and get back to me with comments, that would be most helpful and enable me to make these new docs live. [18:35] Next week, in between release announcement stuff, I'll be working getting this draft of the new tour finished, ready for review. [18:35] Last week kiko mentioned the idea of each LP team working with me to produce some materials. I'm keen for that to happen and would like to speak to each team lead next week. [18:35] mrevell: i'm excited to see the new tour, i point people to the tour almost daily [18:36] statik: Ah great, maybe we should talk early next week. [18:36] monday, 4AM! [18:36] statik: I'd like to know more about what people want from it, that they've told you [18:36] statik: heh, ideal :) [18:36] mrevell: anytime next week I'd love to have a call, monday is pretty open [18:37] statik: I'll send you a calendar invite. [18:37] mrevell, how is the doc team (i.e. users team) progressing? [18:37] I'm interested to see how well that experiment goes [18:38] Rinchen: It's not something I've had time to progress lately, unfortunately. We have people who are interested and have joined the team. Next step is to get an inaugural meeting and let each member know about the mailing list. Neither of which should take me long at all, obviously. [18:38] Week 0 maybe. Ok, thanks [18:39] Yeah, cheers. [18:39] [TOPIC] login() and "current" requests in doctest (flacoste) [18:39] New Topic: login() and "current" requests in doctest (flacoste) [18:39] this is a simple information point [18:39] with the new canonical_url view_name parameter addition [18:39] some of your doc tests may change [18:40] this feature requires that the "current" request (retrieved through get_current_browser_request()) be setup [18:40] otherwise, you'll have AssertionError [18:40] the way to do this is simply to pass a request argument to login() as second parameter [18:40] login(ANONYMOUS, LaunchpadTestRequest()) will work nicely [18:40] that's it! [18:41] flacoste, the existing doc tests will be updated? [18:41] yes [18:41] it's only for new doc test [18:41] great, thanks. [18:41] Any other impromptu topics before we head off? [18:42] 3 [18:42] 2 [18:42] we need to see more mugshots :) [18:42] Yes [18:42] don't like's stub's toe? [18:42] :-) [18:42] Yeah, all LP team members to brand their account! [18:42] We need more material to make pics for pirate day [18:43] A general reminder the LP logo contest ends on 31 March. [18:43] [TOPIC] Blockers [18:43] New Topic: Blockers [18:43] Releases Team: Not blocked. [18:43] Translations: not blocked [18:43] sinzui: pirateday is an illegal site - we don't condone that sort of activity [18:43] Foundations: not blocked [18:43] hwdb: Not blocked. [18:43] Soyuz: blocked on the RT you already know about :) [18:44] intellectronica: you're confusing day with bay. [18:44] lpcomm: not blocked [18:44] [AGREED] Soyuz block on PPA RT [18:44] AGREED received: Soyuz block on PPA RT [18:44] bugs? [18:44] schwuk_: aaaaaaah [18:44] bugs team: not blocked [18:44] Thank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs. [18:44] intellectronica: You mean 'aargh' [18:44] :) [18:44] #endmeeting [18:44] Meeting finished at 19:45. [18:45] photo finish! [18:45] thanks all [18:45] Rinchen: nice timing! thanks for chairing [18:45] Thank you everyone for being so freaking cool. === kiko-afk is now known as kiko === salgado is now known as salgado-afk === kiko is now known as kiko-afk === matsubara is now known as matsubara-afk