You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After some discussion in jupyter-server/jupyter_server#752, I'd like to move this logic into its own extension and repository under this organization. Much like the "terminals" extension, I don't think this belongs in the core APIs, but makes a nice addition to Jupyter servers that serve remote kernels.
Moving it into its own repository allows us to more easily collaborate on this extension during the early experimental phases.
Before creating the repo in this org, I'd like to check for consensus from @jupyter-server/active-team-members. Creating new repos always presents the risk of additional maintenance burden.
Any objections?
The text was updated successfully, but these errors were encountered:
Sounds good. Will we make a recommendation to JupyterLab and Jupyter Notebook to ship with this extension by default or will we just leave it up to those projects to decide?
Hi all,
After some discussion in jupyter-server/jupyter_server#752, I'd like to move this logic into its own extension and repository under this organization. Much like the "terminals" extension, I don't think this belongs in the core APIs, but makes a nice addition to Jupyter servers that serve remote kernels.
Moving it into its own repository allows us to more easily collaborate on this extension during the early experimental phases.
Before creating the repo in this org, I'd like to check for consensus from @jupyter-server/active-team-members. Creating new repos always presents the risk of additional maintenance burden.
Any objections?
The text was updated successfully, but these errors were encountered: