A year of Jupyter community calls

A framing for open source is that the software and code are kernels of community. The code, and its abstractions, unite developers and their patrons; a struggle for growing/evolving open communities is to make sure these groups remain connected. A lot of us showed up for the code, but hung around for the community. We'll continue this post talking about the monthly Jupyter community calls, and how they help all jovyans, Project Jupyter's pet name for their developers and users, stay connected.

Why community calls?

A lot of us showed up for the code, but hung around for the community.

Project Jupyter has a rich community calendar spanning different projects in the ecosystem. Although these events are open to all, the meetings can appear daunting and exclusive.

This year, Quansight Labs took on the responsibility of reviving an existing series of events: the Jupyter community calls. The original monthly series, starting in March 2019, gave the stage to those using Jupyter daily. These events started to created space for Jupyter's patrons to demonstrate how they use Jupyter as a computational tool.

Jupyter is a rapidly moving piece of technology, and staying up to date with the latest advances takes significant labor. The community calls ensure us a monthly check-in of the latest and greatest. Sometimes these events digress into Jupyter's rich folk history, or peer into future interactive computing technologies like real time collaboration or browser-based computing environments.

Having these events consistently encouraged folks to get their work in to share with others. These calls also gave some structure through an otherwise chaotic pandemic.

The last dozen events

We made sure to record these events for posterity, and you can check them out in the community call YouTube playlist, as written notes, or by following any of the links below:

November December

January February March April
May June July August
September October November

Some highlights from the past year

Each event had its own charm as the attendees varied. Below we highlight some interesting outcomes:

  • Jupyter underwent a major version change - 2.x to 3.x - during the past year. The monthly syncs were critical in keeping the community aware of what is coming and weather the storm together. More recently, we're seeing the fruits of the Jupyter 4.0 roadmap at our meetings each month.
  • We received updates from the JupyterHub and BinderHub communities, which support scaling Jupyter's abilities.
  • We saw the first browser based implementation of Jupyterlab called jupyterlite.
  • We explored several cool extensions such as ipydrawio, jupyter-lsp, internationalization, janki, jupyter-videochat, citations, jupyter-h5web
  • We saw the formation of a security-focused working group and governance updates.

More community calls

We'd love to see more events like this cater properly to Jupyter's global audience. If that's something you care about too, please contact us by opening an issue on our planning repository. We've treated these events as an open source project and have a lot of resources to get you started in the technical resources section.

We're all nostalgic for the conference hallway track as we stay safe in a pandemic. With the community calls, for one hour a month, we've been doing our best to simulate the hallway track and the communitas it can bring. We hope to see you and your notebooks at an up and coming event.

Technical resources

Information about the community calls for participants and hosts can be found in the Jupyter community call repository.

Join a call

Jupyter community calls are still happening! If you want to participate in one of these calls, whether as a presenter or audience member, up-to-date info for the next call can be found on the Jupyter community calendar.