update progress report

1 files changed, 33 insertions, 0 deletions

diff --git a/blog/2023-09-25-draft-schedule.md b/blog/2023-09-25-draft-schedule.md
new file mode 100644
index 00000000..4b93e422
--- /dev/null
+++ b/blog/2023-09-25-draft-schedule.md
@@ -0,0 +1,33 @@
+[[!date "2023-09-25"]]
+[[!meta title="EmacsConf 2023 progress report: 44 talks accepted, schedule being drafted"]]
+
+The EmacsConf 2023 call for participation period has wrapped up,
+hooray! We’ve accepted 44 talks and posted them at
+<https://emacsconf.org/2023/talks/>, with 1 more penciled in (woof -
+Watch Over Our Folders). This is about ~12 hours of talks. If we were
+to have 5 minutes buffer in between talks, it would be 15 hours and a
+pretty cramped conference. I think we can pull off a two-track
+conference again this year. Shall we give it a try? =) We can set up a
+schedule for the different roles as we get closer to the conference.
+
+I started drafting a schedule at
+<https://emacsconf.org/2023/organizers-notebook/#draft-schedule> .
+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:
+
+-   Schedule: We&rsquo;ll e-mail the draft schedule to speakers so that they
+    can get a sense of where they are in the schedule, see if they
+    really want to make it to a conflicting session&rsquo;s Q&A live
+    (they&rsquo;ll have early access to the videos), etc.
+-   Infrastructure:
+    -   Dust off and document infrastructure, processes
+    -   Sort out access to media.emacsconf.org so that we can get the upload service up and running
+-   Draft brief intros for talks, keeping in mind that we&rsquo;re going to say them out loud
+-   Speakers will work on videos, and we can help with nudges/coordination if needed
+
+Sacha
+