diff options
| -rw-r--r-- | 2022/organizers-notebook.md | 70 | ||||
| -rw-r--r-- | 2022/organizers-notebook/index.org | 46 |
2 files changed, 92 insertions, 24 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md index 83069630..1a706e91 100644 --- a/2022/organizers-notebook.md +++ b/2022/organizers-notebook.md @@ -167,6 +167,14 @@ talks in the coming weeks. information line. - At some point, use `M-x emacsconf-generate-talk-pages` to update the e-mail address used in the footer. + (let (waiting) + (save-window-excursion + (with-current-buffer (find-file emacsconf-org-file) + (org-map-entries (lambda () (add-to-list 'waiting + (list (org-entry-get (point) "SLUG") + (org-entry-get (point) "ITEM")))) "TODO=\"TO_CONFIRM\""))) + waiting) + ### BLOCKED Prepare email for nudging speakers to send prerec, and inform on upload workflow :timesensitive:needsowner: @@ -394,17 +402,17 @@ 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?](#orgb9c2b00) -- [How much do we want to enrich the wiki with JS?](#org3c898d0) -- [What ideas do we want to borrow from other conferences?](#org0757a4e) -- [Do we want to make the ikiwiki web-editable?](#org8d898e6) -- [How do we want to make better use of Etherpad?](#orga0e588d) -- [Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?](#org1e27028) -- [Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?](#orge9685cf) -- [How many BBB rooms do we want to set up?](#org5a1d383) -- [Do we want to do alt-stream the same way again this year?](#orgbb006c7) -- [Do we want people to advertise any openings with their companies or any work that they're looking for?](#org523eed8) -- [Archive](#org3d7fefa) +- [How do we want to make the full schedule more manageable?](#org91b0b68) +- [How much do we want to enrich the wiki with JS?](#orga0f254b) +- [What ideas do we want to borrow from other conferences?](#org2a3c6df) +- [Do we want to make the ikiwiki web-editable?](#org1e10f54) +- [How do we want to make better use of Etherpad?](#orgffd3d46) +- [Shall we put a generic e-mail address for sending feedback, maybe with different mailtos?](#orge047818) +- [Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them?](#org932e67e) +- [How many BBB rooms do we want to set up?](#orgf266c06) +- [Do we want to do alt-stream the same way again this year?](#org19ae4b0) +- [Do we want people to advertise any openings with their companies or any work that they're looking for?](#org427e1fb) +- [Archive](#org930331e) <a id="overall"></a> @@ -552,7 +560,7 @@ so we know what we need to scramble to do. </table> -<a id="orgb9c2b00"></a> +<a id="org91b0b68"></a> ## How do we want to make the full schedule more manageable? @@ -587,7 +595,7 @@ Shifts will be Sat AM, Sat PM, Sun AM, or Sun PM per track. People can take mult - Console Emacs in a VM with everything set up for publishing to the wiki -<a id="org3c898d0"></a> +<a id="orga0f254b"></a> ## How much do we want to enrich the wiki with JS? @@ -614,7 +622,7 @@ gitolite should have some options to do this Might not be necessary. -<a id="org0757a4e"></a> +<a id="org2a3c6df"></a> ## What ideas do we want to borrow from other conferences? @@ -632,7 +640,7 @@ Might not be necessary. - libreadventure, minetest? -<a id="org8d898e6"></a> +<a id="org1e10f54"></a> ## Do we want to make the ikiwiki web-editable? @@ -649,7 +657,7 @@ Options: - Reduces merge conflict potential -<a id="orga0e588d"></a> +<a id="orgffd3d46"></a> ## How do we want to make better use of Etherpad? @@ -694,7 +702,7 @@ Options: - Embed the IRC channel instead -<a id="org1e27028"></a> +<a id="orge047818"></a> ## Shall we put a generic e-mail address for sending feedback, maybe with different mailtos? @@ -714,7 +722,7 @@ Options: - Private feedback that can be forwarded to the speaker -<a id="orge9685cf"></a> +<a id="org932e67e"></a> ## Can we nudge people to ask IRC questions in a way that will make it easier for us to follow them? @@ -740,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="org5a1d383"></a> +<a id="orgf266c06"></a> ## How many BBB rooms do we want to set up? @@ -754,7 +762,7 @@ Ideas: - Worked fine last time -<a id="orgbb006c7"></a> +<a id="org19ae4b0"></a> ## Do we want to do alt-stream the same way again this year? @@ -766,7 +774,7 @@ Ideas: - Speakers can attend related talks more easily -<a id="org523eed8"></a> +<a id="org427e1fb"></a> ## Do we want people to advertise any openings with their companies or any work that they're looking for? @@ -774,7 +782,7 @@ Ideas: - General audience on a wiki page somewhere? -<a id="org3d7fefa"></a> +<a id="org930331e"></a> ## Archive @@ -1064,6 +1072,22 @@ Backups: - 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. + ## As prerecorded talks come in @@ -1567,7 +1591,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping Make a table of the form -<table id="org788d68b" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> +<table id="org0bdc9f3" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides"> <colgroup> diff --git a/2022/organizers-notebook/index.org b/2022/organizers-notebook/index.org index 9e14102e..84f683d4 100644 --- a/2022/organizers-notebook/index.org +++ b/2022/organizers-notebook/index.org @@ -121,7 +121,34 @@ CLOSED: [2022-10-01 Sat 08:12] e-mail address as <mailto:person@example.com> on the speaker information line. - At some point, use =M-x emacsconf-generate-talk-pages= to update the e-mail address used in the footer. - + +#+begin_src emacs-lisp :results replace table :eval never-export +(let (waiting) + (save-window-excursion + (with-current-buffer (find-file emacsconf-org-file) + (org-map-entries (lambda () (add-to-list 'waiting + (list (org-entry-get (point) "SLUG") + (org-entry-get (point) "ITEM")))) "TODO=\"TO_CONFIRM\""))) + waiting) +#+end_src + +#+RESULTS: +:results: +| wayland | Emacs should become a Wayland compositor | +| dbus | The Wheels on D-Bus | +| eshell | Top 10 reasons why you should be using Eshell | +| tramp | Elisp and the TRAMP: How to NOT write code you don't have to | +| rde | rde Emacs introduction | +| maint | Maintaining the Maintainers: Attribution as an Economic Model for Open Source | +| python | Short hyperlinks to Python docs | +| eev | Bidirectional links with eev | +| orgvm | orgvm: a simple HTTP server for org | +| grail | GRAIL---A Generalized Representation and Aggregation of Information Layers | +| links | Linking headings with org-super-links (poor-man's Zettelkasten) | +| orgyear | This Year in Org | +| survey | Results of the 2022 Emacs Survey | +:end: + *** BLOCKED Prepare email for nudging speakers to send prerec, and inform on upload workflow :timesensitive:needsowner: Blocked by [[*Figure out web-based file upload][Figure out web-based file upload]] @@ -632,6 +659,23 @@ Backups: - 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. + ** As prerecorded talks come in - - Sacha: Parcel out captioning work to volunteers, help them get set up |