Hi Everyone, I put the jupyter server on the back burner as I had major presentations at strata, the european commission and a couple of other things to prepare. Although I will put some cycles into this thing starting tomorrow.
One of the main motivation for the split was to be able to start from a clean state in terms of the mechanism that we will put in place wrt the extension mechanism. I am fine rebasing my work on the top of the latest features of the notebook wrt token authentication etc. I agree that they are part of the general jupyter server side. In fact, I am not too worried about work done on the notebook repo that would need to be repeated in the jupyter server repo. The reason is that most of the issues open in the notebook repo are related to the notebook front ende. (The token authentication thing that was merged recently is a bit of an outlier). The resulting repository is actually very small, and should be, hopefully, simpler to maintain. Sylvain On Tuesday, October 25, 2016 at 3:26:03 PM UTC+2, Jason Grout wrote: > > > On Tue, Oct 25, 2016 at 8:03 AM MinRK <[email protected] <javascript:>> > wrote: > >> >> This sounds like a good plan to me, and I'm happy with Brian, Jason and >> Matthias. The main question for me (at least in terms of where I spend my >> time) is the notebook server vs split-off jupyter-server project. I've been >> implementing some long-awaited new things in the notebook server (login >> tokens, activity tracking), but much further development in that repo is >> going to be a pain for the new server to keep in sync with. I would like to >> have a plan for how/when to stop development on the server-side of the >> notebook application, which is still providing the server-side component of >> JupyterLab. I would like to participate in that side of the conversation, >> and I imagine Sylvain would, as well. >> >> > Good question. Sylvain has worked quite a bit on this on > https://github.com/jupyter/jupyter_server/pull/1. Sylvain, what is the > status? I know you've been tackling the problem of the extension mechanism > - should we push forward (i.e., have discussion/implementation) of the > extension mechanism at the dev meeting in two weeks? > > Thanks, > > Jason > > -- You received this message because you are subscribed to the Google Groups "Project Jupyter" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/jupyter/337c5e24-93be-4808-911f-173bb048e856%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
