[06:33] <YoBoY> good morning
[06:37] <nigelb> lies! I'm going back to bed
[06:38] <nigelb> Good morning YoBoY :)
[06:39] <YoBoY> great idea, the bed was so good and I'm so tired ^^"
[06:39] <YoBoY> ok, now I have more time :D
[06:40] <YoBoY> what the hell is this jono's blog proposition for the ltp ? ^^"
[06:41] <YoBoY> is really near one of my team site : http://ubuntu-party.org/ :p
[06:42] <YoBoY> and I don't rally understand the posts, are we syndicating team blogs ? with all the langages ?
[06:42] <YoBoY> really
[07:42] <nigelb> YoBoY: yup, its going to look like that mostly :)
[07:42] <nigelb> we're not going to sync all blog pots
[07:42] <nigelb> *posts
[07:43] <nigelb> we're just going to start with a few people posting to the LTP about what they did in their loco team
[07:46] <YoBoY> hum... why people and not locos ? if it's people, the posts are already on the planet.u.c no ?
[07:49] <nigelb> YoBoY: No, that's where the problem is
[07:49] <nigelb> Not every rockstar loco team member may have access to planet
[07:49] <nigelb> because they might not be ubuntu members
[07:49] <nigelb> besides, planet does have other noise
[07:49] <nigelb> we want to showcase loco active on the LTP
[07:50] <YoBoY> hum... and none of the locoteam blogs also ;)
[12:07] <daker> mhall119, help!!!
[12:08] <daker> i have added a color field to the track, and i am getting
[12:08] <daker> "NoReverseMatch: Reverse for 'summit.schedule.decorators.inner' with arguments '('',)' and keyword arguments '{}' not found."
[12:58] <nigelb> oops
[12:58] <nigelb> I was workig on that
[13:00] <daker> o.O workin on the color track ?
[13:00] <daker> working*
[13:00] <daker> nigelb, ^
[13:00] <nigelb> daker: yeah, moving the color to a db field
[13:03] <daker> ok
[13:06] <nigelb> blah, we need to talk to each other more often
[13:06] <nigelb> my fault too, I didn't update the blueprint when I took the task
[13:22] <nigelb> daker: anyway, sounds like you might be ahead of me.  Carry on with it.  I'll pick up something else.
[13:23] <nigelb> daker: open a bug and assign it yourself when you start something so that we know you're working on.  If you can assign your name to task in the BP, that'd be awesome too.
[13:28] <mhall119> daker: pong
[13:30] <daker> yo
[13:31] <daker> brb
[13:33] <nigelb> mhall119: ping
[13:38] <nigelb> mhall119: never mind, I'll figure it out :)
[13:56] <mhall119> nigelb: :)
[14:28] <daker> mhall119, can you figure out the problem ?
[14:29] <mhall119> daker: did you make a change to urls.py?
[14:30] <daker> no
[14:31] <daker> i have just added a color field to the track
[14:31] <mhall119> hmmm...
[14:31] <mhall119> any changes to templates?
[14:32] <daker> no
[14:32] <daker> http://pastebin.com/PDQPGy2W
[14:33] <daker> when i want to add a summit from here http://127.0.0.1:8800/admin/schedule/summit/add/ i got that error
[14:33] <mhall119> daker: hmm, I'll have to dig more