-
Notifications
You must be signed in to change notification settings - Fork 8
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
Move jupyter/nb2kg to jupyter_server and archive repo #42
Comments
I think if we're just going to archive it we should leave it in the |
That makes sense. |
Per today's Jupyter Server/Kernels team meeting we felt (within the meeting) that archiving jupyter/nb2kg in-place is probably the best step moving forward (in line with @blink1073's suggestion). I've been asked to poll @jupyter-server/jupyter-server-council regarding the repository's archival. In the meantime, I've commented on an existing issue in the nb2kg repo (which is 2+ years old) indicating the (new) desire to archive the repository. PollingPolling is open to all members of the Jupyter Server Council. Anyone is free to comment. Using the built-in emojis, please indicate approval to archive the nb2kg repository within the jupyter organization using 👍 and its disapproval using 👎. If you'd like to further discuss its future, please feel free to comment separately. Thank you. |
Sorry, this should have been closed with the previous comment. |
The
jupyter/nb2kg
repository houses the NB2KG server extension used to configure a Notebook server to communicate with a Gateway server (running either Jupyter Kernel Gateway or Jupyter Enterprise Gateway). This server extension has been obsolete since its functionality was introduced into thegateway
package of Notebook versions >= 6.0 and all Jupyter Server versions.I would like to propose two changes relative to this repository:
nb2kg
repository in that same organization and propose it be moved intojupyter_server/nb2kg
.6.4.12
, where it should not be used anyway, I think it best that the repository be archived.I will hold off on any changes until we've decided if zero, one, or both of these changes should be made.
The text was updated successfully, but these errors were encountered: