jupyter

Community Guides

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.

Monthly Meetings

This following calendar shows the various meetings and events from Jupyter sub-projects:

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.

All-Jupyter Community Calls happen on the last Tuesday of every month, and are focused around demonstrations and sharing information across all of the Jupyter projects.

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.

Jupyter communications

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.

Governance

Code of conduct

Information can be found in the Jupyter Governance repo on GitHub.

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.

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 Jupyter-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 :-)