The Future of Jupyter: Building the... David Q., Kirstie W., Zach S., Min R., Jason G. & Chris H.

The Future of Jupyter: Building the Next Core, Together - David Qiu, AWS, Kirstie Whitaker, Berkeley Institute for Data Science, Zach Sailer, Apple, Min RK, Jason Grout, Build Open & Chris Holdgraf, 2i2c Project Jupyter's future is being built in the open, but much of it lives outside the default install. This panel brings maintainers from multiple organizations to align on what's next. We'll debate the foundational capabilities that would benefit everyone: disconnection-resilient execution (a reload never loses a running cell), robust real-time collaboration, native diffing, performance for large notebooks, and simpler, better-documented server APIs developers can build on without reverse-engineering. We'll look at the enterprise features (role-based access control, audit logging, SSO) that would bring organizations and their sponsorship back upstream instead of forking. Then the hard part: what does it take for a major feature to become official JupyterLab, and how do we streamline that path? We'll name the challenges holding us back; fragmented development, unclear ownership, duplicated effort and, time permitting, showcase community work that deserves a wider home: jupyterlab-git, nbdime, jupyter-collaboration, jupyter-ai, xtralab. We won't settle everything here; the aim is to spark discussions that continue afterward and eventually converge on a shared roadmap.