summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAmin Bandali <bandali@gnu.org>2020-08-21 01:34:45 -0400
committerAmin Bandali <bandali@gnu.org>2020-08-21 01:34:45 -0400
commit9b2c6e9d8943d5cf5b69c52a846f937e85e2cb66 (patch)
treec6699155d63db588db99e2357fbbbd9fac3c97d8
parent6195213c090f7d3b57354fc009b46d793c7704e1 (diff)
downloademacsconf-wiki-9b2c6e9d8943d5cf5b69c52a846f937e85e2cb66.tar.xz
emacsconf-wiki-9b2c6e9d8943d5cf5b69c52a846f937e85e2cb66.zip
2020/emacsconf-2020-cfp.org: add
This is the Org file that I export to ASCII and send to mailing lists.
-rw-r--r--2020/emacsconf-2020-cfp.org133
1 files changed, 133 insertions, 0 deletions
diff --git a/2020/emacsconf-2020-cfp.org b/2020/emacsconf-2020-cfp.org
new file mode 100644
index 00000000..d33ea0c1
--- /dev/null
+++ b/2020/emacsconf-2020-cfp.org
@@ -0,0 +1,133 @@
+#+title: EmacsConf 2020
+#+subtitle: Online Conference
+#+date: November 28 and 29, 2020
+#+options: author:nil
+
+The [[https://emacsconf.org/2020/cfp/][Call for Proposals]] for [[https://emacsconf.org/2020/][EmacsConf 2020]] talks is now open, until
+*September 30, 2020*.
+
+After a successful EmacsConf 2019, we are back again this year and are
+once again calling for your participation!
+
+EmacsConf is the conference about the joy of [[https://www.gnu.org/software/emacs/emacs.html][Emacs]], Emacs Lisp, and
+memorizing key sequences.
+
+We are holding EmacsConf 2020 as a virtual (online) conference again
+this year, especially now, given the current state of the world with
+the ongoing global pandemic. We remain fully committed to freedom,
+and we will continue using our infrastructure and streaming setup
+consisting entirely of [[https://www.gnu.org/philosophy/free-sw.html][free software]], much like the last EmacsConf.
+
+We welcome speakers of *all backgrounds* and *all levels of
+experience*, including newcomers submitting a proposal to give their
+first talk!
+
+* Important dates
+
+| CFP opens | August 17, 2020 |
+| CFP closes | September 30, 2020 |
+| Speaker notifications | October 24, 2020 |
+| Schedule published | November 7, 2020 |
+| EmacsConf 2020! | November 28 and 29, 2020 |
+
+Please note that although we will try our best to stick to the above
+dates in the coming months, given the current state of the world, we
+may have to move things around a bit in case of unforeseen events.
+Thank you for bearing with us as we all navigate these trying times.
+
+* Talk formats
+
+The following are the main formats for EmacsConf 2020 talks:
+
+- *10 minutes* (Lightning talk): Quickly present a cool project,
+ concept, or trick in 10 minutes or less!
+
+- *20 minutes* (Standard talk): Introduce the audience to a new Emacs
+ mode, concept, or just talk about something not necessarily shiny
+ and new but that you find really neat nonetheless.
+
+- *50 minutes* (Extended talk): Take your time going more in depth,
+ and/or do a demo! Extended talks are a great way of really
+ educating the audience about something you enjoy.
+
+Q&A time is *included* in the Standard and Extended time slots; please
+time your presentation accordingly. If you would like to take
+questions live, we recommend aiming for a 15-minute presentation for
+the Standard time slot, and for 40-45 minutes for the Extended time
+slot. However, as the speaker, the exact allocation of your time is
+up to you, so long as it does not exceed the allocated time slot.
+
+Other session formats such as tutorials, workshops, and hangouts are
+welcome as well, especially considering all that is going on around
+the world, in case you would find those other formats preferable to a
+traditional talk format. If you are interested in these or other
+session types, please get in touch with us publicly or privately; we
+will be happy to work something out with you.
+
+Keynote speaker(s) for EmacsConf 2020 will be introduced in a future
+announcement.
+
+* Topic ideas
+
+Not sure what to talk about? You might find some neat ideas on the
+[[https://emacsconf.org/2020/ideas/][ideas]] page (feel free to add yours there too)! If you're still not
+sure, come by our IRC channel =#emacsconf= on =chat.freenode.net= and
+say hi. You can join the chat using [[ircs://chat.freenode.net:6697/emacsconf][your favourite IRC client]], or by
+pointing your web browser to [[https://chat.emacsconf.org][chat.emacsconf.org]] which runs our
+self-hosted instance of [[https://thelounge.chat][The Lounge]] free software web IRC client.
+
+A great way to get started with writing a proposal is to start by
+exploring the programs from previous years: [[https://emacsconf.org/2019/schedule/][2019]], [[https://emacsconf.org/2015/schedule/][2015]], [[https://emacsconf.org/2013/#program][2013]].
+
+* Submission
+
+Once you're ready to submit your proposal, the [[https://emacsconf.org/2020/submit/][submit]] page has the
+instructions on how to submit your talk.
+
+We are committed to increasing the participation of speakers belonging
+to groups traditionally underrepresented at free software conferences,
+including women and people of colour. If you're comfortable sharing
+demographic information, please include them in your submission email,
+but your proposal will not be judged negatively if you leave them out.
+
+* Getting involved
+
+If you would like to get involved with the various aspects of
+organizing the conference such as planning the sessions or helping
+with the infrastructure, come say hi to us at =#emacsconf= on
+=chat.freenode.net=.
+
+Don't forget to subscribe to our mailing list, [[https://lists.gnu.org/mailman/listinfo/emacsconf-discuss][emacsconf-discuss]], for
+discussion and announcements about the EmacsConf conference.
+
+We look forward to your ideas and submissions!
+
+
+* COMMENT How to export this file
+
+As of the time of writing this document (Org mode version 9.3.7), the
+Org links library (=ol.el=) does not yet recognize =ircs= link types,
+and will throw an error if you try to export a file containing them,
+such as 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