add lessons learned, some speaker bios

6 files changed, 65 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
diff --git a/2023/talks/adventure.md b/2023/talks/adventure.md
index 65e646c1..28bc710f 100644
--- a/2023/talks/adventure.md
+++ b/2023/talks/adventure.md
@@ -19,7 +19,10 @@ to use the built-in Emacs help system, the mechanic of emacs
 customization and the basics of programming Emacs Lisp. I believe this
 game is ideal as a light-hearted complement to the `C-h t` tutorial.
 
+About the speaker:
 
+Dr. Chung-hong Chan is a senior researcher at GESIS Leibniz Institute
+for the Social Sciences, Germany.
 
 [[!inline pages="internal(2023/info/adventure-after)" raw="yes"]]
 
diff --git a/2023/talks/table.md b/2023/talks/table.md
index aef1bc08..50c45fef 100644
--- a/2023/talks/table.md
+++ b/2023/talks/table.md
@@ -23,6 +23,17 @@ I’ll demonstrate some functionality I use for:
 
 For several years, I have been using that workflow, and I consider it is very natural with many advantages, like writing the reasons/feedback in the same file with the qualifications, or to be able to use a version control.
 
+About the speaker:
+
+My name is Daniel Molina Cabrera, I am a senior lecturer in Computer
+Science at the University of Granada, in Spain. I use only Linux in my
+computer, and after been using Vim many years, last years I mainly use
+Emacs for editing, as file manager, as email program, ...
+
+In my experience, using org-table is very powerful and useful, but
+many interesting features are not well-known. Unfortunately, sometimes
+it is difficult to see examples showing the possibilities, and I think
+this example could be very informative.
 
 
 [[!inline pages="internal(2023/info/table-after)" raw="yes"]]
diff --git a/2023/talks/taming.md b/2023/talks/taming.md
index b175e992..04246b62 100644
--- a/2023/talks/taming.md
+++ b/2023/talks/taming.md
@@ -28,6 +28,14 @@ computer will work for you, rather than the other way around.
 Because Emacs and Org mode can bend time and space - at least in a way,
 and you don't even need M-x butterfly!
 
+About the speaker:
+
+I'm a tiny mouse, a hacker. I like to play with things. I'm also very
+opinionated. These things don't always mix well. When I wanted to play with
+NixOS and Doom Emacs, I faced a problem: I don't like the Nix language, and I
+don't like how Doom's config has to be structured. I really wanted to play with
+both, though. So I tamed them. With Org Mode. I'd love to tell you how, so you
+can do the same.
 
 
 [[!inline pages="internal(2023/info/taming-after)" raw="yes"]]
diff --git a/2023/talks/uni.md b/2023/talks/uni.md
index bbababf5..e2628b1a 100644
--- a/2023/talks/uni.md
+++ b/2023/talks/uni.md
@@ -16,6 +16,14 @@ workflows? It's not only possible, it's much more flexible and empowering than b
 entire software stack and workflows for authoring and presenting lessons, authoring and evaluating assessments, and engaging students both in
 person and in fully online teaching environments.
 
+About the speaker:
+
+James Endres Howell has taught Molecular and Cell Biology,
+Biochemistry, Microbiology, Immunology, Toxicology, and Molecular
+Medicine at Penn State since 2006. Recently Dr. Howell has developed
+popular courses for non-science majors in Genetics, Ecology and
+Evolution; Science in Literature; and Science in Society. He has used
+Emacs daily since 1988.
 
 
 [[!inline pages="internal(2023/info/uni-after)" raw="yes"]]
diff --git a/2023/talks/writing.md b/2023/talks/writing.md
index 6c21a732..f40ad646 100644
--- a/2023/talks/writing.md
+++ b/2023/talks/writing.md
@@ -29,6 +29,14 @@ And with a complete post, I’ll then walk through the resulting export.
 Demonstrating the output to Hugo (and its shortcodes) as well as other
 formats.
 
+About the speaker:
+
+Jeremy Friesen is a long-time software developer but only recently an
+Emacs convert (as of May 2020). When he switched to writing posts
+using Emacs, he observed an explosion in writing, in part because of
+the joy of using a tool that he can shape and extend to meet his needs
+and wants.
+
 [[!inline pages="internal(2023/info/writing-after)" raw="yes"]]
 
 [[!inline pages="internal(2023/info/writing-nav)" raw="yes"]]