Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Weekly Triage meetings: Jan-Jun 2023 #169

Closed
JasonWeill opened this issue Dec 29, 2022 · 24 comments
Closed

Weekly Triage meetings: Jan-Jun 2023 #169

JasonWeill opened this issue Dec 29, 2022 · 24 comments
Labels
Dev Meeting Minutes Minutes from a dev meeting.

Comments

@JasonWeill
Copy link
Contributor

JasonWeill commented Dec 29, 2022

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:

  • 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:

Additional areas:

@JasonWeill JasonWeill added the Dev Meeting Minutes Minutes from a dev meeting. label Dec 29, 2022
@fcollonval fcollonval pinned this issue Jan 4, 2023
@JasonWeill
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link

andrii-i commented Mar 21, 2023

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
Copy link

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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
Copy link
Contributor Author

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 jupyter/notebook#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
Copy link
Contributor Author

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
Copy link
Contributor Author

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dev Meeting Minutes Minutes from a dev meeting.
Projects
None yet
Development

No branches or pull requests

2 participants