summaryrefslogtreecommitdiffstats
path: root/2023
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2023-06-18 15:09:30 -0400
committerSacha Chua <sacha@sachachua.com>2023-06-18 15:09:30 -0400
commit98548235682f86d3be9753e67527001599931b94 (patch)
treed1fe13aa93712532659eb05fa5a293d0e69c815d /2023
parent7a9d76a0cca8cbd827231f8baca58353a262b23c (diff)
downloademacsconf-wiki-98548235682f86d3be9753e67527001599931b94.tar.xz
emacsconf-wiki-98548235682f86d3be9753e67527001599931b94.zip
Emphasize Q&A by putting it into its own paragraph
Diffstat (limited to '2023')
-rw-r--r--2023/cfp.org10
1 files changed, 5 insertions, 5 deletions
diff --git a/2023/cfp.org b/2023/cfp.org
index 15bfa916..546e0922 100644
--- a/2023/cfp.org
+++ b/2023/cfp.org
@@ -129,13 +129,13 @@ Think of 20+ minutes presentation as extensions of the 10-minute
presentation. If you are aiming at the 10-minute presentation, just
write an outline of what you plan to talk about if you have 5-10
minutes. If you’d like to propose a longer talk, add an outline of
-what you might add to the first part if you had more time to present
-(up to 40 minutes, including Q&A).
-
+what you might add to the first part if you had more time to present.
20 minutes seems to be the best length for a presentation: short
enough to keep people's attention, long enough to get into some
-details. There will be time for questions and answers after your talk,
-so you don't need to include that in your talk timing.
+details.
+
+There will be time for questions and answers after your talk, so you
+don't need to include that in your talk timing.
Here's an example proposal for a 20-minute talk. Your proposal
would include the 10- and 20- minute sections: