summaryrefslogtreecommitdiffstats
path: root/2023/organizers-notebook
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2023-09-16 10:17:22 -0400
committerSacha Chua <sacha@sachachua.com>2023-09-16 10:17:22 -0400
commit12059f1e8a3987f31cbbd36db459a3e4d854ae5d (patch)
treeddb9c5592f94c46d6f0c95cea5d8be87621ead26 /2023/organizers-notebook
parentf6b023b3eed8faa58857f76e4fe14368f80e106c (diff)
downloademacsconf-wiki-12059f1e8a3987f31cbbd36db459a3e4d854ae5d.tar.xz
emacsconf-wiki-12059f1e8a3987f31cbbd36db459a3e4d854ae5d.zip
add schedule notes
Diffstat (limited to '2023/organizers-notebook')
-rw-r--r--2023/organizers-notebook/index.org20
1 files changed, 19 insertions, 1 deletions
diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org
index 60fe7fd0..db1e9e59 100644
--- a/2023/organizers-notebook/index.org
+++ b/2023/organizers-notebook/index.org
@@ -303,7 +303,25 @@ Sacha
:PROPERTIES:
:CUSTOM_ID: draft-schedule
:END:
-#+INCLUDE: schedule.svg export html
+#+INCLUDE: schedule.svg export EXPORT html
+
+Schedule notes:
+- Saturday on the General track: Org day
+ - 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:taming and emacsconf:one both deal with exports in some way
+ - emacsconf:writing is connected to emacsconf:nabokov
+ - emacsconf:solo and emacsconf:collab are amusing to pair together
+- 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.
+- Saturday afternoon, developer track: REPLs (+ woof because it's Org-related, so we can put it on Org day next to a non-live Q&A)
+ emacsconf:eval and emacsconf:repl are related
+ - if emacsconf:woof happens, it could be nice to have the Q&A go into Org devel brainstorming
+- Sunday morning: Hyperbole (gen track, then crossing over to dev for testing)
+ - morning because [[emacsconf:test]] has to be in the morning; 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
+- Sunday afternoon: mentor to sharing: community, with an aside on [[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 the gray talks don't materialize or if talks get cancelled, we can have an open meetup possibly with breakout rooms
* Archive
:PROPERTIES: