summaryrefslogtreecommitdiffstats
path: root/2023/organizers-notebook/index.org
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2023-09-30 10:26:47 -0400
committerSacha Chua <sacha@sachachua.com>2023-09-30 10:26:47 -0400
commit08baa52e3bf0eafe38975bc31af2a578a0d11d7a (patch)
tree596d41a419964c69b3e050f8bbd5f65c4fe3d6b8 /2023/organizers-notebook/index.org
parente858f9959ed159b8a3138bdd68538afbf478aeb9 (diff)
downloademacsconf-wiki-08baa52e3bf0eafe38975bc31af2a578a0d11d7a.tar.xz
emacsconf-wiki-08baa52e3bf0eafe38975bc31af2a578a0d11d7a.zip
update notebook with links to sun-am option
Diffstat (limited to '2023/organizers-notebook/index.org')
-rw-r--r--2023/organizers-notebook/index.org5
1 files changed, 3 insertions, 2 deletions
diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org
index 2db1c804..e6d5528e 100644
--- a/2023/organizers-notebook/index.org
+++ b/2023/organizers-notebook/index.org
@@ -618,7 +618,7 @@ 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 EXPORT EXPORT html
+#+INCLUDE: schedule.svg export html
What if we have three tracks instead?
@@ -633,8 +633,9 @@ What if we have three tracks instead?
- More logical grouping
- Ends earlier, which is easier for participants from Europe
- votes: max (Three tracks is the best policy if you’re more than 75% sure that you can round up the volunteers)
-- Three tracks just for Sunday morning:
+- [[#three-tracks-sun-am][Three tracks just for Sunday morning]]:
- Allows us to have 20 minutes between talks instead of 15
+ - Might be easier to test the idea for just one part of the conference
#+begin_src emacs-lisp :exports none
(defun emacsconf-schedule-copy-previous-track (list)