diff options
Diffstat (limited to '')
| -rw-r--r-- | organizers-notebook.md | 55 | ||||
| -rw-r--r-- | organizers-notebook/index.org | 85 |
2 files changed, 136 insertions, 4 deletions
diff --git a/organizers-notebook.md b/organizers-notebook.md index 9dbd7acd..f5d6206b 100644 --- a/organizers-notebook.md +++ b/organizers-notebook.md @@ -20,7 +20,11 @@ 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](#orga1b94cf) + - [Process proposals](#orge2fe34a) + - [Accept proposals](#orgac059dd) + - [Draft schedule](#draft-schedule) +- [Other process notes](#other) + - [Adding another user to BBB](#bbb-user) <a id="starting-up-the-conference-planning-process"></a> @@ -118,9 +122,10 @@ 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. +- Put the speaker introduction right after the talk description for easier web page copying. -<a id="orga1b94cf"></a> +<a id="orge2fe34a"></a> ## Process proposals @@ -148,3 +153,49 @@ When proposals come in: TRACK, TIMEZONE, CATEGORY, DATE\_SUBMITTED, PUBLIC\_EMAIL + +<a id="orgac059dd"></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. 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` + + +<a id="draft-schedule"></a> + +## Draft schedule + +- Create entries for opening and closing remarks + - FIXED: t + - SCHEDULED + - TIME: 10 + - BUFFER: 0 + - CUSTOM\_ID: + - SLUG: + - Q\_AND\_A: pad +- Create draft-schedule section in the public organizers notebook for the year +- Add missing items to plan + + +<a id="other"></a> + +# Other process notes + + +<a id="bbb-user"></a> + +## Adding another user to BBB + + ssh bbb.emacsverse.org + docker exec -it greenlight-v2 bundle exec rake user:create["USERNAME","EMAIL","PASSWORD","user"] + diff --git a/organizers-notebook/index.org b/organizers-notebook/index.org index d550f784..e3781998 100644 --- a/organizers-notebook/index.org +++ b/organizers-notebook/index.org @@ -119,6 +119,12 @@ 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. +- Put the speaker introduction right after the talk description for easier web page copying. +** Announce + +- Post CFP to emacsconf-discuss, reddit.com/r/emacs, and in Emacs News +- Submit to https://foss.events/ + ** Process proposals 1. In the private repository, create a conf.org. @@ -155,5 +161,80 @@ Setup: 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. +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~ +** Draft schedule +:PROPERTIES: +:CUSTOM_ID: draft-schedule +:END: +- Create entries for opening and closing remarks + - FIXED: t + - SCHEDULED + - TIME: 10 + - BUFFER: 0 + - CUSTOM_ID: + - SLUG: + - Q_AND_A: pad +- Create draft-schedule section in the public organizers notebook for the year +- Add missing items to plan +** Set up backstage and upload + +See [[emacsconf-ansible:README.org]]. +** Post the schedule + +- [[elisp:(setq emacsconf-publishing-phase 'schedule)]] +- elisp:emacsconf-publish-info-pages +- elisp:emacsconf-publish-schedule-org-files +- elisp:emacsconf-ical-generate-all +- Update talks.md to refer to watch.md as well + + +** Process uploaded files + +Basic setup: + +1. Set up the media server and symlinks: [[emacsconf-ansible:README.org]] (Media). +2. Set up the prerec processing areas on res: [[emacsconf-ansible:README.org]] (Processing prerecs). +2. Set up the caption processor on res: [[emacsconf-ansible:README.org]] (Captioning). + +Process: + +1. Review uploaded files with elisp:emacsconf-upload-dired +2. Open the JSON for the file you want to process and use elisp:emacsconf-upload-copy-from-json . + If more than one file uses the same extension, provide a suffix to disambiguate them. +3. On res: + 1. Create a directory ~/current/files/$slug. + 2. Copy the uploaded file from ~/cache as =$video_slug--original.$extension=, or use =rename-original.sh $slug $file=. + 3. Call =process-prerec.sh $file=. +4. When the screens are finished, do locally: + 1. update-cache on my computer. + 2. elisp:emacsconf-publish-cache-video-data or elisp:emacsconf-cache-all-video-data + 3. elisp:emacsconf-publish-backstage-index +** Getting ready for captions + +Onboarding: + +- Add captioner to conf.org with the ~:caption:~ tag, under a Volunteers heading with the ~volunteer~ tag. Make sure the ~EMAIL~ property is set. +- Add captioner to emacsconf-org mailing list. +- Send backstage information elisp:emacsconf-mail-backstage-info-to-volunteer . (Can be sent to all captioning volunteers with elisp:emacsconf-mail-backstage-info-to-captioning-volunteers) + +* Other process notes +:PROPERTIES: +:CUSTOM_ID: other +:END: +** Adding another user to BBB +:PROPERTIES: +:CUSTOM_ID: bbb-user +:END: + +#+begin_src ssh :eval no +ssh bbb.emacsverse.org +docker exec -it greenlight-v2 bundle exec rake user:create["USERNAME","EMAIL","PASSWORD","user"] +#+end_src +** Ansible + +#+begin_src sh :eval no +git clone git@git.emacsconf.org:pub/emacsconf-ansible +#+end_src |