diff options
| -rw-r--r-- | 2022/organizers-notebook.md | 33 | ||||
| -rw-r--r-- | 2022/organizers-notebook.org | 18 |
2 files changed, 44 insertions, 7 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md index 774fd431..20d88c26 100644 --- a/2022/organizers-notebook.md +++ b/2022/organizers-notebook.md @@ -110,7 +110,7 @@ Planned dates and phases: Current phase: No prerecs to process yet, so it's a good time to focus on infrastructure -## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#orgac86a88), Oct 7 for everything :organizers: +## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#orgbb35d27), Oct 7 for everything :organizers: - zaeph: will start reviewing on Sep 21 @@ -150,12 +150,33 @@ We need time after the prerecs get submitted to: - follow up with missing prerecs -## INPROGRESS Find volunteers for tech-checks :needsowner: +## INPROGRESS Find volunteers for tech-checks :zaeph: ### DONE Add entry in 2022/volunteer.md +### INPROGRESS Write protocol for adding tech-checker volunteer + +- Invite volunteer to BBB (ask core organizers) +- Update <prepare.md> with new tech-checker info +- Coach tech-checker on the protocol + + +### INPROGRESS Write the tech-checking protocol (formerly referred to as “tech-checklist”) + +From previous years: + +> - Can you speak and be heard? Is there echo? +> - Can you hear the organizer? +> - Can you share your screen? Is the screen readable? +> - If you plan to show your keystrokes, is that display visible? +> - If you want to share your webcam (optional), can you enable it? Is it visible? Will there likely be distractions in the background? +> - Can you view the collaborative pad? Will you be comfortable reviewing questions on your own (perhaps by keeping it open beside your shared window), or will you need a volunteer to relay questions to you? +> - Can you share contact information (ex: phone number) so that we can get in touch with you in case of technical issues or scheduling changes? +> - Do you need help finding your way around IRC so that you can check into \`#emacsconf-org\`? What is your IRC nickname? + + ## STANDBY Write viewing instructions :zaeph: Extra stuff to consider adding: @@ -254,7 +275,7 @@ Extra stuff to consider adding: <https://emacsconf.org/2022/volunteer> -## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#orgac86a88), Oct 7 for everything :organizers: +## DONE Review the submissions in the pad (see emacsconf-org-private or conf.org for the link) and add any objections or comments by Sept 26 for possible [early speaker notification](#orgbb35d27), Oct 7 for everything :organizers: - zaeph: will start reviewing on Sep 21 @@ -599,7 +620,7 @@ We tried using q56 before, but it was a little too aggressive. Q=32 is the defau ### Test stream setup -[Stream](#org5f90458) +[Stream](#orgc0a238a) ### Set up MPV for captions @@ -916,7 +937,7 @@ Exceptions: ### Send thanks -[Thank you, next steps](#orga138575) +[Thank you, next steps](#orge71d484) ### Extract the opening and closing remarks @@ -1067,7 +1088,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping Make a table of the form -<table id="org7dfd9ba" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> +<table id="org2970f57" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> <colgroup> diff --git a/2022/organizers-notebook.org b/2022/organizers-notebook.org index 575c8265..ca50828e 100644 --- a/2022/organizers-notebook.org +++ b/2022/organizers-notebook.org @@ -85,8 +85,24 @@ We need time after the prerecs get submitted to: - caption videos - capture any extra info - follow up with missing prerecs -** INPROGRESS Find volunteers for tech-checks :needsowner: +** INPROGRESS Find volunteers for tech-checks :zaeph: *** DONE Add entry in 2022/volunteer.md +*** INPROGRESS Write protocol for adding tech-checker volunteer +- Invite volunteer to BBB (ask core organizers) +- Update [[file:prepare.md::Tech-check]] with new tech-checker info +- Coach tech-checker on the protocol +*** INPROGRESS Write the tech-checking protocol (formerly referred to as “tech-checklist”) +From previous years: +#+begin_quote +- Can you speak and be heard? Is there echo? +- Can you hear the organizer? +- Can you share your screen? Is the screen readable? +- If you plan to show your keystrokes, is that display visible? +- If you want to share your webcam (optional), can you enable it? Is it visible? Will there likely be distractions in the background? +- Can you view the collaborative pad? Will you be comfortable reviewing questions on your own (perhaps by keeping it open beside your shared window), or will you need a volunteer to relay questions to you? +- Can you share contact information (ex: phone number) so that we can get in touch with you in case of technical issues or scheduling changes? +- Do you need help finding your way around IRC so that you can check into `#emacsconf-org`? What is your IRC nickname? +#+end_quote ** STANDBY Write viewing instructions :zaeph: Extra stuff to consider adding: - Suggestions for mpv-filter to invert colourscape. |