summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorSacha Chua <sacha@sachachua.com>2024-06-03 09:54:59 -0400
committerSacha Chua <sacha@sachachua.com>2024-06-03 09:55:29 -0400
commitd147fd387b90e7e1669c84278a83c3d843270085 (patch)
tree67f11ac660ebbf33f5eea403a60a0ad6701c85db
parent4ebf9644a63780ce1fd1c86ecc1f596f652a045a (diff)
downloademacsconf-wiki-d147fd387b90e7e1669c84278a83c3d843270085.tar.xz
emacsconf-wiki-d147fd387b90e7e1669c84278a83c3d843270085.zip
initial draft
-rw-r--r--2024/cfp.md113
-rw-r--r--2024/cfp.org183
2 files changed, 296 insertions, 0 deletions
diff --git a/2024/cfp.md b/2024/cfp.md
new file mode 100644
index 00000000..805a931b
--- /dev/null
+++ b/2024/cfp.md
@@ -0,0 +1,113 @@
+
+
+[[!meta title="Call for Participation"]]
+[[!meta copyright="Copyright &copy; 2020 Amin Bandali, Sacha Chua,
+David Bremner<br />
+Copyright &copy; 2021 Amin Bandali, Sacha Chua, Leo Vivier,
+Sebastian Crane<br />
+Copyright &copy; 2022 Amin Bandali<br />
+Copyright &copy; 2023-2024 Sacha Chua"]]
+<!-- cfp.md is exported from cfp.org, please modify that instead. -->
+
+
+# Call for participation
+
+What have you found exciting about [Emacs](https://www.gnu.org/software/emacs/) lately? Have you figured out
+a good workflow? Used Emacs for something interesting? Come share
+what you've been learning at EmacsConf 2024 and meet other enthusiasts
+along the way! All backgrounds and all levels of experience are
+welcome. Emacs isn't just a text editor, it's a way of life!
+
+Not sure what to talk about? We've shared a few [ideas](https://emacsconf.org/2024/ideas/) to help you get
+started.
+
+[EmacsConf 2024](https://emacsconf.org/2024/) will be a virtual conference on **December 7 and 8, 2024
+(Sat-Sun, 9AM-5PM UTC-5 / 2PM-10PM UTC)**. If you'd like to present at
+the conference, please **[submit your proposal](https://emacsconf.org/2024/cfp/)** by **September 20, 2024
+(Friday)**. You can also take a look at [previous talks](https://emacsconf.org/talks) to see how
+your talk can add to other ideas!
+
+We'll send out rolling acceptances, so feel free to get the conversation
+started early! If there are similar proposals, we'll work with people so
+that the talks can cover different facets.
+
+
+# Talk formats
+
+Ideally, talks will be prerecorded so that you can script and edit
+them as tightly as you want, and so that they can be captioned for
+accessibility. Here are the talk options:
+
+- **5-10 minute lightning talk:** just the essentials! If you can
+ squeeze your prerecorded talk into 5-10 minutes by focusing on the
+ essentials (not by talking super quickly!), we might be able to
+ repeat it during the conference in order to fill gaps.
+- **20-minute talk:** 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. Just like in EmacsConf
+2022, you can answer questions via a live BigBlueButton web
+conference, IRC ([Internet Relay Chat](https://chat.emacsconf.org)), the Etherpad (a web-based
+collaborative document), the wiki, or e-mail (your choice). The stream
+will move on to the next talk at the scheduled time, but interested
+people can keep hanging out with you for a longer conversation.
+
+If you are not available during the conference itself but you have
+a neat idea that you'd like to share, please propose it anyway!
+You can always handle questions after the conference, and we might
+even be able to coordinate with other Emacs meetups for events in
+other timezones.
+
+We may have time for a few longer sessions. If you'd like to be
+considered for a longer time slot, please include an outline for the
+extra time in addition to your 20-minute proposal. Other session
+formats such as tutorials, workshops, and hangouts are welcome as
+well.
+
+
+# Submitting your proposal
+
+[Send us your idea](https://emacsconf.org/2024/submit/) as soon as you can, so that you can have more time
+to work on your talk. (Proposal deadline: Friday, September 20, 2024)
+
+If you need help, you can e-mail us publicly at [emacsconf-org@gnu.org](mailto:emacsconf-org@gnu.org)
+or privately at [emacsconf-org-private@gnu.org](mailto:emacsconf-org-private@gnu.org). You can also come and
+say hi to us on our IRC channel `#emacsconf` on `irc.libera.chat`
+using [your favourite IRC client](ircs://irc.libera.chat:6697/emacsconf), or by visiting [chat.emacsconf.org](https://chat.emacsconf.org) in
+your web browser.
+
+
+# Know someone who might have something to share?
+
+All kinds of people use Emacs for all kinds of things. We'd love it
+if EmacsConf 2024 could highlight interesting perspectives and reflect
+the diversity of our community. If you know someone who might have a
+good idea for a talk, please reach out to them and encourage them to
+submit a proposal. Many people (especially from underrepresented
+groups such as women, people of colour, non-developers, etc.) might
+not consider themselves proficient enough to share their thoughts.
+If you let them know that you value their knowledge and experiences,
+and maybe even suggest something that you think others would like to
+hear about, they may realize that they do have something worth sharing
+and that we would love to hear from them.
+
+
+# Want to volunteer?
+
+If you would like to help with the conference (planning the sessions,
+reviewing proposals, helping with infrastructure, making sessions more
+accessible, editing video transcripts, checking in speakers,
+reading questions out loud, organizing notes, etc.), please see our [volunteer](https://emacsconf.org/2024/volunteer/) page.
+Volunteers get early access to talks and learn lots of things along
+the way. We'd really appreciate your help in making EmacsConf 2024
+the best one so far!
+
+
+# Commitment to freedom
+
+We remain fully committed to freedom. You'll be able to participate
+in EmacsConf using [free/libre software](https://www.gnu.org/philosophy/free-sw.html), and we use free/libre software
+to organize and run the conference. You can find some notes about our
+setup and process at <https://emacsconf.org/infra/>.
+
diff --git a/2024/cfp.org b/2024/cfp.org
new file mode 100644
index 00000000..d2106b05
--- /dev/null
+++ b/2024/cfp.org
@@ -0,0 +1,183 @@
+# [[elisp:(org-md-export-to-markdown)][Export this file to Markdown]]
+# [[elisp:(org-ascii-export-as-ascii nil nil nil t)][Export this file to ASCII]]
+
+[[!template id=pagedraft]]
+#+title: EmacsConf 2024
+#+subtitle: Online Conference
+#+date: December 7 and 8, 2024
+#+options: author:nil toc:nil
+
+#+begin_export md
+[[!meta title="Call for Participation"]]
+[[!meta copyright="Copyright &copy; 2020 Amin Bandali, Sacha Chua,
+David Bremner<br />
+Copyright &copy; 2021 Amin Bandali, Sacha Chua, Leo Vivier,
+Sebastian Crane<br />
+Copyright &copy; 2022 Amin Bandali<br />
+Copyright &copy; 2023-2024 Sacha Chua"]]
+<!-- cfp.md is exported from cfp.org, please modify that instead. -->
+#+end_export
+
+* COMMENT How to export this file :noexport:
+
+The ircs link type is not part of standard Org
+Mode, so Org will will throw an error if you try
+to export this file.
+
+To work around that, you can use something along the lines of the
+Emacs Lisp code below by either adding it to your init file, or by
+putting the point in the code block and hitting =C-c C-v e= (that is,
+hold Ctrl, then hit c followed by v, then release Ctrl, and hit e) to
+evaluate the code, working around the issue only for the current
+session.
+
+#+begin_src emacs-lisp :results silent
+(org-link-set-parameters
+ "ircs"
+ :export
+ (lambda (link description format)
+ "Export an ircs link.
+See `org-link-parameters' for details about LINK, DESCRIPTION and
+FORMAT."
+ (let ((desc (or description link)))
+ (pcase format
+ (`html (format "<a href=\"ircs:%s\">%s</a>" link desc))
+ (`md (format "[%s](ircs:%s)" desc link))
+ (_ nil)))))
+#+end_src
+
+Other CFPs we can borrow ideas from:
+
+- https://debconf23.debconf.org/cfp/ - includes early submission timeline
+- https://fosdem.org/2023/news/2022-11-13-call-for-presentations/ - mentions upload date, license
+- https://www.fsf.org/blogs/community/libreplanet-2023-will-be-held-march-18-19-cfs-extended-to-november-23
+- https://www.reddit.com/r/scala/comments/103v6e5/scalar_2023_cfp_is_still_open/ - very short
+
+* Call for participation
+:PROPERTIES:
+:CUSTOM_ID: cfp
+:END:
+
+What have you found exciting about [[https://www.gnu.org/software/emacs/][Emacs]] lately? Have you figured out
+a good workflow? Used Emacs for something interesting? Come share
+what you've been learning at EmacsConf 2024 and meet other enthusiasts
+along the way! All backgrounds and all levels of experience are
+welcome. Emacs isn't just a text editor, it's a way of life!
+
+Not sure what to talk about? We've shared a few [[https://emacsconf.org/2024/ideas/][ideas]] to help you get
+started.
+
+[[https://emacsconf.org/2024/][EmacsConf 2024]] will be a virtual conference on *December 7 and 8, 2024
+(Sat-Sun, 9AM-5PM UTC-5 / 2PM-10PM UTC)*. If you'd like to present at
+the conference, please *[[https://emacsconf.org/2024/cfp/][submit your proposal]]* by *September 20, 2024
+(Friday)*. You can also take a look at [[https://emacsconf.org/talks][previous talks]] to see how
+your talk can add to other ideas!
+
+We'll send out rolling acceptances, so feel free to get the conversation
+started early! If there are similar proposals, we'll work with people so
+that the talks can cover different facets.
+
+* Talk formats
+:PROPERTIES:
+:CUSTOM_ID: formats
+:END:
+
+Ideally, talks will be prerecorded so that you can script and edit
+them as tightly as you want, and so that they can be captioned for
+accessibility. Here are the talk options:
+
+- *5-10 minute lightning talk:* just the essentials! If you can
+ squeeze your prerecorded talk into 5-10 minutes by focusing on the
+ essentials (not by talking super quickly!), we might be able to
+ repeat it during the conference in order to fill gaps.
+- *20-minute talk:* 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. Just like in EmacsConf
+2022, you can answer questions via a live BigBlueButton web
+conference, IRC ([[https://chat.emacsconf.org][Internet Relay Chat]]), the Etherpad (a web-based
+collaborative document), the wiki, or e-mail (your choice). The stream
+will move on to the next talk at the scheduled time, but interested
+people can keep hanging out with you for a longer conversation.
+
+If you are not available during the conference itself but you have
+a neat idea that you'd like to share, please propose it anyway!
+You can always handle questions after the conference, and we might
+even be able to coordinate with other Emacs meetups for events in
+other timezones.
+
+We may have time for a few longer sessions. If you'd like to be
+considered for a longer time slot, please include an outline for the
+extra time in addition to your 20-minute proposal. Other session
+formats such as tutorials, workshops, and hangouts are welcome as
+well.
+
+* Submitting your proposal
+:PROPERTIES:
+:CUSTOM_ID: submitting
+:END:
+
+[[https://emacsconf.org/2024/submit/][Send us your idea]] as soon as you can, so that you can have more time
+to work on your talk. (Proposal deadline: Friday, September 20, 2024)
+
+If you need help, you can e-mail us publicly at [[mailto:emacsconf-org@gnu.org][emacsconf-org@gnu.org]]
+or privately at [[mailto:emacsconf-org-private@gnu.org][emacsconf-org-private@gnu.org]]. You can also come and
+say hi to us on our IRC channel =#emacsconf= on =irc.libera.chat=
+using [[ircs://irc.libera.chat:6697/emacsconf][your favourite IRC client]], or by visiting [[https://chat.emacsconf.org][chat.emacsconf.org]] in
+your web browser.
+
+* Know someone who might have something to share?
+:PROPERTIES:
+:CUSTOM_ID: sharing
+:END:
+
+All kinds of people use Emacs for all kinds of things. We'd love it
+if EmacsConf 2024 could highlight interesting perspectives and reflect
+the diversity of our community. If you know someone who might have a
+good idea for a talk, please reach out to them and encourage them to
+submit a proposal. Many people (especially from underrepresented
+groups such as women, people of colour, non-developers, etc.) might
+not consider themselves proficient enough to share their thoughts.
+If you let them know that you value their knowledge and experiences,
+and maybe even suggest something that you think others would like to
+hear about, they may realize that they do have something worth sharing
+and that we would love to hear from them.
+
+* Want to volunteer?
+:PROPERTIES:
+:CUSTOM_ID: volunteer
+:END:
+
+If you would like to help with the conference (planning the sessions,
+reviewing proposals, helping with infrastructure, making sessions more
+accessible, editing video transcripts, checking in speakers,
+reading questions out loud, organizing notes, etc.), please see our [[https://emacsconf.org/2024/volunteer/][volunteer]] page.
+Volunteers get early access to talks and learn lots of things along
+the way. We'd really appreciate your help in making EmacsConf 2024
+the best one so far!
+
+* Commitment to freedom
+
+We remain fully committed to freedom. You'll be able to participate
+in EmacsConf using [[https://www.gnu.org/philosophy/free-sw.html][free/libre software]], and we use free/libre software
+to organize and run the conference. You can find some notes about our
+setup and process at https://emacsconf.org/infra/.
+
+* COMMENT Copyright & License
+
+Copyright (c) 2020 Amin Bandali, Sacha Chua, David Bremner
+Copyright (c) 2021 Amin Bandali, Sacha Chua, Leo Vivier,
+Sebastian Crane
+Copyright (c) 2022 Amin Bandali
+Copyright (c) 2023-2023 Sacha Chua
+
+The EmacsConf 2024 Call for Participation is part of the EmacsConf
+wiki, and is dual-licensed under the terms of the Creative Commons
+Attribution-ShareAlike 4.0 International Public License; and the GNU
+General Public License as published by the Free Software Foundation,
+either version 3 of the License, or (at your option) any later
+version.
+
+A copy of these two licenses is available on the EmacsConf wiki, in
+the [[https://emacsconf.org/COPYING.CC-BY-SA][COPYING.CC-BY-SA]] and [[https://emacsconf.org/COPYING.GPL][COPYING.GPL]] files.