Reid, Igal -- let me know if you need it reformatted. Explanation follows:
Format is: Talk ID, Room #, Date, Start Time, End Time
I had to adjust the start times that were in the spreadsheet in the
afternoon to fit our actual schedule :)
I did not add any rooms or time blocks.
Regarding rooms --
Here's my key for the room #s:
1 - Cooking
2 - Cooking
3 - Hacks
4 - Business
5 - Culture
6 - Chemistry
7 - Large Ballroom
8 - Large Ballroom
I can adjust those to actual room names (I believe Peter came up with
some?) if that helps.
Also, the track-to-room mapping is ROUGH :) I tried to keep to it, and
managed to do it most of the time, but we had to shift things around a
bit to make everything work.
-selena
Subject: [osbridgepdx-technology:391] Re: Tantalizingly close: the schedule!
Date: 2009-05-07 12:23:28 PM -0700
From: "M. Edward (Ed) Borasky" <zzn...@gmail.com>
To: osbridgepdx...@googlegroups.com
Our logistics volunteer, Peter (who is doing a great deal of unglamorous
quote gathering and spreadsheet generation that we desperately needed),
has already given this a lot of thought and names were already chosen on
a "bridge" theme.
-selena
Fremont, Steel, Broadway, Burnside, Morrison, Hawthorne, Marquam, Ross
Island, Sellwood, St. Johns ... we need more rooms!!
Reid and I are well-underway on putting together the schedule display. I
believe we have most of low-level code done, and we're working on the
UI. We've gone down a time-block schedule (it groups together things
happening at the same time so that the rows are time and columns are
streams of concurrent events), rather than a time-room grid schedule.
This approach complicates coding, but makes much better use of available
space.
Reid is focused on finishing up the UI for the display. I'm working on
reworking events so they have ScheduleItems (e.g., the coffee break)
that aren't actual session elements. After that, we'll rework events to
allow slug names (e.g., 2009bof for BoFs) and a way to aggregate events
(e.g., 2009 and 2009bof and 2009un) so that we can display a master
schedule for all of their scheduled content, despite it being
effectively part of a separate subevent (e.g., 2009un, the unconference,
will begin accepting proposals right before the conference, but its
proposals will not go into the same pool that the actual conference
sessions).
-igal