summaryrefslogtreecommitdiffstats
path: root/2022/organizers-notebook.md
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2022-10-07 14:50:00 -0400
committerSacha Chua <sacha@sachachua.com>2022-10-07 14:50:00 -0400
commitd5c94e3e7bb2f099e2d2b374e776555b688978e1 (patch)
treef2280061d710d2a1697cf411e35b248e72f5f363 /2022/organizers-notebook.md
parent0a7543c8bde5874ac2dde582ee60e7e5b1908268 (diff)
downloademacsconf-wiki-d5c94e3e7bb2f099e2d2b374e776555b688978e1.tar.xz
emacsconf-wiki-d5c94e3e7bb2f099e2d2b374e776555b688978e1.zip
Reorganize, add tocs
Diffstat (limited to '2022/organizers-notebook.md')
-rw-r--r--2022/organizers-notebook.md267
1 files changed, 125 insertions, 142 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md
index 3bfe56bc..9361a991 100644
--- a/2022/organizers-notebook.md
+++ b/2022/organizers-notebook.md
@@ -101,30 +101,28 @@ Planned dates and phases:
Current phase: No prerecs to process yet, so it's a good time to focus
on infrastructure
-- [Time-sensitive](#org2db84f2)
-- [Projects and other long-running tasks](#org1e6b753)
-- [Projects to bear in mind but which are not actual](#orgd21e52c)
-- [Find volunteers for tech-checks](#org53ebeba):zaeph:
-- [Add nice-to-have stuff to prepare.md](#orgce43a0a):zaeph:
-- [Write viewing instructions](#org6e7cc99):zaeph:
-- [Add category tags and possibly links between talks across 2022 and all previous years](#org48fafc0):needsowner:wiki:
-- [Archive](#orga41dec5):ARCHIVE:
+- [Time-sensitive](#org3a2dd47)
+- [Projects and other long-running tasks](#org485507e)
+- [Projects to bear in mind but which are not actual](#maybe-projects)
+- [Find volunteers for tech-checks](#tech-checks):zaeph:
+- [Update viewing instructions and watch pages](#write-viewing):zaeph:
+- [Add category tags and possibly links between talks across 2022 and all previous years](#link-pages):needsowner:wiki:
-<a id="org2db84f2"></a>
+<a id="org3a2dd47"></a>
## Time-sensitive
Ordered chronologically (and therefore by importance).
-- [Volunteer communications: E-mail update for Oct 9, 2022](#org23e51b3):email:volunteers:
-- [Remind people about confirming e-mail communications](#org32b3b9e):sachac:email:speakers:
-- [Send people schedule information and doublecheck their availability/Q&A preference](#org2ab6c80):sachac:email:speakers:
-- [Send program-published email for emacsconf-discuss](#org70e448d):needsowner:timesensitive:email:
-- [Prepare email for nudging speakers to send prerec, and inform on upload workflow](#org231f141):timesensitive:needsowner:
+- [Volunteer communications: E-mail update for Oct 9, 2022](#volunteer-2022-10-09):email:volunteers:
+- [Remind people about confirming e-mail communications](#confirm-email):sachac:email:speakers:
+- [Send people schedule information and doublecheck their availability/Q&A preference](#check-sched):sachac:email:speakers:
+- [Send program-published email for emacsconf-discuss](#announce-program):needsowner:timesensitive:email:
+- [Prepare email for nudging speakers to send prerec, and inform on upload workflow](#mail-upload):timesensitive:needsowner:
-<a id="org23e51b3"></a>
+<a id="volunteer-2022-10-09"></a>
### Volunteer communications: E-mail update for Oct 9, 2022 :email:volunteers:
@@ -152,19 +150,19 @@ Help wanted / upcoming tasks:
You're receiving this e-mail because you're on the emacsconf-org mailing list.
-<a id="org32b3b9e"></a>
+<a id="confirm-email"></a>
### TODO Remind people about confirming e-mail communications :sachac:email:speakers:
-Look for the TO\_CONFIRM status
+Look for the TO\_CONFIRM status in conf.org, probably include in schedule e-mail
-<a id="org2ab6c80"></a>
+<a id="check-sched"></a>
### TODO Send people schedule information and doublecheck their availability/Q&A preference :sachac:email:speakers:
-<a id="org70e448d"></a>
+<a id="announce-program"></a>
### TODO Send program-published email for emacsconf-discuss :needsowner:timesensitive:email:
@@ -191,25 +189,24 @@ to their availability, and will add the allocated time slots for the
talks in the coming weeks.
-<a id="org231f141"></a>
+<a id="mail-upload"></a>
### BLOCKED Prepare email for nudging speakers to send prerec, and inform on upload workflow :timesensitive:needsowner:
Blocked by [Figure out web-based file upload](#upload)
-<a id="org1e6b753"></a>
+<a id="org485507e"></a>
## Projects and other long-running tasks
- [Figure out web-based file upload](#upload):needsowner:zaeph:bandali:
-- [Prepare for prerecs](#org2bbef8d):zaeph:
-- [Delete all the EmacsConf BBB rooms from last year](#orgc2e46a9):chore:bbb:
-- [Investigate streaming options, maybe OBS in the cloud](#obscloud):corwin:zaeph:
-- [Work on the OBS scenes](#org73749aa):zaeph:corwin:
-- [Create Org heading for scheduling caption team's live IRC duty shifts](#org8582971):dto:
-- [Move scheduling and publishing code to Emacs on a VPS so that other people can help out](#org8a922d4):sachac:
-- [Add nice-to-have stuff to prepare.md](#org8d8ea6c):zaeph:
+- [Prepare for prerecs](#prepare-prerec-process):zaeph:
+- [Delete all the EmacsConf BBB rooms from last year](#bbb-cleanup):chore:bbb:
+- [Investigate streaming options, maybe OBS in the cloud](#streaming):corwin:zaeph:
+- [Work on the OBS scenes](#obs-scenes):zaeph:corwin:
+- [Move scheduling and publishing code to Emacs on a VPS so that other people can help out](#publishing-vps):sachac:
+- [Add nice-to-have stuff to prepare.md](#extra-prepare):zaeph:
Ordered by importance.
@@ -263,7 +260,7 @@ Considerations:
#### TODO Notify speakers when the final solution is available
-<a id="org2bbef8d"></a>
+<a id="prepare-prerec-process"></a>
### TODO Prepare for prerecs :zaeph:
@@ -283,7 +280,7 @@ We need time after the prerecs get submitted to:
- follow up with missing prerecs
-<a id="orgc2e46a9"></a>
+<a id="bbb-cleanup"></a>
### TODO Delete all the EmacsConf BBB rooms from last year :chore:bbb:
@@ -291,7 +288,7 @@ For the admins on BBB. The list is accessible here: [Organization Settings](htt
Should take no more than ~20′.
-<a id="obscloud"></a>
+<a id="streaming"></a>
### TODO Investigate streaming options, maybe OBS in the cloud :corwin:zaeph:
@@ -316,21 +313,14 @@ Resources:
#### TODO corwin: recruit at least one more person to help operate the "video bouncer" :corwin:
-<a id="org73749aa"></a>
+<a id="obs-scenes"></a>
### TODO Work on the OBS scenes :zaeph:corwin:
- [ ] corwin is out from Nov 11-20, and we should start working on them before then.
-<a id="org8582971"></a>
-
-### CANCELLED Create Org heading for scheduling caption team's live IRC duty shifts :dto:
-
-See [Shifts](#shifts)
-
-
-<a id="org8a922d4"></a>
+<a id="publishing-vps"></a>
### Move scheduling and publishing code to Emacs on a VPS so that other people can help out :sachac:
@@ -343,11 +333,13 @@ Where:
- front? my own VPS?
+ Nice if there's an Ansible playbook
+
sachac's notes:
<file:///home/sacha/code/docker/emacsconf-publish/>
-<a id="org8d8ea6c"></a>
+<a id="extra-prepare"></a>
### STANDBY Add nice-to-have stuff to prepare.md :zaeph:
@@ -355,7 +347,7 @@ Where:
- SIL fonts choice
-<a id="orgd21e52c"></a>
+<a id="maybe-projects"></a>
## Projects to bear in mind but which are not actual
@@ -365,8 +357,11 @@ Where:
We’re not sure if we’re going to get a presentation or a prerec for them
this year, but we need to keep this at the back of our minds.
+Note on how DebConf handled incidents:
+<https://www.mail-archive.com/search?l=debconf-team@lists.debian.org&q=subject:%22Re%5C%3A+DebConf+21+Incident+Response%22&o=newest&f=1>
+
-<a id="org53ebeba"></a>
+<a id="tech-checks"></a>
## INPROGRESS Find volunteers for tech-checks :zaeph:
@@ -395,33 +390,31 @@ From previous years:
> - Do you need help finding your way around IRC so that you can check into \`#emacsconf-org\`? What is your IRC nickname?
-<a id="orgce43a0a"></a>
-
-## STANDBY Add nice-to-have stuff to prepare.md :zaeph:
-
-- org-reveal config
-- SIL fonts choice
-
+<a id="write-viewing"></a>
-<a id="org6e7cc99"></a>
-
-## STANDBY Write viewing instructions :zaeph:
+## STANDBY Update viewing instructions and watch pages :zaeph:
Extra stuff to consider adding:
- Suggestions for mpv-filter to invert colourscape.
+Also add to watch page
-<a id="org48fafc0"></a>
-
-## TODO Add category tags and possibly links between talks across 2022 and all previous years :needsowner:wiki:
-List of talks: <https://emacsconf.org/talks/>
+<a id="link-pages"></a>
+## TODO Add category tags and possibly links between talks across 2022 and all previous years :needsowner:wiki:
-<a id="orga41dec5"></a>
+- Prerequisite: Can edit wiki pages (<https://emacsconf.org/edit/>)
+- Goal: Make it easier for people to discover interesting related talks
-## Archive :ARCHIVE:
+- List of talks for EmacsConf 2022: <https://emacsconf.org/talks/>
+- List of talks: <https://emacsconf.org/talks/>
+- List of categories: <https://emacsconf.org/CategoryCategory/>
+- To add something to a category, add `\[[!taglink CategoryName]]` to the bottom of its talk page (ex: 2022/talks/maint.md is in CategoryCommunity)
+- You can create new categories by making up new CategoryNames.
+- You can also link to a talk with a link like this: `\[[/2022/talks/maint|Maintaining the Maintainers: Attribution as an Economic Model for Open Source]]`
+ You can make a new heading called `# Related talks`
<a id="decisions"></a>
@@ -429,17 +422,15 @@ List of talks: <https://emacsconf.org/talks/>
# Things to figure out / decisions to make
- [How fancy do we want to get this year? (overall prioritization)](#overall)
-- [How do we want to make the full schedule more manageable?](#org6d9894a)
-- [How much do we want to enrich the wiki with JS?](#org671bd0e)
-- [What ideas do we want to borrow from other conferences?](#orgbe5bf61)
-- [Do we want to make the ikiwiki web-editable?](#orgf9f0808)
-- [How do we want to make better use of Etherpad?](#org2e44f4b)
-- [Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?](#org538d010)
-- [Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?](#org277efeb)
-- [How many BBB rooms do we want to set up?](#orgdf41952)
-- [Do we want to do alt-stream the same way again this year?](#org8b62354)
-- [Do we want people to advertise any openings with their companies or any work that they're looking for?](#org6305952)
-- [Archive](#org07028ad)
+- [How do we want to make the full schedule more manageable?](#sched-decision)
+- [How much do we want to enrich the wiki with JS?](#wiki-design)
+- [What ideas do we want to borrow from other conferences?](#other-confs)
+- [Do we want to make the ikiwiki web-editable?](#cgi)
+- [How do we want to make better use of Etherpad?](#pad-decision)
+- [Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?](#irc-markers)
+- [How many BBB rooms do we want to set up?](#bbb-rooms)
+- [Do we want people to advertise any openings with their companies or any work that they're looking for?](#advertising)
+- [Decision archive](#decision-archive)
<a id="overall"></a>
@@ -587,7 +578,7 @@ so we know what we need to scramble to do.
</table>
-<a id="org6d9894a"></a>
+<a id="sched-decision"></a>
## How do we want to make the full schedule more manageable?
@@ -617,12 +608,12 @@ Shifts will be Sat AM, Sat PM, Sun AM, or Sun PM per track. People can take mult
- Figure out how hosting can be done in shifts
- Add notes in one place
- Figure out how streaming can be done in shifts: OBS in the cloud?
- - [Investigate streaming options, maybe OBS in the cloud](#obscloud)
+ - [Investigate streaming options, maybe OBS in the cloud](#streaming)
- Figure out how publishing can be done in shifts
- Console Emacs in a VM with everything set up for publishing to the wiki
-<a id="org671bd0e"></a>
+<a id="wiki-design"></a>
## How much do we want to enrich the wiki with JS?
@@ -649,7 +640,7 @@ gitolite should have some options to do this
Might not be necessary.
-<a id="orgbe5bf61"></a>
+<a id="other-confs"></a>
## What ideas do we want to borrow from other conferences?
@@ -667,7 +658,7 @@ Might not be necessary.
- libreadventure, minetest?
-<a id="orgf9f0808"></a>
+<a id="cgi"></a>
## Do we want to make the ikiwiki web-editable?
@@ -684,7 +675,7 @@ Options:
- Reduces merge conflict potential
-<a id="org2e44f4b"></a>
+<a id="pad-decision"></a>
## How do we want to make better use of Etherpad?
@@ -729,30 +720,12 @@ Options:
- Embed the IRC channel instead
-<a id="org538d010"></a>
-
-## Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?
-
-Pain points:
-
-- Many talk pages don't have public e-mail addresses, so it takes a
- little extra work (or is sometimes impossible) for people to follow
- up if they have questions
-
-Options:
-
-- Do nothing (current)
-- Add a mailto link to emacsconf-discuss that prepopulates the subject
-- Add a mailto link to emacsconf-org
- - Wider discussion
-- Add a mailto to emacsconf-org-private
- - Private feedback that can be forwarded to the speaker
-
-
-<a id="org277efeb"></a>
+<a id="irc-markers"></a>
## Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?
+Two tracks mean two IRC channels with lots of space for Q&A, so this may become less of an issue
+
Pain points:
- Q&A/discussions often overlap with the next talks
@@ -775,7 +748,7 @@ Ideas:
- Maybe a volunteer can have an ERC command that copies a question into a buffer, or even into the Etherpad
-<a id="orgdf41952"></a>
+<a id="bbb-rooms"></a>
## How many BBB rooms do we want to set up?
@@ -789,19 +762,7 @@ Ideas:
- Worked fine last time
-<a id="org8b62354"></a>
-
-## Do we want to do alt-stream the same way again this year?
-
-- Alt stream joins the current session and then continues with it until the Q&A finishes; people join the BBB room if they want to ask questions
- - Nice and convivial, Q&A still gets captured
- - Inertia means most people get the main message
-- Multiple streams with more space between talks, people choose which stream they want to watch
- - How other conferences do it
- - Speakers can attend related talks more easily
-
-
-<a id="org6305952"></a>
+<a id="advertising"></a>
## Do we want people to advertise any openings with their companies or any work that they're looking for?
@@ -809,9 +770,9 @@ Ideas:
- General audience on a wiki page somewhere?
-<a id="org07028ad"></a>
+<a id="decision-archive"></a>
-## Archive
+## Decision archive
### Where should volunteers e-mail?
@@ -831,6 +792,36 @@ Ideas:
specific reasons, rather than the other way around
+### CANCELLED Do we want to do alt-stream the same way again this year?
+
+Superseded by decision to have multiple tracks
+
+- Alt stream joins the current session and then continues with it until the Q&A finishes; people join the BBB room if they want to ask questions
+ - Nice and convivial, Q&A still gets captured
+ - Inertia means most people get the main message
+- Multiple streams with more space between talks, people choose which stream they want to watch
+ - How other conferences do it
+ - Speakers can attend related talks more easily
+
+
+### DONE Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?
+
+Pain points:
+
+- Many talk pages don't have public e-mail addresses, so it takes a
+ little extra work (or is sometimes impossible) for people to follow
+ up if they have questions
+
+Options:
+
+- Do nothing (current)
+- Add a mailto link to emacsconf-discuss that prepopulates the subject
+- Add a mailto link to emacsconf-org
+ - Wider discussion
+- **Add a mailto to emacsconf-org-private**
+ - Private feedback that can be forwarded to the speaker
+
+
<a id="roles"></a>
# Roles needed
@@ -1092,38 +1083,18 @@ Interested in a shift? Please e-mail <mailto:emacsconf-org-private@gnu.org> and
# Other tasks and processes
-
-## DONE Sacha: Organize volunteer information :sachac:
+- [As prerecorded talks come in](#prerec-process)
+- [When a talk is captioned](#org01e0d53)
+- [Other tasks before the conference](#before)
+- [During the conference](#during-conference)
+- [After the conference](#after-conference)
+- [In case of](#exceptions)
-## Once talks are approved
-
-- sacha: Publish initial talk information pages
-- Double-check talk pages, format them nicely
-- Publish draft schedule
-- Confirm e-mail communication with all of the speakers
-
-Process for accepting a talk:
-
-- Create subtree for talk and populate it with properties.
- - Required: CUSTOM\_ID SLUG NAME NAME\_SHORT EMAIL AVAILABILITY Q\_AND\_A TRACK MAX\_TIME
- - Optional: PRONOUNS PRONUNCIATION IRC PUBLIC\_EMAIL MIN\_TIME EMERGENCY
- - Can be validated with `emacsconf-validate-talk-subtree`
- - Add a talk abstract subtree
-- Add it to emacsconf-schedule-plan and fiddle with it until the flow looks good
-- Execute the draft-schedule block to update the schedule in the Org file
-- Add the talk page to the wiki with `emacsconf-add-talk-page`.
-- Stage, commit, and push the wiki files. Make sure to add the talk page and the info pages.
-- Doublecheck the wiki page on the web, since the e-mail refers to it.
-- E-mail the speaker the acceptance by using `emacsconf-draft-acceptance-for-email-group` from `organizers-notebook/`.
-- Log the acceptance using `C-c C-z` in the talk subtree in `conf.org`, noting the number of minutes.
-- Change the status to TO\_CONFIRM.
-
+<a id="prerec-process"></a>
## As prerecorded talks come in
--
-
- Sacha: Parcel out captioning work to volunteers, help them get set up
- Volunteers: Caption pre-recorded videos (usually starting from autogenerated ones for easier work)
- Make sure all the links/resources mentioned are written down somewhere (web page and enriched captions for pasting into #emacsconf-accessible)
@@ -1142,10 +1113,16 @@ Usage: `compress-video.sh original-file output-file`:
We tried using q56 before, but it was a little too aggressive. Q=32 is the default and is probably a reasonable space vs. quality compromise.
+<a id="org01e0d53"></a>
+
## When a talk is captioned
-- Upload talk
+- Combine captions with talk
+- Upload captions to YT and Toobnix
+- Prepare captions for wiki inclusion
+
+<a id="before"></a>
## Other tasks before the conference
@@ -1208,6 +1185,8 @@ Links:
rsync -avzue ssh front:/var/www/media.emacsconf.org/2021/protected/*--main.webm .
+<a id="during-conference"></a>
+
## During the conference
@@ -1466,6 +1445,8 @@ Exceptions:
- bandali figures out the downstream
+<a id="after-conference"></a>
+
## After the conference
@@ -1622,7 +1603,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping
Make a table of the form
-<table id="org66ae3dc" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="orge4a8e24" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
<colgroup>
@@ -1712,6 +1693,8 @@ Make a table of the form
### BLOCKED Downsize the server :bandali:
+<a id="exceptions"></a>
+
## In case of