Skip to content
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

Closed
JasonWeill opened this issue Feb 24, 2022 · 21 comments
Closed

Weekly Triage meetings: Feb-Jun 2022 #137

JasonWeill opened this issue Feb 24, 2022 · 21 comments
Labels
Dev Meeting Minutes Minutes from a dev meeting.

Comments

@JasonWeill
Copy link
Contributor

JasonWeill commented Feb 24, 2022

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:

  • 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.
  1. read issues
  2. tag issues
    a. good first issue
    b. bug
    c. feature parity
    d. tag milestones
  3. identify duplicates
  4. respond to issues
  5. assign another person

add milestone if you can acheive the goal

Meetings

Thursdays @ 10:00–12:00 AM PST (18:00–19:00 UTC)

Primary focus:

@JasonWeill JasonWeill added the Dev Meeting Minutes Minutes from a dev meeting. label Feb 24, 2022
@JasonWeill
Copy link
Contributor Author

JasonWeill commented Feb 24, 2022

February 3, 2022

Meeting started at 09:00 PST.

Attendees

name organization username
Jason Weill AWS @jweill-aws
Paul Ivanov Noteable @ivanov
Piyush Jain AWS @3coins
Zach Sailer Apple @Zsailer
Jeremy Tuloup QuantStack @jtpio
Fabio Pliger Anaconda @fpliger
tonyfast Quansight @tonyfast
A. T. Darian Two Sigma @afshin

Agenda

  • one triage example
  • breakout rooms for projects if more than xx folks

Triaged Issues

@JasonWeill
Copy link
Contributor Author

February 10, 2022

Attendees

name organization username
Tony Fast Quansight @tonyfast
Jason Weill AWS @jweill-aws
Zach Sailer Apple @Zsailer
Piyush Jain AWS @3coins

Agenda

Triaged Issues

In jupyter/notebook

In jupyterlab/jupyterlab:

@JasonWeill
Copy link
Contributor Author

February 17, 2022

Starting with this meeting, the start time was moved from 09:00 PST to 10:00 PST.

Attendees

name organization username
Jason Weill AWS @jweill-aws
Fabio Pliger Anaconda @fpliger
Piyush Jain AWS @3coins

Agenda

Triaged Issues

In jupyterlab:

jupyterlab/jupyterlab#11910
jupyterlab/jupyterlab#12018
jupyterlab/jupyterlab#12039
jupyterlab/jupyterlab#12070 (accepted)
jupyterlab/jupyterlab#12071 (duplicate)
jupyterlab/jupyterlab#12073 (accepted)
jupyterlab/jupyterlab#12079 (accepted)

In jupyter/notebook:
jupyter/notebook#534
jupyter/notebook#6284 (answered)
jupyter/notebook#6282 (accepted)
jupyter/notebook#6281 (need input from Steven S.)
jupyter/notebook#6277 (added comments on Discourse)
jupyter/notebook#6274 (referred to colab repo)

@JasonWeill
Copy link
Contributor Author

@JasonWeill
Copy link
Contributor Author

March 3, 2022

Attendees

name organization username
Jason Weill AWS @jweill-aws

Agenda

No 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 jupyterlab/jupyterlab:

@JasonWeill
Copy link
Contributor Author

March 10, 2022

Attendees

name organization username
Jason Weill AWS @jweill-aws
Jeremy Tuloup QuantStack @jtpio
Piyush Jain AWS @3coins
Michał Oxford @krassowski

Agenda

As 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 status:Needs Triage tag to new issues to Jupyter Notebook? Currently low volume (only 7 issues in the last month), but may increase as RetroLab is folded in.

Shortcut UI extension — sunset, move issues out

Jupyter Desktop — should we continue to accept issues? Triage process?

@JasonWeill
Copy link
Contributor Author

March 17, 2022

🍀

Attendees

name organization username
Jason Weill AWS @jweill-aws
Jeremy Tuloup QuantStack @jtpio
Piyush Jain AWS @3coins
Vidar T Fauske JP Morgan Chase @vidartf
Jessica Xu Jupyter community @jess-x
A. T. Darian Two Sigma @afshin

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.

@JasonWeill
Copy link
Contributor Author

@fcollonval fcollonval pinned this issue Mar 30, 2022
@fcollonval fcollonval changed the title Weekly Triage meetings Weekly Triage meetings: Feb - Jun 22 Mar 30, 2022
@fcollonval fcollonval changed the title Weekly Triage meetings: Feb - Jun 22 Weekly Triage meetings: Feb-Jun 2022 Mar 30, 2022
@fcollonval
Copy link
Member

I updated the title to align with the one of the JupyterLab meeting and pinned the issue to ease retrieval.

@JasonWeill
Copy link
Contributor Author

March 31, 2022

Attendees

name organization username
Jason Weill AWS @jweill-aws
Alex Bozarth IBM @ajbozarth
Michał Krassowski Oxford @krassowski
Martha Cryan IBM @marthacryan
Piyush Jain AWS @3coins

Agenda

10 issues in Needs Triage for jupyterlab. After triaging, 2 remain in needs triage.

Triaged issues in jupyterlab:

Triaged issues in jupyterlab-desktop. Items moved to jupyterlab have been cleared of the "Needs Triage" label.

@JasonWeill
Copy link
Contributor Author

April 7, 2022

Attendees

name organization username
Jason Weill AWS @jweill-aws
Jeremy Tuloup QuantStack @jtpio
Alex Bozarth IBM @ajbozarth

Agenda

11 issues in Needs Triage for jupyterlab. After triaging, 2 remain in needs triage.

Issues triaged

jupyterlab

jupyterlab-desktop

@JasonWeill
Copy link
Contributor Author

April 21, 2022

Attendees

Name Organization Username
Jason Weill AWS @jweill-aws
Afshin T. Darian QuantStack @afshin

Agenda

14 issues in Needs Triage for jupyterlab. After triaging, 1 remains in Needs Triage.

Issues triaged

jupyterlab

@JasonWeill
Copy link
Contributor Author

May 12, 2022

Attendees

Name Organization Username
Jason Weill AWS @jweill-aws
A. T. Darian QuantStack @afshin
Rosio Reyes Anaconda @RRosio
Jessica Xu n/a @jess-x

Agenda

18 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

jupyterlab

jupyterlab-desktop

@JasonWeill
Copy link
Contributor Author

May 19, 2022

Attendees

Name Organization Username
Jason Weill AWS @jweill-aws
Afshin T. Darian QuantStack @afshin

Agenda

11 issues in Needs Triage for jupyterlab. After triaging, 1 of these remains in Needs Triage.

We also looked at a few issues tagged with status:Needs Discussion, closing two.

Issues triaged

jupyterlab

@JasonWeill
Copy link
Contributor Author

May 26, 2022

Attendees

Name Organization Username
Jason Weill AWS @jweill-aws
A. T. Darian QuantStack @afshin
Piyush Jain AWS @3coins
Rosio Reyes Anaconda @RRosio

Agenda

9 issues in Needs Triage for jupyterlab. After triaging, 1 of these remains in Needs Triage.

We also looked at the oldest issues tagged with status:Needs Discussion, closing 5. We closed 3 newer issues as duplicates of accepted issues that had status:Needs Discussion tags.

"Accepted" means that the label listed below has been removed because we no longer consider it necessary.

Issues triaged

jupyterlab (status:Needs Triage label)

jupyterlab (status:Needs Discussion label)

@JasonWeill
Copy link
Contributor Author

@JasonWeill
Copy link
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dev Meeting Minutes Minutes from a dev meeting.
Projects
None yet
Development

No branches or pull requests

3 participants