diff options
Diffstat (limited to '')
-rw-r--r-- | 2024/draft-schedule.md | 3 | ||||
-rw-r--r-- | 2024/info/org-teach-after.md | 10 | ||||
-rw-r--r-- | 2024/info/org-teach-before.md | 12 | ||||
-rw-r--r-- | 2024/info/org-teach-nav.md | 6 | ||||
-rw-r--r-- | 2024/info/sharing-after.md | 10 | ||||
-rw-r--r-- | 2024/info/sharing-before.md | 12 | ||||
-rw-r--r-- | 2024/info/sharing-nav.md | 6 | ||||
-rw-r--r-- | 2024/info/water-after.md | 10 | ||||
-rw-r--r-- | 2024/info/water-before.md | 12 | ||||
-rw-r--r-- | 2024/info/water-nav.md | 7 | ||||
-rw-r--r-- | 2024/organizers-notebook.md | 10 | ||||
-rw-r--r-- | 2024/organizers-notebook/index.org | 9 | ||||
-rw-r--r-- | 2024/prepare.md | 311 | ||||
-rw-r--r-- | 2024/schedule-details.md | 10 | ||||
-rw-r--r-- | 2024/sidebar.md | 2 | ||||
-rw-r--r-- | 2024/talks.md | 15 | ||||
-rw-r--r-- | 2024/talks/org-teach.md | 44 | ||||
-rw-r--r-- | 2024/talks/sharing.md | 42 | ||||
-rw-r--r-- | 2024/talks/water.md | 26 | ||||
-rw-r--r-- | donate.md | 35 | ||||
-rw-r--r-- | donors.md | 29 | ||||
-rw-r--r-- | organizers-notebook.md | 46 | ||||
-rw-r--r-- | organizers-notebook/index.org | 38 | ||||
-rw-r--r-- | templates/page.tmpl | 3 |
24 files changed, 700 insertions, 8 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/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..b3905c39 --- /dev/null +++ b/2024/info/org-teach-nav.md @@ -0,0 +1,6 @@ + +<div class="talk-nav"> +Back to the [[talks]] +Previous 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/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..27dbcc3b --- /dev/null +++ b/2024/info/sharing-nav.md @@ -0,0 +1,6 @@ + +<div class="talk-nav"> +Back to the [[talks]] +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/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..84fcc47b --- /dev/null +++ b/2024/schedule-details.md @@ -0,0 +1,10 @@ +Jump to: <a href="#dev">Development</a> + +<h1 id="gen" class="sched-track General">General (3 talks)</h1> +[[!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 (0 talks)</h1> 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/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/sharing.md b/2024/talks/sharing.md new file mode 100644 index 00000000..29830b94 --- /dev/null +++ b/2024/talks/sharing.md @@ -0,0 +1,42 @@ +[[!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 +content creator, including tips, setups (both current and past), and +various alternatives to get your content 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 content creator, 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 +own content creation journey. + + + +[[!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/donate.md b/donate.md new file mode 100644 index 00000000..3bdefd11 --- /dev/null +++ b/donate.md @@ -0,0 +1,35 @@ +[[!meta title="Donate"]] +[[!meta copyright="Copyright © 2024 Amin Bandali"]] + +[[!template id=pagedraft]] + +EmacsConf is a volunteer-run conference organized by a group of people +passionate about GNU Emacs and Emacs Lisp just like you! :-) + +Your donations will help cover the costs for various parts of our +infrastructure, and help support and sustain EmacsConf year after +year.[*] + +<p class="center"><a href="https://my.fsf.org/civicrm/contribute/transact?reset=1&id=70">❤️ Donate</a></p> + +Your donations to EmacsConf are collected and held by our fiscal +sponsor the Free Software Foundation, a 501(c)(3) nonprofit +organization with a worldwide mission to promote computer user +freedom, and are therefore tax-deductible in the United States. + +We would like to acknowledge our donors by listing their names +on our **[[donors]]** page. + +--- + +[*] Don't fret, EmacsConf is not in any financial trouble. :-) +Our costs have consistently been fairly low and paid out of pocket by +one of the organizers each year. EmacsConf's main source of strength +has been our wonderful community, including our amazing volunteers +without whom EmacsConf would not have been as successful as it has +been. Monetary donations are merely an additional avenue for folks +who feel extra generous and so inclined to help cover our +infrastructure costs and expenses, and we plan on brainstorming and +asking the community for suggestions and feedback for how to best +spend any excess funds we may collect to further give back to the +community. diff --git a/donors.md b/donors.md new file mode 100644 index 00000000..a8921a7b --- /dev/null +++ b/donors.md @@ -0,0 +1,29 @@ +[[!meta title="Donors"]] + +[[!template id=pagedraft]] + +## Thank you! + +We are deeply grateful for all the generous donations from our donors. + +Below is a list of all of the donations we have received since +November 2023 when [EmacsConf joined the Free Software Foundation +fiscal sponsorship program][fsf-emacsconf-announce], the [Working +Together for Free Software Fund][fsf-working-together-fund]. + +Donors who agreed to be thanked publicly are listed in alphabetical +order, and those who chose not to are instead listed as 'Anonymous'. + +## 2024 + +- Jeremy Roe + +## 2023 + +- Anonymous (4) +- Jan Prunk +- Scott Randby + + +[fsf-emacsconf-announce]: https://www.fsf.org/news/emacsconf-joins-free-software-foundation-fiscal-sponsorship-program +[fsf-working-together-fund]: https://www.fsf.org/working-together/fund diff --git a/organizers-notebook.md b/organizers-notebook.md index 9589cf57..13cfb034 100644 --- a/organizers-notebook.md +++ b/organizers-notebook.md @@ -20,6 +20,8 @@ This document is the general organizers' notebook that can be used as a starting - [Create the public organizers’ notebook in the wiki](#starting-up-the-conference-planning-process-create-the-public-organizers-notebook-in-the-wiki) - [Phases and lessons learned](#phases-and-lessons-learned) - [Draft CFP](#phases-and-lessons-learned-draft-cfp) + - [Process proposals](#orgef6a44f) + - [Accept proposals](#orgfef7f08) <a id="starting-up-the-conference-planning-process"></a> @@ -118,3 +120,47 @@ Put inside double square brackets: `!template id=pagedraft` (especially for Pacific time). Extending beyond 5pm puts strain on European organizers and volunteers, though. + +<a id="orgef6a44f"></a> + +## Process proposals + +1. In the private repository, create a conf.org. +2. Set `emacsconf-org-file` to its location. +3. Create a heading for Submissions and set `CUSTOM_ID` to `submissions`. +4. Prepare the `prepare` and `submit` pages on the wiki. + +When proposals come in: + +1. Acknowledge with an e-mail along the lines of: + + Hello, ....! + + <feedback> We'll wait another week in case anyone else wants to + chime in before I add it to the wiki and send further notes. :) Thanks for + submitting this! + +2. Use `emacsconf-mail-add-submission` if it works, or create the entry and paste it in. + `org-toggle-item` can help convert Org-style headings into a nested list. +3. Set the following fields (`my/org-set-property` + can be helpful): EMERGENCY, Q\_AND\_A, + AVAILABILITY, NAME, PRONOUNS, TIME, + SLUG, EMAIL, NAME\_SHORT, CUSTOM\_ID, + TRACK, TIMEZONE, CATEGORY, DATE\_SUBMITTED, + PUBLIC\_EMAIL + + +<a id="orgfef7f08"></a> + +## Accept proposals + +Setup: + +1. Create YYYY/talks.md. + +For each talk: + +1. Set up “Talk abstract” and “Talk details” sections in the conf.org talk subtree. +2. Create wiki page with `emacsconf-add-talk`. +3. Use `emacsconf-publish-info-pages` and `emacsconf-publish-schedule` as needed. + diff --git a/organizers-notebook/index.org b/organizers-notebook/index.org index 358c0108..87e0707b 100644 --- a/organizers-notebook/index.org +++ b/organizers-notebook/index.org @@ -119,3 +119,41 @@ Put inside double square brackets: =!template id=pagedraft= - It’s easier for us to extend beyond 5pm than to go before 9am (especially for Pacific time). Extending beyond 5pm puts strain on European organizers and volunteers, though. +** Process proposals + +1. In the private repository, create a conf.org. +2. Set ~emacsconf-org-file~ to its location. +3. Create a heading for Submissions and set ~CUSTOM_ID~ to ~submissions~. +4. Prepare the ~prepare~ and ~submit~ pages on the wiki. + +When proposals come in: + + 1. Acknowledge with an e-mail along the lines of: + + #+begin_example + Hello, ....! + + <feedback> We'll wait another week in case anyone else wants to + chime in before I add it to the wiki and send further notes. :) Thanks for + submitting this! + #+end_example + + 2. Use ~emacsconf-mail-add-submission~ if it works, or create the entry and paste it in. + ~org-toggle-item~ can help convert Org-style headings into a nested list. + 3. Set the following fields (~my/org-set-property~ + can be helpful): EMERGENCY, Q_AND_A, + AVAILABILITY, NAME, PRONOUNS, TIME, + SLUG, EMAIL, NAME_SHORT, CUSTOM_ID, + TRACK, TIMEZONE, CATEGORY, DATE_SUBMITTED, + PUBLIC_EMAIL +** Accept proposals + +Setup: + +1. Create YYYY/talks.md. + +For each talk: + +1. Set up "Talk abstract" and "Talk details" sections in the conf.org talk subtree. +2. Create wiki page with ~emacsconf-add-talk~. +3. Use ~emacsconf-publish-info-pages~ and ~emacsconf-publish-schedule~ as needed. diff --git a/templates/page.tmpl b/templates/page.tmpl index 1f40aa66..20c3dd31 100644 --- a/templates/page.tmpl +++ b/templates/page.tmpl @@ -142,10 +142,11 @@ <TMPL_IF HAVE_ACTIONS> <TMPL_IF HTML5><nav class="actions"><TMPL_ELSE><div class="actions"></TMPL_IF> <ul> +<!-- <li><a href="<TMPL_VAR BASEURL>donate/">❤️ Donate</a></li> --> <TMPL_IF EDITURL> <li><a href="<TMPL_VAR EDITURL>" rel="nofollow">Edit</a></li> <TMPL_ELSE> -<li><a href="/edit/">Edit <span class="muted">(how to)</span></a></li> +<li><a href="<TMPL_VAR BASEURL>edit/">Edit <span class="muted">(how to)</span></a></li> </TMPL_IF> <TMPL_IF RECENTCHANGESURL> <li><a href="<TMPL_VAR RECENTCHANGESURL>">Recent Changes</a></li> |