Welcome to the Community Guides for Jupyter. These guides are intended to provide information about the Jupyter community such as background, events, and communication channels. As our community is highly dynamic, information may change, and we will do our best to keep it up to date.
Jupyter Community Meetings¶
The Jupyter community often meets (usually on-line) in order to discuss matters in the Jupyter community, share new ideas and discussions, and connect with one another. This often happens within specific sub-project (more information below), though there are also occasional community-wide meetings.
This following calendar shows the various meetings and events from Jupyter sub-projects:
All-Jupyter Community Calls generally happen on the last Tuesday of the month, and are focused around demonstrations and sharing information across all of the Jupyter projects.
Find information on this Discourse thread.
Watch previous calls on our YouTube channel.
Read the notes from previous calls.
In addition, you can find the notes from previous community meetings below.
- Community Call Notes
- Jupyter Community Call
- June 29, 2021
- May 2021
- April 2021
- March 2021
- February 2021
- January 2021
- December 2020
- November 2020
- September 2019
- August 2019
- June 2019
- May 2019
- April 2019
- March 2019
Jupyter Project meetings¶
The core developers of various Jupyter sub-projects have regular meetings to discuss and demo what they have been working on, discuss future plans, and bootstrap conversation. These meetings are public and you are welcome to join remotely.
Each team has their own processes around logistics and planning for the team meetings. The following pages should help you find the information for each.
JupyterHub meetings happen monthly. For a calendar of future team meetings, see the JupyterHub team compass repository.
JupyterLab meetings happen weekly. For more information about when these meetings happen, as well as notes from each meeting, see the JupyterLab README.
General meeting conversation and planning often happens in the dev-meeting-attendance Gitter channel. We recommend checking it periodically for new information about when meetings are happening.
As a general rule, most project-wide conversation happens in the Jupyter community forum. There are also many other kinds of communication that happens within the community. See below for links and other relevant information.
Community forum https://discourse.jupyter.org/
Mailing lists (Jupyter, Jupyter in Education) https://jupyter.org/community.html
Steering council: Information about the steering council and its members can be found on the Jupyter website.
Information about Jupyter’s governance process can be found on the Jupyter governance website.
Jupyter Enhancement Proposal (JEP) process: Details about the process can be found in the enhancement proposals website.
Running Jupyter Events¶
Members of the Jupyter community often get together to share what they’re working on, to work together, and to teach and learn from one another.
If you’re organizing an event with the Jupyter community (whether it’s as small as a JupyterDays meetup, or as large as JupyterCon) you should ensure that the event follows the values and goals of the Jupyter project - to be a place where everyone feels welcome and supported and that reflects the diversity of developers and users in the Jupyter community.
Shoot for having 25% of your participants come from under-represented groups. If you’re organizing a Jupyter event, here are some resources to help out.
Mozilla has a number of excellent resources on hosting open events. The Mozilla Open Events guide. This is an excellent resource for planning and running an open, inclusive event. In particular, this section on making events more inviting is a good way to make your event more welcoming, interesting, and accessible to the Jupyter community. Finally, the Diversity and Inclusion wiki includes conference calls related to this topic.
The NumFocus DISCOVER cookbook is another collection of resources for making your event more productive, diverse, and inclusive.
The National Center for Women & Information Technology has an excellent collection of resources for creating a diverse and inclusive environment. In particular, we recommend their Inclusive Environment Assessment Guide and 10 actionable ways to actually increase diversity.
The PyCascades community has several efforts in improving diversity and inclusion.
Ultimately, making events more inclusive is not rocket science and there is no magic bullet. It requires clear, focused dedication, planning ahead, and sustained resources and effort over time. However, we believe this effort is worth it!
What is a Jovyan?¶
You may see the word Jovyan used in Jupyter tools (such as the user ID in the Jupyter Docker stacks or referenced in conversations. But what is a Jovyan?
In astronomical terms, the word “Jovian” means “like Jupiter”. It describes several planets that share Jupiter-like properties.
Much like the planet Jupiter and our solar system, the Jupyter community is large, distributed, and nebulous. We like to use the word Jovyan to describe members of this community. Jovyans are fellow open enthusiasts that use, develop, promote, teach, learn, and otherwise enjoy tools in Jupyter’s orbit. They make up the Jupyter community. If you’re not sure whether you’re a Jovyan, you probably are :-)