Tutorials

Dates to remember

Authors submit proposals by Monday, July 20, 2020 Wednesday, July 22, 2020 (Anywhere on Earth)
Authors receive proposal accept/decline decision August 10-12, 2020
Authors upload talks by September 11, 2020 September 18, 2020

Guidelines for proposal submission

As with the talks, we are looking for tutorials that will advance the Jupyter ecosystem, foster this community, and shape its future. All the content will be streamed online and should cover 3 hours with a mixture of video presentation, hands-on exercises and knowledge checks/ self-assessment (e.g. using nbgrader). Conference attendees will be able to access the tutorial contents on-demand. In addition, we will set a 1 hour office hour over the main conference days (day and time to be scheduled around tutorial leader availability).

Please note: Each presenter is limited to giving two tutorials only, either as the main lead or a co-lead/assistant. Tutorial presenters will receive a free conference tutorial week pass. Tutorial presenters will also receive a speaker kit, including a quality microphone, halo light, branded t-shirt, and other swag.

Proposing a tutorial

Your proposal should include the following:

1. Title: Give your tutorial a title that accurately describes its content and focus to the potential participants.
2. Submitting author(s): Provide the names of the main presenters or facilitators.
3. Brief summary: Submit a high-level description of the tutorial, limited to ~400 characters. The description will be included in the conference program announcements, should it be selected
4. Audience: Describe what level of programming/coding and other topic-specific knowledge, experience or expertise your tutorial is aiming for. Will the attendees need multiple skills or proficiency in tools other than Jupyter notebooks?
   ‘Advanced’, ‘Intermediate’, and ‘Beginner’ may mean different things to different people. Feel free to include any additional details regarding prerequisites for your tutorial, as well as what audience may benefit from it.
5. Format: List what instructional tools you will use in the proposed tutorial. Describe what instructional methods you intend to employ to best facilitate active learning for the entire duration of the tutorial.
6. Outline: List the topics and activities you will guide the participants through during your 3-hour tutorial. Please err on the side of ‘too much detail’ rather than ‘not enough’. Include timing notes, estimating what portion of your tutorial you’ll dedicate to each major topic (usually there are 2-5 of those). The outline will not be shared with conference attendees but will provide the reviewers with greater insight on your tutorial content.
7. Past experience: Please summarize your teaching or public speaking experience, your experience with the subject of the tutorial, and share anything else that would help us understand and gauge your abilities as an instructor. If available, include a link to a video and slides from the tutorial itself (if it’s been presented before), or your other professional presentations. This section is for the reviewers’ benefit only and will not be published on the JupyterCon website. We also would like to know if you have past experience creating recorded or video content. This will help us to better support tutorial leads and plan our speaker packs accordingly.
8. Requests: Let us know if you have specific needs or special requests. We are prepared to accommodate requests that involve accessibility or restrictions on when your office hour can be scheduled.
9. Accessibility: We will accommodate disability-related needs wherever possible. The merit of your tutorial will be judged independently from any request made here. This section will not be visible to attendees.

Tutorial proposal submission FAQs

1. What can I do to increase the likelihood of my tutorial being accepted?

   Things we like to see included:

   • A clear description of the target audience. This helps our attendees know if the tutorial is right for their level of knowledge and skills, and allows us to assess how well the presenter knows the audience he is targeting with his material.
   • Reasonable learning goals. These should demonstrate what the attendees will learn and be able to do after attending the tutorial.
   • Readability counts. We like outlines that are easy to understand. Markdown is a great tool for giving your submission clear formatting, allowing us to distinguish, at first glance, between topics and sub-topics. (If you are new to Markdown, this tutorial is great!) After submitting your proposal, please make sure your submission is rendered properly.
   • Material that clearly should be presented as a tutorial (rather than a talk). Tutorial spaces are limited, and if the material can be presented more concisely, and to a bigger audience by turning it into a talk, we prefer that.
   • Thoughtfulness regarding time. We like to see that submitters have considered how much is reasonable to cover in a given time period and how the material might change based on the audience. To demonstrate this, you may choose to include what topics could run over as well a time for hands-on exercises and self-assesment.

2. What should I avoid in my tutorial proposal?

   Your tutorial is less likely to be accepted if:

   • It requires using commercial or proprietary tools.
   • It criticizes other programming languages, platforms, and paradigms.
   We will not accept any tutorial that violates the Code of Conduct.

3. What should my timing notes look like? How precise do I need to be?

   We request you provide a rough estimate of how much time (or percentage of the tutorial) you’ll dedicate to each major topic (not subtopics). We recommend these timings to be no more precise than 30-minute increments. Even though some leeway is allowed, please don’t give your timings down to the minute!
   Alternatively, you are welcome to provide the portion of the time you expect to spend on each major topic. Please indicate whether you are using percentages or minutes.

4. Why an outline with timings?

   It will help the reviewers to assess what topics your tutorial will focus most, as well as the level of knowledge and experience it suits best. For example, a tutorial that spends 2.5 hours on basic concepts and ends with a brief tour of advanced features is more appropriate for a beginner audience than one with the opposite structure.
   Furthermore, it will help the first-time tutorial presenters to better prepare and assess beforehand if their planned instructional material can be realistically presented in the allotted time.
   It’s fine if these timings slightly change when you give the tutorial.

5. Who should apply?

   While we don’t speak in absolutes, we’d like to see that presenters have experience in instruction and public speaking. This will give us a certain level of assurance that you’re prepared to deliver on what you are proposing.