summaryrefslogtreecommitdiffstats
path: root/organizers-notebook.md
diff options
context:
space:
mode:
Diffstat (limited to 'organizers-notebook.md')
-rw-r--r--organizers-notebook.md81
1 files changed, 81 insertions, 0 deletions
diff --git a/organizers-notebook.md b/organizers-notebook.md
index 9589cf57..f5d6206b 100644
--- a/organizers-notebook.md
+++ b/organizers-notebook.md
@@ -20,6 +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](#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>
@@ -117,4 +122,80 @@ 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="orge2fe34a"></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="orgac059dd"></a>
+
+## Accept proposals
+
+Setup:
+
+1. Create YYYY/talks.md.
+
+For each talk:
+
+1. Set up &ldquo;Talk abstract&rdquo; and &ldquo;Talk details&rdquo; 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"]