Weekly Triage meetings: Jul–Dec 2024

[JasonWeill]

Triage issues in JupyterLab and corresponding projects.

Meeting is typically held at 09:00 US Pacific time on Tuesdays.

Meeting info: https://zoom.us/my/jovyan?pwd=c0JZTHlNdS9Sek9vdzR3aTJ4SzFTQT09

Previous notes:

• https://github.com/jupyterlab/frontends-team-compass/issues/228 (2024-01 through 2024-06)
• https://github.com/jupyterlab/frontends-team-compass/issues/203 (2023-07 through 2023-12)
• https://github.com/jupyterlab/frontends-team-compass/issues/169 (2023-01 through 2023-06)
• https://github.com/jupyterlab/frontends-team-compass/issues/151 (2022-07 through 2022-12)
• https://github.com/jupyterlab/frontends-team-compass/issues/137 (2022-01 through 2022-06)

Goals

Act on long-running, highly demanded, or highly discussed issues to get them ready for development work.

Resources

https://jupyterlab.readthedocs.io/en/latest/developer/contributing.html#submitting-a-pull-request-contribution

Triage Process

All requested information, where applicable, is provided. From the templates in JupyterLab’s issues:

For a bug:

• Description, preferably including screen shots
• Steps to reproduce
• Expected behavior
• Context, such as OS, browser, JupyterLab version, and output or log excerpts

For a feature request:

• Description of the problem
• Description of the proposed solution
• Additional context

The issue should represent real, relevant, feasible work. In short, if a knowledgeable person were to be assigned this issue, they would be able to complete it with a reasonable amount of effort and assistance, and it furthers the goals of the Jupyter project.

• Issues should be unique; triage is the best time to identify duplicates.
• Bugs represent valid expectations for use of Jupyter products and services.
• Expectations for security, performance, accessibility, and localization match generally-accepted norms in the community that uses Jupyter products.
• The issue represents work that one developer can commit to owning, even if they collaborate with other developers for feedback. Excessively large issues should be split into multiple issues, each triaged individually, or into team-compass issues to discuss more substantive changes.

1. Read issues
2. Tag issues a. good first issue b. bug c. feature parity d. Tag milestones
3. Identify duplicates
4. Respond to issues
5. Assign another person

Add milestone if you can achieve the goal.

Meetings

Primary focus:

• JupyterLab untriaged issues
• Notebook untriaged issues
• JupyterLab Desktop untriaged issues
• nbclassic untriaged issues

[JasonWeill]

July 2, 2024

Name	Organization	Username
Jason Weill	AWS	@JasonWeill
Rosio Reyes	Anaconda	@RRosio

Before the meeting, 11 issues in JupyterLab needed triage. After the meeting, 1 remains.

• https://github.com/jupyterlab/jupyterlab/issues/16389 (needs info)
• https://github.com/jupyterlab/jupyterlab/issues/16505 (accepted)
• https://github.com/jupyterlab/jupyterlab/issues/16513 (closed)
• https://github.com/jupyterlab/jupyterlab/issues/16517 (accepted)
• https://github.com/jupyterlab/jupyterlab/issues/16525 (closed, duplicate of https://github.com/jupyterlab/jupyterlab/issues/10593)
• https://github.com/jupyterlab/jupyterlab/issues/16527 (accepted)
• https://github.com/jupyterlab/jupyterlab/issues/16528 (accepted)
• https://github.com/jupyterlab/jupyterlab/issues/16533 (closed, duplicate of https://github.com/jupyterlab/jupyterlab/issues/16373)
• https://github.com/jupyterlab/jupyterlab/issues/16542 (accepted)
• https://github.com/jupyterlab/jupyterlab/issues/16543 (accepted)
• https://github.com/jupyterlab/jupyterlab/issues/16544 (accepted)

Before the meeting, 8 issues in Notebook needed triage. After the meeting, 4 remain.

• https://github.com/jupyter/notebook/issues/7402 (closed)
• https://github.com/jupyter/notebook/issues/7401 (accepted)
• https://github.com/jupyter/notebook/issues/7407 (needs info)
• https://github.com/jupyter/notebook/issues/7408 (needs info)
• https://github.com/jupyter/notebook/issues/7409 (needs info)
• https://github.com/jupyter/notebook/issues/7411 (closed)
• https://github.com/jupyter/notebook/issues/7412 (closed)
• https://github.com/jupyter/notebook/issues/7415 (needs info)

No issues in JupyterLab Desktop or Classic Notebook (nbclassic) needed triage.