-
-
Notifications
You must be signed in to change notification settings - Fork 30
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
Comments
January 9, 2024
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.
|
January 23, 2024
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. |
January 30, 2024
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. |
February 6, 2024
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. |
February 13, 2024
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.
|
February 20, 2024
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. |
February 27, 2024
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. |
March 5, 2024
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.
|
@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? |
March 12, 2024
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. |
March 19, 2024
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. |
March 26, 2024
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. |
April 2, 2024
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.
|
April 16, 2024
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. |
April 23, 2024
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.
|
April 30, 2024
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.
|
May 7, 2024
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.
|
May 14, 2024
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. |
May 21, 2024
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. |
May 28, 2024
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. |
June 4, 2024
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. |
June 18, 2024
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. |
June 25, 2024
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. |
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:
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.
a. good first issue
b. bug
c. feature parity
d. Tag milestones
Add milestone if you can achieve the goal.
Meetings
Primary focus:
The text was updated successfully, but these errors were encountered: