Weekly Team Meetings: Jul-Dec 2023

fcollonval commented 1 year ago

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.

Here are the meeting notes for the 6 previous months (Jan-Jun 2023) and the next 6 months (Jan-Jun 2024)

Meeting Notes

fcollonval commented 1 year ago

July 5, 2023 (watch :tv:)

Name	Affiliation	GitHub	Favorite notebook
Jason Weill	AWS	@JasonWeill	Moleskine A5 size
tonyfast		@tonyfast	rhodia dot grid pad
Eric Gentry	Anaconda	@ericsnekbytes
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
Florence Haudin	QuantStack	HaudinFlorence
Rosio Reyes	Anaconda	@RRosio
Mike Krassowski	Quansight	@krassowski

Jason W
- Developing extensions to support both JupyterLab 3 and 4 (see Discourse thread)
tonyfast
- Collecting keyboard issue
- Triaging keyboard issues
- tag:keyboard added to triage
Mike
- Looking forward to nbdime#639 using cell IDs with an amazing x150 speedup for diffing large notebooks (opened up https://github.com/vidartf/nbdime/pull/3 to push it forward)
- a few PRs waiting for review:
- Open files from errors #13390
- Automatically toggle search in selection #14421
- Improve typing to avoid bad usage of context.contentsModel.content #14660
- Propagate command changed signal in semantic commands #14683
- Improve examples #14726
- spellchecker extension for lab 4.0 released
- spellchecking in code comments (and strings!)
- a patch release 0.8.3 coming today
- should CompleterProvider be able to suggest their ranks? https://github.com/jupyterlab/jupyterlab/issues/14790
- heads-up adding CSS validator in https://github.com/jupyterlab/jupyterlab/pull/14795 because some style values are incorrect see https://github.com/jupyterlab/jupyterlab/issues/14794 - I would encourage adapting this in extensions too
- help filling in https://github.com/jupyterlab/jupyterlab/issues/14590
- [after recording] how to stream data to jupyter-widgets model at request from frontend? In https://github.com/krassowski/jupyter-locuszoom currently using suboptimal "sync model state and find out if it is right" approach.
nick
- mermaid pull request
- pydantic v2 broke some dependencies (eg copier). waiting in on upstream fixes

fcollonval commented 1 year ago

July 12, 2023 (watch :tv:)

Name	Affiliation	GitHub	Favorite Fruit
Frederic Collonval	QuantStack	@fcollonval
William Stein	SageMath, Inc.	@williamstein	buy: Strawberry; pick: Blackberry
Afshin T. Darian	QuantStack	@afshin
Eric Gentry	Anaconda	@ericsnekbytes	Pineapple 👑
Jason Grout	Databricks	@jasongrout
Jason Weill	AWS	@JasonWeill	Rainier cherry
Stephannie Jimenez Gacha	Quansight	@steff456	Granadilla
R Ely	Bloomberg	@ohrely	lychee
Mike Krassowski	Quansight	@krassowski
tonyfast		@tonyfast
Vidar T Fauske		@vidartf	Blueberries (bilberries)
Gabriel Fouasnon	Quansight Labs	@gabalafou	lychee

Frederic
- JupyterLab GitHub org clean-up
  Issues opened on the repositories
- I'll open discussion on the team-compass about:
  - Member rights on GitHub: org owner, release power [Darian] Suggestion for the release group to add people that volunteers for doing the release and then once a year (TBC) [Nick] Need to spread the release power accross multiple stakeholder (+1 from Mike)
  - Versioning: changing principle to move away from bumping the major version from all packages to align with Python package. We should discuss a bit more in details what will be the new way to adapt the maintenance tooling.
Accessibility call 15 min after this call slot
Mike
- Making extensions depend on JupyterLab v4 and Notebook v7 without depending on either, e.g. spellchecker
- dynamic install_requires in setuptools
- should we an option to generate it dynamically in hatch-jupyter-builder?
- Unassigned regressions in 4.0:
- Needs review:
  - Open files from errors [Frederic] Looking into this by Friday
  - Propagate command changed signal in semantic commands. [Frederic] I cannot review it as it is mine
  - Make package importable in node.js - should we remove the label from this one? [Frederic] Yes - we should probably close it.

fcollonval commented 1 year ago

July 19, 2023 (watch :tv:)

Name	Affiliation	GitHub
A. T. Darian	QuantStack	@afshin
Frederic Collonval	QuantStack	@fcollonval
Jason Weill	AWS	@JasonWeill
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
tonyfast		@tonyfast
Jason Grout	Databricks	@jasongrout
Martha Cryan		@marthacryan
Andrii Ieroshenko	AWS	@andrii-i
Florence Haudin	QuantStack	HaudinFlorence
Jeremy Tuloup	QuantStack	@jtpio
Mike Krassowski	Quansight	@krassowski

Notebook 7 released 🎉 https://github.com/jupyter/notebook/releases/tag/v7.0.0
Darian: virtual scrolling update
- accessibility references for scrollbars
- https://adrianroselli.com/2019/01/baseline-rules-for-scrollbar-usability.html
- https://ericwbailey.website/published/dont-use-custom-css-scrollbars/
Tony: Tab traps! please fix them! https://github.com/jupyterlab/jupyterlab/pull/14115

2.1.2 No Keyboard Trap: If keyboard focus can be moved to a component of the page using a keyboard interface, then focus can be moved away from that component using only a keyboard interface, and, if it requires more than unmodified arrow or tab keys or other standard exit methods, the user is advised of the method for moving focus away. (Level A)

There is issue to fix linked to textarea in outputs (needed even if the style changes are removed from the PR).

Frederic
- Member rights on GitHub and other web service: PR opened to clarify some process for the different level of rights
Nick
- Mermaid rendering in Markdown
  Any last comments on the feat'? [frederic] otherwise we should merge (thanks Nick for pushing on this)
Mike
- VIM integration into core
  - Keymap switching but it should be larger than the editor one.
  - But it is probably larger that just a keymap switch to integrate in core.
  - Cons: size (Nick mentions it was a large chunk before, need to check)
  - We will discuss this as 4.1 or 4.2 item (while porting extension to support JupyterLab 4.0)
  - https://gameaccessibilityguidelines.com/
If you'd like to host a (next) Jupyterlab call, please sign up here (there's a guide available there too) https://github.com/jupyterlab/team-compass/issues/197

jtpio commented 1 year ago

July 26, 2023 (watch :tv:)

Name	Affiliation	GitHub	Favorite casual sport/game
Jeremy Tuloup	QuantStack	@jtpio
Andrii Ieroshenko	AWS	@andrii-i	ping-pong
William Stein	SageMath, Inc.	@williamstein	Skateboarding
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
Jason Grout	Databricks	@jasongrout
Jason Weill	AWS	@JasonWeill	cornhole
R Ely	Bloomberg	@ohrely
A. T. Darian	QuantStack	@afshin	riding bikes
Gabriel Fouasnon	Quansight	@gabalafou	hiking
tonyfast		@tonyfast	riding bikes

Jeremy:
- The JupyterLab logo: https://github.com/jupyterlab/team-compass/issues/196
  - OK to use the official Jupyter logo?
  - If yes, will proceed with the change
- Notebook 7 post release:
  - Help wanted :pray:
  - Monitor issues on the repo, Discourse, other places
  - 7.0.x issues: https://github.com/jupyter/notebook/milestone/47
JupyterCon YouTube page now has lots of recordings from JupyterCon 2023
Jason W: Jupyter bug bounty program is now live
- Funded by the European Commission
- JupyterLab, Jupyter Server, and JupyterHub affected
- Bounties of €250 to €5,000 for finding security issues, depending on severity
- Please publicize!
Discussion of @bollwyvl's work on Mermaid: https://github.com/jupyterlab/jupyterlab/pull/14102
- Action item: Call for a vote by the JupyterLab Council
Hosts wanted for upcoming meetings: https://github.com/jupyterlab/team-compass/issues/197
Eric G: Why did we switch from cookiecutter to copier?

fcollonval commented 1 year ago

Eric G: Why did we switch from cookiecutter to copier?

@ericsnekbytes as the notes did not have any comments, here are some reasons; copier is much more powerful than cookiecutter. The inputs asked to the dev are typed, can be documented (not simply the variable name). And also importantly, it supports update. Meaning that if the configuration of extension for testing or packaging needs to be slightly change, you, as a dev, won't need to figure out what to adapt in all your extensions. But running copier update should update the configuration for most extensions.

A side effect of the update feature is the ability to extend a pure frontend extension to a frontend+server extension by running update and changing your choices.

fcollonval commented 1 year ago

August 2, 2023 (watch :tv:)

Name	Affiliation	GitHub
Frederic Collonval	QuantStack	@fcollonval
Mike Krassowski	Quansight	@krassowski
Jason Weill	AWS	@JasonWeill
Florence Haudin	QuantStack	@HaudinFlorence
R Ely	Bloomberg	@ohrely
Carlos Brandt	CUB	@chbrandt
Jeremy Tuloup	QuantStack	@jtpio
tonyfast		@tonyfast
Jason Grout	Databricks	@jasongrout
Andrii Ieroshenko	AWS	@andrii-i
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf

Agenda

Frederic
- I will proceed with archiving the unmaintained jupyterlab repositories - for info only the commenting extension will not be archived
- member rights proposal: I propose to keep it open for discussion for another week and next week open a vote about it.
- Mermaid PR; did someone set up the vote (I was not there last week may have missed it)?
  [frederic] I'll boostrap the vote
Jason W
- Jupyter AI 1.0 and 2.0 are now available, for Lab 3 and Lab 4 respectively
- Blog post ~~to be published (submitted to queue on Monday)~~ published — thanks Sylvain! https://blog.jupyter.org/generative-ai-in-jupyter-3f7174824862
Mike
- jupyterlab-vim now supports JupyterLab v4 and Notebook v7
  - note versionning switched
- anyone planning next JupyterLab 4.0.x release this week?
  [frederic] I'll do it tomorrow
Darian
- Virtual scrollbar research request for interview / user test volunteers
Ely
- Jupyter Open Studio Day in NYC Monday, August 28
  - https://go.bloomberg.com/attend/invite/jupyter-open-studio-day-august2023/
Tony
- new accessibility meeting time every other Thursday @ 9am PST

Additional discussion

Extension upgrade for Lab 4 strategy: new major versions or cross-compatibility?

fcollonval commented 1 year ago

August 9, 2023

Name	Affiliation	GitHub
Jason Weill	AWS	@JasonWeill
William Stein	CoCalc	@WilliamStein
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
Frederic Collonval	QuantStack	@fcollonval
Mike Krassowski	Quansight	@krassowski
Carlos Brandt	Constructor University	@chbrandt
Stephannie Jimenez Gacha	Quansight	@steff456
Afshin T. Darian	QuantStack	@afshin
Gabriel Fouasnon	Quansight Labs	@gabalafou
Jason Grout	Databricks	@jasongrout
R Ely	Bloomberg	@ohrely
Eric Gentry	Anaconda	@ericsnekbytes
Andrii Ieroshenko	AWS	@andrii-i

Agenda

Isabela
- What's the current Jupyter Blog post submission process? Someone reached out to me looking to submit a post and I don't know how to help.
  - There is intention to build a media-focused working group to manage this process (among other things). Right now, there is still no formal process; reach out to individuals with permissions on the Jupyter Blog.
- Is there a way to check, contact, or figure out who has merge rights on Jupyter repos without explicit governance? I'm especially looking for support with jupyter/surveys where I have one user testing PR still open.
  - There is not a singular way at the moment. Some suggestions include checking the repository contributor graph, checking the people in the parent organization for that repo, and checking for any GitHub organization teams (this may not be publicly visible). The long term goal would be that all repos are owned by some kind of group and have an associated team listed as the contact point in the readme.
Frederic
- :warning: JupyterLab 4.0.4 breaks integration tests using galata -> see issue; fix is merged (I will do a release likely tomorrow)
- unmaintained jupyterlab repositories -> repositories archived
- member rights proposal: Brian made really good comments (thanks for those :bow: ). He propose to drop the inactive status of council membership. I support that; but it means changing existing part of the membership policy. So council members, please look at that proposal.
  So I will keep it open for discussion for another week to see if consensus is reachable before calling for a vote.
- Mermaid PR; vote in progress (one week to go dear council members) For info, we already have reached simple majority (Victory Nick :wink: ). But I will leave the vote open for another week as participation is required to compute active status of council member.
Eric G
- Trying to merge Dual Compatibility Guide document (4 PRs)
- Help with code-linking to examples repo, integration tests, welcome
- Doc PR: https://github.com/jupyterlab/jupyterlab/pull/14838
  - (Example 1 PR) Toparea widget: https://github.com/jupyterlab/extension-examples/pull/240
  - (Example 2 PR) Shout button widget: https://github.com/jupyterlab/extension-examples/pull/243
  - (Example 3 PR) Third example PR coming, Clap Widget
Jason W
- Plug for weekly triage
Ely
- Jupyter Open Studio Day in NYC Monday, August 28
  - https://go.bloomberg.com/attend/invite/jupyter-open-studio-day-august2023/
Tony
- Accessibility meeting tomorrow @ 9am PST https://github.com/jupyter/accessibility#join-our-jupyterlab-accessibility-meetings-

Additional discussion

Extension/plugin working group call for volunteers:
- https://github.com/jupyterlab/team-compass/issues/209

fcollonval commented 1 year ago

August 16, 2023

