Brought to you by NumFOCUS Foundation and O’Reilly Media Inc.
The official Jupyter Conference
August 22-23, 2017: Training
August 23-25, 2017: Tutorials & Conference
New York, NY

Call for speakers

Call closes 11:59pm 03/07/2017 EST.

Submit a proposal

Do you have a great Jupyter idea to share?

With millions of users and over a million notebooks on GitHub, the open-source Project Jupyter is having a deep impact in almost all aspects of interactive computing. Jupyter offers a rich architecture whose elements can be used and recomposed for a wide range of problems.

As it grows support for more languages, JupyterLab provides modular support for novel use cases, and projects like PyCharm and nteract build new interfaces atop the Jupyter protocols and formats, Jupyter continues to grow into a rich and diverse technical ecosystem.

That’s why Project Jupyter, the NumFOCUS Foundation, and O’Reilly Media have come together to launch JupyterCon.

We’re looking for a diverse range of talks and speakers for the 2017 program, and in particular invite proposals from members of underrepresented groups in tech and people new to public speaking. Topics include, but are not limited to:

  • The core Jupyter Architecture (notebooks, message specification, kernels, etc.)
  • Any of the Jupyter subprojects (Notebook, JupyterHub, JupyterLab, nbconvert, IPython, etc.)
  • Usage and application of Jupyter software in any domains such as:
    • Education
    • Any area of scientific research (zoology, chemistry, astronomy, etc.)
    • Machine learning
    • Data Journalism
    • Data visualization
    • Economic, finance and econometric forecasting
    • Open Data in society and government
    • Library science
    • Commercial products and services
  • JupyterHub and multi-user or large-scale deployments (universities, companies, HPC)
  • Reproducible research and open science
  • Jupyter development process and community
  • Documentation with and for Jupyter
  • Jupyter kernels: uses of Jupyter across different programming languages
  • Extensions and customization of Jupyter software (Notebook, JupyterHub)

Required information

You’ll be asked to include the following information for your proposal. To help us minimize unwanted bias in the review process, please do not include your name, affiliation, or any other identifying information in the title, description, or abstract of your proposal.

Proposals will be considered for the following types of presentations:

  • 40-minute session (If you find this to be a long time, you may consider enlisting a co-presenter; joint talks can be fun, high-energy, and very engaging). This time includes a Q&A allocation, so you should plan for approximately 30 minutes of actual presentation.
  • 3-hour tutorials

You will need to provide:

  • Proposed title and abstract
  • Description of the presentation
  • Indicate whether you are submitting a 40-minute session or a 3-hour tutorial
  • Suggested main topic and application area (i.e. science, education, industry…)
  • Audience information:
    • Who is the presentation is for?
    • What will they be able to take away?
    • What prerequisite knowledge do they need?
  • For tutorial proposals: hardware installation, materials, and/or downloads attendees will need in advance
  • Speaker(s): biography and hi-res headshot (minimum 1400 pixels wide; required)
  • A video of the speaker (not required)
  • Reimbursement needs for travel or other conference-related expenses (if you are self-employed, for example)

Tips for submitting a successful proposal

Help us understand why your presentation is the right one for JupyterCon.

  • Be clear and specific about your topic (this will help the review process).
  • Be authentic. Inspire your peers with original ideas in real-world scenarios, relevant examples, and knowledge transfer.
  • Give your proposal a simple and straightforward title.
  • Include as much detail about the presentation as possible.
  • If you are proposing a panel, tell us who else would be on it.
  • Keep proposals free of marketing and sales pitches.
  • If you are not the speaker, provide the contact information of the person you’re suggesting. We tend to ignore proposals submitted by PR agencies and require that we can reach the suggested participant directly. Improve the proposal’s chances of being accepted by working closely with the presenter(s) to write a jargon-free proposal that contains clear value for attendees.
  • Keep your audience in mind. JupyterCon attendees will come from a wide range of industries, academic fields, and experiences. Make sure your talk can be understood by a general audience.
  • Limit the scope: in 40 minutes, you won’t be able to cover Everything about Framework X. Instead, pick a useful aspect, or a particular technique, or walk through a simple program.
  • Explain why people will want to attend and what they’ll take away from it
  • Does your presentation have the participation of a woman, person of color, or member of another group often underrepresented at tech conferences? Diversity in the conference program and inclusion are factors we seriously consider when reviewing proposals as we seek to broaden our speaker roster.
  • All presentations and supporting materials must be respectful, inclusive, and adhere to the JupyterCon Code of Conduct.

We want to provide you with support on your idea at all stages of the process. Whether you’d like early advice on whether your topic/idea is a good fit for the conference, or feedback on your abstract before you make your submission, our program committee is available to help. We are here to help you succeed and create the best content for the conference: contact us at speakers@jupyter.org with any questions you may have.

Other resources to help write your proposals:

Important dates:

  • Call for Participation opened: January 23
  • Call for Participation closes: March 7
  • All proposers notified: By April 2017
  • Registration opens: April 2017

Code of Conduct

All participants, including speakers, must follow our JupyterCon Code of Conduct, the core of which is this: JupyterCon should be a safe and productive environment for everyone. Read more »

Create a proposal