[17:52] <mwhudson__> oof
[17:57] <thumper> oof?
[17:59] <Rinchen> foo spelled backwards?
[17:59] <Rinchen> well, I show 18:00
[18:00] <Rinchen> #startmeeting
[18:00] <MootBot> Meeting started at 18:00. The chair is Rinchen.
[18:00] <MootBot> Commands Available: [TOPIC], [IDEA], [ACTION], [AGREED], [LINK], [VOTE]
[18:00] <Rinchen> Welcome to this week's Launchpad development meeting. For the next 45 minutes or so, we'll be coordinating Launchpad development.
[18:00] <Rinchen> [TOPIC] Roll Call
[18:00] <thumper> me
[18:00] <mrevell> me!
[18:00] <MootBot> New Topic:  Roll Call
[18:00] <bac> me
[18:00] <Rinchen> me :-)
[18:00] <sinzui> me
[18:00] <danilos> me
[18:00] <EdwinGrubbs> me
[18:00] <BjornT> me
[18:00] <matsubara> me
[18:00] <danilos> Rinchen: you turned the agenda around again? :)
[18:00] <mwhudson> me
[18:01] <Rinchen> danilos, just for you :-)
[18:01] <Rinchen> bac?
[18:01] <Rinchen> bigjools, cprov ?
[18:01] <bac> ^^^
[18:01] <Rinchen> gmb, herb mthaddon ?
[18:01] <mthaddon> me
[18:01] <cprov> me
[18:01] <gmb> me
[18:01] <mars> me
[18:01] <Rinchen> salgado, ?
[18:01] <salgado> me
[18:01] <Rinchen> stub, ?
[18:01] <thumper> abentley: ?
[18:01] <danilos> Rinchen: I've pinged carlos and jtv
[18:01] <schwuk> me
[18:01] <abentley> me
[18:02] <Rinchen> danilos, thanks
[18:02] <BjornT> intellectronica: ?
[18:02] <intellectronica> me
[18:02] <danilos> Rinchen: ah right, jtv mentioned that he'll be travelling
[18:02]  * bigjools is here for 5 minutes
[18:02] <Rinchen> Steve and kiko are in another meeting so I'm going to press on...
[18:02] <stub> me
[18:02] <salgado> mars, did you say me already?
[18:02] <mars> salgado, me?
[18:02] <Rinchen> [TOPIC] Agenda
[18:02] <MootBot> New Topic:  Agenda
[18:02] <Rinchen>  * Next meeting
[18:02] <Rinchen>  * Actions from last meeting
[18:02] <Rinchen>  * Oops report (Matsubara)
[18:02] <Rinchen>  * Critical Bugs (Rinchen)
[18:02] <Rinchen>  * Bug tags
[18:02] <Rinchen>  * Operations report (mthaddon/herb)
[18:02] <carlos> me
[18:03] <Rinchen>  * DBA report (stub)
[18:03] <adeuring> me
[18:03] <Rinchen>  * Sysadmin requests (Rinchen)
[18:03] <Rinchen>  * New packages required (salgado)
[18:03] <Rinchen>  * A top user-affecting issue (mrevell)
[18:03] <Rinchen>  * Doc Team report (mrevell)
[18:03] <Rinchen> [TOPIC] Next meeting
[18:03] <MootBot> New Topic:  Next meeting
[18:03] <Rinchen> I think we should be able to do next week's meeting.
[18:03] <Rinchen> The Team Leads will be together but that shouldn't stop us :-)
[18:03] <Rinchen> So that would be 6 March, same time, same place
[18:03] <Rinchen> any objections or known absences?
[18:04] <Rinchen> [AGREED] Next meeting 6 March, same time, same place
[18:04] <MootBot> AGREED received:  Next meeting 6 March, same time, same place
[18:04] <Rinchen> [TOPIC] Actions from last meeting
[18:04] <MootBot> New Topic:  Actions from last meeting
[18:04] <Rinchen> repost: salgado to investigate adding turbogears for codebrowse and germinate
[18:04] <Rinchen> repost: danilos to investigate profiling and Rosetta team to prepare proposal for next week to fix remaining timeouts
[18:05] <Rinchen> repost: mthaddon - discuss updating devpad rocketfuel archives to packs and do so if lifeless approved.
[18:05] <salgado> Rinchen, not done yet
[18:05] <Rinchen> [ACTION] repost: salgado to investigate adding turbogears for codebrowse and germinate
[18:05] <MootBot> ACTION received:  repost: salgado to investigate adding turbogears for codebrowse and germinate
[18:05] <danilos> Rinchen: still on it, got some pretty reports now, but not yet discussed with the team
[18:05] <mpt> me
[18:05] <jtv> me too
[18:05] <mpt> (Sorry, had Internet troubles)
[18:05] <Rinchen> [ACTION] repost: danilos to investigate profiling and Rosetta team to prepare proposal for next week to fix remaining timeouts
[18:05] <MootBot> ACTION received:  repost: danilos to investigate profiling and Rosetta team to prepare proposal for next week to fix remaining timeouts
[18:05] <Rinchen> no worries and welcome
[18:05] <mthaddon> Rinchen, on the agenda for the coming week
[18:06] <Rinchen> [ACTION] repost: mthaddon - discuss updating devpad rocketfuel archives to packs and do so if lifeless approved.
[18:06] <MootBot> ACTION received:  repost: mthaddon - discuss updating devpad rocketfuel archives to packs and do so if lifeless approved.
[18:06] <Rinchen> gmb - investigate Bug 193983
[18:06] <ubotu> Launchpad bug 193983 in malone "Oops deactivating account when the account has a conjoined bugtask assigned to it" [Undecided,Fix committed] https://launchpad.net/bugs/193983
[18:06] <Rinchen> kiko and cprov - discuss bug 193656
[18:06] <ubotu> Launchpad bug 193656 in soyuz "Process-death-row procedure became very slow" [Critical,Triaged] https://launchpad.net/bugs/193656
[18:06] <Rinchen> the rest are completed
[18:06] <gmb> Rinchen: That bug has now had a fix comitted.
[18:06] <Rinchen> great thanks gmb
[18:06] <cprov> Rinchen: not done, sorry. I hope we will have time to discuss it together in London next week.
[18:07] <Rinchen> cprov, ok, I'm going to raise that again quickly during the critical bugs :-)
[18:07] <Rinchen> [ACTION] repost: kiko and cprov - discuss bug 193656
[18:07] <MootBot> ACTION received:  repost: kiko and cprov - discuss bug 193656
[18:07] <ubotu> Launchpad bug 193656 in soyuz "Process-death-row procedure became very slow" [Critical,Triaged] https://launchpad.net/bugs/193656
[18:07] <cprov> Rinchen: okay, cool
[18:07] <Rinchen> [TOPIC] Oops report (Matsubara)
[18:07] <MootBot> New Topic:  Oops report (Matsubara)
[18:07] <matsubara> Today's oops report is about bugs 196253, 196661, 196669, OOPS-788EB21, OOPS-788EC5
[18:07] <ubotu> Launchpad bug 196253 in launchpad "OOPS importing pgp key" [High,New] https://launchpad.net/bugs/196253
[18:07] <ubotu> Launchpad bug 196661 in launchpad-answers "Email reply triggered a ProgrammingError" [Undecided,New] https://launchpad.net/bugs/196661
[18:07] <ubotu> Launchpad bug 196669 in launchpad "Change mirror owner to someone who doesn't have a preferred email set crashes the +review form" [Undecided,New] https://launchpad.net/bugs/196669
[18:07] <matsubara> bout OOPS-788EB21, carlos is on it already. I'll file a bug and assign to him.
[18:07] <matsubara> ACTION: matsubara to file a place holder bug for OOPS-788EB21 and assign it to carlos w
[18:07] <matsubara> ho is already investigating it.
[18:08] <matsubara> Any volunteers to fix 196253?
[18:08] <matsubara> salgado, 196669 is for you me thinks.
[18:08] <Rinchen> [ACTION] ACTION: matsubara to file a place holder bug for OOPS-788EB21 and assign it to carlos who is already investigating it.
[18:08] <MootBot> ACTION received:  ACTION: matsubara to file a place holder bug for OOPS-788EB21 and assign it to carlos who is already investigating it.
[18:08] <matsubara> flacoste, can you take a look at the oops in 196661 and check if it was fixed by 191074? If yes, I'll set the status to Invalid.
[18:08] <salgado> matsubara, that sounds like a low priority one to me
[18:09] <matsubara> I need to investigate OOPS-788EC5, it seems related to bug 195809
[18:09] <ubotu> Bug 195809 on http://launchpad.net/bugs/195809 is private
[18:09] <matsubara> ACTION: matsubara to investigate OOPS-788EC5 and confirm if it's related to 195809, if not file a new bug.
[18:09] <Rinchen> [ACTION]  matsubara to investigate OOPS-788EC5 and confirm if it's related to 195809, if not file a new bug.
[18:09] <MootBot> ACTION received:   matsubara to investigate OOPS-788EC5 and confirm if it's related to 195809, if not file a new bug.
[18:09] <matsubara> salgado: please set the status and add a rationale. thanks!
[18:10] <Rinchen> matsubara, flacoste isn't around at the moment. Perhaps an email to him?
[18:10] <salgado> matsubara, as you wish. ;)
[18:10] <matsubara> Rinchen: ok. I'm done then. thanks
[18:11] <salgado> matsubara, btw, you dupper!
[18:11] <Rinchen> [ACTION] matsubara to email flacoste about oops in 196661  and check if it was fixed by 191074
[18:11] <MootBot> ACTION received:  matsubara to email flacoste about oops in 196661  and check if it was fixed by 191074
[18:11]  * salgado always wanted to say that
[18:11] <Rinchen> [TOPIC] Critical Bugs (Rinchen)
[18:11] <MootBot> New Topic:  Critical Bugs (Rinchen)
[18:11] <Rinchen> [LINK] https://bugs.edge.launchpad.net/soyuz/+bug/192713
[18:11] <Rinchen> bigjooles, how is this going?
[18:11] <MootBot> LINK received:  https://bugs.edge.launchpad.net/soyuz/+bug/192713
[18:11] <ubotu> Launchpad bug 192713 in soyuz "PPA packages fail to upload but build successfully" [Critical,In progress]
[18:11] <Rinchen> er bigjools :-)
[18:11] <Rinchen> I'm thinking about the electricity of the moment there
[18:12] <mrevell> :)
[18:12] <Rinchen> [LINK] https://bugs.edge.launchpad.net/soyuz/+bug/193656
[18:12] <Rinchen> cprov, there's been no action on this for a week.
[18:12] <MootBot> LINK received:  https://bugs.edge.launchpad.net/soyuz/+bug/193656
[18:12] <ubotu> Launchpad bug 193656 in soyuz "Process-death-row procedure became very slow" [Critical,Triaged]
[18:12] <cprov> Rinchen: I will assume it, we need another apt backport , this time in gutsy
[18:12] <matsubara> salgado: is it a dupe?
[18:12] <Rinchen> cprov, expecting the backport this week or next?
[18:12] <salgado> matsubara, it is, with a single p
[18:12] <cprov> Rinchen: yes, I know, that's my fault.
[18:12] <matsubara> salgado: I mean, the distro mirror one?
[18:12] <Rinchen> [LINK] https://bugs.edge.launchpad.net/malone/+bug/196125
[18:12] <Rinchen> bjornt, how is this going?
[18:12] <MootBot> LINK received:  https://bugs.edge.launchpad.net/malone/+bug/196125
[18:13] <cprov> Rinchen: ASAP, mvo has it working in his PPA it's just a matter of copying it to gutsy and update lp-dep
[18:13] <BjornT> Rinchen: i think it's considered a non-issue. i'll clarify with stub and update the bug report.
[18:13] <Rinchen> cprov, ok, thank you
[18:13] <Rinchen> BjornT, great! I like not having critical bugs :-)
[18:13] <Rinchen> [TOPIC] Bug tags
[18:13] <MootBot> New Topic:  Bug tags
[18:14] <Rinchen> there are no proposed tags
[18:14] <cprov> Rinchen: btw, do we recommend -backports to be enabled in our development environment ?
[18:14] <Rinchen> cprov, I'm not aware of any recommendation either way there
[18:14] <stub> You will need it for PG 8.3, so yes
[18:14] <Rinchen> cprov, however I do use backports
[18:14] <cprov> salgado: do you know ?
[18:15] <cprov> salgado: or is it better to copy it from -backports to our lpdebs archive ?
[18:15] <Rinchen> cprov, salgado - why don't we cover that in salgado's section
[18:15] <salgado> cprov, well, we don't recommend it, but if we need anything from backports then we'll have to force people to do so
[18:16] <Rinchen> [TOPIC] Operations report (mthaddon/herb)
[18:16] <MootBot> New Topic:  Operations report (mthaddon/herb)
[18:16] <mthaddon> Have migrated to new DB server(s) for production/demo
[18:16] <mthaddon> Staging migration still in progress, expected complete tomorrow
[18:16] <mthaddon> Will be updating documentation to match
[18:16] <mthaddon> Expecting to work on packs updating on devpad this week
[18:16] <mthaddon> That's it from me unless there are any questions
[18:16] <thumper> yay packs
[18:16] <Rinchen> mthaddon, packs tomorrow then?
[18:17] <Rinchen> I also see that herb has the caching for bac due tomorrow. Is that still on schedule?
[18:17] <mthaddon> Rinchen, I don't know if it'll be that quick, but sometime before next week's meeting
[18:18] <Rinchen> I'll ask about that again in the RT section.
[18:18] <Rinchen> [TOPIC] DBA report (stub)
[18:18] <MootBot> New Topic:  DBA report (stub)
[18:18] <stub> New hardware appears to be running happily. Timeouts have dropped, but please don't get lazy :-)
[18:18] <stub> My PostgreSQL 8.3 support branch has landed, so people wanting to can play with Launchpad on PostgreSQL 8.3. DatabaseSetup has been updated.
[18:18] <stub> Migration of Launchpad to PostgreSQL 8.3 goes:
[18:18] <stub> 1) Developers running PostgreSQL 8.3
[18:18] <stub> 2) Staging running PostgreSQL 8.3
[18:18] <stub> 3) PQM running PostgreSQL 8.3
[18:18] <stub> 4) Launchpad production database running PostgreSQL 8.3
[18:18] <stub> There are no fixed or vague timeframes yet. We want to minimize the time taken to complete steps 2-4, whilst giving staging enough time to show up any issues, to avoid PG version specific code to slip through.
[18:18] <stub> This means I don't think we should start step 2 until we have a version of PG 8.3 we are confortable trusting on production. In the past this has been the first or second point release.
[18:18] <stub> That is all.
[18:19] <Rinchen> stub, do we have a rough date for the future point releases?
[18:19] <stub> Not really - it depends on how quicky bugs get fixed, and if there are any high priority ones that need doing sooner rather than later.
[18:20] <stub> I would expect before hardy though, which is a natural point to make the switch over.
[18:20] <Rinchen> hmm. Well, please do keep us informed. Thanks.
[18:20] <stub> (as it avoids the need to get dapper backports)
[18:20] <Rinchen> [TOPIC] Sysadmin requests (Rinchen)
[18:20] <MootBot> New Topic:  Sysadmin requests (Rinchen)
[18:20] <Rinchen> mthaddon, herb - RT 29897 - caching for bac
[18:21] <mthaddon> thx, noted
[18:21] <Rinchen> it was needed a week ago or so and currently has tomorrow as a new due date. It's blocking my closure of 1.2.2
[18:21] <Rinchen> Thanks.
[18:21] <Rinchen>  Is anyone blocked on an RT or have any that are becoming urgent?
[18:22] <Rinchen> I take that as a good sign :-)
[18:22] <Rinchen> [TOPIC] New packages required (salgado)
[18:22] <MootBot> New Topic:  New packages required (salgado)
[18:22] <salgado> 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
[18:22] <salgado> stub, shall I make new packages depending po pg8.3?
[18:23] <salgado> for hardy, that is
[18:23] <salgado> that way we may be able to get some people testing. :)
[18:23] <stub> salgado: PG 8.3 is available on gutsy too. It might be premature though to load up everyones boxes - opinions?
[18:23] <cprov> salgado: okay, I'd rather add the new python-apt package in lpdebs repo and require the specific version in the lp-dep package
[18:24] <cprov> salgado: it will be only required while we are using gutsy, hardy's version is good to go.
[18:24] <salgado> cprov, can you give some background on this?
[18:24] <salgado> stub, yeah, I also think it's too early to do that
[18:24] <Rinchen> stub, I would not want to have technology risk our milestone goals for the next few cycles. Avoiding any issues there would help us meet our objectives.
[18:24] <cprov> salgado: yes, python-apt version in gutsy has a memory leak in debExtract() method we use in upload-processor
[18:25] <salgado> cprov, okay, let's talk about this later, then. I don't think this should be discussed in the meeting
[18:25] <cprov> salgado: sure
[18:25] <schwuk> we're having problems with python-apt under hardy in the hardware testing client as well
[18:25] <schwuk> in fact we've stopped using it
[18:26] <Rinchen> [ACTION] cprov and salgado to discus python-apt packaging in lpdebs
[18:26] <MootBot> ACTION received:  cprov and salgado to discus python-apt packaging in lpdebs
[18:26] <Rinchen> salgado, done?
[18:26] <salgado> yep
[18:26] <Rinchen> thanks
[18:26] <cprov> schwuk: seriously ? let's chat about it later, okay ?
[18:26] <Rinchen> [TOPIC] A top user-affecting issue (mrevell)
[18:26] <MootBot> New Topic:  A top user-affecting issue (mrevell)
[18:26] <mrevell> Couple of things have cropped up this week.
[18:27] <mrevell> 1. We've had what appears to be an unusually high number of people who, it seems, don't understand that they are subscribed to the launchpad-users list.
[18:27] <schwuk> cprov: cr3 has been doing the work - he's your best bet
[18:27] <mrevell> The launchpad-users sign up page is quite explicit in telling people that it's not for ShipIt requests etc, thanks to Kiko's big warning. Any suggestions for what else we could do to warn people that they're signing up to a mailing list will be gratefully received :)
[18:27] <mrevell> 2. You've probably noticed the thread on launchpad-users about the use of real names in the Launchpad Beta Testers team. This has stirred some passions amongst a small but vocal number of the beta test team. The real names issue will, I believe, come up next week.
[18:27] <mrevell> that's all from me, unless anyone wants to talk about these
[18:27]  * Rinchen has emailed SteveA and Kiko about the real names item.
[18:27] <mpt> Do ShipIt user tests on people who don't have English as their first language
[18:28] <mpt> That would find the problem fairly quickly, I think :-)
[18:28] <mrevell> mpt: Think we could do this in Prague?
[18:28] <mpt> maybe
[18:28] <mrevell> although UDS people are unlikely to be ShipIt users
[18:28] <mpt> Yes, we might need to pull people off the street
[18:28] <intellectronica> mpt: are you certain that these people are coming to the list from shipit?
[18:28] <LarstiQ> mrevell: got a link to more info on the real names issue?
[18:28] <mpt> intellectronica, not certain, one of them this morning didn't know what "Ubuntu" was
[18:29] <mrevell> intellectronica: Some of them we can say certainly are, as they mention. others just seem a little lost and, as mpt says, one person didn't even know what Ubuntu was
[18:29] <mrevell> LarstiQ: I'll dig it out
[18:29] <mpt> LarstiQ, in this month's archive it's all the "RE: [Fwd: hggdh2 deactivated by matthew.revell]" messages
[18:29] <intellectronica> it may be worth following up on a few of the cases. find someone that can talk to them in their language and understand how and why they found themselves on the list
[18:29] <Rinchen> poolie has mentioned that it might be to the beta test item on the front page I added this cycle
[18:30] <mrevell> LarstiQ: https://lists.ubuntu.com/archives/launchpad-users/2008-February/003234.html
[18:30] <Rinchen> however I have some doubts about that because if you can read the instructions on how and why to signup, it should be obvious to follow the unsub instructions in the emails
[18:31] <mrevell> Rinchen: There isn't a link to the mailing list in the help page that links to though. Interesting idea, though.
[18:31] <Rinchen> I wonder if a LoCo has encouraged folks to sign-up
[18:31] <mrevell> I'll certainly mail some of the people to see if we can find out what's going on.
[18:31] <intellectronica> Rinchen: exactly. i find it a bit suspicious. could it be that someone is subscribing them and they just click the link in the confirmation email, for example?
[18:31] <Rinchen> mrevell, if you have time, you might email a few of them asking how they got on the list.
[18:31] <mrevell> Rinchen: Yeah, I'd love to know what's going on.
[18:32] <Rinchen> I can't help relating -users recent activity to a social networking list.  "Go signup and get karma"
[18:32] <Rinchen> anyway, thanks mrevell
[18:32] <mrevell> thanks all
[18:32] <Rinchen> and new for this week...
[18:32] <Rinchen> [TOPIC] Doc Team report (mrevell)
[18:32] <MootBot> New Topic:  Doc Team report (mrevell)
[18:33] <mrevell> Two opportunities to stun you into silence with my whit
[18:33] <mrevell> err. wit
[18:33] <mrevell> Anyway
[18:33] <Rinchen> and charm :-)
[18:33] <mrevell> Hello, welcome to the first doc team report!
[18:33] <mrevell> The Launchpad Documentation Team now has 19 direct members and I'm planning to hold the first team meeting in week 2 of the 1.2.3 cycle. During that, I plan to find out what everyone wants from the team and how we can move forward.
[18:33]  * thumper claps
[18:33]  * mrevell bows
[18:33] <mrevell> Additionally, this week I've been working on the new Launchpad user guide. You can see drafts of the "Your account" section at:
[18:33] <mrevell> https://help.launchpad.net/YourAccount/NewAccount/Draft
[18:33] <mrevell> https://help.launchpad.net/YourAccount/Branding/Draft
[18:33] <mrevell> https://help.launchpad.net/YourAccount/ImportingYourPGPKey/Draft
[18:33] <mrevell> https://help.launchpad.net/YourAccount/CreatingAnSSHKeyPair/Draft
[18:33] <mrevell> https://help.launchpad.net/YourAccount/Karma/Draft
[18:33] <mrevell> https://help.launchpad.net/YourAccount/Merging/Draft
[18:33] <mrevell> I'll be posting a new Teams section for review to the list shortly.
[18:33] <mrevell> As always, I'm very grateful for any feedback. Even from mpt ;-)
[18:34] <Rinchen> ouch
[18:34] <mrevell> Next up on my list are the Projects and Bug Tracker sections of the documentation. I'll also be working on a new draft of the 2008 LP tour and working on an initial summer 2008 marketing plan with Gerry Carr while I'm in London next week.
[18:34] <mrevell> hehe
[18:34] <mrevell> :)
[18:34] <gmb> Damned with faint praise there, mpt.
[18:34] <Rinchen> mpt gets that a lot, you notice?
[18:34] <mrevell> Damn, joke backfired.
[18:34] <mrevell> Ah, I'm safe
[18:34] <mpt_> Another thing that might help with #1 is to remember the Referer: for each person who turns up at the launchpad-users@ subscription page, and goes on to subscribe
[18:34] <mrevell> Right, anyway, so if there are any help or docs issues that you have, please ping or mail me! Or grab me next week.
[18:34] <mpt_> Then if they (even weeks later) post to launchpad-users@ showing that they don't want to be there, we could go back and look to see where they came from
[18:35] <intellectronica> mpt_: we should already have this in our logs
[18:35] <Rinchen> thanks mrevell for the doc report. I'm excited to see how the doc team progresses.
[18:35] <mrevell> mpt_: That would be really cool. barry can we get that info out mailman easily? Or is it at the web server level?
[18:35] <mrevell> Thanks for your ears.
[18:35] <carlos> intellectronica: I don't think is easy to map apache logs with user subscriptions...
[18:36] <flacoste> i suck
[18:36] <gmb> Random...
[18:36] <intellectronica> carlos: no, but we can see how people arrive at the page
[18:36] <flacoste> completely forgot about this meeting
[18:36] <carlos> intellectronica: sure, but that would be a huge list
[18:36] <Rinchen> [IDEA] use referrer on -users to see where the subscriptions are coming from
[18:36] <MootBot> IDEA received:  use referrer on -users to see where the subscriptions are coming from
[18:36] <stub> intellectronica: If that is all you want, then we probably already have it with the apache log reports.
[18:37] <intellectronica> stub: that was exactly what i said :)
[18:37] <stub> awstats or whatever we use atm
[18:37] <mpt_> Possibly it would involve altering the subscription form to contain a hidden input field equal to the Referer
[18:37] <mrevell> Do we have a stats programme running on the mailman web interface?
[18:37] <intellectronica> carlos: i doubt that it would be a long list. there will be a few common sources. webalizer or awstats will even make nice graphics showing which ones
[18:37] <carlos> intellectronica: my point is that you cannot get from where did a user reach the mailing list
[18:38] <carlos> just a list from where all users come
[18:38] <intellectronica> carlos: no, not specific users. to do that we'll have to record the information, you're right
[18:39] <stub> mrevell: Don't know as I can't remember the URL to the stats pages, but it is easy enough for the admins to add if it isn't there already.
[18:39] <mrevell> stub: Cool, I'll ask one of the IS chaps.
[18:39] <Rinchen> mrevell, done?
[18:40] <mrevell> yup, thanks
[18:40] <Rinchen> thanks
[18:40] <Rinchen> [TOPIC] Blockers
[18:40] <MootBot> New Topic:  Blockers
[18:40] <Rinchen> [AGREED] Releases Team: mpt blocked on foundations. Email discussion in progress.
[18:40] <MootBot> AGREED received:  Releases Team: mpt blocked on foundations. Email discussion in progress.
[18:40] <thumper> Code team: not blocked
[18:40] <jtv> Translations: Not blocked.
[18:40] <cprov> Soyuz team: not blocked
[18:41] <flacoste> Foundations: Not blocked
[18:41] <adeuring> hwdb: not blocked
[18:41] <Rinchen> bac?
[18:41] <BjornT> Bugs Team: a bit blocked on getting feedback about requirements from kiko
[18:41] <Rinchen> [AGREED] Bugs Team: a bit blocked on getting feedback about requirements from kiko
[18:41] <MootBot> AGREED received:  Bugs Team: a bit blocked on getting feedback about requirements from kiko
[18:41] <bac> Commercialization team: not blocked
[18:41] <Rinchen> the agreed makes it stand out in the summary
[18:42] <Rinchen> thanks
[18:42] <Rinchen> and thus ends another on-time meeting
[18:42] <mrevell> thanks all!
[18:42] <Rinchen> Thank you all for attending this week's Launchpad Developer Meeting. See the channel topic for the location of the logs.
[18:42] <Rinchen> #endmeeting
[18:42] <MootBot> Meeting finished at 18:42.
[18:42] <carlos> thanks
[18:42] <jtv> Rinchen: thank you
[18:42] <carlos> cheers
[18:42] <intellectronica> thanks, Rinchen for a great meeting
[18:42] <thumper> Rinchen: thanks
[18:42] <schwuk> thank Rinchen
[18:42]  * sinzui notes that one should not use the can spray glue next to the can of air to fix a sticky keyboard.
[18:42] <Rinchen> intellectronica, yeah I only made one goof  :-)
[18:43] <intellectronica> Rinchen: that's not goofing. that's what we call "personal style"
[18:43] <Rinchen> intellectronica, ah I see!
[18:43]  * mwhudson off to make coffee
[18:44]  * gmb off to eat food
[18:44] <danilos> Rinchen: my guess would be that most shipit users are coming from loginservice-email-sent.pt (i.e. after they have created an account, launchpad-users list is mentioned there)
[18:44] <adeuring> </quit leaving
[18:44] <cprov> salgado: let's have a phone call to talk about the python-apt dependency ?
[18:45] <jtv> danilos: we could at least check if those people have accounts...
[18:45] <jtv> if they don't, something really weird is going on.
[18:45] <jtv> like spammers filling out the form hoping it'll send their messages to people.
[18:46] <danilos> jtv: well, they might not be activated yet, because that page specifically advises them to read their email and then activate their accounts
[18:46] <Rinchen> danilos, interesting....
[18:46] <jtv> danilos: but those in-progress accounts would still show up somewhere, right?  It'd give us even more information.
[18:46] <danilos> jtv: yeah, but I don't want to discuss too much details, then somebody will ask me to do it :)
[18:47]  * jtv shuts up
[18:47] <danilos> :)
[18:49] <salgado> cprov, can it be tomorrow?
[18:50] <cprov> salgado: okay, np, I will ping you tomorrow.
[18:51] <salgado> cprov, you might want to subscribe to bug https://bugs.edge.launchpad.net/meta-lp-deps/+bug/193324, btw
[18:51] <ubotu> Launchpad bug 193324 in meta-lp-deps "Require dpkg and lzma dependencies on launchpad-dependencies pacakge" [Undecided,New]
[18:52] <cprov> salgado: right, thanks