diff options
Diffstat (limited to '2022')
| -rw-r--r-- | 2022/cfp.md | 4 | ||||
| -rw-r--r-- | 2022/cfp.org | 4 | ||||
| -rw-r--r-- | 2022/planning.md | 27 | ||||
| -rw-r--r-- | 2022/sidebar.md | 12 | ||||
| -rw-r--r-- | 2022/submit.md | 107 |
5 files changed, 150 insertions, 4 deletions
diff --git a/2022/cfp.md b/2022/cfp.md index 403291e4..95abd3cf 100644 --- a/2022/cfp.md +++ b/2022/cfp.md @@ -26,7 +26,7 @@ your workflow might inspire someone to get into Emacs or go deeper? A great way to get started with writing a proposal is to start by exploring the programs from previous years: [2021](https://emacsconf.org/2021/schedule/), [2020](https://emacsconf.org/2020/schedule/), [2019](https://emacsconf.org/2019/schedule/), [2015](https://emacsconf.org/2015/schedule/), -[2013](https://emacsconf.org/2013/#program). You might also find some neat ideas on the [ideas](https://emacsconf.org/2022/ideas/) page. Feel +[2013](https://emacsconf.org/2013/#program). You might also find some neat ideas on the [ideas](https://emacsconf.org/2022/ideas/) page. Feel free to add yours there too! If you're still not sure, come by our IRC channel `#emacsconf` on `irc.libera.chat` and say hi. You can join the chat using [your favourite IRC client](ircs://irc.libera.chat:6697/emacsconf), or by visiting @@ -62,7 +62,7 @@ availability, it might be two half-days. <tbody> <tr> <td class="org-left">CFP opens</td> -<td class="org-left">July 11, 2022</td> +<td class="org-left">July 13, 2022</td> </tr> diff --git a/2022/cfp.org b/2022/cfp.org index 76c17ed4..64ef7769 100644 --- a/2022/cfp.org +++ b/2022/cfp.org @@ -62,7 +62,7 @@ your workflow might inspire someone to get into Emacs or go deeper? A great way to get started with writing a proposal is to start by exploring the programs from previous years: [[https://emacsconf.org/2021/schedule/][2021]], [[https://emacsconf.org/2020/schedule/][2020]], [[https://emacsconf.org/2019/schedule/][2019]], [[https://emacsconf.org/2015/schedule/][2015]], -[[https://emacsconf.org/2013/#program][2013]]. You might also find some neat ideas on the [[https://emacsconf.org/2022/ideas/][ideas]] page. Feel +[[https://emacsconf.org/2013/#program][2013]]. You might also find some neat ideas on the [[https://emacsconf.org/2022/ideas/][ideas]] page. Feel free to add yours there too! If you're still not sure, come by our IRC channel =#emacsconf= on =irc.libera.chat= and say hi. You can join the chat using [[ircs://irc.libera.chat:6697/emacsconf][your favourite IRC client]], or by visiting @@ -86,7 +86,7 @@ For EmacsConf 2022, we are planning for 9am to 5pm Toronto/EST (2pm-10pm UTC) on December 3 and 4. Depending on people's availability, it might be two half-days. -| CFP opens | July 11, 2022 | +| CFP opens | July 13, 2022 | | CFP closes | August 31, 2022 | | Speaker notifications | September 30, 2022 | | Schedule published | October 31, 2022 | diff --git a/2022/planning.md b/2022/planning.md new file mode 100644 index 00000000..b7952f1a --- /dev/null +++ b/2022/planning.md @@ -0,0 +1,27 @@ +[[!meta title="Planning"]] +[[!meta copyright="Copyright © 2020, 2021, 2022 Amin Bandali"]] + +Most of the EmacsConf organizers and other volunteers hang out in the +`#emacsconf` IRC channel on `irc.libera.chat`. If you would like to +get involved, come by our `#emacsconf` channel and say hi! + +Besides IRC, the [emacsconf-org][emacsconf-org] public mailing list is +the main medium of communication for the EmacsConf organizers. + +The organizers may use this page as a collection of various notes, +ideas, and plans for organizing the conference, and may add excerpts +from the channel logs for `#emacsconf` and `#emacsconf-org` to this +page. + +You might find it useful to also look at the plans and notes from +previous years: + +- 2021: [[planning|2021/planning]], + [[organizers' notebook|2021/organizers-notebook]] +- 2020: [[planning|2020/planning]], + [[organizers' notebook|2020/organizers-notebook]] +- 2019: [[planning|2019/planning]], + [[organizers' notebook|2019/organizers-notebook]] + + +[emacsconf-org]: https://lists.gnu.org/mailman/listinfo/emacsconf-org diff --git a/2022/sidebar.md b/2022/sidebar.md new file mode 100644 index 00000000..224db86a --- /dev/null +++ b/2022/sidebar.md @@ -0,0 +1,12 @@ +<p>Welcome to...</p> +<p class="center">[[!img /i/emacsconf-logo1-256.png alt="EmacsConf logo" size="72x" link=2022]]</p> +<p class="center"><strong>[[EmacsConf 2022|2022]]</strong></p> + +--- + +* [[**Call for Proposals**|cfp]] +* [[Ideas]] +* [[Submit]] +* [[Planning]] +* [[Guidelines for Conduct|conduct]] +* [[Contact information|contact]] diff --git a/2022/submit.md b/2022/submit.md new file mode 100644 index 00000000..5c850c31 --- /dev/null +++ b/2022/submit.md @@ -0,0 +1,107 @@ +[[!meta title="Submit"]] +[[!meta copyright="Copyright © 2019, 2020 Amin Bandali<br /> +Copyright 2021 Amin Bandali, Sacha Chua, Leo Vivier<br /> +Copyright 2022 Amin Bandali"]] + +When you're ready to submit your proposal, send your submission via +email to <emacsconf-submit@gnu.org> by **August 31**, including at +minimum these essential information: + +- Your [preferred] name and its pronunciation, and optionally your + preferred pronouns; + +- your availability during the conference days (December 3 and 4) and + how you'd like to handle questions (live web conference, IRC, pad, + wiki, questions after the event); + +- emergency contact information (such as phone number) in case the + organizers need to contact you at the last minute before your talk, + or reach you during your talk (for example due to technical + difficulties); + +- the title of your talk/session; + +- an abstract of your talk/session (500 words or less); + +- brief descriptions/outlines for [[all talk formats|cfp#formats]] up + to your maximum planned length: + - 5-10 minutes: + - 20 minutes: + - 40 minutes: + +- your agreement with the speaker release for EmacsConf (see below). + + +Please use the following template for your submission email, +filling it out with information about you and your proposal: + +``` +Speaker name (and optional pronunciation) and preferred pronouns: + + +Speaker availability and preferred Q&A approach: + + +Speaker emergency contact information: + + +Talk title: + + +Talk abstract: + + + + + + + + +- 5-10 minutes: (brief description/outline) +- 20 minutes: (brief description/outline) +- 40 minutes: (brief description/outline) + +Speaker release: + + By submitting this proposal, I agree that my presentation at + EmacsConf 2022 is subject to the following terms and conditions: + + The EmacsConf organizers may capture audio and video (a "Recording") + of my presentation and any associated materials, which may include + slides, notes, transcripts, and prerecording(s) of my presentation + that I provide to the EmacsConf organizers. + + I authorize the EmacsConf organizers to distribute, reproduce, + publicly display, and prepare derivative works of the Recording and + any derivative works of the Recording (the "Licensed Materials") + under the terms of the Creative Commons Attribution-ShareAlike 4.0 + International (CC BY-SA 4.0) license. + + I grant to the EmacsConf organizers permission to use my name, + likeness, and biographic information in association with their use + of the Licensed Materials under the above license. + + I represent that I have the authority to grant the above license to + the EmacsConf organizers. If my presentation incorporates any + material owned by third parties, I represent that the material is + sublicensable to the EmacsConf organizers or that my use of them is + fair use. +``` + + +All kinds of people use Emacs for all kinds of things. We would love +it if EmacsConf 2022 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 expert enough to +share their thoughts. If you let them know that you value their +knowledge and maybe even suggest something that you think others would +like to hear more about, they may realize that they have something +worth sharing and that we would love to hear from them. + +The submissions will be reviewed by a selection committee. If you +would like to help review submissions as part of this committee, +please [[let us know|contact]]. We look forward to hearing from you +(and the people you want to nudge to speak)! |