-
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
The future of the classic notebook interface #461
Comments
Please post your comments in jupyter/notebook#6210 and not here. Thanks for posting here Zach! I think we should try and keep the discussion in one place (the original issue, not here). Hence this comment. I think closing this issue would prevent comments but also reduce the visibility (which is the reason for this issue). Maybe let's keep this open for a while and then think about what to do. |
thanks @Zsailer for opening this! I edited your top comment to make that point a bit easier to notice :-) |
hey y'all, we're starting to converge on some concrete steps to get through this transition. the weekly notebook meetings are going to be repurposed to manage the release of notebook 7. we're going to manage these steps using a github project that we'll fill out over the next few weeks. https://github.com/orgs/jupyterlab/projects/2/ i've started new hackmd to keep track of our meetings https://hackmd.io/gl6x_SL0S_aYVn0Y0lSBpQ |
Thanks for this update Tony! I also opened up this in the repo2docker repo in case we want to follow-suit with mybinder jupyterhub/repo2docker#1095 |
we discussed moving notebook classic to the jupyterlab organization to make managing the sunrise process a little smoother. @Zsailer do we need to open a new issue entirely? |
is there an existing place for notebook classic meeting notes on the team compass or should i start a new thread? |
Yes the meeting notes are now being added to this issue: jupyter/notebook-team-compass#5 Looks like this issue can now be closed, since the JEP has been accepted and the fist 7.0 pre-release is out? |
Hey all - since that conversation has now completed and we have several other links and threads for more discussion, I'll close this one. Thanks @Zsailer for being inclusive and bringing the JupyterHub team's attention to these important conversations! |
Hey y'all, I'm opening this issue here to (hopefully) increase visibility on the discussion about the future of the classic notebook.
"The future of the classic notebook": jupyter/notebook#6210
If you have thoughts on this topic, please visit the above issue and leave comments
Let's try to centralize conversation there and avoid commenting here.
The text was updated successfully, but these errors were encountered: