update schedule

1 files changed, 27 insertions, 0 deletions

diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org
index bb51b963..1c7b17d8 100644
--- a/2023/organizers-notebook/index.org
+++ b/2023/organizers-notebook/index.org
@@ -609,6 +609,8 @@ SCHEDULED: <2023-10-25 Wed>
 Good idea to include it because that gives people (a) more context on
 where a speaker is coming from, and (b) a feeling for the kinds of
 backgrounds and interests people have.
+*** TODO Follow up with people we haven't heard from in a while before the schedule is released
+SCHEDULED: <2023-10-18 Wed>
 ** Prepare infrastructure
 :PROPERTIES:
 :CUSTOM_ID: check-infra
@@ -640,6 +642,24 @@ Because the pads refer to the next and previous talks and include the talk title
 :PROPERTIES:
 :CUSTOM_ID: check-prerec
 :END:
+**** Process
+***** Set up for the new year
+As orga@res:
+
+- mkdir /data/emacsconf/$year
+- rm ~/current
+- ln -s /data/emacsconf/$year current
+- ln -s /data/emacsconf/$year $year
+When we receive files
+
+- mkdir ~/current/$slug
+- copy the files to there
+- ~/scripts/
+
+
+I don't have access
+
+
 **** Captions
 :PROPERTIES:
 :CUSTOM_ID: check-captions
@@ -712,6 +732,13 @@ conf.org.
 Actually recording the introductions can wait until closer to the
 conference because talk titles and Q&A methods can change. We can
 verify speaker name pronunciations at that time.
+**** Intros   :levels:
+
+- Good: Use the same template as before: In this talk, SPEAKER shares
+  TITLE OR SUMMARY. Afterwards, PRONOUN will handle questions over Q&A
+  METHOD.
+- Better: Include some more biographical information to give listeners some context.
+ 
 
 **** DONE Do we want to use honorifics like Dr.?                :decision:
 CLOSED: [2023-10-03 Tue 15:38] DEADLINE: <2023-11-14 Tue>