Close old issues in the notebook repo

[jtpio]

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:

• List of running notebooks should indicate the kernel type notebook#395
• Search and Replace issues notebook#558
• feature request: minimap for longer notebooks notebook#594
• Does notebook have the function of navigation in a sidebar ? notebook#672
• Consider internationalizing all UI strings notebook#870
• Review docs on troubleshooting and correcting a stale JS build notebook#872
• Any plan for including a CSV file viewer such as Calc? notebook#921
• Is it possible to add this extension into notebook? notebook#1228
• Better debugging support.  notebook#1246
• Menus below buttons in notebook notebook#1381
• Getting started contributing documentation notebook#1754
• Add nbextension/serverextension commands for uninstall/disable all notebook#2149
• Document the IPython.notebook.kernel.execute function notebook#2219
• Add the Ability to Remove Some Toolbar Buttons notebook#2294
• Issue Creating New Notebooks in IE only notebook#2594
• Getting Error as :Module not Found while running import teradata in jyputer notebook notebook#2569
• Can not use tensorflow in jupyter notebook notebook#2712
• COPYING.md to LICENSE notebook#2768
• Improve Documentation for Building Documenation notebook#2809
• Should "Save with Widgets" be a checkbox? notebook#2735
• Allow tabs / windows notebook#2758
• Feature request: Markdown preview on the side notebook#2882
• Add handlers for common file types notebook#2765
• Feature: Add SFTP tab in Jupyter notebook#2762
• [Feature Request] Dialog window when choosing action. notebook#2795
• Latex Rendering Problem notebook#2807
• Using python entrypoints for notebook server extensions? notebook#2894
• Create notebook without kernel only for markdown editing notebook#2908
• Switch to puppeteer for regression tests notebook#2891
• Katex for mathjax notebook#3094
• Set up a system for contributing translations notebook#3103
• TensorFlow1.5.0 absl.flags._exceptions.UnparsedFlagAccessError in Jupyter Notebook notebook#3327
• I want to acces notebook on port 80 not on 8888 notebook#3416
• Create narrative, user-focused documentation about the nbextension system notebook#3445
• can't install jupyter notebook#3609
• my jupyter notebook always show kernel busy and this is error  notebook#3612
• Windows test failures notebook#1626
• Display a table of content based on markdown sections notebook#1498
• Add how to print version / environment data to the contribution guideline notebook#3198
• da notebook#3717
• when session killed from other tab, notebook UI doesn't reflect change notebook#3178
• Integrate building translation files notebook#3102
• add persistence language setting in web ui notebook#5712
• [feature request] Shutdown all running kernels in one click notebook#4421

It would be great to continue this effort and lower the number of issues over time.

This could be done:

• as part of the regular triage meeting
• at the end of the regular notebook weekly meeting
• during a dedicated call
• asynchronously by anyone who would like to take some time to review old issues

cc @jupyter/notebook-council for awareness

[andrii-i]

There is a huge volume of unclosed issues in the jupyter repo as well. Dedicated call might be a good idea.

[andrii-i]

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.

[jtpio]

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!