Archived old options, tweaked order in schedule

1 files changed, 25 insertions, 89 deletions

diff --git a/2022/decisions.md b/2022/decisions.md
index 5eb72883..51da2a70 100644
--- a/2022/decisions.md
+++ b/2022/decisions.md
@@ -3,30 +3,13 @@
 
 -   [How do we want to schedule talks?](#schedule)
     -   [Notes](#schedule-notes)
+    -   [Option H: Gen starts with high-level use cases, second day has Hyperbole](#gen-to-specific)
     -   [Option A: General and development tracks - 15/25 buffers, 60 min lunch, dev starts at 10](#gen-and-dev)
-    -   [Option G: Time-aligned](#gen-and-dev-aligned)
-    -   [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>
 
-# DONE How do we want to schedule talks?
-
-<span class="timestamp-wrapper"><span class="timestamp">[2022-10-04 Tue]</span></span>
-
--   Discussed option G with zaeph on #emacsconf-org. zaeph prefers
-    option A over option G because it gives people more choices -
-    they can hop from talk to talk.
-
-<span class="timestamp-wrapper"><span class="timestamp">[2022-10-03 Mon]</span></span>
-
--   Discussed with bandali and zaeph on #emacsconf-org
--   Decided on Option A with B, C, or F as fallbacks depending on volunteer roster
--   Better for the viewers and the volunteers
+# TODO How do we want to schedule talks?
 
 
 <a id="schedule-notes"></a>
@@ -55,89 +38,42 @@ 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.
 
+<span class="timestamp-wrapper"><span class="timestamp">[2022-10-04 Tue]</span></span>
 
-<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
--   If they decide a talk isn't for them, they can switch and catch another one
--   Stagger live Q&A sessions so that just in case we have only one streamer, they can bounce back and forth
--   Can give some talks extra time if we want
--   Could use dedicated host/streamer(s) for dev track; if not, they can probably pick up questions themselves
-
--   ![img](schedule-option-gen-and-dev.svg)
-
-
-<a id="gen-and-dev-aligned"></a>
-
-## Option G: Time-aligned
-
--   Line up the starts and the Q&A; easier to display in a table, but
-    then we will really need to have multiple hosts/streamers, and
-    people will have to choose.
-
--   ![img](schedule-option-gen-and-dev-aligned.svg)
-
-
-<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
--   ![img](schedule-option-two-afternoon-tracks.svg)
-
-
-<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
-
--   ![img](schedule-option-one-afternoon-track.svg)
-
+-   Added option H. General starts with general Org use cases and moves on to more niche things on day 2.
 
-<a id="no-irc"></a>
+<span class="timestamp-wrapper"><span class="timestamp">[2022-10-04 Tue]</span></span>
 
-## Option D: Remove buffer from non-live talks (not recommended)
+-   Discussed option G with zaeph on #emacsconf-org. zaeph prefers
+    option A over option G because it gives people more choices -
+    they can hop from talk to talk.
 
--   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
+<span class="timestamp-wrapper"><span class="timestamp">[2022-10-03 Mon]</span></span>
 
--   ![img](schedule-option-only-live-qa.svg)
+-   Discussed with bandali and zaeph on #emacsconf-org
+-   Decided on Option A with B, C, or F as fallbacks depending on volunteer roster
+-   Better for the viewers and the volunteers
 
 
-<a id="non-round"></a>
+<a id="gen-to-specific"></a>
 
-## Option E: Reduce buffer to non-round numbers (3/7 minutes, like 2021); 10min break 30min lunch (not recommended)
+## Option H: Gen starts with high-level use cases, second day has Hyperbole
 
--   Schedule looks too precise, sets expectations; timekeeping is more challenging
--   Pretty frenetic
--   Could probably use shifts for hosts or streamers
--   Not recommended
+-   compared to A, general audience will be more interested in Org use cases than in Hyperbole, and then we can look at specific techniques on day 2
 
--   ![img](schedule-option-non-round-buffer.svg)
+-   ![img](schedule-option-gen-to-specific.svg)
 
 
-<a id="long"></a>
+<a id="gen-and-dev"></a>
 
-## Option F: Pack everything in one long day (current schedule)
+## Option A: General and development tracks - 15/25 buffers, 60 min lunch, dev starts at 10
 
--   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
+-   Lots of space for Q&A and hallway conversations
+-   People can probably find lots of sessions that interest them throughout the day
+-   If they decide a talk isn't for them, they can switch and catch another one
+-   Stagger live Q&A sessions so that just in case we have only one streamer, they can bounce back and forth
+-   Can give some talks extra time if we want
+-   Could use dedicated host/streamer(s) for dev track; if not, they can probably pick up questions themselves
 
--   ![img](schedule-option-one-full-day.svg)
+-   ![img](schedule-option-gen-and-dev.svg)