[00:01] mhall119: thanks [00:01] cjohnston: merged. get it deployed. [00:03] Filed bug 889337 [00:03] Launchpad bug 889337 in loco-team-portal "Remove all the print statements in application code (affects: 1) (heat: 6)" [Undecided,New] https://launchpad.net/bugs/889337 [00:14] mhall119: nigelb thoughts: https://code.launchpad.net/~chrisjohnston/loco-team-portal/event-recap/+merge/81925 [00:56] svwilliams: ! [00:56] Hey! cjohnston I'm finally on a really computer! (no vm on top of mac osx) [00:56] sweet [00:57] still getting everything setup just got the bzr branch for loco-directory [00:57] cool [00:57] im getting ready to push a release [00:57] we have a bad bug we need to fix [00:58] whats the bug? [00:59] something with switching to wsgi [00:59] ahh [01:00] I'm hoping I can over come the issues I had synching open-ids last night using this old dell from work [01:00] for some reason the vm kept timing out [01:00] gotcha [01:00] are you handling the release on your own [01:00] fwiw its now lp:loco-team-portal [01:00] fwiw (?) [01:00] for what its worth [01:00] i prepare the release, and then notify IS [01:01] I was wondering about that I should switch to that correct [01:01] instead of loco-directory [01:01] loco-directory points to l-t-p [01:01] but l-t-p would now be more appropriate [01:02] svwilliams: any chance your close to being ready to working on a real quick bug that needs to be pushed out [01:02] bug #888511 [01:02] Launchpad bug 888511 in loco-team-portal "Fix links to launchpad project/team (affects: 1) (heat: 6)" [High,Triaged] https://launchpad.net/bugs/888511 [01:02] I'm still getting set up and my old env was hindering working on the three bitsize bugs I have [01:03] but I would look into that one and take that one on instead [01:03] it should only be 3 or 4 lines of code [01:03] really easy [01:03] its just updating the links [01:03] alright I'll go pull up the bug and fix it [01:03] this asap or by end of weekend? [01:03] if you can't do it in the next hour I will [01:04] well I kicked off make live [01:04] i figured it would give you a little more experience [01:04] cancel that out [01:04] ill give you a db for this one [01:04] ok [01:04] http://dl.dropbox.com/u/2494160/loco_directory.db [01:05] this one is super easy... [01:05] in your branch (so the folder that contains loco_directory/) [01:05] grep -rn ".net/loco-directory" * [01:09] so they all need to change to /loco-team-portal [01:10] correct? [01:10] The text already says Loco Team Portal so we're just cleaning up the links [01:10] after that want me to go through the wiki and clean up the intructions for developers [01:10] yr\es [01:10] yes [01:10] I was going to add the stuff I learned yesterday about synching open ids [01:10] k [01:10] sure.. [01:16] cjohnston, I just went through about.html has the link to the developers changed ... I went to launch pad and its still loco-directory-dev [01:18] it has not yet changed svwilliams [01:18] it will [01:18] but it will also have a forward [01:18] so it can wait a bit [01:19] ok [01:19] well its done [01:19] let me run it real quick and run through all of the links [01:19] and make sure they work [01:19] t [01:19] y [01:30] cjohnston, syntax for the commit to link to the bug [01:30] --fixes lp:bugnumber [01:30] ? [01:30] yup [01:36] cjohnston, mp is up [01:36] I'm going to attack the wiki now [01:36] ok [01:36] ty [01:37] your welcome [01:37] you are welcome [01:37] svwilliams: never noticed this, but do you mind fixing: [01:38] the "report it" links, point them to https://bugs.launchpad.net/loco-team-portal/+filebug [01:38] yes I noticed that it was a search I think ... [01:38] so login_failure [01:38] .html [01:38] 404.html [01:38] and 500.html [01:39] add /+filebug to all of the links [01:39] since most of them point to just bugs [01:40] ya [01:43] added it to all of them [01:44] and pushed to same branch [01:44] ty [01:45] np [01:45] did all the links redirect [01:46] I don't want to screw up the release process instructions [01:46] I'm working on the wiki now [01:46] and I'm modifying the directions to point at loco-team-portal instead of loco-directory [01:46] didn't know if everything including translations had moved? [01:46] everything except the team is moved [01:48] there is a directory under the team /loco-directory-dev/loco-directory [01:48] has that been changed to /loco-directory-dev/loco-team-portal? [01:48] lp:~loco-directory-dev/loco-team-portal/translations [01:48] lp:~loco-directory-dev/loco-team-portal/production [01:49] ok so the instructions to sysadmin's will have changed [01:49] got it [01:49] lp:loco-team-portal is the same as lp:loco-directory-dev/loco-team-portal [01:49] whats the link [01:50] instructions bzr pull lp:~loco-directory/loco-directory/production [01:50] https://wiki.ubuntu.com/LoCoDirectory/ReleaseProcess [01:50] had it open so I started there [01:50] lp:~loco-directory-dev/loco-team-portal/production is the new link [01:50] for now [01:53] is the stuff on thier end still /srv/shared-branches/loco-directory-dev_loco-directory_production [01:53] ya, leave that alone [01:56] last thing, I think, would you like me to migrate the wiki pages [01:56] from LoCoDirectory [01:56] to LoCoTeamPortal [01:56] I'm migrating the text [01:56] Ya.. and then point LoCoDirectory to LoCoTeamPortal [01:56] I mean changing the text [01:56] ok [01:57] yes [02:04] ok I've moved everything and fixed most of the references to loco-directory [02:05] little things like loco_directory.db [02:05] I left alone [02:05] but all launchpad references and wiki pages and project references calling it loco directory I fixed [02:05] cool [02:05] ty [02:07] oh there is a bunch of old text about releases [02:07] .1 [02:07] and .2 [02:07] I left their references to loco-directory alone [02:07] k [02:07] if I get a chance I'll update to our current number and [02:08] ok [02:08] put in some items from the UDS blueprint [02:08] this weekend [02:08] :-) [02:08] watch out.. you might become the project lead [02:14] ha :-) I'll leave that in more competent hands, but I'm happy to help :-) [02:15] like was said during uds.. if you go to the bathroom, you may end up in charge [02:15] lol, good advice for next UDS [02:15] don't go to the bathroom [02:15] I think I over heard hallway conversations where people were getting volunteered for things [02:15] :-D [02:16] lol [02:46] svwilliams: im including you on the email requesting a release just so you can watch it [03:01] excellent [03:07] mhall119: http://paste.ubuntu.com/735870/ do you have any idea who any of the people are that are throwing the errors? (ie their proper lp name) [03:08] svwilliams: you said your familiar with python right? [03:08] just new to django [03:08] familar with web dev [03:08] new to django and python [03:08] ok [03:08] well I've done a little python [03:08] very little [03:08] ok. [03:08] I get the basics [04:25] cjohnston: You should change your review status to Approved too. [04:25] https://code.launchpad.net/~doctormo/loco-team-portal/event-page-design/+merge/81231 === Ronnie1 is now known as Ronnie [14:12] cjohnston: all I recognize is achuni [14:12] his lp username is elachuni [14:14] I can also recognize cdbs [14:14] and coolbhavi [14:14] could yall fix the ones you know please [14:16] cjohnston: EW. [14:17] Status can't handle case difference? [14:17] dont know.. i guess now? [14:17] not/ [14:18] Yeah [14:18] ok, I fixed the ones I know. [14:18] ty [15:49] nigelb: mhall119 et al: https://code.launchpad.net/~chrisjohnston/loco-team-portal/req/+merge/82049 [15:50] https://code.launchpad.net/~chrisjohnston/summit/track-summary/+merge/81912 [15:50] on a saturday? [15:51] mhall119: on a every day [15:55] cjohnston: I'm not sure your requirements change for django-openid-auth will work [15:56] it works on summit [15:56] why wouldnt it here [15:56] eveytime I've seen a downloaded tarball, the line started with -f, and ended with some package info [15:57] mhall119: it works on summit [15:57] mhall119: try it? [15:58] if you tried it, then it's ok [15:59] getting psycopg2 out of there is going to make things easier for new devs [16:00] its still there.. its commented out [16:01] it'll make settingup the virtualenv faster [16:16] mhall119: get ready to go outside and wave [16:16] cjohnston: driving past? [16:16] ya [16:17] where are you headed? [16:17] fl aquarium [16:17] the one in ybor? [16:17] si [16:17] hope says 'channelside' [16:17] ah, too bad Michelle is sick, or we'd come out with you [16:18] :-( [16:18] she's had Ubuflu all week [16:18] I'm the only one here who hasn't had it [16:18] :-( [16:18] i didnt get it this time [16:21] mhall119: is there anything requreid other than the translation for the translation to show up in the list of translations [16:22] cjohnston: you mean on LTP? [16:22] I think we just get languages from the iso-codes package [16:23] yes, ltp.. [16:24] so if the language isnt in the menu, how do we add it [16:44] what language are we missing? [16:44] https://answers.launchpad.net/loco-team-portal/+question/178481 [16:45] I pushed the translations to production.. so when IS releases it, the .po's will be there [17:10] cjohnston: if we can't get django 1.3 installed system-wide, we can get a local branch of it and put it on the PYTHONPATH [17:10] Is IS okay wwith that? [17:10] nigelb: they should be, that's SOP for ISD apps now [17:11] there's even an official ISD branch of django 1.3 we can use [17:11] we'll just need to update the .wsgi files to add it to the path [17:11] oooh. Then I'm all for that. [17:11] mhall119: we are trying to move servers too [17:11] Why move servers? [17:11] more power! [17:11] becuase cranberry is still in trouble [17:14] Since when? [17:14] we haven't had any issues in a long while. [17:15] nigelb: its still overrun per is.. they want to move us [18:14] cjohnston: do you know about status.ubuntu.com? [18:17] cprofitt: He does. He maintains it. Is it broken? [18:18] no, just curious why my page is missing... [18:18] I clicked on my name and get page not found [18:22] cprofitt, only people who are members of the teams on the teams page have pages [18:22] ok... [18:23] and what determines what blueprints are included? [18:23] for example -- https://blueprints.launchpad.net/ubuntu/+spec/community-p-bug-involvement [18:25] cproffit, managers [18:26] * cprofitt nods [18:27] the site looks fantastic... would be really useful if I had a page and it was tracking all the blueprints [18:27] thanks for the explanation cjohnston [18:31] cprofitt, find me a python dev to optimize it and we can.. right now it isnt practical [18:33] hello [18:34] hey daker [18:35] cjohnston: I thought you were out ;) [18:35] %I am [18:37] cjohnston: nigelb do we have a twitter account ? [18:52] https://code.launchpad.net/~daker/loco-team-portal/fix.889567/+merge/82053 [23:29] mhall119: nigelb Ronnie http://paste.ubuntu.com/736761/ the error for /meetings/history [23:29] cjohnston: is that the full error? [23:30] is that displaying past meetings? [23:30] yews [23:30] http://paste.ubuntu.com/736764/ [23:30] The error is that there is a print statement. [23:31] ok.. so nigelb your code fixes that right [23:31] ya [23:31] ah, the famous print statements with wsgi [23:32] before commit i usually exec "bzr diff | grep print" [23:48] django 1.4 will have the new command which will significantly reduce the amount of queries: https://docs.djangoproject.com/en/dev/ref/models/querysets/#prefetch-related [23:52] wow, the event history list runs 5432 queries to print the page. thats the same number as the port of a standard postgresql database.