-
Notifications
You must be signed in to change notification settings - Fork 14
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
Archive this repository #60
Conversation
@@ -1,3 +1,5 @@ | |||
:warning: **This repository is now archived as the feature is directly available when installing [`jupyter-collaboration`](https://github.com/jupyterlab/jupyter_collaboration)** |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the repo was renamed to use a -
instead of _
:
:warning: **This repository is now archived as the feature is directly available when installing [`jupyter-collaboration`](https://github.com/jupyterlab/jupyter_collaboration)** | |
:warning: **This repository is now archived as the feature is directly available when installing [`jupyter-collaboration`](https://github.com/jupyterlab/jupyter-collaboration)** |
Thanks @fcollonval. Pinging @yuvipanda and @minrk who also contributed to this repo, to make sure archiving it is fine with them too. |
Does jupyter-collaboration address #54? jupyter-collaboration also explicitly recommends installing this extension in its docs. And does it still work to use collaboration to generate links with tokens when RTC is unavailable? If not, it doesn't really seem to replace this extension at all. |
The dialog has a checkbox that you introduced to include or not the token. But I guess there is still the need to add a server settings for admin to control that behavior.
Thanks I opened a PR to remove it
This indeed is a good point for not archiving the repository. |
Closing this as per the discussion conclusion. |
No description provided.