-
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
Create new, empty repo to facilitate collaboration on the "notebook state" problem #52
Comments
Pinging folks who've been involved in the conversations: @matthewwiese @skukhtichev and @parul100495 |
How about: jupyter-server/jupyter_message_replay ? |
@Zsailer |
The name looks good to me as well. |
Some other names that were discuss:
|
How about "serverside-notebook-state"? "message replay" is one possible solution, but not the only one. |
The Server Team voted in favor of creating a new repo for this work 🚀! (8 Yes, 7 Abstain). Let's create the repo during the meeting. |
@ivanov true. The problem is a bit broader than the notebook too—e.g. kernel state (say for a console, not a notebook document) needs restoration too. |
@Zsailer Could you add a placeholder README to the |
Done! |
Thank you @blink1073! |
For anyone following along, here's the link: https://github.com/jupyter-server/message_replay |
Hi folks,
In yesterday's server meeting, I proposed creating a new repo to explore solutions to the issue raised here: Proposal: Restore Notebook execution progress when a browser page is reload
We've seen a lot of interest on this issue from people representing different organizations. I'd like to focus this energy to a single place on Github so we can easily collaborate. This work will likely be larger than a single PR and require some explorative work. For that reason, I'd like to focus this work in a separate repo.
I'll open a vote in our private council repo. @jupyter-server/jupyter-server-council
In the meantime, what should we call this repo if it gets created?
The text was updated successfully, but these errors were encountered: