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

Jupyter Server Roadmap #2

Closed
11 of 21 tasks
Zsailer opened this issue Oct 24, 2019 · 7 comments
Closed
11 of 21 tasks

Jupyter Server Roadmap #2

Zsailer opened this issue Oct 24, 2019 · 7 comments

Comments

@Zsailer
Copy link
Member

Zsailer commented Oct 24, 2019

In today's call, we put together a technical roadmap for the Jupyter Server. Here's a place to discuss the plan.


  • Release nbclassic
    • a notebook ExtensionApp (from jupyter_server).
    • pulls Notebook JS and templates from notebook.
    • execute from command line with jupyter nbclassic
    • migrates configuration to jupyter_server_config.
    • shim notebook vs. server traits.
  • Setup Jupyter Server's Testing Framework
    • Port old tests to pytest.
    • Move to Github actions
      back to old way.
  • Update Jupyter Server JEP to reflect new nbclassic.
  • Transition other frontends:
    • JupyterLab to Jupyter Server, dropping notebook as a dependency.
    • voila to Jupyter Server
    • Uses nbclassic to run multiple frontends side-by-side.
  • Notebook 7.x: transition jupyter/notebook to Jupyter Server
    • drop the old notebook server
    • NotebookApp becomes
    • shim the notebook server API to jupyter_server
    • raise DeprecationWarnings in shimmed APIs.
    • release notebook 7.x
  • Notebook 8.x: drop shims.
@Zsailer
Copy link
Member Author

Zsailer commented Oct 24, 2019

Just moved Zsailer/notebook_shim to Zsailer/nbclassic.

NBClassic is a thin package that provides the classic Jupyter Notebook frontend on top of Jupyter Server. You can install NBClassic side-by-side with notebook. NBClassic uses the Javascript and templates from notebook, but runs on the Jupyter Server's tornado server (not the notebook's native tornado server).

You can install nbclassic from PyPI today.

pip install jupyter_server nbclassic notebook

You can try the nbclassic frontend by running jupyter server or jupyter nbclassic and going to localhost:<port>/tree?token=...

@willingc willingc pinned this issue Oct 24, 2019
@willingc
Copy link

@Zsailer I've gone ahead and pinned this issue for visibility. Thanks for putting it together!

@Zsailer
Copy link
Member Author

Zsailer commented Oct 24, 2019

Thanks, @willingc!

@echarles
Copy link
Member

didn't know about the pinned feature, learning every day here...

Good to have more visibility here but further actions could be needed in downstream projects that are using notebook or are/will be using server. This is especially true for the kernel_mgmt - nbclassic should have 0 impact I believe.

@echarles
Copy link
Member

@Zsailer Zsailer transferred this issue from jupyter-server/jupyter_server Nov 19, 2020
@Zsailer Zsailer pinned this issue Nov 19, 2020
@Zsailer
Copy link
Member Author

Zsailer commented Dec 9, 2021

Closing this issue, as this roadmap is very out-of-date. We'll work on developing a new roadmap in the new year, once a Jupyter Server Team is established.

@Zsailer Zsailer closed this as completed Dec 9, 2021
@Zsailer Zsailer unpinned this issue Dec 9, 2021
@saiwing-yeung
Copy link

Where will the new roadmap be communicated?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants