jupyterlab / frontends-team-compass

A repository for team interaction, syncing, and handling meeting notes across the JupyterLab ecosystem.
https://jupyterlab-team-compass.readthedocs.io/en/latest/
BSD 3-Clause "New" or "Revised" License
59 stars 30 forks source link

Weekly Triage meetings: Jan-Jun 2023 #169

Closed JasonWeill closed 1 year ago

JasonWeill commented 1 year ago

Jupyter Issue Triaging

Triage issues in JupyterLab and corresponding projects.

Meeting is typically held at 10:00 US Pacific time on Thursdays.

Meeting info: https://zoom.us/my/jovyan?pwd=c0JZTHlNdS9Sek9vdzR3aTJ4SzFTQT09 HackMD: https://hackmd.io/HaQ3S_nPSbqaRtk9rj59iA

Previous notes:

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:

For a feature request:

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.

  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:

Additional areas:

JasonWeill commented 1 year ago

January 5, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Rosio Reyes Anaconda @RRosio
Michał Krassowski @krassowski
Andrii Ieroshenko AWS @andrii-i

Before the meeting, 8 issues in JupyterLab needed triage. After the meeting, 2 remain.

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

Before the meeting, 4 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain.

JasonWeill commented 1 year ago

January 12, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Rosio Reyes Anaconda @RRosio
Michał Krassowski @krassowski

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

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

We did not triage JupyterLab Desktop issues today.

JasonWeill commented 1 year ago

January 19, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Rosio Reyes Anaconda @RRosio
Michał Krassowski @krassowski
Tony Fast @tonyfast
Gabriel Fouasnon @gabalafou

Before the meeting, 14 issues in JupyterLab needed triage. After the meeting, 2 remain.

Before the meeting, 6 issues in Jupyter Notebook needed triage. After the meeting, 3 remain.

We did not triage JupyterLab Desktop issues today.

JasonWeill commented 1 year ago

January 26, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Rosio Reyes Anaconda @RRosio
Michał Krassowski @krassowski
Tony Fast @tonyfast

Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, 3 remain.

Before the meeting, 4 issues in Jupyter Notebook needed triage. After the meeting, one remains.

Before the meeting, 1 issue in JupyterLab Desktop needed triage. After the meeting, none remains.

JasonWeill commented 1 year ago

February 2, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Rosio Reyes Anaconda @RRosio
Tony Fast @tonyfast
Andrii Ieroshenko AWS @andrii-i
Nicholas Bollweg @bollwyvl

Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, 2 remain.

Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, 2 remain.

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

JasonWeill commented 1 year ago

February 9, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
tony fast @tonyfast
Rosio Reyes Anaconda @RRosio
Michal Krassowski Quansight @krassowski
Gabriel Fouasnon @gabalafou

Before the meeting, 14 issues in JupyterLab needed triage. After the meeting, 5 remain.

Before the meeting, 7 issues in Jupyter Notebook needed triage. After the meeting, 3 remain.

No issues in JupyterLab Desktop needed triage.

JasonWeill commented 1 year ago

February 16, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Michal Krassowski Quansight @krassowski
tony fast @tonyfast
Rosio Reyes Anaconda @RRosio
Martha Cryan IBM @marthacryan

Before the meeting, 18 issues in JupyterLab needed triage. After the meeting, 5 remain.

Before the meeting, 5 issues in Jupyter Notebook needed triage. After the meeting, none remain.

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

JasonWeill commented 1 year ago

February 23, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Michal Krassowski Quansight @krassowski
tony fast @tonyfast
Rosio Reyes Anaconda @RRosio
Andrii Ieroshenko AWS @andrii-i

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

No issues in Jupyter Notebook needed triage.

Before the meeting, 6 issues in JupyterLab Desktop needed triage. After the meeting, 3 remain.

JasonWeill commented 1 year ago

March 2, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Andrii Ieroshenko AWS @andrii-i
Rosio Reyes Anaconda @RRosio

Before the meeting, 16 issues in JupyterLab needed triage. After the meeting, 2 remain.

Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, none remain.

Before the meeting, 8 issues in JupyterLab Desktop needed triage. After the meeting, 5 remain.

JasonWeill commented 1 year ago

March 9, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
tony fast @tonyfast
Michal Krassowski @krassowski
Rosio Reyes Anaconda @RRosio
Michal Krassowski Quansight @krassowski
Andrii Ieroshenko AWS @andrii-i

Before the meeting, 9 issues in JupyterLab needed triage. After the meeting, 2 remain.

Before the meeting, 1 issue in Jupyter Notebook needed triage. After the meeting, none remain.

Before the meeting, 9 issues in JupyterLab Desktop needed triage. After the meeting, 5 remain.

JasonWeill commented 1 year ago

As discussed earlier today, there will be no triage next week. Starting on March 21, 2023, triage moves to Tuesdays at 09:00 PDT (16:00 UTC). See you then!

