update draft schedule and notes

1 files changed, 44 insertions, 36 deletions

diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org
index 662f8130..adce853c 100644
--- a/2023/organizers-notebook/index.org
+++ b/2023/organizers-notebook/index.org
@@ -366,10 +366,10 @@ Sacha
 					writing
 					nabokov 
 					collab
+					(woof :track "General")
 					solo
 					ref
 					unentangling
-					(woof :track "General")
 					(devel :track "General") 
 					(sat-close)
 					("DEV Saturday, Dec 2" :start "2023-12-02 10:00")
@@ -380,9 +380,8 @@ Sacha
 					(overlay :start "12:50")
 					(eval)
 					(repl)
+					(hyperdrive :track "Development")
 					(extending :track "Development")
-					(steno :track "Development")
-					(emacsen :track "Development")
 					("GEN Sunday, Dec 3" :start "2023-12-03 09:00")
 					sun-open
 					hyperamp
@@ -392,7 +391,7 @@ Sacha
 					cubing
 					lunch
 					(eat :start "12:50")
-					(hyperdrive :track "General")
+					(emms :track "General")
 					mentor
 					(hn :start "15:00")
 					web
@@ -407,7 +406,8 @@ Sacha
 					(flat :track "Development")
 					(windows :track "Development")
 					(emacsconf :track "Development")
-					(emms :track "Development")
+					(steno :track "Development")
+					(emacsen :track "Development")
 					))
 	(setq emacsconf-schedule-draft (emacsconf-schedule-prepare (emacsconf-schedule-inflate-sexp emacsconf-schedule-plan)))
 	(prog1 (string-join (emacsconf-schedule-validate emacsconf-schedule-draft) "\n")
@@ -437,26 +437,34 @@ Schedule notes:
 - 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, table for grading
+  - 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.
-  - emacsconf:collab and emacsconf:solo are amusing to pair together
-  - [[emacsconf:unentangling]] and [[emacsconf:taming]] are related, but they have opposite availability constraints
-  - I put emacsconf:woof on the general track because it's Org-related and could encourage people to help out. If it emacsconf:woof happens, it could be nice to have the Q&A go into Org devel brainstorming
-- 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
-  - start off with developer tweaks: emacsconf:overlay, and then emacsconf:eval and emacsconf:repl are paired together
+  - 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]] is also Org-related.
+  - [[emacsconf:devel]] is 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?
   - [[emacsconf:extending]] might just be replays of demos + Q&A session if people are interested
-  - emacsconf:steno: programming faster with steno?
-  - emacsconf:emacsen is more high-level and can talk about other editors    
-- Sunday morning: Hyperbole (gen track, then crossing over to dev for testing) + misc talks
+- 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: community theme (emacsconf:mentor to 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 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:scheme, emacsconf:lspocaml
+    - emacsconf:test is related to the Hyperbole talks emacsconf:hyperamp and emacsconf:koutline
+  - Afternoon:
+    - 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 local time) is okay with them. It would be nice to pair it with emacsconf:hn, which is nice to pair with emacsconf:mentor, but maybe I can move it to Saturday afternoon.
 - if the talks get cancelled, we can have an open meetup possibly with
   breakout rooms
@@ -465,25 +473,25 @@ Schedule notes:
   - emacsconf:hyperamp, emacsconf:koutline, and emacsconf:test are all in touch because they work on Hyperbole together
   - [[emacsconf:unentangling]], [[emacsconf:taming]]? 
   
-  #+NAME: draft-schedule-table
-  #+begin_src emacs-lisp :results raw replace :exports results  :eval t
-(string-join
- (seq-keep (lambda (o) (when (plist-get o :slug)
+    #+NAME: draft-schedule-table
+    #+begin_src emacs-lisp :results raw replace :exports results  :eval t
+  (string-join
+   (seq-keep (lambda (o) (when (plist-get o :slug)
 												
-												(concat "| "
-												 (replace-regexp-in-string "[<>]" ""
-																									 (plist-get o :scheduled))
-												 " | "
-												 (format "[[emacsconf:%s][%s]]"
-																 (plist-get o :slug)
-																 (plist-get o :slug))
-												 " | "
-												 (plist-get o :title)
-												 " | "
-												 (plist-get o :speakers)
-												 "|")))
-					(sort emacsconf-schedule-draft (lambda (a b) (string< (plist-get a :scheduled) (plist-get b :scheduled))))) "\n")
-#+end_src
+												  (concat "| "
+												   (replace-regexp-in-string "[<>]" ""
+																									   (plist-get o :scheduled))
+												   " | "
+												   (format "[[emacsconf:%s][%s]]"
+																   (plist-get o :slug)
+																   (plist-get o :slug))
+												   " | "
+												   (plist-get o :title)
+												   " | "
+												   (plist-get o :speakers)
+												   "|")))
+					  (sort emacsconf-schedule-draft (lambda (a b) (string< (plist-get a :scheduled) (plist-get b :scheduled))))) "\n")
+  #+end_src
 
 | 2023-12-02 Sat 09:00-09:10 | [[emacsconf:sat-open][sat-open]]     | Saturday opening remarks                                                                                    |                                    |
 | 2023-12-02 Sat 09:10-09:20 | [[emacsconf:adventure][adventure]]    | An Org-Mode based text adventure game for learning the basics of Emacs, inside Emacs, written in Emacs Lisp | Chung-hong Chan                    |