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 2023 #203

Closed
JasonWeill opened this issue Jun 27, 2023 · 24 comments
Closed

Weekly Triage meetings: Jul–Dec 2023 #203

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

Comments

@JasonWeill
Copy link
Contributor

Jupyter Issue Triaging

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

Notes on GitHub:

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 Jun 27, 2023
@fcollonval fcollonval pinned this issue Jul 11, 2023
@JasonWeill
Copy link
Contributor Author

July 11, 2023

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

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

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

July 18, 2023

Name Organization Username
Jason Weill AWS @JasonWeill

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

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

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

@JasonWeill
Copy link
Contributor Author

@JasonWeill
Copy link
Contributor Author

@JasonWeill
Copy link
Contributor Author

August 15, 2023

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

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

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

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

@JasonWeill
Copy link
Contributor Author

August 29, 2023

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

Before the meeting, 12 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, 4 issues in JupyterLab Desktop needed triage. After the meeting, 1 remains.

@JasonWeill
Copy link
Contributor Author

September 5, 2023

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

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

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

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

@JasonWeill
Copy link
Contributor Author

September 12, 2023

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

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

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, 1 remains.

@JasonWeill
Copy link
Contributor Author

September 19, 2023

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

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

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

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

@JasonWeill
Copy link
Contributor Author

September 26, 2023

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

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

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

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

@JasonWeill
Copy link
Contributor Author

October 3, 2023

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

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

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

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

Additional topic: FileUpload is not working with kernel gateway

@JasonWeill
Copy link
Contributor Author

October 10, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Rosio Reyes Anaconda @RRosio
Piyush Jain AWS @3coins

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

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

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

@JasonWeill
Copy link
Contributor Author

October 17, 2023

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

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

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

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

@JasonWeill
Copy link
Contributor Author

October 24, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
R Ely Bloomberg @ohrely

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

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

October 31, 2023

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

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

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

@andrii-i
Copy link

andrii-i commented Nov 7, 2023

November 7, 2023

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

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

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, 1 remains.

@JasonWeill
Copy link
Contributor Author

November 14, 2023

Name Organization Username
Jason Weill AWS @JasonWeill
Rosio Reyes Anaconda @RRosio
Michał Krassowski Quansight @krassowski
Eric Gentry Anaconda @ericsnekbytes
Gabriel Fouasnon @gabalafou

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, none remain.

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

@JasonWeill
Copy link
Contributor Author

November 21, 2023

Name Organization Username
Rosio Reyes Anaconda @RRosio
Eric Gentry Anaconda @ericsnekbytes

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

jupyterlab/jupyterlab#15397 (needs triage)
jupyterlab/jupyterlab#15411 (needs info)
jupyterlab/jupyterlab#15414 (accepted)
jupyterlab/jupyterlab#15415 (accepted)
jupyterlab/jupyterlab#15416 (accepted)
jupyterlab/jupyterlab#15420 (accepted)
jupyterlab/jupyterlab#15423 (accepted)
jupyterlab/jupyterlab#15425 (accepted)
jupyterlab/jupyterlab#15428 (closed as duplicate)
jupyterlab/jupyterlab#15429 (closed)
jupyterlab/jupyterlab#15431 (needs info)
jupyterlab/jupyterlab#15432 (accepted)

@JasonWeill
Copy link
Contributor Author

December 5, 2023

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

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

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

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

@JasonWeill
Copy link
Contributor Author

JasonWeill commented Dec 12, 2023

December 12, 2023

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

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

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

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

@JasonWeill
Copy link
Contributor Author

December 19, 2023

Name Organization Username
Michał Krassowski Quansight @krassowski
Jason Weill AWS @JasonWeill
Carlos Brandt @chbrandt

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

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

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

No triage meeting will be held on December 26.

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