|
|
# Table of Contents
- [How do we want to schedule talks?](#schedule)
- [Notes](#schedule-notes)
- [Option A: General and development tracks - 15/25 buffers, 60 min lunch, dev starts at 10](#gen-and-dev)
- [Option B: Two afternoon tracks (dev starts at 13:30), 10/20 buffer, 60 min lunch](#two-afternoons)
- [Option C: One afternoon track, 5/10 minute buffers, 60 minute lunch](#one-afternoon)
- [Option D: Remove buffer from non-live talks (not recommended)](#no-irc)
- [Option E: Reduce buffer to non-round numbers (3/7 minutes, like 2021); 10min break 30min lunch (not recommended)](#non-round)
- [Option F: Pack everything in one long day (current schedule)](#long)
<a id="schedule"></a>
# How do we want to schedule talks?
<a id="schedule-notes"></a>
## Notes
- Green: no availability constraints
- Red: invalid because of availability constraint
- Dashed: IRC/pad Q&A, not live
Host role:
- Give the speaker a heads-up before their Q&A session begins
- If needed, read the questions from the pad to the speaker (Many speakers are comfortable reading the pad on their own.)
- Give the speaker time warnings before the end of their Q&A session on the stream. Interested participants can continue
Streamer role:
- Switch between playing the prerec and joining the Q&A session
- Adjust audio volume at the beginning of the Q&A session
- (optional) Switch scene layouts to focus on different things
Updating the images requires `emacsconf-schedule.el` from
`git@git.emacsconf.org:emacsconf-el` and `emacsconf-org-file` set to
wherever the private conf org file is.
<a id="gen-and-dev"></a>
## Option A: General and development tracks - 15/25 buffers, 60 min lunch, dev starts at 10
- Lots of space for Q&A and hallway conversations
- People can probably find lots of sessions that interest them throughout the day
- Can give some talks extra time if we want
- Need host/streamer(s) for dev track
- 
<a id="two-afternoons"></a>
## Option B: Two afternoon tracks (dev starts at 13:30), 10/20 buffer, 60 min lunch
- Good option if we don't have enough hosts/streamers to cover both days
- Some room to breathe, some dev talks still on the main track
- LUNCH: Ends at 13:45 after 13:30
- 
<a id="one-afternoon"></a>
## Option C: One afternoon track, 5/10 minute buffers, 60 minute lunch
- Lightens up the schedule a little bit, allows us to test out tracks without committing too much
- Needs an extra host and streamer for one afternoon
- 
<a id="no-irc"></a>
## Option D: Remove buffer from non-live talks (not recommended)
- Considerations:
- Frees up about 20 minutes on each day, so we might be able to squeeze in two more talks sideways.
- Pretty frenetic
- Not recommended
- 
<a id="non-round"></a>
## Option E: Reduce buffer to non-round numbers (3/7 minutes, like 2021); 10min break 30min lunch (not recommended)
- Schedule looks too precise, sets expectations; timekeeping is more challenging
- Pretty frenetic
- Could probably use shifts for hosts or streamers
- Not recommended
- 
<a id="long"></a>
## Option F: Pack everything in one long day (current schedule)
- Considerations:
- Difficult to accommodate extra talks
- Host/streamer have a very long intense day
- Ideas:
- Split up hosting duties into shifts (volunteers can read the questions)
- Use prerecorded intros and outros
- Split up streaming duties into shifts (volunteers can adjust audio volume, switch to the right BBB room)
- Set up cloud streaming so that streamers can work in shifts
- 
|
