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

Create new, empty repo to facilitate collaboration on the "notebook state" problem #52

Closed
Zsailer opened this issue Jun 16, 2023 · 12 comments
Labels
vote Voted on by the Jupyter Server Council

Comments

@Zsailer
Copy link
Member

Zsailer commented Jun 16, 2023

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?

@Zsailer Zsailer added the vote Voted on by the Jupyter Server Council label Jun 16, 2023
@Zsailer
Copy link
Member Author

Zsailer commented Jun 16, 2023

Pinging folks who've been involved in the conversations: @matthewwiese @skukhtichev and @parul100495

@Zsailer
Copy link
Member Author

Zsailer commented Jun 16, 2023

In the meantime, what should we call this repo if it gets created?

How about: jupyter-server/jupyter_message_replay ?

@matthewwiese
Copy link

@Zsailer jupyter-server/jupyter_message_replay is succinct enough for me!

@parul100495
Copy link

The name looks good to me as well.

@Zsailer
Copy link
Member Author

Zsailer commented Jun 23, 2023

Some other names that were discuss:

  • kernel-playback
  • message-recovery

@ivanov
Copy link

ivanov commented Jun 27, 2023

How about "serverside-notebook-state"? "message replay" is one possible solution, but not the only one.

@Zsailer
Copy link
Member Author

Zsailer commented Jul 6, 2023

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.

@Zsailer
Copy link
Member Author

Zsailer commented Jul 6, 2023

How about "serverside-notebook-state"? "message replay" is one possible solution, but not the only one.

@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.

@matthewwiese
Copy link

@Zsailer Could you add a placeholder README to the jupyter-server/message_replay repo? GitHub won't let me fork it and open a PR with the extension cookiecutter template because the repository is empty

@blink1073
Copy link
Contributor

Could you add a placeholder README to the jupyter-server/message_replay repo?

Done!

@Zsailer
Copy link
Member Author

Zsailer commented Jul 12, 2023

Thank you @blink1073!

@ivanov
Copy link

ivanov commented Jul 15, 2023

For anyone following along, here's the link: https://github.com/jupyter-server/message_replay

@Zsailer Zsailer closed this as completed Nov 8, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
vote Voted on by the Jupyter Server Council
Projects
None yet
Development

No branches or pull requests

5 participants