Skip to content
This repository has been archived by the owner on Oct 30, 2024. It is now read-only.

Long term maintenance plans #23

Open
betatim opened this issue Sep 25, 2019 · 3 comments
Open

Long term maintenance plans #23

betatim opened this issue Sep 25, 2019 · 3 comments

Comments

@betatim
Copy link
Collaborator

betatim commented Sep 25, 2019

@yuvipanda and @ryanlovett do you have a feeling for which of this repo or https://github.com/ryanlovett/jupyter-tree-download (or a new option like #19?) will be maintained for the long term?

We discussed making it easier for people to "resume their binder" at the meeting in Oslo and one simple way towards that goal is to make it easy to download your binder's contents and then upload it again later (more sophisticated ideas abound but this would be simple and take ~0 time to implement). So now wondering which extension we should use.

@ryanlovett
Copy link
Contributor

@betatim My feeling is that the backend functionality should be integrated into jupyter_server (what Min was suggesting, albeit with notebook). After that I think inertia would eventually land frontend support into notebook and lab. I don't really want to maintain the extensions long term though its not much effort.

@hadim
Copy link

hadim commented Oct 3, 2019

Hi all,

I didn't know this project was still active and I also needed this feature to JLab so at the end of July I started to develop a similar extension: https://github.com/hadim/jupyter-archive

It only supports JLab and also support more archive formats than ZIP.

My ultimate goal is to integrate it into Jupyter.

@hadim
Copy link

hadim commented Oct 3, 2019

See this jupyterlab-contrib/jupyter-archive#2

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants