Tweak schedule and check for overlap

1 files changed, 21 insertions, 13 deletions

diff --git a/2022/decisions.md b/2022/decisions.md
index a0f31e97..dd2bdea4 100644
--- a/2022/decisions.md
+++ b/2022/decisions.md
@@ -3,8 +3,8 @@
 
 -   [How do we want to schedule talks?](#schedule)
     -   [Notes](#schedule-notes)
-    -   [Option G: Time-aligned](#gen-and-dev-aligned)
     -   [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)
@@ -16,6 +16,12 @@
 
 # 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
@@ -50,29 +56,31 @@ Updating the images requires `emacsconf-schedule.el` from
 wherever the private conf org file is.
 
 
-<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 wil have to choose.
-
--   ![img](schedule-option-gen-and-dev-aligned.svg)
-
-
 <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
--   Need host/streamer(s) for dev track
+-   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 wil 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