summaryrefslogtreecommitdiffstats
path: root/2023/organizers-notebook.md
diff options
context:
space:
mode:
Diffstat (limited to '2023/organizers-notebook.md')
-rw-r--r--2023/organizers-notebook.md24
1 files changed, 12 insertions, 12 deletions
diff --git a/2023/organizers-notebook.md b/2023/organizers-notebook.md
index 931f27d0..c905999a 100644
--- a/2023/organizers-notebook.md
+++ b/2023/organizers-notebook.md
@@ -422,20 +422,20 @@ Sacha
Schedule notes:
- Saturday on the General track: Org day
- - [[adventure|/2023/talks/adventure "An Org-Mode based text adventure game for learning the basics of Emacs, inside Emacs, written in Emacs Lisp"]] is the first talk because of availability constraints; would be nice to connect it to [[solo|/2023/talks/solo "How I play TTRPGs in Emacs"]]
- - [[uni|/2023/talks/uni "Authoring and presenting university courses with Emacs and a full libre software stack"]] for teaching, table for grading
- - [[taming|/2023/talks/taming "Taming things with Org Mode"]] and [[one|/2023/talks/one "one.el: the static site generator for Emacs Lisp Programmers"]] both deal with exports in some way
- - [[writing|/2023/talks/writing "Emacs Turbo-Charges My Writing"]] is connected to [[nabokov|/2023/talks/nabokov "Why Nabokov would use Org-Mode if he were writing today"]]
- - [[solo|/2023/talks/solo "How I play TTRPGs in Emacs"]] and [[collab|/2023/talks/collab "Collaborative data processing and documenting using org-babel"]] are amusing to pair together
-- Saturday morning Development track: large language models, AI. Has to be morning because of [[matplotllm|/2023/talks/matplotllm "MatplotLLM, iterative natural language data visualization in org-babel"]].
- [[llm|/2023/talks/llm "LLM clients in Emacs, functionality and standardization"]] is about general interfaces, so we can put that last.
+ - [adventure](https://emacsconf.org/2023/talks/adventure "An Org-Mode based text adventure game for learning the basics of Emacs, inside Emacs, written in Emacs Lisp") is the first talk because of availability constraints; would be nice to connect it to [solo](https://emacsconf.org/2023/talks/solo "How I play TTRPGs in Emacs")
+ - [uni](https://emacsconf.org/2023/talks/uni "Authoring and presenting university courses with Emacs and a full libre software stack") for teaching, table for grading
+ - [taming](https://emacsconf.org/2023/talks/taming "Taming things with Org Mode") and [one](https://emacsconf.org/2023/talks/one "one.el: the static site generator for Emacs Lisp Programmers") both deal with exports in some way
+ - [writing](https://emacsconf.org/2023/talks/writing "Emacs Turbo-Charges My Writing") is connected to [nabokov](https://emacsconf.org/2023/talks/nabokov "Why Nabokov would use Org-Mode if he were writing today")
+ - [solo](https://emacsconf.org/2023/talks/solo "How I play TTRPGs in Emacs") and [collab](https://emacsconf.org/2023/talks/collab "Collaborative data processing and documenting using org-babel") are amusing to pair together
+- Saturday morning Development track: large language models, AI. Has to be morning because of [matplotllm](https://emacsconf.org/2023/talks/matplotllm "MatplotLLM, iterative natural language data visualization in org-babel").
+ [llm](https://emacsconf.org/2023/talks/llm "LLM clients in Emacs, functionality and standardization") 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)
- [[eval|/2023/talks/eval "Editor Integrated REPL Driven Development for all languages"]] and [[repl|/2023/talks/repl "REPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZ"]] are related
- - if [[woof|/2023/talks/woof "Watch Over Our Folders"]] happens, it could be nice to have the Q&A go into Org devel brainstorming
+ [eval](https://emacsconf.org/2023/talks/eval "Editor Integrated REPL Driven Development for all languages") and [repl](https://emacsconf.org/2023/talks/repl "REPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZ") are related
+ - if [woof](https://emacsconf.org/2023/talks/woof "Watch Over Our Folders") 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 [[test|/2023/talks/test "What I learned by writing test cases for GNU Hyperbole"]] has to be in the morning; [[hyperamp|/2023/talks/hyperamp "Top 10 Ways Hyperbole Amps Up Emacs"]] and [[koutline|/2023/talks/koutline "Using Koutline for stream of thought journaling"]] go before it, try to avoid conflicts so they can attend each other’s talks
- - Sunday morning after [[test|/2023/talks/test "What I learned by writing test cases for GNU Hyperbole"]] 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 [[web|/2023/talks/web "Emacs saves the Web"]] (using Emacs as a client for stuff). [[sharing|/2023/talks/sharing "Sharing Emacs is Caring Emacs: Emacs education and why I embraced video"]] is possible closing keynote - encourage people to go out and explore/share all year?
+ - morning because [test](https://emacsconf.org/2023/talks/test "What I learned by writing test cases for GNU Hyperbole") has to be in the morning; [hyperamp](https://emacsconf.org/2023/talks/hyperamp "Top 10 Ways Hyperbole Amps Up Emacs") and [koutline](https://emacsconf.org/2023/talks/koutline "Using Koutline for stream of thought journaling") go before it, try to avoid conflicts so they can attend each other’s talks
+ - Sunday morning after [test](https://emacsconf.org/2023/talks/test "What I learned by writing test cases for GNU Hyperbole") 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 [web](https://emacsconf.org/2023/talks/web "Emacs saves the Web") (using Emacs as a client for stuff). [sharing](https://emacsconf.org/2023/talks/sharing "Sharing Emacs is Caring Emacs: Emacs education and why I embraced video") 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
<a id="archive"></a>