Name	Affiliation	GitHub
Mike Krassowski	Quansight	@krassowski
Andrii Ieroshenko	AWS	@andrii-i
William Stein	CoCalc	@WilliamStein
Gabriel Fouasnon	Quansight Labs	@gabalafou
Mehmet Bektas	Netflix	@mbektas
R Ely	Bloomberg	@ohrely
Jason Weill	AWS	@JasonWeill
Rosio Reyes	Anaconda	@RRosio
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
Frederic Collonval	QuantStack	@fcollonval

Agenda

Gabriel
- Keyboard brainstorming. What are some good dates? I was thinking:
- August 23, 17:00 UTC - next week immediately after this meeting
- August 30, 17:00 UTC - two weeks from now after this meeting
- Or does anyone have an alternative suggestion?
Frederic
- JupyterLab 4.0.5 released - it solves the bug of 4.0.4 with galata (unable to start a test)
  Some additional troubles have been seen with filebrowser.open: follow-up PR
- member rights proposal: I updated the proposal by removing the notion of inactive members and that bi-yearly active commitment will be done on the private council repo to limit the diffusion of who has release and/or admin rights. So council members, please look at that proposal.
  So I will keep it open for discussion for yet another week to see if consensus is reachable before calling for a vote.
- Mermaid PR; vote in progress dead line is August 20th
Ely
- Jupyter Open Studio Day in NYC Monday, August 28
  - https://go.bloomberg.com/attend/invite/jupyter-open-studio-day-august2023/
Jason W
- Plug for triage, every Tuesday at 09:00 PDT; all are welcome, even if you are not very familiar with JupyterLab, Jupyter Notebook, or JupyterLab Desktop
Tony
- adding semantic structure to code elements https://tonyfast.github.io/tonyfast/xxiii/2023-08-10-semantic-code-blocks.html#the-modified-highlighter-in-action
Jupyter AI 2.1.0 (JupyterLab 4) and Jupyter AI 1.1.0 (JupyterLab 3) with supoport for local models was released
- v2.1.0 https://github.com/jupyterlab/jupyter-ai/releases/tag/v2.1.0
- v1.1.0 https://github.com/jupyterlab/jupyter-ai/releases/tag/v1.1.0

JasonWeill commented 1 year ago

Thanks @afshin for providing video links; I updated the issue with them.

jtpio commented 1 year ago

August 23, 2023

Name	Affiliation	GitHub
Eric Gentry	Anaconda	@ericsnekbytes
Andrii Ieroshenko	AWS	@andrii-i
Stephannie Jimenez Gacha	Quansight	@steff456
Jason Weill	AWS	@JasonWeill
Afshin T. Darian	QuantStack	@afshin
Gabriel Fouasnon	Quansight Labs	@gabalafou
Jeremy Tuloup	QuantStack	@jtpio
William Stein	CoCalc	@WilliamStein
Mike Krassowski	Quansight	@krassowski
Carlos Brandt	CUB	@chbrandt
R Ely	Bloomberg	@ohrely

Agenda

Darian

list of youtube videos by date


20230104
https://youtu.be/RGonQhHgC4o

20230111
https://youtu.be/urRsOGjOKtc

20230118
https://youtu.be/pF3sHc4GrxM

20230201
https://youtu.be/GU-aMXMHnlg

20230208
https://youtu.be/orPGWXZdvUE

20230215
https://youtu.be/68uohFrXoJ4

20230222
https://youtu.be/BLl7GORJccU

20230301
https://youtu.be/ktY6KdliBN8

20230308
https://youtu.be/1FxPUpcHHrs

20230315
https://youtu.be/mlwmUICpdIk

20230322
https://youtu.be/M6DC0nCUrI4

20230329
https://youtu.be/he2IIFVcbps

20230405
https://youtu.be/GTnKltJ-srU

20230412
https://youtu.be/vdrf2Y5FcdE

20230419
https://youtu.be/XTgrRhsgjwE

20230426
https://youtu.be/MVlZNnFpdnY

20230503
https://youtu.be/kGx44l9-zoI

20230517
https://youtu.be/AjRPib-UHyo

20230531
https://youtu.be/uESFSLhjgZY

20230607
https://youtu.be/yHMq5xCSEH0

20230614
https://youtu.be/Xjt8TvX1PcI

20230621
https://youtu.be/77YqB0FSZlQ

20230628
https://youtu.be/xVdTVIPaNlA

20230705
https://youtu.be/lABzu3Rjttg

20230712
https://youtu.be/vd7UYI8a6u8

20230719
https://youtu.be/ss9iEBgkqfI

20230726
https://youtu.be/LUMVh7X9KvU

20230802
https://youtu.be/fLl3GeQljCE

