[01:31] <cjohnston> svwilliams: https://lists.ubuntu.com/mailman/listinfo/community-web-projects
[20:11] <cjohnston> mhall119: email
[20:58] <cjohnston> mhall119: nigelb why would a db field be clearing out every 24 hours? its a char field
[20:59] <mhall119> cjohnston: in summit?
[20:59] <cjohnston> ltp
[20:59] <cjohnston> our override name
[20:59] <mhall119> btw, the local_settings in the email looks okay to me, do we know what linaro is using?
[20:59] <nigelb> what db field?
[20:59] <mhall119> cjohnston: is the lpupdate process resetting it?
[20:59] <cjohnston> no i dont
[21:00] <nigelb> mhall119: hey, did you see the upgrade thing for django 1.3 for authentication modules?
[21:00] <cjohnston> mhall119: the override name should only be set manually.. lpupdate shouldnt be touching it
[21:00] <nigelb> (openid_auth in particular)
[21:00] <cjohnston>     override_name = models.CharField(_("Override Imported Team Name"), max_length=80, null=True, blank=True)
[21:01] <nigelb> Oh, this is LTP.
[21:01] <cjohnston> ya
[21:01]  * nigelb gets back to what he was doign.
[21:01] <nigelb> :P
[21:01] <cjohnston> nigelb: do some summit work ;-)
[21:01] <nigelb> cjohnston: ya, 'm looking at the upgrade
[21:02] <nigelb> mhall119: do you have some time to help me?
[21:02] <cjohnston> cool
[21:02] <nigelb> after the upgrade all our tests break. WIIN.
[21:02] <cjohnston> nice
[21:04] <nigelb> mhall119: http://paste.ubuntu.com/730405/
[21:04] <nigelb> It still works, but you guys should probably know.
[21:05] <mhall119> james_w: happy birthday!
[21:05] <nigelb> oooh
[21:05] <cjohnston> happy birthday james_w !
[21:06] <nigelb>  _   _    _    ____  ______   __  ____ ___ ____ _____ _   _ ____    _ __   __
[21:06] <nigelb> | | | |  / \  |  _ \|  _ \ \ / / | __ )_ _|  _ \_   _| | | |  _ \  / \\ \ / /
[21:06] <nigelb> | |_| | / _ \ | |_) | |_) \ V /  |  _ \| || |_) || | | |_| | | | |/ _ \\ V /
[21:06] <nigelb> |  _  |/ ___ \|  __/|  __/ | |   | |_) | ||  _ < | | |  _  | |_| / ___ \| |
[21:06] <nigelb> |_| |_/_/   \_\_|   |_|    |_|   |____/___|_| \_\|_| |_| |_|____/_/   \_\_|
[21:06] <cjohnston> troll!
[21:06] <nigelb>  
[21:06] <nigelb> :D
[21:06] <nigelb> haha
[21:07] <cjohnston> mhall119: twice last week I WATCHED hauts add the override name of Ubuntu France to his team.. and twice I checked and it was back to ubuntu-fr
[21:07] <cjohnston> I just changed it in the admin area...
[21:07] <nigelb> mhall119: Thoughts on this error I see when running tests? http://paste.ubuntu.com/730414/
[21:08] <cjohnston> http://paste.ubuntu.com/730415/  why does it add the field and then delete the field
[21:13] <mhall119> nigelb: eating lunch,  I'll check it in a few
[21:13] <nigelb> mhall119: cool, thanks. I'm digging as well.
[21:14] <mhall119> cjohnston: it's gotta be something in the lpupdate then
[21:16] <mhall119> nigelb: I recall encountering that wsgi.input error in ISD, I think we just added it into the env dict as an empty string or something
[21:22] <mhall119> nigelb: on line 79 of schedule/tests.py, add wsgi.input as an empty string
[21:22] <mhall119> should allow the tests to proceed
[21:22] <mhall119> nigelb: http://paste.ubuntu.com/730425/ is what is in our test that had the same problem
[21:23] <cjohnston> mhall119: power went out for nigelb.. he says he will look in the morning
[21:23] <mhall119> ok
[21:23] <cjohnston> mhall119: could you take a look at mine as well please?
[21:24] <mhall119> sure
[21:24] <mhall119> cjohnston: it's a migration file, it has a forward() and backward() function
[21:24] <mhall119> forward() adds the field
[21:25] <mhall119> backward() removed it (for rollbacks, etc)
[21:33] <mhall119> I don't see anything in the code that might be re-setting it
[21:33] <mhall119> did you verify that it was being saved?
[21:37] <nigelb> back!
[21:37] <nigelb> yay power
[21:39] <nigelb> mhall119: \o/ down to 2 errors
[21:39] <nigelb> Both something to do with SSL handshake.
[21:39] <mhall119> nigelb: was lack of power one of the errors?
[21:39] <nigelb> heh
[21:39] <mhall119> nigelb: bah, I had that before too, something failing trying to connect to Launchpad
[21:40] <mhall119> nigelb: is this running lpupdate, or running tests?
[21:40] <nigelb> mhall119: just tests
[21:40] <nigelb> http://paste.ubuntu.com/730435/
[21:40] <mhall119> that probably means we should be mocking something outthen
[21:40] <nigelb> Yeah
[21:40] <nigelb> I'm thinking oof creating a launchpad app
[21:41] <mhall119> nigelb: might be a useful separation
[21:41] <nigelb> I'll do a quick test and propose the move to 1.3
[21:41] <nigelb> and then work on that
[21:41] <mhall119> and yeah, that was a quick test I added for a fix for jcastro during sponsorship applications, it should be mocked out properly
[21:42] <nigelb> Shall I ignore this for now and instead fix it after the move?
[21:42] <mhall119> yeah
[21:42] <nigelb> cool
[21:42] <mhall119> for now, if "manage.py test schedule" all pass, I'm happy
[21:42] <nigelb> I'm so glad we have tests :)
[21:42] <nigelb> This migration would have been painful otherwise :)
[21:42] <mhall119> yeah
[21:43] <mhall119> it may still be painful, we didn't have 100% test coverage
[21:43] <nigelb> ./manage.py test schedule works perfectly.
[21:43] <mhall119> any code we didn't touch in the past 6 months doesn't have tests
[21:43] <mhall119> ok, tests on the sponsor app can be fixed later then
[21:43] <mhall119> file a bug for the failing test and you can assign it to me
[21:44] <nigelb> cool, ok
[21:44] <nigelb> I'll file a bug for the launchpad separation as well.
[21:44] <mhall119> ok
[21:44] <nigelb> cjohnston: Get people to stop playing with that stupid bug.
[21:44] <mhall119> well, we were going to make a common app, would it make more sense to just put the launchpad code in there rather than it's own app?
[21:45] <nigelb> launchpad on its own will let us do things like run against staging or local dev
[21:45] <nigelb> we could use a django setting for production, staging, qastaging, and dev.
[21:45] <mhall119> we can't do that now with a local_settings.py variable?
[21:45] <nigelb> Not easily.
[21:45] <mhall119> ok
[21:45] <nigelb> We also use launchpadlib in certain places
[21:46] <mhall119> yeah, but I don't think that alone needs a separate app
[21:46] <mhall119> LTP has ./common/launchpad.py
[21:46] <nigelb> Oh.
[21:46] <nigelb> That might work :)
[21:47] <mhall119> cjohnston: nigelb: so which of you is going to be project manager this cycle?
[21:47] <nigelb> I can do it. Hopefully more effectively than last cycle.
[21:47] <mhall119> or should I flip a coin? loser gets the job?
[21:48] <nigelb> haha
[21:48] <mhall119> as long as it isn't me, I'll be happy
[21:48] <nigelb> heh
[21:51] <nigelb> mhall119: So, I've been thinking about this render.py clean up more.
[21:51] <nigelb> I wonder, should we render the plenary like we do currently?
[21:52] <nigelb> Can the plenary room be one room?
[21:52] <nigelb> and used like any other room
[21:53] <mhall119> nigelb: it's rendered the way it is so that nothing get's scheduled in any other rooms during the plenary time slot
[21:53] <nigelb> Ahh.
[21:53] <nigelb> fuuuu.
[21:53] <mhall119> besides, we're going to get a new UI for desktop users
[21:53] <nigelb> I realized now that we have to handle that as well.
[21:53] <nigelb> when is this UI going to be ready?
[21:53] <mhall119> so render.py can be relegated to just doing the screens at UDS
[21:53] <mhall119> nigelb: I have no idea
[21:54] <nigelb> Ideally, I want render.py out.
[21:54] <nigelb> We should be rendering everything using the same code.
[21:54] <mhall119> yes, I agree
[21:54] <nigelb> Also, have you used django's sites module?
[21:54] <mhall119> but it'll be easier to replace the functionality in separate, clean code, rather than trying to fix the mess that is render.py
[21:55] <nigelb> Maybe that's our solution to the linaro hard-coding.
[21:55] <mhall119> nigelb: only for testing
[21:55] <nigelb> Okay, so I tend to agree with you there.
[21:55] <mhall119> nigelb: sites framework would work, yes
[21:55] <nigelb> Maybe I'll work on a new class called display.py with new code.
[21:56] <nigelb> So they can coexist while I code.
[21:58] <mhall119> that sounds good to me
[21:59] <mhall119> I'd like to see a clean separation between the data model that calculates the schedule, and the code that produces the view of it
[21:59] <nigelb> I think I'll do it like you suggested.
[22:00] <nigelb> Get everything loaded into a class
[22:00] <nigelb> and then do the looping and stuff in the template
[22:00] <nigelb> possibly using helpers
[22:05] <nigelb> mhall119: I've made summit incompatible with Django 1.1
[22:05] <nigelb> Well, there was no other way :)
[22:06] <cjohnston> mhall119: re: verify if its being saved, we went to /teams and it showed up with the override name
[22:09] <cjohnston> nigelb: for mobile we want the screen to look like guidebook
[22:09] <nigelb> cjohnston: dream on.
[22:09] <cjohnston> mhall119: i dont think we really decided too much on a desktop view did we?
[22:09] <cjohnston> dream on for the mobile view?
[22:10] <nigelb> dream on for making it look like guidebook.
[22:10] <cjohnston> why
[22:11] <mhall119> nigelb: johnoxton is going to develop the mobile UI for us
[22:11] <mhall119> using HTML/CSS
[22:11] <mhall119> weren't you on skype for that session?
[22:11] <nigelb> Yeah
[22:11] <nigelb> I think its a better idea to *not* make it look like guidebook.
[22:12] <mhall119> oh, ok
[22:12] <cjohnston> not color and all, but similar layout
[22:12] <cjohnston> http://guidebookapp.com/static/corp/img/screenshots/phoneshot-schedule-3.png
[22:12] <mhall119> I think it's just going to be a fall-back option, I think we'll still use guidebook next UDS anyway
[22:12] <nigelb> That's easy.
[22:12] <nigelb> I can do that
[22:12] <cjohnston> thats what we want
[22:12] <nigelb> We don't eeven need to muck up with render.py for that.
[22:13] <mhall119> we're not going to muck up with render.py at all
[22:13] <nigelb> cjohnston: can you send me more screenshots from your phone?
[22:13] <mhall119> treat render.py as read-only and just write new code
[22:13] <nigelb> +1
[22:13] <cjohnston> mhall119: i think if we get mobile summit looking better than guidebook, we dont need guidebook... i wonder if we could talk them into giving us 15 minutes after the keynote for a "new summit how-to"
[22:13] <cjohnston> nigelb: itll be a few days
[22:13] <cjohnston> http://guidebookapp.com/features/
[22:13] <nigelb> cjohnston: sure
[22:14] <mhall119> then when we don't need render.py anymore  we'll throw a party with cake and fireworks and play rock-paper-scissors for who gets the honor of running "bzr remove render.py"
[22:14] <nigelb> cjohnston: We could a youtube video instead
[22:14] <cjohnston> send out the video the week before or something?
[22:14] <mhall119> +1 for a video, we could link to it on summit.u.c too
[22:15] <nigelb> cjohnston: Yeah, we could announce it on uds-announce as soon as its up.
[22:15] <mhall119> cjohnston: the benefit of guidebook is that it runs offline with a copy of the schedule, much less network usage
[22:15] <cjohnston> mhall119: but everyone cries about it all week
[22:15] <mhall119> and I don't think Canonical paid more than a couple hundred dollars for it
[22:15] <cjohnston> ya
[22:15] <cjohnston> i dont like this city search bug
[22:16] <mhall119> for LTP?
[22:16] <cjohnston> ya
[22:16] <cjohnston> where are the cities supposed to come from
[22:16] <mhall119> I don't know how we'd go about implementing it without going to an outside source
[22:16] <cjohnston> or make the admins list big cities or something
[22:16] <cjohnston> but that sounds like a ton of work
[22:16] <mhall119> yeah, I'm going to -1 that one
[22:16] <cjohnston> im ok with that
[22:17] <mhall119> simplest solution, add a TextField called "keywords" or "search terms" for the admin to fill out
[22:17] <cjohnston> ya
[22:17] <nigelb> Is that the one where we show venues but no teams?
[22:17] <cjohnston> ya
[22:17] <cjohnston> and venues arent linked to teams
[22:17] <cjohnston> mhall119: bug 886938
[22:17] <mhall119> I thought the problem was they wanted to enter a city name in the search field, and get the state-wide team in the results
[22:18] <mhall119> nothing to do with venues
[22:18] <cjohnston> mhall119: bug #886938
[22:18] <cjohnston> thats what they want
[22:18] <cjohnston> but they get venues
[22:18] <mhall119> oh, ok
[22:18] <cjohnston> mhall119: http://loco.ubuntu.com/teams/ ctrl f "france"
[22:18] <cjohnston> then tomorrow do the same
[22:18] <cjohnston> where is the stupid bug bot
[22:18] <nigelb> I don't know what cjohnston has against the French Team :P
[22:19] <nigelb> Maybe we'll never know.
[22:19]  * cjohnston slapps nigelb 
[22:19] <nigelb> Bad vacation there or something? :P
[22:19] <cjohnston> nigelb: if you look right now, its using the override name.. tomorrow, it wont be
[22:19] <cjohnston> hauts went ahead and applied the override name before the blog post and all
[22:20] <mhall119> cjohnston: is there any chance that this is just another admin unsetting it?
[22:21] <cjohnston> mhall119: its only a LC field
[22:21] <cjohnston> or atleast is supposed to be only an LC field
[22:21] <mhall119> oh yeah, you're right
[22:22]  * cjohnston wants ask a favor and see if we can get loco-directory renamed to loco-team-portal on LP
[22:22] <cjohnston> https://blueprints.launchpad.net/loco-directory/+spec/locale-team-support  mhall119
[22:22] <mhall119> I'm not sure what that would require
[22:22] <cjohnston> i dont know.. but i figure id ask a favor to a few of our friends in private to see if we could work it out
[22:22] <cjohnston> would you be against renaming it?
[22:23] <mhall119> no
[22:23] <cjohnston> i dont know that i want to do it if we have to create a new project
[22:23] <mhall119> I don't think it's a big deal though, since the project name in LP doesn't matter to users
[22:23] <cjohnston> i know..
[22:27] <nigelb> mhall119: https://code.launchpad.net/~nigelbabu/summit/django-upgrade/+merge/81422
[22:28] <nigelb> cjohnston: https://code.launchpad.net/~nigelbabu/summit/crew-fix/+merge/81153
[22:28] <nigelb> There, work for both of you.
[22:28] <cjohnston> did yall see that i renamed summit in lp
[22:28] <nigelb> Yeah
[22:34]  * cjohnston is off.. company.. have a good night
[22:34] <nigelb> cjohnston: REVIEW THAT CODE!
[23:47]  * mhall119 dinner, no code review