On Tue, Oct 25, 2016 at 8:03 AM MinRK <[email protected]> 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/CAPDWZHwBmh-zQ%3D-STKEk%2Bvfox_UgFoebsrQHhv89rWKZnc8R3g%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
