Weekly Triage meetings: Jul-Dec 2022 #151
Labels
Dev Meeting Minutes
Minutes from a dev meeting.
Comments
July 14, 2022🇫🇷
Issues triagedBefore the meeting, 9 issues in JupyterLab needed triage. After the meeting, 2 remain.
|
July 21, 2022Happy Belgian Independence Day 🇧🇪
Issues triagedBefore the meeting, 13 issues in JupyterLab needed triage. After the meeting, 8 remain.
|
July 28, 2022Happy Fiestas Patrias 🇵🇪
Issues triagedBefore the meeting, 17 issues in JupyterLab needed triage. After the meeting, 8 remain.
|
August 4, 2022
Issues triagedBefore the meeting, 21 issues in JupyterLab needed triage. After the meeting, 7 remain.
We also discussed adding the Jupyter probot integration, for automatic triage tagging, to the |
August 11, 2022
Issues triagedBefore the meeting, 16 issues in JupyterLab needed triage. After the meeting, 4 remain.
Starting with this meeting, Rosio will lead weekly triage of Jupyter Notebook issues. Probot now tags all new Notebook issues with Before the meeting, 1 issue in Jupyter Notebook needed triage. After the meeting, zero remain.
|
August 18, 2022Happy National Fajita Day (US)
Before the meeting, 17 issues in JupyterLab needed triage. After the meeting, 2 remain.
No new issues in Jupyter Notebook need triage. We discussed closing most JupyterLab pull requests without activity in a year or more. Accessibility-related PRs are exempt, although we should still leave comments to encourage progress on them. |
August 25, 2022
Before the meeting, 14 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 3 issues in Jupyter Notebook needed triage. After the meeting, none remains.
|
September 1, 2022
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, none remain.
|
September 8, 2022🇬🇧
Before the meeting, 3 issues in JupyterLab needed triage. After the meeting, none remain.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, 2 remain.
|
September 15, 2022
Before the meeting, 8 issues in JupyterLab needed triage. After the meeting, 5 remain.
Before the meeting, 3 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
|
September 22, 2022Thanks to @3coins for leading this meeting.
Before meeting, 10 issues in JupyterLab needed triage.
Before meeting, 2 issues in Notebook needed triage. After the meeting 1 remains.
|
September 29, 2022
Before the meeting, 18 issues in JupyterLab needed triage. After the meeting, 3 remain.
Before the meeting, 1 issue in Jupyter Notebook needed triage. After the meeting, 1 remains.
|
October 6, 2022
Before the meeting, 12 issues in JupyterLab needed triage. After the meeting, 4 remain.
Before the meeting, 1 issue in Jupyter Notebook needed triage. After the meeting, none remains.
|
October 13, 2022
Before the meeting, 9 issues in JupyterLab needed triage. After the meeting, 5 remain.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
|
October 20, 2022
Before the meeting, 11 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 4 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
|
November 3, 2022
Before the meeting, 12 issues in JupyterLab needed triage. After the meeting, none remain. "Answered" means that the issue has been accepted and tagged with
Before the meeting, 7 issues in Jupyter Notebook needed triage. After the meeting, 2 remain.
|
November 10, 2022🫡
Before the meeting, 14 issues in JupyterLab needed triage. After the meeting, none remain.
Before the meeting, 1 issue in Jupyter Notebook needed triage. After the meeting, none remain. |
November 17, 2022
Note: No triage meeting next week due to the US Thanksgiving holiday. Before the meeting, 6 issues in JupyterLab needed triage. After the meeting, none remain.
Before the meeting, 3 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
|
December 1, 2022
Before the meeting, 20 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 5 issues in Jupyter Notebook needed triage. After the meeting, 3 remain.
|
December 15, 2022No meeting next week due to Christmas
Before the meeting, 13 issues in JupyterLab needed triage. After the meeting, 4 remain.
Before the meeting, 3 issues in Jupyter Notebook needed triage. After the meeting, 0 remain. |
December 29, 2022
Before the meeting, 17 issues in JupyterLab needed triage. After the meeting, 4 remain.
Skipped notebook triage this week. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Jupyter Issue Triaging
Triage issues in jupyterlab and corresponding projects. A major goal at the moment is to triage the Jupyter Notebook background.
Meeting info: https://zoom.us/my/jovyan?pwd=c0JZTHlNdS9Sek9vdzR3aTJ4SzFTQT09
Previous notes: #137 (2022-01 through 2022-06)
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
Thursdays @ 10:00–11:00 AM PDT (17:00–18:00 UTC)
Meetings after November 6, 2022 were at 10:00 AM PST (18:00 UTC).
Primary focus:
The text was updated successfully, but these errors were encountered: