[14:44] <czajkowski> mhall119: ping :)
[14:44] <mhall119> pong
[14:45] <thecolonyroom> czajkowski: Hullo.
[14:45] <czajkowski> thecolonyroom: ahh didnt recognise the nick
[14:45] <steveedwards> czajkowski: Hullo.
[14:45] <czajkowski> ta da
[14:45] <steveedwards> czajkowski: Sorry. My alter ego.
[14:45] <mhall119> cjohnston, meet steveedwards
[14:45] <cjohnston> o/
[14:45] <czajkowski> so basiccally just trying to work out why we have 2 projects with the same name and wondering can they not be under one project
[14:45] <steveedwards> cjohnston: Don't hate me.
[14:45] <czajkowski> or is there something I'm missing here
[14:46] <cjohnston> theres alot that we are missing
[14:46] <cjohnston> but i agree
[14:46] <mhall119> so cjohnston has already given maintainership of uds-project to ~uds-organizers, and I've already pushed steveedwards's code there
[14:46] <cjohnston> i dont care which it is, just pick one and point the other to it if possible
[14:47] <mhall119> we also already have bugs files against uds-project, though they're probably not relevant after the theme change
[14:47] <cjohnston> mhall119: ive gone through them
[14:47] <cjohnston> 2.5 still are
[14:47] <mhall119> ok
[14:47] <czajkowski> at prsent steveedwards project that was registed is inactive so just wondering can he use the project that currenly cjohnston ownes for the summit work
[14:48] <mhall119> sorry, but just to clarify, this is for uds.u.c work, not summit.u.c work
[14:48] <cjohnston> steveedwards: if possible, whatever we choose, can we put a link in the footer as to where to file a bug for the site so that people dont file against ubuntu-website
[14:48] <cjohnston> summit work need to go under the summit project
[14:48] <steveedwards> cjohnston: Will do. I can add that.
[14:48] <mhall119> summit *code* work anyway, we still have some content on there that is UDS-specific (but we're working on removing that)
[14:49] <cjohnston> theme work needs to go against https://launchpad.net/ubuntu-community-webthemes
[14:49] <mhall119> cjohnston: not for uds.u.c
[14:49] <cjohnston> for summit
[14:49] <mhall119> the django one, yes
[14:50] <cjohnston> if everything wasnt hard coded into uds.u.c branch, the branch could be pushed there and all sites could be updated to the new guidelines
[14:50] <cjohnston> but oh well
[14:51] <mhall119> so is everybody okay with using uds-project?
[14:51] <cjohnston> +0 just pick one
[14:51] <mhall119> I'm +1, simply because it's all there already
[14:51] <steveedwards> mhall119: Sounds good.
[14:52] <mhall119> steveedwards: we can add you to ~uds-organizers if you think we need to, so you can push to the branch on that project
[14:52] <steveedwards> mhall119: That would be great. Thanks.
[14:52] <mhall119> otherwise you can just push under your name and make a merge proposal to that branch
[14:54] <czajkowski> great we're sorted so
[14:54] <czajkowski> https://launchpad.net/uds-project  is the one to live right ?
[14:54] <mhall119> right
[14:54] <cjohnston> yes
[14:56] <mhall119> thanks czajkowski, steveedwards, cjohnston
[14:56] <czajkowski> lovely jubbly
[14:56] <czajkowski> sorted so
[14:56]  * czajkowski goes back to reviewing more projects 
[14:56] <czajkowski> toodles
[14:56] <steveedwards> mhall119: Cheers.
[14:57] <cjohnston> steveedwards so what are the thoughts from the design team on making the user experience a decent one going between uds.u.c and summit.u.c
[14:57] <cjohnston> it was ok at best in prior to the update
[15:02] <niceguyjames> cjohnston: the issue with the previous uds.u.com and summit.u.com was primarily that the sites tried to mirror each other to make it less obvious you were jumping between different websites, but because they were out of sync that didn't really work.
[15:02] <cjohnston> right..
[15:02] <niceguyjames> cjohnston: so during the UX, the top-level navigation links to summit were reimagined as call-to-actions to go off-site.
[15:03] <niceguyjames> cjohnston: hence them being removed from the top-level navigation which should be reserved for navigation in the current site.
[15:03] <cjohnston> it doesnt make sense to me that there is only 1 link that i find to the schedule
[15:04] <niceguyjames> cjohnston: equally it doesn't make sense that an empty page is promoted before it's populated
[15:04] <cjohnston> I've been against having two seperate sites from day one.. the work should be done to make it one site IMO
[15:04] <niceguyjames> cjohnston: so it may be that it gets dropped into the nav when it does?
[15:04] <niceguyjames> cjohnston: +1
[15:04] <steveedwards> cjohnston: We'd love to help with that.
[15:04] <steveedwards> cjohnston: If we can find the time.
[15:04] <cjohnston> bzr branch lp:summit
[15:04] <cjohnston> ;-)
[15:04] <niceguyjames> cjohnston: the above is just so you know where the UX decision came from.
[15:04] <steveedwards> cjohnston: :)
[15:04] <cjohnston> ty niceguyjames
[15:05] <cjohnston> hardcoding would have been just as easy with both
[15:05] <cjohnston> If we are going to hardcode, I could easily add it all to summit, then just point uds.u.c to summit
[15:06] <cjohnston> ill be back in 5 minutes
[15:15] <cjohnston> im back
[15:25] <cjohnston> svwilliams: ping
[15:26] <svwilliams> Hey cjohnston
[15:26] <cjohnston> have you had a change to work on your branches anymore?
[15:28] <svwilliams> I worked on them more sunday, but not yesterday
[15:28] <cjohnston> ok
[15:28] <svwilliams> I'll have time tonight to straighten out the position: relative issue
[15:29] <cjohnston> cool.. ty
[15:29] <svwilliams> thats the only thing left, removing the % and specifying the px fixed the ltp issue
[15:29] <svwilliams> :-)
[15:30] <cjohnston> sweet
[15:30] <cjohnston> do you know what the problem is with the position relative issue?
[15:30] <cjohnston> or do you need to mess around with it
[15:42] <svwilliams> I need to mess around with it
[15:42] <svwilliams> cjohnston, (sorry for the delays in responses)
[15:42] <cjohnston> np
[15:43] <svwilliams> I think I can put them inside a block that is position relative, but it seems like if they themselves are position relative it ignores that when resizing the page
[15:43] <svwilliams> due to the display:inline-block
[15:43] <svwilliams> though now that I'm typing it
[15:44] <svwilliams> I'm wondering if my margins are throwing it off
[15:44] <svwilliams> I have plenty of time to play with it tonight
[15:44] <svwilliams> I'll let you know
[15:44] <cjohnston> ok
[16:41] <cjohnston> svwilliams: this is really odd.. I'm seeing doubles and dont know why.. I've stared adding links in your side bar.. but i have two side bars
[16:42] <cjohnston> and the side-bar needs to wrap text
[16:45] <cjohnston> svwilliams: mhall119 http://ubuntuone.com/5sgMhDL72yeJDnjBXaPVXv
[16:46] <mhall119> Could not locate object
[16:48] <cjohnston> mhall119: svwilliams http://ubuntuone.com/6sEitrdTgdTwyTYXlSHTWz
[18:05] <daker> mhall119, can you help with a small question ?
[18:05] <mhall119> daker: sure
[18:06] <daker> mhall119, i want to select all the events that are in still happening
[18:07] <mhall119> daker: from within Django, or from the JSON API?
[18:07] <daker> django
[18:07] <daker> ORM
[18:07] <daker> FYI: each events has a start/end date
[18:07] <daker> event*
[18:09] <daker> imagine you have two events happening today and i need to get them just by passing the date
[18:10] <daker> mhall119, ^
[18:12] <mhall119> daker: we have that in the object managers already I think
[18:14] <daker> mhall119, no i think you didn't understand
[18:14] <daker> imagine you have event 1 from 10-03-2012 to 13-03-2012
[18:15] <daker> and event 2 from 12-03-2012 to 13-03-2012
[18:15] <daker> and i want just by passing the 12-03-2012 to the query to get the list of the two events
[18:17] <svwilliams> cjohnston, that's odd ... it looks like the block that you are building links into exists in more than one place ... did I leave a trailing one in from all of our testing
[18:17] <svwilliams> last friday
[18:20] <mhall119> daker: ah, I think I understand
[18:21] <mhall119> daker: something like TeamEvent.objects.filter(date_end__gte=your_date_variable)
[18:21] <mhall119> that will give you any date that *end* after the given variable date
[18:22] <mhall119> daker: look at next_events in TeamEventsManager
[18:22] <mhall119> /events/models.py line 105
[18:24] <daker> ok
[18:25] <cjohnston> svwilliams: i dont think so
[18:35] <cprofitt> hey cjohnston
[18:35] <cjohnston> hey
[18:36] <cprofitt> bobweaver is his irc nick
[18:36] <cjohnston> ok
[18:37] <cprofitt> he is not on now.
[18:37] <cjohnston> ok
[18:37] <cprofitt> but if you see him... you know who he is
[18:38] <cjohnston> ok.. cool
[18:38] <cjohnston> ty
[18:39] <cprofitt> I will likely have to work on bzr with him...
[18:39] <cjohnston> ok
[18:40] <cjohnston> thats easy enough
[18:40] <cjohnston> groundcontrol may be something to look at too
[18:40] <cprofitt> yeah... that is
[18:41] <cprofitt> I will try to ensure that he gets in contact with you.
[18:41] <cjohnston> awesome.. ty
[18:44] <cprofitt> mhall119: I just saw cjohnston in the other channel and mentioned it to him
[18:44] <cprofitt> but yes, we need to get bob in here
[21:59] <cjohnston> daker: https://code.launchpad.net/~chrisjohnston/loco-team-portal/bzr-req-update