-
-
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: Feb-Jun 2022 #137
Comments
February 3, 2022Meeting started at 09:00 PST. Attendees
Agenda
Triaged Issues
|
February 17, 2022Starting with this meeting, the start time was moved from 09:00 PST to 10:00 PST. Attendees
Agenda
Triaged IssuesIn jupyterlab/jupyterlab#11910 In |
February 24, 2022Attendees
AgendaTriaged issues: In
In |
March 3, 2022Attendees
AgendaNo attendees this week; I decided to do triage ad hoc As of meeting start, there are 18 open issues in JupyterLab that need triage. Triaged issues: In
|
March 10, 2022Attendees
AgendaAs of meeting start, there are 15 open issues in JupyterLab that need triage. Issues triaged in JupyterLab:
Currently 43 issues in RetroLab, most over a week old. Move over to jupyter/notebook as part of the Jupyter Notebook 7 transition from RetroLab?
Should we start applying the Shortcut UI extension — sunset, move issues out Jupyter Desktop — should we continue to accept issues? Triage process? |
March 17, 2022🍀 Attendees
As of meeting start, there are 11 open issues in JupyterLab that need triage. Issues triaged in JupyterLab:
Still no "new" option to create an issue in Notebook — jupyter/notebook-team-compass#7 — so there are no new Notebook issues. Move RetroLab issues into Notebook repo? To discuss next week at Notebook meeting. |
March 24, 2022Attendees
AgendaAs of meeting start, there are 13 open issues in JupyterLab that need triage. Issues triaged:
As of the end of the meeting, there are no open issues in JupyterLab that need triage. 👏 |
I updated the title to align with the one of the JupyterLab meeting and pinned the issue to ease retrieval. |
March 31, 2022Attendees
Agenda10 issues in Needs Triage for jupyterlab. After triaging, 2 remain in needs triage. Triaged issues in
Triaged issues in
|
April 7, 2022Attendees
Agenda11 issues in Needs Triage for jupyterlab. After triaging, 2 remain in needs triage. Issues triaged
|
April 14, 2022Attendees
Agenda10 issues in Needs Triage for jupyterlab. After triaging, 2 remain in Needs Triage. Issues triaged
|
April 21, 2022Attendees
Agenda14 issues in Needs Triage for jupyterlab. After triaging, 1 remains in Needs Triage. Issues triaged
|
May 5, 2022Attendees
Agenda13 issues in Needs Triage for jupyterlab. After triaging, 5 remain in Needs Triage. Issues triaged
|
May 12, 2022Attendees
Agenda18 issues in Needs Triage for jupyterlab. After triaging, 2 of these remain in Needs Triage. New comment on jupyterlab-desktop#436: jupyterlab/jupyterlab-desktop#436 (comment) Issues triaged
|
May 19, 2022Attendees
Agenda11 issues in Needs Triage for jupyterlab. After triaging, 1 of these remains in Needs Triage. We also looked at a few issues tagged with Issues triaged
|
May 26, 2022Attendees
Agenda9 issues in Needs Triage for jupyterlab. After triaging, 1 of these remains in Needs Triage. We also looked at the oldest issues tagged with "Accepted" means that the label listed below has been removed because we no longer consider it necessary. Issues triaged
|
June 2, 2022Attendees
Agenda9 issues in Needs Triage for jupyterlab. After triaging, 1 of these remains in Needs Triage. Issues Triaged
|
June 9, 2022Attendees
Agenda14 issues in Needs Triage for jupyterlab. After triaging, 3 of these remain in Needs Triage. Issues Triaged
|
June 16, 2022Attendees
Agenda14 issues in Needs Triage for jupyterlab. After triaging, 3 of these remain in Needs Triage. Issues Triaged
|
June 23, 2022
Agenda7 issues in Needs Triage for jupyterlab. After triaging, 4 of these remain in Needs Triage. Issues Triaged
|
This issue contains weekly bug triage meetings, scheduled for either 09:00 PST or 10:00 PST on Thursdays.
HackMD notes: https://hackmd.io/HaQ3S_nPSbqaRtk9rj59iA
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
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 acheive the goal
Meetings
Thursdays @ 10:00–12:00 AM PST (18:00–19:00 UTC)
Primary focus:
The text was updated successfully, but these errors were encountered: