# [[elisp:(memoize 'emacsconf-get-talk-info "5 seconds")][Memoize emacsconf-get-talk-info]]
# [[elisp:(org-md-export-to-markdown)][Export this file to Markdown]]
#+todo: TODO(t) SOMEDAY STARTED INPROGRESS(i) WAITING(w) STANDBY(s) BLOCKED(b) | DONE(x) CANCELLED(c)
#+OPTIONS: h:6 toc:nil num:nil ':t
#+PROPERTY: header-args :results silent :exports code :tangle yes
#+EXPORT_FILE_NAME: ../organizers-notebook.md
#+PROPERTY: QUANTIFIED Emacs
#+begin_export md
<!-- organizers-notebook.md is exported from organizers-notebook/index.org, please modify that instead. -->
[[!sidebar content=""]]
This file is automatically exported from [/2023/organizers-notebook/index.org](/2023/organizers-notebook/index.org). You might prefer to navigate this as an Org file instead. To do so, [clone the wiki repository](https://emacsconf.org/edit/).
#+end_export
#+begin_src emacs-lisp :results value replace :exports results :eval never-export
(emacsconf-surround "Decisions to make:\n\n"
(string-join
(delq nil
(org-map-entries
(lambda ()
(unless (or (not (org-entry-is-todo-p)) (org-entry-is-done-p))
(format "- %s (by %s)\n"
(org-link-make-string
(concat "#" (org-entry-get (point) "CUSTOM_ID"))
(org-entry-get (point) "ITEM"))
(if (org-entry-get (point) "DEADLINE")
(replace-regexp-in-string "[<>]" "" (org-entry-get (point) "DEADLINE"))
""))))
"decision" nil))
"")
"" "")
#+end_src
#+RESULTS:
:results:
:end:
#+TOC: headlines 2
* Timeline
:PROPERTIES:
:CUSTOM_ID: timeline
:END:
| CFP | [2023-06-26 Mon] |
| CFP deadline | [2023-09-14 Thu] |
| Speaker notifications | [2023-09-25 Mon] |
| *Publish schedule* | [2023-10-25 Wed] |
| Video submission deadline | [2023-11-04 Sat] |
| EmacsConf | [2023-12-02 Sat], [2023-12-03 Sun] |
Last year, these were the actual dates:
- July 17: CFP sent
- Sept 18: Original CFP deadline
- Sept 30: CFP closed after extension
- Oct 1: acceptances sent
** TODO Dry run
SCHEDULED: <2023-10-28 Sat>
:PROPERTIES:
:CUSTOM_ID: dry-run
:END:
* Phases
:PROPERTIES:
:CUSTOM_ID: phases
:END:
** DONE Draft CFP
CLOSED: [2023-09-22 Fri 09:49]
:PROPERTIES:
:CUSTOM_ID: cfp
:END:
*** How to mark pages as drafts
Put inside double square brackets: =!template id=pagedraft=
*** Considerations
We could see if there are parts of the CFP that we can remove or
postpone. Here are some thoughts:
- We might not need the 10+20+40 structure in the proposal. We did
that before because people tend to propose longer talks, and we had
to do lots of e-mail coordination in order to squeeze everything
into one track. If we're doing multiple streams, there's less time
pressure, so we might not need to confuse people with those
requirements. I think it would still be good to nudge people towards
20 minutes for their prerecorded presentations (separate time for
Q&A) instead of 40 minutes, because it's good for people's attention
spans. As an incentive to consider a 5-10 minute talk, we can say
that 5-10 minute videos can be played extra times during the
conference to fill gaps.
- Choices:
- Keep the 10+20+40 structure so that people who want to propose
longer talks are nudged to think about shorter versions
- Strongly nudge people towards 20-minute talks, with repeats as
the incentive for shorter talks and extra coordination/waiting
needed for longer talks. People propose just the talk length
they want (and can optionally propose other talk lengths if they
want to be considered for them).
- We added emergency contact info, public contact info, pronouns, and
introduction to the submission form because we ended up going back
and forth with people in previous years, and sometimes we had
incomplete info and were panicking about how to reach people during
the conference. We could drop this from the submission form and do a
separate speaker information form.
- Choices:
- Talk submission, then speaker information form: less
intimidating for speakers
- Everything in one: easier for organizers
*** Previous years
- Ask for public e-mail or contact information, IRC handle in CFP
- Added to submit page.
- Be even more stringent about the 10/20/40-min splits. A lot of
speakers still default to the 20- or 40-min formats without
providing us shorter formats, and that puts strain on our schedule
and requires us to use a different template for the notification
(which can be confusing). We need to stress that not respecting the
format makes it harder not only for the organizers, but also for the
speakers themselves (since they will have to rethink their
presentation). Maybe we can have an e-mail template for a quick
reply that says something like "Just in case we need to squeeze
talks into shorter times, could you please also propose an outline
for a possible 10-minute talk that could get people interested in
your topic and point them to where they can find out more?"
- sachac: I'd love to experiment with rolling acceptances. If people
have a good 10-20 minute version of their talk and we want to
accept it in the program, it would be nice to be able to say yes
early so that they can start working on it. We can work with any
duplication of content in later proposals.
- Two people is the sweet number of reviewers to have for the
proposals before sending the notifications, and there’d be
diminishing returns with more. Two is enough to release the pressure
on SCHED, verify the metadata (esp. speaker availability), and
suggest a different ordering where appropriate. It can take a long
time to comb through the proposals (roughly 10 proposals per hour),
and whilst it’d be difficult to justify more in-depth reviewers,
other orgas can do a shallow-pass to catch red-flags or discuss the
submissions as they come in. Other organizers can always chime in on
topics they particularly care about so that their encouraging
comments or suggestions can be included in the acceptance e-mail.
- sachac: Who wants to help me with this?
- We extended CFP-end by two weeks this year, but that made it coincide
with speaker-notifs, and that’s awkward. Next time, we should only
extend the CFP by one week to avoid having to scramble with the
schedule until the very last day.
- Proposed dates in https://emacsconf.org/2023/cfp/ have similar
spacing, so yeah, we'll want to extend by only one week.
- Some people assume that they have to suggest longer formats even if
they intend their talks to be 10′ or 20′. We should change the
wording on the CFP to ask them to only provide alternatives for
shorter formats, not longer.
- Added a brief note to CFP.
- It was hard to squeeze all the org/hyperbole talk on day-1.
Generally, the people who submit these kinds of talk come from all
over the world, and US mornings are more accommodating than US
evenings when it comes to timezones. We might consider having two org
*mornings* rather than an org *day*; it would give us more flexibility
with those talks.
- Let's see if we can do two streams again. That was fun.
- We’re starting to reach critical mass on the org-talks. We might want
to consider splitting the org-talks and the dev-talks into two
distinct events to allow them to grow independently.
- Let's see if we can do two streams again. That was fun.
- We should associate time-of-day with CFP-deadline; otherwise, the
scheduler has to be on edge until the very end of the day. It’s worse
this year because we made CFP-end coincide with speaker-notif, so this
might not be as much of a problem next year.
- If we do rolling acceptances and we extend by at most one week
instead of two, this should be fine.
- It’s easier for us to extend beyond 5pm than to go before 9am
(especially for the West coast). Extending beyond 5pm puts strain on
European organizers and volunteers, though.
- Time pressure should be alleviated with multiple streams.
- Sometimes, ikiwiki on front0 took a lot of time to process the new
commits. sachac assumed this is due to a faulty regex parsing. We
should be able to find out more by looking at the logs from ikiwiki
after a slow commit.
- Seems speedy at the moment.
- Ask for preferred timezone in CFP
- Added to availability.
- Check with John Wiegley re: schedule - we always happen to coincide
with his work trips
- I checked with him and the people at his work don't have a schedule
yet, so we should go ahead and plan
*** Lessons learned for next year
- Maybe incentivize proper timezone specification by saying we can translate times to their local time?
- Make sure to include cfp.org as an attachment instead of inline
*** Other thoughts
- sachac: bandali likes having the commitment to freedom section in the CFP as a form of activism
- sachac: I thought about pulling the deadline back to Sept 1, but it might be
good to keep it at Sept 14 so that anyone who tends to work with the
schoolyear can still have a little time to work on it.
** DONE Distribute CFP
CLOSED: [2023-09-22 Fri 09:50]
:PROPERTIES:
:CUSTOM_ID: distrib-cfp
:END:
*** DONE Add proposal review volunteers to emacsconf-submit
CLOSED: [2023-06-25 Sun 19:35]
- https://lists.gnu.org/mailman/admin/emacsconf-submit/members/add
- Ask volunteers to e-mail an SSH public key so they can be added via the gitolite-admin repo to the conf.org repo for the year
*** First announcement
SCHEDULED: <2023-06-26 Mon>
- Remove draft tags :sachac:
- Post on emacsconf-discuss, emacs-tangents :bandali: :zaeph:
- Sticky on reddit.com/r/emacs
- Post in Emacs News :sachac:
*** Reminder
** DONE Process submissions
CLOSED: [2023-09-22 Fri 09:50]
:PROPERTIES:
:CUSTOM_ID: submission-process
:FUNCTION: emacsconf-mail-review
:END:
- Proposal received: sachac adds it to this document with status of PROPOSED
- Fields:
#+begin_example
EMERGENCY, Q_AND_A, AVAILABILITY, NAME, PRONOUNS, TIME, MIN_TIME, MAX_TIME, SLUG, EMAIL, NAME_SHORT, CUSTOM_ID, TRACK, TIMEZONE, CATEGORY, DATE_SUBMITTED
#+end_example
- jc doublechecks that the data has been correctly captured (especially EMAIL and AVAILABILITY)
- People review it (sachac, jc, etc.) and weigh in
- Proposal accepted: sachac e-mails the speaker and sets status to WAITING_FOR_EMAIL_CONFIRM
- E-mail confirmation received: log it in the logbook
- Schedule set: sachac e-mails the speaker and sets status to WAITING_FOR_SCHED_CONFIRM
*** 2023-08-14 EmacsConf 2023 CFP progress report (8 talks accepted so far, 1 to review, 6 todo)
SCHEDULED: <2023-08-14 Mon>
:PROPERTIES:
:CUSTOM_ID: cfp-progress
:END:
#+begin_comment
https://emacsconf.org/blog/2023-08-14-cfp-progress/
#+end_comment
The end of the EmacsConf 2023 call for participation is one month away
(Sept 14; https://emacsconf.org/2023/cfp/). Whee! So far, we've sent
early acceptances to the following talks and added them to the program
on the wiki (https://emacsconf.org/2023/talks):
#+begin_src emacs-lisp :results replace table :exports results :eval never-export
(append
'(("Duration" "Title" "Speaker"))
(mapcar (lambda (o)
(list (plist-get o :duration)
(plist-get o :title)
(plist-get o :speakers)))
(seq-filter (lambda (o) (string= (plist-get o :status) "WAITING_FOR_PREREC")) (emacsconf-get-talk-info))))
#+end_src
#+RESULTS:
:results:
| Duration | Title | Speaker |
| 10 | An Org-Mode based text adventure game for learning the basics of Emacs, inside Emacs, written in Emacs Lisp | Chung-hong Chan |
| 20 | Authoring and presenting university courses with Emacs and a full libre software stack | James Howell |
| 20 | Org-Mode workflow: informal reference tracking | Christopher Howard |
| 20 | GNU Emacs for electronics, note-taking, and as lightweight IDE | Anand Tamariya |
| 10 | A modern Emacs look-and-feel without pain | Pedro A. Aranda |
| 10 | Writing a language server in OCaml for Emacs, fun, and profit | Austin Theriault |
| 20 | LLM clients in Emacs, functionality and standardization | Andrew Hyatt |
| 10 | The many ways to browse Hacker News from Emacs | Mickael Kerjean |
:end:
We sent the speakers https://emacsconf.org/2023/prepare/ in case
anyone wants to get started on their presentations.
There's one talk that's waiting for feedback on the emacsconf-submit
before we send the early acceptance in about a week:
#+begin_src emacs-lisp :results replace table :exports results :eval never-export
(append
'(("Duration" "Title" "Speaker"))
(mapcar (lambda (o)
(list (plist-get o :duration)
(plist-get o :title)
(plist-get o :speakers)))
(seq-filter (lambda (o) (string= (plist-get o :status) "TO_REVIEW")) (emacsconf-get-talk-info))))
#+end_src
#+RESULTS:
:results:
| Duration | Title | Speaker |
| 20 | one.el: the static site generator for Emacs Lisp Programmers | Tony Aldon |
:end:
There are several talk proposals that are in progress (need to
coordinate, don't have speaker releases / full details / etc.):
#+begin_src emacs-lisp :results replace table :exports results :eval never-export
(append
'(("Title" "Speaker"))
(mapcar (lambda (o)
(list (plist-get o :title)
(plist-get o :speakers)))
(seq-filter (lambda (o) (string= (plist-get o :status) "TODO")) (emacsconf-get-talk-info))))
#+end_src
#+RESULTS:
:results:
| Title | Speaker |
| Emacs MultiMedia System (EMMS) | Yoni Rabkin |
| Emacs development updates | John Wiegley |
| Watch Over Our Folders | Bastien Guerry |
| Emacs community information sharing? | Jake B |
| Emacs saves the Web | Yuchen Pei |
| How to build an Emacs 2: Revenge of the Lem | Fermin |
:end:
This time last year, we had 2 proposals, with most of the proposals
coming in at the end of the CFP. This was usually when we started
panicking about not having lots of proposals, but I think we can skip
stressing about it this year. <laugh> Even with the program as it is
now, we'd already have a pretty fun EmacsConf. Can't wait to see what
it'll look like when more people get their proposals in!
bandali, maybe we can do a 1-month and/or 2-week reminder about the
CFP deadline? I'd like to see if we can get away without officially
extending the CFP this time.
Sacha
*** Lessons learned from the CFP acceptance phase :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. =)
- 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.
- I added some more automation for including a template in a mail
reply. Changing the subject to =EmacsConf 2023 acceptance: talk
title= made it easier to verify that talks had been responded to.
- I added =emacsconf-mail-add-submission= for parsing submissions from
e-mail and adding them to =emacsconf-org-file=. That was nice
because it automatically saved =EMAIL=, =DATE_SUBMITTED=, and
=DATE_TO_NOTIFY=.
- Displaying the schedule as a list with time constraints made it
easier to verify the time constraints and to see how I can fix
errors.
- Drafting the schedule in the public organizers notebook was nice
because I could share that with the speakers and other volunteers.
** Draft schedule
:PROPERTIES:
:CUSTOM_ID: draft-schedule
:END:
These times are in EST (GMT-5).
#+NAME: schedule
#+begin_src emacs-lisp :results value replace :exports none :eval never-export
(require 'emacsconf)
(require 'emacsconf-schedule)
(setq emacsconf-schedule-tracks
'((:label "Saturday"
:start "2023-12-02 9:00"
:end "2023-12-02 18:00"
:tracks ("General" "Development"))
(:label "Sunday"
:start "2023-12-03 9:00"
:end "2023-12-03 18:00"
:tracks ("General" "Development"))))
(let ((emacsconf-schedule-default-buffer-minutes 10)
(emacsconf-schedule-default-buffer-minutes-for-live-q-and-a 15)
(emacsconf-schedule-break-time 10)
(emacsconf-schedule-lunch-time 60)
(emacsconf-use-absolute-url t)
(emacsconf-schedule-strategies '(emacsconf-schedule-allocate-buffer-time))
(emacsconf-schedule-validation-functions
'(emacsconf-schedule-validate-time-constraints
;; emacsconf-schedule-validate-live-q-and-a-sessions-are-staggered
emacsconf-schedule-validate-all-talks-present
emacsconf-schedule-validate-no-duplicates)))
(setq emacsconf-schedule-plan
'(("GEN Saturday, Dec 2" :start "2023-12-02 09:00")
sat-open
adventure
uni
teaching
table
taming
one
(lunch :start "12:00")
writing
nabokov
collab
solo
ref
unentangling
(hyperdrive)
(devel :track "General")
(sat-close)
("DEV Saturday, Dec 2" :start "2023-12-02 10:00")
(matplotllm :track "Development")
(voice :track "Development")
(llm :track "Development")
(woof :track "Development")
(lunch :start "12:00")
(overlay)
(eval)
(repl)
(extending :track "Development")
gap
("GEN Sunday, Dec 3" :start "2023-12-03 09:00")
sun-open
hyperamp
koutline
(parallel :track "General")
eat
poltys
cubing
(lunch :start "12:00")
(emms :track "General")
(steno :track "General")
mentor
break
(hn :start "15:00")
web
sharing
sun-close
("DEV Sunday, Dec 3" :start "2023-12-03 10:00")
scheme
test
(flat :track "Development")
(lunch :start "12:00")
gc
lspocaml
(windows :track "Development")
(emacsconf :track "Development")
(emacsen :track "Development")
))
(setq emacsconf-schedule-draft (emacsconf-schedule-prepare (emacsconf-schedule-inflate-sexp emacsconf-schedule-plan)))
(prog1 (string-join (emacsconf-schedule-validate emacsconf-schedule-draft) "\n")
(let ((emacsconf-schedule-svg-modify-functions
'(;emacsconf-schedule-svg-color-by-availability
emacsconf-schedule-svg-color-by-status)))
(with-temp-file (expand-file-name "schedule.svg" (file-name-directory emacsconf-org-file))
(svg-print (emacsconf-schedule-svg 800 300 emacsconf-schedule-draft)))
(with-temp-file (expand-file-name "schedule.svg" (expand-file-name "organizers-notebook" (expand-file-name emacsconf-year emacsconf-directory)))
(svg-print (emacsconf-schedule-svg 800 300 emacsconf-schedule-draft))))
(clear-image-cache)))
#+end_src
#+RESULTS: schedule
:results:
:end:
#+begin_comment
[[file:schedule.svg]]
#+end_comment
#+INCLUDE: schedule.svg export html
- Legend: dashed line means non-BBB Q&A; light gray means penciled-in talk; yellow means video already submitted and being processed
*** Draft schedule as a list
:PROPERTIES:
:CUSTOM_ID: schedule-list
:END:
#+NAME: draft-schedule-table
#+begin_src emacs-lisp :results raw replace :exports results :eval never-export
(string-join
(seq-keep (lambda (o) (when (plist-get o :slug)
(concat "- "
(replace-regexp-in-string "[<>]" ""
(plist-get o :scheduled))
" "
(if (string-match "after the event" (or (plist-get o :q-and-a) "")) "- no live Q&A - "
(emacsconf-surround "- " (emacsconf-schedule-format-time-constraint o) " - " ""))
(format "[[emacsconf:%s][%s]]: "
(plist-get o :slug)
(plist-get o :slug))
(plist-get o :title)
(emacsconf-surround " ("
(plist-get o :speakers)
") " ""))))
(sort emacsconf-schedule-draft (lambda (a b) (string< (plist-get a :scheduled) (plist-get b :scheduled))))) "\n")
#+end_src
#+RESULTS: draft-schedule-table
- 2023-12-02 Sat 09:00-09:10 [[emacsconf:sat-open][sat-open]]: Saturday opening remarks
- 2023-12-02 Sat 09:10-09:20 - <= 10:00 - [[emacsconf:adventure][adventure]]: An Org-Mode based text adventure game for learning the basics of Emacs, inside Emacs, written in Emacs Lisp (Chung-hong Chan)
- 2023-12-02 Sat 09:30-09:50 [[emacsconf:uni][uni]]: Authoring and presenting university courses with Emacs and a full libre software stack (James Howell)
- 2023-12-02 Sat 10:00-10:10 - <= 10:30 - [[emacsconf:matplotllm][matplotllm]]: MatplotLLM, iterative natural language data visualization in org-babel (Abhinav Tushar)
- 2023-12-02 Sat 10:05-10:25 - on 2023-12-02 - [[emacsconf:teaching][teaching]]: Teaching computer and data science with literate programming tools (Marcus Birkenkrahe)
- 2023-12-02 Sat 10:20-10:40 [[emacsconf:voice][voice]]: Improving access to AI-assisted literate programming with voice control (Blaine Mooers)
- 2023-12-02 Sat 10:40-10:50 - <= 11:00 - [[emacsconf:table][table]]: Who needs Excel? Managing your students qualifications with org-table (Daniel Molina)
- 2023-12-02 Sat 10:55-11:15 - >= 10:00 - [[emacsconf:llm][llm]]: LLM clients in Emacs, functionality and standardization (Andrew Hyatt)
- 2023-12-02 Sat 11:05-11:15 - <= 15:00 - [[emacsconf:taming][taming]]: Taming things with Org Mode (Gergely Nagy (algernon))
- 2023-12-02 Sat 11:30-11:50 - <= 13:00 - [[emacsconf:one][one]]: one.el: the static site generator for Emacs Lisp Programmers (Tony Aldon)
- 2023-12-02 Sat 11:30-11:50 - <= 15:00 - [[emacsconf:woof][woof]]: Watch Over Our Folders (Bastien Guerry)
- 2023-12-02 Sat 13:00-13:10 [[emacsconf:writing][writing]]: Emacs turbo-charges my writing (Jeremy Friesen)
- 2023-12-02 Sat 13:00-13:20 - >= 11:00 - [[emacsconf:overlay][overlay]]: Improving compiler diagnostics with Overlays (Jeff Trull)
- 2023-12-02 Sat 13:25-13:35 [[emacsconf:nabokov][nabokov]]: Why Nabokov would use Org-Mode if he were writing today (Edmund Jorgensen)
- 2023-12-02 Sat 13:35-13:45 [[emacsconf:eval][eval]]: Editor Integrated REPL Driven Development for all languages (Musa Al-hassy)
- 2023-12-02 Sat 13:50-14:10 - no live Q&A - [[emacsconf:collab][collab]]: Collaborative data processing and documenting using org-babel (Jonathan Hartman, Lukas C. Bossert)
- 2023-12-02 Sat 14:00-14:40 [[emacsconf:repl][repl]]: REPLs in strange places: Lua, LaTeX, LPeg, LPegRex, TikZ (Eduardo Ochs)
- 2023-12-02 Sat 14:20-14:40 - >= 12:00 - [[emacsconf:solo][solo]]: How I play TTRPGs in Emacs (Howard Abrams)
- 2023-12-02 Sat 14:50-15:10 [[emacsconf:extending][extending]]: GNU Emacs for electronics, note-taking, and as lightweight IDE (Anand Tamariya)
- 2023-12-02 Sat 14:55-15:15 - >= 13:00 - [[emacsconf:ref][ref]]: Org-Mode workflow: informal reference tracking (Christopher Howard)
- 2023-12-02 Sat 15:25-15:35 - between 15:00-16:00 - [[emacsconf:unentangling][unentangling]]: (Un)entangling projects and repos (Alexey Bochkarev)
- 2023-12-02 Sat 15:25-16:05 [[emacsconf:gap][gap]]: Bridging the gap between emacs-devel and the community
- 2023-12-02 Sat 15:45-16:25 - >= 11:00 - [[emacsconf:hyperdrive][hyperdrive]]: hyperdrive.el: Peer-to-peer filesystem in Emacs (Joseph Turner)
- 2023-12-02 Sat 16:40-16:50 - no live Q&A - [[emacsconf:devel][devel]]: Emacs development updates (John Wiegley)
- 2023-12-02 Sat 17:00-17:10 [[emacsconf:sat-close][sat-close]]: Saturday closing remarks
- 2023-12-03 Sun 09:00-09:05 [[emacsconf:sun-open][sun-open]]: Sunday opening remarks
- 2023-12-03 Sun 09:05-09:25 - <= 12:00 - [[emacsconf:hyperamp][hyperamp]]: Top 10 ways Hyperbole amps up Emacs (Robert Weiner)
- 2023-12-03 Sun 09:40-10:00 [[emacsconf:koutline][koutline]]: Using Koutline for stream of thought journaling (Matthew Jorgensen (PlasmaStrike))
- 2023-12-03 Sun 10:00-10:20 - <= 12:00 - [[emacsconf:scheme][scheme]]: Bringing joy to Scheme programming (Andrew Tropin)
- 2023-12-03 Sun 10:10-10:20 - <= 11:00 - [[emacsconf:parallel][parallel]]: Parallel Text Replacement: Does P = NP? (Lovro, Valentino Picotti)
- 2023-12-03 Sun 10:35-10:45 - <= 13:00 - [[emacsconf:eat][eat]]: Eat and Eat powered Eshell, fast featureful terminal inside Emacs (Akib Azmain Turja)
- 2023-12-03 Sun 10:35-10:55 - <= 12:00 - [[emacsconf:test][test]]: What I learned by writing test cases for GNU Hyperbole (Mats Lidell)
- 2023-12-03 Sun 11:00-11:20 - <= 13:00 - [[emacsconf:poltys][poltys]]: The browser in a buffer (Michael Bauer)
- 2023-12-03 Sun 11:10-11:20 - between 11:00-13:00 - [[emacsconf:flat][flat]]: A modern Emacs look-and-feel without pain (Pedro A. Aranda)
- 2023-12-03 Sun 11:35-11:55 - <= 17:00 - [[emacsconf:cubing][cubing]]: Speedcubing in Emacs (Vasilij "wasamasa" Schneidermann)
- 2023-12-03 Sun 13:00-13:20 - <= 14:00 - [[emacsconf:gc][gc]]: emacs-gc-stats: Does garbage collection actually slow down Emacs? (Ihor Radchenko)
- 2023-12-03 Sun 13:00-13:40 [[emacsconf:emms][emms]]: Emacs MultiMedia System (EMMS) (Yoni Rabkin)
- 2023-12-03 Sun 13:35-13:45 [[emacsconf:lspocaml][lspocaml]]: Writing a language server in OCaml for Emacs, fun, and profit (Austin Theriault)
- 2023-12-03 Sun 13:55-14:25 [[emacsconf:steno][steno]]: Programming at 200 wpm (Daniel Alejandro Tapia)
- 2023-12-03 Sun 14:00-14:40 [[emacsconf:windows][windows]]: Windows into Freedom (Corwin Brust)
- 2023-12-03 Sun 14:35-14:45 [[emacsconf:mentor][mentor]]: Mentoring VS-Coders as an Emacsian (or How to show not tell people about the wonders of Emacs) (Jeremy Friesen)
- 2023-12-03 Sun 14:55-15:15 [[emacsconf:emacsconf][emacsconf]]: EmacsConf.org: How we use Org Mode and TRAMP to organize and run a multi-track conference (Sacha Chua)
- 2023-12-03 Sun 15:00-15:10 - >= 15:00 - [[emacsconf:hn][hn]]: The many ways to browse Hacker News from Emacs (Mickael Kerjean)
- 2023-12-03 Sun 15:25-16:05 - >= 15:00 - [[emacsconf:web][web]]: Emacs saves the Web (Yuchen Pei)
- 2023-12-03 Sun 15:30-15:50 - no live Q&A - [[emacsconf:emacsen][emacsen]]: The Emacsen family, the design of an Emacs and the importance of Lisp (Fermin)
- 2023-12-03 Sun 16:20-16:40 [[emacsconf:sharing][sharing]]: Sharing Emacs is Caring Emacs: Emacs education and why I embraced video (Jacob Boxerman)
- 2023-12-03 Sun 16:55-17:05 [[emacsconf:sun-close][sun-close]]: Sunday closing remarks
*** Schedule notes
:PROPERTIES:
:CUSTOM_ID: schedule-notes
:END:
- *Schedule changes after the schedule FYI email from 2023-10-05*:
- Moved [[emacsconf:hyperdrive][hyperdrive]] talk to general track; moved [[emacsconf:woof]] to development track and removed afternoon break. Changed [[emacsconf:woof]], emacsconf:solo, emacsconf:unentangling, emacsconf:ref, emacsconf:devel, emacsconf:sat-close, emacsconf:overlay, emacsconf:eval, emacsconf:repl, emacsconf:hyperdrive, and emacsconf:extending, but none of the talks moved by 2 hours or more, so no extra e-mails needed for now.
- [2023-10-08 Sun] Moved [[emacsconf:woof]] earlier and added [[emacsconf:gap]]
- Saturday on the General track: Org day + misc
- emacsconf:adventure is the first talk because of availability constraints; would be nice to connect it to emacsconf:solo
- emacsconf:uni for teaching, [[emacsconf:teaching]] is also related, and emacsconf:table for grading
- emacsconf:taming and emacsconf:one both deal with exports in some way. emacsconf:unentangling would be nice to add here, but that one needs to be in the afternoon because of availability constraints.
- emacsconf:writing is connected to emacsconf:nabokov (blog posts, novel). It's also a little connected to emacsconf:one (exporting a blog).
- emacsconf:collab and emacsconf:solo are amusing to pair together, but maybe following emacsconf:collab (coordinating with other people who use Org) with emacsconf:woof (Org development coordination) also makes sense and makes it so that [[emacsconf:woof]] isn't too late (Europe/Paris timezone). I put emacsconf:woof on the general track because it's Org-related and could encourage people to help out. Penciled in because bzg isn't sure he'll make it.
- [[emacsconf:unentangling]] and emacsconf:ref are also Org-related. emacsconf:ref would be nice to place together with emacsconf:nabokov, but that would move emacsconf:woof and emacsconf:unentangling too late.
- [[emacsconf:devel]] is not Org-related, but probably good to share with everyone.
- Saturday morning Development track: large language models, AI. Has to be morning because of emacsconf:matplotllm. emacsconf:llm is about general interfaces, so we can put that last. Could have a general LLM discussion after the talks. Can't swap it with Sunday morning because [[emacsconf:test]] should stick with [[emacsconf:hyperamp]] and emacsconf:koutline (Hyperbole talks), and the Hyperbole talks won't fit into Saturday morning
- Saturday afternoon, developer track: REPLs, misc talks
- start off with developer tweaks: emacsconf:overlay (compilation), and then emacsconf:eval and emacsconf:repl are paired together
- emacsconf:hyperdrive: adding another file protocol, using HTTP APIs
- [[emacsconf:extending]] might just be replays of demos + Q&A session if people are interested
- Sunday morning gen: Hyperbole (gen track, then crossing over to dev for testing) + misc talks
- Hyperbole mini-track is in the morning because of [[emacsconf:test]]'s availability constraints; emacsconf:hyperamp and emacsconf:koutline go before it. Try to avoid conflicts so they can attend each other's talks
- Sunday morning after emacsconf:test could be a fun extended "let's write tests together" session if someone wants to lead it
- emacsconf:parallel needs to go in the morning. Might be okay to include in the general talk.
- emacsconf:poltys and emacsconf:cubing aren't related to Hyperbole, but we need to fit them into the schedule somewhere. It would be nice to connect emacsconf:poltys (talking to web browsers from Emacs) to emacsconf:web (doing web stuff in Emacs instead), but emacsconf:poltys needs to be in the morning (which is pretty full) and emacsconf:web is in the afternoon because Yuchen is in Australia/Sydney.
- emacsconf:cubing can be something fun to transition to lunch, then.
- Sunday afternoon gen: misc talks, community
- emacsconf:eat is about shells and running commands, so it's generally useful
- [[emacsconf:emms]] is a user+dev talk
- community theme (emacsconf:mentor, emacsconf:hn, emacsconf:sharing), with an aside for [[emacsconf:web]] (using Emacs as a client for stuff). [[emacsconf:sharing]] is possible closing keynote - encourage people to go out and explore/share all year? If not, emacsconf:web could be good for a closing talk - encouraging people to use Emacs for more stuff.
- Sunday dev: misc dev talks
- Morning:
- emacsconf:test is related to the Hyperbole talks emacsconf:hyperamp and emacsconf:koutline, so we don't want to overlap with the Q&A for those talks
- 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:
- 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
- [[emacsconf:unentangling]], [[emacsconf:taming]]?
- emacsconf:matplotllm, emacsconf:voice, emacsconf:llm (so they don't all have to define LLMs?)
- 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
*** DONE E-mail all the speakers a link to the draft schedule
CLOSED: [2023-10-05 Thu 15:38]
so that they can confirm that I've got their availability correctly coded and ask for any adjustments in case they really want to attend someone else's Q&A session
*** TODO Check with hyperdrive and gap if they're willing to swap
:PROPERTIES:
:CUSTOM_ID: hyperdrive-gap
:END:
If Stefan Kangas puts together [[emacsconf:gap][Bridging the gap between emacs-devel
and the community]] speaking as a new Emacs maintainer, that might be
a good general closing talk on the first day because it can encourage
people to help with Emacs development. We don't have a lot of space on
the General track, but if we move [[emacsconf:hyperdrive][hyperdrive.el: Peer-to-peer
filesystem in Emacs]] to the other track, then there's enough space.
It might also be a good idea to move [[emacsconf:devel]] earlier than
[[emacsconf:unentangling]] in case John Wiegley can have a live Q&A
session (he might be travelling at that time, so it's unsure), so that
there's more time for people to ask emacs-devel highlight questions
and so that John Wiegley and Stefan Kangas can attend each other's
Q&A.
Joseph Turner wanted to make sure that people don't assume the
[[emacsconf:hyperdrive]] talk is too technical for them. We can rename the
tracks (Track A and Track B)? if that helps, so that people don't
think the other track is exclusively for more technical things.
Thoughts?
**** Option A: Here's the schedule with emacsconf:hyperdrive in the second track and emacsconf:gap in the first track.
:PROPERTIES:
:CUSTOM_ID: gap-a
:END:
#+begin_src emacs-lisp :var filename="emacsconf-hyperdrive-gap-swap.svg" :results replace :exports results
(emacsconf-schedule-test
filename
(emacsconf-time-constraints '())
(arranged
(emacsconf-schedule-inflate-sexp
'(("GEN Saturday, Dec 2" :start "2023-12-02 09:00")
sat-open
adventure
uni
teaching
table
taming
one
(lunch :start "12:00")
writing
nabokov
collab
solo
ref
(devel :track "General")
unentangling
(gap :track "General")
(sat-close)
("DEV Saturday, Dec 2" :start "2023-12-02 10:00")
(matplotllm :track "Development")
(voice :track "Development")
(llm :track "Development")
(lunch :start "12:00")
(woof :track "Development")
(overlay)
(eval)
(repl)
(extending :track "Development")
(hyperdrive :track "Development")
("GEN Sunday, Dec 3" :start "2023-12-03 09:00")
sun-open
hyperamp
koutline
(parallel :track "General")
eat
poltys
cubing
(lunch :start "12:00")
(emms :track "General")
(steno :track "General")
mentor
break
(hn :start "15:00")
web
sharing
sun-close
("DEV Sunday, Dec 3" :start "2023-12-03 10:00")
scheme
test
(flat :track "Development")
(lunch :start "12:00")
gc
lspocaml
(windows :track "Development")
(emacsconf :track "Development")
(emacsen :track "Development")
)))
(emacsconf-schedule-break-time 10)
(emacsconf-schedule-lunch-time 60)
(emacsconf-schedule-default-buffer-minutes 10)
(emacsconf-schedule-default-buffer-minutes-for-live-q-and-a 15)
(emacsconf-schedule-svg-modify-functions '(emacsconf-schedule-svg-color-by-status))
(emacsconf-schedule-validation-functions
'(emacsconf-schedule-validate-time-constraints
;; emacsconf-schedule-validate-live-q-and-a-sessions-are-staggered
emacsconf-schedule-validate-all-talks-present
emacsconf-schedule-validate-no-duplicates))
(emacsconf-schedule-strategies
'(emacsconf-schedule-allocate-buffer-time)))
#+end_src
#+RESULTS:
:results:
:end:
[[my-include:emacsconf-hyperdrive-gap-swap.svg?wrap=export html]]
**** Option B: Keep emacsconf:hyperdrive on the first track, and group emacsconf:devel and emacsconf:gap on the second track.
[[emacsconf:woof]] can be moved to before lunch, and we can encourage people to check out the different tracks in the opening remarks.
#+begin_src emacs-lisp :var filename="emacsconf-hyperdrive-gap-swap-b.svg" :results replace :exports results
(emacsconf-schedule-test
filename
(emacsconf-time-constraints '())
(arranged
(emacsconf-schedule-inflate-sexp
'(("GEN Saturday, Dec 2" :start "2023-12-02 09:00")
sat-open
adventure
uni
teaching
table
taming
one
(lunch :start "12:00")
writing
nabokov
collab
solo
ref
unentangling
(hyperdrive)
(sat-close :start "16:40")
("DEV Saturday, Dec 2" :start "2023-12-02 10:00")
(matplotllm :track "Development")
(voice :track "Development")
(llm :track "Development")
(woof :track "Development")
(lunch :start "12:00")
(overlay)
(eval)
(repl)
(extending :track "Development")
(devel :track "Development")
(gap :track "Development")
("GEN Sunday, Dec 3" :start "2023-12-03 09:00")
sun-open
hyperamp
koutline
(parallel :track "General")
eat
poltys
cubing
(lunch :start "12:00")
(emms :track "General")
(steno :track "General")
mentor
break
(hn :start "15:00")
web
sharing
sun-close
("DEV Sunday, Dec 3" :start "2023-12-03 10:00")
scheme
test
(flat :track "Development")
(lunch :start "12:00")
gc
lspocaml
(windows :track "Development")
(emacsconf :track "Development")
(emacsen :track "Development")
)))
(emacsconf-schedule-break-time 10)
(emacsconf-schedule-lunch-time 60)
(emacsconf-schedule-default-buffer-minutes 10)
(emacsconf-schedule-default-buffer-minutes-for-live-q-and-a 15)
(emacsconf-schedule-svg-modify-functions '(emacsconf-schedule-svg-color-by-status))
(emacsconf-schedule-validation-functions
'(emacsconf-schedule-validate-time-constraints
;; emacsconf-schedule-validate-live-q-and-a-sessions-are-staggered
emacsconf-schedule-validate-all-talks-present
emacsconf-schedule-validate-no-duplicates))
(emacsconf-schedule-strategies
'(emacsconf-schedule-allocate-buffer-time)))
#+end_src
#+RESULTS:
:results:
:end:
[[my-include:emacsconf-hyperdrive-gap-swap-b.svg?wrap=export html]]
**** Other ideas?
Feel free to suggest something!
Notes:
- emacsconf:sharing is nice to pair with emacsconf:mentor and emacsconf:hn and might be a good general-audience keynote-type thing as well. I don't want to schedule emacsconf:gap to compete with it.
*** TODO Announce schedule publicly
SCHEDULED: <2023-10-25 Wed>
*** TODO Incorporate "About the speaker" info on the wiki pages
Good idea to include it because that gives people (a) more context on
where a speaker is coming from, and (b) a feeling for the kinds of
backgrounds and interests people have.
*** TODO Follow up with people we haven't heard from in a while before the schedule is released
SCHEDULED: <2023-10-18 Wed>
** Prepare infrastructure
:PROPERTIES:
:CUSTOM_ID: check-infra
:END:
*** WAITING Get access to media.emacsconf.org so that we can set up the upload service and the backstage area
SCHEDULED: <2023-10-03 Tue>
:PROPERTIES:
:CREATED: [023-09-26 Tue 10:3]
:CUSTOM_ID: check-media-emacsconf
:END:
*** TODO Double-check streaming on res
:PROPERTIES:
:CUSTOM_ID: check-streaming
:END:
*** TODO Double-check icecast
:PROPERTIES:
:CUSTOM_ID: check-icecast
:END:
*** TODO Figure out a better way to handle 480p stream
It kept dropping last year and sachac didn't have the mental bandwidth to figure it out
*** BLOCKED Create pads for all the talks
:PROPERTIES:
:CUSTOM_ID: create-pads
:END:
Because the pads refer to the next and previous talks and include the talk titles, this is best done after the schedule has settled down.
*** TODO Doublecheck prerec processing workflow
:PROPERTIES:
:CUSTOM_ID: check-prerec
:END:
**** Process
***** Set up for the new year
As orga@res:
- mkdir /data/emacsconf/$year
- rm ~/current
- ln -s /data/emacsconf/$year current
- ln -s /data/emacsconf/$year $year
When we receive files
- mkdir ~/current/$slug
- copy the files to there
- ~/scripts/
I don't have access
**** Captions
:PROPERTIES:
:CUSTOM_ID: check-captions
:END:
- OpenAI Whisper SaaS (https://platform.openai.com/docs/guides/speech-to-text/longer-inputs) limits audio files to 25MB, so it's probably easier to do it ourselves
***** TODO [#C] Try out Deepgram, play around with it for last-minute submissions?
***** TODO Get the autocaptions for emms up in the backstage area, then e-mail volunteers and speakers
SCHEDULED: <2023-10-08 Sun>
**** Reencoding
:PROPERTIES:
:CUSTOM_ID: check-reencoding
:END:
*** TODO Write something for merging in information from previous years if not specified
:PROPERTIES:
:CUSTOM_ID: previous-years
:END:
- availability
- timezone
- name
- short name
- pronouns
** Prepare assets
:PROPERTIES:
:CUSTOM_ID: prepare-assets
:END:
*** TODO Generate intro slides and overlays
:PROPERTIES:
:CUSTOM_ID: generate-intro
:END:
We generate intro slides to display in between talks so that people
can find out information about the previous talk and learn about the
next talk. It includes talk titles, speaker names, URLs, and Q&A
methods. The image will also be used for an introduction video if we
can record one before the conference.
We also generate overlays that show talk information during the talk
itself.
SVGs don't support line-wrapping, so it helps to do a quick pass to
make sure all the talks are displayed properly.
*** BLOCKED Generate redirects
:PROPERTIES:
:CUSTOM_ID: generate-redirects
:END:
We use redirects for Q&A sessions with BBB web conferences so that people can easily join the web conference. This is blocked while waiting for media.emacsconf.org.
*** TODO Write 1-2 sentence intros for all the talks
:PROPERTIES:
:CUSTOM_ID: write-intros
:END:
We do a brief introduction before each talk so that people know the
topic of the next talk, the pronunciation of the speaker's name, the
pronouns to use when referring to them, and the type of Q&A that will
follow.
The template we used last year was: "In this talk, SPEAKER shares
TITLE OR SUMMARY. Afterwards, PRONOUN will handle questions over Q&A
METHOD."
This year, we asked speakers to contribute a short introduction. These
are in conf.org in the private repository. Many of the introductions
are a little longer than the template, but we might be able to handle
that. Some need to be rewritten into third-person (using the speaker's
name/pronouns instead of I). Some might be a bit of a tongue-twister
and can be rewritten to be easier to say.
We can store the introduction in the =INTRO_NOTE= property in
conf.org.
Actually recording the introductions can wait until closer to the
conference because talk titles and Q&A methods can change. We can
verify speaker name pronunciations at that time.
**** Intros :levels:
- Good: Use the same template as before: In this talk, SPEAKER shares
TITLE OR SUMMARY. Afterwards, PRONOUN will handle questions over Q&A
METHOD.
- Better: Include some more biographical information to give listeners some context.
**** DONE Do we want to use honorifics like Dr.? :decision:
CLOSED: [2023-10-03 Tue 15:38] DEADLINE: <2023-11-14 Tue>
:PROPERTIES:
:CUSTOM_ID: honorifics
:END:
DECISION: Include in the intro-review email:
#+begin_quote
We will usually introduce you by your first name (or handle, if you
prefer to go by a pseudonym) but if you'd rather be introduced
differently (for example honorific followed by last-name, or whatever
you prefer), just let us know.
#+end_quote
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 (as in previous EmacsConfs)
- Equality
- votes: zaeph
- CHOSEN: Asking speakers if they want us to use any honorifics in their intro:
- Observes personal preferences
- votes: corwin, max, jc (We can also say that we prefer not to use honorifics (it's not an academic
- Corwin's suggested wording: We will usually introduce you by your first name (or handle, if you prefer to go by a pseudonym) but if you'd rather be introduced
differently (for example honorific followed by last-name, or
whatever you prefer) just let us know.
conference) but we respect people's preferences.)
- OPTION: Using honorifics based on e-mail signatures and intros:
- Recognizes credentials
*** BLOCKED Record intro videos with 1-2 sentence intros for all the talks
:PROPERTIES:
:CUSTOM_ID: record-intros
:END:
** Coordinate volunteers
:PROPERTIES:
:CUSTOM_ID: coordinate-volunteers
:END:
*** TODO Prepare shift calendar
:PROPERTIES:
:CUSTOM_ID: shifts
:END:
#+BEGIN_EXPORT md
<a name="shifts"></a>
#+END_EXPORT
AM: 9-12 PM EST, PM: 1-5 PM EST (plus a little extra for setup/transition)
Saturday Dec 2 2023
#+NAME: saturday-shifts
| | [[https://emacsconf.org/2023/volunteer/host/][Host]] | Streamer | [[https://emacsconf.org/2023/volunteer/checkin/][Checkin]] | [[https://emacsconf.org/2023/volunteer/irc/][IRC]] | [[https://emacsconf.org/2023/volunteer/pad/][Pad]] | Coord |
|--------+------+----------+---------+-----+-----+-------|
| Gen AM | | sachac | | | | sachac |
| Gen PM | | sachac | | | | sachac |
| Dev AM | | sachac | | | | sachac |
| Dev PM | | sachac | | | | sachac |
Sunday Dec 3 2023
#+NAME: sunday-shifts
| | [[https://emacsconf.org/2023/volunteer/host/][Host]] | Streamer | [[https://emacsconf.org/2023/volunteer/checkin/][Checkin]] | [[https://emacsconf.org/2023/volunteer/irc/][IRC]] | [[https://emacsconf.org/2023/volunteer/pad/][Pad]] | Coord |
|--------+------+----------+---------+-----+-----+--------|
| Gen AM | | sachac | | | | sachac |
| Gen PM | | sachac | | | | sachac |
| Dev AM | | sachac | | | | sachac |
| Dev PM | | sachac | | | | sachac |
Backups:
- dev host/streamer:
- gen host/streamer:
- checkin, IRC, pad:
Interested in a shift? Please e-mail [[mailto:emacsconf-org-private@gnu.org]] and we'll help you figure out what you need to learn.
#+begin_src emacs-lisp :var sat=saturday-shifts :var sun=sunday-shifts :rownames no :colnames no :results verbatim replace
`(setq emacsconf-shifts
(list
,@(apply #'append
(mapcar
(lambda (day)
(let ((headers (mapcar (lambda (field) (intern (concat ":" (downcase field))))
(cdr (car (cadr day))))))
(mapcar
(lambda (row)
(apply #'append
(list 'list :id
(when (string-match "^\\([^ ]+\\) \\(AM\\|PM\\)" (car row))
(format "%s-%s-%s"
(car day)
(downcase (match-string 2 (car row)))
(downcase (match-string 1 (car row)))))
:track
(if (string-match "^Gen" (car row)) "General" "Development")
:start
(format "%sT%s:00:00%s"
(elt day 2)
(if (string-match "AM" (car row)) "08" "13")
emacsconf-timezone-offset)
:end
(format "%sT%s:00:00%s"
(elt day 2)
(if (string-match "AM" (car row)) "12" "18")
emacsconf-timezone-offset))
(seq-map-indexed
(lambda (value index)
(unless (string= value "")
(list (elt headers index) value)))
(cdr row))))
(cdr (cadr day)))
))
(list
(list "sat" sat "2022-12-03")
(list "sun" sun "2022-12-04"))))))
#+end_src
*** DONE Document volunteer roles
CLOSED: [2023-09-26 Tue 11:07]
:PROPERTIES:
:CUSTOM_ID: document-volunteer-roles
:END:
Copied it over from the previous year
* Progress reports
:PROPERTIES:
:CUSTOM_ID: progress
:END:
- https://emacsconf.org/blog/2023-08-14-cfp-progress/
- https://emacsconf.org/blog/2023-09-25-draft-schedule
* E-mail templates
:PROPERTIES:
:CUSTOM_ID: templates
:END:
** Review
:PROPERTIES:
:CUSTOM_ID: review
:END:
*** Template
:PROPERTIES:
:EMAIL_ID: review
:CUSTOM_ID: review-template
:END:
Thanks for submitting your proposal! (ZZZ: feedback) We're experimenting
with early acceptance this year, so we'll wait a week in case the
other volunteers want to chime in regarding your talk. =)
** Acceptance
:PROPERTIES:
:CUSTOM_ID: acceptance
:END:
*** Function
:PROPERTIES:
:CUSTOM_ID: acceptance-func
:END:
#+begin_src emacs-lisp
(defun emacsconf-mail-accept-talk (talk &optional template)
(interactive (list (emacsconf-complete-talk-info)))
(emacsconf-mail-prepare
(or template (emacsconf-mail-merge-get-template "acceptance"))
(plist-get talk :email)
(list
:title (plist-get talk :title)
:email (plist-get talk :email)
:time (plist-get talk :time)
:conf-name emacsconf-name
:speakers-short (plist-get talk :speakers-short)
:url (concat emacsconf-base-url (plist-get talk :url))
:video-target-date emacsconf-video-target-date
:year emacsconf-year)))
#+end_src
*** Template
:PROPERTIES:
:EMAIL_ID: acceptance
:TO: ${email}
:REPLY_TO: emacsconf-submit@gnu.org, ${email}, sacha@sachachua.com
:MAIL_FOLLOWUP_TO: emacsconf-submit@gnu.org, ${email}, sacha@sachachua.com
:CC: emacsconf-submit@gnu.org
:LOG_NOTE: accepted talk
:SUBJECT: ${conf-name} ${year} acceptance: ${title}
:FUNCTION: emacsconf-mail-accept-talk
:CUSTOM_ID: acceptance-template
:END:
Hi, ${speakers-short}!
Looks like all systems are a go for your talk. =) Thanks for proposing
it! Your talk page is now at ${url} . Please feel free to update it or
e-mail us if you'd like help with any changes.
If you want to get started on your talk early, we have some
instructions at https://emacsconf.org/${year}/prepare/ that might help.
We strongly encourage speakers to prepare a talk video by
${video-target-date} in order to reduce technical risks and make
things flow more smoothly. Plus, we might be able to get it captioned
by volunteers, just like the talks last year. We'll save ${time} minutes
for your talk, not including time for Q&A. Don't sweat it if
you're a few minutes over or under. If it looks like a much shorter or
longer talk once you start getting into it, let us know and we might
be able to adjust.
I'll follow up with the specific schedule for your talk once things
settle down. In the meantime, please let us know if you have any
questions or if there's anything we can do to help out!
Sacha
* Archive
:PROPERTIES:
:CUSTOM_ID: archive
:END:
** DONE Test the idea of three tracks and more aligned times :decision:
CLOSED: [2023-10-03 Tue 15:35] DEADLINE: <2023-10-13 Fri>
:PROPERTIES:
:CUSTOM_ID: three-tracks
:END:
Decision: We'll stick with the two-track schedule for now because it's
more likely, and we'll adjust as we get closer to the conference
depending on speaker submissions and on volunteer availability.
Note: 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
- votes: max (Three tracks is the best policy if you’re more than 75% sure that you can round up the volunteers)
- [[#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)
(cl-loop
with track = (plist-get (car list) :track)
with track-names = (seq-map (lambda (o) (plist-get o :name)) emacsconf-tracks)
for talk in list
collect
(progn
(when (member (plist-get talk :track) track-names)
(setq track (plist-get talk :track)))
(append (list :track track) talk))))
#+end_src
#+begin_src emacs-lisp :results value replace :exports results :var filename="schedule-option-aligned-talks.svg" :eval never-export
(emacsconf-schedule-test
filename
(emacsconf-schedule-tracks
'((:label "Saturday"
:start "2023-12-02 9:00"
:end "2023-12-02 18:00"
:tracks ("A" "B" "C"))
(:label "Sunday"
:start "2023-12-03 9:00"
:end "2023-12-03 18:00"
:tracks ("A" "B" "C"))))
(emacsconf-time-constraints '())
(emacsconf-tracks
'((:name "A" :id "a")
(:name "B" :id "b")
(:name "C" :id "c")))
(arranged
(emacsconf-schedule-inflate-sexp
'(("A Saturday, Dec 2" :start "2023-12-02 09:00" :track "A")
(sat-open)
adventure
(uni :start "9:40")
(table :start "10:30")
(teaching :start "11:15")
(lunch :start "12:00" :time 60)
collab
(woof :start nil)
(solo :start nil)
(hn :start "15:00")
(web :start nil)
sat-close
("B Saturday, Dec 2" :start "2023-12-02 09:40" :track "B")
(one :start nil)
(poltys :start "10:30")
(taming :start "11:15")
(lunch :start "12:00" :time 60)
writing
(nabokov :start "13:40")
(steno :start "14:20")
(emacsen :start "15:30")
("C Saturday, Dec 2" :start "2023-12-02 9:40" :track "C")
(matplotllm)
(voice :start "10:30")
(llm :start "11:15")
(lunch :start "12:00" :time 60)
overlay
eval
(repl :start "14:20")
(emacsconf :start "15:30")
("A Sunday, Dec 3" :start "2023-12-03 09:00" :track "A")
(sun-open :time 10)
hyperamp
(koutline :start "10:00")
(test :start "11:00")
(lunch :start "12:00" :time 60)
(emms :start nil)
(devel :start "14:00")
(mentor :start nil)
(sharing :start "15:00")
(sun-close :start "16:00")
("B Sunday, Dec 3" :start "2023-12-03 09:10" :track "B")
(parallel :start "10:00")
(eat :start "10:30")
(gc :start "11:00")
(lunch :start "12:00" :time 60)
hyperdrive
(ref :start "14:00")
(unentangling :start "15:00")
("C Sunday, Dec 3" :start "2023-12-03 09:10" :track "C")
(scheme :start "10:00")
(lspocaml :start "11:00")
(flat :start "11:30")
(lunch :start "12:00" :time 60)
(windows :start nil)
(cubing :start "14:00")
(extending :start "15:00")
)))
(emacsconf-schedule-break-time 10)
(emacsconf-schedule-lunch-time 60)
(emacsconf-schedule-default-buffer-minutes 20)
(emacsconf-schedule-svg-modify-functions '(emacsconf-schedule-svg-color-by-status))
(emacsconf-schedule-default-buffer-minutes-for-live-q-and-a 20)
(emacsconf-schedule-validation-functions
'(emacsconf-schedule-validate-time-constraints
;; emacsconf-schedule-validate-live-q-and-a-sessions-are-staggered
emacsconf-schedule-validate-all-talks-present
emacsconf-schedule-validate-no-duplicates))
(emacsconf-schedule-strategies
'(emacsconf-schedule-copy-previous-track emacsconf-schedule-allocate-buffer-time)))
#+end_src
#+RESULTS:
:results:
:end:
#+begin_comment
[[file:schedule-option-aligned-talks.svg]]
#+end_comment
#+INCLUDE: schedule-option-aligned-talks.svg export html
*** Three tracks for Sunday morning?
:PROPERTIES:
:CUSTOM_ID: three-tracks-sun-am
:END:
#+begin_src emacs-lisp :results value replace :exports results :var filename="schedule-option-sun-am.svg" :eval never-export
(emacsconf-schedule-test
filename
(emacsconf-schedule-tracks
'((:label "Saturday"
:start "2023-12-02 9:00"
:end "2023-12-02 18:00"
:tracks ("A" "B" "C"))
(:label "Sunday"
:start "2023-12-03 9:00"
:end "2023-12-03 18:00"
:tracks ("A" "B" "C"))))
(emacsconf-time-constraints '())
(emacsconf-tracks
'((:name "A" :id "a")
(:name "B" :id "b")
(:name "C" :id "c")))
(arranged
(emacsconf-schedule-inflate-sexp
'(("A Saturday, Dec 2" :start "2023-12-02 09:00" :track "A")
sat-open
adventure
uni
table
teaching
writing
(lunch :start "12:00")
nabokov
collab
(woof)
solo
unentangling
ref
(devel)
(sat-close)
("DEV Saturday, Dec 2" :start "2023-12-02 10:00" :track "B")
(matplotllm)
(voice)
(llm)
(lunch :start "12:00")
(overlay)
(eval)
(repl :start "14:00")
(hyperdrive)
(extending)
("GEN Sunday, Dec 3" :start "2023-12-03 09:00" :track "A")
sun-open
hyperamp
koutline
one
cubing
(lunch :start "12:00" :time 60)
(emms)
taming
mentor
(hn :start "15:00")
web
sharing
sun-close
("DEV Sunday, Dec 3" :start "2023-12-03 10:00" :track "B")
scheme
eat
(flat)
lspocaml
(lunch :start "12:15" :time "45")
gc
(steno)
(windows)
(emacsen)
(emacsconf)
("C Sunday Dec 3" :start "2023-12-03 10:00" :track "C")
poltys
(parallel)
test
)))
(emacsconf-schedule-break-time 10)
(emacsconf-schedule-lunch-time 60)
(emacsconf-schedule-default-buffer-minutes 20)
(emacsconf-schedule-svg-modify-functions '(emacsconf-schedule-svg-color-by-status))
(emacsconf-schedule-default-buffer-minutes-for-live-q-and-a 20)
(emacsconf-schedule-validation-functions
'(emacsconf-schedule-validate-time-constraints
;; emacsconf-schedule-validate-live-q-and-a-sessions-are-staggered
emacsconf-schedule-validate-all-talks-present
emacsconf-schedule-validate-no-duplicates))
(emacsconf-schedule-strategies
'(emacsconf-schedule-copy-previous-track emacsconf-schedule-allocate-buffer-time)))
#+end_src
#+RESULTS:
:results:
:end:
#+begin_comment
[[file:schedule-option-sun-am.svg]]
#+end_comment
#+INCLUDE: schedule-option-sun-am.svg export html
