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: Jul–Dec 2024 #250

Open
JasonWeill opened this issue Jun 25, 2024 · 7 comments
Open

Weekly Triage meetings: Jul–Dec 2024 #250

JasonWeill opened this issue Jun 25, 2024 · 7 comments
Labels
bug Something isn't working

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 bug Something isn't working label Jun 25, 2024
@JasonWeill JasonWeill pinned this issue Jun 25, 2024
@JasonWeill
Copy link
Contributor Author

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.

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

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

@JasonWeill
Copy link
Contributor Author

July 9, 2024

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

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

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

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

@JasonWeill
Copy link
Contributor Author

July 16, 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, 5 issues in Notebook needed triage. After the meeting, 4 remain.

Before the meeting, 1 issue in JupyterLab Desktop needed triage. After the meeting, no issues remain.

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

@JasonWeill
Copy link
Contributor Author

July 23, 2024

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

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

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

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

No issues in Classic Notebook (nbclassic) needed triage.

@JasonWeill
Copy link
Contributor Author

July 30, 2024

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

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

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

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

No issues in Classic Notebook (nbclassic) needed triage.

@JasonWeill
Copy link
Contributor Author

August 6, 2024

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

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

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

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

No issues in Classic Notebook (nbclassic) needed triage.

@JasonWeill
Copy link
Contributor Author

August 13, 2024

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

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

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

Before the meeting, 3 issues in jupyterlab-desktop needed triage. After the meeting, none remain.

There were no issues in Classic Notebook (nbclassic) needing triage.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant