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

move to jupyterlab #133

Merged
merged 5 commits into from
Mar 21, 2022
Merged

move to jupyterlab #133

merged 5 commits into from
Mar 21, 2022

Conversation

vivian-rook
Copy link
Collaborator

@vivian-rook vivian-rook commented Mar 7, 2022

Not sure if we would want to announce this some before sending it out. The interface would be, suddenly, different.
https://phabricator.wikimedia.org/T295043

@yuvipanda
Copy link
Collaborator

yuvipanda commented Mar 7, 2022

here's my suggested method for doing this:

  1. Set singleuser.defaultUrl in
    singleuser:
    to be /lab so the default UI is JupyterLab
  2. Install retrolab as well, primarily because it provides an interface switcher that lets you switch between classic notebook, retrolab and jupyterlab.
  3. Make an announcement that the default is what is being switched, and this won't affect what is available.

@yuvipanda
Copy link
Collaborator

There is still a lot of extensions and what not that work in classic notebook but don't have equivalents in jupyterlab, so keeping the classic around is helpful

@vivian-rook
Copy link
Collaborator Author

Seems reasonable. Not sure if we will need the redirect as it would appear the default default is /lab.

@chicocvenancio
Copy link
Member

Yeah, I think jupyterhub 2 changed the default, so by upgrading we're changing it.

Maybe we should write a small announcement and link to it from the banner?

@vivian-rook
Copy link
Collaborator Author

We could update the banner, though I would expect anyone already logged in would not see it, as, I believe, the banner page would be skipped at that point. Perhaps a message out to cloud-announce?

@chicocvenancio
Copy link
Member

The banner is visible on the server lauch page, so everyone should see it eventually. Not sure if currently running servers are restated?

But yeah, we should announce in cloud-announce and probably the tech newsletter as well.

@vivian-rook
Copy link
Collaborator Author

#135 for a potential banner update. Added a line to the newsletter about updating the interface (https://www.mediawiki.org/wiki/Technical_Community_Newsletter/2022/April) how long do we want to wait after sending to cloud-announce before merging this? Two weeks?

@vivian-rook
Copy link
Collaborator Author

Unless there are any objections, my plan is to merge #135
Send a note to cloud-announce linking to https://phabricator.wikimedia.org/T295043 and announcing that the update will go out on the 21st. And sending the same to tech news, such that the news should come out on the 14th giving a week for anyone to notice.

If this all sounds alright, if I could get an approval on this and #135 I'll get things in motion.

@vivian-rook vivian-rook merged commit cd6ee19 into master Mar 21, 2022
@vivian-rook vivian-rook deleted the T295043 branch May 20, 2022 20:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants