Weekly Dev Meetings: Jan-Jul 2021

[jasongrout]

Here is a record of the agenda/minutes for our weekly meeting. Everyone is welcome to join.

Let's avoid using this thread for discussion. If you'd like to discuss something in the minutes, open a separate issue and reference this thread.

Meeting Notes

• 4 Aug 2021
• 28 Jul 2021
• 21 Jul 2021
• 14 Jul 2021
• 7 Jul 2021
• 23 Jun 2021
• 16 Jun 2021
• 09 Jun 2021
• 02 Jun 2021
• 26 May 2021
• 19 May 2021
• 12 May 2021
• 05 May 2021
• 28 Apr 2021
• 21 Apr 2021
• 14 Apr 2021
• 07 Apr 2021
• 31 Mar 2021
• 24 Mar 2021
• 17 Mar 2021
• 10 Mar 2021
• 03 Mar 2021
• 24 Feb 2021
• 17 Feb 2021
• 10 Feb 2021
• 03 Feb 2021
• 27 Jan 2021
• 20 Jan 2021
• 13 Jan 2021
• 06 Jan 2021

[jasongrout]

06 Jan 2021 Weekly Meeting

• Isabela

  • Happy new year!
  • Congrats on 3.0!
  • How is everyone?
  • Accessibility meeting is next week.

• Jason

  • JupyterLab 3.0 is out, still some things to do, though: 3.0 Release Plan jupyterlab#8038
  • Hacker News: https://news.ycombinator.com/item?id=25647034
  • Blog post: https://blog.jupyter.org/jupyterlab-3-0-is-out-4f58385e25bb

• Vidar

  • Should I be using _jupyter_labextension_paths for extensions, given Support pure npm dynamic packages jupyterlab#8854 ? Is it recommended / optional ?

• Darian

  • JupyterLab 4.0 product management process
    • small meeting for realistic ideas with broad targets
    • larger meeting new features and product roadmapping
      • this meeting need facilitation

• Luciano

  • Help spreading the word about Survey
    • Add link to Jupyter 2021 survey jupyter/jupyter.github.io#396
  • This should help with prioritizing featureset for next releases

• Discussion

  • 3.1 triage: https://github.com/jupyterlab/jupyterlab/milestone/58
  • How is everyone?

[jasongrout]

13 Jan 2021 Weekly Meeting

• Isabela

  • How is everyone?
  • #9335 first step PR for meeting accessible color contrast standards. I'm looking for review and/or next steps needed.
  • The JupyterLab accessibility meeting will be happening right after this. All are welcome!
  • The Jupyter community call is coming up in two weeks (Jan 26 (your timezone)). Sign up to share on the agenda. Does anyone want to share about 3.0?
  • I'm adding the proposed settings UI to the items for further discussion. Just want to check in about it.

• Eric

  • Trim large notebook outputs for better performance
  • Plan to release 2.3.0rc0

• Brian

  • Happy new years :-)
  • New RTC funding for QuantStack

• Jason

  • Example overhaul
  • 3.0.4 released

• Alex

  • Working on updating nbdime and git extensions to 3.0, the git extension work needs review and feedback. nbdime PR git PR
  • Settings UI work is still on my back burner, others are still welcome to jump in and start the work without me.

