Call for speakers
11:59pm 03/06/2018 EST.
Do you have a great Jupyter related idea or work 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 including scientific computing and data science.
The core Jupyter open source projects are experiencing a phase of significant innovation and development. Our next-generation JupyterLab modular interface is now available, JupyterHub supports increasingly complex infrastructure deployments with thousands of users, the Binder project supports one-click deployment of executable environments for reproducibility and collaboration, Jupyter widgets support rich interactive interfaces, and more.
Around the core project, a rich ecosystem continues to grow atop of the Jupyter protocols and standards. From open source clients like nteract to support in tools as varied as Google’s Colaboratory, Microsoft’s VSCode and JetBrains PyCharm IDEs or the CoCalc platform for mathematical computation and education, developers and companies in multiple areas have embraced our open standards as a backbone that supports innovation with interoperability.
That’s why Project Jupyter, the NumFOCUS Foundation, and O’Reilly Media have come together to host JupyterCon. For the first iteration of JupyterCon in 2017 we attracted over 700 attendees, including 23 scholarship recipients, across 4 days with access to 5 parallel session tracks totaling 11 keynotes, 55 talks, 8 tutorials, and 2 training courses. The conference also featured 33 poster sessions as a starting point for further discussion and was a huge success. Videos of the event have been made available on Safari and YouTube.
We’re looking for a diverse range of talks for the 2018 program, including—but not limited to—the topics below. The deadline for submissions is 11:59 pm EST on March 6.
- 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:
- 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
- Citizen science
- JupyterHub and multi-user or large-scale deployments (universities, companies, HPC)
- Reproducible research and open science
- Jupyter development process and community
- Organizational and enterprise adoptions of Jupyter
- Documentation with and for Jupyter
- Jupyter kernels: uses of Jupyter across different programming languages
- Extensions and customization of Jupyter software (Notebook, JupyterHub, JupyterLab, etc.)
- JupyterCon Business Summit: high-level presentations on the most promising and important developments in Jupyter for executives and decision-makers.
- Surprise us! If you have a great idea for a talk on a topic that is part of the Jupyter ecosystem and community but is not listed above, please submit it
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 firstname.lastname@example.org with any questions you may have.
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, or any other personally identifying information in the title, description, or abstract of your proposal. You can provide information about any company, products or open-source projects related to the content of your work.
- 40-minute session (if this seems like a long time, consider enlisting a co-presenter; joint talks can be very engaging); allow about 30 minutes for your presentation and 10 minutes for Q&A
- 3-hour tutorials
You will need to provide:
- Proposed title and abstract
- Description of the presentation
- 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). Check out our guidelines for capturing a great portrait.
- Prerequisite knowledge and/or requirements needed by attendees
- A video of the speaker (recommended but not required)
- Reimbursement needs for travel or other conference-related expenses (if you are self-employed, for example).
Note for speakers coming from abroad: If your proposal is accepted and you are traveling internationally, we can provide a formal invitation letter upon request that you can use to apply for a visa, should you need one. Please allow sufficient time for that process, as the conference organizers can not guarantee that a visa will be issued to you in time.
Tips for submitting a successful proposal
Help us understand why your presentation is the right one for JupyterCon. All speakers must adhere to our Code of Conduct. Please be sure that your presentation, including all supporting materials and informal commentary, is welcoming and respectful to all participants, regardless of race, gender, gender identity and expression, age, sexual orientation, disability, physical appearance, national origin, ethnicity, religion, or political affiliation.
- 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.
Again, 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 email@example.com with any questions you may have.
Other resources to help write your proposals
- Call for Participation closes: March 6, 2018
- All proposers notified: By April 2018
- Registration opens: April 2018
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 »
Submit a proposal