-
-
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 2024 #250
Comments
July 9, 2024
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. |
July 16, 2024
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. |
July 23, 2024
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. |
July 30, 2024
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. |
August 6, 2024
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. |
August 13, 2024
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. |
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: