Description
Triage issues in JupyterLab and corresponding projects.
Meeting is typically held at 09:00 US Pacific time on Tuesdays.
Meeting info: https://zoom.us/j/95228013874?pwd=Ep7HIk8t9JP6VToxt1Wj4P7K5PshC0.1
Previous notes:
- Weekly Triage meetings: Jul–Dec 2024 #250 (2024-07 through 2024-12)
- Weekly Triage meetings: Jan–Jun 2024 #228 (2024-01 through 2024-06)
- Weekly Triage meetings: Jul–Dec 2023 #203 (2023-07 through 2023-12)
- Weekly Triage meetings: Jan-Jun 2023 #169 (2023-01 through 2023-06)
- Weekly Triage meetings: Jul-Dec 2022 #151 (2022-07 through 2022-12)
- Weekly Triage meetings: Feb-Jun 2022 #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
Triage Process
All requested information, where applicable, is provided. From the templates in JupyterLab’s issues:
For a bug:
- Description, preferably including screen shots
- Steps to reproduce
- Expected behavior
- Context, such as OS, browser, JupyterLab version, and output or log excerpts
For a feature request:
- Description of the problem
- Description of the proposed solution
- Additional context
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.
- Issues should be unique; triage is the best time to identify duplicates.
- Bugs represent valid expectations for use of Jupyter products and services.
- Expectations for security, performance, accessibility, and localization match generally-accepted norms in the community that uses Jupyter products.
- The issue represents work that one developer can commit to owning, even if they collaborate with other developers for feedback. Excessively large issues should be split into multiple issues, each triaged individually, or into team-compass issues to discuss more substantive changes.
- Read issues
- Tag issues
a. good first issue
b. bug
c. feature parity
d. Tag milestones - Identify duplicates
- Respond to issues
- Assign another person
Add milestone if you can achieve the goal.
Meetings
Primary focus: