fixup! Add schedule-option-sun-am

Add schedule-option-sun-am

1 files changed, 116 insertions, 2 deletions

diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org
index d414c374..2db1c804 100644
--- a/2023/organizers-notebook/index.org
+++ b/2023/organizers-notebook/index.org
@@ -618,7 +618,7 @@ Let's see if we can decide on this by [2023-10-13 Fri] so that we can
 e-mail the draft schedules to people.
 
 Compared to [[#draft-schedule][two-track schedule]]:
-#+INCLUDE: schedule.svg export html
+#+INCLUDE: schedule.svg export EXPORT EXPORT html
 
 What if we have three tracks instead?
 
@@ -632,7 +632,10 @@ What if we have three tracks instead?
   - Easier to explain the schedule
   - More logical grouping
   - Ends earlier, which is easier for participants from Europe         
-
+  - votes: max (Three tracks is the best policy if you’re more than 75% sure that you can round up the volunteers)
+- Three tracks just for Sunday morning:
+  - Allows us to have 20 minutes between talks instead of 15
+    
 #+begin_src emacs-lisp :exports none
 (defun emacsconf-schedule-copy-previous-track (list)
 	(cl-loop
@@ -752,6 +755,112 @@ What if we have three tracks instead?
 #+end_comment
 
 #+INCLUDE: schedule-option-aligned-talks.svg export html
+**** Three tracks for Sunday morning?
+:PROPERTIES:
+:CUSTOM_ID: three-tracks-sun-am
+:END:
+
+
+
+#+begin_src emacs-lisp :results value replace :exports results :var filename="schedule-option-sun-am.svg" :eval never-export
+(emacsconf-schedule-test
+ filename
+ (emacsconf-schedule-tracks
+	'((:label "Saturday"
+						:start "2023-12-02 9:00"
+						:end "2023-12-02 18:00"
+						:tracks ("A" "B" "C"))
+		(:label "Sunday"
+						:start "2023-12-03 9:00"
+						:end "2023-12-03 18:00"
+						:tracks ("A" "B" "C"))))
+ (emacsconf-time-constraints '())
+ (emacsconf-tracks
+	'((:name "A" :id "a")
+		(:name "B" :id "b")
+		(:name "C" :id "c")))
+ (arranged
+  (emacsconf-schedule-inflate-sexp
+				'(("A Saturday, Dec 2" :start "2023-12-02 09:00" :track "A")
+					sat-open
+					adventure
+					uni
+					table
+					teaching
+					writing
+					(lunch :start "12:00")
+					nabokov 
+					collab
+					(woof)
+					solo
+					unentangling
+					ref
+					(devel) 
+					(sat-close)
+					("DEV Saturday, Dec 2" :start "2023-12-02 10:00" :track "B")
+					(matplotllm)
+					(voice)
+					(llm)
+					(lunch :start "12:00")
+					(overlay)
+					(eval)
+					(repl :start "14:00")
+					(hyperdrive)
+					(extending)
+					("GEN Sunday, Dec 3" :start "2023-12-03 09:00" :track "A")
+					sun-open
+					hyperamp
+					koutline
+					taming 
+					one
+					cubing
+					(lunch)
+					(emms)
+					(steno)
+					mentor
+					break
+					(hn :start "15:00")
+					web
+					sharing
+					sun-close
+					("DEV Sunday, Dec 3" :start "2023-12-03 10:00" :track "B")
+					scheme
+					test
+					(flat)
+					(lunch :start "12:15" :time "45")
+					gc
+					lspocaml
+					(windows :start "14:00")
+					(emacsconf)
+					(emacsen)
+					("C Sunday Dec 3" :start "2023-12-03 10:00" :track "C")
+					poltys
+					(parallel)
+					eat
+					)))
+ (emacsconf-schedule-break-time 10)
+ (emacsconf-schedule-lunch-time 60)
+ (emacsconf-schedule-default-buffer-minutes 20)
+ (emacsconf-schedule-svg-modify-functions '(emacsconf-schedule-svg-color-by-status))
+ (emacsconf-schedule-default-buffer-minutes-for-live-q-and-a 20)
+ (emacsconf-schedule-validation-functions
+	'(emacsconf-schedule-validate-time-constraints
+		;; emacsconf-schedule-validate-live-q-and-a-sessions-are-staggered
+		emacsconf-schedule-validate-all-talks-present
+		emacsconf-schedule-validate-no-duplicates))
+ (emacsconf-schedule-strategies
+	'(emacsconf-schedule-copy-previous-track emacsconf-schedule-allocate-buffer-time)))
+#+end_src
+
+#+RESULTS:
+:results:
+:end:
+
+#+begin_comment
+[[file:schedule-option-sun-am.svg]]
+#+end_comment
+
+#+INCLUDE: schedule-option-sun-am.svg export html
 
 ** Prepare infrastructure
 :PROPERTIES:
@@ -863,6 +972,11 @@ use it when recording the intros.
   - votes: zaeph
 - OPTION: Asking speakers if they want us to use any honorifics in their intro:
   - Observes personal preferences
+  - votes: corwin, max, jc (We can also say that we prefer not to use honorifics (it's not an academic
+    - Corwin's suggested wording: We will usually introduce you by your first name (or handle, if you prefer to go by a pseudonym) but if you'd rather be introduced
+      differently (for example honorific followed by last-name, or
+      whatever you prefer) just let us know.
+ conference) but we respect people's preferences.)
 - OPTION: Using honorifics based on e-mail signatures and intros:
   - Recognizes credentials