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 2024 #228

Closed
JasonWeill opened this issue Dec 19, 2023 · 24 comments
Closed

Weekly Triage meetings: Jan–Jun 2024 #228

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

Comments

@JasonWeill
Copy link
Contributor

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:

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:

@JasonWeill JasonWeill added the Dev Meeting Minutes Minutes from a dev meeting. label Dec 19, 2023
@JasonWeill
Copy link
Contributor Author

January 2, 2024

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

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

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

We did not triage JupyterLab Desktop issues, due to a lack of time.

@fcollonval fcollonval pinned this issue Jan 5, 2024
@JasonWeill
Copy link
Contributor Author

January 9, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Eric Gentry Anaconda @ericsnekbytes
Rosio Reyes Anaconda @RRosio
Jeremy Tuloup QuantStack @jtpio

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

Before the meeting, 5 issues in 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

January 23, 2024

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

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

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

We did not triage JupyterLab Desktop issues, due to a lack of time.

@JasonWeill
Copy link
Contributor Author

January 30, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Michał Krassowski QuanSight @krassowski

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

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

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

@JasonWeill
Copy link
Contributor Author

JasonWeill commented Feb 6, 2024

February 6, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Michał Krassowski QuanSight @krassowski

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

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

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

@JasonWeill
Copy link
Contributor Author

February 13, 2024

Name Organization Username
Jason Weill AWS @JasonWeill

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

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

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

@JasonWeill
Copy link
Contributor Author

February 20, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Michał Krassowski QuanSight @krassowski
Rosio Reyes Anaconda @RRosio
Eric Gentry Anaconda @ericsnekbytes

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

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

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

@JasonWeill
Copy link
Contributor Author

February 27, 2024

Name Organization Username
Jason Weill AWS @JasonWeill

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

Before the meeting, 9 issues in Jupyter Notebook needed triage. After the meeting, 3 remain. (@RRosio triaged all of these except 7275.)

No issues in JupyterLab Desktop needed triage.

@JasonWeill
Copy link
Contributor Author

March 5, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Michał Krassowski QuanSight @krassowski

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

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

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

@JasonWeill
Copy link
Contributor Author

@RRosio Thank you very much for triaging the Notebook issues for the last couple of weeks! Would another time of day work better for you so that we could all join triage together?

@JasonWeill
Copy link
Contributor Author

March 12, 2024

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

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

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

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

@JasonWeill
Copy link
Contributor Author

March 19, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Michał Krassowski QuanSight @krassowski

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

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

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

@JasonWeill
Copy link
Contributor Author

March 26, 2024

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

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

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

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

@JasonWeill
Copy link
Contributor Author

April 2, 2024

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

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

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

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

@JasonWeill
Copy link
Contributor Author

April 16, 2024

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

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

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

We did not triage JupyterLab Desktop issues, due to time constraints.

@JasonWeill
Copy link
Contributor Author

April 23, 2024

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

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

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

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

@JasonWeill
Copy link
Contributor Author

April 30, 2024

Name Organization Username
Jason Weill AWS @JasonWeill

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

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

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

@JasonWeill
Copy link
Contributor Author

May 7, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Rosio Reyes Anaconda @RRosio
Michał Krassowski QuanSight @krassowski
Carlos Brandt @chbrandt

Before the meeting, 18 issues in JupyterLab needed triage. After the meeting, 2 remains.

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

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

@JasonWeill
Copy link
Contributor Author

May 14, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Michał Krassowski QuanSight @krassowski

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

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

No issues in JupyterLab Desktop needed triage.

@JasonWeill
Copy link
Contributor Author

May 21, 2024

Name Organization Username
Jason Weill AWS @JasonWeill
Michał Krassowski QuanSight @krassowski
Rosio Reyes Anaconda @RRosio
Jiayi Xu @Sunnyweather1314

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

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

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

@JasonWeill
Copy link
Contributor Author

May 28, 2024

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

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

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

Before the meeting, 5 issues in Classic Notebook (nbclassic) needed triage. After the meeting, none remain.

No issues in JupyterLab Desktop needed triage.

@JasonWeill
Copy link
Contributor Author

June 4, 2024

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

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

Before the meeting, 5 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.

No issues in Classic Notebook (nbclassic) needed triage.

@JasonWeill
Copy link
Contributor Author

June 18, 2024

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

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

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

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

No issues in Classic Notebook (nbclassic) needed triage.

@JasonWeill
Copy link
Contributor Author

June 25, 2024

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

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

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

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

No issues in Classic Notebook (nbclassic) needed triage.

@JasonWeill JasonWeill unpinned this issue Jun 25, 2024
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

1 participant