add TOC, rearrange sections, add next steps for schedule

1 files changed, 54 insertions, 42 deletions

diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org
index 4b110fc5..7298af94 100644
--- a/2023/organizers-notebook/index.org
+++ b/2023/organizers-notebook/index.org
@@ -429,49 +429,13 @@ Sacha
 [[file:schedule.svg]]
 #+end_comment
 
-#+INCLUDE: schedule.svg export EXPORT html
+#+INCLUDE: schedule.svg export html
 
-Schedule notes:
+*** Draft schedule as a list
+:PROPERTIES:
+:CUSTOM_ID: schedule-list
+:END:
 
-- Legend: dashed line means non-BBB Q&A; light gray means penciled-in talk
-- Saturday on the General track: Org day + misc
-  - emacsconf:adventure is the first talk because of availability constraints; would be nice to connect it to emacsconf:solo
-  - emacsconf:uni for teaching, emacsconf:table for grading
-  - emacsconf:taming and emacsconf:one both deal with exports in some way. emacsconf:unentangling would be nice to add here, but that one needs to be in the afternoon because of availability constraints.
-  - emacsconf:writing is connected to emacsconf:nabokov (blog posts, novel). It's also a little connected to emacsconf:one (exporting a blog).
-  - emacsconf:collab and emacsconf:solo are amusing to pair together, but maybe following emacsconf:collab (coordinating with other people who use Org) with emacsconf:woof (Org development coordination) also makes sense and makes it so that [[emacsconf:woof]] isn't too late (Europe/Paris timezone). I put emacsconf:woof on the general track because it's Org-related and could encourage people to help out. Penciled in because bzg isn't sure he'll make it.
-  - [[emacsconf:unentangling]] and emacsconf:ref are also Org-related. emacsconf:ref would be nice to place together with emacsconf:nabokov, but that would move emacsconf:woof and emacsconf:unentangling too late.
-  - [[emacsconf:devel]] is not Org-related, but probably good to share with everyone.
-- Saturday morning Development track: large language models, AI. Has to be morning because of emacsconf:matplotllm. emacsconf:llm is about general interfaces, so we can put that last. Could have a general LLM discussion after the talks. Can't swap it with Sunday morning because [[emacsconf:test]] should stick with [[emacsconf:hyperamp]] and emacsconf:koutline (Hyperbole talks), and the Hyperbole talks won't fit into Saturday morning
-- Saturday afternoon, developer track: REPLs, misc talks
-  - start off with developer tweaks: emacsconf:overlay (compilation), and then emacsconf:eval and emacsconf:repl are paired together
-  - emacsconf:hyperdrive: adding another file protocol, using HTTP APIs
-  - [[emacsconf:extending]] might just be replays of demos + Q&A session if people are interested
-- Sunday morning gen: Hyperbole (gen track, then crossing over to dev for testing) + misc talks
-  - Hyperbole mini-track is in the morning because of [[emacsconf:test]]'s availability constraints; emacsconf:hyperamp and emacsconf:koutline go before it. Try to avoid conflicts so they can attend each other's talks
-  - Sunday morning after emacsconf:test could be a fun extended "let's write tests together" session if someone wants to lead it
-  - emacsconf:parallel needs to go in the morning. Might be okay to include in the general talk.
-  - emacsconf:poltys and emacsconf:cubing aren't related to Hyperbole, but we need to fit them into the schedule somewhere. It would be nice to connect emacsconf:poltys (talking to web browsers from Emacs) to emacsconf:web (doing web stuff in Emacs instead), but emacsconf:poltys needs to be in the morning (which is pretty full) and emacsconf:web is in the afternoon because Yuchen is in Australia/Sydney.
-  - emacsconf:cubing can be something fun to transition to lunch, then.
-- Sunday afternoon gen: misc talks, community
-  - emacsconf:eat is about shells and running commands, so it's generally useful
-  - [[emacsconf:emms]] is a user+dev talk
-  - community theme (emacsconf:mentor, emacsconf:hn, emacsconf:sharing), with an aside for [[emacsconf:web]] (using Emacs as a client for stuff). [[emacsconf:sharing]] is possible closing keynote - encourage people to go out and explore/share all year? If not, emacsconf:web could be good for a closing talk - encouraging people to use Emacs for more stuff.
-- Sunday dev: misc dev talks
-  - Morning:
-    - emacsconf:test is related to the Hyperbole talks emacsconf:hyperamp and emacsconf:koutline, so we don't want to overlap with the Q&A for those talks
-    - emacsconf:flat, emacsconf:scheme, emacsconf:gc, emacsconf:flat, emacsconf:windows, emacsconf:emacsconf, emacsconf:steno 
-    - emacsconf:emacsen is more high-level and can talk about other editors
-- checking with emacsconf:web and emacsconf:hn if ~3pm Sunday afternoon (~7am Mon local time) is okay with them. It would be nice to pair it with emacsconf:hn, which is nice to connect to emacsconf:mentor and emacsconf:web.
-- if the talks get cancelled, we can have an open meetup possibly with
-  breakout rooms
-- coordination notes:
-  - TODO emacsconf:repl, emacsconf:eval
-  - emacsconf:hyperamp, emacsconf:koutline, and emacsconf:test are all in touch because they work on Hyperbole together
-  - emacsconf:hn and emacsconf:web
-  - [[emacsconf:unentangling]], [[emacsconf:taming]]? 
-  - emacsconf:matplotllm, emacsconf:voice, emacsconf:llm (so they don't all have to define LLMs?)
-    
     #+NAME: draft-schedule-table
     #+begin_src emacs-lisp :results raw replace :exports results  :eval t
   (string-join
@@ -546,8 +510,56 @@ Schedule notes:
   - 2023-12-03 Sun 16:20-16:40 [[emacsconf:sharing][sharing]]: Sharing Emacs is Caring Emacs: Emacs education and why I embraced video (Jacob Boxerman) 
   - 2023-12-03 Sun 17:00-17:10 [[emacsconf:sun-close][sun-close]]: Sunday closing remarks
 
+*** Schedule notes
+:PROPERTIES:
+:CUSTOM_ID: schedule-notes
+:END:
 
-
+- Legend: dashed line means non-BBB Q&A; light gray means penciled-in talk
+- Saturday on the General track: Org day + misc
+  - emacsconf:adventure is the first talk because of availability constraints; would be nice to connect it to emacsconf:solo
+  - emacsconf:uni for teaching, emacsconf:table for grading
+  - emacsconf:taming and emacsconf:one both deal with exports in some way. emacsconf:unentangling would be nice to add here, but that one needs to be in the afternoon because of availability constraints.
+  - emacsconf:writing is connected to emacsconf:nabokov (blog posts, novel). It's also a little connected to emacsconf:one (exporting a blog).
+  - emacsconf:collab and emacsconf:solo are amusing to pair together, but maybe following emacsconf:collab (coordinating with other people who use Org) with emacsconf:woof (Org development coordination) also makes sense and makes it so that [[emacsconf:woof]] isn't too late (Europe/Paris timezone). I put emacsconf:woof on the general track because it's Org-related and could encourage people to help out. Penciled in because bzg isn't sure he'll make it.
+  - [[emacsconf:unentangling]] and emacsconf:ref are also Org-related. emacsconf:ref would be nice to place together with emacsconf:nabokov, but that would move emacsconf:woof and emacsconf:unentangling too late.
+  - [[emacsconf:devel]] is not Org-related, but probably good to share with everyone.
+- Saturday morning Development track: large language models, AI. Has to be morning because of emacsconf:matplotllm. emacsconf:llm is about general interfaces, so we can put that last. Could have a general LLM discussion after the talks. Can't swap it with Sunday morning because [[emacsconf:test]] should stick with [[emacsconf:hyperamp]] and emacsconf:koutline (Hyperbole talks), and the Hyperbole talks won't fit into Saturday morning
+- Saturday afternoon, developer track: REPLs, misc talks
+  - start off with developer tweaks: emacsconf:overlay (compilation), and then emacsconf:eval and emacsconf:repl are paired together
+  - emacsconf:hyperdrive: adding another file protocol, using HTTP APIs
+  - [[emacsconf:extending]] might just be replays of demos + Q&A session if people are interested
+- Sunday morning gen: Hyperbole (gen track, then crossing over to dev for testing) + misc talks
+  - Hyperbole mini-track is in the morning because of [[emacsconf:test]]'s availability constraints; emacsconf:hyperamp and emacsconf:koutline go before it. Try to avoid conflicts so they can attend each other's talks
+  - Sunday morning after emacsconf:test could be a fun extended "let's write tests together" session if someone wants to lead it
+  - emacsconf:parallel needs to go in the morning. Might be okay to include in the general talk.
+  - emacsconf:poltys and emacsconf:cubing aren't related to Hyperbole, but we need to fit them into the schedule somewhere. It would be nice to connect emacsconf:poltys (talking to web browsers from Emacs) to emacsconf:web (doing web stuff in Emacs instead), but emacsconf:poltys needs to be in the morning (which is pretty full) and emacsconf:web is in the afternoon because Yuchen is in Australia/Sydney.
+  - emacsconf:cubing can be something fun to transition to lunch, then.
+- Sunday afternoon gen: misc talks, community
+  - emacsconf:eat is about shells and running commands, so it's generally useful
+  - [[emacsconf:emms]] is a user+dev talk
+  - community theme (emacsconf:mentor, emacsconf:hn, emacsconf:sharing), with an aside for [[emacsconf:web]] (using Emacs as a client for stuff). [[emacsconf:sharing]] is possible closing keynote - encourage people to go out and explore/share all year? If not, emacsconf:web could be good for a closing talk - encouraging people to use Emacs for more stuff.
+- Sunday dev: misc dev talks
+  - Morning:
+    - emacsconf:test is related to the Hyperbole talks emacsconf:hyperamp and emacsconf:koutline, so we don't want to overlap with the Q&A for those talks
+    - emacsconf:flat, emacsconf:scheme, emacsconf:gc, emacsconf:flat, emacsconf:windows, emacsconf:emacsconf, emacsconf:steno 
+    - emacsconf:emacsen is more high-level and can talk about other editors
+- checking with emacsconf:web and emacsconf:hn if ~3pm Sunday afternoon (~7am Mon local time) is okay with them. It would be nice to pair it with emacsconf:hn, which is nice to connect to emacsconf:mentor and emacsconf:web.
+- if the talks get cancelled, we can have an open meetup possibly with
+  breakout rooms
+- coordination notes:
+  - TODO emacsconf:repl, emacsconf:eval
+  - emacsconf:hyperamp, emacsconf:koutline, and emacsconf:test are all in touch because they work on Hyperbole together
+  - emacsconf:hn and emacsconf:web
+  - [[emacsconf:unentangling]], [[emacsconf:taming]]? 
+  - emacsconf:matplotllm, emacsconf:voice, emacsconf:llm (so they don't all have to define LLMs?)
+- next steps for schedule:
+  - sanity-check with other organizers/volunteers
+  - reach out to speakers so that they can get a sense of where they
+    are in the schedule, see if they really want to make it to a
+    conflicting session's Q&A live (they'll have early access to the
+    videos), etc.
+    
 * E-mail templates
 :PROPERTIES:
 :CUSTOM_ID: templates