From a0a5cc1efb389391a5bcb1ebe5c8b6e75158b89c Mon Sep 17 00:00:00 2001 From: Sacha Chua Date: Fri, 22 Sep 2023 13:37:58 -0400 Subject: update schedule notes --- 2023/organizers-notebook.md | 240 +++++++++++++++++++++++++++++++------------- 1 file changed, 168 insertions(+), 72 deletions(-) (limited to '2023/organizers-notebook.md') diff --git a/2023/organizers-notebook.md b/2023/organizers-notebook.md index 00161cbb..889ef9cd 100644 --- a/2023/organizers-notebook.md +++ b/2023/organizers-notebook.md @@ -12,7 +12,11 @@ This file is automatically exported from [/2023/organizers-notebook/index.org](/ - [Draft CFP](#cfp) - [Distribute CFP](#distrib-cfp) - [Process submissions](#submission-process) + - [2023-09-22 EmacsConf 2023 progress report](#2023-09-22) - [Draft schedule](#draft-schedule) +- [E-mail templates](#orgb2db113) + - [Review](#org95fdd71) + - [Acceptance](#org420e87d) - [Archive](#archive) @@ -29,7 +33,7 @@ This file is automatically exported from [/2023/organizers-notebook/index.org](/ -CFP +CFP [2023-06-26 Mon] @@ -39,7 +43,7 @@ This file is automatically exported from [/2023/organizers-notebook/index.org](/ -Speaker notifications +Speaker notifications [2023-09-25 Mon] @@ -77,7 +81,7 @@ Last year, these were the actual dates: -## Draft CFP +## DONE Draft CFP ### How to mark pages as drafts @@ -210,7 +214,7 @@ postpone. Here are some thoughts: -## Distribute CFP +## DONE Distribute CFP ### DONE Add proposal review volunteers to emacsconf-submit @@ -220,22 +224,16 @@ postpone. Here are some thoughts: ### First announcement - -#### TODO Remove draft tags :sachac: - -#### TODO Post on emacsconf-discuss, emacs-tangents :bandali: - -#### TODO Sticky on reddit.com/r/emacs :zaeph: - -#### TODO Post in Emacs News :sachac: - -(link to wiki) +- Remove draft tags :sachac: +- Post on emacsconf-discuss, emacs-tangents :bandali: :zaeph: +- Sticky on reddit.com/r/emacs +- Post in Emacs News :sachac: ### Reminder -## Process submissions +## DONE Process submissions - Proposal received: sachac adds it to this document with status of PROPOSED - Fields: @@ -413,39 +411,67 @@ extending the CFP this time. Sacha +### Lessons learned :lessons: + +- Early acceptances are nice. A few got comments within the 1-week period. +- It’s a good idea to send the review and acceptance e-mails even to fellow organizers/volunteers, even if they helped write the page. =) +- I added some more automation for including a template in a mail reply +- We successfully didn’t panic about submissions, yay! It was nice to be able to draft schedules as we went along. + + + +## 2023-09-22 EmacsConf 2023 progress report + +- 42 talks accepted so far, whee! +- 3 talks penciled in (woof, emms, devel) - we’ll save time for them in the schedule, no worries +- doublecheck: + - all proposals responded to? + (everything accepted except for Noah’s talk, which she cancelled) + - availability correctly captured? +- draft schedule +- lessons learned +- next steps: + - start coordinating with speakers regarding draft schedule, wishlist of any talks they want to attend live + - coordinating with FSF regarding media.emacsconf.org + ## Draft schedule - Graphical view of the schedule Schedule for Saturday Saturday 9:00- 9:10 Saturday opening remarks sat-open 9:10- 9:20 An Org-Mode based text adventure game for learning the basics of Emacs, inside Emacs, written in Emacs Lisp adventure 9:30- 9:50 Authoring and presenting university courses with Emacs and a full libre software stack uni 10:10-10:20 Who needs Excel? Managing your students qualifications with org-table table 10:40-10:50 Taming things with Org Mode taming 11:10-11:30 one.el: the static site generator for Emacs Lisp Programmers one 12:50- 1:00 Emacs turbo-charges my writing writing 1:20- 1:30 Why Nabokov would use Org-Mode if he were writing today nabokov 1:50- 2:10 Programming at 200 wpm steno 2:20- 2:40 How I play TTRPGs in Emacs solo 3:00- 3:20 Collaborative data processing and documenting using org-babel collab 3:30- 3:50 Org-Mode workflow: informal reference tracking ref 4:00- 4:10 (Un)entangling projects and repos unentangling 4:20- 4:30 Emacs development updates devel 5:00- 5:10 Saturday closing remarks sat-close 10:00-10:10 MatplotLLM, iterative natural language data visualization in org-babel matplotllm 10:20-10:40 Improving access to AI-assisted literate programming with voice control voice 11:00-11:20 LLM clients in Emacs, functionality and standardization llm 12:50- 1:00 Editor Integrated REPL Driven Development for all languages eval 1:20- 2:00 REPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZ repl 2:10- 2:30 GNU Emacs for electronics, note-taking, and as lightweight IDE extending 2:50- 3:10 The Emacsen family, the design of an Emacs and the importance of Lisp emacsen 3:20- 3:40 Watch Over Our Folders woof 9 AM 10 AM 11 AM 12 PM 1 PM 2 PM 3 PM 4 PM 5 PM Schedule for Sunday Sunday 9:00- 9:05 Sunday opening remarks sun-open 9:05- 9:25 Top 10 ways Hyperbole amps up Emacs hyperamp 9:45-10:05 Using Koutline for stream of thought journaling koutline 10:15-10:25 Parallel Text Replacement: Does P = NP? parallel 10:45-11:05 The browser in a buffer poltys 11:25-11:45 Speedcubing in Emacs cubing 12:50- 1:02 Eat and Eat powered Eshell, fast featureful terminal inside Emacs eat 1:22- 2:02 hyperdrive.el: Peer-to-peer filesystem in Emacs hyperdrive 2:22- 2:32 Mentoring VS-Coders as an Emacsian (or How to show not tell people about the wonders of Emacs) mentor 3:00- 3:10 The many ways to browse Hacker News from Emacs hn 3:20- 4:00 Emacs saves the Web web 4:20- 4:40 Sharing Emacs is Caring Emacs: Emacs education and why I embraced video sharing 5:00- 5:10 Sunday closing remarks sun-close 10:00-10:20 Bringing joy to Scheme programming scheme 10:40-10:50 Writing a language server in OCaml for Emacs, fun, and profit lspocaml 11:10-11:30 What I learned by writing test cases for GNU Hyperbole test 12:50- 1:10 emacs-gc-stats: Does garbage collection actually slow down Emacs? gc 1:30- 1:40 A modern Emacs look-and-feel without pain flat 2:00- 2:40 Windows into Freedom windows 3:00- 3:20 EmacsConf.org: How we use Org Mode and TRAMP to organize and run a multi-track conference emacsconf 3:40- 4:20 Emacs MultiMedia System (EMMS) emms 9 AM 10 AM 11 AM 12 PM 1 PM 2 PM 3 PM 4 PM 5 PM + Graphical view of the schedule Schedule for Saturday Saturday 9:00- 9:10 Saturday opening remarks sat-open 9:10- 9:20 An Org-Mode based text adventure game for learning the basics of Emacs, inside Emacs, written in Emacs Lisp adventure 9:30- 9:50 Authoring and presenting university courses with Emacs and a full libre software stack uni 10:10-10:20 Who needs Excel? Managing your students qualifications with org-table table 10:40-10:50 Taming things with Org Mode taming 11:10-11:30 one.el: the static site generator for Emacs Lisp Programmers one 12:50- 1:00 Emacs turbo-charges my writing writing 1:20- 1:30 Why Nabokov would use Org-Mode if he were writing today nabokov 1:50- 2:10 Collaborative data processing and documenting using org-babel collab 2:20- 2:40 How I play TTRPGs in Emacs solo 3:00- 3:20 Org-Mode workflow: informal reference tracking ref 3:30- 3:40 (Un)entangling projects and repos unentangling 3:50- 4:10 Watch Over Our Folders woof 4:30- 4:40 Emacs development updates devel 5:00- 5:10 Saturday closing remarks sat-close 10:00-10:10 MatplotLLM, iterative natural language data visualization in org-babel matplotllm 10:20-10:40 Improving access to AI-assisted literate programming with voice control voice 11:00-11:20 LLM clients in Emacs, functionality and standardization llm 12:50- 1:10 Improving compiler diagnostics with Overlays overlay 1:30- 1:40 Editor Integrated REPL Driven Development for all languages eval 2:00- 2:40 REPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZ repl 2:50- 3:10 GNU Emacs for electronics, note-taking, and as lightweight IDE extending 3:30- 3:50 Programming at 200 wpm steno 4:00- 4:20 The Emacsen family, the design of an Emacs and the importance of Lisp emacsen 9 AM 10 AM 11 AM 12 PM 1 PM 2 PM 3 PM 4 PM 5 PM Schedule for Sunday Sunday 9:00- 9:05 Sunday opening remarks sun-open 9:05- 9:25 Top 10 ways Hyperbole amps up Emacs hyperamp 9:45-10:05 Using Koutline for stream of thought journaling koutline 10:15-10:25 Parallel Text Replacement: Does P = NP? parallel 10:45-11:05 The browser in a buffer poltys 11:25-11:45 Speedcubing in Emacs cubing 12:50- 1:00 Eat and Eat powered Eshell, fast featureful terminal inside Emacs eat 1:20- 2:00 hyperdrive.el: Peer-to-peer filesystem in Emacs hyperdrive 2:20- 2:30 Mentoring VS-Coders as an Emacsian (or How to show not tell people about the wonders of Emacs) mentor 3:00- 3:10 The many ways to browse Hacker News from Emacs hn 3:20- 4:00 Emacs saves the Web web 4:20- 4:40 Sharing Emacs is Caring Emacs: Emacs education and why I embraced video sharing 5:00- 5:10 Sunday closing remarks sun-close 10:00-10:20 Bringing joy to Scheme programming scheme 10:40-10:50 Writing a language server in OCaml for Emacs, fun, and profit lspocaml 11:10-11:30 What I learned by writing test cases for GNU Hyperbole test 12:50- 1:10 emacs-gc-stats: Does garbage collection actually slow down Emacs? gc 1:30- 1:40 A modern Emacs look-and-feel without pain flat 2:00- 2:40 Windows into Freedom windows 3:00- 3:20 EmacsConf.org: How we use Org Mode and TRAMP to organize and run a multi-track conference emacsconf 3:40- 4:20 Emacs MultiMedia System (EMMS) emms 9 AM 10 AM 11 AM 12 PM 1 PM 2 PM 3 PM 4 PM 5 PM Schedule notes: -- Legend: dashed line means non-BBB Q&A -- Saturday on the General track: Org day +- Legend: dashed line means non-BBB Q&A; light gray means penciled-in talk +- Saturday on the General track: Org day + misc - [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](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](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 + - [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. [unentangling](https://emacsconf.org/2023/talks/unentangling "(Un)entangling projects and repos") would be nice to add here, but that one needs to be in the afternoon because of availability constraints. + - [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") (blog posts, novel). It’s also a little connected to [one](https://emacsconf.org/2023/talks/one "one.el: the static site generator for Emacs Lisp Programmers"). + - [collab](https://emacsconf.org/2023/talks/collab "Collaborative data processing and documenting using org-babel") and [solo](https://emacsconf.org/2023/talks/solo "How I play TTRPGs in Emacs") are amusing to pair together + - [unentangling](https://emacsconf.org/2023/talks/unentangling "(Un)entangling projects and repos") and [taming](https://emacsconf.org/2023/talks/taming "Taming things with Org Mode") are related, but they have opposite availability constraints + - I put [woof](https://emacsconf.org/2023/talks/woof "Watch Over Our Folders") on the general track because it’s Org-related and could encourage people to help out. If it [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 +- 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. Could have a general LLM discussion after the talks. + Can’t swap it with Sunday morning because [test](https://emacsconf.org/2023/talks/test "What I learned by writing test cases for GNU Hyperbole") should stick with [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") (Hyperbole talks), and the Hyperbole talks won’t fit into Saturday morning +- Saturday afternoon, developer track: REPLs + - start off with developer tweaks: [overlay](https://emacsconf.org/2023/talks/overlay "Improving compiler diagnostics with Overlays"), and then [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 paired together + - [extending](https://emacsconf.org/2023/talks/extending "GNU Emacs for electronics, note-taking, and as lightweight IDE") might just be replays of demos + Q&A session if people are interested + - [steno](https://emacsconf.org/2023/talks/steno "Programming at 200 wpm"): programming faster with steno? + - [emacsen](https://emacsconf.org/2023/talks/emacsen "The Emacsen family, the design of an Emacs and the importance of Lisp") is more high-level and can talk about other editors +- Sunday morning: Hyperbole (gen track, then crossing over to dev for testing) + misc talks + - Hyperbole mini-track is in the morning because of [test](https://emacsconf.org/2023/talks/test "What I learned by writing test cases for GNU Hyperbole")’s availability constraints; [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: community theme ([mentor](https://emacsconf.org/2023/talks/mentor "Mentoring VS-Coders as an Emacsian (or How to show not tell people about the wonders of Emacs)") to [sharing](https://emacsconf.org/2023/talks/sharing "Sharing Emacs is Caring Emacs: Emacs education and why I embraced video")), 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 -- it would be nice to connect [poltys](https://emacsconf.org/2023/talks/poltys "The browser in a buffer") (talking to web browsers from Emacs) to [web](https://emacsconf.org/2023/talks/web "Emacs saves the Web") (doing web stuff in Emacs instead). [poltys](https://emacsconf.org/2023/talks/poltys "The browser in a buffer") needs to be in the morning (which is pretty full) and [web](https://emacsconf.org/2023/talks/web "Emacs saves the Web") is in the afternoon because Yuchen is in Australia/Sydney. -- [cubing](https://emacsconf.org/2023/talks/cubing "Speedcubing in Emacs") and [steno](https://emacsconf.org/2023/talks/steno "Programming at 200 wpm") are both about doing things quickly, but [steno](https://emacsconf.org/2023/talks/steno "Programming at 200 wpm") can also be placed near [nabokov](https://emacsconf.org/2023/talks/nabokov "Why Nabokov would use Org-Mode if he were writing today") (writing and then editing, even if it might not be Org). [cubing](https://emacsconf.org/2023/talks/cubing "Speedcubing in Emacs") can be something fun to transition to lunch, then. -- [parallel](https://emacsconf.org/2023/talks/parallel "Parallel Text Replacement: Does P = NP?") needs to go in the morning. Might be a general talk. -- checking with [web](https://emacsconf.org/2023/talks/web "Emacs saves the Web") and [hn](https://emacsconf.org/2023/talks/hn "The many ways to browse Hacker News from Emacs") if ~3pm Sunday afternoon (~7am local time) is okay with them. It would be nice to pair it with [hn](https://emacsconf.org/2023/talks/hn "The many ways to browse Hacker News from Emacs"), which is nice to pair with [mentor](https://emacsconf.org/2023/talks/mentor "Mentoring VS-Coders as an Emacsian (or How to show not tell people about the wonders of Emacs)"), but maybe I can swap it with [emms](https://emacsconf.org/2023/talks/emms "Emacs MultiMedia System (EMMS)") and [devel](https://emacsconf.org/2023/talks/devel "Emacs development updates") if needed. + - [parallel](https://emacsconf.org/2023/talks/parallel "Parallel Text Replacement: Does P = NP?") needs to go in the morning. Might be okay to include in the general talk. + - [poltys](https://emacsconf.org/2023/talks/poltys "The browser in a buffer") and [cubing](https://emacsconf.org/2023/talks/cubing "Speedcubing in Emacs") aren’t related to Hyperbole, but we need to fit them into the schedule somewhere. It would be nice to connect [poltys](https://emacsconf.org/2023/talks/poltys "The browser in a buffer") (talking to web browsers from Emacs) to [web](https://emacsconf.org/2023/talks/web "Emacs saves the Web") (doing web stuff in Emacs instead), but [poltys](https://emacsconf.org/2023/talks/poltys "The browser in a buffer") needs to be in the morning (which is pretty full) and [web](https://emacsconf.org/2023/talks/web "Emacs saves the Web") is in the afternoon because Yuchen is in Australia/Sydney. + - [cubing](https://emacsconf.org/2023/talks/cubing "Speedcubing in Emacs") can be something fun to transition to lunch, then. +- Sunday afternoon: community theme ([mentor](https://emacsconf.org/2023/talks/mentor "Mentoring VS-Coders as an Emacsian (or How to show not tell people about the wonders of Emacs)") to [sharing](https://emacsconf.org/2023/talks/sharing "Sharing Emacs is Caring Emacs: Emacs education and why I embraced video")), with an aside for [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 not, [web](https://emacsconf.org/2023/talks/web "Emacs saves the Web") could be good for a closing talk - encouraging people to use Emacs for more stuff. +- checking with [web](https://emacsconf.org/2023/talks/web "Emacs saves the Web") and [hn](https://emacsconf.org/2023/talks/hn "The many ways to browse Hacker News from Emacs") if ~3pm Sunday afternoon (~7am local time) is okay with them. It would be nice to pair it with [hn](https://emacsconf.org/2023/talks/hn "The many ways to browse Hacker News from Emacs"), which is nice to pair with [mentor](https://emacsconf.org/2023/talks/mentor "Mentoring VS-Coders as an Emacsian (or How to show not tell people about the wonders of Emacs)"), but maybe I can move it to Saturday afternoon. +- if the talks get cancelled, we can have an open meetup possibly with + breakout rooms - coordination notes: - TODO [repl](https://emacsconf.org/2023/talks/repl "REPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZ"), [eval](https://emacsconf.org/2023/talks/eval "Editor Integrated REPL Driven Development for all languages") - [hyperamp](https://emacsconf.org/2023/talks/hyperamp "Top 10 ways Hyperbole amps up Emacs"), [koutline](https://emacsconf.org/2023/talks/koutline "Using Koutline for stream of thought journaling"), and [test](https://emacsconf.org/2023/talks/test "What I learned by writing test cases for GNU Hyperbole") are all in touch because they work on Hyperbole together - + - [unentangling](https://emacsconf.org/2023/talks/unentangling "(Un)entangling projects and repos"), [taming](https://emacsconf.org/2023/talks/taming "Taming things with Org Mode")? @@ -531,10 +557,10 @@ Schedule notes: - - - - + + + + @@ -545,24 +571,24 @@ Schedule notes: - - - - + + + + - - - + + + - - - - + + + + @@ -574,41 +600,48 @@ Schedule notes: - - - + + + - - - + + + - - - - + + + + - - - + + + - - - - + + + + + + + + + + + - + @@ -653,7 +686,7 @@ Schedule notes: - + @@ -685,7 +718,7 @@ Schedule notes: - + @@ -699,7 +732,7 @@ Schedule notes: - + @@ -720,7 +753,7 @@ Schedule notes: - + @@ -770,6 +803,69 @@ Schedule notes:
2023-12-02 Sat 12:50-13:00evalEditor Integrated REPL Driven Development for all languagesMusa Al-hassy2023-12-02 Sat 12:50-13:10overlayImproving compiler diagnostics with OverlaysJeff Trull
2023-12-02 Sat 13:20-14:00replREPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZEduardo Ochs2023-12-02 Sat 13:30-13:40evalEditor Integrated REPL Driven Development for all languagesMusa Al-hassy
2023-12-02 Sat 13:50-14:10stenoProgramming at 200 wpmDaniel Alejandro TapiacollabCollaborative data processing and documenting using org-babelJonathan Hartman, Lukas C. Bossert
2023-12-02 Sat 14:10-14:30extendingGNU Emacs for electronics, note-taking, and as lightweight IDEAnand Tamariya2023-12-02 Sat 14:00-14:40replREPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZEduardo Ochs
2023-12-02 Sat 14:50-15:10emacsenThe Emacsen family, the design of an Emacs and the importance of LispFerminextendingGNU Emacs for electronics, note-taking, and as lightweight IDEAnand Tamariya
2023-12-02 Sat 15:00-15:20collabCollaborative data processing and documenting using org-babelJonathan Hartman, Lukas C. BossertrefOrg-Mode workflow: informal reference trackingChristopher Howard
2023-12-02 Sat 15:20-15:40woofWatch Over Our FoldersBastien Guerry2023-12-02 Sat 15:30-15:40unentangling(Un)entangling projects and reposAlexey Bochkarev
2023-12-02 Sat 15:30-15:50refOrg-Mode workflow: informal reference trackingChristopher HowardstenoProgramming at 200 wpmDaniel Alejandro Tapia
2023-12-02 Sat 16:00-16:10unentangling(Un)entangling projects and reposAlexey Bochkarev2023-12-02 Sat 15:50-16:10woofWatch Over Our FoldersBastien Guerry
2023-12-02 Sat 16:00-16:20emacsenThe Emacsen family, the design of an Emacs and the importance of LispFermin
2023-12-02 Sat 16:20-16:302023-12-02 Sat 16:30-16:40 devel Emacs development updates John Wiegley2023-12-03 Sun 10:15-10:25 parallel Parallel Text Replacement: Does P = NP?LovroLovro, Valentino Picotti
2023-12-03 Sun 12:50-13:022023-12-03 Sun 12:50-13:00 eat Eat and Eat powered Eshell, fast featureful terminal inside Emacs Akib Azmain Turja
2023-12-03 Sun 13:22-14:022023-12-03 Sun 13:20-14:00 hyperdrive hyperdrive.el: Peer-to-peer filesystem in Emacs Joseph Turner
2023-12-03 Sun 14:22-14:322023-12-03 Sun 14:20-14:30 mentor Mentoring VS-Coders as an Emacsian (or How to show not tell people about the wonders of Emacs) Jeremy Friesen
+ + +# E-mail templates + + + + +## Review + + +### Template + +Thanks for submitting your proposal! (ZZZ: feedback) We’re experimenting +with early acceptance this year, so we’ll wait a week in case the +other volunteers want to chime in regarding your talk. =) + + + +## Acceptance + + +### Function + + (defun emacsconf-mail-accept-talk (talk &optional template) + (interactive (list (emacsconf-complete-talk-info))) + (emacsconf-mail-prepare + (or template (emacsconf-mail-merge-get-template "acceptance")) + (plist-get talk :email) + (list + :title (plist-get talk :title) + :email (plist-get talk :email) + :time (plist-get talk :time) + :conf-name emacsconf-name + :speakers-short (plist-get talk :speakers-short) + :url (concat emacsconf-base-url (plist-get talk :url)) + :video-target-date emacsconf-video-target-date + :year emacsconf-year))) + +### Template + +Hi, ${speakers-short}! + +Looks like all systems are a go for your talk. =) Thanks for proposing +it! Your talk page is now at ${url} . Please feel free to update it or +e-mail us if you’d like help with any changes. + +If you want to get started on your talk early, we have some +instructions at that might help. +We strongly encourage speakers to prepare a talk video by +${video-target-date} in order to reduce technical risks and make +things flow more smoothly. Plus, we might be able to get it captioned +by volunteers, just like the talks last year. We’ll save ${time} minutes +for your talk, not including time for Q&A. Don’t sweat it if +you’re a few minutes over or under. If it looks like a much shorter or +longer talk once you start getting into it, let us know and we might +be able to adjust. + +I’ll follow up with the specific schedule for your talk once things +settle down. In the meantime, please let us know if you have any +questions or if there’s anything we can do to help out! + +Sacha + # Archive -- cgit v1.2.3