diff options
Diffstat (limited to 'organizers-notebook.md')
| -rw-r--r-- | organizers-notebook.md | 85 |
1 files changed, 51 insertions, 34 deletions
diff --git a/organizers-notebook.md b/organizers-notebook.md index 2ff10b06..d173478f 100644 --- a/organizers-notebook.md +++ b/organizers-notebook.md @@ -21,7 +21,7 @@ This document is the general organizers' notebook that can be used as a starting - [Phases and lessons learned](#phases-and-lessons-learned) - [Draft CFP](#phases-and-lessons-learned-draft-cfp) - [Announce](#phases-and-lessons-learned-announce) - - [Process proposals](#phases-and-lessons-learned-process-proposals) + - [Process proposals / submissions](#phases-and-lessons-learned-process-proposals) - [Accept proposals](#phases-and-lessons-learned-accept-proposals) - [Draft schedule](#draft-schedule) - [Set up backstage and upload](#phases-and-lessons-learned-set-up-backstage-and-upload) @@ -88,8 +88,8 @@ This repository will store submissions, contact information, etc. 1. Create the repository on `front0`. Ex: - export YEAR=2025 sudo su - git + export YEAR=2026 cd repositories mkdir emacsconf-$YEAR-private.git cd emacsconf-$YEAR-private.git @@ -99,14 +99,15 @@ This repository will store submissions, contact information, etc. @emacsconf-2024-org = bandali sachac ... repo emacsconf-2024-private RW+ = @admins @emacsconf-2024-org orga -3. Clone the private repository into the appropriate location. `git clone git@git.emacsconf.org:emacsconf-2025-private private` + +1. Clone the private repository into the appropriate location. `git clone git@git.emacsconf.org:emacsconf-2026-private private` <a id="starting-up-the-conference-planning-process-create-the-public-organizers-notebook-in-the-wiki"></a> ## Create the public organizers’ notebook in the wiki -Ex: <../2024/organizers-notebook/index.md> +Ex: <../2026/organizers-notebook/index.md> <a id="phases-and-lessons-learned"></a> @@ -120,9 +121,9 @@ Ex: <../2024/organizers-notebook/index.md> Create linked pages -- [ ] year index: ex: <../2024.md> -- [ ] volunteer page: ex: <../volunteer.md> -- [ ] submit page: ex: <../2024/submit.md> +- [X] year index: ex: <../2026.md> +- [X] volunteer page: ex: <../volunteer.md> +- [X] submit page: ex: <../2026/submit.md> ### How to mark pages as drafts @@ -268,7 +269,7 @@ available to spark more interest. <a id="phases-and-lessons-learned-process-proposals"></a> -## Process proposals +## Process proposals / submissions 1. In the private repository, create a conf.org. 2. Set `emacsconf-org-file` to its location. @@ -277,23 +278,24 @@ available to spark more interest. 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. +1. 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` + +2. Set the following fields (`sacha-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 +3. Use `emacsconf-mail-review` or 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! + <a id="phases-and-lessons-learned-accept-proposals"></a> @@ -302,14 +304,27 @@ When proposals come in: Setup: 1. Create YYYY/talks.md. + + We're getting ready for EmacsConf 2026. Want to propose a talk? + [[Check out our call for participation|/2026/cfp]] and submit your proposal + by Friday, September 18, 2026! + + Here are some of the talks we've accepted so far: + + [[!inline pages="internal(2026/schedule-details)" raw="yes"]] + + Want to help make EmacsConf even awesomer? [[Volunteer!|/volunteer]] + + We hope to see you all around on Dec 12-13 for EmacsConf 2026! For each talk: 1. Set up “Talk abstract” and “Talk details” sections in the conf.org talk subtree. 2. Change status to `TO_CONFIRM`. -3. Create wiki page with `emacsconf-publish-add-talk`. -4. Use `emacsconf-publish-info-pages` and `emacsconf-publish-schedule` as needed. -5. Send acceptance e-mail with `emacsconf-mail-accept-talk` +3. Use `emacsconf-set-file-prefixes`. +4. Create wiki page with `emacsconf-publish-add-talk`. +5. Use `emacsconf-publish-info-pages` and `emacsconf-publish-schedule` as needed. +6. Send acceptance e-mail with `emacsconf-mail-accept-talk` After the CFP ends: @@ -343,9 +358,11 @@ After the CFP ends: ### TODO Send draft schedule to speakers :email: 1. Evaluate the draft schedule we want to use. -2. `emacsconf-schedule-update-from-info` -3. `C-u M-x emacsconf-mail-template-to-all-groups RET emacsconf-mail-draft-schedule RET` -4. If that looks good, `M-x emacsconf-mail-template-to-all-groups`. You can use `M-x emacsconf-mail-merge-send-all` to send all the drafts, or send them one by one. +2. <elisp:emacsconf-schedule-update-from-info> +3. Verify with <elisp:emacsconf-agenda>. +4. `C-u M-x emacsconf-mail-template-to-all-groups RET emacsconf-mail-draft-schedule RET` +5. If that looks good, `M-x emacsconf-mail-template-to-all-groups`. You can use `M-x emacsconf-mail-merge-send-all` to send all the drafts, or send them one by one. +6. Save the e-mailed schedules emacsconf-schedule-save-emailed-times <a id="phases-and-lessons-learned-set-up-backstage-and-upload"></a> @@ -1029,26 +1046,26 @@ After the conference: 2. `ansible-playbook -i inventory.yml prod-playbook.yml --tags prerec` 3. Set up the `update-cache` script. - #!/bin/bash - # export CONF_PUBLIC=1 - rsync -avu ~/proj/emacsconf/2025/assets/intros/*--intro.* ~/proj/emacsconf/2025/cache/ - rsync -avzue ssh --exclude ffmpeg2pass* --exclude .lock-\* --exclude 'partial--*' res:~/cache/ ~/proj/emacsconf/2025/cache/ --exclude .git + export CONF_PUBLIC=0 + rsync -avu ~/proj/emacsconf/$year/assets/intros/*--intro.* ~/proj/emacsconf/$year/cache/ + rsync -avzue ssh --exclude ffmpeg2pass\* --exclude .lock-\* --exclude 'partial--*' res:~/cache/ ~/proj/emacsconf/$year/cache/ --exclude .git chmod ugo+r . -R - rsync -avzue ssh --exclude ffmpeg2pass* --exclude 'partial--*' ~/proj/emacsconf/2025/cache/ res:~/cache/ $* --exclude .git - rsync -avzue ssh --exclude ffmpeg2pass* --exclude 'partial--*' ~/proj/emacsconf/2025/cache/ orga@media:/var/www/media.emacsconf.org/2025/backstage/ $* --exclude .git + rsync -avzue ssh --exclude ffmpeg2pass\* --exclude .lock-\* --exclude 'partial--*' res:~/cache/ ~/proj/emacsconf/$year/cache/ --exclude .git + rsync -avzue ssh --exclude ffmpeg2pass\* --exclude 'partial--*' ~/proj/emacsconf/$year/cache/ res:~/cache/ $* --exclude .git + rsync -avzue ssh --exclude ffmpeg2pass\* --exclude 'partial--*' ~/proj/emacsconf/$year/cache/ orga@media:/var/www/media.emacsconf.org/$year/backstage/ $* --exclude .git ssh orga@media "cd ~/backstage; chmod ugo+r -- *" if [ ! -z "$CONF_PUBLIC" ]; then echo "Updating public media" - rsync -avzue ssh --exclude \*--original\* --exclude ffmpeg2pass* --exclude \*--reencoded\* ~/proj/emacsconf/2025/cache/ orga@media:/var/www/media.emacsconf.org/2025/ 3--exclude .git + rsync -avzue ssh --exclude \*--original\* --exclude ffmpeg2pass* --exclude \*--reencoded\* ~/proj/emacsconf/$year/cache/ orga@media:/var/www/media.emacsconf.org/$year/ 3--exclude .git fi - rsync -avzue ssh ~/proj/emacsconf/2025/assets/ res:~/current/assets/ + rsync -avzue ssh ~/proj/emacsconf/$year/assets/ res:~/current/assets/ When a talk comes in: 1. Update the talk status to `PROCESSING`. Re-evaluate the schedule draft. 2. Set the file prefix with `emacsconf-set-file-prefix-if-needed` or use `emacsconf-set-file-prefixes`. -3. Download the talk’s files to your local cache (as specified by `emacsconf-cache-dir`). -4. Rename the files with `emacsconf-rename-files`. +3. Download the talk’s files to your local cache (as specified by `emacsconf-cache-dir`) by using <elisp:emacsconf-upload-dired>, finding the .json file, using `emacsconf-upload-scp-command-from-json`, and then pasting the command into a terminal so you can run it in the background. +4. Rename the files with `emacsconf-rename-files` if needed. 5. Use `../update-cache` to update res and backstage. 6. SSH to res. Go to the `~/cache` directory. 1. Start or reuse a `screen` session. |