diff options
Diffstat (limited to '')
47 files changed, 1117 insertions, 7 deletions
diff --git a/2024/draft-schedule.md b/2024/draft-schedule.md new file mode 100644 index 00000000..f857dfad --- /dev/null +++ b/2024/draft-schedule.md @@ -0,0 +1,3 @@ +[[!sidebar content=""]] + +This is a *DRAFT* schedule. diff --git a/2024/info/learning-after.md b/2024/info/learning-after.md new file mode 100644 index 00000000..01237ebd --- /dev/null +++ b/2024/info/learning-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [emacsconf-org-private@gnu.org](mailto:emacsconf-org-private@gnu.org?subject=Comment%20for%20EmacsConf%202023%20learning%3A%20Survival%20of%20the%20Skillest%3A%20Thriving%20in%20the%20Learning%20Jungle) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/learning-before.md b/2024/info/learning-before.md new file mode 100644 index 00000000..91a3dc1d --- /dev/null +++ b/2024/info/learning-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 20-min talk; Q&A: Etherpad +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/learning-nav.md b/2024/info/learning-nav.md new file mode 100644 index 00000000..f2d8e6c7 --- /dev/null +++ b/2024/info/learning-nav.md @@ -0,0 +1,7 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/p-search">p-search: a local search engine in Emacs</a> +Next by track: <a href="/2024/talks/sharing">So You Want To Be An Emacs-Fluencer?</a> +Track: <span class="sched-track General">General</span> +</div> diff --git a/2024/info/literate-after.md b/2024/info/literate-after.md new file mode 100644 index 00000000..17e8fe28 --- /dev/null +++ b/2024/info/literate-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [emacsconf-org-private@gnu.org](mailto:emacsconf-org-private@gnu.org?subject=Comment%20for%20EmacsConf%202023%20literate%3A%20Literate%20Programming%20for%20the%2021st%20Century) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/literate-before.md b/2024/info/literate-before.md new file mode 100644 index 00000000..14c43a73 --- /dev/null +++ b/2024/info/literate-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 20-min talk; Q&A: BigBlueButton conference room +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/literate-nav.md b/2024/info/literate-nav.md new file mode 100644 index 00000000..1ae38f6a --- /dev/null +++ b/2024/info/literate-nav.md @@ -0,0 +1,7 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/rust">An Experimental Emacs Core in Rust</a> +Next by track: <a href="/2024/talks/pgmacs">PGmacs: browsing and editing PostgreSQL databases from Emacs</a> +Track: <span class="sched-track Development">Development</span> +</div> diff --git a/2024/info/org-teach-after.md b/2024/info/org-teach-after.md new file mode 100644 index 00000000..ef8639dc --- /dev/null +++ b/2024/info/org-teach-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [james@endres-howell.org](mailto:james@endres-howell.org?subject=Comment%20for%20EmacsConf%202023%20org-teach%3A%20org-teach%3A%20a%20minor%20mode%20for%20writing%20course%20materials%20in%20Emacs) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/org-teach-before.md b/2024/info/org-teach-before.md new file mode 100644 index 00000000..14c43a73 --- /dev/null +++ b/2024/info/org-teach-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 20-min talk; Q&A: BigBlueButton conference room +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/org-teach-nav.md b/2024/info/org-teach-nav.md new file mode 100644 index 00000000..f9d583d2 --- /dev/null +++ b/2024/info/org-teach-nav.md @@ -0,0 +1,7 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/water">Watering my (digital) plant with Emacs timers</a> +Next by track: <a href="/2024/talks/rust">An Experimental Emacs Core in Rust</a> +Track: <span class="sched-track General">General</span> +</div> diff --git a/2024/info/p-search-after.md b/2024/info/p-search-after.md new file mode 100644 index 00000000..04999565 --- /dev/null +++ b/2024/info/p-search-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [zacromero@posteo.com](mailto:zacromero@posteo.com?subject=Comment%20for%20EmacsConf%202023%20p-search%3A%20p-search%3A%20a%20local%20search%20engine%20in%20Emacs) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/p-search-before.md b/2024/info/p-search-before.md new file mode 100644 index 00000000..14c43a73 --- /dev/null +++ b/2024/info/p-search-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 20-min talk; Q&A: BigBlueButton conference room +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/p-search-nav.md b/2024/info/p-search-nav.md new file mode 100644 index 00000000..dbb1835e --- /dev/null +++ b/2024/info/p-search-nav.md @@ -0,0 +1,7 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/writing">Emacs Writing Studio</a> +Next by track: <a href="/2024/talks/learning">Survival of the Skillest: Thriving in the Learning Jungle</a> +Track: <span class="sched-track General">General</span> +</div> diff --git a/2024/info/pgmacs-after.md b/2024/info/pgmacs-after.md new file mode 100644 index 00000000..bd63ed38 --- /dev/null +++ b/2024/info/pgmacs-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [eric.marsden@risk-engineering.org](mailto:eric.marsden@risk-engineering.org?subject=Comment%20for%20EmacsConf%202023%20pgmacs%3A%20PGmacs%3A%20browsing%20and%20editing%20PostgreSQL%20databases%20from%20Emacs) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/pgmacs-before.md b/2024/info/pgmacs-before.md new file mode 100644 index 00000000..bbac2748 --- /dev/null +++ b/2024/info/pgmacs-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 10-min talk; Q&A: BigBlueButton conference room +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/pgmacs-nav.md b/2024/info/pgmacs-nav.md new file mode 100644 index 00000000..9203ac05 --- /dev/null +++ b/2024/info/pgmacs-nav.md @@ -0,0 +1,6 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/literate">Literate Programming for the 21st Century</a> +Track: <span class="sched-track Development">Development</span> +</div> diff --git a/2024/info/project-after.md b/2024/info/project-after.md new file mode 100644 index 00000000..32ab8822 --- /dev/null +++ b/2024/info/project-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [blaine-mooers@ouhsc.edu](mailto:blaine-mooers@ouhsc.edu?subject=Comment%20for%20EmacsConf%202023%20project%3A%20Managing%20writing%20project%20metadata%20with%20org-mode) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/project-before.md b/2024/info/project-before.md new file mode 100644 index 00000000..14c43a73 --- /dev/null +++ b/2024/info/project-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 20-min talk; Q&A: BigBlueButton conference room +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/project-nav.md b/2024/info/project-nav.md new file mode 100644 index 00000000..472d4768 --- /dev/null +++ b/2024/info/project-nav.md @@ -0,0 +1,6 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Next by track: <a href="/2024/talks/writing">Emacs Writing Studio</a> +Track: <span class="sched-track General">General</span> +</div> diff --git a/2024/info/rust-after.md b/2024/info/rust-after.md new file mode 100644 index 00000000..77ee042b --- /dev/null +++ b/2024/info/rust-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [troy@troyhinckley.com](mailto:troy@troyhinckley.com?subject=Comment%20for%20EmacsConf%202023%20rust%3A%20An%20Experimental%20Emacs%20Core%20in%20Rust) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/rust-before.md b/2024/info/rust-before.md new file mode 100644 index 00000000..14c43a73 --- /dev/null +++ b/2024/info/rust-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 20-min talk; Q&A: BigBlueButton conference room +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/rust-nav.md b/2024/info/rust-nav.md new file mode 100644 index 00000000..c946350e --- /dev/null +++ b/2024/info/rust-nav.md @@ -0,0 +1,7 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/org-teach">org-teach: a minor mode for writing course materials in Emacs</a> +Next by track: <a href="/2024/talks/literate">Literate Programming for the 21st Century</a> +Track: <span class="sched-track Development">Development</span> +</div> diff --git a/2024/info/sharing-after.md b/2024/info/sharing-after.md new file mode 100644 index 00000000..2ee4e080 --- /dev/null +++ b/2024/info/sharing-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [gopardaniel@gmail.com](mailto:gopardaniel@gmail.com?subject=Comment%20for%20EmacsConf%202023%20sharing%3A%20So%20You%20Want%20To%20Be%20An%20Emacs-Fluencer%3F) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/sharing-before.md b/2024/info/sharing-before.md new file mode 100644 index 00000000..91a3dc1d --- /dev/null +++ b/2024/info/sharing-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 20-min talk; Q&A: Etherpad +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/sharing-nav.md b/2024/info/sharing-nav.md new file mode 100644 index 00000000..7271c984 --- /dev/null +++ b/2024/info/sharing-nav.md @@ -0,0 +1,7 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/learning">Survival of the Skillest: Thriving in the Learning Jungle</a> +Next by track: <a href="/2024/talks/water">Watering my (digital) plant with Emacs timers</a> +Track: <span class="sched-track General">General</span> +</div> diff --git a/2024/info/water-after.md b/2024/info/water-after.md new file mode 100644 index 00000000..6a908d6a --- /dev/null +++ b/2024/info/water-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [christopher@librehacker.com](mailto:christopher@librehacker.com?subject=Comment%20for%20EmacsConf%202023%20water%3A%20Watering%20my%20%28digital%29%20plant%20with%20Emacs%20timers) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/water-before.md b/2024/info/water-before.md new file mode 100644 index 00000000..f39383a9 --- /dev/null +++ b/2024/info/water-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 10-min talk; Q&A: IRC +Status: TO_CONFIRM + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/water-nav.md b/2024/info/water-nav.md new file mode 100644 index 00000000..78c8e0a2 --- /dev/null +++ b/2024/info/water-nav.md @@ -0,0 +1,7 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/sharing">So You Want To Be An Emacs-Fluencer?</a> +Next by track: <a href="/2024/talks/org-teach">org-teach: a minor mode for writing course materials in Emacs</a> +Track: <span class="sched-track General">General</span> +</div> diff --git a/2024/info/writing-after.md b/2024/info/writing-after.md new file mode 100644 index 00000000..e9e4236b --- /dev/null +++ b/2024/info/writing-after.md @@ -0,0 +1,10 @@ +<!-- Automatically generated by emacsconf-publish-after-page --> + + +Questions or comments? Please e-mail [peter@prevos.net](mailto:peter@prevos.net?subject=Comment%20for%20EmacsConf%202023%20writing%3A%20Emacs%20Writing%20Studio) + +---- +Got an idea for an EmacsConf talk or session? We'd love to hear from you! Check out the [[Call for Participation|/2024/cfp]] for details. + + +<!-- End of emacsconf-publish-after-page --> diff --git a/2024/info/writing-before.md b/2024/info/writing-before.md new file mode 100644 index 00000000..4f4824ed --- /dev/null +++ b/2024/info/writing-before.md @@ -0,0 +1,12 @@ +<!-- Automatically generated by emacsconf-publish-before-page --> +[[!toc ]] +Format: 10-min talk; Q&A: ask questions via Etherpad/IRC; we'll e-mail the speaker and post answers on this wiki page after the conference +Status: Waiting for video from speaker + + + + + + +# Description +<!-- End of emacsconf-publish-before-page -->
\ No newline at end of file diff --git a/2024/info/writing-nav.md b/2024/info/writing-nav.md new file mode 100644 index 00000000..17bca7ec --- /dev/null +++ b/2024/info/writing-nav.md @@ -0,0 +1,7 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous by track: <a href="/2024/talks/project">Managing writing project metadata with org-mode</a> +Next by track: <a href="/2024/talks/p-search">p-search: a local search engine in Emacs</a> +Track: <span class="sched-track General">General</span> +</div> diff --git a/2024/organizers-notebook.md b/2024/organizers-notebook.md index 6df520e1..5e2c3bfe 100644 --- a/2024/organizers-notebook.md +++ b/2024/organizers-notebook.md @@ -12,7 +12,7 @@ You might also like the [general organizers' notebook](/organizers-notebook) and - [About this document](#about-this-doc) - [Communications plan](#comms) - [Good/better/best](#good-better-best) -- [Phases](#orge09db02) +- [Phases](#phases) - [Draft CFP](#cfp) @@ -33,14 +33,14 @@ You might also like the [general organizers' notebook](/organizers-notebook) and <tbody> <tr> <td class="org-left">CFP</td> -<td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2024-06-28 Fri]</span></span></td> +<td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2024-06-30 Sun]</span></span></td> <td class="org-right"> </td> </tr> <tr> <td class="org-left">CFP deadline</td> <td class="org-left"><span class="timestamp-wrapper"><span class="timestamp">[2024-09-20 Fri]</span></span></td> -<td class="org-right">84</td> +<td class="org-right">82</td> </tr> <tr> @@ -180,7 +180,7 @@ interests you! </table> -<a id="orge09db02"></a> +<a id="phases"></a> # Phases @@ -198,7 +198,7 @@ interests you! - [X] volunteer page -#### TODO Check with other organizers +#### DONE Check with other organizers #### TODO Post CFP in the usual places diff --git a/2024/organizers-notebook/index.org b/2024/organizers-notebook/index.org index a8ee386a..74d15746 100644 --- a/2024/organizers-notebook/index.org +++ b/2024/organizers-notebook/index.org @@ -16,6 +16,8 @@ This file is automatically exported from [/2024/organizers-notebook/index.org](/ You might also like the [general organizers' notebook](/organizers-notebook) and [the organizers' notebook from 2023](/2023/organizers-notebook). #+end_export + + #+NAME: list-headings #+begin_src emacs-lisp :results value replace :exports results :eval never-export :var heading="Help wanted" :var match="helpwanted" (emacsconf-surround @@ -52,14 +54,17 @@ You might also like the [general organizers' notebook](/organizers-notebook) and #+TOC: headlines 2 +* COMMENT Shortcuts + +[[file:~/proj/emacsconf/wiki/organizers-notebook/index.org][Common notebook]] * Timeline :PROPERTIES: :CUSTOM_ID: timeline :END: -| CFP | [2024-06-28 Fri] | | -| CFP deadline | [2024-09-20 Fri] | 84 | +| CFP | [2024-06-30 Sun] | | +| CFP deadline | [2024-09-20 Fri] | 82 | | Speaker notifications | [2024-09-27 Fri] | | | *Publish schedule* | [2024-10-25 Fri] | | | Video submission deadline | [2024-11-08 Fri] | 49 | diff --git a/2024/prepare.md b/2024/prepare.md new file mode 100644 index 00000000..4b20d5ba --- /dev/null +++ b/2024/prepare.md @@ -0,0 +1,311 @@ +[[!meta title="Preparing your talk"]] +[[!meta copyright="Copyright © 2019, 2020 Amin Bandali; 2021, 2022 Amin Bandali, Sacha Chua, Leo Vivier; 2023, 2024 Sacha Chua"]] + +This page contains tips for preparing your talk. (Target date: on or before +**November 8, 2024**) If you have any questions, concerns, or suggestions +please feel free to write to one our organizational mailing lists: the +public <emacsconf-org@gnu.org> list, or the private +<emacsconf-org-private@gnu.org> list, depending on the nature of the +matter you would like to discuss. + +Note: being part of a wiki, this page is subject to change (including +by you!); so please check back every now and again for any changes and +updates. + +We'll bring up the web-based upload service at some point. Let us know +at <emacsconf-org-private@gnu.org> if you're already ready to go! +<!--[[Already done? Upload your video and other files|upload]]--> + +## Guidelines for conduct + +Please review our [[guidelines for conduct|conduct]] when preparing your +talk to make sure we’re all on the same page and strive to make the +event a great experience for all. If you’re not sure whether your talk +or presentation style meets the guidelines laid out in the guidelines +for conduct, we’d be happy to help. You can email Sacha Chua at +<sacha@sachachua.com> to chat more about this. + +## Recording your talk + +To help EmacsConf 2024 run smoothly, please prerecord your talk, and +plan to upload your video(s) by **November 8, 2024** to allow us enough time +to do any needed processing (e.g. format or codec conversion) in +preparation for the event. Please consider submitting a prerecording as +early as possible so that we can see if volunteers can caption your +video to make it more accessible and searchable. + +To make it easier for people to orient themselves +when listening to lots of EmacsConf videos in the +playlist, you may want to start your video with +something along the lines of: + +"Hi! I’m ${NAME} and I’ll be talking about ${TOPIC}." + +We'll also try to record a brief introduction for +your talk with enough time for you to review the +pronunciation. + +### Appearance + +The talks will be broadcast with a resolution of **1280x720px** +(720p), so it may help to switch to that size before you record. +Please make sure your text will be easy to read. +[You can change the font-size in your Emacs.](https://www.emacswiki.org/emacs/SetFonts#h5o-6) +(Maybe `M-x customize-face default` and set the height to 150 or more, depending on your resolution?) If you +are capturing a single window, you can also resize it before you +record. + +We recommend using **dark text on a light background** for your +recording, as this can be easier to see especially for people who are +visually impaired. Themes with more contrast are easier to read than +low-contrast ones. If you use a dark theme with your Emacs, you can +change to a lighter one with `M-x customize-theme` (look for those +with a `-light` suffix). The `modus-themes-load-operandi` command from +the `modus-themes` package can be a good option. + +### Audio quality + +Audio quality can go a long way in making your talk enjoyable to +watch. Consider the background noise in the room that you are using to +record, and see if you can temporarily turn off things for your +recording. + +You can help us try to denoise the audio by +providing a recording of at least **5 seconds of +quiet** in the same room in which you plan to do +your main recording. You can listen to it to see +how quiet things are, and figure out if there are +other things you can turn off such as fans or +other computers. We can try to use the noise +profile from that recording to reduce the noise in +your presentation. + +If you have an **external microphone or a +headset**, try recording the audio through that so +that you can reduce the sound of the computer +itself. If you have a smartphone, that might also +be a good way to record audio that you can then +combine with your video afterwards. + +Many speakers prefer to record and edit the audio until they're happy +with how it fits in the time, and then add the slides or videos +afterwards. It might be easier than trying to do both the audio and +the video in one go. + +### Tools + +You can use your favorite video recording tool. If you don't have one yet, you can try +any of the following pieces of free software, depending on your needs: + +- [OBS](//obsproject.com) +- [SimpleScreenRecorder](//www.maartenbaert.be/simplescreenrecorder/) +- [vokoscreenNG](//linuxecke.volkoh.de/vokoscreen/vokoscreen.html) +- [peek](//github.com/phw/peek) +- [ffmpeg](//trac.ffmpeg.org/wiki/Capture/Desktop) + +If you decide to use OBS, please make sure to verify the window-capture +options. Most notably, there is a “Swap red and blue” option that is +necessary for some setups, and it's easy to miss it. + +You might find the following free software programs useful for editing +your video recordings: + +- [Kdenlive](//kdenlive.org/en/) +- [Blender](//www.blender.org) +- [Pitivi](http://www.pitivi.org) + +Per GNU Project’s [Guide to +Formats](//audio-video.gnu.org/docs/formatguide.html), we prefer to +receive prerecorded videos in formats unencumbered by software patents, +such as `video/webm` ([WebM](https://www.webmproject.org/)-encoded video +files, with `.webm` file extension) and `video/ogg` (video files encoded +with the Theora video codec, encapsulated in an Ogg transport layer, +with `.ogg` or `.ogv` file extension). However, if for one reason or +another you are unable to send us your prerecorded video in one of the +above formats, you may submit them in other common formats, like MPEG-4 +(`.mp4`), and we will convert them to our preferred formats on your +behalf. + +*Prepare recorded video in 720p (1280px by 720px) or higher, in the +WebM format if possible.* + + +# Compression + +If you would like to compress your video before uploading, the following shell script may be useful: + + Q=32 + CPU=8 + ffmpeg -y -i "$1" -c:v libvpx-vp9 -b:v 0 -crf $Q -an -row-mt 1 -tile-columns 2 -tile-rows 2 -cpu-used $CPU -g 240 -pass 1 -f webm -threads $CPU /dev/null && + ffmpeg -y -i "$1" -c:v libvpx-vp9 -b:v 0 -crf $Q -c:a libopus -row-mt 1 -tile-columns 2 -tile-rows 2 -cpu-used $CPU -pass 2 -g 240 -threads $CPU "$2" + +If you put it in a file called `compress-video.sh`, you can execute it +from the command line with something like `sh compress-video.sh +input-file.webm output-file.webm`. It will compress the file in two +passes. During the first pass, the frame count will increase, but the +speed will be 0. After the first pass, it will display proper progress +information. + +<a name="tech-check"></a> +# Tech-check + +We ask that speakers who plan to participate in live Q&A sessions schedule +a short tech-check in the weeks leading to the conference; this is to ensure +that you can perform all the common tasks you’d need such as sharing your +screen or toggling your microphone. + +We use BigBlueButton for our video-conferencing needs, and a quick way +to familiarize yourself with it is to run it in a test room: +<https://test.bigbluebutton.org/> Tiling window managers and +multi-monitor setups can be a little tricky, so it's good to figure +out a setup that works for you. If there are things you'd like to +confirm by having another person in the meeting, such as audio +quality, please feel free to get in touch with us and we’ll sort +things out together. + +Thank you so much for helping with EmacsConf 2024! + +# Frequently-asked questions + +## Can I present live? + +We’d prefer that all talks have prerecorded +videos. + +- It's a lot less stressful for both +presenters and organizers. +- Videos can be immediately available for playback once your session starts. +- We can work on getting the video captioned for better accessibility. + +If you really need or want to present live, +though, let us know and we'll figure that out. + +There will also be time for live questions and +answers, so if you can record a short video +covering your main points, you might be able to go +into more detail in live Q&A. + +## My presentation is over/under the time I proposed. Do I need to stress out about it? + +No need to stress out about it. If it's a little +over or under, we'll adjust the Q&A accordingly. + +If you find that your talk is much shorter than +anticipated, let us know and we can adjust the +schedule. + +If there's so much you want to talk about and you +can't decide what to squeeze in, maybe you can +think of your video as a short teaser that can get +people interested and point them to where they can +find out more. You can email +<emacsconf-submit@gnu.org> links and other notes +to add to the wiki page for your talk. If you’d +like to record a longer video *in addition* to the +short one for the main conference, please feel +free to send us that too. + +Additionally, even though it is tempting, please refrain from speaking +super quickly or fast-forwarding your recording to make it fit within +the format. Trimming out the silences and the filler words can help +sometimes, but a better solution for you might be to condense your +talk to the essentials, then write, record, and edit your voice-over. +Once you've figured out how to use the time, you can record your video +to go along with it. Don't sweat being a few minutes over or under, +that's cool. + +Feel free to send some questions for the host to ask you during the +Q&A so that you can address extra points that didn't make it into the +video. + +## What if there are lots of great questions during Q&A and it's already time for the next talk? + +The stream will move on to the next talk, but people can join the +BigBlueButton meeting room and keep chatting with you for as long as +you want to keep going. You can also continue answering questions on +the collaborative pad or IRC, and we’ll copy questions and answers +onto the wiki page afterwards so that you can answer them in your own +time after the event. + +## Do I need to follow some visual guidelines for the presentation? + +- Dark text on a light background is more legible than the opposite + (especially for people who are visually impaired), and more contrast + is better than a low-contrast theme. This stands for both your + slides and your Emacs theme. +- If you think your fonts might be too small in your slides or in Emacs, + they might very well be. [You can change the font-size in your + Emacs](https://www.emacswiki.org/emacs/SetFonts#h5o-6), but you can + also play with the size of the captured window during your recording. +- Try to minimize the screen-flashes that occur when you switch between + windows, especially if their themes do not cohere (light-to-dark and + the reverse). If you can edit your recording, fades and other + transitions are a neat solution to this problem. + +## How do I show my keystrokes on screen? + +In Emacs, you can use +[interaction-log.el](https://github.com/michael-heerdegen/interaction-log.el) +(in MELPA) to display the keystrokes and the commands they run in a separate +buffer. For a system-wide solution, you can look into +[screenkey](https://gitlab.com/screenkey/screenkey). + +## I’m not used to talking to myself. Can I present the talk to someone? + +We might be able to help you record your talk using the BigBlueButton +web conferencing system before the conference. Please email +<emacsconf-submit@gnu.org> with some times that might work for you and +we’ll see if a volunteer can meet up with you to record it. + +## Can I see the other proposed talks? + +Once we’ve emailed the speakers about their acceptance, we’ll put +up the talk wiki pages. That way, you can see what else is going on +in the conference and maybe coordinate with other speakers in order to +minimize overlap and maximize awesomeness. + +## Do you have an Org TODO I can just copy into my agenda file? + +Sure, modify this as needed: + +``` +* TODO Record presentation for EmacsConf: Title goes here +DEADLINE: <2024-11-08 Fri> + +- 1280x720px +- large text; ideally dark text on a light background +- minimize background noise + - try to use an external microphone if possible (ex: backup audio recording with phone) + - consider recording ~5 seconds of silence in the room you're planning to record in + +https://emacsconf.org/2024/prepare - tips and instructions + +Questions: +- public: mailto:emacsconf-org@gnu.org +- private: mailto:emacsconf-org-private@gnu.org + +Note: 2024-11-08 is a target date and we'd love to +get your video by then. It's not a *deadline* +deadline, so don't stress out if life happens. +Just let us know! + +Thanks for sharing what you're learning! +``` + +## More questions? + +Please email <emacsconf-submit@gnu.org>. We’d love to hear from you. + +Thanks for contributing to EmacsConf 2024! + +<!-- <a name="tech-checklist"></a> --> +<!-- #### Tech checklist --> + +<!-- - Can you speak and be heard? Is there echo? --> +<!-- - Can you hear the organizer? --> +<!-- - Can you share your screen? Is the screen readable? --> +<!-- - If you plan to show your keystrokes, is that display visible? --> +<!-- - If you want to share your webcam (optional), can you enable it? Is it visible? Will there likely be distractions in the background? --> +<!-- - Can you view the collaborative pad? Will you be comfortable reviewing questions on your own (perhaps by keeping it open beside your shared window), or will you need a volunteer to relay questions to you? --> +<!-- - Can you share contact information (ex: phone number) so that we can get in touch with you in case of technical issues or scheduling changes? --> +<!-- - Do you need help finding your way around IRC so that you can check into `#emacsconf-org`? What is your IRC nickname? --> diff --git a/2024/schedule-details.md b/2024/schedule-details.md new file mode 100644 index 00000000..d529fde3 --- /dev/null +++ b/2024/schedule-details.md @@ -0,0 +1,17 @@ +Jump to: <a href="#dev">Development</a> + +<h1 id="gen" class="sched-track General">General (7 talks)</h1> +[[!template id=sched title="""Managing writing project metadata with org-mode""" url="""/2024/talks/project""" speakers="""Blaine Mooers""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""project""" note=""""""]] +[[!template id=sched title="""Emacs Writing Studio""" url="""/2024/talks/writing""" speakers="""Peter Prevos""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""writing""" note=""""""]] +[[!template id=sched title="""p-search: a local search engine in Emacs""" url="""/2024/talks/p-search""" speakers="""Zac Romero""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""p-search""" note=""""""]] +[[!template id=sched title="""Survival of the Skillest: Thriving in the Learning Jungle""" url="""/2024/talks/learning""" speakers="""Bala Ramadurai""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""learning""" note=""""""]] +[[!template id=sched title="""So You Want To Be An Emacs-Fluencer?""" url="""/2024/talks/sharing""" speakers="""Gopar""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""sharing""" note=""""""]] +[[!template id=sched title="""Watering my (digital) plant with Emacs timers""" url="""/2024/talks/water""" speakers="""Christopher Howard""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""water""" note=""""""]] +[[!template id=sched title="""org-teach: a minor mode for writing course materials in Emacs""" url="""/2024/talks/org-teach""" speakers="""James Endres Howell""" watch="""https://emacsconf.org/2024/watch/gen""" slug="""org-teach""" note=""""""]] + +Jump to: <a href="#gen">General</a> + +<h1 id="dev" class="sched-track Development">Development (3 talks)</h1> +[[!template id=sched title="""An Experimental Emacs Core in Rust""" url="""/2024/talks/rust""" speakers="""Troy Hinckley""" watch="""https://emacsconf.org/2024/watch/dev""" slug="""rust""" note=""""""]] +[[!template id=sched title="""Literate Programming for the 21st Century""" url="""/2024/talks/literate""" speakers="""Howard Abrams""" watch="""https://emacsconf.org/2024/watch/dev""" slug="""literate""" note=""""""]] +[[!template id=sched title="""PGmacs: browsing and editing PostgreSQL databases from Emacs""" url="""/2024/talks/pgmacs""" speakers="""Eric Marsden""" watch="""https://emacsconf.org/2024/watch/dev""" slug="""pgmacs""" note=""""""]]
\ No newline at end of file diff --git a/2024/sidebar.md b/2024/sidebar.md index 12203883..ec441ca3 100644 --- a/2024/sidebar.md +++ b/2024/sidebar.md @@ -7,7 +7,9 @@ * [[**Call for Participation**|cfp]] * [[Ideas]] * [[Submit]] +* [[Talks]] * [[Volunteer]] +* [[Prepare]] * [[Planning]] * [[Guidelines for Conduct|conduct]] * [[Contact information|contact]] diff --git a/2024/talks.md b/2024/talks.md new file mode 100644 index 00000000..e642a148 --- /dev/null +++ b/2024/talks.md @@ -0,0 +1,15 @@ +[[!meta title="Talks"]] +[[!meta copyright="Copyright © 2024 Sacha Chua"]] +[[!sidebar content=""]] + +We're getting ready for EmacsConf 2024. Want to propose a talk? +[[Check out our call for participation|/2024/cfp]] and submit your proposal +by September 20, 2024 (Friday)! + +Here are some of the talks we've accepted so far: + +[[!inline pages="internal(2024/schedule-details)" raw="yes"]] + +Want to help make EmacsConf even awesomer? [[ [[Volunteer!|/volunteer]] + +We hope to see you all around on Dec 7-8 for EmacsConf 2024! diff --git a/2024/talks/learning.md b/2024/talks/learning.md new file mode 100644 index 00000000..c5814d23 --- /dev/null +++ b/2024/talks/learning.md @@ -0,0 +1,68 @@ +[[!meta title="Survival of the Skillest: Thriving in the Learning Jungle"]] +[[!meta copyright="Copyright © 2024 Bala Ramadurai"]] +[[!inline pages="internal(2024/info/learning-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Survival of the Skillest: Thriving in the Learning Jungle +Bala Ramadurai (his/him) - https://balaramadurai.net + +[[!inline pages="internal(2024/info/learning-before)" raw="yes"]] + +In today's fast-paced world, the need to learn new skills is more crucial +than ever. The ability to adapt and evolve not only enhances your +employability but also empowers you to navigate life's challenges more +effectively. By acquiring new skills, you stay relevant, innovative, and +capable of seizing opportunities that come your way. + +The session will begin with an engaging discussion on the necessity of +learning new skills, emphasizing that the ability to adapt and evolve is +crucial. Using the metaphor of "emptying your teacup," you will explore the +concept of approaching learning with an open mind, ready to absorb new +knowledge and skills. + +Next, you'll dive into actionable techniques for managing your tasks and +projects efficiently. Bala will introduce the PARA method—Projects, Areas, +Resources, and Archives—a structured approach to organizing your work and +life. You will learn how to categorize your tasks, set clear goals, and +maintain a balanced workflow. + +Furthermore, the talk will highlight the importance of regular reviews. +Weekly, quarterly, and yearly reviews will help you stay on track, reflect +on your progress, and plan for the future. Through these reviews, you'll be +encouraged to ask big life questions, such as your financial goals, the +impact you've had on others, and your work-life balance. + +Finally, you'll be introduced to the 9-windows framework, a powerful tool +for future career planning. Join us and take the first step towards +mastering the art and developing the mindset of skillful survival in the +fast-paced ever changing learning jungle. + +About the speaker: + +Dr. Bala Ramadurai is an author, coach, consultant, podcaster and +professor. He has authored a book on Design Thinking called Karmic Design +Thinking (<https://dt.balaramadurai.net>). He has 3 patents to his credit and +10+ publications in international research journals. He co-founded TRIZ +Innovation India (<https://trizindia.org>) and is an Adjunct Professor at +Symbiosis Institute of Business Management (India), Universidad +Panamericana (Mexico), Symbiosis Institute of Management Studies and +National Programme on Technology Enhanced Learning (NPTEL). He is also a +board member in the Board of Studies for Symbiosis International University. + +In this talk, you'll discover the importance of continuous skill +development and learn practical strategies to manage your personal and +professional growth effectively using Emacs org-mode, Getting Things Done +(David Allen's GTD), PARA (Tiego Forte's Projects-Areas-Resources-Archives) +and system operator (or 9-windows). Bala will guide you through a +transformative journey of self-improvement and productivity. + + + +[[!inline pages="internal(2024/info/learning-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/learning-nav)" raw="yes"]] + + diff --git a/2024/talks/literate.md b/2024/talks/literate.md new file mode 100644 index 00000000..0fb0a0de --- /dev/null +++ b/2024/talks/literate.md @@ -0,0 +1,50 @@ +[[!meta title="Literate Programming for the 21st Century"]] +[[!meta copyright="Copyright © 2024 Howard Abrams"]] +[[!inline pages="internal(2024/info/literate-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Literate Programming for the 21st Century +Howard Abrams (he/him) - @howard@emacs.ch , <https://www.howardism.org> + +[[!inline pages="internal(2024/info/literate-before)" raw="yes"]] + +Donald Knuth’s idea of *literate programming* in the 80’s and 90’s was +interesting, but he didn’t realize what Emacs and Org can do in this +century. In this talk, I would like to go back your initial *dabblings* +with Org `src` blocks to show how you can program *literately* as quickly +as you can in any other mode. + +Some of the tips and tricks include: + +- Automatically keeping your lit code sync’d +- Easier code generation +- Jumping to Org headers to help organize code +- Jumping to code definitions with the xref interface + +At the end of this talk, I hope to inspire you to try it again, as my +personal “go to” is *programming literately*. + +I will be following the format and outline in my essay: +<https://howardism.org/Technical/Emacs/literate-writ-large.html> + +About the speaker: + +About ten years ago, I gave a talk I called *literate devops* and people +still ask me if I still use those techniques. For all my personal +projects, I do. Even projects that I share with others, I often *start* +programming with an Org file. + +I will admit, programming within Org blocks has some burrs, but over +the years, I’ve filed them off with helper functions, snippets and +other features. Thought I would share these. + + + +[[!inline pages="internal(2024/info/literate-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/literate-nav)" raw="yes"]] + + diff --git a/2024/talks/org-teach.md b/2024/talks/org-teach.md new file mode 100644 index 00000000..30b7b8ea --- /dev/null +++ b/2024/talks/org-teach.md @@ -0,0 +1,44 @@ +[[!meta title="org-teach: a minor mode for writing course materials in Emacs"]] +[[!meta copyright="Copyright © 2024 James Endres Howell"]] +[[!inline pages="internal(2024/info/org-teach-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# org-teach: a minor mode for writing course materials in Emacs +James Endres Howell (he/him) - <mailto:james@endres-howell.org> + +[[!inline pages="internal(2024/info/org-teach-before)" raw="yes"]] + +I will demonstrate how I used Emacs to produce all the materials for teaching an undergraduate +molecular and cell biology course at a very large university. My org-teach package +(<https://git.sr.ht/~jamesendreshowell/org-teach/>) is a collection of Org macros that customize export +to LaTeX and Beamer in order to produce (1) textbook-style handouts, (2) slides for classroom +presentation, and (3) quiz and exam questions, all from a single Org source document. It also +provides a simple minor mode that facilitates authoring such source documents. We will discuss the +benefits of producing course materials as plain-text outlines, and of exploiting the power of Emacs +and Org mode for writing and managing book-length teaching materials. + +Last year at EmacsConf 2023, I presented some aspects of an earlier version of org-teach +(<https://git.sr.ht/~jamesendreshowell/org-teach-EmacsConf2023>). This talk will provide more +background, more details, and some exciting new features. + +About the speaker: + +James Endres Howell has taught Molecular and Cell +Biology, Biochemistry, Microbiology, Immunology, +Toxicology, and Molecular Medicine at Penn State +since 2006. Recently Dr. Howell has developed +popular courses for non-science majors in +Genetics, Ecology and Evolution; Science in +Literature; and Science in Media. He has used +Emacs daily since 1988. + + + +[[!inline pages="internal(2024/info/org-teach-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/org-teach-nav)" raw="yes"]] + + diff --git a/2024/talks/p-search.md b/2024/talks/p-search.md new file mode 100644 index 00000000..01e8aed7 --- /dev/null +++ b/2024/talks/p-search.md @@ -0,0 +1,61 @@ +[[!meta title="p-search: a local search engine in Emacs"]] +[[!meta copyright="Copyright © 2024 Zac Romero"]] +[[!inline pages="internal(2024/info/p-search-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# p-search: a local search engine in Emacs +Zac Romero - <mailto:zacromero@posteo.com> + +[[!inline pages="internal(2024/info/p-search-before)" raw="yes"]] + +Search is an essential part of any digital work. Despite this +importance, most tools don't go beyond simple string/regex matching. +Oftentimes, a user knows more about what they're looking for: who +authored the file, how often it's modified, as well as search terms that +the user is only slightly confident exist. + +p-search is a search-engine designed to combine the various prior +knowledge about the search target, presenting it to the user in a +systematic way. In this talk, I will present this package as well as go +over the fundamentals of inforation retrieval. + +Details: + +In this talk, I will go over the p-search. p-search is a search-engine +to assist users in finding things, with a focus on flexibility and +customizablity. + +The talk will begin by going over concepts from the field of information +retrieval such as indexing, querying, ranking, and evaluating. This +will provide the necessary background to describe the workings of +p-search. + +Next, an overview of the p-search package and its features will be +given. p-search utilizes a probabilistic framework to rank documents +according to prior beliefs as to what the file is. So for example, a +user might know for sure that the file contains a particular string, +might have a strong feeling that it should contain another word, and +things that some other words it may contain. The user knows the file +extension, the subdirectory, and has known that a particular person +works on this file a lot. p-search allows the user to express all of +these predicates at once, and ranks documents accordingly. + +The talk will then progress to discuss assorted topics concerting the +project, such as design considerations and future directions. + +The aim of the talk is to expand the listeners' understanding of search +as well as inspire creativity concerning the possibilities of search +tools. + +Code: <https://github.com/zkry/p-search> + + + +[[!inline pages="internal(2024/info/p-search-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/p-search-nav)" raw="yes"]] + + diff --git a/2024/talks/pgmacs.md b/2024/talks/pgmacs.md new file mode 100644 index 00000000..232294ac --- /dev/null +++ b/2024/talks/pgmacs.md @@ -0,0 +1,49 @@ +[[!meta title="PGmacs: browsing and editing PostgreSQL databases from Emacs"]] +[[!meta copyright="Copyright © 2024 Eric Marsden"]] +[[!inline pages="internal(2024/info/pgmacs-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# PGmacs: browsing and editing PostgreSQL databases from Emacs +Eric Marsden (he/him) - <mailto:eric.marsden@risk-engineering.org> + +[[!inline pages="internal(2024/info/pgmacs-before)" raw="yes"]] + +PGmacs provides an Emacs-based browsing and +editing interface for the PostgreSQL DBMS. It +allows you to browse the contents of database +tables, in paginated mode for large tables, to +edit column values in the minibuffer or using a +widget-based interface, to delete, copy and insert +new rows, and to save the contents of a table in +CSV or JSON format. You can run shell commands on +column values. You can also rename tables and +columns, add SQL comments, and generate SchemaSpy +diagrams. + +PGmacs works both in the terminal and in GUI mode. +It uses the pg-el library, which implements the +PostgreSQL wire protocol, to connect to PostgreSQL +over the network or over a Unix socket. + +The talk will provide an overview of the functionality of PGmacs, then show how it can be easily +extended to display images stored as database BLOBs inlined in a row-list buffer. + +About the speaker: + +Eric Marsden developed his first Emacs packages +pg-el, coffee.el (an implementation of the +essential Hyper Text Coffee Pot Control Protocol) +and ipp.el as a procrastination exercise to avoid +working on his PhD. He continues to use Emacs Lisp +in his spare time. + + + +[[!inline pages="internal(2024/info/pgmacs-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/pgmacs-nav)" raw="yes"]] + + diff --git a/2024/talks/project.md b/2024/talks/project.md new file mode 100644 index 00000000..65c33ac1 --- /dev/null +++ b/2024/talks/project.md @@ -0,0 +1,64 @@ +[[!meta title="Managing writing project metadata with org-mode"]] +[[!meta copyright="Copyright © 2024 Blaine Mooers"]] +[[!inline pages="internal(2024/info/project-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Managing writing project metadata with org-mode +Blaine Mooers (he/him) - Pronunciation: Blane Moors, <mailto:blaine-mooers@ouhsc.edu> + +[[!inline pages="internal(2024/info/project-before)" raw="yes"]] + +The planning and writing of a scientific manuscript is an intricate process that requires focused effort. +Scientists must make many decisions about what to include and exclude from the paper, often capturing these decisions in notes in the margins, appended notes, or external files. +This ad hoc approach becomes unmanageable when the notes exceed the length of the manuscript, which is often the case. +Nonetheless, these notes can be vital when responding to reviewers' critiques. + +Great scientists like Linus Pauling effectively utilized laboratory notebooks to store metadata on his manuscripts. +His cross-referencing system resembled that of Niklas Luhmann in his physical zettelkasten. +These paper-based approaches have pros and cons, but they are no longer popular because of the hard work required to make them work well. +In comparison, the org-roam-ui view of my zettelkasten provides a garden of endlessly forking paths I can wander in all day. + +I sought a more focused approach to managing my attention and the metadata for one writing project. +I developed a project-specific writing log for this purpose about a decade ago. +The writing log helps me manage anxieties about forgetting where I left off on an interrupted project (Fear of Forgetting, FoF). +In this talk, I will highlight the features of my writing log template in org-mode. + +The first section supports gathering the initial thoughts about the project needed to assemble a central hypothesis around which to build the paper. +Subsections support listing the experiments required to address the central hypothesis and the key discussion points. +These subsections include plans for graphical items like images, data plots, tables, equations, and code blocks. +Of course, this section will evolve as the results accumulate. +When largely completed, this section supports drafting a quarter to a third of a manuscript on day one of the project. + +The following two sections support project administration and assessment. +The administration section includes plans to apply for funding and approvals for the work. +The assessment section supports periodic checks of the project's current state, what holds the manuscript from submission today, and what is missing that makes a larger impact. +This section includes a timeline and milestones to finish the project promptly. +These can be displayed in tables that org-mode so strongly supports. + +The central section of the template contains daily accounts of accomplishments, decisions, and correspondence about the project. +I read this section after a hiatus to resume work on the project quickly. +An open-ended to-do list and a section for collecting ideas for future projects follow the daily log. +The last section contains protocols and guidelines for the various tasks involved in completing the project. + +Here, context switching between the writing log and the manuscript is fine because it usually happens only at the beginning and the end of the writing session. My project-specific approach keeps my mind focused on the project at hand and my FoF under control. +I share my writing log template in org-mode on GitHub. + +About the speaker: + +Blaine Mooers is an associate professor of Biochemistry and Physiology at the University of Oklahoma. +He uses X-ray diffraction to study the molecular structure of proteins and RNAs important in disease. +He writes grant applications, progress reports, manuscripts, lectures, seminars, and talks each year in Emacs. +To control his fear of forgetting (FoF), he uses an external document, the **writing log**, to store metadata about each writing project. +He switched from using LaTeX to Org-mode recently. +He will discuss the features of the writing log and the joys of editing it in Org-mode. + + + +[[!inline pages="internal(2024/info/project-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/project-nav)" raw="yes"]] + + diff --git a/2024/talks/rust.md b/2024/talks/rust.md new file mode 100644 index 00000000..e994d28f --- /dev/null +++ b/2024/talks/rust.md @@ -0,0 +1,34 @@ +[[!meta title="An Experimental Emacs Core in Rust"]] +[[!meta copyright="Copyright © 2024 Troy Hinckley"]] +[[!inline pages="internal(2024/info/rust-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# An Experimental Emacs Core in Rust +Troy Hinckley - <https://coredumped.dev>, <mailto:troy@troyhinckley.com> + +[[!inline pages="internal(2024/info/rust-before)" raw="yes"]] + +An overview and discussion and early prototype of a new Emacs core written in Rust. The talk covers some of the interesting design choices in the GNU Emacs C core, as well as some of the trade-offs made in the Rust core. <https://github.com/CeleritasCelery/rune> + +- What is the Emacs core? +- How has the core evolved? +- Design trade-offs + - multi-threading + - Precise GC +- Being bug compatible with GNU Emacs +- Comparison + +About the speaker: + +Hardware Engineer with interest in low-level programming and the hardware-software boundary. + + + +[[!inline pages="internal(2024/info/rust-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/rust-nav)" raw="yes"]] + + diff --git a/2024/talks/sharing.md b/2024/talks/sharing.md new file mode 100644 index 00000000..4c71a925 --- /dev/null +++ b/2024/talks/sharing.md @@ -0,0 +1,39 @@ +[[!meta title="So You Want To Be An Emacs-Fluencer?"]] +[[!meta copyright="Copyright © 2024 Gopar"]] +[[!inline pages="internal(2024/info/sharing-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# So You Want To Be An Emacs-Fluencer? +Gopar - IRC: gopar, <https://www.youtube.com/@goparism/> , <mailto:gopardaniel@gmail.com> + +[[!inline pages="internal(2024/info/sharing-before)" raw="yes"]] + +Ever thought about sharing your Emacs knowledge? Starting a YouTube +channel, blog, podcast, or even smoke signals to share those tidbits? If +you’ve answered "No", then I'd like to change your mind. And if you said +"Yes", then you're already on the right path. + +In this talk, I will share what I've learned from my journey as an Emacs +advocate, including tips, setups (both current and past), and various +alternatives to get your works out there. Most importantly, I'll discuss +why your story and perspective matter, even if you think otherwise. Your +unique experience can inspire and help others in the Emacs community. + +About the speaker: + +Gopar, a fellow Emacs user and advocate, will be sharing insights on how +everyone can become the Emacs Influencer they never knew they wanted to be. + +From starting a YouTube channel to writing blogs, Gopar will provide +practical tips and share personal experiences to help you embark on your +journey of sharing Emacs knowledge. + + +[[!inline pages="internal(2024/info/sharing-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/sharing-nav)" raw="yes"]] + + diff --git a/2024/talks/water.md b/2024/talks/water.md new file mode 100644 index 00000000..bd96711c --- /dev/null +++ b/2024/talks/water.md @@ -0,0 +1,26 @@ +[[!meta title="Watering my (digital) plant with Emacs timers"]] +[[!meta copyright="Copyright © 2024 Christopher Howard"]] +[[!inline pages="internal(2024/info/water-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Watering my (digital) plant with Emacs timers +Christopher Howard (he/him) - IRC: lispmacs, http://gem.librehacker.com, <mailto:christopher@librehacker.com> + +[[!inline pages="internal(2024/info/water-before)" raw="yes"]] + +This talk gives a brief introduction to Emacs timer functionality. I explain how I used Emacs timers to water and harvest my flower on the gemini Astrobotany service. + +About the speaker: + +Christopher Howard is a simulator technican and free software ethusiast living in Fairbanks, Alaska. Christopher explains how he uses Emacs timers to automatically water and harvest his flower on the Astrobotany gemini service. + + + +[[!inline pages="internal(2024/info/water-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/water-nav)" raw="yes"]] + + diff --git a/2024/talks/writing.md b/2024/talks/writing.md new file mode 100644 index 00000000..d05af940 --- /dev/null +++ b/2024/talks/writing.md @@ -0,0 +1,34 @@ +[[!meta title="Emacs Writing Studio"]] +[[!meta copyright="Copyright © 2024 Peter Prevos"]] +[[!inline pages="internal(2024/info/writing-nav)" raw="yes"]] + +<!-- Initially generated with emacsconf-publish-talk-page and then left alone for manual editing --> +<!-- You can manually edit this file to update the abstract, add links, etc. ---> + + +# Emacs Writing Studio +Peter Prevos (he) - <mailto:peter@prevos.net> , <https://peterprevos.com> , @danderzei@aus.social + +[[!inline pages="internal(2024/info/writing-before)" raw="yes"]] + +Emacs Writing Studio is a comprehensive guide and configuration +for authors using Emacs. The book covers everything from +organising ideas and writing distraction-free to publishing in +multiple formats. The book itself was fully written and published +with the configuration it describes. This talk outlines the proces +of developing this configuration and the book and some +perspectives on using Emacs as a tool to write for humans. + +About the speaker: + +Peter Prevos is a water engineer and social scientist. In this +talk Peter introduces Emacs Writing Studio, a starter kit and +associated manual for authors with no Emacs experience. + + + +[[!inline pages="internal(2024/info/writing-after)" raw="yes"]] + +[[!inline pages="internal(2024/info/writing-nav)" raw="yes"]] + + |