This week I worked on introducing an early version of state saving in JupyterLab for plugins that need to persist page refreshing. Some of it is in master already, some more of it is still being developed.
We can try to put you in contact with GitHub see if they can do some internal query of their notebooks. We can also give you access to Google Analytics on Nbviewer, don't know if that would be helpful to find notebooks.
Matthias BReminder to try to make full sentences with all the informations you want to give, otherwise it is a daunting task to try to make a written summary on the mailing list. If writing the summary take more than 30min I won't send it. (Matthias)
Most of us were off for the past two weeks. We will be working in earnest on finishing state restoration (but not yet dock panel layout) and the Abstract Code Editor this week. We released version 0.12.1 over the break which has compatibility with Notebook 4.3.1.
All of the jupyter/docker-stacks images have been updated to include notebook 4.3 with token auth enabled by default.
There were a handful of PRs and issues submitted against nbviewer related to self-hosted instances (e.g., adding modification times to localfiles listing, fixing local notebook download from localfiles mode). There appears to be rising interest in getting more doc about running nbviewer on-premise.
General meetings Tuesdays at 9:00 am US Pacific (17:00 UTC during US winter)
Matthias BReminder to try to make full sentences with all the informations you want to give, otherwise it is a daunting task to try to make a written summary on the mailing list. If writing the summary take more than 30min I won't send it.
Project management (Jamie)
Brian has submitted materials to a trademark lawyer to pursue initial US based word and logo mark registration.
Working on updating and testing jupyterhub-deploy-teaching
Updating travis to cover Python 3.6
Review and fix jupyterhub doc build failure
Summary for Matthias: The JupyterHub team is working on compatibility fixes for DockerSpawner and 0.7. We're updating and testing ansible scripts for jupyterhub-deploy-teaching. With the recent release of Python 3.6, we will be updating Travis configurations.
There's a large, open PR on state management and application restoration on page refreshes that should be finished within a day or so. If you want to follow along, there's an overview of the restoration lifecycle in the PR description: jupyterlab/jupyterlab#1291
Demos at Gateways 2016, NYU, PlotCon and multiple other venues (fperez, jason). Very well received, lots of interest for potential collaborations. Special thanks to Matt Rocklin & Luke Canavan for great Dask demo.
Ongoing work on the embedding of widgets with formal json spec for widget state + sphinx extension. (Widget state can be fully generated from python backend now, which will enable pure-python sphinx extensions)
New approach: put a minus (-) next to your name if you would NOTlike to audibly share progress during the meeting. The moderator will start at the top of the Hackpad and call out those without a minus next to their name.
Would like us to discuss this technical topic all together during this meeting
We've never had *good* support for lists on the CLI, though you could cram them into list literals, e.g. `--Class.list_trait="['x', 'y']"`. This paves the way for proper list aliases, etc., but it will be hard to do without breaking the old, clunky way.
I think i volunteered indirectly to be the lab rat for this experiment last Friday. Once there's a bit more than the vanilla cookiecutter, I'd like to sit down and try to add something as simple as a ... button? menu item? ... and see how far I get. I probably could use what's there, but I'm sure I'd start struggling as soon as I wanted to do more than console.log.
Agreed. We should just make sure we look at it before we get close to a release. The principles of the design shouldn't be substantially different. Starting with LESS to get the ball rolling makes sense.
Also, I am trying to use very simple aspects of less that would be supported by basically any less preprocessor. The "API" aspects of our CSS are 1) class names (which won't change) and 2) the variable declarations (which will be a few dozen lines). But those things should be stable through major versions of JupyterLab