Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Weekly Team Meetings: Jul-Dec 2023 #205

Closed
fcollonval opened this issue Jul 11, 2023 · 26 comments
Closed

Weekly Team Meetings: Jul-Dec 2023 #205

fcollonval opened this issue Jul 11, 2023 · 26 comments
Labels
Dev Meeting Minutes Minutes from a dev meeting.

Comments

@fcollonval
Copy link
Member

fcollonval commented Jul 11, 2023 •
edited by gabalafou
Loading

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 fcollonval added the Dev Meeting Minutes Minutes from a dev meeting. label Jul 11, 2023
@fcollonval fcollonval mentioned this issue Jul 11, 2023
Closed
@fcollonval
Copy link
Member Author

fcollonval commented Jul 11, 2023 •
edited by JasonWeill
Loading

July 5, 2023 (watch 📺)

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

@fcollonval fcollonval pinned this issue Jul 13, 2023
@fcollonval
Copy link
Member Author

fcollonval commented Jul 13, 2023 •
edited by JasonWeill
Loading

July 12, 2023 (watch 📺)

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

@fcollonval
Copy link
Member Author

fcollonval commented Jul 19, 2023 •
edited by JasonWeill
Loading

July 19, 2023 (watch 📺)

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

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

  • 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) Hosting our weekly meeting #197

@jtpio
Copy link
Member

jtpio commented Jul 27, 2023 •
edited by JasonWeill
Loading

July 26, 2023 (watch 📺)

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

@fcollonval
Copy link
Member Author

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
Copy link
Member Author

fcollonval commented Aug 3, 2023 •
edited by JasonWeill
Loading

August 2, 2023 (watch 📺)

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

Additional discussion

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

@fcollonval
Copy link
Member Author

fcollonval commented Aug 10, 2023 •
edited
Loading

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

    • ⚠️ 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 🙇 ). 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 😉 ). But I will leave the vote open for another week as participation is required to compute active status of council member.

  • Eric G

  • Jason W

    • Plug for weekly triage

  • Ely

  • Tony

Additional discussion

@fcollonval
Copy link
Member Author

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

@JasonWeill
Copy link
Contributor

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

@jtpio
Copy link
Member

jtpio commented Aug 30, 2023 •
edited by fcollonval
Loading

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)

  • Eric G

    • Extension tutorial is broken
    • 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 remove analytics jupyter/jupyter.github.io#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
Copy link
Member

jtpio commented Aug 30, 2023

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

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 #197

@fcollonval
Copy link
Member Author

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

PSA PRs that need review:

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

PSA: Sign up to host this meeting: #197

Additional discussion

  • Jason W: Bringing AI-based completion in core
    Integrate Copilot-like completions with JupyterLab jupyterlab#14267
    Integrate Copilot-like completions with JupyterLab jupyterlab#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 fcollonval mentioned this issue Sep 7, 2023
Merged
63 tasks
@fcollonval
Copy link
Member Author

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

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

PSA: Sign up to host this meeting: #197

Additional discussion

This was referenced Sep 20, 2023
Closed
Open
@fcollonval
Copy link
Member Author

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

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: #197

@krassowski
Copy link
Member

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

Additional discussion

Sign up to host this meeting: #197

@krassowski krassowski mentioned this issue Sep 29, 2023
Open
4 tasks
@krassowski
Copy link
Member

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

@krassowski
Copy link
Member

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

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

@brichet brichet mentioned this issue Oct 12, 2023
Merged
@fcollonval
Copy link
Member Author

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

Additional discussion

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

@krassowski
Copy link
Member

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

⚠️ 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.

@fcollonval
Copy link
Member Author

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

⚠️ 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.

Additional discussion

4.1.0 triage for issues, pull requests

Triaged pull requests:

@fcollonval
Copy link
Member Author

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

    • 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
Copy link
Member Author

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

Additional discussion

@fcollonval
Copy link
Member Author

fcollonval commented Nov 23, 2023 •
edited
Loading

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

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
Copy link
Member Author

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

Additional discussion

@brichet brichet mentioned this issue Nov 30, 2023
Open
63 tasks
@fcollonval
Copy link
Member Author

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

Additional discussion

  • [Demo time] Quickly open recent document (proposed for 4.2) #15483
  • Fix UI tests in JupyterLab

    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
Copy link
Contributor

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

Additional discussion

Notes taken using JupyterLab on notebooks.gesis.org. For reference, we are running: 
$ 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

@JasonWeill JasonWeill mentioned this issue Dec 20, 2023
Closed
@fcollonval fcollonval unpinned this issue Jan 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
Dev Meeting Minutes Minutes from a dev meeting.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@jtpio @krassowski @fcollonval @JasonWeill