-
Notifications
You must be signed in to change notification settings - Fork 33
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
move to jupyterlab #133
Conversation
here's my suggested method for doing this:
|
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 |
Seems reasonable. Not sure if we will need the redirect as it would appear the default default is /lab. |
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? |
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? |
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. |
#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? |
Unless there are any objections, my plan is to merge #135 If this all sounds alright, if I could get an approval on this and #135 I'll get things in motion. |
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