[05:15] <nigelb> AlanBell: Your kind of game http://type.method.ac
[08:25] <czajkowski> aloha
[19:49] <mhall119> jcastro: give me a ping when you're around
[19:49] <jcastro> yo
[19:50] <cjohnston> that was too long
[19:51] <cjohnston> to respond
[19:54] <jussi> ahh, back to KDE <3
[19:55] <mhall119> jcastro: sorry, my irc is slow
[20:02] <jcastro> mhall119: what did you need?
[20:06] <mhall119> jcastro: was wondering if you saw my post about Summit development
[20:06] <jcastro> no, where at?
[20:09] <mhall119> jcastro: give me one second, I'm having to ressurect apache
[20:09] <mhall119> yahoo's bot kills my t1.micro
[20:10] <jcastro> heh
[20:10] <jcastro> micros are so worthless
[20:12] <mhall119> yeah, but they're cheap
[20:12] <mhall119> and a convenient place to run irssi
[20:12] <mhall119> jcastro: http://mhall119.com/2011/10/uds-p-summit-development-cycle/
[20:13] <jcastro> oh nice!
[20:13] <jcastro> so hey, do you think we'll have the double page thing done?
[20:14] <jcastro> the &page=1 and all that?
[20:16] <mhall119> jcastro: i think AlanBell was starting on that, if not i can knock it out tomorrow
[20:16] <jcastro> okey
[20:17] <AlanBell> linaro has a hacked together "just rooms with linaro sessions in" view
[20:17] <jcastro> ah
[20:17] <jcastro> do you think we could get the inverse?
[20:17] <jcastro> I think even without the linaro rooms we don't fit on one panel anyway right?
[20:17] <AlanBell> well, I think it is an ugly hack
[20:18] <AlanBell> should be based on tracks
[20:18] <AlanBell> or possibly arbitary sets of rooms
[20:26] <cjohnston> the problem is that linaro keeps hacking in linaro stuff... which sucks.
[20:36] <AlanBell> hacking in multiple conference support is a good thing
[20:37] <AlanBell> hacking in stuff that depends on a conference with 'linaro' in the track and session slugs isn't so great
[20:39] <mhall119> AlanBell: next cycle perhaps
[20:39] <mhall119> too late now
[20:39] <AlanBell> sure
[20:39] <mhall119> AlanBell: will you be at UDS?
[20:39] <AlanBell> not this one
[20:39] <mhall119> too bad
[20:40] <cjohnston> AlanBell: i agree
[20:41] <cjohnston> we need to seperate UDS and LDS in summit.. but make sure that summit is aware that both events are taking place at the same time, and not allow one person to be scheduled for something at each event at the same time
[20:42] <jcastro> cjohnston: hey I need that travel info for when you plan on stopping by
[20:43] <AlanBell> oh, my local summit is broken after upgrading to oneiric
[20:43] <AlanBell> (could be unrelated to that)
[20:45] <AlanBell> argh, it could be the django update
[20:46] <cjohnston> jcastro: we are just gonna park at the dock...
[20:46] <jcastro> ok
[20:46] <cjohnston> we are driving down there monday the 17th, and get back tuesday the 25th
[20:47] <cjohnston> are you home those two days
[20:48] <AlanBell> fixored. Summit doesn't run by default on oneiric.
[20:48] <cjohnston> AlanBell: no it doesnt.. outdated versions suck
[20:49] <AlanBell> its fine, a one line fix
[21:03] <AlanBell> thinking of having a URL like this-> http://summit.ubuntu.com/uds-p/roomset?rooms=antigua-1,antigua-2,grand-sierra-f
[21:05] <jcastro> oooh
[21:05] <cjohnston> I think pg 1 pg 2 would be better
[21:06] <cjohnston> or easier
[21:06] <AlanBell> how do you work out what goes on which page?
[21:06] <mhall119> alphabetical order
[21:06] <AlanBell> this way you could have a screen showing "stuff on this floor"
[21:06] <mhall119> or we can just give a list of room ids, it'd be shorter than names
[21:06] <mhall119> AlanBell: only one floor
[21:07] <AlanBell> brussels wasn't
[21:07] <mhall119> fancy belgians
[21:08] <AlanBell> but anyhow, that was an example of why you might want the flexibility to do a schedule of an arbitary set of rooms
[21:09] <mhall119> true
[21:09] <mhall119> I think that would be better, if not easier
[21:09] <AlanBell> I think it would be easier :)
[21:10] <mhall119> though I'm not sure how useful "stuff on this floor" would be
[21:10] <mhall119> I don't want to miss out on interesting sessions just because they're on a different floor from my last session
[21:11] <cjohnston> well... that would be have a monitor "this floorr" and a monitor "first floor"
[21:11] <AlanBell> three monitors stacked vertically
[21:12] <mhall119> I'm beginning to think the monitors approach just doesn't scale well
[21:12] <AlanBell> however, the point is to have a way of doing ubuntu rooms, and linaro rooms, allowing for overlap, and allowing dual monitor setups
[21:12] <mhall119> properly segregating concurrent summits would give us that
[21:13] <AlanBell> if you just pass a room list on the query string then you can do anything
[21:13] <mhall119> AlanBell: have you started on that yet?
[21:13] <cjohnston> mhall119: I am all for doing that... we just need jcastro to give us permission
[21:14] <mhall119> since when do we need his permission? :)
[21:14] <cjohnston> I think that would be the best easiest cleanest way
[21:14] <cjohnston> ok then.. lets do it!
[21:14] <jcastro> permission for what?
[21:14] <mhall119> I thought AlanBell already was!
[21:14] <cjohnston> (we need him to do it tho so that when it breaks we blame him)
[21:14] <AlanBell> not yet mhall119, just looked at the linaro stuff, and in some django documentation on parsing lists in urls or query strings
[21:14] <jcastro> oh, so the way it will be, is the areas around the linaro rooms will have the linaro shcedules
[21:14] <cjohnston> mhall119: im talking the segregating summits
[21:14] <jcastro> and then we can put the uds ones where the UDS TVs will be
[21:14] <jcastro> and certain spots in the middle will have 2 displays, one for linaro, one for UDS
[21:15] <cjohnston> jcastro: can we just do it right, and make them two different summits?
[21:15] <mhall119> cjohnston: oh that, yeah, I wish we could have done that this cycle, but there was just so much work in getting things cleaner and stabilized
[21:15] <jcastro> cjohnston: yeah, sure, just not for this UDS.
[21:15] <cjohnston> its dont
[21:15] <cjohnston> done
[21:15] <AlanBell> if they are different summits you will struggle with room sharing, and people sharing
[21:15] <mhall119> no it's not
[21:16] <cjohnston> mhall119: http://bazaar.launchpad.net/~summit-hackers/summit/trunk/revision/168 ?
[21:17] <cjohnston> i think the scheduler would need a little love.. but its there
[21:17] <mhall119> cjohnston: that just lets one summit use multiple LP Sprint records
[21:17] <cjohnston> o.. i thought it allowed multiple sprints
[21:18] <cjohnston> ahh.. misreading
[21:18] <cjohnston> jcastro: are the rooms that linaro has there stuff in linaro only rooms?
[21:18] <jcastro> some of them
[21:18] <jcastro> and only some of the time
[21:18] <cjohnston> 17.14.33 < jcastro> oh, so the way it will be, is the areas around the linaro rooms will have the linaro shcedules
[21:19] <cjohnston> so we need uds monitors everywhere
[21:19] <jcastro> yeah, the dedicated hackrooms
[21:19] <jcastro> well, it was explained to me that most of our stuff will be in the southern end of the place
[21:19] <jcastro> they will basically be at the end of each hallway
[21:20] <jcastro> cjohnston: I figure just make it flexible enough to be able to show the rooms we want like alan says
[21:20] <jcastro> IS is handling the # of TVs and where to put them, etc.
[21:20] <cjohnston> ok
[21:23]  * AlanBell has a functional schedule for UDS Quintisential Quoll