andrii-i commented 1 year ago

March 21, 2023

Name Organization Username
Andrii Ieroshenko AWS @andrii-i

Before the meeting, 24 issues in JupyterLab needed triage. After the meeting, 6 remain.

Jupyter Notebook issues were not triaged this meeting.

JupyterLab Desktop issues were not triaged this meeting.

andrii-i commented 1 year ago

March 28, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Andrii Ieroshenko AWS @andrii-i
Rosio Reyes Anaconda @RRosio

Before the meeting, 23 issues in JupyterLab needed triage. After the meeting, 5 remain.

Before the meeting, 16 issues in Notebook needed triage. After the meeting, 3 remain.

JupyterLab Desktop issues were not triaged this meeting.

JasonWeill commented 1 year ago

April 4, 2023

Name Organization Username
Jason Weill AWS @jweill-aws
Rosio Reyes Anaconda @RRosio
Andrii Ieroshenko AWS @andrii-i

Before the meeting, 19 issues in JupyterLab needed triage. After the meeting, 3 remain.

Before the meeting, 5 issues in Notebook needed triage. After the meeting, 3 remain.

Before the meeting, 19 issues in JupyterLab Desktop needed triage. After the meeting, 7 remain.

JasonWeill commented 1 year ago

April 11, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Andrii Ieroshenko AWS @andrii-i
Rosio Reyes Anaconda @RRosio
Michał Krassowski Quansight @krassowski

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

Before the meeting, 6 issues in Notebook needed triage. After the meeting, 1 remains.

Before the meeting, 12 issues in JupyterLab Desktop needed triage. After the meeting, 5 remain.

JasonWeill commented 1 year ago

April 18, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Andrii Ieroshenko AWS @andrii-i
Rosio Reyes Anaconda @RRosio
Michał Krassowski Quansight @krassowski

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

Before the meeting, 1 issue in Notebook needed triage. After the meeting, 1 remains.

Before the meeting, 6 issues in JupyterLab Desktop needed triage. After the meeting, 4 remain.

JasonWeill commented 1 year ago

April 25, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Rosio Reyes Anaconda @RRosio
Michał Krassowski Quansight @krassowski

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

Before the meeting, 5 issues in Notebook needed triage. After the meeting, 2 remain.

Before the meeting, 6 issues in JupyterLab Desktop needed triage. After the meeting, 4 remain.

JasonWeill commented 1 year ago

May 2, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Andrii Ieroshenko AWS @andrii-i
Rosio Reyes Anaconda @RRosio

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

Before the meeting, 3 issues in Notebook needed triage. After the meeting, 1 remains.

Before the meeting, 5 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain.

JasonWeill commented 1 year ago

May 16, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Andrii Ieroshenko AWS @andrii-i

Before the meeting, 16 issues in JupyterLab needed triage. After the meeting, 5 remain.

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

Before the meeting, 5 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain.

JasonWeill commented 1 year ago

May 30, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Andrii Ieroshenko AWS @andrii-i
Rosio Reyes Anaconda @RRosio
Michał Krassowski Quansight @krassowski

Before the meeting, 14 issues in JupyterLab needed triage. After the meeting, 3 remain.

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

No issues in JupyterLab Desktop needed triage.

Notebook 7.0 bugs triage during May 30 call to identify release blockers:

JasonWeill commented 1 year ago

June 6, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Andrii Ieroshenko AWS @andrii-i
Paddy Mullen

Before the meeting, 13 issues in JupyterLab needed triage. After the meeting, 3 remain.

Before the meeting, 7 issues in Notebook needed triage. After the meeting, 2 remain.

Before the meeting, 2 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain.

JasonWeill commented 1 year ago

June 13, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Andrii Ieroshenko AWS @andrii-i
Paddy Mullen
Rosio Reyes Anaconda @RRosio
Gabriel Fouasnon @gabalafou

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

Before the meeting, 7 issues in Notebook needed triage. After the meeting, 5 remain.

We also discussed https://github.com/jupyter/notebook/issues/6800, which was not in need of triage, but which may result in additional issues created for individual tasks within it.

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

JasonWeill commented 1 year ago

June 20, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Andrii Ieroshenko AWS @andrii-i
Michał Krassowski Quansight @krassowski
Rosio Reyes Anaconda @RRosio

Before the meeting, 19 issues in JupyterLab needed triage. After the meeting, 2 remain.

Before the meeting, 6 issues in Notebook needed triage. After the meeting, 2 remain.

Before the meeting, 2 issues in JupyterLab Desktop needed triage. After the meeting, none remain.

JasonWeill commented 1 year ago

June 27, 2023

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

Before the meeting, 11 issues in JupyterLab needed triage. After the meeting, 2 remain.

Before the meeting, 10 issues in Notebook needed triage. After the meeting, 1 remains.

No issues in JupyterLab Desktop needed triage.