Jupyter Community Workshops 2025-2026

[jtpio]

Problem

The call for proposals for Jupyter Community Workshops is still open through Sunday, September 14 2025: https://events.linuxfoundation.org/jupyter-workshops

And there are plenty of topics within Jupyter Frontends that could apply.

Quoting @jasongrout (#Announcements > Community workshops @ 💬):

We had a short discussion in the Jupyter Frontends weekly call, and had a few ideas people thought would make great workshops that those present aren't able to organize. If someone is looking for ideas to organize a workshop around, here are some:

• Build tools, isolating them so they are more usable by other packages, extensions, etc.
• Accessibility workshop: work on a list of accessibility issues. Get some expert users in the room.
• Building extensions: a workshop around developing extensions
• Documentation workshop: bringing in copy writers and UX folks who are comfortable writing and editing docs

Proposed Solution

Draft one or several proposals for a workshop.

If anyone would like to start something or suggest other ideas, please feel free!

Additional context

The deadline has been pushed to Sunday, September 14, 2025, Anywhere On Earth.

cc @jupyterlab/jupyterlab-council for awareness as not everyone may be following the discussions on Zulip.

[jtpio]

Build tools, isolating them so they are more usable by other packages, extensions, etc.

This one could be about:

• Improving the contributor experience when working on JupyterLab or Jupyter Notebook
• This can take the form of using a more performant bundler such as rspack
  • Still keep compatibility with the federated extension of course (which is the case with Rspack)
  • For example resuming or rebooting Switch from webpack to rspack for bundling jupyterlab#16005
  • This would help make dev builds faster and decrease the memory usage (webpack can make a machine with 16GB choke easily)
• Extract build tools to https://github.com/jupyterlab/jupyter-builder
  • Improve tooling for extension authors
  • Make it easier to build lab-based applications (or JupyterLab remixes)
• Drop managing source extensions with jupyter labextension? jupyterlab#11336
• Look into modernizing and cleaning up some other parts of the code base, if possible