Open JasonWeill opened 4 months ago
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Before the meeting, 11 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 8 issues in Notebook needed triage. After the meeting, 4 remain.
No issues in JupyterLab Desktop or Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
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.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Michał Krassowski | QuanSight | @krassowski |
Rosio Reyes | Anaconda | @RRosio |
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.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Michał Krassowski | QuanSight | @krassowski |
Rosio Reyes | Anaconda | @RRosio |
Matthew Simpson |
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.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Michał Krassowski | QuanSight | @krassowski |
Rosio Reyes | Anaconda | @RRosio |
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.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Michał Krassowski | QuanSight | @krassowski |
Rosio Reyes | Anaconda | @RRosio |
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.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Andrii Ieroshenko | AWS | @andrii-i |
Rosio Reyes | Anaconda | @RRosio |
Michał Krassowski | QuanSight | @krassowski |
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.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Michał Krassowski | QuanSight | @krassowski |
Before the meeting, 11 issues in JupyterLab needed triage. After the meeting, none remain.
Before the meeting, 7 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
Before the meeting, 1 issue in JupyterLab Desktop needed triage. After the meeting, 1 remains.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Michał Krassowski | QuanSight | @krassowski |
Rosio Reyes | Anaconda | @RRosio |
Before the meeting, 7 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 3 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
Before the meeting, 5 issues in JupyterLab Desktop needed triage. After the meeting, 4 remain.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Before the meeting, 7 issues in JupyterLab needed triage. After the meeting, none remain.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
Before the meeting, 2 issues in JupyterLab Desktop needed triage. After the meeting, none remain.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Michał Krassowski | QuanSight | @krassowski |
Before the meeting, 13 issues in JupyterLab needed triage. After the meeting, 3 remain.
Before the meeting, 5 issues in Jupyter Notebook needed triage. After the meeting, 2 remain.
No issues in JupyterLab Desktop or Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Rosio Reyes | Anaconda | @RRosio |
Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, 4 remain.
Before the meeting, 4 issues in Jupyter Notebook needed triage. After the meeting, 0 remain.
Before the meeting, 1 issue in JupyterLab Desktop needed triage. After the meeting, 0 remain.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Michał Krassowski | QuanSight | @krassowski |
Before the meeting, 16 issues in JupyterLab needed triage. After the meeting, 3 remain.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
Before the meeting, 4 issues in JupyterLab Desktop needed triage. After the meeting, 2 remain.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Michał Krassowski | QuanSight | @krassowski |
Before the meeting, 7 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, 2 remain.
Before the meeting, 2 issues in JupyterLab Desktop needed triage. After the meeting, none remain.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Before the meeting, 7 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 3 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
Before the meeting, 1 issue in JupyterLab Desktop needed triage. After the meeting, none remain.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, 2 remain.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, none remain.
No issues in JupyterLab Desktop needed triage.
Before the meeting, 2 issues in Classic Notebook (nbclassic) needed triage. After the meeting, none remain.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Michał Krassowski | QuanSight | @krassowski |
Before the meeting, 10 issues in JupyterLab needed triage. After the meeting, 4 remain.
Before the meeting, 2 issues in Jupyter Notebook needed triage. After the meeting, 1 remains.
No issues in JupyterLab Desktop or Classic Notebook (nbclassic) needed triage.
@JasonWeill Will the following issue be fixed for 4.3?
FYI @practicusai
@benz0li 4.3.0 is now in a release candidate state, so any pull request that you open to fix https://github.com/jupyterlab/jupyterlab/issues/16489 would likely be considered for a point release or for 4.4.0. We would prefer to receive a pull request rather than a ping for updates. Thanks for your interest!
We would prefer to receive a pull request rather than a ping for updates.
To be honest: The repeated arguments and constant rejections have already cost me too much energy. See also
I have nothing more to add.
Thanks to everyone @jupyterlab for all the hard work you put into JupyterLab.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Michał Krassowski | QuanSight | @krassowski |
Nisha Nair | IBM | @nkn2022 |
Maduabuchi | @Maduflavins |
Before the meeting, 12 issues in JupyterLab needed triage. After the meeting, 1 remains.
Before the meeting, 8 issues in Jupyter Notebook needed triage. After the meeting, none remain.
No issues in JupyterLab Desktop or Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Michał Krassowski | QuanSight | @krassowski |
Before the meeting, 8 issues in JupyterLab needed triage. After the meeting, none remain.
Before the meeting, 4 issues in Jupyter Notebook needed triage. After the meeting, 2 remain.
Before the meeting, 1 issue in JupyterLab Desktop needed triage. After the meeting, 1 remains.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Jason Weill | AWS | @JasonWeill |
Rosio Reyes | Anaconda | @RRosio |
Before the meeting, 12 issues in JupyterLab needed triage. After the meeting, 3 remain.
Before the meeting, 4 issues in Jupyter Notebook needed triage. After the meeting, 2 remain.
Before the meeting, 1 issue in JupyterLab Desktop needed triage. After the meeting, 1 remains.
No issues in Classic Notebook (nbclassic) needed triage.
Name | Organization | Username |
---|---|---|
Piyush Jain | AWS | @3coins |
Andrii Ieroshekno | AWS | @andrii-i |
Rosio Reyes | Anaconda | @RRosio |
Before meeting, 7 issues in JupyterLab. After meeting, 4 remain.
Before meeting, 5 issues in Notebook. After meeting, 3 remain.
Before meeting, 1 issue in JupyterLab-Desktop. After meeting, none remain.
No issues in Classic Notebook (nbclassic) needed 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.
Add milestone if you can achieve the goal.
Meetings
Primary focus: