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.

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

Weekly Team Meetings: Aug-Dec 2021 #128

Closed
isabela-pf opened this issue Aug 4, 2021 · 26 comments
Closed

Weekly Team Meetings: Aug-Dec 2021 #128

isabela-pf opened this issue Aug 4, 2021 · 26 comments
Labels
Dev Meeting Minutes Minutes from a dev meeting.

Comments

@isabela-pf
Copy link
Contributor

isabela-pf commented Aug 4, 2021

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.

(Thanks to @jasongrout for starting the last six-month note issue jupyterlab/retrolab#117 that I copied this intro from.)

Meeting Notes

@isabela-pf
Copy link
Contributor Author

isabela-pf commented Aug 4, 2021

Originally posted by @afshin

JupyterLab Weekly Call - August 4, 2021

Attendees

Name Organization GitHub Favorite Color
A. T. Darian Two Sigma @afshin pink
William Stein SageMath/CoCalc @williamstein White
Vidar T Fauske JP Morgan Chase @vidar Ultramarine
Steve Silvester Apple @blink1073 fuchsia
Loïc Huder ESRF @loichuder midnightblue
Martha Cryan IBM @marthacryan yellow
Isabela Presedo-Floyd Quansight Labs @isabela-pf orange!
Frederic Collonval QuantStack @fcollonval
Jessica Xu Quansight @jess-x
Nick Bollweg Georgia Tech @bollwyvl @nrbgt #000, also #chucknorris
Alex Bozarth IBM @ajbozarth Black
Piyush Jain AWS @3coins blue
Karla Spuldaro IBM @karlaspuldaro scarlet
Mike UOXF/own behalf @krassowski coffee
Gonzalo Quansight, inc @goanpeca blue
Kevin Bates IBM @kevin-bates Dodger Blue

Agenda

Additional Discussion

Links

  • settings UI

  • conda-forge multiple outputs

@isabela-pf isabela-pf added the Dev Meeting Minutes Minutes from a dev meeting. label Aug 4, 2021
@isabela-pf isabela-pf changed the title Weekly Dev Meetings: Aug-Dec 2021 Weekly Team Meetings: Aug-Dec 2021 Aug 4, 2021
@fcollonval
Copy link
Member

Originally posted by @afshin

JupyterLab Weekly Call, August 11, 2021

Attendees

Name Affiliation GitHub Favorite Street Food
A. T. Darian Two Sigma @afshin tteokbokki? toppoki?
Piyush Jain AWS @3coins छोले-पूरी
Frederic Collonval QuantStack @fcollonval French Belgian fries
Nick Bollweg Georgia Tech @bollwyvl @nrbgt DÖNER
Michał Krassowski Oxford @krassowski
William Stein SageMath, Inc. @williamstein navajo tacos
Kevin Bates IBM @kevin-bates carne asada tacos
Pete Blois Google (Colab) @blois chili dogs
Zach Sailer Apple @Zsailer tacos, obviously
Max Klein JPM @telamonian https://www.youtube.com/watch?v=Esi7zmmS-H4
Martha Cryan IBM @marthacryan banh mi
Vidar T Fauske JPMorgan Chase @vidartf tacooo
Alex Bozarth IBM @ajbozarth tacos
Isabela Presedo-Floyd Quansight Labs @isabela-pf
Carlos Herrero QuantStack @hbcarlos
Jason Grout Bloomberg @jasongrout
Jessica Xu Quansight @jess-x
Karla Spuldaro IBM @karlaspuldaro Brazilian coxinha

Agenda

  • William: I've been making an effort to encourage some developers of other Jupyter frontends to come to this meeting. (Hi Pete!) I hope this is OK. I think it's valuable since it's useful to see how problems have been solved, and get feedback about usage based on experience by hosting providers.

  • Frederic: new Galata (WIP - PR)

  • Max: what's the current state of the version pinning that jupyter lab build does?

    • recently came up at work: our python jlab pkg is at 3.0.14 while our js bundle is at 3.0.16 after a build
    • is there a potential for this to cause issues? Or has our semver discipline around changes to python<->js interactions been strong?
  • Piyush

    • Removed debug switch - PR
      Frederic has some comments to use command interface, want to get feedback from others and make sure this is the right direction to go.
    • Removed toolbar scrollbar - PR. Small change, is there any feedback?
  • nick

  • Adam

    • Question about sharedPackages.

Additional Discussion

@afshin
Copy link
Member

afshin commented Aug 18, 2021

JupyterLab Weekly Call, August 18, 2021

Attendees

Name Affiliation GitHub Favorite Fictional Villain
A. T. Darian Two Sigma @afshin Randall Flagg
Steven Silvester Apple @blink1073 Dr Claw
Vidar T Fauske JPMorgan Chase @vidartf
Martha Cryan IBM @marthacryan
Layne Sadler Julia Computing @aiqc Lich King (wow/lotr)
Pete Blois Google Colab @blois Dr Strangelove
Frederic Collonval QuantStack @fcollonval
Alex Bozarth IBM @ajbozarth
William Stein SageMath @williamstein Frank Underwood (House of Cards)
Isabela Presedo-Floyd Quansight Labs @isabela-pf Ozu from The Tatami Galaxy
Brian Granger AWS/Cal Poly @ellisonbg
Michał Krassowski U Oxford @krassowski sentiment analysis with Vader
Avish Mehta Student @avishmehta68710
Jason Grout Bloomberg @jasongrout
Luciano Resende IBM @lresende
Karla Spuldaro IBM @karlaspuldaro

Agenda

  • Isabela
    • Jupyter community call is in two weeks! Yay! More info on discourse
    • Quick feedback on how blind and visually impaired students are working around Jupyter inaccessibility. The main feedback is around getting code out of cells and in a place they can accessibly work on it. This add-on was also mentioned.
  • Martha

    • Small Settings UI demo!
  • Frederic

    • recurrent Jupyter Performance Meeting set up (thanks to Zach)
      It will be every 4 weeks after this meeting - next will be on September 1st 10am PT
      meeting notes - archived on GitHub
      • (william) I want to try to invite some people from collab/nteract -- how? It's particularly useful, since they have experience with fully implementing other approaches, e.g., Monaco editor, react, etc.
    • JupyterLab review
      • Backport of Firefox toolbar style fix #10849
      • Maintenance camelcase #10500
        Needs to look at the CodeQL Regex error.

Additional Discussion

  • Layne: If time allows, the "Ju" in Jupyter. Pluto. History?
    • JUlia PYThon R

@afshin
Copy link
Member

afshin commented Sep 1, 2021

JupyterLab Weekly Call, August 25, 2021

Attendees

Name Affiliation GitHub Favorite Flower
A. T. Darian Two Sigma afshin crocus sativus (saffron crocus)
Steve Silvester Apple blink1073 sunflower (the radioactive ones in TMNT 2)
Frederic Collonval QuantStack @fcollonval
Kevin Jahns Yjs / QuantStack @dmonad
Pete Blois Google @blois Dahlia
tonyfast quansight @tonyfast top shelf
Nick Bollweg Georgia Tech @bollwyvl @nrbgt morning glory
William Stein SageMath, Inc (CoCalc) @williamstein Iris
Carlos Herrero QuantStack @hbcarlos
Theodore Aptekarev Independent @piiq lavender
Jason Grout Bloomberg @jasongrout all? cool flower
Mehmet Bektas Splunk @mbektas Plumeria
Isabela Presedo-Floyd Quansight Labs @isabela-pf osteospermum
Brian Granger AWS, Cal Poly @ellisonbg ?
Vidar T Fauske JPMorgan Chase @vidartf orchids
Alex Bozarth IBM @ajbozarth
Martha Cryan IBM @marthacryan

Agenda

  • Frederic:
    • Translations
      • Documentation translation update policy (strings should not change in a patch release)
      • Add CI to check source strings are not change by a PR
    • CSS Icon deprecation PR10908
    • Galata PR10796 in 3.2.x as @jupyterlab/galata @4.0.0
  • Steve

    • JupyterLab 3.1.8 and 4.0.0a5
      • The testutils package was not populated due to #10891, hot fix coming in #10916
    • There is now a separate lint check that uses TypeScript, that does not run by default on commit see #10900 - will be much faster and less intrusive
    • Still working on automated release fixes
  • Jason

    • Assigning issues - we have a number of people requesting issues be assigned to them in the GitHub interface so that they can work on them. Sometimes these new contributors are optimistic about fixing an issue and a PR does not eventually come, but the issue is not ever unassigned (thus it appears to be "taken" to other new contributors). I would suggest as a policy that either:
      • in general, we not assign an issue to a person (an exception would be assigning a short list of issues to people in the final phases of a release when there is time pressure to finish that final set of issues, and we are documenting a short time-limited commitment from people to fix issues before a release)
      • or at least that we not assign an issue to a new contributor until after they have submitted a reasonable PR fixing the issue.
      • Based on the discussion in the meeting, I'll put a PR somewhere in the docs that says:
        • we encourage someone that wants to work on an issue to post a comment on the issue
        • we generally don't assign issues to people
        • we encourage draft PRs to be opened early in the development process and linking the draft PR back to the issue
      • Also, we could extend the bot to flag new PRs by first-time contributors for attention.
  • Isabela

    • Can we add the Jupyter discourse to the resources at the top of the mailing list?
    • Do we have a "don't show this again" or similar checkbox or settings for some dialogs?

      It was introduced for the renaming untitled files but it was not generic (and the feat. has been reverted).

    • Jupyter Community Call is next week! You can get more info on discourse
  • Carlos

    • Undo manager capture timeout
      • We are using the default (500ms), which groups sentences. This is the behavior of every OS and editor but Apple software. Apple capture every character individually. What behavior should we adopt? Or should we make it configurable?
      • (william) Apple maybe doesn't do it every character anymore. CoCalc is similar, but a longer timeout, and I'm not sure I like it.
      • Colab seems to group undos by a similar amount of time.
    • Document or cell level history tracking?
  • Brian

  • Vidar

  • Martha

    • Based on this spec modified fields that are very long make the modified fields section a little long / awkward? suggestion - indicator next to modified fields / keep plugin settings together

Additional Discussion

  • Frederic:
  • Darian / Pete / William
    • In RTC we should look at history to rewind, debug, etc.
      • I was talking to some users yesterday and they asked for a L/R panel that has a list of the timestamped versions of the doc.
    • William mentioned that their current collaborative meetings in CoCalc don't have the problems we were experiencing. What changed? Was it a technical change (refining the cocalc rtc implementation), or a behavioral change (understanding better how to collaborate)?

@afshin
Copy link
Member

afshin commented Sep 1, 2021

JupyterLab Weekly Call, September 1, 2021

Attendees

Name Affiliation GitHub Favorite Dinosaur
A. T. Darian Two Sigma @afshin peregrine falcon
Steven Silvester Apple @blink1073 stegasaurus
F. Collonval QuantStack @fcollonval
W. Stein SageMath @williamstein Pyrex-o-suarus
Pete Blois Google @blois Apatosaurus
Alex Bozarth IBM @ajbozarth raptor
Michał Krassowski Oxford @krassowski
Mehmet Bektas Splunk @mbektas
Gonzalo Peña-C Quansight @goanpeca T-rex
Jessica Xu Quansight @jess-x
Martha Cryan IBM @marthacryan
Karla Spuldaro IBM @karlaspuldaro
Jason Grout Bloomberg @jasongrout
Jeremy Tuloup QuantStack @jtpio
Rick McGeer engageLively @rickmcgeer Troodon
Brian Granger AWS/Cal Poly @ellisonbg

Agenda

Additional Discussion

  • Darian / Pete / William (from last week)
    • In RTC we should look at history to rewind, debug, etc.
    • I was talking to some users yesterday and they asked for a L/R panel that has a list of the timestamped versions of the doc.
    • William mentioned that their current collaborative meetings in CoCalc don't have the problems we were experiencing. What changed? Was it a technical change (refining the cocalc rtc implementation), or a behavioral change (understanding better how to collaborate)? [Answer from William: mostly just fixing bugs. You didn't have these problems when using hackpad? Example bug right now: every time somebody types the preview on the right keeps scrolling back to the top, which is annoying and hard to use.]
    • The coolest undo interface Jason has used is the undo tree interface in Emacs or Vim
    • A user might want to use global history vs local history in different phases in their work. For example, if they are iterating quickly in different cells, they may want a local cell undo. If they are trying to revert the document to the working state from yesterday, a global rollback mechanism is valuable.

Proposed dataset interface

https://github.com/jupyterlab/jupyterlab-data-explorer/blob/4beec8bf7a5d2cfb68985d4452fd6215f6f424bf/packages/dataregistry/src/dataset.ts

export interface Dataset<T extends JSONObject, U extends JSONObject> {
  /**
   * Unique identifier for the dataset, for in-memory
   * datasets, a unique uuid might be provided.
   * This id should be unique across a jupyter server instance.
   */
  id: string;
  abstractDataType: string;
  serializationType: string;
  storageType: string;
  /**
   * Output value for the dataset
   */
  value: T;
  /**
   * Additional properties for the dataset
   * that help serialize or query data
   */
  metadata: U;
  title: string;
  description: string;
  tags?: { [key: string]: string };
  version?: number;
}

@afshin
Copy link
Member

afshin commented Sep 8, 2021

JupyterLab Weekly Call, September 8, 2021

Attendees

Name Affiliation GitHub Favorite Ancient Monument
A. T. Darian Two Sigma @afshin Göbekli Tepe
William Stein SageMath, Inc. @williamstein The Mount Baker Volcano
Frederic Collonval QuantStack @fcollonval
Loïc Huder ESRF @loichuder Angkor Wat
Brian Granger AWS/Cal Poly @ellisonbg
Kevin Jahns Yjs / Quantstack @dmonad
Alex Bozarth IBM @ajbozarth
Steven Silvester Apple @blink1073 Barbican London Wall
Carlos Herrero QuantStack @hbcarlos
Jason Grout Bloomberg @jasongrout just found https://en.wikipedia.org/wiki/Megalith for good reading :)
Jessica Xu Quansight @jess-x
Youness Bennani Bloomberg @bsyouness Ek Balam
Isabela Presedo-Floyd Quansight Labs @isabela-pf Jantar Mantar
Mehmet Bektas Splunk @mbektas Galata Tower :)
Pete Blois Google @blois 2001 Monolith
Karla Spuldaro IBM @karlaspuldaro
Martha Cryan IBM @marthacryan
Rick McGeer engageLively @rickmcgeer Stonehenge
Max Klein JPM @telamonian
Nick Bollweg Georgia Tech @bollwyvl @nrbgt rosetta stone

Agenda

  • Loic

  • Brian

    • Enable disabling document-wide history tracking jupyterlab#10949 (comment)

    • In cocalc, William solves the simultaneous cell edit/move problem by just maintaining a "position" metadata field on each cell, and when a cell is moved, the position is just updated, i.e., it doesn't actually change an array datastructure. Caveat: you have to ensure the positions are unique. The position is a float so it is easy to insert between two other positions. Periodically, one of the processes renumbers all the cells as integers to take care of precision issues (it looks like maybe in the code now that is done by the client doing the cell move, since they can change anything globally anyways).

    • Regarding the discussion about moving objects in CRDTs: There is a discussion about it on the yjs discussion https://discuss.yjs.dev/t/moving-elements-in-lists/92 (Brian & William). Moving elements in a CRDT is not trivial but definitely possible. However, it always comes with tradeoffs. There is a solution described that sounds fairly similar to William's solution.

  • Isabela

    • Jupyter accessibility workshops are starting on October 2 and 9! We would like to have some more event moderators from the community. (More specific announcements to come!)
  • Max

    • yarn v3 upgrade!
      • almost done
      • Upgrade jlpm cmd to yarn 3.x jupyterlab#10929
      • one last problem: jlpm run vs yarn run (vs $npm_execpath run) in ensure-buildutils.js and other related scripts that might run as part of pip install ... before jlpm is properly installed
        • under discussion: move jlpm entrypoint to jupyterlab_server
  • Frederic

    • End of 3.1.x to start 3.2.x?
      Need to sync with @goanpeca to list if all 3.2.x feat. are ready.
    • Performance: status bar item position unstable - maybe related to #9910
    • Translation:
      • Settings are now translated before being served (JLab server 2.8+)
      • What about the documentation?
        It should be its own project on Crowdin. Ideally an intermediate step could be to get the translated text from the
        UI text; like sentence You can access that feature through the File menu.

Additional Discussion

  • Duplicate Design System CSS GitHub label? Can we remove?
    • Design System CSS
    • tag: Design System CSS
    • used in labeler

@afshin
Copy link
Member

afshin commented Sep 15, 2021

15 September 2021

Attendees

Name Affiliation GitHub Favorite semi-precious material
A. T. Darian Two Sigma @afshin amber
William Stein SageMath, Inc. @williamstein turquoise
Martha Cryan IBM @marthacryan
Jason Grout Bloomberg @jasongrout
Pete Blois Google @blois tungsten
Karla Spuldaro IBM @karlaspuldaro
Mehmet Bektas Splunk @mbektas
Kevin Jahns Yjs / Quantstack @dmonad clay
Steven Silvester Apple @blink1073
Jeremy Tuloup QuantStack @jtpio
Mithil Poojary @Mithil467 titanium
Rick McGeer engageLively @rickmcgeer chicken-blood stone
Nick Bollweg Georgia Tech @nrbgt @bollwyvl coprolite
Isabela Presedo-Floyd Quansight Labs @isabela-pf
Alex Bozarth IBM @ajbozarth
Frederic Collonval QuantStack @fcollonval
Mike Oxford @krassowski
Konstantin Taletskiy Axle Informatics/NIH NCATS @ktaletsk emerald

Agenda

  • Martha

  • Jeremy:

  • Frederic

    • Remove old phosphor class to reduce CSS class stack (goal improve performances by reducing style computation complexity)
      • This implies upgrading @Lumino packages to the next major version
      • Opportunity to update typescript
      • Need to wait for IPyWidgets v8 to be compatible to lumino
      • other things we had considered for lumino 2.0:
        Better react integration
        Use native iterators instead of the custom lumino ones
        Provide ways to consume signals using ReactiveX
        Meta-issue opened Lumino v2 Plan lumino#233
  • Mehmet

  • Konstantin

    • JupyterLab LaTeX extension
    • jupyterlab-latex 3.1.0 - federated extension now
    • Becoming a maintainer?
      • +1 from @jasongrout to you becoming a maintainer for jupyterlab-latex - thanks! @blink1073 - I added you as a maintainer on the repo
    • Incoming group of 5 Georgia Tech students working on Computer Science Junior Design Capstone project we proposed. Improvements to LaTeX experience in JupyterLab:
      • bibliography tools
      • journal templates repository
      • drag-and-drop support for plots and data frames from Jupyter notebook into the editor
      • simplified uploads of figures into the publications
      • UI to quickly create tables, equations and find mathematical symbols
    • Discussion: do these features belong in the extension? Or is it something out of scope/should be in separate extension?
      • CoCalc/Colab perspective: How do we support notebooks with bibliography (say) in a consistent way...? (I thought this had to do with Jupyter notebooks, but it doesn't.)
  • Steve

Additional discussions

  • Frederic
    • benchmark tests
      • [Michal] It seems there is a bit of a jitter due to VMs with different processors being assigned. Would it be a good idea to try to divide the time by some performance score from a third-party benchmark of a processor and show it as "normalized score" in addition to time lapsed?
      • Another option is a self-hosted runner that only runs on push, maybe using our project AWS credits. https://docs.github.com/en/actions/hosting-your-own-runners/about-self-hosted-runners
        I think the best we can do is deal with the runner differences and have a large threshold for change, which is what this action does: https://github.com/rhysd/github-action-benchmark
        Follow up 🚧 change the logic to switch to manual to launch more experiments to improve statistical information by comparing the base node of the PR and the head (we want to be independent of the evolution of master).
    • Sponsors: What about adding NumFocus sponsor badge on JupyterLab projects as conda-forge does? jupyter.org uses this link

@fcollonval
Copy link
Member

fcollonval commented Sep 22, 2021

22 September 2021

Attendees

Name Affiliation GitHub Favorite season
Frederic Collonval QuantStack @fcollonval Fall
Alex Bozarth IBM @ajbozarth winter
Vidar T Fauske JP Morgan Chase @vidartf no
William Stein SageMath, Inc. @williamstein Early Spring
Mehmet Bektas Splunk @mbektas Summer
Rick McGeer engageLively @rickmcgeer Fall
Pete Blois Google @blois Fall
Carlos Herrero QuantStack @hbcarlos Winter
Afshin T. Darian Two Sigma @afshin Autumn
Karla Spuldaro IBM @karlaspuldaro Fall
Isabela Presedo-Floyd Quansight Labs @isabela-pf autumn
Rebecca Ely Bloomberg @ohrely Spring
Jeremy Tuloup QuantStack @jtpio Summer

Agenda

Additional discussions

@fcollonval
Copy link
Member

29 September 2021

Attendees

Name Affiliation GitHub Favorite music instrument
Alex Bozarth IBM @ajbozarth trumpet
William Stein SageMath, Inc. @williamstein Harpsichord
Vidar T Fauske JP Morgan Chase @vidartf Contra-Bassoon
Frederic Collonval QuantStack @fcollonval xylophone
Tony Fast Quansight @tonyfast trash
Martha Cryan IBM @marthacryan piano
Rick McGeer engageLively @rickmcgeer Accordion
Carlos Herrero QuantStack @hbcarlos
Mehmet Bektas Splunk @mbektas
Pete Blois Google @blois Trumpet
Zach Sailer Apple @Zsailer Guitar
Steven Silvester Apple @blink1073 Piano
Jeremy Tuloup QuantStack @jtpio Synth
Jason Grout Bloomberg @jasongrout French horn is nice
Rebecca Ely Bloomberg @ohrely Upright Bass
Adam Patterson UM @adpatter conchs
Kevin Bates IBM @kevin-bates Talking drum
Jessica Xu Quansight @jess-x Bass drum
Isabela Presedo-Floyd Quansight Labs @isabela-pf vocal cords?

Agenda

  • Zach

  • Frederic

    • Performance meeting just after this one
    • Drop of Blueprint: #11173
  • Mehmet

    • JupyterLab Desktop App Release
    • Released v3.1.13-1
      (https://github.com/jupyterlab/jupyterlab_app/releases)
    • Bug fixes & enhancements
      • Windows re-launch issues
      • Classic Notebook launch problem
      • Automated JupyterLab version upgrade
    • Stats (past week)
      • GitHub: 50 stars to ~1100 stars. 2nd most starred project in jupyterlab org now
      • Twitter: 150k impressions, 10k total engagements, 1300 likes
    • Most requested features
      • Launching from commandline (directory & file)
      • Ability to connect another conda env
        • numerous comments about this on the Hacker News Discussion, e.g., "It comes with it’s own conda environment. But can it ran in my conda environment? Which is pretty much a requirement for any serious project."
      • Ability to connect to remote env
  • Carlos

    • Move jupyterlab-js-logs to core:

    • Add a new package IUser to core

      • Discussion: IUser to represent a connected users jupyterlab#10965.
      • PR: Add new package "user" to represent a connected users jupyterlab#11180
      • The PR introduces three new plugins:
        • ICurrentUser that provides a representation of the connected user, the idea is that some extensions will require this plugin to modify the information (an extension for Hub to fetch the user info from the backend), and other extensions will require the user just to read the information (docprovider to use this identity in RTC, or and extension to add comments in a notebook)
        • IUserMenu that adds a new menu to the JupyterLab toolbar with the current user's name allows anonymous users to rename themself and provides a lumino menu where extensions can add different buttons to actions related to the user (Login with GitHub, Logout, settings, ...).
        • IUserPanel (Maybe needs to be renamed) it's a side panel to add info about the current user and the shared document (who is collaborating, what permissions they have, ...)
          • In cocalc a nice little feature is that you can click on the user's avatar and it scrolls your document to the place where they are editing.
  • Steve

Additional discussions

I have a Lumino question - if there is time (Adam Patterson).

Discussion on line endings
There is a implicit conversion of file ending to normalize it (with \n) to avoid synchronization warning.
Question: should we remove the debugging code linked to the line ending?
👍 Vidar / Pete and Vidar supports having the dialog because it informs the app is in a broken state

@ajbozarth
Copy link
Member

6 October 2021

Attendees

Name Affiliation GitHub Favorite animated TV show
Alex Bozarth IBM @ajbozarth Gurren Lagann
William Stein SageMath, Inc. @williamstein South Park
Jason Grout Bloomberg @jasongrout Daniel Tiger
Rick McGeer engageLively @rickmcgeer Star Trek: Lower Decks
Steven Silvester Apple @blink1073 X-Men
Mehmet Bektas Splunk @mbektas Family Guy
R Ely Bloomberg @ohrely Batman: The Animated Series
Luciano Resende Apple @lresende Dungeons & Dragons
Tony Fast Quansight @tonyfast Animaniacs
Martha Cryan IBM @marthacryan
Nick Bollweg Georgia Tech @bollwyvl @nrbgt Star Wars: Clone Wars (2003)
Pete Blois Google @blois Aeon Flux
Isabela Presedo-Floyd Quansight Labs @isabela-pf The Tatami Galaxy
Karla Spuldaro IBM @karlaspuldaro Timon & Pumbaa
Jeremy Tuloup QuantStack @jtpio
Jessica Xu Quansight @jess-x

Agenda

  • Steve
    • Working 3.2RC0. Currently blocked by an issue related to hashing and Webpack. Still debugging.
  • Mehmet
  • Jason: Document-wide undo/redo questions
    • Discussion
    • Initial PR
    • Follow-up PR
    • To enable 3.0 behavior, set Notebook.experimentalDisableDocumentWideUndoRedo to true (after
    • Discussion:
      • We should support the 3.0 local undo/redo behavior as the default if the --collaborative flag is not enabled. The current implementation comes close, but technical difficulties mean that moving a cell kills the undo functionality in that cell moving forward. Possible solutions include:
        • We can actually go back to the 3.0 implementation (punting to CodeMirror undo/redo) without too much trouble for non-collaborative situations, according to Kevin. We might have to actually delete and insert a new codemirror, but we should be able to copy the undo history over to the new codemirror. Kevin said he would engage more on this idea.
        • William suggested that maybe a hack is to delete and add a new cell when moving a cell in order to get the undo/redo history going forward, even if past undo history is deleted.
  • Isabela
    • Do we have review guidelines for the project?
      • We don't have explicit review guidelines
      • The ladder of feedback article was mentioned as a way to clearly communicate the importance of various review feedback.
      • We discussed the value of having mentors that can help new contributors, acknowledging that it is also a resourcing difficulty, but also emphasizing that anyone can help new contributors, including other newer contributors.
  • Nick

@fcollonval
Copy link
Member

fcollonval commented Oct 13, 2021

13 October 2021

Attendees

Name Affiliation GitHub Favorite Planet
Frederic Collonval QuantStack @fcollonval Neptune
Johan Mabille QuantStack @JohanMabille Earth
William Stein SageMath, Inc. @williamstein Earth
Mehmet Bektas Splunk @mbektas Earth
Pete Blois Google @blois Pluto
Rick McGeer engageLively @rickmcgeer Eris
Alex Bozarth IBM @ajbozarth Mars
Martha Cryan IBM @marthacryan Venus
Steven Silvester Apple @blink1073 Pluto
Carlos Herrero QuantStack @hbcarlos
Kevin Jahns QuantStack / Yjs / Church of VIM @dmonad Jupyter
Jeremy Tuloup QuantStack @jtpio Saturn
Tony Fast Quansight @tonyfast Mars
Michał Krassowski Oxford @krassowski Mars
Jason Grout Bloomberg @jasongrout Earth
Cameron Durbin ParaTools @PlatinumCD Saturn
Vidar T Fauske JP Morgan Chase @vidartf Neptune
Jessica Xu Quansight @jess-x Pluto
Piyush Jain AWS @3coins Earth
R Ely Bloomberg @ohrely Mars

Agenda

Additional discussions

  • I feel like the last columns in the Attendees list in these meeting notes are slowly asking me for all my security questions.. :D
    • that is part of the reason why I (another person) often leave them blank

@isabela-pf
Copy link
Contributor Author

isabela-pf commented Oct 13, 2021

  • I feel like the last columns in the Attendees list in these meeting notes are slowly asking me for all my security questions.. :D
    • that is part of the reason why I (another person) often leave them blank

This is a great point! Are there any recommendations for fun questions that won't risk this, or is it just putting personal information at all that is the concern?

@williamstein
Copy link

williamstein commented Oct 13, 2021 via email

@jasongrout
Copy link
Contributor

Could the questions instead be a little more specialized, so they can't possibly overlap with generic security questions? E.g.

Awesome idea. More:

  • favorite command line tool
  • favorite Jupyter frontend (maybe eye-opening to ask?? :)
  • least favorite command-line tool
  • favorite programming language
  • favorite git command

@fcollonval
Copy link
Member

fcollonval commented Oct 20, 2021

20 October 2021

Attendees

Name Affiliation GitHub Favorite Jupyter Kernel
Rick McGeer engageLively @rickmcgeer Python3
Alex Bozarth IBM @ajbozarth
Pete Blois Google @blois ipython 2.0
William Stein SageMath, Inc. @williamstein SageMath
Tony Fast Quansight @tonyfast pidgy
Frederic Collonval QuantStack @fcollonval
Steven Silvester Apple @blink1073 Octave
Max Klein JPM @telamonian ProxyProvider
Jessica Xu Quansight @jess-x
Nick Bollweg Georgia Tech @nrbgt @bollwyvl @deathbeds/jyve-kyrnel-coffee-unsafe
Michał Krassowski Oxford @krassowski
Mehmet Bektas Splunk @mbektas
Jeremy Tuloup QuantStack @jtpio Echo
Carlos Herrero QuantStack @hbcarlos
R Ely Bloomberg @ohrely
Isabela Presedo-Floyd Quansight Labs @isabela-pf
Jason Grout Bloomberg @jasongrout Xeus example
Martha Cryan IBM @marthacryan

Agenda

Additional discussions

@fcollonval
Copy link
Member

27 October 2021

Attendees

Name Affiliation GitHub Favorite Package on Pypi
Frederic Collonval QuantStack @fcollonval cycler
Rick McGeer engageLively @rickmcgeer pickleshare
Mehmet Bektas Splunk @mbektas
Alex Bozarth IBM @ajbozarth
Pete Blois Google @blois emoji
Jason Weill AWS none yet (I'm new) none yet
William Stein SageMath, Inc. @williamstein sagemath ("This is a dummy package...")
Carlos Herrero QuantStack @hbcarlos
Michał Krassowski Oxford @krassowski antigravity
R Ely Bloomberg @ohrely
Jeremy Tuloup QuantStack @jtpio server
Jason Grout Bloomberg @jasongrout
Tony Fast Quansight @tonyfast tonyfast
Isabela Presedo-Floyd Quansight Labs @isabela-pf
Jessica Xu Quansight @jess-x
Nick Bollweg Georga Tech @nrbgt @bollwyvl pants

Agenda

  • Carlos

    • ICurrentUser:
      • Add new package "user" to represent a connected users jupyterlab#11180
      • MainAreaWidget header
      • [William]:
        • You could make it stupidly easy for people to provide feedback when using collaborative jlab collaboratively? Add a button to provide feedback. I learned a huge amount doing that about what matters.
        • Do you plan to have chat on the side of documents ever?
        • In Cocalc: When you look at the file listing in a project, it shows collabs who are active on the project, and when you click on them, it opens the document they were last active on. Once that doc is open it looks exactly like what was just demoed… except the avatar fades out over time.
        • The number one thing I learned was that the core functionality of RTC has to work 99.99%, not 98%. Even the slightest edge case problems are very impactful.
    • Add support for RBAC:
  • Mehmet

    • Released JupyterLab Desktop v3.2.1-1
      • Upgraded to JupyterLab v3.2.1
      • Fixes for export downloads, menubar visibility on macOS in maximized mode
      • Other fixes & enhancements
    • Working on code-signing for macOS with NumFOCUS
    • Stats: ~1000 daily downloads
  • Frederic

    • JupyterLab Performance meeting just after this one; meeting notes

Additional discussions

  • JupyterLab 4.0 roadmap:
    • GitHub project
    • Spreadsheet
      • jupyterlab-git integration: not likely to be moved into core, reomved from the release schedule; instead we will try to create a metapackage in contrib with "batteries included" and discuss if we can have it in Desktop by default, but as [Nick] says its install size is already large and we need to decide when it stops (do we include latex?) [removed from the project]
      • displaying variables: some work already merged, ongoing work on improvements [marked as merged]
      • better undo/redo: work in progress to enable moving cells without loosing history [moved to in progress]
      • user interface for workspaces: no one working on it? [left for now]
      • restart and re-run: no one working on it? [left for now]
      • syntax highlight in SQL: no one working on it? [left for now]
  • FYI: Pydata Global is Oct 28-30. Kevin and Jeremy and many others are on the schedule.
  • [Discuss] The future of the classic notebook interface: [Discuss] The future of the classic notebook interface jupyter/notebook#6210

@fcollonval
Copy link
Member

fcollonval commented Nov 3, 2021

3 November 2021

Attendees

Name Affiliation GitHub Favorite git command
Frederic Collonval QuantStack @fcollonval git rebase -i
Rick McGeer engageLively @rickmcgeer whatever I need to get what I'm doing now done
Jason Grout Bloomberg @jasongrout git pull
Alex Bozarth IBM @ajbozarth git stash
William Stein SageMath @williamstein git commit -av
Steven Silvester Apple @blink1073 git push upstream -f
Jason Weill AWS @jweill-aws git status
Jessica Xu Quansight @jess-x git log
Pete Blois Google @blois hg init
R Ely Bloomberg @ohrely git bisect
Carlos Herrero QuantStack @hbcarlos
Kevin Jahns Yjs / QuantStack @dmonad git shortlog -s
Jeremy Tuloup QuantStack @jtpio git clean
Tony Fast quansight @tonyfast git submodule
Mehmet Bektas Splunk @mbektas
Gabriel Fouasnon Quansight @gabalafou To archive and delete a branch:
git tag archive/<branchname> <branchname>
git branch -d <branchname>
Isabela Presedo-Floyd Quansight Labs @isabela-pf
Karla Spuldaro IBM @karlaspuldaro git push --force
Michał Krassowski Oxford @krassowski stash

Agenda

Additional discussions

  • Overcrowded toolbar [Tony]: how to deal with overcrowded toolbar due to many extension buttons

    • The new Reactive Toolbar helps a lot
    • For 4.0, the user will be able to customize the toolbar through settings - see documentation
      This implies that the extensions will be updated to define their toolbar in the settings.
  • JupyterLab 4.0 roadmap:

@fcollonval
Copy link
Member

fcollonval commented Nov 10, 2021

10 November 2021

Attendees

Name Affiliation GitHub Favorite command-line tool
Frederic Collonval QuantStack @fcollonval
Rick McGeer engageLively @rickmcgeer awk
Jeremy Tuloup QuantStack @jtpio yes
Jason Weill AWS @jweill-aws watch
R Ely Bloomberg @ohrely
Pete Blois Google @blois rm -rf
Alex Bozarth IBM @ajbozarth
Loic Huder ESRF @loichuder sl (not a typo)
Tony Fast quansight @tonyfast doit/nox
Martha Cryan IBM @marthacryan man
Gabriel Fouasnon Quansight @gabalafou xargs
nick bollweg georgia tech @bollwyvl @nrbgt cowsay
Piyush Jain AWS @3coins find
Steven Silvester Apple @blink1073 podman
Vidar T Fauske JP Morgan Chase @vidartf grep
Jessica Xu Quansight @jess-x
Jason Grout Bloomberg @jasongrout
Isabela Presedo-Floyd Quansight Labs @isabela-pf

Agenda

Additional discussions

@hbcarlos
Copy link
Member

Regarding the undo manager issue to disable the document-wide history, Kevin is working on a new feature in YJS that will solve the issue. He will open a PR soon, but I'm unsure of the actual state.

@fcollonval
Copy link
Member

17 November 2021

Attendees

Name Affiliation GitHub Favorite programming language
Frederic Collonval QuantStack @fcollonval Python what else
A. T. Darian Two Sigma @afshin
Piyush Jain AWS @3coins Python
Martha Cryan IBM @marthacryan
Jason Weill AWS @jweill-aws TypeScript
Michał Krassowski Oxford @krassowski Python
R Ely Bloomberg @ohrely Scala
Jason Grout Bloomberg @jasongrout
Jeremy Tuloup QuantStack @jtpio
Eric Charles Datalayer @echarles
Jessica Xu Quansight @jess-x
Rick McGeer engageLively @rickmcgeer Smalltalk
Karla Spuldaro IBM @karlaspuldaro
Pete Blois Google @blois
Nick Bollweg Georgia Tech @bollwyvl logo
Martin Renou QuantStack @martinRenou Not decided yet
Gabriel Fouasnon Quansight @gabalafou Lisp?
Mehmet Bektas Splunk @mbektas C++
Carlos Herrero QuantStack @hbcarlos
Ahmed Fasih Bloomberg @fasiha still waiting
tony fast quansight @tonyfast markdown
Isabela Presedo-Floyd Quansight Labs @isabela-pf

Agenda

Additional discussions

@fcollonval
Copy link
Member

24 November 2021

Attendees

Name Affiliation GitHub Favorite favorite topics
Frederic Collonval QuantStack @fcollonval
Sylvain Corlay QuantStack @SylvainCorlay
Rick McGeer engageLively @rickmcgeer Obscure dictionary word
Pete Blois Google @blois
Nick Bollweg Georgia Tech @bollwyvl downfall of society
Karla Spuldaro IBM @karlaspuldaro
R Ely Bloomberg ohrely ice cream flavor
Michał Krassowski Oxford @krassowski
Isabela Presedo-Floyd Quansight Labs @isabela-pf favorite ancient monument
Konstantin Taletskiy Axle Informatics/NIH @ktaletsk Favorite holiday food
Alex Bozarth IBM @ajbozarth
Martin Renou QuantStack @martinRenou Favorite between Jupyter Notebook and JupyterLab
Carlos Herrero QuantStack @hbcarlos
Gabriel Fouasnon Quansight Labs @gabalafou Favorite books

Agenda

JupyterLab 3.x or 4.0 for notebook 7 issue
Currently RetroLab (to-be notebook 7) is based on lab 3.x branch. But some new features will be needed for it:

  • Customize widget position to fit with notebook layout
  • Add cells toolbar ([TBC] bringing jlab-enhanced-cell-toolbar in Lab)
  • Add tour (bringing jupyterlab-tour in Lab)
    Cons for 3.x
  • If we do a release 3.x for it, this will strip more reasons to update to JLab 4.
  • If it is linked to 4, this avoid releasing notebook 8 after JLab 4 😉
  • An excuse for extensions authors to modify their extension to be compatible because the API has changed.
    Pros for 3.x
  • [Mike] IMO for Notebook we need prebuilt extension manager
  • Less breaking changes?

[Afshin] it makes sense regarding the amount of work to be done for notebook v7 that it will be based on JLab 4. Moreover it will be better to not annoy extension authors that just got converted to NPM world to modify again their extensions because we bumped the major version.

Additional discussions

N/A

@fcollonval
Copy link
Member

01 December 2021

Attendees

Name Affiliation GitHub Favorite Ice Cream Flavor
Frederic Collonval QuantStack @fcollonval Rum Raisin
William Stein SageMath @williamstein chocolate
Carlos Herrero QuantStack @hbcarlos
Isabela Presedo-Floyd Quansight Labs @isabela-pf i can't choose!
Gabriel Fouasnon Quansight Labs @gabalafou Americone Dream
Alex Bozarth IBM @ajbozarth mint chip
R Ely Bloomberg @ohrely Bailey's
Pete Blois Google @blois Bubblegum
Ahmed Fasih Bloomberg @fasiha rocky road
Jeremy Tuloup QuantStack @jtpio
Jason Grout Databricks @jasongrout Homemade Vanilla?
Mehmet Bektas Splunk @mbektas
Theodore Aptekarev No org 🤷‍♂️ @piiq Lemon sorbet
Jessica Xu ☝️ @jess-x Horchata
Martin Renou QuantStack @martinRenou

Agenda

Link to good first issues (good way to start contributing): https://github.com/jupyterlab/jupyterlab/issues?q=is%3Aopen+is%3Aissue+label%3A%22good+first+issue%22

Additional discussions

  • Link to JupyterLab 4 roadmap: GitHub project
  • Update on undo feature: additional tests are on their way on yjs to be able to bring it in JupyterLab then.

@fcollonval
Copy link
Member

08 December 2021

Attendees

Name Affiliation GitHub Favorite Ancient Monument
Alex Bozarth IBM @ajbozarth Liberary of Alexandria
Frederic Collonval QuantStack @fcollonval
Martha Cryan IBM @marthacryan
William Stein SageMath, Inc. @williamstein
Jason Weill AWS @jweill-aws Great Pyramids
Vidar T Fauske JP Morgan Chase @vidartf
R Ely Bloomberg @ohrely Moai
Gabriel Fouasnon Quansight Labs @gabalafou Hagia Sophia
Pete Blois Google @blois Parthenon
Martin Renou QuantStack @martinRenou
Piyush Jain AWS @3coins
Brian Granger AWS @ellisonbg
Kevin Jahns QuantStack / Yjs @dmonad
Mehmet Bektas Splunk @mbektas
Sylvain Corlay QuantStack @SylvainCorlay
Johan Mabille QuantStack @JohanMabille
Karla Spuldaro IBM @karlaspuldaro Machu Picchu
Matt Henderson LBNL @mlhenderson Pyramids
Jason Grout Databricks @jasongrout Obelisks?
Carlos Herrero QuantStack @hbcarlos
Jeremy Tuloup QuantStack @jtpio
Jessica Xu @jess-x
Michał Krassowski Oxford @krassowski
Isabela Presedo-Floyd Quansight Labs @isabela-pf

Agenda

Additional discussions

@fcollonval
Copy link
Member

15 December 2021

Attendees

Name Affiliation GitHub Favorite Dish for Christmas
Alex Bozarth IBM @ajbozarth Peanutbutter Balls
Johan Mabille QuantStack @JohanMabille
David Brochart QuantStack @davidbrochart
William Stein SageMath/CoCalc @williamstein
Craig Citro Google @craigcitro pie
Martin Renou QuantStack @martinRenou Turkey and Chestnuts
Martha Cryan IBM @marthacryan
Carlos Herrero QuantStack @hbcarlos Puchero
Michal Krassowski Oxford @krassowski
tonyfast quansight @tonyfast
Piyush Jain AWS @3coins
Ely Bloomberg @ohrely Chinese Takeout
Frederic Collonval QuantStack @fcollonval Cheese soufflé
Sylvain Corlay QuantStack @SylvainCorlay Champagne
Kevin Jahns QuantStack / Yjs @dmonad Printen
Gabriel Fouasnon Quansight @gabalafou
Pete Blois Google @blois Cranberries
Matt Henderson LBNL @mlhenderson Cookies
Karla Spuldaro IBM @karlaspuldaro Chocolate Panettone
Jason Grout Databricks @jasongrout Bratzeli
Jeremy Tuloup QuantStack @jtpio
Isabela Presedo-Floyd Quansight Labs @isabela-pf
Ahmed Fasih Bloomberg @fasiha mapo tofu

Agenda

Additional discussions

These meetings will continue to be held through the holiday season (Dec 22, Dec 29).

@fcollonval
Copy link
Member

22 December 2021

Attendees

Name Affiliation GitHub Favorite Winter Sport
Frederic Collonval QuantStack @fcollonval Eating cheese
Jason Weill AWS @jweill-aws Ice hockey, eating bredele
William Stein SageMath, Inc. (CoCalc) @williamstein Splitboard Mountaineering on Volcanoes
Gabriel Fouasnon Quansight @gabalafou Hot tubbing
Carlos Herrero QuantStack @hbcarlos
Sylvain Corlay QuantStack @SylvainCorlay Eating Raclette
Karla Spuldaro IBM @karlaspuldaro ice skating
Mehmet Bektas Splunk @mbektas
R Ely Bloomberg @ohrely complaining
Ahmed Fasih Bloomberg @fasiha snowman-making
A. T. Darian Two Sigma @afshin Hockey
Isabela Presedo-Floyd Quansight Labs @isabela-pf cleaning leaves out of gutters when it rains
Pete Blois Google @blois Skate skiing
Matt Henderson LBNL @mlhenderson
M Krassowski Oxford @krassowski

PRs needing review

Agenda

Additional Discussions

This meeting will not be held next week (Dec 29).

@fcollonval
Copy link
Member

The notes starting from January 2022 are in jupyterlab/retrolab#135

@fcollonval fcollonval unpinned this issue Feb 2, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Dev Meeting Minutes Minutes from a dev meeting.
Projects
None yet
Development

No branches or pull requests

7 participants