summaryrefslogtreecommitdiffstats
path: root/2023/organizers-notebook
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2023-09-24 13:50:05 -0400
committerSacha Chua <sacha@sachachua.com>2023-09-24 13:50:05 -0400
commitddb3534de3726c8483adeaa0aaadcee4214842b8 (patch)
tree22c98cacf98d2b9887deedb5954592eb4fcafb4d /2023/organizers-notebook
parent8366a72643054cf6bd81dea192f8f1dfda4d76e8 (diff)
downloademacsconf-wiki-ddb3534de3726c8483adeaa0aaadcee4214842b8.tar.xz
emacsconf-wiki-ddb3534de3726c8483adeaa0aaadcee4214842b8.zip
add lessons learned, some speaker bios
Diffstat (limited to '')
-rw-r--r--2023/organizers-notebook/index.org40
1 files changed, 27 insertions, 13 deletions
diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org
index cf95cdfa..ee0bcd54 100644
--- a/2023/organizers-notebook/index.org
+++ b/2023/organizers-notebook/index.org
@@ -302,25 +302,39 @@ CFP deadline? I'd like to see if we can get away without officially
extending the CFP this time.
Sacha
-*** Lessons learned :lessons:
-- Early acceptances are nice. A few got comments within the 1-week period.
-- It's a good idea to send the review and acceptance e-mails even to fellow organizers/volunteers, even if they helped write the page. =)
-- I added some more automation for including a template in a mail reply
-- We successfully didn't panic about submissions, yay! It was nice to be able to draft schedules as we went along.
+*** Lessons learned from the CFP :lessons:
+
+- Early acceptances are nice. A few got comments within the 1-week
+ period, which helped refine the talk idea more. We probably don't
+ need to make this a 2-week review period.
+- It's a good idea to send the review and acceptance e-mails even to
+ fellow organizers/volunteers, even if they're quite familiar with
+ the page already. =)
+- I added some more automation for including a template in a mail
+ reply.
+- We successfully didn't panic about submissions, yay! It was nice to
+ be able to draft schedules as we went along, and to compare the
+ dates with last year's trends.
+
** 2023-09-23 EmacsConf 2023 progress report
:PROPERTIES:
:CUSTOM_ID: 2023-09-22
:END:
-- 44 talks accepted so far, whee!
-- 1 talks penciled in (woof) - we'll save time for this in the schedule
-- doublecheck:
- - all proposals responded to? https://lists.gnu.org/mailman/private/emacsconf-submit/2023/thread.html
- (everything accepted except for Noah's talk, which she cancelled)
- - availability correctly captured?
-- draft schedule
-- lessons learned
+- result of call for participation:
+ - 44 talks accepted so far, whee!
+ - 1 talks penciled in (woof) - we'll save time for this in the schedule
+ - ~12 hours of talks. If we had 5 minutes buffer in between talks, we'd end up with 16 hours and no lunch break, so let's do a two-track conference again this year!
+- Since this is the sort of fiddly stuff my brain tends to hiccup on, it would be great if people can doublecheck things. (zaeph? JC Helary? other volunteers? Y'all can split this up however you like.). Things to check:
+ - Have all speakers been responded to? You can cross-reference with the mailing list archives: https://lists.gnu.org/mailman/private/emacsconf-submit/2023/thread.html
+ (Pretty much everything accepted, although some things were tweaked along the way. Noah's talk was cancelled.)
+ - Was speaker availability correctly captured, timezones converted, etc.? Availability constraints: emails -> conf.org -> https://emacsconf.org/2023/organizers-notebook/#draft-schedule
+ - Was speaker availability correctly followed? I included the
+ constraints at
+ https://emacsconf.org/2023/organizers-notebook/#draft-schedule and
+ things look right, but it's always good to double-check.
+- I started drafting a schedule for EmacsConf. https://emacsconf.org/2023/organizers-notebook/#draft-schedule has detailed notes. Thoughts on the order/grouping of talks? If the schedule looks all right, I can send this draft to all the speakers in case they have any requests regarding time preferences, other talk Q&A sessions that they want to attend live, etc.
- next steps:
- start coordinating with speakers regarding draft schedule, wishlist of any talks they want to attend live
- coordinating with FSF regarding media.emacsconf.org