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.
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
Proposal: Emulate what a desktop editor would do: aggressively save to a temporary file that can be recovered, and have a setting for an auto save interval to disk. "Checkpointing" should be done using version control. We should also periodically check for a file change on disk and ask to revert.
Documentation while I am gone: I will have the Cal Poly Developers monitor this site http://www.iheartjupyterdocs.org/for any doc build failures. I will ask them to file an issue if there is a broken build and ask the Jupyter team to rally as needed. Thanks!
Will attend JupyterDays Atlanta
Shout outs: Reese Netro for excellent work capturing notes and comments from JupyterHub conference on Friday. Ana for speaker mentoring and SciPy organization. Matthias Bussonnier for help with CPython issue tracker comments.