summaryrefslogtreecommitdiffstats
path: root/2022/organizers-notebook.md
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2022-10-04 10:05:21 -0400
committerSacha Chua <sacha@sachachua.com>2022-10-04 10:05:21 -0400
commit51ef1e83d8d54d3b561a0e739d85845af7518f53 (patch)
tree8921d055df4a53ef59d65eba76bd886e000a191f /2022/organizers-notebook.md
parentf85c2c2af5f5e4192b52804a277ec11d74c7d6a5 (diff)
downloademacsconf-wiki-51ef1e83d8d54d3b561a0e739d85845af7518f53.tar.xz
emacsconf-wiki-51ef1e83d8d54d3b561a0e739d85845af7518f53.zip
add prioritization matrix
Diffstat (limited to '2022/organizers-notebook.md')
-rw-r--r--2022/organizers-notebook.md228
1 files changed, 212 insertions, 16 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md
index 533c9767..736f956f 100644
--- a/2022/organizers-notebook.md
+++ b/2022/organizers-notebook.md
@@ -105,6 +105,22 @@ on infrastructure
Ordered chronologically (and therefore by importance).
+### TODO Prepare to publish schedule :sachac:wiki:
+
+- Should be understandable as plain text
+- Ideally responsive to take advantage of more screen space on monitors while still being understandable on mobile
+- Organize by tracks and then days
+- Links to jump to a track and day
+- Graphics to make it easier for people to see nearby talk options
+- Optionally, graphical view on talk pages as well (might need to publish a JSON somewhere to front)
+
+
+#### TODO Set up main schedule
+
+
+#### TODO Set up talk page navigation
+
+
### TODO Send program-published email for emacsconf-discuss :needsowner:timesensitive:email:
@@ -151,16 +167,9 @@ Blocked by [Figure out web-based file upload](#upload)
Look for the TO\_CONFIRM status
-### TODO Send people schedule information and doublecheck their availability/Q&A preference :sachac:email:
-
+### BLOCKED Send people schedule information and doublecheck their availability/Q&A preference :sachac:email:
-## Projects to bear in mind but which are not actual
-
-
-### STANDBY Find a way to accommodate a specific return-speaker
-
-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.
+Waiting for schedule to be finalized
## Projects and other long-running tasks
@@ -233,7 +242,7 @@ We need time after the prerecs get submitted to:
- follow up with missing prerecs
-### TODO Investigate streaming options, maybe OBS in the cloud :corwin:
+### TODO Investigate streaming options, maybe OBS in the cloud :corwin:zaeph:
- Issue: zaeph was dropping frames and couldn’t pay attention to as many things as he wanted
- Issue: corwin needs assistance to not be locked in his chair for the whole conf. Premptively, zaeph can do it by broadcasting OBS scenes via the rtmp (instead of just his webcam).
@@ -306,6 +315,15 @@ git clone git@git.emacsconf.org:emacsconf-2022-private
- SIL fonts choice
+## Projects to bear in mind but which are not actual
+
+
+### STANDBY Find a way to accommodate a specific return-speaker
+
+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.
+
+
## TODO Write viewing instructions :zaeph:
Extra stuff to consider adding:
@@ -365,9 +383,166 @@ 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?](#org0c837b2)
+- [How much do we want to enrich the wiki with JS?](#org118a906)
+- [What ideas do we want to borrow from other conferences?](#org20bb81a)
+- [Do we want to make the ikiwiki web-editable?](#orgecaf2b4)
+- [How do we want to make better use of Etherpad?](#orge12919a)
+- [Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?](#org959762d)
+- [Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?](#org7f3263f)
+- [How many BBB rooms do we want to set up?](#orgbff646e)
+- [Do we want to do alt-stream the same way again this year?](#org767d179)
+- [Do we want people to advertise any openings with their companies or any work that they're looking for?](#orgaa42c88)
+- [Archive](#org0b92419)
+
+
+<a id="overall"></a>
+
+## How fancy do we want to get this year? (overall prioritization)
+
+<table border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+
+
+<colgroup>
+<col class="org-left" />
+
+<col class="org-left" />
+
+<col class="org-left" />
+
+<col class="org-left" />
+</colgroup>
+<thead>
+<tr>
+<th scope="col" class="org-left">&#xa0;</th>
+<th scope="col" class="org-left">Good</th>
+<th scope="col" class="org-left">Better</th>
+<th scope="col" class="org-left">Best</th>
+</tr>
+</thead>
+
+<tbody>
+<tr>
+<td class="org-left">upload</td>
+<td class="org-left">FTP</td>
+<td class="org-left"><b>Z: web-based</b></td>
+<td class="org-left">auto-encoded, preview (SReview?)</td>
+</tr>
+
+
+<tr>
+<td class="org-left">schedule</td>
+<td class="org-left">one track</td>
+<td class="org-left"><b>S: two tracks</b></td>
+<td class="org-left">aligned times, full roster</td>
+</tr>
+
+
+<tr>
+<td class="org-left">schedule view</td>
+<td class="org-left">text table</td>
+<td class="org-left">S: imagemap fallback</td>
+<td class="org-left"><b>S: responsive HTML or SVG</b></td>
+</tr>
+
+
+<tr>
+<td class="org-left">prerec</td>
+<td class="org-left">play original</td>
+<td class="org-left">Z: normalize audio</td>
+<td class="org-left"><b>S: post as soon as talk is live</b></td>
+</tr>
+
+
+<tr>
+<td class="org-left">stream</td>
+<td class="org-left">ffmpeg from computer</td>
+<td class="org-left">OBS</td>
+<td class="org-left"><b>Z: OBS in cloud, switchable hosts</b></td>
+</tr>
+
+
+<tr>
+<td class="org-left">host</td>
+<td class="org-left">no host, speaker reads pad</td>
+<td class="org-left"><b>host reads pad</b></td>
+<td class="org-left">host monitors IRC as well</td>
+</tr>
+
+
+<tr>
+<td class="org-left">watch page</td>
+<td class="org-left">stream</td>
+<td class="org-left">+ IRC</td>
+<td class="org-left">+ talk info, maybe even pad</td>
+</tr>
+
+
+<tr>
+<td class="org-left">pad</td>
+<td class="org-left">one pad for conf</td>
+<td class="org-left">one pad per talk, wikimedia</td>
+<td class="org-left"><b>one pad per talk, self-hosted</b> so we can access API</td>
+</tr>
+
+
+<tr>
+<td class="org-left">IRC</td>
+<td class="org-left">#emacsconf, -org</td>
+<td class="org-left"><b>tracks, hallway, org</b></td>
+<td class="org-left">IRC volunteer copying to pads; maybe even IRC bots</td>
+</tr>
+
+
+<tr>
+<td class="org-left">sched update</td>
+<td class="org-left"><b>S: publish at start</b></td>
+<td class="org-left">update main sched</td>
+<td class="org-left">update talk pages</td>
+</tr>
+
+
+<tr>
+<td class="org-left">talk pages</td>
+<td class="org-left"><b>S: link to stream, pad, IRC</b></td>
+<td class="org-left"><b>link to prerec when live</b></td>
+<td class="org-left">embed stream, pad, IRC, prerec</td>
+</tr>
+
+
+<tr>
+<td class="org-left">other streams</td>
+<td class="org-left">480p</td>
+<td class="org-left">+ Toobnix</td>
+<td class="org-left"><b>S: + YouTube</b></td>
+</tr>
+
+
+<tr>
+<td class="org-left">other platforms</td>
+<td class="org-left"><b>S: Toobnix &amp; YT after event</b></td>
+<td class="org-left">&#xa0;</td>
+<td class="org-left">S: Toobnix + YT when live</td>
+</tr>
+
+
+<tr>
+<td class="org-left">wiki</td>
+<td class="org-left">plain text, markdown</td>
+<td class="org-left"><b>S: some JS enrichment</b></td>
+<td class="org-left">more JS and CSS, embeds, videoplayer</td>
+</tr>
+</tbody>
+</table>
+
+
+<a id="org0c837b2"></a>
## How do we want to make the full schedule more manageable?
+<https://emacsconf.org/2022/decisions/#schedule>
+
- 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?
@@ -376,6 +551,8 @@ List of talks: <https://emacsconf.org/talks/>
- Console Emacs in a VM with everything set up for publishing to the wiki
+<a id="org118a906"></a>
+
## How much do we want to enrich the wiki with JS?
Ideas to consider:
@@ -401,6 +578,8 @@ gitolite should have some options to do this
Might not be necessary.
+<a id="org20bb81a"></a>
+
## What ideas do we want to borrow from other conferences?
- FOSDEM had a conference track
@@ -408,14 +587,17 @@ Might not be necessary.
- DebConf
- Thorough documentation at <https://debconf-video-team.pages.debian.net/docs/>
- <https://debconf-video-team.pages.debian.net/docs/online_volunteer_roles.html>
+ - Ansible: <https://salsa.debian.org/debconf-video-team/ansible> , <https://debconf-video-team.pages.debian.net/ansible>
- SReview for cutting videos?
- <https://wiki.debian.org/Teams/DebConf/Video/Subtitles>
- Pentabarf <https://lists.debian.org/debconf-team/2008/08/msg00147.html>
-
+ - Schedule shows local time and DebConf time: <https://debconf21.debconf.org/schedule/>
- LibrePlanet <https://libreplanet.org/2022/>
- libreadventure, minetest?
+<a id="orgecaf2b4"></a>
+
## Do we want to make the ikiwiki web-editable?
Pain points:
@@ -431,6 +613,8 @@ Options:
- Reduces merge conflict potential
+<a id="orge12919a"></a>
+
## How do we want to make better use of Etherpad?
Pain points:
@@ -474,6 +658,8 @@ Options:
- Embed the IRC channel instead
+<a id="org959762d"></a>
+
## Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?
Pain points:
@@ -492,6 +678,8 @@ Options:
- Private feedback that can be forwarded to the speaker
+<a id="org7f3263f"></a>
+
## Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?
Pain points:
@@ -516,6 +704,8 @@ Ideas:
- Maybe a volunteer can have an ERC command that copies a question into a buffer, or even into the Etherpad
+<a id="orgbff646e"></a>
+
## How many BBB rooms do we want to set up?
- One per talk
@@ -528,6 +718,8 @@ Ideas:
- Worked fine last time
+<a id="org767d179"></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
@@ -538,12 +730,16 @@ Ideas:
- Speakers can attend related talks more easily
+<a id="orgaa42c88"></a>
+
## Do we want people to advertise any openings with their companies or any work that they're looking for?
- Speakers on their page?
- General audience on a wiki page somewhere?
+<a id="org0b92419"></a>
+
## Archive
@@ -684,7 +880,7 @@ Saturday
<tr>
<td class="org-left">Host</td>
<td class="org-left">zaeph</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">zaeph</td>
<td class="org-left">bandali</td>
<td class="org-left">&#xa0;</td>
</tr>
@@ -693,7 +889,7 @@ Saturday
<tr>
<td class="org-left">Streamer</td>
<td class="org-left">zaeph</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">zaeph</td>
<td class="org-left">bandali</td>
<td class="org-left">&#xa0;</td>
</tr>
@@ -756,7 +952,7 @@ Sunday
<tr>
<td class="org-left">Host</td>
<td class="org-left">zaeph</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">zaeph</td>
<td class="org-left">bandali</td>
<td class="org-left">&#xa0;</td>
</tr>
@@ -765,7 +961,7 @@ Sunday
<tr>
<td class="org-left">Streamer</td>
<td class="org-left">zaeph</td>
-<td class="org-left">&#xa0;</td>
+<td class="org-left">zaeph</td>
<td class="org-left">bandali</td>
<td class="org-left">&#xa0;</td>
</tr>
@@ -1335,7 +1531,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping
Make a table of the form
-<table id="orgae713f8" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="org0373b4e" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
<colgroup>