Weekly Dev Call 2020-02-05

[tgeorgeux]

5 February 2020 Weekly Meeting

• Introductions
• Tim
  • Working on Command Palette and in-Cell UI for 3.0
• Darian
  • Another debugger 0.2 alpha release this week
  • Question about FontAwesome
  • Update on governance / question for discussion
• Steve
  • Released RC 2.0
  • Posted notes on extension system refactor: Extension Development Wishlist jupyterlab#7468 (comment). Summary: bundle with Parcel (it gives us the appropriate intermediate format) and use a private requirejs as a loader (battle-tested code, but private variable so it is an implementation detail)
• Alex
  • Was working on moving our extensions onto the 2.0 beta/rc specifically becoming familar with the new LabIcon work. Starting this week will be setting time aside to work on jupyterlab issues specifically (not just our extensions) -> open to direction
• Gordon
  • Lumino UMD PR Discussion feat(build): Add UMD support lumino#40
• Jason
  • Working on ipywidgets 8 (and JupyterCon, etc.)
  • FYI, zmq has default "high water mark" of 1000 messages, after which it can start dropping messages, so if you ever are in a situation where you have a lot of messages coming from the kernel and some are dropped, think about the zmq buffer (1, 2)
• Max
  • JLIcon is now LabIcon
    • Clean up handling of Icons under unified LabIcon jupyterlab#7767
• Vidar
  • Added Dummystore on RTC repo for a non-collaboration datastore interface implementation https://github.com/jupyterlab/rtc/pull/4
  • RC consumption noise: Either not include source map, or include source in dist jupyterlab#7851
• Additional Discussion
  • When to Freeze API for 3.0 release.
    • Should we appoint a release manager and let them take input and make a final decision?
    • We will hold a meeting about this post-2.0 final release.
  • Governance questions re: delegates
  • Lumino packaging UMD (min files / sourcemaps / types)