Weekly Team Meetings: Jan–Dec 2026

[andrii-i]

Here is a record of the agenda/minutes for our weekly meeting. Everyone is welcome to join.

Let's avoid using this thread for discussion. If you'd like to discuss something in the minutes, open a separate issue and reference this thread.

Previous meeting notes thread:

• Weekly Team Meetings: Jul–Dec 2025 Weekly Team Meetings: Jul–Dec 2025 #279

Recordings

You can also watch the contributor meetings recordings on the Project Jupyter YouTube channel: https://www.youtube.com/@projectjupyter

[andrii-i]

Wednesday, January 7 '26

Name	Affiliation	GitHub
Mike Krassowski	OpenTeams	@krassowski
Afshin Darian	QuantStack	@afshin
Omar Jarjur	Google	@ojarjur
Jordan Boxer	Hudson River Trading	@jordanhboxer
Isabel Paredes	QuantStack	@IsabelParedes
Andrii Ieroshenko	AWS	@andrii-i
Jeremy Tuloup	QuantStack	@jtpio
Nicolas Brichet	QuantStack	@brichet

Mike:

• backporting Make system clipboard opt-in when performing copy/cut/paste of cells #18250 into 4.5.x
• GSoC

Omar:

• Thoughts/feedback on Support ProactorEventLoop on Windows jupyter-server/jupyter_server#1587 ?
  • Will send out a PR with the proposed change to run tests against and give a concrete place to anchor discussions.
  • Have to also consider why this same change had to be rolled back in ipykernel: ipykernel should use default WindowsProactorEventLoopPolicy rather than WindowsSelectorEventLoopPolicy for windows ipython/ipykernel#1468

Jordan:

• Thoughts/feedback on Fix cell duplication when YStore diverges from disk jupyter-server/jupyter_ydoc#376

Isabel:

• Introduced herself in chat and asked about accessibility issue priority and about issues relating to keyboard navigation.
• Considering: Accessibility - Keyboard Navigation using a Screen Reader jupyterlab#15303 and Accessibility Issues Needing Addressing for WCAG 2.1 compliance (As of Version 2.2.6) jupyterlab#9399
  • Mike:
    • maybe New plugin (token) for aria-live jupyterlab#16145
    • maybe reviewing some PRs from the https://github.com/jupyterlab/jupyterlab/pulls?q=is%3Aopen+is%3Apr+label%3Atag%3AAccessibility queue

[andrii-i]

Wednesday, January 14 '26

Name	Affiliation	GitHub
Mike Krassowski	OpenTeams	@krassowski
A. T. Darian	QuantStack	@afshin
Andrii Ieroshenko	AWS	@andrii-i
Ian Thomas	QuantStack	@ianthomas23
Jeremy Tuloup	QuantStack	@jtpio

Mike:

• JupyterLab 4.5.2 and 4.6.0a1 are out
• GSoC '26? Google Summer of Code 2026? jupyter/governance#322 (Google Summer of Code)
• shout out to Martin for reworking the update snapshots boilerplate
  • Implementationn PR: Add composite workflow action for checking user permissions prior to updating snapshots maintainer-tools#268
  • Example transition Update snapshots bot checkout and permission check jupyterlab-contrib/jupyterlab-favorites#43
• /review-ready command or code owners Improve PR Review Workflow in JupyterLab jupyterlab#18330?

Jeremy:

• AI rules: Add AI rules jupyterlab#18322

Darian:
- small EC update asking about roadmapping sessions / planning the different projects are planning this year, please invite the EC to tag along if there is something coming up

[andrii-i]

Wednesday, January 21 '26

Name	Affiliation	GitHub
Mike Krassowski	OpenTeams	@krassowski
Jason Grout	Independent	@jasongrout
William Stein	SageMath	@williamstein
Drake Aiman	Google	@wh1ter4bb1t-js
Andrii Ieroshenko	AWS	@andrii-i

