diff options
| -rw-r--r-- | 2024/organizers-notebook.md | 28 | ||||
| -rw-r--r-- | 2024/organizers-notebook/index.org | 20 |
2 files changed, 34 insertions, 14 deletions
diff --git a/2024/organizers-notebook.md b/2024/organizers-notebook.md index a35d71db..09250cf0 100644 --- a/2024/organizers-notebook.md +++ b/2024/organizers-notebook.md @@ -15,7 +15,7 @@ You might also like the [general organizers' notebook](/organizers-notebook) and - [Phases](#phases) - [Draft CFP](#cfp) - [Draft schedule](#draft-schedule) -- [Support code](#orge386c8a) +- [Support code](#org37b28d4) <a id="timeline"></a> @@ -224,14 +224,24 @@ Notes: - General approach: - I’ve mostly tried to alternate IRC/pad Q&A with live Q&A. - 1.5 tracks keeps things faster-paced than the 2-track option. - - Sunday morning last year had some packet loss issues at around 9:30, so we’ll start with some talks that don’t have BBB Q&A. -- [transducers](https://emacsconf.org/2024/talks/transducers "Transducers: finally, ergonomic data processing for Emacs!") can only be on Sunday afternoon at 4pm -- [pgmacs](https://emacsconf.org/2024/talks/pgmacs "PGmacs: browsing and editing PostgreSQL databases from Emacs"), [regex](https://emacsconf.org/2024/talks/regex "Emacs regex compilation and future directions for expressive pattern matching"), and [transducers](https://emacsconf.org/2024/talks/transducers "Transducers: finally, ergonomic data processing for Emacs!") are all development-oriented, but are on the general track for scheduling purposes. -- [gypsum](https://emacsconf.org/2024/talks/gypsum "Gypsum: my clone of Emacs and ELisp written in Scheme"), [rust](https://emacsconf.org/2024/talks/rust "An experimental Emacs core in Rust"), [julia](https://emacsconf.org/2024/talks/julia "Exploring shared philosophies in Julia and Emacs"), [guile](https://emacsconf.org/2024/talks/guile "Beguiling Emacs: Guile-Emacs relaunched!"), and [mcclim](https://emacsconf.org/2024/talks/mcclim "Elisp and McCLIM") are about other projects -- I’ve separated [hyperbole](https://emacsconf.org/2024/talks/hyperbole "Fun things with GNU Hyperbole") and [hywiki](https://emacsconf.org/2024/talks/hywiki "HyWiki: Fast, hyperlinked note-taking with no markup required") by another talk with non-BBB Q&A so that people who are interested in that can attend the live Q&A for both without worrying about missing things. - - -<a id="orge386c8a"></a> +- Sat: + - Gen track: + - [papers](https://emacsconf.org/2024/talks/papers "Writing academic papers in Org-Roam"), [project](https://emacsconf.org/2024/talks/project "Managing writing project metadata with org-mode"), [org-teach](https://emacsconf.org/2024/talks/org-teach "org-teach: a minor mode for writing course materials in Emacs"), [hyperdrive](https://emacsconf.org/2024/talks/hyperdrive "New in hyperdrive.el: org-transclusion, easy installation, and more!"), [color](https://emacsconf.org/2024/talks/color "Colour your Emacs with ease") should be pretty general + - [color](https://emacsconf.org/2024/talks/color "Colour your Emacs with ease") and [theme](https://emacsconf.org/2024/talks/theme "My journey of finding and creating the “perfect” Emacs theme") are both theme-related. [color](https://emacsconf.org/2024/talks/color "Colour your Emacs with ease") needs to be in the morning and [theme](https://emacsconf.org/2024/talks/theme "My journey of finding and creating the “perfect” Emacs theme") needs to be in the afternoon, so I put them on either side of the lunch break. + - Other afternoon talks: [water](https://emacsconf.org/2024/talks/water "Watering my (digital) plant with Emacs timers") and [shell](https://emacsconf.org/2024/talks/shell "Emacs as a shell") are by the same speaker. [casual](https://emacsconf.org/2024/talks/casual "Re-imagining the Emacs user experience with Casual Suite"), [flp](https://emacsconf.org/2024/talks/flp "The Free Life Planner: Empowering lives with Emacs-based AI"), and [writing](https://emacsconf.org/2024/talks/writing "Emacs Writing Studio") will probably be good for a general audience. + - I put [emacs30](https://emacsconf.org/2024/talks/emacs30 "Emacs 30 Highlights") at the end of Saturday to act sort of as a keynote. + - Dev track: + - [gypsum](https://emacsconf.org/2024/talks/gypsum "Gypsum: my clone of Emacs and ELisp written in Scheme"), [rust](https://emacsconf.org/2024/talks/rust "An experimental Emacs core in Rust"), [julia](https://emacsconf.org/2024/talks/julia "Exploring shared philosophies in Julia and Emacs"), [guile](https://emacsconf.org/2024/talks/guile "Beguiling Emacs: Guile-Emacs relaunched!"), and [mcclim](https://emacsconf.org/2024/talks/mcclim "Elisp and McCLIM") are about other projects + - [graph](https://emacsconf.org/2024/talks/graph "Graph mode: a major mode to create, edit and display discrete element graphs"), [p-search](https://emacsconf.org/2024/talks/p-search "p-search: a local search engine in Emacs"), [secrets](https://emacsconf.org/2024/talks/secrets "Committing secrets with git using sops-mode"), and [repro](https://emacsconf.org/2024/talks/repro "Reproducibly building Emacs: “Hey your checksum is the same as mine!”") will probably be more dev-focused +- Sun: + - Sunday morning last year had some packet loss issues at around 9:30, so we’ll start with some talks that don’t have BBB Q&A: [students](https://emacsconf.org/2024/talks/students "An example of a cohesive student workflow in Emacs"), [links](https://emacsconf.org/2024/talks/links "Unlocking linked data: replacing specialized apps with an Org-based semantic wiki"), [regex](https://emacsconf.org/2024/talks/regex "Emacs regex compilation and future directions for expressive pattern matching") + - [blee](https://emacsconf.org/2024/talks/blee "About Blee: towards an integrated Emacs environment for enveloping our own autonomy directed digital ecosystem") and [language](https://emacsconf.org/2024/talks/language "Immersive language learning with Emacs") are probably general-audience + - [pgmacs](https://emacsconf.org/2024/talks/pgmacs "PGmacs: browsing and editing PostgreSQL databases from Emacs"), [regex](https://emacsconf.org/2024/talks/regex "Emacs regex compilation and future directions for expressive pattern matching"), and [transducers](https://emacsconf.org/2024/talks/transducers "Transducers: finally, ergonomic data processing for Emacs!") are all development-oriented, but are on the general track for scheduling purposes. [transducers](https://emacsconf.org/2024/talks/transducers "Transducers: finally, ergonomic data processing for Emacs!") can only be on Sunday afternoon at 4pm because of availability. + - I’ve separated [hyperbole](https://emacsconf.org/2024/talks/hyperbole "Fun things with GNU Hyperbole") and [hywiki](https://emacsconf.org/2024/talks/hywiki "HyWiki: Fast, hyperlinked note-taking with no markup required") by another talk with non-BBB Q&A so that people who are interested in that can attend the live Q&A for both without worrying about missing things. + - [learning](https://emacsconf.org/2024/talks/learning "Survival of the skillest: Thriving in the learning jungle"), [sharing](https://emacsconf.org/2024/talks/sharing "So you want to be an Emacs-fluencer?"), [literate](https://emacsconf.org/2024/talks/literate "Literate programming for the 21st Century") will probably be good for a general audience + + +<a id="org37b28d4"></a> # Support code diff --git a/2024/organizers-notebook/index.org b/2024/organizers-notebook/index.org index c6f71b3b..c64b926f 100644 --- a/2024/organizers-notebook/index.org +++ b/2024/organizers-notebook/index.org @@ -257,11 +257,21 @@ Notes: - General approach: - I've mostly tried to alternate IRC/pad Q&A with live Q&A. - 1.5 tracks keeps things faster-paced than the 2-track option. - - Sunday morning last year had some packet loss issues at around 9:30, so we'll start with some talks that don't have BBB Q&A. -- [[emacsconf:transducers]] can only be on Sunday afternoon at 4pm -- emacsconf:pgmacs, emacsconf:regex, and emacsconf:transducers are all development-oriented, but are on the general track for scheduling purposes. -- emacsconf:gypsum, emacsconf:rust, emacsconf:julia, emacsconf:guile, and emacsconf:mcclim are about other projects -- I've separated emacsconf:hyperbole and emacsconf:hywiki by another talk with non-BBB Q&A so that people who are interested in that can attend the live Q&A for both without worrying about missing things. +- Sat: + - Gen track: + - emacsconf:papers, emacsconf:project, emacsconf:org-teach, emacsconf:hyperdrive, emacsconf:color should be pretty general + - emacsconf:color and emacsconf:theme are both theme-related. emacsconf:color needs to be in the morning and emacsconf:theme needs to be in the afternoon, so I put them on either side of the lunch break. + - Other afternoon talks: emacsconf:water and emacsconf:shell are by the same speaker. emacsconf:casual, emacsconf:flp, and emacsconf:writing will probably be good for a general audience. + - I put emacsconf:emacs30 at the end of Saturday to act sort of as a keynote. + - Dev track: + - emacsconf:gypsum, emacsconf:rust, emacsconf:julia, emacsconf:guile, and emacsconf:mcclim are about other projects + - emacsconf:graph, emacsconf:p-search, emacsconf:secrets, and emacsconf:repro will probably be more dev-focused +- Sun: + - Sunday morning last year had some packet loss issues at around 9:30, so we'll start with some talks that don't have BBB Q&A: emacsconf:students, emacsconf:links, emacsconf:regex + - emacsconf:blee and emacsconf:language are probably general-audience + - emacsconf:pgmacs, emacsconf:regex, and emacsconf:transducers are all development-oriented, but are on the general track for scheduling purposes. [[emacsconf:transducers]] can only be on Sunday afternoon at 4pm because of availability. + - I've separated emacsconf:hyperbole and emacsconf:hywiki by another talk with non-BBB Q&A so that people who are interested in that can attend the live Q&A for both without worrying about missing things. + - emacsconf:learning, emacsconf:sharing, emacsconf:literate will probably be good for a general audience *** Option: 2 tracks :noexport: :PROPERTIES: |