diff options
Diffstat (limited to '')
| -rw-r--r-- | 2023/organizers-notebook/index.org | 49 |
1 files changed, 25 insertions, 24 deletions
diff --git a/2023/organizers-notebook/index.org b/2023/organizers-notebook/index.org index ee0bcd54..6fae62be 100644 --- a/2023/organizers-notebook/index.org +++ b/2023/organizers-notebook/index.org @@ -317,33 +317,20 @@ Sacha dates with last year's trends. -** 2023-09-23 EmacsConf 2023 progress report +** 2023-09-25 EmacsConf 2023 progress report: 44 talks accepted, schedule being drafted :PROPERTIES: -:CUSTOM_ID: 2023-09-22 +:CUSTOM_ID: 2023-09-25 :END: -- 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 +https://emacsconf.org/blog/2023-09-25-draft-schedule ** Draft schedule :PROPERTIES: :CUSTOM_ID: draft-schedule :END: +These times are in EST (GMT-5). + #+begin_src emacs-lisp :results value replace :exports none (require 'emacsconf) (require 'emacsconf-schedule) @@ -559,6 +546,12 @@ Sacha - emacsconf:flat, emacsconf:scheme, emacsconf:gc, emacsconf:flat, emacsconf:windows, emacsconf:emacsconf, emacsconf:steno - emacsconf:emacsen is more high-level and can talk about other editors - checking with emacsconf:web and emacsconf:hn if ~3pm Sunday afternoon (~7am Mon local time) is okay with them. It would be nice to pair it with emacsconf:hn, which is nice to connect to emacsconf:mentor and emacsconf:web. +- Thinking about the flow: + - General: Org day, then misc talks Sunday morning and part of Sunday afternoon. Ending with a focus on community and expanding Emacs. It would be nice to get people excited about connecting and sharing throughout the year. + - Dev: people who are really curious about AI can connect on + Saturday morning and keep the conversation going. Some programming + tweaks are grouped together. The rest are mostly based on + availability. - if the talks get cancelled, we can have an open meetup possibly with breakout rooms - coordination notes: @@ -567,12 +560,20 @@ Sacha - emacsconf:hn and emacsconf:web - [[emacsconf:unentangling]], [[emacsconf:taming]]? - emacsconf:matplotllm, emacsconf:voice, emacsconf:llm (so they don't all have to define LLMs?) -- next steps for schedule: - - sanity-check with other organizers/volunteers - - reach out 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's Q&A live (they'll have early access to the - videos), etc. +- The schedule doesn't have neat aligned slots on purpose so that + organizers can jump between streams if needed, and also because we + have so many awesome talks. Somehow people managed to handle the + schedule last year. =) +- Next steps: + - Schedule: We'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's Q&A live + (they'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're going to say them out loud + - Speakers will work on videos, and we can help with nudges/coordination if needed * E-mail templates :PROPERTIES: |