• Discussion

  • Introductions and Welcome!
  • Are there any plans for moving forward with the proposed settings UI #8148?
    • This will be moved to next week because one of the main people interested is not here. Max may have some work started.
  • initial planning meeting for 4.0 roadmap
    • make sure we talk about editors at this meeting.
  • What is the status of implementing directed-acyclic-graph-like notebooks? I found [#1175]
    • One of the Jupyter interns built a reactive DAG kernel: https://github.com/jupytercalpoly/reactivepy that has a similar execution model as observablehq.
    • Julia Pluto is another example
    • Dataflow Notebook: https://dataflownb.github.io/, https://www.youtube.com/watch?v=5MmXs6m3JcE
    • https://github.com/stitchfix/nodebook
  • CodeMirror next: "The project is in the beta phase—there's a stable interface, but small breaking changes might still happen. It is being used in production in a few mid-size systems, but is not as battle-tested as the old version."
  • 2.3 and 3.1
  • Questions about IntelliSense features: https://github.com/krassowski/jupyterlab-lsp adds more IntelliSense features, ?/??/Shift+Tab for documentation
    • There is also https://github.com/kiteco/jupyterlab-kite

[jasongrout]

20 Jan 2021 Weekly Meeting

• Alex

  • nbdime and git extension betas supporting 3.0 have been released
  • Elyra 2.0 should released in the coming days (supporting 3.0)

• Isabela

  • January's community call is next Tuesday at 9am Pacific (your timezone)! Sign up on the agenda if you want to present.
  • JupyterLab accessibility meeting is next Wednesday!

• Jason

  • Continuing to work on 3.0 regressions, cookiecutters, etc.

• Martha

  • #9622 Accessibility PR for aria roles
  • #9487 Different accessibility PR, looking for feedback

• Eric

  • #9594 Trim large notebook outputs for better performance. Once merged, release 2.3.0rc0

• jd41

  • brief update on directed acyclic graph-like notebook vs dataflow notebook (see last week's meeting)

• Discussion

  • 4.0 planning process
    • Please read this rubric document and use it as a guide to filling out this spreadsheet for new 4.0 features.
    • This is a placeholder issue for JupyterLab 4.0

[jasongrout]

27 Jan 2021 Weekly Meeting

• Isabela

  • How is everyone?
  • Is anyone interested in guest hosting a community call? It's probably good for sustainability if it isn't all known by one person.
  • JupyterLab accessibility meeting is directly after this one!
  • @jtpio and I are trying to help close the JLab 3.0 issue. Come join us!

• Gonzalo

  • Fix some issues with translation of backend extensions. Still investigating the best option.
  • jupyter lab modifies the locale env variables like LANG jupyterlab#9672
  • 2.3.0rc0 review. Performance improvements.
    • PRs merged
    • Installing 2.3.0rc0!

    conda create -n jlabrc jupyterlab=2.3.0 -c conda-forge/label/jupyterlab_rc
    conda activate jlabrc
    jupyter lab

    pip install --pre jupyterlab==2.3.0rc0

• Jeremy:

  • JS Cookiecutter updated to the new distribution system
    • should TS and JS cookiecutters be a single cookiecutter?
      • @jasongrout: initial thoughts are that combining these would complicate the cookiecutter so much that it might not be worth it, i.e., it would be simpler to have two repos, but would be happy to look at it if someone wants to try it.
  • Make the file browser plugins more reusable: Make the filebrowser plugins more reusable jupyterlab#9667
    • will help reuse the component in lab-based apps such as JupyterLab Classic
  • Move flaky tests to a separate workflow on CI: Move flaky tests to a separate workflow on CI jupyterlab#9677

• Jason

  • A few more bugfixes for 3.0, which still need to be released (#9674 needs review still)

• Eric

  • 2.3 rc needs feedback.

• Discussion

  • Welcome new people
  • PR adjusting JLab colors for accessibility (#9335). What else needs to be done? (Isabela)
  • Branching for 3.1
    • Some 3.1 PRs are waiting to be merged. Master is still on 3.0.x
    • Jason will branch off 3.0.x so master can move to 3.1: https://github.com/jupyterlab/jupyterlab/tree/3.0.x
    • Steve will migrate the 3.0.x changelog to 3.0.x branch
    • We'll wait until #9674 is merged and backported to cut the next 3.0.x patch release
  • Recording these minutes: Weekly Dev Meetings: Jan-Jul 2021 #117
  • 4.0 Planning
    • Google Form Version

[jasongrout]

3 Feb 2021 Weekly Meeting

• Gonzalo (in another meeting, bump me as needed!)

  • Reminder on 2.3.0rc0 testing :)
    • https://github.com/jupyterlab/benchmarks/tree/master/examples/from-benchmarks
  • Strategy for moving to 3.0/master?

• Isabela

  • We had three PRs for accessibility merged in the last week! Just wanted to announce and congratulate the team.
  • JLab accessibility meeting will be next week directly after this one.

• Jeremy

  • JupyterLab Desktop App for 4.0? 🚀
    • Continue from Supporting most of the features jupyterlab-desktop#186
    • Added to the 4.0 spreadsheet
  • Move JupyterLab Classic to the jupyterlab organization: Move RetroLab to the jupyterlab organization #119
    • To get more people involed
    • To help sunset the Classic Notebook
    • Strengthen the concept of JupyterLab Distributions and the tooling around it (leveraging prebuilt extensions)

• Loic

  • View HDF5 attributes in jupyterlab-hdf5: Added basic display of attributes as context menu action jupyterlab-hdf5#80
  • Improvements to the backend

• Releases

  • 3.0.7 released, contains some bugfixes
  • 3.1.0alpha0 is being released (pypi release done, conda-forge pending)

Discussion

• Introductions
• Status of Update for JLab 3.0 mimerender-cookiecutter-ts#21 ?
• Keyboard shortcuts for moving cells (Add default shortcuts for moving cells jupyterlab#9031) (Krishna)
• 4.0 Planning
  • Google Form Version
  • Please provide issues or a JEP (JupyterLab enhancement proposal) for each potential roadmap item
  • This will be due by the 17 Feb dev meeting so we can choose how to move forward with 4.0 planning
  • The goals of the planning process are:
    • Provide a way for developers to communicate, coordinate, and consolidate development of major features
    • Message to the public what major features we are working on for 4.0
    • Commit to developers working on features that they are in scope for 4.0
    • Establish a timeline for release phases (alpha, beta, rc, final)

[jasongrout]

10 Feb 2021 Weekly Meeting

• Isabela

  • Hi everyone! What’s your favorite color?
  • Who is running Jupyter social media? Who should I reach out to?
    • Ana Ruvalcaba, Sylvain Corlay, Matthias Bussonnier are some people that are actively doing things with Jupyter social media
  • Our JupyterLab accessibility meeting is today right after this meeting.
  • February's Jupyter community call will be on Tuesday two weeks from now. Sign up on the agenda if you would like to share!

• Vidar

  • Not able to find the new issues I care about on the repo anymore (too many issues). Any tips or tips for how to manage would be welcome (at the end). For now I've unwatched.
    • See also #9714

• Alex

  • Is there a timeframe for releasing nbdime with 3.0 support?

• Kevin

  • Jupyter shared editing implementation
  • Will open PR to Jupyterlab next week. Current status: [WIP] Collaborative editing using Yjs QuantStack/jupyterlab#1
  • Demo link: https://notebooks.gesis.org/binder/jupyter/user/quantstack-jupyterlab-i3g2x6z5/lab-dev/lab/tree/Untitled.ipynb?token=Y_wTa-IMRKavQFFsTEDAQA

• Brian

  • Yjs + React utilities
  • I have built some react hooks that make it easy to use Yjs as a data model layer for react component hierarchies.
  • Going to open PRs to this repo: https://github.com/yjs/y-react

• Gonzalo

  • How is 2.3.0rc0 testing going :) ?
    • Vidar: No weirdness
    • Darian: No weirdness
  • Timeline: 1 week.
    • Release 2.3.0

• MJ Zhang

  • I'm trying to set a cache-control header through the server extension, but had some issue #9762. With the advice from Brian, I'm here to look for more insights.
    • To follow up to discuss the legacy code https://github.com/jupyter-server/jupyter_server/blob/master/jupyter_server/base/handlers.py#L662

• Mike

  • Planning completer API refactor #9763, seeking wishlist items from the team (use cases, missing features)

• Jason

  • Looking at how we handle "trusted" status (#9765). Anyone want to discuss this later this week?

• Max

  • Started concrete work on new filebrowser UI implementation
    • https://github.com/telamonian/tree-finder

  

  tree-finder

Further Discussion

• A part of making JupyterLab accessiblity efforts sustainable will be adding relevant tests to JupyterLab. There's nothing to show right now, but I wanted to give an early heads up since this will eventually affect all contributors. #9742 (Isabela)
• How do people manage the high amount of issues? How do find the things that are relevant to you as they come in? (see also #9714)
  • https://octobox.io/
  • https://github.com/minrk/all-my-pulls
• Reminder that the 4.0 Planning items are due by next Wednesday. Please make sure each item has a link elaborating on that specific item (like to an issue, etc.)
• How to not have RTC become a project collaboration problem
  • Hopefully this discussion can happen on the bi-weekly RTC call

[jasongrout]

17 Feb 2021 Weekly Meeting

• Survey Initiative [Layne, Luciano, Isabela, Brian, Tim]

  • Opening statement. Characterize threats. Why action needed? Ran survey to get info to guide actions. Half baked recommendation.
  • Aggregate survey trends.
  • Use cases by frequency. Satisfaction by use case versus competitive tools.
  • Git permissions for github.com/jupyter/surveys
    • From chat, submit pr and will be merged
  • Future: which user segments to learn more about?
    • [a] the disatisfied & disenchanted, [b] JupyterHub & collaborators, [c] pain area (e.g. scale, data wrangle) vs competition.
  • Future: keyword analysis of open text responses.

• Isabela

  • February's Jupyter community call is next Tuesday, the 23rd at 9am Pacific (your timezone). You can find more info on the Jupyter Discourse. Hope to see you there!

• Eric and Pierre

  • RTC Demo - Collaborative Notebook and FileEditor
    • Using Collaborative ModelDB
    • Collaborative Kernel Manager for next Monday
    • Multiuser with GitHub Authentication (pluggable)
  • PR on its way
    • Better to first align with other existing PR (cfr backwards compatibility + open to other CRDT libraries)?
    • Please join next Jupyter RTC meeting on Monday 22 Feb 12:30 EST (Local time) https://github.com/jupyterlab/rtc
      • Backwards compatible (events structure/content, uses existing collaborators classes) => Demo with LSP extension is planned.
      • Custom ModelDB for pluggable RTC algorithms
        • Automerge is used for now
        • Y.js can be added
    • Will also include
      • jupyterlab-iam (identity and access management) providing permissions on kernels for the collaborators
      • jupyterlab-observables-extension: to allow users to choose his collaboration provider

• MJ

  • I just want to say thanks to you folks for the quick fix for the Cache-Control header issue #9762 I brought up last week.

Discussion

• Status of file openers without content fetching: Allow file openers by to accept URLs jupyterlab#5885 and Add null fileformat jupyterlab#7596
• Scipy 2021 Virtual Conference talk deadline: 22 Feb
  • Martha and Alex are planning to submit a tutorial
  • Alex submitting a talk about extensions (including lab 3.x extensions)
  • Layne might submit talk about survey findings
  • Max submitted a proposal about accessibility work in JupyterLab
  • Anyone else wanting to collaborate, please open an issue on the team compass
• JLab 4.0 Planning items
  • Deadline extended to account for more info being available around the survey. To have a helpful discussion, all proposals need to have all columns filled out before next week's meeting (Wednesday the 24th).
  • Primary outcome for the roadmapping:
    • Commit to developers that something is in scope for 4.0
    • Communicate to public what we are planning for 4.0
    • Decide a timeline for release milestones (alpha, beta, rc, etc.)

[layne-sadler]

@jasongrout i followed through in submitting a scipy abstract.

[jtpio]

24 Feb 2021 Weekly Meeting

• Isabela
  • Congrats on closing the JupyterLab 3.0 issue! It makes me so happy to see that wrapped up. Special thanks to @jtpio for finishing the last to-dos.
  • Recent Jupyter survey data has been submitted as jupyter/surveys #7.
  • We need a private place to keep the emails collected for follow-up interviews. Can we get it in the rumored NumFocus-run Jupyter Dropbox?
    • We have official Google Drive shared drives through NumFOCUS, the team can work with Brian to get access.
• Layne (2min)
  • Aggregated & ranked (pains, use cases, competitive str./weak) to facilitate roadmap decision making. Ranked pain points to help w roadmap #121 .
  • Comparing top use cases and competition indicates where to focus long term -> call for brainstorm on "documenting research."
• Backport initial page load performance improvements to JL 1.2.x jupyterlab#9870

Jupyter roadmap discussion (Brian to attend starting at 9:15am)

• https://docs.google.com/spreadsheets/d/1r6_ySd18xZwfPexdmlkdFhHUWynaza0zXjrxMMIoLWw/edit#gid=0
• https://hackmd.io/MXuxSIhfTDuulGuCfpqICA
• Approach:
  • For each row:
    • Discuss and answer questions about the items
    • Discuss reach, impact, effort scores
    • Vote on the scores using zoom chat and average as needed
    • Ask if there are other people who are interested in working on the item

Discussion

[jtpio]

03 Mar 2021 Weekly Meeting

• Isabela

  • We have a accessibility quick start meeting to get people joining in up to speed on some of our work today. It is right after this call on the same Zoom channel.

• Mehmet

  • Galata: UI Testing & Automation Framework
    • JupyterLab 3 compatible & migrated to use playwright instead of puppeteer
    • Ready to move under jupyterlab org
    • Contributing Galata (JupyterLab UI Testing & Automation Framework) #77
    • Screencast: Contributing Galata (JupyterLab UI Testing & Automation Framework) #77 (comment)

• Jeremy

  • JupyterLab Renderers PRs:
    • GitHub Actions: Switch to GitHub Actions on CI jupyter-renderers#242
    • New distribution system: Distribute the extensions as Python packages jupyter-renderers#243

• Darian

  • Discussion around Jupyter front-ends and 4.0

• Nick

  • licenses PRs: https://github.com/bollwyvl/jupyterlab-meta
    • fer voila, jlabc
  • theme trash: https://github.com/gt-coar/jupyterlab-gt-coar-theme
    • json viewer scrolling
    • hardcoded colors, px usage

• Alex

  • I've archived our weekly minutes, new archive for last four months linked below

• Tony

  • n lab / n lumino dev binders for accessibility testing
  • a binder that can launch different versions of jupyterlab dev builds jupyter/accessibility#20

Additional Discussion

• JupyterLab 4.0 roadmap, continued

[jtpio]

10 Mar 2021 Weekly Meeting

• Isabela

  • Reminder that we have our usual accessibility meeting after this one. Everyone is welcome!

• Steve

  • Added the jupyterlab-bot webhook to a bunch of repos. It auto-cancels workflows for previous commits when pushing commits to a pull request.
    • All workflows, including labeling workflows? Or just CI workflows? - just ones that use the pull_request event. We've already been using this in JupyterLab itself for a few months ;)
  • Alpha release of ipykernel is now available to try with debugger support

• Eric

  • Virtual notebook with a window Virtual notebook with a window jupyterlab#9925 on 2.3.x branch for better tab switching
    • Tagged experimental
    • Default is the curent virtual notebook behavior
    • Ready for review

• Mehmet

  • Galata: now a Jupyter project! https://github.com/jupyterlab/galata. Published to npmjs as @jupyterlab/galata.
  • JupyterLab Desktop App: upgrading to JupyterLab 3 and electron 10.

• Jason

  • Entry points for discovering JupyterLab extensions: data/config path entry_points with minimal examples jupyter/jupyter_core#209
  • Handling issues
    • Triage of issues.
    • "Answered" tag: Automatically close “answered” issues if they have no activity for 30 days jupyterlab#9920
    • Place for discourse?

      • nb: Or GH discussion? i think there's a "convert to discussion" button

    • Adopt org-wide GitHub configuration similar to jupyterhub?
      • Includes something similar to the "Answered" tag
      • Also includes a welcome bot
    • Problems with discourse
      • silent restrictions of things like number of links in a post, etc.
      • What moderation capabilities do we have?

• Layne

  • Track changes
  • Prior art: https://github.com/timkpaine/jupyterlab_autoversion
  • jupyterlab-git also has some version history capability

[jtpio]

17 Mar 2021 Weekly Meeting

• Steve

  • Will release a new 3.0.x today with some recent fixes for TOC and the process module - https://pypi.org/project/jupyterlab/3.0.11/

• Jeremy

  • [Debugger] Basic support for evaluating code at a breakpoint: [Debugger] Basic support for evaluating code at a breakpoint jupyterlab#9930

• Martha

  • Has anyone seen the AWS error that's showing up in the binder on this PR? Add aria roles and labels jupyterlab#9622 (comment)
    • jasongrout: The binder link in #9622 appears to work just fine for me

• Tony

  • Accessibility working meeting after this March 17, 2021 working meeting jupyter/accessibility#31

• Eric

  • Closing Virtual notebook with a window Virtual notebook with a window jupyterlab#9925 (take it over later maybe)
    • release 2.3 final as-is
    • start porting performance to master

• Brian

  • Questions about this issue (themes with bundled fonts in jlab 3):
    • possible extension changes in 3.x (from 2.x) break themes with bundled fonts jupyterlab#9839

Additional Discussion

• JupyterLab 2.3.0 final?
• Top level jupyterlab/.github repo? See conversation from last week about JupyterHub's repo - open a team compass issue. Question - can a repo override the org-wide settings for issue templates? Jason says that the presence of a .github directory completely overrides the org-wide values
• Roadmap discussion continued