summaryrefslogtreecommitdiffstats
path: root/2022
diff options
context:
space:
mode:
authorLeo Vivier <zaeph@zaeph.net>2022-10-01 00:14:19 +0200
committerLeo Vivier <zaeph@zaeph.net>2022-10-01 00:14:19 +0200
commit4cec043029ff185aca400ebfa28f7404a5034b31 (patch)
tree8460c8309883f3c8c4968828773065c182c54ca6 /2022
parent8fe5c8ef78427441e59216aa81d02ff99457a3f3 (diff)
downloademacsconf-wiki-4cec043029ff185aca400ebfa28f7404a5034b31.tar.xz
emacsconf-wiki-4cec043029ff185aca400ebfa28f7404a5034b31.zip
Publish
Diffstat (limited to '')
-rw-r--r--2022/organizers-notebook.md88
1 files changed, 66 insertions, 22 deletions
diff --git a/2022/organizers-notebook.md b/2022/organizers-notebook.md
index 20d88c26..049438fb 100644
--- a/2022/organizers-notebook.md
+++ b/2022/organizers-notebook.md
@@ -107,10 +107,22 @@ Planned dates and phases:
</tbody>
</table>
-Current phase: No prerecs to process yet, so it's a good time to focus on infrastructure
+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](#orgbb35d27), Oct 7 for everything :organizers:
+## TIME SENSITIVE
+
+
+### TODO Draft program-published email for emacsconf-discuss :needsowner:
+
+
+#### TODO Post it to r/emacs as well
+
+Please let zaeph know when it’s live so that the post can be distinguished.
+
+
+## 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](#orgac4deeb), Oct 7 for everything :organizers:
- zaeph: will start reviewing on Sep 21
@@ -240,6 +252,7 @@ Maybe we could ask some of the volunteers who wanted to help us with the infra?
## DONE Prepare to export talk information to wiki :sachac:
Tested code in a fork, can publish talk information once talks are approved.
+emacsconf-publish.el
emacsconf-generate-info-pages
emacsconf-generate-main-schedule
emacsconf-generate-talk-pages
@@ -275,7 +288,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](#orgbb35d27), 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](#orgac4deeb), Oct 7 for everything :organizers:
- zaeph: will start reviewing on Sep 21
@@ -291,6 +304,9 @@ zaeph helped with this, even catching some based on e-mail timestamps
## TODO Allocate extra time if possible; send e-mail :sachac:
+## TODO Create relevant links between talks across 2022 and all previous years :needsowner:
+
+
<a id="decisions"></a>
# Things to figure out / decisions to make
@@ -620,7 +636,7 @@ We tried using q56 before, but it was a little too aggressive. Q=32 is the defau
### Test stream setup
-[Stream](#orgc0a238a)
+[Stream](#org91f6be2)
### Set up MPV for captions
@@ -937,7 +953,7 @@ Exceptions:
### Send thanks
-[Thank you, next steps](#orge71d484)
+[Thank you, next steps](#org3a0392d)
### Extract the opening and closing remarks
@@ -1088,7 +1104,7 @@ Probably focus on grabbing the audio first and seeing what's worth keeping
Make a table of the form
-<table id="org2970f57" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
+<table id="orgb5c2403" border="2" cellspacing="0" cellpadding="6" rules="groups" frame="hsides">
<colgroup>
@@ -1399,9 +1415,11 @@ Objectives for this e-mail:
(talks (cdr group))
(first (car talks))
(reply-by-date (date-to-time "2022-10-08"))
- (prerec-target (date-to-time "2022-11-07"))
+ (prerec-target (date-to-time "2022-11-04"))
(attrs `(:speakers-short
,(plist-get first :speakers-short)
+ :plural
+ ,(if (= (length talks) 1) "" "s")
:email
,(plist-get first :email)
:year
@@ -1416,10 +1434,12 @@ Objectives for this e-mail:
,(mapconcat (lambda (o) (format "https://emacsconf.org/%s/talks/%s" (plist-get o :year)
(plist-get o :slug)))
talks "\n")
+ :irc
+ ,(if (plist-get first :irc) (concat (plist-get first :irc) "? ") "")
:acceptance-tasks
,(concat
"* TODO Reply to acceptance e-mail in order to confirm e-mail communication :emacsconf:
- DEADLINE: " (format-time-string "<%Y-%m-%d %a>" reply-by-date) "\n Please include public e-mail and/or any extra information you want on\n"
+ DEADLINE: " (format-time-string "<%Y-%m-%d %a>" reply-by-date) "\n Please include any extra information you want (ex: public e-mail, IRC nick) on\n"
(mapconcat (lambda (o) (format " https://emacsconf.org/%s/talks/%s"
(plist-get o :year)
(plist-get o :slug)))
@@ -1439,7 +1459,11 @@ Objectives for this e-mail:
(plist-get o :title)
(plist-get o :year)
(plist-get o :slug)
- (string-fill (emacsconf-replace-plist-in-string o (plist-get o :acceptance-comment)) 72)))
+ (string-fill (emacsconf-replace-plist-in-string
+ (append o
+ (list
+ :prerec-target (format-time-string "%b %e" prerec-target)))
+ (plist-get o :acceptance-comment)) 72)))
talks "\n---------------------------------------------------------------------\n"))))
(compose-mail
(car group)
@@ -1448,7 +1472,9 @@ Objectives for this e-mail:
("Mail-Followup-To" . ,(plist-get template :mail-followup-to))
("Cc" . ,(plist-get template :cc))))
(message-goto-body)
- (save-excursion (insert (emacsconf-replace-plist-in-string attrs (plist-get template :body))))))
+ (save-excursion (insert (emacsconf-replace-plist-in-string attrs (plist-get template :body)))
+ (goto-char (point-min))
+ (emacsconf-mail-merge-wrap))))
(defun emacsconf-draft-all-early-acceptances ()
(interactive)
@@ -1468,11 +1494,11 @@ Hi, ${speakers-short}!
Summary:
,${acceptance-tasks}
-We've accepted your EmacsConf proposal for ${titles}! Thanks for
+We've accepted your EmacsConf proposal${plural} for ${titles}! Thanks for
volunteering to share what you're learning about. I know it takes a
fair bit of work to prepare a presentation, so I appreciate that
you're taking the time to show what's possible with Emacs and
-encourage people to learn more.
+encourage people to learn more.${wrap}
---
@@ -1480,27 +1506,29 @@ ${talk-details-and-comments}
---
-You'll have some time after your talk for Q&A, so the allocated time
-can be just for your pre-recorded talk. Of course, if you like, you
+You'll have some time after your talk${plural} for Q&A, so the allocated time
+can be just for your pre-recorded talk${plural}. Of course, if you like, you
can make it shorter.
We've posted preparation tips at <https://emacsconf.org/${year}/prepare/> .
We'll send you instructions on how to upload files once we get that
set up.
-Could you please plan to ****put your pre-rec together by ${prerec-target}****
-(or even earlier if you want)? We're going to try to caption as many talks
-as possible again this year, and extra time helps a lot. People found
-the captions really helpful while watching the stream, and sending
-your talk in early will make it more likely that we'll be able to get
-your captions edited and reviewed before the conference.
+Could you please plan to ****put your pre-rec${plural} together by
+${prerec-target}**** (or even earlier if you want)? We're going to try
+to caption as many talks as possible again this year, and extra time
+helps a lot. People found the captions really helpful while watching
+the stream, and sending your talk in early will make it more likely
+that we'll be able to get your captions edited and reviewed before the
+conference.
****Please reply to this e-mail by ${reply-date}**** (including
emacsconf-submit@gnu.org in the To: or Cc:) so that we can confirm
that we've got the right email address for you and that messages can
-get properly delivered. Would you like us to put ${email} as the
+get properly delivered. Also, would you like us to put ${email} as the
public contact information for you, or would you like us to add
-something else to the talk pages?
+something else to the talk pages?${wrap}
+
${page-urls}
If you have any questions, please e-mail us at
@@ -2234,4 +2262,20 @@ see emacsconf-import-comments-from-etherpad-text
they intend their talks to be 10′ or 20′. We should change the
wording on the CFP to ask them to only provide alternatives for
shorter formats, not longer.
+- It was hard to squeeze all the org/hyperbole talk on day-1.
+ Generally, the people who submit these kinds of talk come from all
+ over the world, and US mornings are more accommodating than US
+ evenings when it comes to timezones. We might consider having two org
+ **mornings** rather than an org **day**; it would give us more flexibility
+ with those talks.
+- We’re starting to reach critical mass on the org-talks. We might want
+ to consider splitting the org-talks and the dev-talks into two
+ distinct events to allow them to grow independently.
+- We should associate time-of-day with CFP-deadline; otherwise, the
+ scheduler has to be on edge until the very end of the day. It’s worse
+ this year because we made CFP-end coincide with speaker-notif, so this
+ might not be as much of a problem next year.
+- It’s easier for us to extend beyond 5pm than to go before 9am
+ (especially for the West coast). Extending beyond 5pm puts strain on
+ European organizers and volunteers, though.