Frederic (I won't make it)
- JupyterLab 4.1.0-alpha.1 released
- Mermaid PR;
  - the vote has ended; the majority is in favor to add that feature
  - The PR has been merged
  - The feature has been released as part of 4.1.0-alpha.1
Eric G
- Extension tutorial is broken
  - M: are you referring to https://github.com/jupyterlab/jupyterlab/issues/14994?
- Making a Jupyter documentation subproject
  - A group that coordinates docs across all subprojects
  - Possible major focuses:
    - Content (writing docs)
    - Discovery/community engagement (getting users info they need)
    - Feedback (what needs to be documented? what info do people need?)
  - Possible early targets:
    - Characterize documentation needs across subprojects (what needs to be added, improved, made consistent across each)
    - Capture/store (possibly automate) readthedocs traffic stats/CSVs for last 90 days on a regular basis to get rough metrics on what's important to users
    - Add some easy CI tests to ensure commands in the tutorial run without erroring (would have helped prevent the docs from breaking this time as mentioned above), other CI tests
    - "Get Help" effort spanning multiple subprojects, to consistently communicate to users how they can get help from different documentation sites
    - Add homebrew recommendations to the docs (so users don't encounter recent errors discovered for homebrew installations)
    - And more!
  - analytics from jupyter.org got removed in https://github.com/jupyter/jupyter.github.io/pull/408
Gabriel
- Looks like August 30 after this meeting is best time for keyboard brainstorming. How do I go about reserving it, putting it on the calendar?
  - Jason W added this to the shared Google Calendar
- I will also advertise the event on Discourse.

jtpio commented 1 year ago

August 30, 2023

Name	Affiliation	GitHub
Eric Gentry	Anaconda	@ericsnekbytes
William Stein	CoCalc	@WilliamStein
R Ely	Bloomberg	@ohrely
Andrii Ieroshenko	AWS	@andrii-i
Jason Weill	AWS	@JasonWeill
Florence Haudin	QuanstStack	@HaudinFlorence
Gabriel Fouasnon	Quansight Labs	@gabalafou
Mehmet Bektas	Netflix	@mbektas
Mike Krassowski	Quansight	@krassowski
Stephannie Jimenez Gacha	Quansight	@steff456
Gabriela Vives	QuantStack	@GabrielaVives
Rosio Reyes	Anaconda	@RRosio
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf

Agenda

Eric G
- Documentation Working Group proposal is here!
- We need you! :)
Jason W
- JupyterLab keyboard UX brainstorm starts at 10:00 PDT / 17:00 UTC, on this channel
Mehmet
- JupyterLab Desktop 4.0.5-1 release
  - Fixes for Python environment activation issues
  - Upgrade to JupyterLab 4.0.5
  - Icon updates
  - Upgrade to Electron v26
Mike
- LSP extension future
- 5.0.0-beta.0 available
- porting it to JupyterLab 4.0 was very painful
- can we merged individual features into JupyterLab core? Which ones?
  - [if as plugin which can be overriden] - why not
  - maybe ship a language server like JSON, so that we have something tests being non kernels-specific?
  - possibly disabled by default, but shipped
  - ToC: https://github.com/jupyter-lsp/jupyterlab-lsp/pull/970
- blocking usptream issues (please help):
- Completer improvements
- auto-imports, snippet https://github.com/jupyterlab/jupyterlab/issues/15026
- autocompletion config https://github.com/jupyterlab/jupyterlab/issues/15022
- AI hint/completions https://github.com/jupyterlab/jupyterlab/issues/14267
  - Related Jupyter AI issues regarding code completion, automatic indexing: https://github.com/jupyterlab/jupyter-ai/issues/268, https://github.com/jupyterlab/jupyter-ai/issues/290
- autosuggestion heuristics: https://github.com/jupyterlab/jupyterlab/issues/15013
Gabriel
- Keyboard brainstorm call at the top of the hour after this call

PSA: don't forget to add the "status:Needs Review" label to PRs that have been open but need review, like these:

Signup to host this meeting https://github.com/jupyterlab/team-compass/issues/197

fcollonval commented 1 year ago

September 6, 2023

Name	Affiliation	GitHub
Andrii Ieroshenko	AWS	@andrii-i
Mike Krassowski	Quansight	@krassowski
Jason Weill	AWS	@JasonWeill
William Stein	CoCalc	@WilliamStein
Nicolas Brichet	Quantstack	@brichet
Gabriel Fouasnon	Quansight Labs	@gabalafou
Frederic Collonval	QuantStack	@fcollonval
Florence Haudin	QuantStack	@HaudinFlorence
Jeremy Tuloup	QuantStack	@jtpio

Agenda

Frederic
- member rights proposal: i'll be calling for a vote by the lab council as no additional points were raised.
- nbdime migration we are reaching a first working version (thanks a lot to Florence, Mike, Johan and Jeremy). We have a bottleneck issue with the maintenance of the project; I opened an issue to increase the number of maintainer as there are clearly interest by multiple stackholders.
Gabriel
- [Accessibility] Keyboard navigation in Jupyterlab/Notebook #15051
- ^ It's a GitHub discussion, join in on the fun!

PSA PRs that need review:

PSA: If your PR needs review, put "Needs review" label on it

PSA: Sign up to host this meeting: https://github.com/jupyterlab/team-compass/issues/197

Additional discussion

Jason W: Bringing AI-based completion in core
https://github.com/jupyterlab/jupyterlab/issues/14267
https://github.com/jupyterlab/jupyterlab/issues/14267

[Mike] It will be good to bring to core an API to handle multiple extensions providing completion

How to distribute models [Nick] Wrapping them in an existing completion source (LSP or kernels) substantially reduces the amount of rework [William] I would very much want to make it so jupyterlab as hosted by cocalc has access to ChatGPT, but with the calls to openai proxied through an api I provide, in order to securely protect my api key and also meter usage. Similar remarks for other LLM providers, and I bet other jupyterlab hosting providers also could have similar requirements. [Jason W] It is now possible to specify a proxy to inforce API limitation for example [William] Maybe off topic, but cocalc jupyter has had extensive openai integration for a while and I get to look at usage stats, and by far the most popular feature is "Help me fix this", which is a button that appears next to any traceback, which when clicked, suggests a fix as a conversation in a side chat (so user can follow up). I implemented a lot of things, then looked at stats, and didn't know what would be popular, but that is what is. [Jason W] We implemented "%%ai error" and it is similar to this.
Should we create additional chat-baseed communication channel like Slack or Discord due to better usability vs Gitter, more relevant people using it
- they have community managers and developer advocates to moderate it.... not an easy thing to do when the space grows
- Zulip (https://zulip.com/) actually looks nice
  - Zulip now has public read-only logs, which is nice for oss communities. and oss projects get a free hosted account at zulip

fcollonval commented 1 year ago

September 13, 2023

Name	Affiliation	GitHub
Andrii Ieroshenko	AWS	@andrii-i
Mike Krassowski	Quansight	@krassowski
William Stein	CoCalc	@WilliamStein
R Ely	Bloomberg	@ohrely
Jason Weill	AWS	@JasonWeill
Afshin T. Darian	QuantStack	@afshin
Florence Haudin	QuantStack	@HaudinFlorence
Gabriel Fouasnon	Quansight Labs	@gabalafou
Carlos Brandt	CUB	@chbrandt
Jeremy Tuloup	QuantStack	@jtpio

Agenda

Andrii:
- Looking for a review and/or approval
  - PR for adding Jupyter Scheduler recipe to conda forge https://github.com/conda-forge/staged-recipes/pull/23961
  - PR for adding Jupyter AI recipe to conda forge https://github.com/conda-forge/staged-recipes/pull/23959
Jason W: Publishing multiple major versions of packages to conda-forge?
- Jason G.: You can have two branches for a recipe, each branch releases a single major version
- Frederic: See e.g. https://github.com/conda-forge/jupyterlab-feedstock/
- Nick: bot will only update main, PRs (for PRs) welcome
Frederic:
- member rights proposal: vote is on until September 21st. We already have the majority but the vote will stay opened for JupyterLab council member to have a chance to vote.
- [Accessibility] tab trap PR: https://github.com/jupyterlab/jupyterlab/pull/14115
  - Mike: the biggest risk right now is that this PR allows the notebook widget to "steal" keyboard shortcuts from cell outputs.
Mike
- API for inline completions for 4.1 (https://github.com/jupyterlab/jupyterlab/issues/14267)
  - IInlineCompletionProvider beside ICompletionProvider
  - another package, or just a plugin in completer package?
- nbdime and jupyterlab-git for JupyterLab 4.0 :eyes:
- time for a new point release?
Andrii
- PR #181 Add Jupyter Media Strategy Charter at Jupyter Governance repo: https://github.com/jupyter/governance/pull/181

PSA: If your PR needs review, put "Needs review" label on it (and help reviewing other PRs)

PSA: Sign up to host this meeting: https://github.com/jupyterlab/team-compass/issues/197

Additional discussion

FYI: Chan Zuckerberg Initiative (CZI) Essential Open Source Software for Science (EOSS) Cycle 6 Request for Applications (RFA) is up - https://chanzuckerberg.com/rfa/essential-open-source-software-for-science/

fcollonval commented 1 year ago

September 20, 2023

Name	Affiliation	GitHub
Jason Weill	AWS	@JasonWeill
Eric Gentry	Anaconda	@ericsnekbytes
Frederic Collonval	QuantStack	@fcollonval
William Stein	CoCalc	@WilliamStein
Mike Krassowski	Quansight	@krassowski
Nicolas Brichet	QuantStack	@brichet
Stephannie Jimenez	Quansight	@steff456
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
Andrii Ieroshenko	AWS	@andrii-i
Vidar T Fauske	JP Morgan Chase	@vidartf

Agenda

Eric G
- Deciding on first meeting date for the proposed new Documentation Working Group
- Tentative time and date is 11am EST Wednesday (weekly), starting October 4th
Jason W
- Conda-forge pull request for Jupyter AI blocked due to dependency problems — seeking some help on this (via @3coins)
- Also seeking help with the Jupyter Scheduler conda-forge PR, which has a passing CI pipeline, on behalf of @andrii-i
Frederic:
- member rights proposal: vote is on until September 21st. We already have the majority but the vote will stay opened for JupyterLab council member to have a chance to vote.
- Announcement prerelease of nbdime 4.0.0a0 compatible with JLab4: https://github.com/jupyter/nbdime
  - Special thanks to Florence, Mike and Vidar
  - There are rough edges. So feel free to test and report issues and even fix opened issues
Mike:
- jupyterlab-lsp 5.0 release candidate - please test if you are interested
- JupyterLab 4.0.6 and Notebook 7.0.4 (thanks Jeremy!)
- PR that "need review"

Additional discussion

Mike:
- maintainers list
- has a history of going outdated, maybe should be automated?
- good for recognition
- good for users but might be too much info?
  - "is readme the right place"
- might be good to recognise someone if they do not want to be engaged in council work
- silent releases

Sign up to host this meeting: https://github.com/jupyterlab/team-compass/issues/197

krassowski commented 1 year ago

September 27, 2023

Name	Affiliation	GitHub
Andrii Ieroshenko	AWS	@andrii-i
William Stein	CoCalc	@WilliamStein
Mike Krassowski	Quansight	@krassowski
Frederic Collonval	QuantStack	@fcollonval
Jason Weill	AWS	@JasonWeill
Florence Haudin	QuantStack	@HaudinFlorence

Agenda

Andrii
- Created issue "New chat-based communication channel to replace Gitter/Matrix for Project Jupyter" in jupyter/governance. Please share your thoughts and opinions on the topic https://github.com/jupyter/governance/issues/182
Eric G
- The Documentation Working Group is still looking for people interested in doing docs-related work
  - https://github.com/jupyter/governance/issues/182#issuecomment-1728454247
  - you may want to ping the Jupyter EC mailing list to reach for someone with the proper rights to transfer the repository
- First meeting is (tentatively):
  - Wednesday at 11am EST (weekly), starting October 4th
- Move the Docs Working Group proposal out of the JupyterLab org into Jupyter org?
Mike:
- Inline completer draft open, request for comments on API https://github.com/jupyterlab/jupyterlab/pull/15160

Additional discussion

Pull request to document "no recording" request for meetings: https://github.com/jupyter/jupyter/pull/698 (fixes https://github.com/jupyterlab/team-compass/issues/214)
Regressions in 4.0 by number of upvotes
- we discussed all reported regresssions with more than one upvote and clarified next steps where needed
Pull requests which need review

Sign up to host this meeting: https://github.com/jupyterlab/team-compass/issues/197

krassowski commented 12 months ago

October 4, 2023

Name	Affiliation	GitHub
Afshin T. Darian	QuantStack	@afshin
Eric Gentry	Anaconda	@ericsnekbytes
Jason Weill	AWS	@JasonWeill
Frederic Collonval	QuantStack	@fcollonval
Mike Krassowski	Quansight	@krassowski
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
Rosio Reyes	Anaconda	@RRosio
R Ely	Bloomberg	@ohrely
Florence Haudin	QuantStack	@HaudinFlorence
Nicolas Brichet	QuantStack	@brichet
William Stein	CoCalc	@WilliamStein

Agenda

Jason W
- ipywidgets issue with kernel gateway
- Request to merge no-recording policy for meetings
  - Thanks @isabela-pf for merging!
Darian:
- Virtual scrollbar PR demo
Frederic:
- member rights proposal: Merged
  - I'm working to add a CI job to automatically ping for membership update
- Jupyter Community Survey 2023: the community subgroup is looking for representatives of the subproject for interviews. I sent an email to the council with more details.
Mike:
- plugin manager demo
- inline completer (https://github.com/jupyterlab/jupyterlab/pull/15160) demo
- debouncer/timeout question
- discussion: improving contrast/alternative indicator of ghost text

krassowski commented 11 months ago

October 11, 2023

Name	Affiliation	GitHub
Andrii Ieroshenko	AWS	@andrii-i
Jason Weill	AWS	@JasonWeill
Mike Krassowski	Quansight	@krassowski
Nicolas Brichet	QuantStack	@brichet
Jeremy Tuloup	QuantStack	@jtpio
Mehmet Bektas	Netflix	@mbektas
Florence Haudin	QuantStack	@HaudinFlorence
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf

Agenda

Jason W
- Quick reminder: Jupyter records meetings and publishes on-record discussions to YouTube, but please do not record our meetings on your own: https://docs.jupyter.org/en/latest/community/content-community.html#jupyter-community-meetings
Frederic:
- Council membership bot tick: [for council members only] I create a PR to ping the council members twice a year. Would you mind commenting on https://github.com/jupyterlab/council/issues/9 about it? If not feeback before the week-end, I'll start rolling it.
- Grant Nicolas Brichet (@brichet) Write rights on JupyterLab; so he can re run the CI.
- Jupyter Community Survey 2023: who is interested??
Mike:
- Enable full windowed mode for notebooks by default
  - opened tracking issue #15258
- Exposing execution history in Notebook UI (in cells):
  - PR #15062, modeled after the Console history, targetting 4.1
  - opt-in via settings
  - shortcuts review: Alt + Up, Alt + Down
  - history is shared across sessions (in case of ipykernel with IPython)
  - history is requested incrementally, only on user request.
  - Should we (optionally?) advise kernels to store history per notebook/separate from their own history? See issue #15220
  - Discussion on history_request status and future plans issue #976
  - JupyterLab 4.1 feature freeze/beta/release planning
  - soft feature freeze 1st November (3 weeks from now, at this point no new pull requests would be considered for 4.1)
  - aiming to have the first release candidate 1st December
  - 4.1 Release Plan: https://github.com/jupyterlab/jupyterlab/issues/14613
Andrii:
- Opinions on testing zulip as an alternative text-based communication channel in JupyterLab subproject to compare user experience and actual usage vs gitter? https://jupyter.zulipchat.com
- Related discussion re Gitter/Zulip:
  - https://github.com/jupyter/governance/issues/182
  - https://github.com/jupyterlab/team-compass/issues/213#issuecomment-1727618191
- At this moment, to request media posts (like tweets or blogposts) please email to jupyter-media-strategy@googlegroups.com. Google request form is planned to be rolled out after charter is approved.

Additional discussion

Frederic: Tab trap PR
- (Mike) Multiselection selector/focus pattern in notebooks
  - When multi-selection is active, no cell is focused preventing .jp-Notebook.jp-mod-commandMode :focus selector from activating commands
    - maybe the issue is not there? Gabriel unable to repro. Needs further testing.
    - if it does, we should probably make the focus always stay on the cell (if it does not already).
    - full windowing notebook may require fixes to make the pattern of "focus stays on the cell in multiselection"
    - grid pattern/multiselectable could be a good follow-up
- next steps: Nicolas will open a PR against Gabriel's branch, Gabriel will review/merge, we will switch the default for bubbling in JupyterLab (keeping it as it was in lumino), merge the PR, release a new 4.1 alpha

fcollonval commented 11 months ago

October 18, 2023

Name	Affiliation	GitHub
Andrii Ieroshenko	AWS	@andrii-i
Jay Rodge	NVIDIA	@jayrodge
Frederic Collonval	QuantStack	@fcollonval
Jason Weill	AWS	@JasonWeill
Mike Krassowski	Quansight	@krassowski
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
R Ely	Bloomberg	@ohrely
Stephannie Jimenez	Quansight Labs	@steff456
Gabriel Fouasnon	Quansight Labs	@gabalafou
Nicolas Brichet	QuantStack	@brichet
William Stein	CoCalc/SageMath, Inc	@williamstein
Florence Haudin	QuantStack	@HaudinFlorence
Jeremy Tuloup	QuantStack	@jtpio

Agenda

Need speaker for PyData Bay Area meetup to Talk about latest Jupyter Lab/notebook updates and how it helps Data Scientist improve their productivity.(Jay).
- Andrii: What is the date? I could potentially talk about lab and notebook updates, let's connect, my email is ieroshenkoa@gmail.com
- Nov 8, 6 - 8 pm
Frederic:
- I opened a PR to set the council member list for the bi-yearly check: https://github.com/jupyterlab/council/pull/11
  Please JupyterLab council member check that the information are correct. And we also need to reduce the number of administrators. Note: the goal is to start the check by the end of this week. So that the council members are up-to-date by mid-november. And we can start the election of the JupyterLab SSC representative right after to be on time for January 2024.
  PSA: I won't run for a second year.
Mike:
- Remainder: feature freeze on JupyterLab 4.1 by 1st November (https://github.com/jupyterlab/jupyterlab/issues/14613)
- Inline Completer PR ready for review https://github.com/jupyterlab/jupyterlab/pull/15160
Jeremy:
- Status of https://github.com/jupyter/governance/issues/182 ?
  - Discussed last week (see notes below)
  - Using the same channel for weekly calls?
- There is a JupyterLab test channel on Discourse now: https://discourse.jupyter.org/chat/c/jupyterlab/31

Additional discussion

(Mike) Triage of pull requests targetting 4.1 (if there is time at the end)

krassowski commented 11 months ago

October 25, 2023

Name	Affiliation	GitHub
Mike Krassowski	Quansight	@krassowski
Gabriel Fouasnon	Quansight	@gabalafou
Eric Gentry	Anaconda	@ericsnekbytes
Frederic Collonval	QuantStack	@fcollonval
Jason Weill	AWS	@JasonWeill
Jeremy Tuloup	QuantStack	@jtpio
Mehmet Bektas	Netflix	@mbektas
Andrii Ieroshenko	AWS	@andrii-i
Afshin T. Darian	QuantStack	@afshin
Florence Haudin	QuantStack	@HaudinFlorence

Agenda

:warning: Next week, most of Europe changes from CEST (UTC+2) to CET (UTC+1) but most of the Western US remains on PDT (UTC-7). Most of our calendar events are in Pacific time, so European colleagues will have to join an hour earlier. US daylight saving time ends one week later than European summer time does.

Mike:
- scrolling behaviour on execution vs on navigation https://github.com/jupyterlab/jupyterlab/pull/15288
- PSA: 1 week to feature freeze for 4.1
- PSA: Pull requests which need review, issues that need design or discussion
Jason W: Status of jupyterlab-git release for use with JupyterLab 4?
- [Frederic] Alpha version released pip install --pre jupyterlab-git==0.50.0a0; a final release is pending a final release of nbdime.
- Continuous integration is now passing
Jeremy:
- Discussions about Contents.IDrive:
  - https://github.com/jupyterlab/jupyterlab/issues/15143
  - https://github.com/jupyterlab/jupyterlab/issues/15289
Frederic
- PSA JupyterLab council: the first membership check has been triggered. All members must confirm their membership by November 15th.

fcollonval commented 11 months ago

November 1st, 2023

Name	Affiliation	GitHub
William Stein	CoCalc/SageMath, Inc	@williamstein
Jason Weill	AWS	@JasonWeill
A. T. Darian	QuantStack	@afshin
Mike Krassowski	Quansight	@krassowski
Andrii Ieroshenko	AWS	@andrii-i
R Ely	Bloomberg	@ohrely

Agenda

:warning: Time change announcement: Next week, US Pacific Standard Time (PST, UTC-8) begins, so London will once again be 8 hours ahead and Paris will be 9 hours ahead. The meeting is in US Pacific time on the shared Google Calendar.

Frederic (won't be able to attend):
- 4.1.0 - Plugin manager access; should we keep it as toolbar button in the settings panel or move it to the extension manager side panel.
- (Eric G) Extension Manager side panel seems like a good fit
- (Mike) maybe both places are good to have a link; the rationale for keeping the link in Settings is that users will go to "Settings" to enabled/disable optional feature of extensions which is enabled by the Plugin manager
Nick
- build testing/JupyterLite
- https://github.com/jupyterlite/jupyterlite/discussions/1238
Mike
- PSA Needs Review
- PSA discussion about kernel panel https://github.com/jupyterlab/jupyterlab/issues/15294

Additional discussion

4.1.0 triage for issues, pull requests

Triaged pull requests:

https://github.com/jupyterlab/jupyterlab/pull/13390 (needs review)
https://github.com/jupyterlab/jupyterlab/pull/14784 (needs review)
https://github.com/jupyterlab/jupyterlab/pull/14996 (needs review)
https://github.com/jupyterlab/jupyterlab/pull/14743 (@RRosio to revise)
https://github.com/jupyterlab/jupyterlab/pull/14115 (@brichet to revise)
https://github.com/jupyterlab/jupyterlab/pull/15109 (@afshin to revise)
https://github.com/jupyterlab/jupyterlab/pull/15092 (closed in favor of https://github.com/jupyterlab/jupyterlab/pull/14766, which is now added to 4.1.0, and which now has @tonyfast as a requested reviewer)

fcollonval commented 10 months ago

November 8, 2023

Name	Affiliation	GitHub
Afshin T. Darian	QuantStack	@afshin
Eric Gentry	Anaconda	@ericsnekbytes
Mike Krassowski	Quansight	@krassowski
Jason Weill	AWS	@JasonWeill
tonyfast	materialsgenomefoundation	@tonyfast
William Stein	CoCalc/SageMath, Inc	@williamstein
R Ely	Bloomberg	@ohrely
Rosio Reyes	Anaconda	@RRosio

Agenda

Eric G
- Jupyter Developer experience
  - What should our new maintainer pipeline be like?
    - Complexity of tech stack, and CI
    - Many dependencies
    - Difficulty getting work through often undocumented CI processes
      - Each check, many tools, each with their own configurations
      - "Marked by a senseless, disorienting, often menacing complexity"
    - Suggestions?
      - Mike brings up mozilla/contributor guide
      - Formalized process for bringing people on and supporting people
      - Getting started guide on jupyter.org/community, or an improvement to the Contributing doc
      - Don't add to CI if not human readable!
        
        for ci, $GITHUB_STEP_SUMMARY would be good
      - "Quality of life" tag, Darian
      - Add to issue template: "- [ ] I would consider opening a PR"
      - Bot on issuess, thumbs up if you need some help
      - Spare time in meetings, for popular items/PRs
      - Pay testers, esp disabled users
      - "developer experience" initiative in docs working group
  - "Module Owners" might be a good way to organize expertise and knowledge transfer
    - Mentoring, like GSOC?
      - GSOC was discussed e.g. here
- Tribal knowledge in Jupyter
  - Document it! Docs working group is planning moots around different topics to gather expert knowledge and consensus
  - Suggestions
    - How does funding work? for example (getting funds for user testing for low vision users for instance)
    - Check team compasses for proj specific knowledge
  - Gabriel: running the test suite locally is really hard. I know how to run (many) Galata tests, for example, but I'm not even sure where to put this info. The JupyterLab contributing page? The Galata readme? Also, the way I often figure out how to do things is to read the GitHub workflows.
- Jupyter.org meta docs purpose/refactors
Frederic
- JupyterLab council membership check: one week left to validate your membership
Mike
- Wrapping up for JupyterLab 4.1 (last alpha/first beta soon?)

fcollonval commented 10 months ago

November 15, 2023

Name	Affiliation	GitHub
Eric Gentry	Anaconda	@ericsnekbytes
R Ely	Bloomberg	@ohrely
Jason Weill	AWS	@JasonWeill
Vidar Fauske	JP Morgan Chase	@vidartf
Carlos Brandt	Constructor Uni	@chbrandt
Mike Krassowski	Quansight	@krassowski
Rosio Reyes	Anaconda	@RRosio
Gabriel Fouasnon	Quansight Labs	@gabalafou
Andrii Ieroshenko	AWS	@andrii-i
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
Mohammad Pishahang	UCLA	@mhpishahang
tonyfast		@tonyfast
Nicolas Brichet	QuantStack	@brichet
Jeremy Tuloup	QuantStack	@jtpio
Florence Haudin	QuantStack	@HaudinFlorence
Afshin T. Darian	QuantStack	@afshin

Agenda

Frederic
- JupyterLab council membership check: today is the last day to validate your membership
Tony
- Can i take over this meeting to run an hour and a half community call on dec 13 from 8:30PST to 10PST? email me if you want to help while i start organizing.
- 12/13 8:30am JupyterLab meeting to triage 4.1 issues
- 12/13 9:00am Community Call Demos
- make an issue
Jason W
- Volunteers wanted to facilitate the meeting: https://github.com/jupyterlab/team-compass/issues/197
Eric G
- "Complexity Managed" parts of the Lab codebase
  - Do this as a JEP specifying what build/packaging tools we use and then require a new JEP to change it?
  - Who would do that? We have enough difficulty getting PRs
  - Maybe it would be sufficient to "agree" that we work to reduce complexity and make it easier for reviewers to argument for it
  - Possible workflow/details
    - CI writes to markup, of a diff
    - Use milestones/tie to releases
    - Do an example/workflow on some example area, build a prototype
    - Checklist for PRs
  - Examples of complexity problems:
    - build system
    - packaging (hatch)
    - CI (jupyter-maintainers tools, visual regression tests)
    - RTC
  - Example solution to common CI problems: better scripts for reporting status of visual regression tests
  - Maybe add a review guide to member docs: https://jupyterlab-team-compass.readthedocs.io/en/latest/team/member-guide.html#when-should-i-merge-a-pull-request
Mohammad Pishahang
- Presenting LibroBase Apps
- https://github.com/librobase
Rosio Reyes
- Issues with development install of JupyterLab

Additional discussion

accessibility improvment: notebook tab trap fixed with https://github.com/jupyterlab/jupyterlab/pull/14115

fcollonval commented 10 months ago

November 22, 2023

Name	Affiliation	GitHub
Afshin T. Darian	QuantStack	@afshin
Frederic Collonval	QuantStack	@fcollonval
Jeremy Tuloup	QuantStack	@jtpio
Mike Krassowski	Quansight	@krassowski
Florence Haudin	QuantStack
William Stein	CoCalc/SageMath, Inc	@williamstein
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf

Eric G (not attending)
- Host script (draft) PR is here! Linked at the top also
  - Feedback/formatting appreciated
  - Thanks to @isabela-pf and work from other community members in their draft host guide
Frederic
- Reminder for council members: the nomination for the SSC representative is open until December 4th
- FYI: following the council member check, rights on GitHub, PyPI and NPM have been updated. If you are having too little or too large rights, please contact me.
Mike
- PRs that "need review"

Additional discussion

Remaining PRs of 4.1 release plan issue:
- Custom CSS: [frederic] I'll push a commit to use Playwright routing for test the feat'. It will probably easier then to explain how this is achieved.
- Scrollbar UI [frederic] I'll have a look by the end of the week.

fcollonval commented 10 months ago

November 29, 2023

Name	Affiliation	GitHub
Mike Krassowski	Quansight	@krassowski
Isabela Presedo-Floyd	Quansight Labs	@isabela-pf
Frederic Collonval	QuantStack	@fcollonval
R Ely	Bloomberg	@ohrely
Jeremy Tuloup	QuantStack	@jtpio
Mehmet Bektas	Netflix	@mbektas
Andrii Ieroshenko	AWS	@andrii-i
Florence Haudin	QuantStack	@HaudinFlorence
William Stein	CoCalc/SageMath, Inc	@williamstein

Mike
- merging https://github.com/jupyterlab-contrib/jupyterlab-recents into document manager (all of it or just a history)?
  [Frederic] :+1:
- should it be on disk/server-operated or statedb operated (statedb is usually good enough, but lets discuss on the PR once open)
- did you all see https://github.com/parmentelat/jupyterlab-gridwidth
Frederic
- Should we merge this meeting with the JupyterLab one as now the work on Notebook 6 is done and Notebook 7 shares code with JupyterLab 4? Opened an issue for discussion
- Reminder for council members: the nomination for the SSC representative is open until December 4th
- Darian
  - Virtual scrollbar UI minimum viable feature set
tony
- December 13, 2023 Jupyter Community Call https://github.com/jupyterlab/team-compass/issues/223

Additional discussion

JupyterLab 4.1
- 17 PRs tagged for 4.1: https://github.com/jupyterlab/jupyterlab/issues?q=is%3Apr+milestone%3A4.1.0+is%3Aopen
- major pending PRs
- Virtual scrollbar UI
- Add filtering notebook cells with tags
- all other PRs
- release blockers:
- Update fast stack to non-deprecated packages
- CodeMirror built-in search shows up on cells upon ctrl+f

fcollonval commented 9 months ago

December 6, 2023

Name	Affiliation	GitHub
Jason Weill	AWS	@JasonWeill
Andrii Ieroshenko	AWS	@andrii-i
Matthias Bussonnier	Quansight	@carreau
Mike Krassowski	Quansight	@krassowski
Jeremy Tuloup	QuantStack	@jtpio
Frederic Collonval		@fcollonval
Ian Dong	Apple	@misterfads
Florence Haudin	QuantStack	@HaudinFlorence
Rosio Reyes	Anaconda	@RRosio
Gabriel Fouasnon	Quansight Labs	@gabalafou

Jeremy:
- Merge the Notebook meeting with the JupyterLab meeting?
  - Merge meeting for Notebook and Lab #30
  - Advantages
  - Long term: single Jupyter Frontends subproject?
- Additional discussion about fixing the UI tests
Eric G:
- Docs page metrics
  - Matthias: there was strong pushback against google analitics at some point. Some peopel suggested matomo. That's likely a question for NumFOCUS if we coudl get a shared matomo instance.
  - Links from chat:
- Jupyter web hosting?
- Hex editor (WIP) for demo next week?
Matthias:
- Tidelift seem to have ~$500/Month for JupyterLab, I didn't see any response to the discussion I opened so I checked in here.
  - Andrii: subproject (JupyterLab, Security) can’t make decisions about financial matters, contracts, etc. All of that has to go through Executive Council. So to proceed with this, the security and/or JupyterLab group should write a doc for this and submit it to EC here: https://github.com/jupyter-governance/ec-team-compass
  - Mike: How would the security earmarking work? Should we have a form like JupyterHub has (https://jupyterhub-team-compass.readthedocs.io/en/latest/practices/funding.html#how-to-get-reimbursed-from-numfocus)?
Mike:
- Bug/regression: Windows line endings break Markdown rendering #14752
  - two components at play ydoc and marked.js
- Difference levels of page config in extensions, sys.prefix being default
  - Plugin manager doesn't allow users to enable an extension #15486
  - Jupyter Lab does not find extensions #14965
- Updating 4.1 release schedule
Jason W / Tony:
- Community call next week
  - expectations for 8:30 am and 9:00 am PST sessions
  - Promotion
    - Please send your requests for blogpost or social media publishing to jupyter-media-strategy@googlegroups.com. Please make sure to include the text that you want to be posted and where it should be posted (blog and/or social media).
- Sign up to host future meetings: #197 Hosting our weekly meeting
Frederic
- jupyter-ui-toolkit move to JupyterLab organization vote (opened until December 14th): #227 Move jupyter-ui-toolkit in the JupyterLab organization
- JupyterLab SSC representative election: nomination period is closed. The nominees have been contacted to check if they are willing to become representative. ETA is to launch the vote by the end of this week.
Ian
- PR review request: #15421 Show toast notification for running code cell while kernel initializing

Additional discussion

[Demo time] Quickly open recent document (proposed for 4.2) #15483
Fix UI tests in JupyterLab
- Maintenance fatigue
- #14947 Flaky UI tests
- Mike on Gitter:
  
  Yes, I know of three issues: (a) concurrent runners (#15375) (b) benchmark snapshots seem to need updating (the size change issue) (c) open tabs snapshot needs investigation I did not want to put more time in waiting for #15375 to avoid clashes but could take it over to finish if Fredric is not around this week

JasonWeill commented 9 months ago

December 20, 2023

Name	Affiliation	GitHub
Jason Weill	AWS	@JasonWeill
Andrii Ieroshenko	AWS	@andrii-i
Carlos Brandt		@chbrandt
Frederic Collonval		@fcollonval
Mike Krassowski	Quansight	@krassowski
Nick Bollweg	Georgia Tech	@bollwyvl
Mehmet Bektas	Netflix	@mbektas
Jeremy Tuloup	QuantStack	@jtpio
R Ely	Bloomberg	@ohrely
Gabriel Fouasnon	Quansight Labs	@gabalafou

Agenda

Jason W
- Should we have a meeting on December 27?
  - Consensus was not to have a meeting on 12/27.
Mike
- JupyterLab 4.1 beta 0 was released :tada:
  - to try it out
    - pip install jupyterlab==4.1.0b0
    - conda install -c conda-forge/label/jupyterlab_beta jupyterlab
  - migration guide for extension authors
  - lets announce it on Discourse community forum now and again (maybe a blog post) in the new year
- JupyterLab Desktop certificate for Windows is coming :tada:
  - Mehmet: it will also enable auto-updates on Windows
  - Fixes https://github.com/jupyterlab/jupyterlab-desktop/issues/202 and https://github.com/jupyterlab/jupyterlab-desktop/issues/261

Additional discussion

Jason W: Review 4.1.0 release blockers

Notes taken using JupyterLab on notebooks.gesis.org. For reference, we are running:

```bash $ pip list | grep jupyter jupyter_client 7.4.9 jupyter_collaboration 2.0.0 jupyter_core 5.4.0 jupyter-events 0.9.0 jupyter-lsp 2.2.1 jupyter-offlinenotebook 0.2.2 jupyter-resource-usage 0.7.1 jupyter_server 2.12.1 jupyter_server_fileid 0.9.0 jupyter-server-mathjax 0.2.6 jupyter_server_terminals 0.5.0 jupyter_server_ydoc 0.8.0 jupyter-telemetry 0.1.0 jupyter-ydoc 2.0.0 jupyterhub 3.1.1 jupyterlab 4.1.0b0 jupyterlab_git 0.50.0rc0 jupyterlab-lsp 5.0.1 jupyterlab-pygments 0.2.2 jupyterlab_server 2.25.0 jupyterlab-widgets 3.0.9 ```

jupyterlab / frontends-team-compass