Propose a talk or poster
Do you have a great idea or tool for the Jupyter community you would like to share? Do you have an interesting application where you've used Jupyter heavily and have developed workflows for using Jupyter that are broadly applicable? What lessons do you have for others using or deploying Jupyter? What do you wish you would have known when starting to use Jupyter or interacting in the Jupyter community? What has been the slowest or most frustrating thing you've had to learn about using Jupyter that you could share with others to make their experience better? Propose a talk or poster at the JupyterCon 2020!
Talks will be held on August 12-13, 2020 at the Berlin Conference Center in Berlin, Germany.
Talks at JupyterCon 2020
JupyterCon talks are 30 minutes long (plan for 25 minutes of presentation and 5 minutes of questions). Talks are organized into the following tracks:
Enterprise Jupyter Infrastructure
Talks that address deploying Jupyter and JupyterHub at scale in industry, government, high-performance computing, science, education, and other settings. Topics include DevOps, scaling services, security concerns, regulation compliance, and more.
Jupyter in Education
Talks that address how to teach and learn using Jupyter in a variety of settings.
Jupyter in scientific research
Talks that address how Jupyter is used in specific scientific research fields, such as climate change, physics, astronomy, meteorology, and more.
Data science applications
Talks that address how Jupyter is used by data science practitioners in industry, government, and elsewhere.
Jupyter community: tools and practices
Talks that address the community tooling and best practices in the Jupyter ecosystem. Community tools include frontends, kernels, extensions, and other tools in the Jupyter ecosystem. Community practices include how Jupyter is used in a workflow and how the Jupyter community itself works.
Posters at JupyterCon 2020
If your work is in progress, this is the place to share and get feedback. More suited for topics relevant to a narrow subset of the Jupyter community, poster presentations encourage one-on-one discussions between presenters and attendees that continue far beyond conference halls.
Posters is a forum for ideas to be presented in a concise, visually appealing way. Anyone is welcome to submit to the Posters program: researchers, practitioners, enthusiasts, and students. The strongest posters focus on clear communication and consideration of all audiences. Posters should be A0 size or at most 36 inches by 48 inches.
Guidelines for proposing a talk or poster
To propose a talk, you will first need to create a speaker profile. This includes information such as your name (as you would like it to appear in the conference program), and the following optional information, which will be published as a part of the conference program if your talk is accepted:
- a short biography telling the audience a little about you
- a photo
- a GitHub and/or Twitter handles to connect with you
The primary presenter should submit the proposal, and afterwards the proposal can be edited to add other authors.
A talk or poster proposal must include the following information that will be listed publicly in the conference program for accepted talks or posters.
- Title: Give your talk a title that accurately describes its content and focus to the potential attendees.
- Audience: Describe what level of programming/coding and other topic-specific knowledge, experience or expertise your talk 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 talk, as well as what audience may benefit from it. Brief summary: Submit a short paragraph describing the topic and key takeaways for attendees. The description will be included in the conference program announcements, should it be selected.
- A detailed outline: This is a self-contained statement that summarises the objective of the talk or poster, its outline, central thesis, and key takeaways. After reading the description, the audience should have an idea of the overall presentation and know what to expect. The description should also make clear what background knowledge is expected from the attendees. Include links to relevant source code, articles, videos, or other information that add context to your proposal.
- Your affiliation: for the purposes of this talk or poster.
Talk and poster proposal submission FAQs
What can I do to increase the likelihood of my talk/poster being accepted?
Here are some common pitfalls that could lead to the proposal being rejected:
- Submit early. Submissions can be modified up until the submission deadline.
- Ensure your talk or poster will appeal to a wider swatch of the Jupyter community. If your talk topic addresses a narrow segment of issues, users, or applications, consider shifting focus or highlighting best practices and themes that apply to a more general audience. People from many fields and backgrounds attend JupyterCon, which can lead to rich discussions among attendees that would not normally have a chance to interact with each other. What lessons have you learned that can benefit others in the Jupyter community that may not be from your specific field or application?
- Take a look at the JupyterCon 2017 and JupyterCon 2018 conference schedules for previously accepted talks.
- Clearly identify who your target audience is, what background is required for attendees to benefit from your presentation, and what the key takeaways are.
- Get feedback, especially from those in your target audience.
- There is a limited amount of financial aid to attend the conference. The financial aid application deadlines coincide with the call for proposals deadlines, so if you apply for financial aid to attend, you should know the results before you will need to confirm acceptance.
What should I avoid in my talk proposal?
Here are some common pitfalls that could lead to the proposal being rejected:
- Overly long proposal Keep it simple, clear and focused. Good proposals provide the most important information within the brief summary.
- Future work While talking about future work is interesting and could be mentioned in your talk, the core content of the talk should already be shaped, and you should be able to describe it in your proposal.
- Sales pitches We are a community of open source developers and users of open source scientific computing tools. You can reference your closed-source product or platform, but the audience will find the talk more interesting if they can try your techniques within the Jupyter ecosystem. Your problem definition, proposed techniques, broad issues you solved, and business domain might be interesting, but sales pitches and "how to use our product" talks are typically rejected.
- Repeated Talk We have a strong preference for new material and fresh faces, and as such, if your talk is already available online it is unlikely to be accepted for the conference.
Talks and posters will each be reviewed by several community reviewers in open reviews (i.e. identities of the submitters and reviewers are known to each other). The proposals and reviews will be submitted to the co-chairs of each track, who then will make a decision on which talks and posters should be accepted in the JupyterCon 2020 program. Lastly, the JupyterCon 2020 Organizing Committee will review the selected proposals for the final approval. All the submitters will be notified of the outcome. Those whose talks and posters have been accepted will be invited to confirm their participation. The Program Committee will prepare a schedule of the accepted talks.
Reviewers play an essential role in creating great JupyterCon programming. Sign up to be a reviewer here.