-
-
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: Jul–Dec 2023 #203
Comments
July 18, 2023
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. |
July 25, 2023
Before the meeting, 6 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 5 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. |
August 1, 2023
Before the meeting, 4 issues in JupyterLab needed triage. After the meeting, none remain.
Before the meeting, 5 issues in Notebook needed triage. After the meeting, 2 remain.
No issues in JupyterLab Desktop needed triage. |
August 8, 2023
Before the meeting, 7 issues in JupyterLab needed triage. After the meeting, 2 remain.
Before the meeting, 5 issues in Notebook needed triage. After the meeting, 1 remains.
No issues in JupyterLab Desktop needed triage. |
August 15, 2023
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. |
August 22, 2023
Before the meeting, 9 issues in JupyterLab needed triage. After the meeting, 1 remains.
No issues in Notebook needed triage. Before the meeting, 2 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain. |
August 29, 2023
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.
|
September 5, 2023
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. |
September 12, 2023
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. |
September 19, 2023
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. |
September 26, 2023
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. |
October 3, 2023
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 |
October 10, 2023
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. |
October 17, 2023
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. |
October 24, 2023
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.
|
October 31, 2023
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. |
November 7, 2023
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. |
November 14, 2023
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. |
November 21, 2023
Before the meeting, 12 issues in JupyterLab needed triage. After the meeting, none remain. jupyterlab/jupyterlab#15397 (needs triage) |
November 28, 2023
Before the meeting, 7 issues in Notebook needed triage. After the meeting, 5 remain.
|
December 5, 2023
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. |
December 12, 2023
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.
|
December 19, 2023
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. |
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:
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:
Additional areas:
The text was updated successfully, but these errors were encountered: