-
Notifications
You must be signed in to change notification settings - Fork 5
Close old issues in the notebook repo #27
Comments
There is a huge volume of unclosed issues in the jupyter repo as well. Dedicated call might be a good idea. |
During todays Notebook call we discussed that dedicating part of the notebook call to this on a regular basis (~once a month) would be a good idea (mentioned by @afshin). It was also mentioned that it would be nice to get more involvement and participation from both old and new contributors; a good way to do that would be to somehow make triaging actions appear as github contributions and allow all call participants to make it (mentioned by @tonyfast). I myself think that a separate call for triaging old issues in both notebook and lab would be good, would be happy to host it. |
Did another pass at closing outdated accessibility issues that were for the classic notebook frontend: https://github.com/jupyter/notebook/issues?q=is%3Aissue+label%3Atag%3AAccessibility+is%3Aclosed Closing this issue as a follow-up to #32. But we should indeed still consider doing more rounds of closing issues, as there are still 1913 open issues as of February 21st 2024, and many of them likely don't apply to Notebook 7 anymore: Something to continue discussing on the Jupyter Frontends team compass, or during the Triage meeting: https://github.com/jupyterlab/team-compass Thanks all! |
As the Notebook 7 final release is approaching (jupyter/notebook#6307), many issues reported the past years in the notebook repo will either not be relevant anymore, or will be fixed by the new version.
I already spent some time closing a few of them today:
COPYING.md
toLICENSE
notebook#2768It would be great to continue this effort and lower the number of issues over time.
This could be done:
cc @jupyter/notebook-council for awareness
The text was updated successfully, but these errors were encountered: