summaryrefslogtreecommitdiffstats
path: root/2023/organizers-notebook/index.org
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2023-09-27 18:36:29 -0400
committerSacha Chua <sacha@sachachua.com>2023-09-27 18:36:29 -0400
commit3626ed66dba4b88b83aec203501dbf582fda49a0 (patch)
tree906c6da7ed14d2059cfdb8f7e2b585c2c3f3e320 /2023/organizers-notebook/index.org
parent12681347d7ba4f21c7691e14d7d595514636539c (diff)
downloademacsconf-wiki-3626ed66dba4b88b83aec203501dbf582fda49a0.tar.xz
emacsconf-wiki-3626ed66dba4b88b83aec203501dbf582fda49a0.zip
add decision target dates, votes so far, coordination notes
Diffstat (limited to '2023/organizers-notebook/index.org')
-rw-r--r--2023/organizers-notebook/index.org30
1 files changed, 21 insertions, 9 deletions
diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org
index fe236f55..d414c374 100644
--- a/2023/organizers-notebook/index.org
+++ b/2023/organizers-notebook/index.org
@@ -20,18 +20,19 @@ Decisions to make:
(org-map-entries
(lambda ()
(unless (org-entry-is-done-p)
- (format "- %s\n"
+ (format "- %s (by %s)\n"
(org-link-make-string
(concat "#" (org-entry-get (point) "CUSTOM_ID"))
- (org-entry-get (point) "ITEM")))))
+ (org-entry-get (point) "ITEM"))
+ (replace-regexp-in-string "[<>]" "" (org-entry-get (point) "DEADLINE")))))
"decision" nil))
"")
#+end_src
#+RESULTS:
:results:
-- [[#three-tracks][Test the idea of three tracks and more aligned times]]
-- [[#honorifics][Do we want to use honorifics like Dr.?]]
+- [[#three-tracks][Test the idea of three tracks and more aligned times]] (by 2023-10-13 Fri)
+- [[#honorifics][Do we want to use honorifics like Dr.?]] (by 2023-11-14 Tue)
:end:
#+TOC: headlines 2
@@ -586,6 +587,7 @@ These times are in EST (GMT-5).
- if the talks get cancelled, we can have an open meetup possibly with
breakout rooms
- coordination notes:
+ - TODO emacsconf:uni, emacsconf:teaching, emacsconf:table are all about Emacs, Org Mode, and teaching
- TODO emacsconf:repl, emacsconf:eval
- emacsconf:hyperamp, emacsconf:koutline, and emacsconf:test are all in touch because they work on Hyperbole together
- emacsconf:hn and emacsconf:web
@@ -607,24 +609,29 @@ These times are in EST (GMT-5).
- Speakers will work on videos, and we can help with nudges/coordination if needed
*** TODO Test the idea of three tracks and more aligned times :decision:
+DEADLINE: <2023-10-13 Fri>
:PROPERTIES:
:CUSTOM_ID: three-tracks
:END:
+Let's see if we can decide on this by [2023-10-13 Fri] so that we can
+e-mail the draft schedules to people.
+
Compared to [[#draft-schedule][two-track schedule]]:
#+INCLUDE: schedule.svg export html
What if we have three tracks instead?
+- Two-track advantages as in EmacsConf 2022:
+ - Fewer volunteers needed (host, IRC, pad)
+ - Can do with existing computing power (instead of spinning up another node for VNC+OBS)
+ - Less fear of missing out for participants
+ - votes: zaeph
- Three-track advantages:
- More space between talks for streaming the Q&A
- Easier to explain the schedule
- More logical grouping
- Ends earlier, which is easier for participants from Europe
-- Three-track disadvantages:
- - Needs more volunteers (host, IRC, pad)
- - Needs more computing power (will probably need to spin up another node for VNC+OBS)
- - More fear of missing out for participants
#+begin_src emacs-lisp :exports none
(defun emacsconf-schedule-copy-previous-track (list)
@@ -842,13 +849,18 @@ conference because talk titles and Q&A methods can change. We can
verify speaker name pronunciations at that time.
**** TODO Do we want to use honorifics like Dr.? :decision:
+DEADLINE: <2023-11-14 Tue>
:PROPERTIES:
:CUSTOM_ID: honorifics
:END:
+Let's see if we can decide on this by [2023-11-04 Fri] so that we can
+use it when recording the intros.
+
- OPTION: Consistently using names without honorifics, even if indicated in the
- speaker-submitted intros:
+ speaker-submitted intros (as in previous EmacsConfs)
- Equality
+ - votes: zaeph
- OPTION: Asking speakers if they want us to use any honorifics in their intro:
- Observes personal preferences
- OPTION: Using honorifics based on e-mail signatures and intros: