You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To help with all sorts of aspects of planning, we need a skeleton schedule. At first, this should go into the internal docs repo, until we're ready to share this on the website. I expect there'll be a little bit of back and forth between the committee about this, and I don't want us to commit to anything before we're happy we've not missed anything out.
This should take the form of a rough outline -- even saying something like "we'll have X talks of length Y in the morning in rooms A, B, C" would be very helpful.
We don't need to think about how we'll display the schedule yet. The purpose of this is to aid with planning, so it's important that what we've got is flexible.
To help with all sorts of aspects of planning, we need a skeleton schedule. At first, this should go into the internal docs repo, until we're ready to share this on the website. I expect there'll be a little bit of back and forth between the committee about this, and I don't want us to commit to anything before we're happy we've not missed anything out.
This should take the form of a rough outline -- even saying something like "we'll have X talks of length Y in the morning in rooms A, B, C" would be very helpful.
We don't need to think about how we'll display the schedule yet. The purpose of this is to aid with planning, so it's important that what we've got is flexible.
We've already got a (short) list of things that should be scheduled, and we've begun to record what we've provisionally allocated for each room.
The text was updated successfully, but these errors were encountered: