Jupyter Community Committee Meeting

Community Committee Meeting (2026-08-20)¶

Please add new agenda items under the New agenda items heading!

• Previous meetings

• Jupyter Community Committee handy links:

  • GitHub repo

Attendees¶

• Rosio

• Serena

• April

• Jason

• Matt

Action items¶

• Jason: Disable AI meeting sumarries

• Jason: Respond to Sylvain with concerns

• Matt: Reach out to Martha about EC endorsement of CFP

Standing items¶

• Active initiatives

  • ...

• Upcoming initiatives

  • ...

Agenda & notes¶

• CFP!

  • Do we feel like it’s done?

    • Matt, April, Rosio: Yes

    • Serena: Will do a double-check, but feeling good right now :)

  • Still waiting for response from EC for endorsement

• Upcoming events:

  • Pytorch

  • OSS EU w/ Jupyter mini-summit

    • Serena chairing!

    • In welcome presentation, share about Jupyter community in general. Will send slides for our opinions!

  • Compute! (Paris)

    • Serena presenting on role as community manager

    • Sylvain interested in reviving Jupyter developers meeting (see below)

• Email by Sylvain:

  Dear Jupyter Community Working Group, Jupyter Media Strategy Group, (cc Fernando, Darian)

  I hope you are all well.

  I would like to propose reviving the Jupyter Dev meetings that brought our community together in the 2010s. With many maintainers not having met in person in years - or ever - this feels like an important opportunity to reconnect and collaborate.

  Proposal: November 27 in Paris I suggest holding the meeting on November 27, the day after Compute! Paris. This timing and location maximize participation:

  Strong European presence: Most of QuantStack’s 12 Jupyter Distinguished Contributors will already be at the conference. Quansight’s Mike Krassowski (England, JupyterLab maintainer) and Matthias Bussonnier (France, IPython maintainer) can join with minimal travel. Serena Bonaretti (Switzerland, JupyterHub/Book Community Manager) will be presenting. 2i2c has team members across Europe (e.g., Angus Holland and Giuliano Maciocci in England, Georgiana Dolocan in Romania). Yann Pellegrini (France, Jupyter Security) will be presenting. And Fernando Pérez (opening keynote speaker) has confirmed interest in staying.

  Built-in momentum: Compute! Paris features a “Planet Jupyter” track on November 26, with talks from Jeremy Tuloup (JupyterLab, JupyterLite), Yann Pellegrini (Jupyter security), Tim Paine (nbplay), and Afshin Darian (JupyterLab co-creator). Additional Jupyter-related sessions include a geojupyter case study and Serena’s community management report.

  Logistics and venue: The venue for the Compute! Sprints will be the Sorbonne Cluster for Artificial Intelligence (SCAI) in the center of Paris, which offers modern facilities with large open spaces and breakout rooms, ideal for sprints and structured discussions. Besides, the conference venue provides two additional rooms (with a capacity of 70 people each) for potential Jupyter BoF sessions.

  Funding: The Venue is already provided. We would encourage non-European maintainers to seek employer funding, with Jupyter Foundation support available as needed.

  Are you supportive of this proposal?

  • Jason: Is he asking for permission to call this an official Jupyter event?

    • Code of conduct, event insurance, etc. comes in to play if it is.

    • We can say this sounds great, and go ahead and market it, but we don’t know what it means (e.g. insurance) to approve a third-party event as an official Jupyter event.

  • For us:

    • Write down what it means for Jupyter to sanction a 3rd party event.

    • Ask EC to delegate authority to sanction 3rd party events?

      • Is this something we want to do?

        • Do we want “officialness” to be something that can only be blessed by the foundation?

        • Our role can be collaborating on making sure events are in line with community values and goals (CoC, trademark guidelines, ?). Perhaps also liaising with Foundation for insurance issues?

    • Branding things as official events vs community events? Things like JupyterCon vs community workshop. And clearly documenting the implications of this.

      • How does LF handle community events in other projects?

    • Puts us in a policing role?

      • We can say “yes that sounds like a great event, and we’re not funding it, and you need to use our CoC, and you need to use the Jupyter logo persuant to guidelines if you want to call it official”

    • Understand from LF what their needs are -- do we need their approval?

    • Where does this information live?

      • Jupyter.org and linked from Team Compass?