• Mike:

  • {%preview Started failing with TypeError: '<' not supported between instances of 'str' and 'float' executablebooks/github-activity#164 %}
  • New shortcuts:
    • Ctrl + B for bold (only in markdown cells) {%preview Add Ctrl+B shortcut to toggle bold formatting in markdown cells jupyterlab#18328 %}
    • Accel + Alt + Num to switch tabs {%preview Add keyboard shortcuts to switch main area tabs by index jupyterlab#18293 %}
  • Update CodeMirror to latest versions jupyterlab#18344:
    • backport Backport PR #18344 on branch 4.5.x (Update CodeMirror to latest versions) jupyterlab#18366
      • deactivates new features
      • restores DOM cmView
    • downstream updates:
      • Use public API of CodeMirror's EditorView to find view from DOM jupyterlab-contrib/spellchecker#146
      • Use public API of CodeMirror's EditorView to find view from DOM jupyter-lsp/jupyterlab-lsp#1163

• Jeremy's PR for AI files:

  • Add AI rules jupyterlab#18322

• Isabel Paredes

  • Would like to work on the keyboard shortcut display system.
  • Recent work on keyboard shortcut settings: Allow adding shortcuts to commands without a default shortcut via UI jupyterlab#18163

• @jasongrout

  • Plausible stats for JupyterLite usage on jupyter.org. tl;dr: 15k-20k daily users, average time on page is around 17 minutes

--

What is one thing in your subproject that really should be done in 2026?

• (+2) More contributors and reviewers especially
  • Or ways to scale our reviewing, perhaps using LLMs to help
  • Perhaps starting PR review meetings like the current issue triage meetings
• Easy to use UI library (like Material UI) for consistent UI elements people can easily use
• Enable JupyterLab researchers to use local AI models or in-cluster AI models
  • Better integration in general with AI tooling by default with builtin packages
• Move document and session state to the server
  • William polished and open sourced the realtime sync algorithm used by cocalc: https://github.com/sagemathinc/patchflow It’s a very different feel than yjs — much more like a revision control system.

[RRosio]

Wednesday, January 28 '26

Name	Affiliation	GitHub
Mike Krassowski	OpenTeams	@krassowski
Jason Grout	Independent	@jasongrout
Ian Thomas	QuantStack	@ianthomas23
Rosio Reyes	Anaconda	@RRosio
A. T. Darian	QuantStack	@afshin
Jeremy Tuloup	QuantStack	@jtpio
Omar Jarjur	Google	@ojarjur
Nick Bollweg		@bollwyvl
R Ely		@ohrely

• Mike

  • LLM policy AI-assisted code policy: "Literature Review" jupyter/governance#326
    • One problem is the disproportion between the cost of generating vs reviewing the code
    • Omar: minimum could be "All use of LLMs must be disclosed up front"
    • Nick: a checklist with
      [ ] I did not use any AI
      [ ] I did use AI
      [ ] this is the model
      [ ] this is the prompt
    • consensus: tedious but would be valuable to gather data
    • split between what the LLM touches (code vs assist)
    • Add PR / issue template disclosure checkboxes?
      • - [ ] No code in this PR was generated with AI
      • - [ ] Some code in this PR was generated using AI.
      • - [ ] I have carefully reviewed this code (until this is true, keep the PR draft)
      • - AI models used:
    • "you must start with a new test that shows the problem before submitting a fix"
  • Improving quality of software and review capacity
    • [preface] working on shortening feedback loop for integration tests
    • copilot like reviews eg
      • Copilot
      • https://www.ellipsis.dev/
      • https://www.cubic.dev/
      • https://graphite.com/pricing
      • consensus:
        • allow reviewers to request Copilot review for now
        • encourage feedback from users (emojis) for out own evaluation purposes
        • reviewer should quickly triage the LLM results to avoid the PR author having to respond to noise
    • Stricter requirements on testing
      • both unit tests and integration tests
    • How do we ensure extensions still work (to be covered next time)

• Rosio

  • Interested in hosting a community call during this meeting time on February 25- thoughts or concerns? Issue opened in the team compass: Use meeting time for a Jupyter Community Call on February 25th #302

[RRosio]

Wednesday, 04 Feb 2026

Name	Affiliation	GitHub
Jason Grout	Independent	@jasongrout
Jeremy Tuloup	QuantStack	@jtpio
Sylvain Corlay	QuantStack	@SylvainCorlay
Ian Thomas	QuantStack	@ianthomas23
William Stein	SageMath	@williamstein
Konstantin Taletskiy	Anaconda	@ktaletsk
Rosio Reyes	Anaconda	@RRosio

• First Wednessday: Accessibility topics?

  • "Isabel is not connected but she is working on accessibility topics, more updates to come"- Sylvain
  • Rosio: Any ideas for additional ways in which we could highlight at the dedicated accessibility meeting?

• @SylvainCorlay

  • Quick announcement on notebook.link and demo
    • See blog post for more info
    • Example link from demo: https://notebook.link/@SylvainCorlay/demo
    • Jupyter Games demo
    • AI assistant uses https://github.com/jupyterlite/ai

• @jasongrout

  • JuptyerLab: Follow-up from last week's AI discussion, here is a proposal for AI info in the PR template. Any objections to merging or thoughts for improving?

    ## AI usage
    
    - [ ] No code in this PR was generated by AI
    - [ ] Some or all of the code in this PR was generated by AI.
      - [ ] The author has carefully reviewed this code (keep this PR draft until code has been reviewed)
      - AI tools and models used:
    

  • JupyterLab: FYI, @bollwyvl has a PR to update prettier, which involves lots of formatting changes that may conflict with existing open PRs.

• @krassowski

  • follow up on Copilot reviews experiment:
    • We requested reviews on roughly 16 PRs
    • it looks not everyone can request them :(
      • we may need to request EC/Jupyter Foundation funds to enable it for our repo or in the enteprise settings
    • it was able to pickup some accessibility issues too
    • it looks they are sometimes quite useful e.g.
      • Allow adding shortcuts to commands without a default shortcut via UI jupyterlab#18163 (comment)
      • Fix bulk rename dialog and enable rename for multi-selection jupyterlab#18407
    • List of Copilot-reviewed PRs in JupyterLab
  • Jupyter Foundation CFP update
    • Use sharding for faster visual regression/integration tests merged, UI tests now complete within 15 minutes. More work to come!
    • Tracking progress of proposals touching jupyterlab code in {%preview CFP '25 tracking %}
  • Cell duplication for ydoc still a problem and might be a problem until yjs v14 comes out (which is in pre-release since ~2022ish)
  • A couple of PRs on JupyterLab repo which need discussion.

• @andrii-i: let's (again) discuss potentially automatically running an agentic review for all new PRs and mb issues (for triaging)? Reviewers can later disagree / delete / edit the review. This might help with review load

  • @jasongrout: For PRs, I would prefer to expand the opt-in trial for now.
  • @SylvainCorlay: pointer to previous work by Matthias Meschede https://github.com/QuantStack/Trigent, which was applied to JupyterLab to create the issue triage board

• @ianthomas23

  • ipykernel 7.2.0 release planned for Friday
    • improvements to debugging
    • XPUB socket for iopub channel JEP 65
    • kernel spec reporting correct kernel protocol version, etc
    • wx event loop improvements

• @SylvainCorlay

  • Please vote on the parameterized kernelspec JEP
  • Parameterized kernel specs proposal jupyter/enhancement-proposals#87

• @ktaletsk

  • JupyterLab has reached 700 published JupyterLab-4-compatible extensions today!
    • Is there an interest in Jupyter blog post celebrating the milestone?
      • @jasongrout: YES!

[RRosio]

Wednesday, 11 Feb 2026

Name	Affiliation	GitHub
Jason Grout	Independent	@jasongrout
Mike Krassowski	OpenTeams	@krassowski
William Stein	CoCalc	@williamstein
Ian Thomas	QuantStack	@ianthomas23
Afshin T. Darian	QuantStack	@afshin
Drake Aiman	Google	@wh1ter4bb1t-js
Andrii Ieroshenko	AWS	@andrii-i
Jeremy Tuloup	QuantStack	@jtpio

• @jasongrout

  • Preserve PR description in squashed PR merges. Please make sure your PR descriptions are complete and kept up to date.
  • Updated Locking workflow - end result is that closed issues and prs with no activity will be locked after 180 days. Today this will start locking 176 closed inactive issues and 282 closed inactive PRs.
  • Delayed merge: Sometimes it seems that a maintainer reviews a PR and approves it, but wants others to have a chance to look at it before merging. Would it be helpful to have a bot that could merge a PR if it had at least one approval, CI passes, and there was no activity for 24 hours?
    • This would be used on occasion
    • Question is if the implementation/maintenance cost is too high

• Mike @krassowski

  • heads up jupyterlab-code-formatter new version released
  • Fix flaky tests
    • Fix flaky UI tests jupyterlab#18453
  • improving quality/reducing breakages
    • Nick: quarterly distribution of a set of Jupyter packages that were tested together and vetted. Sort of like an LTS (but without the ongoing S)
    • Host a JupyterLab metapackage jupyterlab-contrib/jupyterlab-contrib.github.io#23
    • Regression testing across versions/browsers/repeats
    • https://github.blog/changelog/2025-10-28-github-code-quality-in-public-preview/
  • Code Quality on top of CodeQL: should we experiment with enabling it?
    • @jasongrout: sure, +1 to experimenting
  • Copilot review update
    • Multiple reviews often bring up the same issues, not remembering the resolution from the last review
    • Does not have empathy. For example, does not highlight the big stuff, or the nice things about the PR, etc.
    • Does not have memory
    • @jasongrout: +1 to continuing to keep copilot reviews as opt-in, not automatically enabled
  • CODEOWNERS
    • PR
  • PRs that need discussion
    • Feature: jump to last cell of notebook
    • Improve placeholder in the rendered markdown cell
    • Add keyboard shortcuts to switch main area tabs by index

• Andrii @andrii-i, question from Triaging: this issue is about LaTeX newcommands not being used at startup. JupyterLab makes more sense for that issue as it houses relevant packages like rendermime responsible for cell source code processing, right? LaTeX newcommands not used at startup in first few cells but then used after that jupyter/notebook#7827

  • @jasongrout: agreed it makes sense to move to JupyterLab because that is likely where the code lives. The issue even indicates it reproduces on JupyterLab.

---

Wednesday, 18 Feb 2026

Name	Affiliation	GitHub
Andrii Ieroshenko	AWS	@andrii-i
Mike Krassowski	OpenTeams	@krassowski
Wasim Lorgat	Posit	@seeM
Drake Aiman	Google	@wh1ter4bb1t-js
Nicolas Brichet	QuantStack	@brichet
Jason Grout	Independent	@jasongrout
Jeremy Tuloup	QuantStack	@jtpio
William Stein	CoCalc	@williamstein

• Mike (needs to drop early)

  • discusssion around potential policy for agent contributions on Jupyter zulip
    • A "literature review" of AI policies
    • As a reviewer, feel free to insist that the AI disclosure section on JupyterLab PRs be filled out
  • jupyter-server jupyverse extension compatibility or future beyond tornado?
    • @jasongrout: IIRC, Zach looked at using fastapi, and (IIRC) said that there weren't many advantages over tornado
    • Nick: I would not take on fastapi as a basis for the server, saying that as a person maintaining some fastapi projects. Tornado is fast enough. If moving on from tornado, you might look at Django, etc. The dependency chain for fastapi is complex and poorly maintained - it is hard to keep on top of that nest of packages. ASGI might be the right level to make an interface. Tornado does not support ASGI. A way to move forward is to help Tornado support ASGI.
      • https://connexion.readthedocs.io/en/stable/
    • Mike: can we have an extension interface layer for cross compatibility?
    • Towards a new generic and composable server jupyter-server/team-compass#11
  • Adding core-meta package in Add @jupyterlab/core-meta package for core metadata jupyterlab#18528

• Rosio (joining meeting late)

  • Community Call next week during this meeting hour, please see blog post (thank you to @SylvainCorlay for publishing!) and add yourself to the agenda to present!

• Wasim

  • Hi 👋 first time joining. I lead the team working on notebooks in Positron, and worked on nbdev before that. We're huge Jupyter fans and would love to get more involved and see how we can help!

---

Wednesday, 25 February 2026

The Jupyter Community Call was hosted during this hour.

---

Wednesday, 4 March 2026

Name	Affiliation	GitHub
Mike Krassowski	OpenTeams	@krassowski
Jenn Kotler	STScI	@Jenneh
Thomas Dutkiewicz	STScI	@ttdu
Jason Grout	Independent	@jasongrout
Drake Aiman	Google	@wh1ter4bb1t-js
Wasim Lorgat	Posit	@seeM
Andrii Ieroshenko	AWS	@andrii-i
Isabel Paredes	QuantStack	@IsabelParedes
Ian Thomas	QuantStack	@ianthomas23
Jeremy Tuloup	QuantStack	@jtpio
Rosio Reyes	Anaconda	@RRosio
Konstantin Taletskiy	Anaconda	@ktaletsk

Accessibility Topics

• Jenn:
  • New Grant Proposal at STScI for a FTE for several years working on accessibility. Decision comes in June. This may be internal or contracting work - still figuring out proposal.
  • Want to check in on the Quantstack Project, see if there is potential for collaboration. (Yes, but relevant Quantstack people not here today)
    • Goal for Quantstack is getting things keyboard accessible
    • See Theme variables for focus indicators jupyterlab#18598
    • High-level overview of this? Not at present. Could be added to the CFP tracking board at CFP '25 tracking
  • Potentially worth advertising to jupyter-accessibility-council@googlegroups.com

Agenda

• Mike:
  • moved eslint-plugin to JupyterLab org after reviewing the codebase, it is now on npm
  • plugin-playground activity
  • Please help review PRs
  • Tracking board for community proposal work: CFP '25 tracking
  • Specific accessibility PR to review: Improve screen reader behavior in launcher/notebook and add tests jupyterlab#18570

Events:

• Scipy 2026 talk submission deadline is today
• Community workshops
  • Jupyter AI workshop March 18-19 in Seattle and Paris
  • Security tooling workshop March 31

Off the record

• JupyterLab 4.6 planning - following up next week

[choldgraf]

Just a quick note that Jupyter Book's team has been talking about a11y needs more and more lately, so if there are opportunities to collaborate or join forces, maybe we can figure something out? Here's a recent issue where folks were asking about accessibility for PDFs, for example:

• Improve accessibility of MyST-generated PDFs jupyter-book/mystmd#2743

[IsabelParedes]

Just a quick note that Jupyter Book's team has been talking about a11y needs more and more lately, so if there are opportunities to collaborate or join forces, maybe we can figure something out? Here's a recent issue where folks were asking about accessibility for PDFs, for example:

• Improve accessibility of MyST-generated PDFs jupyter-book/mystmd#2743

Hi @choldgraf ! I'm working on some accessibility issues. What's the best way to communicate better for collaboration? Should there be an Accessibility channel on the Jupyter Zulip instance?

[jtpio]

Wednesday, 11 March 2026

Name	Affiliation	GitHub
Mike Krassowski	OpenTeams	@krassowski
R Ely	Bloomberg	@ohrely
Jason Grout	Independent	@jasongrout
Vidar Fauske	JP Morgan Chase	@vidartf
Konstantin Taletskiy	Anaconda	@ktaletsk
Jeremy Tuloup	QuantStack	@jtpio
Rosio Reyes	Anaconda	@RRosio
Andrii Ieroshenko	AWS	@andrii-i
Ian Thomas	QuantStack	@ianthomas23
Isabel Paredes	QuantStack	@IsabelParedes

Mike:

• tree based file browser WIP/Discussion: Tree view for file browser jupyterlab#5526
• early mention for frontends: choose an SSC representative for frontends 26/27

Ely:

• Next Jupyter Open Studio Day in NYC on Monday, April 20th
  • https://go.bloomberg.com/attend/invite/jupyter-open-studio-day-april-20-2026/

Rosio:

• From last week: JupyterLab 4.6 planning

Status Options: Needs testing, Blocked, Needs reviewer, Needs decision, At risk

Type	Item	Status	Action	Notes
PR	18030	Needs testing	Give it a try accross browsers to find any issues
PR	17986	Blocked	Review after conflicts resolved	Waiting on author
Issue	16528	At risk	Find contributor	Might be removed