JupyterLab Weekly Meeting Minutes - Archive Oct 19 - June 2020

# JupyterLab Weekly Meeting Minutes - Archive Oct 19 - June 2020 09 October 2019 - 24 June 2020 ### Future Meeting Note https://hackmd.io/Y7fBMQPSQ1C08SDGI-fwtg ### Archive July - Oct 2020 https://hackmd.io/P1Y_TM2WSxOENvQzWVsnvw?view ### 24 June 2020 Weekly Meeting - Brian (can I go first, have another meeting to jump to) - RTC project management - Update on document mode - 1st PR merged - URL refactor underway - What about an IndexedDB based datastore ServerAdapter for workspaces? - Darian - Workspace question related to Brian's update: treating workspaces as files for users to m - Tim - Can somebody tweet this? Trying to do some more research for the File System re-design. - Have opinions on JupyterLab's file browser experience? Give us your gut reactions on this first-click test: https://ows.io/cm/b44013lp - Done: https://twitter.com/ProjectJupyter/status/1275825424271052803 - Max - How are we currently publishing our API docs? - https://jupyterlab.github.io/jupyterlab/ - Manual process (Steven and Jason have both done it) - improved api docs - https://github.com/jupyterlab/jupyterlab/pull/8320 - auth handling for jupyter-fs - https://github.com/jpmorganchase/jupyter-fs/pull/41 - Saul - Made some movement on the development process formalization - https://github.com/jupyterlab/team-compass/pull/54 - Had some calls with folks from RTC, If you wanna hear about it come to the meeting next monday! - https://hackmd.io/UbnBH58hS8itoWgfiWT77A - Martha - Update ToC extension to use signal instead of settings registry - https://github.com/jupyterlab/jupyterlab/pull/8601 - Eric - [Slow Terminating Kernels](https://github.com/jupyterlab/jupyterlab/pull/8562): Any remaining question? Otherwise ready to merge for 2.2. release. - Working on a draft PR for [File Browser Search](https://github.com/jupyterlab/jupyterlab/issues/8157) - Athan - What is the current status of toast notifications in JLab? - https://github.com/jupyterlab/jupyterlab/pull/6389 - Can be done in userland (e.g., https://github.com/jupyterlab/jupyterlab-git/pull/630), but would like some resolution on direction: core or userland? - Jason - [Extension system refactor (and proof of concept demo using webpack module federation)](https://github.com/jupyterlab/jupyterlab/pull/8385). Next priority is getting some changes into Webpack to support our usecases, like prerelease versions and support for `||` clauses in required versions of shared modules. More at the [webpack issue](https://github.com/webpack/webpack/issues/11073) and a corresponding [webpack draft PR](https://github.com/webpack/webpack/pull/11079) - Additional discussion - 3.0 release prioritization - 3.0 triage session tomorrow or Friday? - 2.2 release triage - https://github.com/jupyterlab/jupyterlab/issues/8585 - Development Process - JS version bumping procedure: https://github.com/jupyterlab/team-compass/pull/54#issuecomment-648898095 - Changelog proposal! https://github.com/jupyterlab/team-compass/pull/54#discussion_r445004481 - ### 17 June 2020 Weekly Meeting - Mehmet: present Galata (JupyterLab UI Testing Framework) - Eric - JupyterLab Server as Server Extension [jupyterlab/79](https://github.com/jupyterlab/jupyterlab_server/pull/79) and [jupyterlab-server/7416](https://github.com/jupyterlab/jupyterlab/pull/7416) updated and green - Depends on a few jupyter_server PR/issues ([Confusion between extension_name and module name](https://github.com/jupyter/jupyter_server/issues/222), [Existing Classical Server Extension Support](https://github.com/jupyter/jupyter_server/issues/243)...) - [Race Condition with Slow Restarting Kernels](https://github.com/jupyterlab/jupyterlab/issues/8477): Opened PR [jupyterlab/8562](https://github.com/jupyterlab/jupyterlab/pull/8562) which adds `terminating` state in the Kernel Status Indicator (with new method on `ISessionContext`) and blocks cell run if Kernel is terminating - Will update PR with cell run queuing with toast in a second iteration. - Saul - Future of [JupyterLab Vim](https://github.com/jwkvam/jupyterlab-vim) - JupyterLab already has Vim key bindings for text editing, this extends it to allow command mode in the notebook - Huge number of stars and users! - Current version unmaintained, fork is updated for most recent jlab https://github.com/axelfahy/jupyterlab-vim - We have a client who uses this - Currently uses some hacks: https://github.com/axelfahy/jupyterlab-vim/blob/c4e43f940ef4be4c961608b6192412d2f3a33d1f/src/index.ts#L61 - Going to look into either bringing into core or adding hooks in core to make less hacky - Any thoughts from others on whether I should explore moving this into core? - Conclusions: - We don't wanna move this into core - There is support for making it less hacky, by exposing ways to override codemirror more easily - Athan - JupyterLab ToC context menus: https://github.com/jupyterlab/jupyterlab-toc/pull/141 - Tim - Cal Poly interns started this week. Expect to see them in here from time to time. - Snippets UI - Tabular Data editor - JupyterLab Viola Extension (customizeable dashboards) - Jason - Extension system refactor - Brian - Canceling meetings on Juneteenth 6/19 to reflect on systemic racism and injustice. - Aiming to get an improved document oriented UX into JLab for 3.0. - https://github.com/jupyterlab/jupyterlab/issues/8567 - Starting to work on task breakdown for overall RTC work - Additional Discussion - Minor release still feasible? - Release timeline for 3.0 - Priorities for 3.0 - Triage for 3.0 - [Dropping python 3.5 and 3.6 support](https://github.com/jupyterlab/jupyterlab/issues/8577) ### 10 June 2020 Weekly Meeting #ShutDownSTEM edition. - Why we're doing this. - If you get a chance, please read over this before the meeting: https://www.shutdownstem.com/ - Suggestions from https://www.shutdownstem.com/ - **Education**: If this is new to you, start reading the [resource materials](https://www.shutdownstem.com/resources); these exist and you need to learn from them. Keep learning by reading books and blogs, watching movies, listening to podcast and following the suggested people on social media. - **Action**: Take responsibility to be [actively anti-racist](https://www.shutdownstem.com/action) in your spaces of influence. You need to change how things are done and support organization that are continuing this work. - **Healing**: Racism creates this toxic space and [those affected need to heal from it](https://www.shutdownstem.com/healing). We need to make time and space for this emotional work to occur. - What is JupyterLab's role in all this? - What actionable steps can we make as a team? - All take a book from the [beginners](https://www.shutdownstem.com/beginners) list and present a summary of what we learned - Steve has "How to Be an Antiracist" on audio - All take an episode from one of the recommended podcasts and present what we learned - Consider attending a course like [Introduction to Being an Antiracist](https://ti.to/kim.crayton.llc/introduction-to-being-an-antiracist/en) (Steve has already signed up - email at steven.silvester at gmail dot com or [Atlanta @ devopsdays.org](https://twitter.com/devopsdaysATL/status/1270665954968719360?s=20) if you need your cost covered) - Encourage our employers to sponsor events like [DISC](https://blog.jupyter.org/highlights-from-the-2018-nyc-disc-sprint-ac4cf34b1566) or provide travel so we can attend - What is the impact of JupyterLab software on these systems? - Can we move that impact in any positive way? - Are there any pitfalls to be aware of? - Are there any things we can take back to our employers? - Adding organizations to the list of charities that employers will match funds for. - Short Term: Give employees time off to join protests. - Notes - On data anlysis that picks up on and perpetrates racist signals. - The first line of defense her is how data scientists are trained. - What can we do that's positive? - We can do a https://covid-oss-help.org style website to prioritize people who are working on anti-racist data analysis to push them to the front of the line for getting help. - Working to keep getting diverse groups of new contributors and helping get people involved who otherwise wouldn't have the oppourtunity. - Career launchpad - Intership with follow up steps that helps students have a path to working in Jupyter. - Increase the demand on a more diverse work force that puts upward pressure on the supply. ### 03 June 2020 Weekly Meeting - Brian - Added benchmarks to lumino datastore to validate our CRDT algorithm. - https://github.com/jupyterlab/lumino/pull/78 - https://github.com/jupyterlab/lumino/blob/8726968af142e44ca61ba28ab5f9f6911f34ee3f/datastore-benchmarks/results.md - The lumino datastore is orders of magnitude faster and more memory efficient than automerge. - Yjs and lumino trade off performance in different areas, but in general Yjs is impressive. - We should think of the lumino datastore as an abstraction layer over different types of CRDTs. - We could likely leverage the Yjs text field implementation. - Wei Ouyang - [ImJoy](https://imjoy.io) (powered by [imjoy-rpc](https://github.com/imjoy-team/imjoy-rpc)) - [ImJoy Jupyter nbextension](https://github.com/imjoy-team/imjoy-rpc/blob/master/jupyter/README.md), Try it on binder [here](https://mybinder.org/v2/gh/imjoy-team/imjoy-binder-image/master?filepath=imjoy-jupyter-tutorial.ipynb) - [imjoy-elfinder](https://github.com/imjoy-team/imjoy-elfinder) file browser (use the demo link above) - How to integrate ImJoy with Jupyterlab? - Saul Shanabrook - Eric Commit rights and general process for this - https://github.com/jupyterlab/team-compass/issues/66 - Steve Silvester - Picking back up the extension system [refactor](https://github.com/jupyterlab/jupyterlab/pull/8385#issuecomment-636319437). We influenced the design of Webpack to provide exactly what we would have built ourselves to solve our problem - Athan Reines - What is the status of evaluating potential ToC integration into core? - Should we hold off on any further feature development or go ahead? - Jason - Also picking back up the extension system refactor. Excited about the recent webpack developments. - Additional Discussion - Where do we stand on thinking about the classic notebook mode for JLab? - What is the delta between Classic Mode and Single Document Mode? - Pieces of Classic that are important: - Allow /tree/ interactions. (multiple browser tab experience.) - Make it look more like classic mode? - Tasks: - Improve Single Document via CSS. - Restructure UI to have more whitespace and use side drawers. - Work on multi-tab experience. - Experience surrounding switching between modes. - Explore single document mode for other activities. - Should we add Eric as a core committers? - How should we add new core committers? ### 27 May 2020 Weekly Meeting - Max - Early prototype of [new filebrowser widget](https://github.com/jpmorganchase/regular-table/pull/19#issuecomment-633800819) - ![](https://i.imgur.com/XgKdVEp.png) - this week I helped to launch regular-table: - https://github.com/jpmorganchase/regular-table - fast, fully virtualized html table - since it's all just plian `<table>`, `<tr>`, `<td>` etc nodes, super easy to style (just use CSS!) and customize - currently building a filebrowser widget on top of regular-table - current features: - multiple, dynamic columns - first column is a tree - columns have headers that sort on click - columns have dividers that resize on drag - to be implemented - some variety of drag-n-drop - multiselection model - mouse event model - - Steve - Progress toward extension system [refactor](https://github.com/jupyterlab/jupyterlab/pull/8385) - [Fixed CI!](https://github.com/jupyterlab/jupyterlab/pull/8464) - 2.1.x release with some bugfixes - Hope on the file descriptor leak [front](https://github.com/jupyter/jupyter_client/pull/548) - Tim - JupyterLab FS - Does somebody have Twitter Access to post a survey? - Steve does - We're working on a new interface for JupyterLab file system. Do you have opinions about remote data access in Notebooks? Please ring in [here](https://forms.gle/pCHTqgR8wmcQjWgx8). - Done: https://twitter.com/ProjectJupyter/status/1265681675079561216 - Darian - Some movement on a JupyterLab mobile experience https://github.com/jupyterlab/jupyterlab/pull/8456 ![](https://user-images.githubusercontent.com/159529/82658940-c5857b00-9c1f-11ea-82a0-0824b75da7cc.gif) - Saul - Received (most of) [CZI grant for RTC](https://chanzuckerberg.com/eoss/proposals/real-time-collaboration-in-jupyter/) - Meeting next monday https://hackmd.io/UbnBH58hS8itoWgfiWT77A - Trying out some tighter react integration in rtc, using rxjs - New FB framework for react, somewhat similar to this https://www.youtube.com/watch?v=_ISAA_Jt9kI![](https://i.imgur.com/RaVMbOu.jpg) - https://github.com/jupyterlab/rtc/pull/16 - Demo usage here: - https://github.com/jupyterlab/rtc/blob/master/packages/rtc-todo-example/src/Todo.tsx - https://github.com/jupyterlab/rtc/blob/master/packages/rtc-node/src/react.tsx - https://github.com/jupyterlab/rtc/blob/c70652896873fad5e546b1a2a4215db2b73387b0/packages/rtc-node/src/Table.ts#L14-L31 - - Additional Discussion - ### 20 May 2020 Weekly Meeting - Saul - RTC call on a week from Monday, please come, if you would like! https://hackmd.io/UbnBH58hS8itoWgfiWT77A - Current progress: - Moving towards a proof of concept of the supernode approach, with the existing lumino datastore - To look into (opened issue https://github.com/jupyterlab/rtc/issues/15) - CRDTs: - [automerge](https://github.com/automerge/automerge) - [Microsoft Fluid framework](https://techcommunity.microsoft.com/t5/microsoft-365-blog/introducing-the-first-microsoft-fluid-framework-experiences-in/ba-p/1345543) - Other approaches: - https://github.com/jaredly/local-first (Jared Forsyth has a few interesting posts looking at libraries out there: https://jaredforsyth.com/) - William Stein's implementation in cocalc - There are tradeoffs between performance and some features we want. - Steve - Mostly focused on PR reviews and CI stability - [subprocesses](https://github.com/jupyterlab/jupyterlab_server/pull/91) are a bear - Released [ipykernel 5.3](https://github.com/ipython/ipykernel/pull/511) this morning - Starting a sprint tomorrow on Extension System Refactor - Darian - JupyterLab mobile considerations - `jupyter/notebook` [maintenance](https://github.com/jupyter/notebook/issues/5360) - Tim - JupyterLab/Design - Will open Team-Compass Issue. - Files System UX Research - [competetive analysis](https://github.com/jpmorganchase/jupyter-fs/issues/36) - Survey tomorrow to pass around if you have interested parties, please feel free share around. - Jason - Upgrade to TS 3.9 merged - nbgrader port to JLab - https://github.com/jupyter/nbgrader/issues/1006 - No Cell Toolbar, to quickly introspect cell metadata or grading data. - Extension system exploration: https://github.com/jupyterlab/jupyterlab/pull/8385 - Luciano - TOC as JLab core extension ? - https://github.com/jupyterlab/jupyterlab-toc/issues/130 - Team compass issue - https://github.com/jupyterlab/team-compass/issues/63 More discussion: - Is time even real anymore? Corona Time Vortex - Is lumino discussion supposed to happen in this meeting? - Yes. Lumino readme should get a note about this meeting. - Key code discussion: https://github.com/jupyterlab/lumino/issues/74 - Continued RTC Discussion. - [Poll about notebook vs lab usage](https://discourse.jupyter.org/t/any-recent-usage-polling-on-jupyter-lab-vs-notebook-usage/4344/15), and in particular [python developers survey 2019](https://www.jetbrains.com/lp/python-developers-survey-2019/) - Several take-aways from discussion about priorities for helping users to migrate to JupyterLab - Single-document mode emulating the feel of the classic notebook - Lowering the barrier to writing dynamic plugins, like Wolf's [dynamic extension plugin](https://discourse.jupyter.org/t/dynamic-jupyterlab-extension-loading/3089) - Stand-alone installer, like the [jlab electron project](https://github.com/jupyterlab/jupyterlab_app) offers ### 13 May 2020 Weekly Meeting - - Vidar - Made a script for whether published checking lab extensions support the latest version of lab. Current results: > Up to date (193) > Outdated (379): > Support ends at v2.x: 3 > Support ends at v1.x: 173 > Support ends at v0.x: 203 - Will put it in team compass - Max - The [Provisional Features proposal](https://github.com/jupyterlab/team-compass/pull/57) - The [filebrowser is critically broken](https://github.com/jupyterlab/jupyterlab/issues/8382) - Can't open subsubdirs or lower - Broken for the last 3 weeks - [Fix here](https://github.com/jupyterlab/jupyterlab/pull/8383) - moved some API around, added unittests - [Tiny scrollbar for toolbar on mobile/narrow screen](https://github.com/jupyterlab/jupyterlab/pull/8417) - Give any div a tiny scrollbar with the new `jp-scrollbar-tiny` class - ![toolbar_scrollbar_chrome](https://user-images.githubusercontent.com/2263641/81764163-ec64e400-949e-11ea-96ba-a45fc2fbc461.gif) - Alex - Is there anyone planning to work on https://github.com/jupyterlab/jupyterlab/issues/8013 ? Jason? A custmer is pushing for a fix. - Found a "feature" a we may want to either fix or document. Cant extend extension packages without mutiple inintializations - opened issue: https://github.com/jupyterlab/jupyterlab/issues/8421 - Saul - RTC meeting time: - When is ipywidgets meeting time? - after voilla meetings everyone - Calender - RTC repo - gitter - Team compass - proposal for standardizing versioning process - https://github.com/jupyterlab/team-compass/pull/54#discussion_r424366374 - Questions: - Can/should we allow bumping versions of different sub packages - things shouldn't be in lockstep? This would make things easier for extensions, because jlab forces singletons of these packages. - rendermime - coreutils - As we go, the hope is that we become more stable as we go so we have less breaking changes. - Additional Discussion - Details of Provisional Features ### 06 May 2020 Weekly Meeting - Max - [jupyter-fs 0.0.2](https://github.com/jpmorganchase/jupyter-fs/pull/21) is now ready for beta testers - ![](https://i.imgur.com/ElFFkVN.png) - actual release of 0.0.2 later today - vscode: [back-and-forth Python/Typescript debugging](https://github.com/jupyterlab/jupyterlab/pull/8328) for JupyterLab core and extensions - works great! - current blocker: can't just check `.vscode/launch.json` into VCS - need to figure out [how to incorporate debug config into jlab](https://github.com/jupyterlab/jupyterlab/pull/8328#issuecomment-623635275) - [@telamonian/theme-darcula](https://github.com/telamonian/theme-darcula) is now available for JupyterLab >=2.0 - Ed - Potential fix for single completion insertions (https://github.com/jupyterlab/jupyterlab/issues/8255) - https://github.com/jupyterlab/jupyterlab/pull/8375 - Steve - Test refactor. Using straight-up Jest now for every package. Tests are now by the source instead of in their own directory. This means you can debug package-by-package, and conforms to a more standard approach. We have mocks for all services and a js test server. Updated instructions are in the contributor guide. - Cleaned up our CI. Fixed the link checking using caching (Thanks also to Nick!). - Federated webpack bundler is now in a beta release, ready for serious work toward refactoring the build system. - Vidar - RTC meeting? - Additional Discussion - Traitlets/ Server [settings for jupyter-fs](https://github.com/jpmorganchase/jupyter-fs/blob/master/jupyter-config/jupyter_notebook_config.d/jupyterfs.json) ### 29 Apr 2020 Weekly Meeting - Steve - Devops extravaganza - [Services](https://github.com/jupyterlab/jupyterlab/pull/8279) is the important one, but there are a slew of others - [pytest-check-links caching](https://github.com/jupyterlab/pytest-check-links/pull/12) - [JupyterLab IDE Demo](https://github.com/blink1073/jupyter-ide-demo) - Eric - JupyterLab as Server Extension [PR1](https://github.com/jupyterlab/jupyterlab/pull/7416) and [PR2](https://github.com/jupyterlab/jupyterlab_server/pull/79) on Jupyter Server 0.3 - Only Windows JS test fail on GitHub Actions - Need to align across jupyterlab/jupyter-server/nbclassic supported python version (3.5, 3.6, 3.7, 3.8) and platforms (linux, windows) combination - Max - [experimental "library" mode in typedoc makes for greatly improved API docs](https://github.com/jupyterlab/jupyterlab/pull/8320) - remaining issues - packages listed as eg `"apputils/src/index"` instead of `@jupyterlab/apputils` - doesn't include default exports - LabIcon docs finished (for now) - dev docs now mostly complete, still more to do on the API docs side - Jason - Extension rework - Saul - Git branch/release flow - Discussed in this issue https://github.com/jupyterlab/jupyterlab/issues/8195 - Have a current WIP RFC here https://github.com/saulshanabrook/team-compass/blob/master/rfc/development-cycle.md - Open questions: - Things would be *a lot* simpler if we just did an automatic release after every minor and patch PR merge. This should be fine with semver. I believe there was some pushback last time this came up. How strongly do people feel about this? What's the rationale? There are a lot of wins in terms of development time! - Can we bump all JS packages in unison, even for breaking changes? - are there previous discussions here? - Are the docs only deployed from master? Are we currently making changelogs for 1.2.x releases? Are these changelogs going into master? - Darian - Some thoughts on sunsetting classic notebook: feature parity, checking with other Jupyter projects - Lab on Mobile - Vidar: Do we need changes in Lumino? - Additional Discussion - 51 days until feature freeze (19 June) - Final decision on [jupyterlab-forge](https://github.com/jupyterlab/team-compass/issues/52) - ### 22 Apr 2020 Weekly Meeting - Max - [More LabIcon docs](https://github.com/jupyterlab/jupyterlab/pull/8246) - Added background section, should hopefully make the central issues clearer - Where should I stick these in the main jlab docs? - [Unified API docs for the entire @jupyterlab monorepo](https://github.com/jupyterlab/jupyterlab/pull/8239) - Huge improvement of the landing page for our API docs - Doesn't quite work right - The `typedoc-plugin-monorepo` plugin creates lots of duplicate entries - Easy fix: use a static landing page, like @lumino currently does - Better fix: use the `library` mode of typedoc (currently [experimental](https://github.com/TypeStrong/typedoc/pull/1184)) - unlike now, `library` will allow for the API docs of each `@jupyterlab` package to link to one another (I think) - [The future of LabIcon](https://github.com/jupyterlab/jupyterlab/issues/8237) - I want to bring everyone onto the same page about LabIcon - Turns out there is in fact no single optimal way to create and use icons - I need a way to consume LabIcons that allows for both late binding (like our old icons-as-css-background) and dynamic repainting on theme change (like our new icons-as-inline-svg) - Improve performance of long lists with 1+ icons per item - Allow for updates of component/widget style post-render - ([example issue](https://github.com/jupyterlab/debugger/pull/376)) Should make a lot of complex icon usages easier to refactor for LabIcon - I've investigated [three proposals](https://github.com/jupyterlab/jupyterlab/issues/8237) for implementing the above - There's a [working prototype](https://github.com/jupyterlab/jupyterlab/pull/8232) for proposal 1: dynamically generated icon stylesheets - - Tim - Working on [settings editor](https://github.com/jupyterlab/jupyterlab/issues/8148) for JupyterLab. - Thinking about how to treat this, JSON Schema editor or pure GUI interface that hides the complexity? - Check VSCode Settings editor. (UI with Validation) - Web browsers. - Not IntelliJ. - Extension points for setting editor. - Brian - Starting to pick away at tasks related to RTC. - Can we make the DocRegistry agnostic to the type of underlying model and remove the hard dependency on ModelDB? - https://github.com/jupyterlab/jupyterlab/issues/8235 - The notebook uses a horribly complex ContentFactory pattern that is making it difficult to work on the notebook. - https://github.com/jupyterlab/jupyterlab/issues/8236 - Steve - [nteract Data Explorer](https://github.com/jupyterlab/jupyter-renderers/pull/224) - general policy on new renderers? - Depricate renderers repo, these should live in the community. - Added an issue to [Team Compass](https://github.com/jupyterlab/team-compass/issues/52) to suggest a `jupyterlab-forge` GitHub org for any repos that aren't considered core to JupyterLab (either JupyterLab or repos that we depend on). - [puppeteer woes](https://github.com/jupyterlab/jupyterlab/issues/8244) - [Fix session context error handling](https://github.com/jupyterlab/jupyterlab/pull/8250) - Cache [checked links](https://github.com/jupyterlab/pytest-check-links/issues/11) - Meeting to discuss federated build? [See additional discussion] - Alex - My team is currently hosting a IBM workshop on JupyerLab, the new JupyterLab interns are in attendance (:tada: Thanks, Alex! This is awesome! -Zach) - Git extension lab 2.0 update pr has been merged, pending rc for extension release with 2.0 support - Zach - Jupyter Server docs received a makeover. - https://jupyter-server.readthedocs.io/en/latest/index.html - Release Server 1.0 this week. :tada: - Server 2.0 (master) is planning merge the following features: - [Kernel Providers](https://github.com/jupyter/jupyter_server/pull/112) - (opt-in) [Authorization layer](https://github.com/jupyter/jupyter_server/pull/165) - (opt-in) telemetry in the server-no open PR yet. - [Messaging on notebook repo](https://github.com/jupyter/notebook/issues/5360) - [Actively maintained, maintenance-only mode, or end-of-life?](https://github.com/jupyter/notebook/issues/5360#issuecomment-612138705) - Darian volunteered to write a JEP about the classic notebook status. - Jeremy - Update JupyterLab Demo to 2.0 - https://github.com/jupyterlab/jupyterlab-demo/pull/92 - Docs update to link to the extension example repo: - https://github.com/jupyterlab/jupyterlab/pull/8254 - Jason - Researching the extension refactor, currently webpack module federation seems most promising - [Fixed "Save As..."](https://github.com/jupyterlab/jupyterlab/pull/8238) and working on [fix for kernel gateways being able to restart kernels](https://github.com/jupyterlab/jupyterlab/issues/8013). - Looked into being able to take advantage of the notebook buffering input. - Question about coordinating merging https://github.com/jupyterlab/jupyterlab/pull/8225 and https://github.com/jupyterlab/jupyterlab_server/pull/87 - Darian - Should we add `libgbm1` manually to handle CI breakage https://github.com/jupyterlab/debugger/pull/428 - Reviewed completer refactor and had some comments that might be worth discussing in this call https://github.com/jupyterlab/jupyterlab/pull/8080 #### Aditional Discussion: - Meeting about federated build - ### 15 Apr 2020 Weekly Meeting - - Steve - [Jupyterlab Favorites](https://github.com/jupyterlab/team-compass/issues/50) - [Test Modernization](https://github.com/jupyterlab/jupyterlab/pull/8214) - [ESLint all the things](https://github.com/jupyterlab/jupyterlab/pull/8191) - [Slow Kernel Startup Handling](https://github.com/jupyterlab/jupyterlab/pull/8174) - Shreyas - https://github.com/NERSC/jupyterlab-favorites - [Compass Issue - Jupyterlab Favorites](https://github.com/jupyterlab/team-compass/issues/50) - This feature is helpful but doesn't have a maintainer at this point. - Saul - Discussion around lazy rendering of cells - https://github.com/jupyterlab/jupyterlab/issues/4292#issuecomment-597730963 - Idea: use IntersectionObserver to know what is in view, and wait on rendering the rest until you scroll. - When things are idle, use `requestIdleCallback` to schedule a call to load more. - here is an example of doing this with React - https://gist.github.com/saulshanabrook/b886dfa9acf9c2e21d7caa1646fa8dcd - Might need to add some UI in the notebook to show "loading" state, so that if you are running find and replace, you know that maybe you aren't searching the whole document - Questions: - Should we lazy render input code cells as well? - Brian: replacing codemirror just with syntax highlighted text doesn't help much. - Do it at the cell level instead of output level to do all of it? - do it at resize - Chunking into batches of updates helps, to minimize resize events. - Would this help in making it quicker to do a first render, when they have multiple notebooks open and then they reload? - Question changes to completer API changes, how to deal with changes but making it backwards compatible? - https://github.com/jupyterlab/jupyterlab/pull/8080#discussion_r406964000 - Darian building this branch locally to take a look. - Max - jupyter-fs - samba/Windows share backend now working on Windows - https://github.com/jpmorganchase/jupyter-fs/pull/16 - Darian - Debugger update - `egg_info` in source package of JupyterLab - Zach - "Collaboration in Jupyter" Initiative - https://hackmd.io/3wvMwR-1SYesRYsrJFwpMw #### Aditional Discussion: - Favorites UI resourcing? - Shreya do you have funding to help support this work, even if you don't have time yourself? - Or is someone here volunteering to take this on and support it? - Usually things that are brought into the jupyterlab core have someone who is responsible for maintaining them. - It's unclear to me if anyone in core has spare resources to devote to this. I would't want it to just be something added to our plate and us not have enough time to maintain it. - Result: - Basically we won't put a lot of resources into improving it neccesarily, but can allow new contributions and act as shephards for new maintainors. Also increases visibility of project - ### 08 Apr 2020 Weekly Meeting - Eric - Extension Manager for 2.1: Polishing PRs - Thx Jason and Saul for reviews and merges - [Jupyterlab renderers upgrade to jupyterlab 2.1](https://github.com/jupyterlab/jupyter-renderers/pull/219) - Playing with Webpack Federation for other project, pulling jlab react widgets from remote - Ed - Check in on - https://github.com/jupyterlab/jupyterlab/pull/8080 - https://github.com/jupyterlab/jupyterlab/pull/8137 - https://github.com/jupyterlab/jupyterlab/pull/8140 - https://github.com/jupyterlab/jupyterlab/pull/8141 - Saul, Darian, Tim are looking at these this week - Saul - Things have been released... - A few questions on releasing... - How do we get to end goal of hitting a button to release on Github? - auto generate changelog, enforcing stricter syntax in PR description - figure out what backports should/could be done for each PR - How often do we release things? - If we can automate, it makes it less of a burden to actually do release - and so "when" it happens can be based more on first principles than on who is available (maybe?) - Should we be clearer about our intentions, both around getting PRs in and doing releases? So that we understand the conflicting priorities possibly between our employer's desires and the project's needs? - As a benchmark, this release took somewhere between 16-30 hours of Saul's time and 16-30 hours of Jason's time - changelog took maybe 12 hours total - Make an issue for Testing automation on releases - https://github.com/jupyterlab/jupyterlab/issues/8195 - Jason - Exploring webpack module federation and other issues around the extension system rework - Will try to set up a meeting with at least Eric and Steve later this week to push forward - Darian - Debugger update - Tim - I would like to set up a meeting with UCI teams and stakeholders for Debugger and JupyterLab-FS/Data Explorer stuff. - Alex - Elyra added a beta code snippet extension yeserday (https://github.com/elyra-ai/elyra) - What's the git extension 2.0 support timing looking like and can I aid in speeding it up? - https://github.com/jupyterlab/jupyterlab-git/pull/520 - revert to b00da65 - rebase on top of master #### Aditional Discussion: - Releases: - We released 2.1.0 and 2.0.2 (thanks Saul!) - We still have the beta freeze at 19 Jun 2020, so if you plan to work on a major feature, now is a good time to plan out the work. - New Zoom channel, takes effect next week: - https://zoom.us/my/jovyan - https://zoom.us/j/546199338 - Tim to change readme - Extension system rework - Concerns we are addressing: - Can we ship an extension that does not require a post-install phase that re-compiles the JupyterLab application? In other words, can an extension be a simple set of static assets that resides in a well-known location? Can I untar some file into a directory and refresh the page and have it magically work? - **System is not magic for extension authors**: Giving extension authors more control over the environment their code is built in, before being run in the browser, would be useful. For example, currently we run all extensions in our webpack config. This is an issue, if extensions have their own config they would rather run. It's also confusing for them, because the post install build step is opaque and not documented. So when it fails (as pointed out above) we get weird issues. Also, it fails on user machines, not extension athors machines, which is even harder to debug. - Track versioning between frontend extensions, backend extensions, jupyterlabs server versions, jupyterlab version. We currently have two package manager resolutions working seperately. It would be nice if we could just use one to properly resolve versions between frontend and backend code and extensions. - One package per extension, even if that involves both a frontend and backend component - A way to minimize the download size for clients on slow networkd - debuggability - Make it easier to develop multiple extensions independently - allow for the creation of seperately deployable built artifacts from each extension ### 03 Apr 2020 Extension system refactor Resources - Steve has some design time - Saul has some time to work on design discussion - Jason has some cycles - Darian can test, research, put some time into discussion Primary win: - end users don't need node and internet access - packaging is easier - you package up a single "binary" with all dependencies Timeline: - Beta slated for June 2020, so we have about 2.5 months - Approaches: - We could have two modes, a compiled mode like we have now, and a totally amd-based solution (where we could concatenate multiple amd modules into a single requested file). - Webpack federated modules First steps - Identify the concerns we are solving and prioritize those - Investigate the webpack federated modules as a possible new technical alternative ### 01 Apr 2020 Weekly Meeting **Updates** - Max - My priority this week is the LabIcon docs - [What currently exists](http://jupyterlab.github.io/jupyterlab/ui-components/index.html#codelabiconcode-user-guide) - My plan is to flesh out the narrative with more examples, and to look into how I can clean up the API docs - It would be nice if our [API docs landing page](http://jupyterlab.github.io/jupyterlab/) was styled/advertised - Making progress on jupyter-fs - Added smb/Windows share support. Currently working on Mac and Linux: - https://github.com/jpmorganchase/jupyter-fs/pull/16 - Can anyone suggest a nice, open-source friendly way for me to get ssh access to a Windows image for development/testing? - Discussion of potential backends/prior art for jupyter-fs - https://github.com/jpmorganchase/jupyter-fs/issues/7 - Jason - Help Saul with JLab 2.1/2.0.2 - Thank you! - Saul - Start planning for extension rework work for 3.0 - Saul - Release party this week! - 2.1.0 alpha release is out, please test! - plan: 2.0.2 release on thursday - another 2.1.0 release on thursday as well - 1:30-3pm EST on thursday - Working on a cross interface mime renderer abstraction, to make it easier to write comms based renderer - https://github.com/Quansight-Labs/jupyter-output-spec - Luciano - Look into reported TOC issue/release - https://github.com/jupyterlab/jupyterlab-toc/issues/123 - Help with JupyterLab-git extension release that supports JupyterLab 2.x - Eric - Extensions Manager: Black/White Listings + Badges released in 2.1.0-a.0: Thx Saul and Steven for reviews and merges! - Jlab on JServer: WIP with Zach to align on latest Server branch **Additional Discussion** - 2.1/2.0.2 plan - Planning meeting for extension rework (see [#5672](https://github.com/jupyterlab/jupyterlab/issues/5672) and [#7468](https://github.com/jupyterlab/jupyterlab/issues/7468)) - Attendees: Saul, Eric (TBC), Vidar, Luciano, Darian, Max, Max - Please fill out http://whenisgood.net/dzcqq3q if you are interested in attending - Which restart-and-run icon: [#8091](https://github.com/jupyterlab/jupyterlab/pull/8091) or [#8136](https://github.com/jupyterlab/jupyterlab/pull/8136)? ### 25 March 2020 Weekly Meeting **Updates** - Tim - Two teams of Students from UCI's [Master of Human-Computer Interaction](https://mhcid.ics.uci.edu/) will be joining me to help work on some JupyterLab related proejts for the net six months. I'm thinking about having them work on the following, but aam open to input. - UX Review and design for debugger, as well as designing a settings UI. - Jupyteral-FS work that the Max and Tim have been working on. - Steve - Helping with the 2.1 release - PR to help with our [docs woes](https://github.com/minrk/pytest-check-links/pull/7) in CI. - Released `jupyterlab-git@0.9.1` with a compatibility fix for nbdime (needs <2.0) - Ed - https://github.com/jupyterlab/jupyterlab/pull/8080 - New Completer API PR - Saul's feedback: Has breaking changes - Release schedule? - Eric - [Run/Tests/Examples as a Server Extension](https://github.com/jupyterlab/jupyterlab/pull/7416#issuecomment-603160346), depends on jupyter-server+nclassic releases and [CI stability](https://github.com/jupyterlab/jupyterlab/pull/8068) - [Larger Badges for Extension Installer UI](https://github.com/jupyterlab/jupyterlab/pull/8078) - [Update user messages when installing extensions with companions](https://github.com/jupyterlab/jupyterlab/pull/8076) - [Listings](https://github.com/jupyterlab/jupyterlab/issues/7933#issuecomment-602447785): Should JupyterLab maintain a blacklist? (discuss in additional discussion, comment also on https://github.com/jupyterlab/jupyterlab/issues/7972) - Max: - Release of jupyterlab-git 0.10.0 *today* - https://github.com/jupyterlab/jupyterlab-git/issues/568 - The S3 stuff in jupyter-fs now works, added some examples and CI tests: - https://github.com/jpmorganchase/jupyter-fs/pull/15 - Saul: - Help for 2.1 release - Demo performance results: - https://github.com/jupyterlab/jupyterlab/pull/8020 - TLDR: switching to notebooks with many plotly plots is too slow! - Jeremy / Sylvain / Johan / Darian: - On behalf of the debugger team, blog post published: https://blog.jupyter.org/a-visual-debugger-for-jupyter-914e61716559 - Please RT the announcement: https://twitter.com/ProjectJupyter/status/1242850222688161798 - Darian - Updated @ikiw's PR to move throttling of setting registry `fetch` requests to the setting data connector: https://github.com/jupyterlab/jupyterlab/pull/7927 - `@jupyterlab/debugger` v0.2.0 released last week in advance of the blog post that Jeremy mentions above - Jason: - Helping Saul with 2.1 release, reviewing PRs, etc. - We added GitHub actions for tests, and split up each test suite: https://github.com/jupyterlab/jupyterlab/pull/8064 - Do we need the windows js tests? **Additional Discussion** - Should we have a policy for how to warn about JS deprecations (e.g. `console.warn()` on access)? See - Release plans: - [2.1](https://github.com/jupyterlab/jupyterlab/milestone/49), 2.0.2? ### 18 March 2020 Weekly Meeting - Please introduce yourself when it's your turn. - Tim - Release update: - We target a 22-week release cycle for 3.0, releasing in time for a JupyterCon announcement. - https://github.com/jupyterlab/jupyterlab/issues/8038 - Darian - Minor PR to include `.yarnrc` - Jupyter governance work is proceeding well. - Debugger 0.2 target release this Friday, 1.0 to either ship with JupyterLab 3.0 or coincide with its release - Max - Last few issues to burn down for 0.10.0 release of jupyterlab-git - https://github.com/jupyterlab/jupyterlab-git/issues/568 - If anyone wants to pitch in some CSS help, it would be appreciated - jupyter-fs is now live on jpmchase's public github: - https://github.com/jpmorganchase/jupyter-fs - Will be able to support multiple filebrowsers of various protocols: - local - S3 - samba - whatever else we can implement - the (hopeful) future of jlab core's contents manager - Eric - Black and White listings: Dev done (specs by Tim and Mars, reviewed by Saul) [PR1](https://github.com/jupyterlab/jupyterlab/issues/7989) [PR2](https://github.com/jupyterlab/jupyterlab_server/pull/82). Open for 1 or 2 weeks for review, then candidate for merge. - Extensions splash screeen to be planned. - Once merged, we can [enable the extension manager by default](https://github.com/jupyterlab/jupyterlab/pull/8050). - Vidar - More extensions lab 2.0, all good still - Additional Discussion - Ipykernel and Xeus debugger support - integrating debugger support would require a re-write of ipykernel - Saul mentioned this PR https://github.com/jupyterlab/jupyterlab/pull/8037 to allow extensions to work in a dev build ### 11 March 2020 Weekly Meeting - Introductions - Tim - UI Components - [Switches](https://github.com/jupyterlab/jupyterlab/issues/8010) - Release meeting tomorrow at 10 PDT Notes will be posted in teamp-compass - Vidar - Lab 2 compat extensions - Eric - Working with Zach to finalize [JupyterLab as Server Extension](https://github.com/jupyterlab/jupyterlab/pull/7416) and [JupyterLab Server as Server Extension](https://github.com/jupyterlab/jupyterlab_server/pull/79) (relying on [Enable ServerApp to discover ExtensionApps](https://github.com/jupyter/jupyter_server/pull/180)). - 2 PRs for Black and White listings: [Black and White listings for the Extension Manager](https://github.com/jupyterlab/jupyterlab/issues/7989) and [Black and White Listings Handler](https://github.com/jupyterlab/jupyterlab_server/pull/82). - New `ListingsHandler` refreshing the listings in a cache on server side. - [Listings format example](https://github.com/datalayer-jupyterlab/jupyterlab-listings-example/blob/master/blacklist_simple.json). - [Docs being written in a new Admin section](https://github.com/datalayer-contrib/jupyterlab/blob/15ab0953505e70cfe4ab3ec99ac277d45f2a6654/docs/source/admin/listings.rst) - Feedback on UI welcome, cfr. Disclaimer, better icons needed... (Tim and Mars working on it). - Jeremy: - Opened: https://github.com/jupyterlab/team-compass/issues/44 to migrate the extension examples to the `jupyterlab` GitHub organization - Saul - notebook performance party! - https://github.com/jupyterlab/jupyterlab/pull/8020 - next step is to test with plotly... so need to add custom extensions in dev mode - Jason - Working on using GitHub actions: https://github.com/jupyterlab/jupyterlab/pull/8027 - Darian - Changed the `Throttler` API in this PR https://github.com/jupyterlab/lumino/pull/54 to include an `edge` argument. This allows a future `invocation` argument if we decide it's necessary. - Additional Discussion - Elyra was open-sourced: https://github.com/elyra-ai/elyra - ### 04 March 2020 Weekly Meeting - Introductions - Tim - We should schedule meeting to discuss future releases. - Quick review of Extension Installer warning. - https://github.com/jupyterlab/jupyterlab/issues/7967 - Steve - Released 2.0.0 and 1.2.7 - Updated and released jupyter-renderers for 2.0 - Eric - JupyterLab as Server Extension ready for review (tests green): [PR on jupyterlab](https://github.com/jupyterlab/jupyterlab/pull/7416), [PR on jupyterlab-server](https://github.com/jupyterlab/jupyterlab_server/pull/79) - Quick demo for feedback of [[DRAFT] [WIP] Black and White listings for the Extension Manager](https://github.com/jupyterlab/jupyterlab/pull/7989) - Jeremy: - Progress on the JupyterLab Extension Examples with @echarles and @fcollonval: https://github.com/jtpio/jupyterlab-extension-examples - Debugger fixes - Alex - Helping update TOC to lab 2.0 - working on a lab-git issue - no work on lab linter yet - Ed (Kite) - Feedback on Completer changes - https://github.com/jupyterlab/jupyterlab/issues/7044#issuecomment-594249225 - https://github.com/jupyterlab/jupyterlab/issues/7983 - Darian - Source-only version of PyPI package was missing `package_data` and now it is not (which is part of why Steve published 1.2.7), but it still ignores dot files unless we explicitly add them. This matters because of `.yarnrc` - Saul - Had a fun time with Glue folks last week in NYC - Built a lil demo for them on building dashboards in jupyterlab https://github.com/Quansight-Labs/jupyter-widgets-takeover#jupyter-widgets-takeover - I can demo this - TLDR is blurring lines between "dashboard" and "notebook", need ways to start users in constrained environment and then move slowly to less contstrained - Many technical next steps to make this viable - Conflicting with curent Voila stack. Might be nice to chart out unified best way forward if possible - Working on performance improvements on switching between notebooks - profiled, mostly in style updates - going to try to do virtualized dom to update - strategy is to not change any API for output widget but under the hood put a later of React in the middle between two layers of Lumino widgets - Then use react virtualized library - https://github.com/jupyterlab/jupyterlab/issues/4292 - Here is an in-progress discussion about a web standard that enables native browser virtualized scrolling for some cases: https://github.com/WICG/display-locking/ - At one point Jason explored making a Lumino widget for virtualized scrolling. No code to show for it, but Jason would be interested in discussions around this. - Jason - Helped with changelog and fallout from 2.0 and upgrading and migration challenges - Upgrading custom widget packages for jlab 1 *and* 2 turns out (through a lot of work :) to be as easy as adding `||^3` to `@jupyter-widgets/base` dependency version. - Luciano - Helping releasing JupyterLab extensions that support JupyterLab 2.0 - TOC for Lab 2.0 release by end of the week - Git for Lab 2.0 (Any ETA? I could help with release by end of the week as well) - Max - starting work on jupyter-fs - next generation ContentsManager - flexibly work with multiple remote(?) "filesystems" - will be an official JPM project - Still working on icons - lots of optimization/speedup work - Starting to work on more general UI components - LabButton (maybe) - Towards the next release of jupyterlab-git - https://github.com/jupyterlab/jupyterlab-git/pull/520 - File icon fallback is not rendering: https://github.com/jupyterlab/jupyterlab/issues/7968 - Zach - NBClassic: add Jupyter Server / Notebook config shim layer. - Add a simple class to jupyterlab_server for a "transition period" that manages config shims. - Remove this class after transition period ends—little disruption to Jupyter Lab. - https://github.com/Zsailer/nbclassic/pull/7 - Aditional Discussion: - Release meeting you're interested in this meeting you please put your name below, and I'll reach out to schedule the meeting - Tim @tgeorgeux - Max @telamonian - Saul @saulshanabrook - Vidar @vidartf - Steve @blink1073 - Brian @ellisonbg - Darian @afshin - Luciano @lresende lresende@us.ibm.com - Extension Manager. ### 26 February 2020 Weekly Meeting - Introductions - Saul - Jlab git history/company contributions (again) - https://github.com/jupyterlab/jupyterlab-git/pull/530 - Alex - Helped my teammates on work on the TOC and git extensions - Will most likely start looking at Lab lint this week - Martha - Working on updating TOC extension to 2.0 rc1 - Working on making TOC compatible with python files - Steve - Fixed RTD build - Reviewed PRs - Max - icons are all fixed up now - new icon styling system, try it out and give me feedback - see docstrings in `ui-components/src/icon/labicon.tsx` and `ui-components/src/style/icon.ts` - starting work on multi-contents manager - Darian - https://github.com/jupyterlab/lumino/pull/54 - Jason - Released 2.0 rc1 and rc2, updated changelog, etc. - Continued working on porting ipywidgets to jlab 2.0 and making a release plan coordinating ipywidgets and custom widgets releases for jlab 2.0. - Eric - JupyterLab on Jupyter Server - 👀 [JupyterLab Server as Server Extension](https://github.com/jupyterlab/jupyterlab_server/pull/79) - RFR (Ready for Review). - 🏃 [JupyterLab as Server Extension](https://github.com/jupyterlab/jupyterlab/pull/7416) - Runtime is working 👍 - Tests migrated and 90% green - 100% by next week. - Pending discussions (join [tomorrow server meeting](https://github.com/jupyter/jupyter_server/issues/126)): [Make ExtensionHandler a Mixin](https://github.com/jupyter/jupyter_server/pull/174) + [[SPEC] Migration of notebook extension definitions to jupyter_server](https://github.com/Zsailer/nbclassic/issues/6) - JupyterLab Extension Manager - Requirement collection on - [[DISCUSS] black/white listing for extensions](https://github.com/jupyterlab/jupyterlab/issues/7933) - Discourse https://discourse.jupyter.org/t/security-of-jupyterlab-extension-manager/3444 - Additional Discussion - JupyterLab 2.0 final timeline? - RC2 released yesterday - Acknowledgments - provide a way to acknowledge individuals and sponsoring organizations - easy to keep up to date (or clearly point-in-time so no need to update) - provides visibility to incentivize contributions and sponsorship - in interest of fairness, has a clear decision criteria for an acknowledgment - two current proposals: - a special acknowledgements file that is kept up to date manually - harder to keep up to date - subjective criteria for inclusion - an acknowledgement in the changelog and/or release blog post - clearly point-in-time, but harder to update ex post facto - subjective criteria for a big callout, but can also easily include all contributors ### 19 February 2020 Weekly Meeting - Introductions - Tim - No updates. Interviewing Interns for this summer this week. - Eric - [JupyterLab Server as Server Extension](https://github.com/jupyterlab/jupyterlab_server/pull/79) ready for review (unit tests migrated and green) - - Max - Icons update - almost done, hopefully today - https://github.com/jupyterlab/jupyterlab/pull/7864 - one more lumino fix - https://github.com/jupyterlab/lumino/pull/53 - - Saul - [OpenCollective](https://opencollective.com/) for Jupyter Donations? - Additional Discussion points below. - Alex - Added "click out" for modules - Need some aid on linting, specifically the how and why of - Jason - Steve put in a [PR to add aliasing for phosphor modules](https://github.com/jupyterlab/jupyterlab/pull/7893), to help extension developers transition and maintain a single codebase for JLab 1 and 2 in certain cases. - Aditional discussion - More `Poll` talk. `leading` and `trailing` et alia: https://github.com/jupyterlab/jupyterlab/pull/7895 - [OpenCollective](https://opencollective.com/) for Jupyter Donations? - Why? Gives users an easy way to donate that is transparent. - How does it compare to existing NumFocus donation? - Better UI (example https://opencollective.com/spyder) - Get "cred" b/c donation is public - Spyder team got enough donations to fund some people very part time - Can we start collecting money before we figure out what to do with it? - [Discourse Post](https://discourse.jupyter.org/t/open-collective-for-jupyter/3352) - Next steps: - Talk to folks on NumFocus side and come back to discourse thread with reccomendation. - JupyterLab Release Discussion. - Have we scheduled release plan meeting for next cycle? - Tim to make an issue on to - RC on Friday Morning, Release on Wednesday. - Travel grants for jcon? ### 12 February 2020 Weekly Meeting - Introductions - - Darian - Checked out the Lumino UMD branch to play with examples. Not sure what I was doing wrong... - Steve - Working with Max on icon finalization before cutting final release - some Lumino packages were bumped - Tentative ETA? I believe we have a dependency on these and we wanted to try these before GA. - Jason - Working on ipywidgets 8. Good news is I think we actually can release a jupyter lab manager that allows us to have ipywidgets 7 in jlab 2.0, so pressure is off for people to migrate. - Saul - RTC grant submitted - Weird UI discussion around context menus in outputs - Currently react outputs cannot render their own context menus and disable JupyterLab's (in an easy way) b/c Reacts event lifecycle takes place after the default one (this is an underlying React bug/design decision) - Suggestion (which I would like feedback on): - Can we allow disabling JupyterLab context menus in outputs that have their own context menu? - https://github.com/jupyterlab/jupyterlab/issues/7670 - Am going to take a look at performance issues for many outputs in one notebook - Like https://github.com/jupyterlab/jupyterlab/issues/4292#issuecomment-585314230 - Slow: https://github.com/jupyterlab/jupyterlab/issues/1639 - Long time to switch tabs with many 12 plotly cells - Max - the .icon field in various Lumino interfaces now will accept a `LabIcon` - https://github.com/jupyterlab/lumino/pull/46 - Post LabIcon cleanup: https://github.com/jupyterlab/jupyterlab/pull/7864 - Aditional discussion - JupyterCon 2020 is announced! Berlin, August 10-14. [Reviewers are requested](https://blog.jupyter.org/jupytercon-2020-is-a-go-47c82b281fa8). There will be a CFP opening soon for tutorials, talks, and sprints. - Scipy 2020 talks/tutorial? [Tutorial deadline is 15 Feb](https://www.scipy2020.scipy.org/tutorials), [talk deadline is also 15 Feb](https://www.scipy2020.scipy.org/talk-poster-presentations). [Sprints](https://www.scipy2020.scipy.org/sprints) are also there. - I (saul) am down to give a tutorial, maybe on extension development including backend/frontend extension? - [Lumino polling discussion](https://github.com/jupyterlab/lumino/issues/47) - Roadmap / product management and planning for JupyterLab: - Given JupyterCon's timing, we should think about releases: JupyterLab 3.0, Debugger 1.0, *et alia* ### 5 February 2020 Weekly Meeting - Introductions - Tim - Working on Command Palette and in-Cell UI for 3.0 - Darian - Another debugger 0.2 alpha release this week - Question about `FontAwesome` - Update on governance / question for discussion - Steve - Released RC 2.0 - Posted notes on extension system refactor: https://github.com/jupyterlab/jupyterlab/issues/7468#issuecomment-581600432. Summary: bundle with Parcel (it gives us the appropriate intermediate format) and use a private requirejs as a loader (battle-tested code, but private variable so it is an implementation detail) - Alex - Was working on moving our extensions onto the 2.0 beta/rc specifically becoming familar with the new LabIcon work. Starting this week will be setting time aside to work on jupyterlab issues specifically (not just our extensions) -> open to direction - Gordon - Lumino UMD PR Discussion https://github.com/jupyterlab/lumino/pull/40 - Jason - Working on ipywidgets 8 (and JupyterCon, etc.) - FYI, zmq has default "high water mark" of 1000 messages, after which it can start dropping messages, so if you ever are in a situation where you have a lot of messages coming from the kernel and some are dropped, think about the zmq buffer ([1](https://github.com/jupyter/nbconvert/issues/659#issuecomment-484673647), [2](https://github.com/voila-dashboards/voila/issues/534)) - Max - `JLIcon` is now `LabIcon` - https://github.com/jupyterlab/jupyterlab/pull/7767 - Vidar - Added Dummystore on RTC repo for a non-collaboration datastore interface implementation https://github.com/jupyterlab/rtc/pull/4 - RC consumption noise: https://github.com/jupyterlab/jupyterlab/issues/7851 - Additional Discussion - [x] When to Freeze API for 3.0 release. - Should we appoint a release manager and let them take input and make a final decision? - **We will hold a meeting about this post-2.0 final release.** - [x] Governance questions re: delegates - [x] [Lumino packaging UMD](https://github.com/jupyterlab/lumino/pull/40 ) (min files / sourcemaps / types) ### 29 January 2020 Weekly Meeting - Max - icons! - [#7767](https://github.com/jupyterlab/jupyterlab/pull/7767) is done, there's also some docs - where should dev docs go? - should we have a core-interfaces package? - A. T. Darian - Debugger update: Working on JupyterLab 2.0 version of debugger, released 2 alphas of `0.2.0` so far. We are on a weekly release schedule. - [JupyterLab 1.x to 2.0 Extension Migration Guide](https://jupyterlab.readthedocs.io/en/latest/developer/extension_migration.html) - Please submit PRs to [the migration guide](https://github.com/jupyterlab/jupyterlab/blob/master/docs/source/developer/extension_migration.rst) with other migration examples/suggestions. - Tim - No updates - Hiring interns. - Jason Grout - continued work on ipywidgets targeting 8.0 release shortly after JLab 2.0 (needed for support). - [Small PR](https://github.com/jupyterlab/jupyterlab/pull/7830) moving the notebook logging to the notebook extension. Could easily be moved to 3.0. - Steve Silvester - Released a beta3 and 1.2.6 last Friday with a bug fix for extension authors using our CI helper - Working with Max on the icon refactor - Finished initial exploration of module transpilers and loaders, need to type notes - Saul Shanabrook - JupyterLab 2.0 issue text: - JupyterLab 2.0 is currently in beta and will be released soon. If you have an extension for JupyterLab, you will likely need to release a new version for it to be installable in the new version. To test your new extension with JupyterLab 2.0, you can install it with `pip install --pre jupyterlab` and then try to install your extension. - We have put together a guide on the latest docs on things you need to change to update: https://jupyterlab.readthedocs.io/en/latest/developer/extension_migration.html - If you encounter other things that you need to change, please submit a PR to [that document](https://github.com/jupyterlab/jupyterlab/blob/master/docs/source/developer/extension_migration.rst)! - Adding "History" section to JupyterLab git - Way to give individuals and companies credit and let ppl know how the project came to be in a holistic way, is the goal. - https://github.com/jupyterlab/jupyterlab-git/pull/530 - :+1: from Steve, Darian and Luciano - Maybe add another section for used at, to give a sense of production ready (Luciano suggestion) - I put some thoughts down about a different way to do this at https://discourse.jupyter.org/t/ideas-for-recognizing-developer-contributions-by-companies-institutes/3178/4?u=jasongrout - Updates on CZI grant - Fernando gave some comments, suggested we include real time commenting - Will send out a version later today after I edit for any comments to whoever is interested - [Google Doc](https://docs.google.com/document/d/1JEL0_LLzWzOJ92vsAWC6LTivraFO0tPD8DRjAFsYTsw/edit#) - Luciano - Volunteering to help migrate TOC extensions to JupyterLab 2.0 - Addtional Discussion - RC and release - Jason thinks we should have at least week between first RC and final release. - We need to push in major changes earlier so we have time for them to bake. As we get closer to beta/api freeze, we should be more conservative about merging major changes. - - Release process - We will schedule a seperate sub-group - - - ### 22 January 2020 Weekly Meeting - Darian - Extension migration guide: https://github.com/jupyterlab/jupyterlab/pull/7808 - `JLIcon` needs documentation - Steve - Experimenting with JS loaders and transpilers. Will write up findings and recommendations - Investigating a strange bug affecting our browser_check (in core and for extensions) - Jason - Mainly been working on ipywidgets. Upgrading it to JLab 2.0 has worked great. There was a small subtle issue dealing with kernel startup being different now (i.e., no .ready anymore), but it is simpler code now than before, I think. - On ipywidgets, we've switched to GitHub Actions and it is *great*. - Luciano - Finally able to make progress with JupyterLab 2.0 extension migration and trying to look into small ui side effects (e.g. icons, output areas). - Lots of changes related to new KernelManager infrastructure/API. - Will start contributing to Darian's PR and Blog based on my (our) experience. - Released notebook 6.0.3, so it works with Python 3.8 on Windows now! - Max - icon interface - https://github.com/jupyterlab/jupyterlab/pull/7767 - Additional Discussion - RC release this week? - Should we have a separate (non-weekly?) call for Lumino? - Ship UMD in lumino? - https://github.com/jupyterlab/lumino/pull/40 ### 15 January 2020 Weekly Meeting - Tim - Modals in ~~Phosphor~~Lumino for: - https://github.com/jupyterlab/jupyterlab/issues/7039 - A widget whose update allows it's height to change. - We can make a flexible modal class - with a specific class for command pallette - Vidar - Widgets workshop - Some small refactor PRs - Darian - Added Lumino `lm-*` namespaced events, selectors, and `data` attributes to JupyterLab - Made one final 0.1.x release of `@jupyterlab/debugger` before switching to JupyterLab 2. - Working on narrative(ish) blog post for extension migration. Plan on finishing it this week. - Follow up meeting with Kite folks to talk about completion API - Steve - PRs to update nbdime and jupyterlab-git to JupyterLab 2.0 - https://github.com/jupyter/nbdime/pull/508 - https://github.com/jupyterlab/jupyterlab-git/pull/520 - Fixed our binder launch, which lets us use the PR helper bot again - Looking into module types and bundlers for the build system refactor - https://github.com/wolfv/jupyterlab-dynext - Saul - Two meetings coming up on Friday: - RTC Grant Call Friday, January 17, 12-1pm EST - jupyter zoom - Kite Integration Call Friday, January 17, 1-2pm EST - https://zoom.us/j/155447985 - Show what companies funded what work? "Sponosored" branding? (our client wants some marketing) - Eric - [JupyterLab Server as Server Extension](https://github.com/jupyterlab/jupyterlab_server/pull/79) - LabServerApp is a Server Extension - Question: Should APIHandler... be migrated as a HandlerExtension? See [[DISCUSS] Should the base.handlers have their counterpart in extension.handlers? ](https://github.com/jupyter/jupyter_server/issues/173) - WIP: Migrating tests to pytest with `pytest_jupyter_server` (released in [server 0.2.1](https://github.com/jupyter/jupyter_server/releases/tag/0.2.1)) - Favor [fixtures](https://docs.pytest.org/en/latest/fixture.html). - Prolly a complete rewrite of `test_settings_api.py` and `test_workspaces_api.py`. - Alex - Trying to understand how TabBar handles Signals in lumino, would appreciate insight (first caught tabClose signal clears remaining callbacks) - Addional Discussion - Ship UMD in lumino? - https://github.com/jupyterlab/lumino/pull/40 - When should extension author port their extensions? - Announcement - Can extension installers port now? - >> Put this info in the Changelog under an extension Developer heading << Now is the time to check it works locally, open a PR; then for 2.0 merge and release. - How should we recognize companies pouring money into JupyterLab development? - two sigma and bloomberg helped support jlab debugger, this will go into blog post. - README and changelog branding? - For now, write a blog-post with a Jupyter Dev. - JLIcon - Remove backwards ### 8 January 2020 Weekly Meeting - Adam - Introduction - Working Kite - Darian - https://github.com/jupyterlab/lumino/pull/20 CSS selectors / events that are namespaced with `p-`... - Shortcuts update - Debugger update - Steve - Working through the release checklist, updating sibling repos and examples - Fix for linked extensions - https://github.com/jupyterlab/jupyterlab/pull/7728 - Question about JLICon in rendermime-interfaces - end of call - Saul - Real Time Collaboration funding - Chan Zuckerbug Initiative (CZI) Essential Open Source Software for Science, Cycle 2 grant - https://chanzuckerberg.com/rfa/essential-open-source-software-for-science/ - Due FEBRUARY 4, 2020 - Tim - Need help for [File Browser button fix](https://github.com/jupyterlab/jupyterlab/issues/7593). - Brian - Work on triplex id generation for CRDT algorithm. - https://github.com/jupyterlab/lumino/issues/13 - Rebalancing will be needed eventually - datastore and widgets - time to dive in? - The lumino name has a nice property => lmno - Jason - working on ipywidgets. The new jlab beta works great! - Experimented with VDOM (lumino) to render widgets - Input checked state is not reflected in HTML dom, need to reset checked state on render refresh. - https://reactjs.org/docs/forms.html#controlled-components - Font (/Fort) Awesome in IpyWidgets - Max - state of the icons - https://github.com/jupyterlab/jupyterlab/pull/7700 - state of ui components - need to decide on styling system - typescript 3.7 issue in detail - will have to go into the migration guide - https://github.com/jupyterlab/extension-cookiecutter-ts/pull/52#issuecomment-571715056 - backports for extensions - https://github.com/jupyterlab/jupyterlab-git/issues/517 - Further Discussion - Partnership with JupyterLab-Kite - Existing Jupyterlab LSP work: https://github.com/krassowski/jupyterlab-lsp - - JLICon in rendermime-interfaces: Brings in a dependency on ui-components and React - CZI Grant - Brian knows PM for grant so we could run things by them - Saul to set up time for people to meet: - Jason - Steve - Tim - Brian - Saul - Update on Widgets and Datastore - ### 2 January 2020 Weekly Meeting - Tim - No big updates - Darian - Keyboard shortcut UI: - Updated to use JupyterLab 2.0 and Lumino - Found some issues in Firefox, addressing them, still hoping to merge into `master` - Added a `jp-mod-loading` class to file browser for initial load, saving one round-trip in `/tree` URLs - Steve - Cut a beta release before the holiday but it was broken - We need to cut a new beta this week - Released `@lumino/virtualdom` with updates for https://github.com/jupyterlab/jupyterlab/pull/7700 - Eric - Will relaunch work on [JupyterLab as Server Extension](https://github.com/jupyterlab/jupyterlab/pull/7416) and [JupyterLab Server as Server Extension](https://github.com/jupyterlab/jupyterlab_server/pull/79): Ensure unit tests pass (maybe using [jupyter_server pytest plugin](https://github.com/jupyter/jupyter_server/pull/162)). - [WIP] [jupyterlab-react-widgets](https://github.com/datalayer/jupyterlab-react-widgets) - Thx @telamonian for [#2](https://github.com/datalayer/jupyterlab-react-widgets/pull/2) - Jason - Fixed some issues in master - Shifted focus to ipywidgets in preparation for our dev sprint next week - Continued Discussion - ~~More generic property inspector - is there an issue for this?~~ - https://github.com/jupyterlab/jupyterlab/issues/7686 - Fixed in https://github.com/jupyterlab/jupyterlab/pull/7718 - ~~Split out from coreutils (https://github.com/jupyterlab/jupyterlab/issues/7615)~~ (fixed now) - ~~TypeScript 3.7 (cf. https://github.com/jupyterlab/lumino/pull/27#issuecomment-563999676)~~ - Typescript 3.7 issue? https://github.com/microsoft/TypeScript/issues/33939 - We decided we could go ahead and upgrade jlab 2.0 to TS 3.7. - Debugger 0.1 and 0.2 plan - Shortcut editor UI. - Still need RC, Blogpost, documentation updates. ### 18 December 2019 Weekly Meeting - Vidar - Strict nulls! - Steve - Working through 2.0 beta issues - Open PRs - [Release cleanup](https://github.com/jupyterlab/jupyterlab/pull/7614) - [Make session dialogs configurable](https://github.com/jupyterlab/jupyterlab/pull/7618). Overlaps with https://github.com/jupyterlab/jupyterlab/pull/7647 - Darian - StateDB bug fix. Reviewing coreutils. - Shortcuts and Debugger - Brian - Tim - 2.0 Design issues - Submitted Community workshop for JupyterLab 3.0 Sprint. - Max - hpass - a pass thru vdom element in lumino: https://github.com/jupyterlab/lumino/pull/29 - Jason - Finalizing the [services refactor](https://github.com/jupyterlab/jupyterlab/pull/7252) - Steve and Vidar and I worked through most of the changes during the dev meeting - (most) tests passing now, doing some by-hand integration testing - I think almost to the point where it can have another review pass and merged - the longer we wait, the more painful the continuous rebasing is :) - Discussion about removing vega 4: https://github.com/jupyterlab/jupyterlab/issues/7523 - Steve will take over this - **General Discussion** - More generic property inspector - is there an issue for this? - Split out from coreutils (https://github.com/jupyterlab/jupyterlab/issues/7615) - TypeScript 3.7 (cf. https://github.com/jupyterlab/lumino/pull/27#issuecomment-563999676) - Typescript 3.7 issue? https://github.com/microsoft/TypeScript/issues/33939 - Debugger 0.1 and 0.2 plan ### 11 December 2019 Weekly Meeting - Saul - Output search UI https://github.com/jupyterlab/jupyterlab/pull/7258 demo! - To match Tim's mockups pixel perfect requires refactoring some the existing UI - Merge in this feature and move that work to a new issue? - Jason - Finishing up kernel services refactor - Steve - Working on the 2.0 release and associated changes to lumino - Cut new versions of a few lumino packages - Cut security releases of 1.1, 1.2, and 2.0a - Research into loaders and module formats - AMD as our format - Use system.import - systemjs as our loader - https://github.com/jupyterlab/jupyterlab/issues/7468#issuecomment-564650118 - Vidar - Strict null checks incoming (since we now have partial JSON structures in Lumino). Starting with coreutils to do this piecewise (limits risks of merge conflicts, and piecewise reviews are better) :+1: - Want to help Jason get the kernel services refactor done - Luciano - Working on dependency updates - Updates to script are ready to review [#7599](https://github.com/jupyterlab/jupyterlab/pull/7599) - Updates to dependencies are mostly done, pending codemirror build issues [#7590](https://github.com/jupyterlab/jupyterlab/pull/7590) - Tim - Wrapping up UI tweaks to include in 2.0. - Final UX review for Celltags - Max - Celltags is ready to go in. Try it out! - https://github.com/jupyterlab/jupyterlab/pull/7407 - Alex - Opened PR [#7611](https://github.com/jupyterlab/jupyterlab/pull/7611) addressing transient file editor configs as discussed last week - General Discussion - Refactor coreutils somewhat? Polling is upstreamed to Lumino, should we extract any other parts into separate packages? - Community Workshop CFP deadline Dec 15! - When is 2.0 RC target? 20 Dec 2019 Beta, RC 6 Jan 2020. - ipykernel vs xeus https://github.com/jupyterlab/debugger/issues/274 ### 4 December 2019 Austin Dev Meeting Edition - Packaging - RTC [Find more info here](https://hackmd.io/kwWDDaRnR2eOxpXF18Arjw) - Lumino datastore and existing RTC libraries. - Current issue with lumino datastore - Unpaired surrogates - ID generation - Where to put all the code we're working on? - Should we require node on the server side? - We need a definitive yes or no on whether to include this. - Pros: - Enables us to move notebook state to server. - Can forward kernel messages to the datastore on the server side. - Can have a server side datastore client. - Datastore is written in nodejs. - Cons: - Have to ship node. - Protocols on top of REST - We can keep moving in the same direction for now, and move it to python later if we need to. - ID Generation - Datastore utils package is bisecting the inverval? - SQRT is making things more uniform, but not fixing altogether - We could use a uniform spacing for a set of ID's across a given range. - Next steps: - Keep exploring in node for now. - UI Components - Add Storybook - Remove Blueprint - Add Material UI for complex components only. (Eg. dialogue boxes) - Pros: - Gives us access to much better modal dialogues. - Porting is less work than building certain complex components from scratch. - Cons: - Another dependency - Because they're meant to be general purpose they're extrodinarily complex, but they're complex enough to use in ways that completely break accessibility. - Also there's a burden that's a basic button class we have in JupyterLab it's very small. - Blueprint and Material UI buttons have many more props. - What we want in a JupyterLab UI Framework. - Simple components with small # of props. - Possible to work with Accessibility. - Specifically applies to JupyterLab only, doesn't need to be general purpose. - Next steps - Add Storybook - Go through and remove blueprint components with Custom JupyterLab components. - Brian has a design contact for accessibilty at Amazon that can review components. - Don't bring bagage from Blueprint Props into the new components. - Future Steps - It's not objectionable to use Material UI for more complex components that would require a lot of work for us to replicate. - Recording notebook timings - Currently there's a notebook metadata option to record timing. - New step will be having a Jupyterlab-wide setting to turn notebook timings on or off. - ### 20 November 2019 - Tim - Continued discussion from last week: - Tests: Azure, Github, Travis? - Darian - https://github.com/jupyterlab/jupyterlab/pull/7147 is stuck and I would like help, please. - Steve - Created and released lumino packages 🎉 - Checklist to move over to using lumino - We are blocked on using them in JupyterLab until we have API docs for lumino - Yarn resolutions - Update names in jupyterlab - Saul - Speccing out server side datastore package https://github.com/Quansight/jupyter-datastore - Vidar - Looking further at api-extractor / api-documenter. Probably going to try for lumino first, then lab afterwards if applicable. - Max - typescript source maps - fix for locally installed extensions - https://github.com/jupyterlab/jupyterlab/pull/7541 - how should we fix the sourcemaps we currently ship in the npm packages? - This has already been fixed and rebroken at least once before - https://github.com/jupyterlab/jupyterlab/pull/1655 - https://github.com/jupyterlab/jupyterlab/pull/1657 - cell output search - PR mostly done, but UI needs work - https://github.com/jupyterlab/jupyterlab/pull/7258 - I can confirm: I'll be at the dev meeting in Austin! - also giving a talk at pydata - Brian - Working with Steve on the lumino fork (ok, I just talked to him) - Will be remote for the Austin meeting. - Should we commence a weekly lumino call? - Let's begin to open issue on lumino to spec out where we want to take it in the short term and long term. - Race conditions in the Jupyter server. - Jupyter Community Workshops! Deadline is 12/15 for submissions. - JupyterLab? - Accessibility? - Maintenance (tech debt)? - Accessibility critical mass. - https://github.com/jupyter/accessibility - https://discourse.jupyter.org/c/special-topics/accessibility - Jason - Continuing work on services kernel refactor: https://github.com/jupyterlab/jupyterlab/pull/7252 - We upgraded to TS 3.7. Enjoy null coalescing and optional chaining! For example, `this.session?.kernel?.name ?? 'No kernel'` - PyData Austin - Additional Discussion Topics - `@jupyterlab/debugger` in core for 2.0? - Targetting 0.1 release for December (depends on having the xeus-python Kernel). - - `@jupyterlab/shortcutui` in core for 2.0? - Discuss [Austin meeting](https://hackmd.io/kwWDDaRnR2eOxpXF18Arjw) if we have time. - Daily 10 AM (Austin Time) meetings to set up for the day on https://zoom.us/tgeorgeux (Excluding Tuesday) - Tuesday 10am (CT) is a presentation on JupyterLab to a seminar over video conference - Add video channels to topical discussion as we can. - Should we link back to phosphor issues on lumino? - For small discussions, probably not. - For larger discussions, case by case. - Lumino Readme Copy (or perhaps a very abbreviated mention is in the readme, with something like this in the changelog?): - Lumino was originally developed as a framework for JupyterLab, much of the code originated in the PhosphorJS repo. The project is officially a part of the JupyterLab org now! - Lumino was originally developed as a foundation for applications like JupyterLab under the PhosphorJS name. When the main developer of PhosphorJS retired from open source in November 2019, the other PhosphorJS maintainers continued development as the Lumino project as part of Project Jupyter, under Jupyter governance and Jupyter code of conduct. - Lumino is a toolkit for building extensible and high-performance browser applications like JupyterLab. Lumino is a Jupyter project, under Jupyter governance and Jupyter code of conduct. Lumino was formerly known as PhosphorJS. ### 13 November 2019 - Eric - Working with @jtpio on [jupyterlab-extension-examples](https://github.com/jtpio/jupyterlab-extension-examples) - Follow-up on https://github.com/jupyterlab/jupyterlab/issues/7273 - Vidar - Been looking at [API Extractor (rush-stack)](https://api-extractor.com/) - Steve - Absorbing Phosphor: - https://github.com/jupyterlab/team-compass/issues/28 - Jason: release a new version with the exact version codes. - Use yarn resolutions to force a transition in JLab 2.0 - Tim - Continued work on Design System. - Cleaning up [icons.](https://www.figma.com/file/9QnGjW1px8SjvXVJMssPkY/_Design-Atoms?node-id=0%3A1) - Brian - Update on icon bug in 1.2.x - TS/TSX config for jp-babel kernel - Developing JL extensions in JL itself? - https://github.com/jupyterlab/jupyterlab/issues/7469 - Luciano - Austin dev meeting participants - Does anyone know the status of jupyterlab-monaco extension? - For governance, if one has a proposal, should wait for Austin dev meeting ? - Saul - JupyterLab governance, exploring Node JS model with working groups. - https://medium.com/the-node-js-collection/healthy-open-source-967fa8be7951 - Will talk to JupyterHub devs as well about theirs - Goal is come to in person meeting with enough background to end week with proposal for JL governence - Let's call this "team structure" instead of governance. - To encode existing power structures and decision making process. - Don't have BDFL, instead have group. - Jeremy - Iterations on the debugger - 0.1.0 milestone for the first release - Development and Binder link: https://github.com/jupyterlab/debugger - Jason - 1.2.3 released - Going back to working on kernel refactor for 2.0 - JLab and Brookhaven meeting at dev meeting (https://www.jlab.org/indico/event/307/, we are the 3 Dec spot): 20-30 minute presentation, 15-30 minutes for discussion - Jupyter Community Workshop [call for proposals](https://blog.jupyter.org/jupyter-community-workshops-call-for-proposals-for-jan-aug-2020-710f687e30f4) (due 15 Dec) - TS 3.7 is out! https://github.com/jupyterlab/jupyterlab/pull/7428 Further Discussion: - (Carry over to next week) The future of tests: - Azure? Travis? Github? - Phosphor fork name possibilities (needs to be available as an npm org) - @sol - @solar - @lumino - @lightstick - @glowstick - @glow - @lumo (esparanto) - @lux (latin) - @luce (italian) - @marama (maori) ### 6 November 2019 - Eric - jlab on jupyter_server with nbclassic shim: [jupyterlab-server#79](https://github.com/jupyterlab/jupyterlab_server/pull/79) and [jupyterlab#7416](https://github.com/jupyterlab/jupyterlab/pull/7416) ready for review - Prints warning if NotebookApp configs still used - need to sync with nbclassic - Needs [jupyter_server#133](https://github.com/jupyter/jupyter_server/pull/133) for subcommands. - Vidar: - Issue responses - Saul: - JupyterLab Governance clone JupyterHub? - Dev Meeting in December will be a good time to discuss this. - https://jupyterhub-team-compass.readthedocs.io/en/latest/team.html - https://jupyterhub-team-compass.readthedocs.io/en/latest/team/member-guide.html - - Tim - Agenda for Dev Meeting. - https://hackmd.io/kwWDDaRnR2eOxpXF18Arjw - Do some rough Prioritization Further Discussion: - Phosphor repo archived. - Team Compass issue to be followed up by gitter comments. ### 30 October 2019 - Vidar: - RTC sprint with Darian - Jupyter server for 2.0? - Darian - RTC sprint with Vidar - Short debugger update - Steve - Exploring the concept of environment-aware JupyterLab - Max - Extension manager improvements? - Vidar: There are conceptual improvements. If there was another way to register a python package it would work better, not sure if there's a clean way to do it. - There is a PR that could be cleaned up and merged that would help. [pip packages should not include builds] - https://github.com/jupyterlab/jupyterlab/issues/6228 - https://github.com/jupyterlab/jupyterlab/pull/6277 - Tim - Working on Design Debt. - Adding "atoms" to JupyterLab Design System. - Can we add the design assets to the repo? - Yes. Let's tie them to JupyterLab Releases. - Mike - Working on jupyterlab-lsp, will open an issue on the future of the integration with Jupyter project organizations / JupyterLab core - Discussion Points - Question about `@jupyterlab/coreutils#Poll` *et alia* possibly in PhosphorJS: Next time there is a major version change in `@jupyterlab/coreutils`, move `Poll` and its relatives into a separate `@jupyterlab/poll` package. ### 23 October 2019 - Tim - Design system progress: [Elevation](https://www.figma.com/file/aB4s6Y7rgb7DLl2O9pZwKp/Elevation?node-id=0%3A1), [Search Related](https://www.figma.com/file/EUhoxdn5TBn4qf4eCxaw5J/Search-related?node-id=0%3A1), [Input Field](https://www.figma.com/file/xC2IPevB5ErQyKd2JRREt4/Input-Field?node-id=0%3A1), [Toolbard Specific Styling](https://www.figma.com/file/CBqTcB8Pu26DXeVvstkZ23/Toolbar-Specific?node-id=0%3A1), [Cell Specific](https://www.figma.com/file/RCOmTMKsvWw820xzKdPMZ2/Cell-Specific?node-id=0%3A1), and a few others. - Protons for Light mode complete. - Next Step Atoms for light mode. - Eric - Demo of JupyterLab as jupyter_server extension, so that we dont depend on notebook repo - ~~Vidar~~ Jason - 1.2 https://github.com/jupyterlab/jupyterlab/milestone/38 - Discussion surround the name, is 'log console appropriate?' - Log console discussion, summarized [here](https://github.com/jupyterlab/jupyterlab/issues/7386#issuecomment-545553510). Once those changes are in for the log console, release the 1.2RC. - Steve - Onboarding to new role focusing more on core JupyterLab work - Max - "passthru" vdom elements in phosphor - lets you blend React into phosphor vdom - https://github.com/phosphorjs/phosphor/pull/437 - bundling `.ts` source files with a Python serverextension: @jupyterlab/git - https://github.com/jupyterlab/jupyterlab-git/issues/341 - https://github.com/jupyterlab/jupyterlab-git/pull/415 - https://github.com/jupyterlab/jupyterlab-git/issues/430 ### 15 October 2019 * Tim * Could use feedback on [Icon Font](https://github.com/jupyterlab/jupyterlab-data-explorer/issues/62P) before Friday. * Steve * reviewed and merged updates to Phosphor datagrid with a new release - [Undo/redo](https://github.com/phosphorjs/phosphor/pull/422), [Undo/redo example](https://github.com/phosphorjs/phosphor/pull/425) * Saul * Not much * Phoila release? * [~~meta pr~~](https://github.com/jupyterlab/jupyterlab/pull/7377) * Collaboration with VSCode team * https://gitter.im/jupyterlab/jupyterlab?at=5da085bb80e62056e4e6e0d3 * https://github.com/microsoft/vscode-python/blob/5c1d2bcc83599f1964f18bd557e900e85484336c/src/client/datascience/jupyter/jupyterServer.ts#L28 * Vidar * Another week of reviews only :'( * Hoping to move Lab to strict null checks for 2.0 * [Bug fix for 1.1.x](https://github.com/jupyterlab/jupyterlab/pull/7374), are we still doing those? Not critical... * Luciano * Unrelated Notebook question * Ideas on how to update JQuery if that is not available in bower * https://github.com/components/jquery/pull/63 * Try unpkg? e.g. https://unpkg.com/jquery@3.4.1/dist/jquery.js * Try [jsdeliver?](https://github.com/jupyter/notebook/blob/ed96937401a0a551cb0eeafcde657b9e9c71400c/bower.json#L9) * Jason * General plan is to work on these things in order: * ipywidgets bug fix (vidar reviewing) * jlab 1.2 * kernel refactor in jlab * ipywidgets 8 * Discussion * 1.2 release - tracking down one more issue with the log console widget and layouts restoring * in-person dev meeting: in Austin Dec 2-6 * Outline for notes https://hackmd.io/@_4xc7QhhSHKODRQn1uiulw/rJErUpEKS/edit * meeting purpose: The in-person JupyterLab meeting is an intensive code sprint focused on JupyterLab 2.0. We have a limited number of spots, with a goal of producing a JupyterLab 2.0 release candidate by the end of the week as well as a roadmap for the future. * Current attendees * Steve * Tim * Jason * Zach * Saul * Luciano * Darian * Server meeting recap: * Two major updates to separate out Notebook from server. * 7.0 would shim all the Rest APIs and endpoints, will throw warning that these shims won't work in the next major release. * 8.0 depends on server and removes server from notebook repo. ### 09 October 2019 * Vidar: * Mostly reviewing various bits and pieces. * Saul had an interesting point about making it easier for rendermime renderers who use Comm to get access to that, vs phoila (Phosphor Viola) https://github.com/vidartf/phoila/issues/7 * Steve * Issues with the [resolutions field](https://github.com/jupyterlab/jupyterlab/pull/7304) * [Phosphor and React](https://github.com/phosphorjs/phosphor/issues/302#issuecomment-540030092) * Jason * Continuing work on [kernel architecture refactor](https://github.com/jupyterlab/jupyterlab/pull/7252) * Tim * Ongoing work on protype icon system for [MIME types](https://github.com/jupyterlab/jupyterlab-data-explorer/issues/62). * If this works out we will have a better lookings icon set for JupyterLab. * Max * started work on [the one true way to consume icons in jlab](https://calpoly.zoom.us/j/2261836383) * [PR for "pass thru"](https://github.com/phosphorjs/phosphor/pull/437) vdom element in Phosphor * Discussion * in-person meeting venue * IBM Austin space available for the week of Dec 2-6. * PyData Austin is Dec 7-8 * There is close food and a local contact. * Jupyterlab team hasn't been here yet. * **We have *tentatively* decided on Austin, waiting to hear from others not on this call.** * Bloomberg San Francisco space available for the week of Dec 2-6. * Will have catered Breakfast and Lunch. * Potentially JPMorganChase in NYC, but unconfirmed. * Jupyterlab team hasn't been here yet. * 1.2 release * Jason will put some cycles into 1.2 release to include log console and maybe some very high priority PRs. * [Comm access for Phoila](https://github.com/vidartf/phoila/issues/7) *

Syntax	Example	Reference
# Header	Header	基本排版
- Unordered List	Unordered List
1. Ordered List	Ordered List
- [ ] Todo List	Todo List
> Blockquote	Blockquote
Bold font	Bold font
Italics font	Italics font
~~Strikethrough~~	~~Strikethrough~~
19^th^	19^th
H~2~O	H₂O
++Inserted text++	Inserted text
==Marked text==	Marked text
[link text](https:// "title")	Link
![image alt](https:// "title")	Image
`Code`	`Code`	在筆記中貼入程式碼
```javascript var i = 0; ```	`var i = 0;`
:smile:		Emoji list
{%youtube youtube_id %}	Externals
$L^aT_eX$	L^aT_eX
:::info This is a alert area. :::	This is a alert area.