Jupyter Server Notes 2020

Zsailer commented 5 years ago

Hello everyone,

Welcome to the Jupyter Server Team!

You can find us in our Gitter chat room or visit us at our weekly meetings!

We meet on Thursdays at 8:00am, Pacific Standard Time on Jupyter's Zoom Channel. You can add yourself to the weekly agenda here. Everyone is welcome!

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

Meeting Minutes

December 17th, 2020
December 10th, 2020
December 3rd, 2020
November 26th, 2020 - no meeting (US Holiday - Thanksgiving)
November 19th, 2020
November 12th, 2020
November 5th, 2020
October 29th, 2020
October 22nd, 2020
October 15th, 2020 - no meeting for JupyterCon 2020
October 8th, 2020 - no meeting for JupyterCon 2020
October 1st, 2020 - no minutes captured (sorry about that)
September 24th, 2020
September 17th, 2020
September 10th, 2020
September 3rd, 2020
August 27th, 2020
August 20th, 2020
August 13th, 2020
August 6th, 2020
July 30th, 2020
July 23rd, 2020
July 16th, 2020
July 9th, 2020
July 2nd, 2020
June 25th, 2020
June 18th, 2020
June 11th, 2020
June 4th, 2020
May 28th, 2020
May 21st, 2020
May 14th, 2020
May 7th, 2020
April 30th, 2020
April 23rd, 2020
April 16th, 2020
April 9th, 2020
April 2nd, 2020
March 26th, 2020
March 19th, 2020
March 12th, 2020
March 5th, 2020
February 27th, 2020
February 20th, 2020—meeting canceled.
February 13th, 2020
February 6th, 2020
January 30th, 2020
January 16th, 2020
January 9th, 2020
January 2nd, 2020
December 12th, 2019—no meeting.
December 5th, 2019
November 21st, 2019
November 7th, 2019
October 31st, 2019
October 24th, 2019
October 17th, 2019
October 10th, 2019

Zsailer commented 5 years ago

October 10th, 2019

Attendees

Add your name to the table below:

Name	affiliation	username
Zach Sailer	Jupyter Cal Poly	@Zsailer
Eric Charles	Datalayer	@echarles
Steven Silvester	J.P. Morgan Chase	@blink1073
Vidar T Fauske	J.P. Morgan Chase	@vidartf
Kyle R Kelley	Netflix	@rgbkrk
M Pacer	Netflix	@mpacer
Carol Willing	Project Jupyter	@willingc
Kevin Bates	IBM	@kevin-bates
Luciano Resende	IBM	@lresende
Safia Abdalla	Microsoft	@captainsafia

There were other attendees at the meeting, but they were not added to the list.

Agenda + Minutes

[x] Background [name=@Zsailer]
- Proposal: separate the Python server from the classic Notebook frontend.
  - Jupyter Enhancement Proposal
  - Jupyter Server Documentation
- Motivation: make all Jupyter frontends equal citizens in the eyes of the server.
  - All frontends are a server extension.
  - n frontends to 1 server.
- Positive Side-effects:
  - Server can evolve for next generation frontends without being constrained by classic notebook (e.g. see Kernel Provider proposal).
  - Jupyter Server becomes a replaceable component. We can explore new implementations of the server.
- Challenges:
  - What do we do with jupyter/notebook?
  - Migration pains (the APIs and traitlets bases change name).
  - Further confusion for users—where are issues, PRs, bugs, etc. coming from and where should they be reported.
[x] Current Progress [name=@Zsailer]
1. Forked Notebook in July 2018
2. Notebook + Jupyter Server in sync (Ported ~60 PRs from Notebook).
3. Jupyter Server frontends
  - For nteract, jupyterlab, voila, notebook, etc.
  - Demo: ExtensionApp
    - Before, we subclassed NotebookApp.
    - Now, we subclass ExtensionApp.
  - Documentation: xx
  - Current examples:
    - Simple Extension Example jupyter_server#117
    - jupyter/notebook
    - voila-dashboards/voila
[x] [Poll] Community Adoption of Jupyter Server [name=@Zsailer]
- Discussion topic: ask Jupyter frontends to adopt the ExtensionApp mechanism and depend on jupyter_server for the future.
- Poll: _We should encourage Jupyter frontends to adopt the ExtensionApp mechanism and depend on jupyterserver for the future.
  - Vote:
    - Endorse ++++++
    - Agree with reservation +++
    - Mixed feelings +
    - Disagree but won't block
    - Veto
  - Results and discussion.
[x] [Poll] The Future of jupyter/notebook. [name=@Zsailer]
- Discussion topic: what do we do with jupyter/notebook?
  - Proposed direction 1: next major release (7.x) of jupyter/notebook depends on jupyter_server (and ExtensionApp).
  - Proposed direction 2: fork frontend code in jupyter/notebook to new repo (i.e. jupyter/nbclassic).
- Poll: _Switch jupyter/notebook to depend on jupyterserver (and ExtensionApp) with a major release (7.x).
  - Vote:
    - Endorse +++++
    - Agree with reservation ++
    - Mixed feelings ++
    - Disagree but won't block +
    - Veto
  - Results and discussion.
[ ] Simple extension example jupyter_server#117
- Ready for review/merge.
[ ] Kernel Provider Mechanism
- Jupyter Kernel Management goal is to decouple kernel from server and rely on a discovery mecanism. The added values:
  1. without changing the notebook config, have multiple providers (each responsible for the kernel lifecycle (async (re)start, terminate…).
  2. Finding the correct provider with a KernelFinder.
- @takluyver has implemented jupyter_kernel_mgmt and jupyter_protocol repos.
- jupyter_client is no more used (would be deprecated, to be confirmed...).
- Various PRs last year(s) to integrate this in notebook and add async features (not merged, deprecated...).
- Current work is in jupyter_server by @kevin-bates:
- [WIP] Kernel providers jupyter_server#112
- Impact on downstream projects:
- `Classic Notebook:`` depends on previous point...
- JupyerLab: POC to evolve jlab server components to onboard jupyter_server to be discussed on jupyterlab#7310
  - Voila: needs to adapt the exisitng voila server direct interactions with Kernels.
- Questions:
- Any others projects interacting with Kernels (via jupyter_client...): nbconvert...?
- Migrate @takluvyer repos to Jupyter org?
- Minimum python version for async support: 3.5, 3.6, 3.7?

Zsailer commented 5 years ago

October 17th, 2019

Attendees

Name	affiliation	username
Zach Sailer	Jupyter Cal Poly	@Zsailer
Vidar T Fauske	J.P. Morgan Chase	@vidartf
Eric Charles	Datalayer	@echarles
Kevin Bates	IBM	@kevin-bates
Luciano Resende	IBM	@lresende

There were other attendees at the meeting, but they were not added to the list.

Agenda + Minutes

[x] Plan to transition jupyter/notebook to depend on jupyter_server.
- [x] Build a notebook (jupyter) server extension.
- [ ] Shim the notebook APIs
- [ ] Make the PR branch into a temporary package for side-by-side testing ("nbclassic"? "nbclassic-temp"?)?
- [ ] Release a major notebook (7.x?) release with shims + warnings
- [ ] Release a major notebook (8.x?), dropping notebook server APIs
- [ ] Switch JupyterLab to jupyter_server
[x] Jupyter Authorized Server
- https://github.com/Zsailer/jupyter_authorized_server
- Jupyter Server with authorization.
- User authorization is defined by policies.
[ ] Kernel Provider Mechanism
- Jupyter Kernel Management goal is to decouple kernel from server and rely on a discovery mecanism. The added values:
  1. without changing the notebook config, have multiple providers (each responsible for the kernel lifecycle (async (re)start, terminate…).
  2. Finding the correct provider with a KernelFinder.
- @takluyver has implemented jupyter_kernel_mgmt and jupyter_protocol repos.
- jupyter_client is no more used (would be deprecated, to be confirmed...).
- Various PRs last year(s) to integrate this in notebook and add async features (not merged, deprecated...).
- Current work is in jupyter_server by @kevin-bates:
- [WIP] Kernel providers jupyter_server#112
- Impact on downstream projects:
- `Classic Notebook:`` depends on previous point...
- JupyerLab: POC to evolve jlab server components to onboard jupyter_server to be discussed on jupyterlab#7310
  - Voila: needs to adapt the exisitng voila server direct interactions with Kernels.
- Questions:
- Any others projects interacting with Kernels (via jupyter_client...): nbconvert...?
- Migrate @takluvyer repos to Jupyter org?
- Minimum python version for async support: 3.5, 3.6, 3.7?
- Follow up with nb_conda_kernels
[x] Quick demo (5 minutes) of Classic Notebook and JupyterLab (Core) as Server Extension with Kernel Management based on:
- notebook#4653
- jupyter_server#112
- jupyter_kernel_mgmt/fixup-async
- jupyterlab/server-ext
- jupyterlab_server/server-ext
- PS:
  - Minor glitch for the kernel name display in classic notrebook (see this comment).
  - Goal is to have JupyterLab and Classic Notebook extensions deployed in the same Jupyter Server runtime.
[ ] JupyterLab
- [DISCUSS] Remove notebook dep from jupyterlab and jupyterlab_server jupyterlab#7310.
- [NEXT MEETING] Need also to discuss on the handlers currently in jupyterlab repo (which could be in jupyterlab-server - Other option is to merge jupyterlab-server into juptyerlab).

Zsailer commented 5 years ago

October 24th, 2019

Attendees

Name	affiliation	username
Zach Sailer	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles
Afshin Darian	Two Sigma	@afshin
Steve Silvester	AWS	@blink1073
Vidar Tonaas Fauske	J.P.Morgan Chase	@vidartf

Agenda + Minutes

[ ] [name=Zsailer] Notebook Shim
- https://github.com/Zsailer/notebook_shim
- Allows you to install notebook, jupyterlab, and a notebook server extension side-by-side.
- Config priorities:
  
  lab notebook
  
  user 1st 2nd
  
  default 3rd 4th (N/A)
[ ] [name=Zsailer] Roadmap (items are listed in order of priority).
- [ ] Rename notebook_shim to nbclassic.
  - [x] a notebook ExtensionApp (from jupyter_server).
  - [x] pulls Notebook JS and templates from notebook.
  - [ ] execute from command line with jupyter nbclassic
  - [ ] migrates configuration to jupyter_server_config.
- [ ] Update Jupyter Server JEP to reflect new nbclassic.
- [ ] Merge Kernel Providers
  - [ ] Move jupyter_kernel_mgmt, jupyter_protocol to Jupyter's Github org.
  - [ ] Documentation for Kernel Providers, jupyter_kernel_mgmt and jupyter_protocol.
  - [ ] Merge Kernel Providers into jupyter_server: jupyter/jupyter_server#112.
  - [ ] Help voila adjust to kernel_mgmt
    - @kevin-bates mentioned that he spoke with @SylvainCorlay about KP.
  - [ ] Release jupyter_server with Kernel Providers
  - [ ] Helpnb_conda_kernels switch to Kernel Providers.
    - They currently have an old version of Kernel Provider.
    - nb_conda_kernels tries to import Kernel Providers. If found, uses the new kernel management framework. Otherwise, falls back to old way.
- [ ] Transition JupyterLab to Jupyter Server, dropping notebook as a dependency.
  - Uses nbclassic to run notebook and lab side-by-side.
- [ ] Notebook 7.x: transition jupyter/notebook to Jupyter Server
  - [ ] drop the old notebook server
  - [ ] NotebookApp becomes
  - [ ] shim the notebook server API to jupyter_server
  - [ ] raise DeprecationWarnings in shimmed APIs.
  - [ ] release notebook 7.x
- [ ] Notebook 8.x: drop shims.
JupyterLab team meeting
- Dec 2nd-6th, Austin, TX.
- Push to JLab 2.0
- JLab 2.0 won't switch to Jupyter Server
- As soon as JLab 2.0 is out, Jlab 3.0dev should switch JS immediately
  - 6 months of testing JupyterLab on Jupyter Server.
- Zach is planning to work on Jupyter Server, Notebook 7.0, JupyterLab-to-JS that whole week.
[ ] Kernel Provider PR
- Question: How does this affect custom KernelManagers, e.g. nb_conda_kernels?
  - It won't crash anything :tada:
  - KernelManagers are not configurable anymore.
  - The new kernel managment mechanism with ignore custom KernelManagers.
  - Custom KernelManagers will need transition to the new Kernel Providers framework.

	lab	notebook
user	1st	2nd
default	3rd	4th (N/A)

Zsailer commented 5 years ago

October 31st, 2019

Attendees

Name	affiliation	username
Zach Sailer	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles

Agenda + Minutes

[ ] [name=Zsailer] Jupyter Home
- "Desktop" for many Jupyter Frontends.
- Discovers Jupyter frontends and shows them in one panel.
Bugs to fix.
- Check that default_url routes entrypoints correctly.
- Subcommand PR.
  - ExtensionApp doesn't currently handle subcommands.
  - Example where this is needed jupyter lab build.
- Proposed fix: https://github.com/jupyter/jupyter_server/pull/133
Switch test framework to pytest.
- Since the fork from jupyter/notebook, we've never really revisited the tests. We need to give them some attention.
- Current test framework (nose) is brittle.
- Pytest is more arguably readable
- Pytest fixtures + pytest-tornado alleviate some of the issues with runnning tests locally.
- Zach will spend this next week refactoring tests to pytest. Gives him a chance to make sure all tests make sense in jupyter_server.

Zsailer commented 5 years ago

November 7th, 2019

Attendees

Name	affiliation	username
Zach Sailer	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Luciano Resende	IBM	@lresende
Brian Granger	AWS	@ellisonbg
Eric Charles	Datalayer	@echarles

Agenda + Minutes

[name=Zsailer] Porting Server tests to PyTest
- Separate repo for now: https://github.com/Zsailer/jupyter_server_tests
- Zach will finish the porting of tests and merge this week.
[name=echarles] JupyterLab and JupyterLab Server
- ExtensionApp into Jupyterlab Server: https://github.com/jupyterlab/jupyterlab_server/pull/79 
- JupyterLab as a Jupyter Server Extension: https://github.com/jupyterlab/jupyterlab/pull/7416 
- Example: https://github.com/jupyter/jupyter_server/pull/117 
- nbclassic needs to manage configuration migration.
- JupyterLab will depend on nbclassic for the transition period.
[name=ellisonbg] FastAPI/Pydantic with tornado
- Might need to explore ASGI integration in Tornado.
[name=echarles] jupyter kernel mgmt with jupyter server doc https://github.com/takluyver/jupyter_kernel_mgmt/pull/28 (look the images)
- Both Kernel Management and Kernel Protocol have readthedocs pages up and running: https://jupyter-protocol.readthedocs.io and https://jupyter-kernel-mgmt.readthedocs.io
- Eric made diagrams showing the Kernel Provider architecture; we should get some review over there.
- Kernel Management and its relationship to remote terminals
  - There's work around using Kernel Gateway to launch remote terminals. It's currently working on KG.
  - Question: will the new kernel management prevent this from working in the future?
  - Terminals don't have "terminal" specs.
[name=Zsailer] Review the RoadMap

vidartf commented 5 years ago

The time for the meeting seems to be different in the calendar and the README. Which one is the right one? I was there at 8 PST with @blink1073. 😕

ellisonbg commented 5 years ago

Zach is traveling today so he canceled - I don't remember where he posted that, but he did send out something...sorry about the miscommunication

On Thu, Nov 14, 2019 at 8:29 AM Vidar Tonaas Fauske < notifications@github.com> wrote:

The time for the meeting seems to be different in the calendar https://jupyter.readthedocs.io/en/latest/community/content-community.html#monthly-meetings and the README https://github.com/jupyter/jupyter_server/blob/master/README.md#weekly-dev-meeting. Which one is the right one? I was there at 8 PST with @blink1073 https://github.com/blink1073. 😕

— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/jupyter/jupyter_server/issues/126?email_source=notifications&email_token=AAAGXUCC4ZU2G2S2UIIMN33QTV4HHA5CNFSM4JEGWEM2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEECN35Y#issuecomment-553967095, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAGXUEOXII2QI23WF7VCV3QTV4HHANCNFSM4JEGWEMQ .

-- Brian E. Granger

Principal Technical Program Manager, AWS AI Platform (brgrange@amazon.com) On Leave - Professor of Physics and Data Science, Cal Poly @ellisonbg on GitHub

kevin-bates commented 5 years ago

Yeah, sorry for the inconvenience: https://github.com/jupyter/jupyter_server/issues/111#issuecomment-553492796

vidartf commented 5 years ago

Sure, that's ok. There's still a discrepancy between the readme and calendar though :)

echarles commented 5 years ago

@vidartf The README points to Thursdays at 8:00am, Pacific as written in the initial comment. When I click on the link I receive the following which I think is correct (worked for me last week).

Screenshot from 2019-11-15 11-06-11

vidartf commented 5 years ago

@echarles Yes, and the jupyter calendar says 7 am pacific

echarles commented 5 years ago

oh I see... @Zsailer can you update the jupyter calendar to 8am pacific so west coast participants have their minimal required coffee :)

Zsailer commented 5 years ago

Fixed :) Sorry, y'all. The discrepancy came from a recent day light savings change here.

echarles commented 5 years ago

Thx Zach. Searched a bit on DST Google Calendar recurring event and not clear if Google supports automatically the changes. Otherwise, someone has to schedule in his calendar to update the calendar...

Zsailer commented 4 years ago

November 21st, 2019

Attendees

Name	affiliation	username
Zach Sailer	Jupyter	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles

Agenda + Meeting

[name=Kevin] Kernel Management on Windows trouble.
- Popen subprocess used in asyncronous kernels doesn't work on Windows
- Current fix:
  - Using a syncronous Popen call on Windows to side-step this problem
  - Using an asyncronous Popen call on non-Windows.
[name=Eric] Flags and Aliases on Extensions are failing #140
- https://github.com/jupyter/jupyter_server/issues/55
[name=Zach] Pytest Progress
- https://github.com/Zsailer/jupyter_server_tests
- conftest.py: https://github.com/Zsailer/jupyter_server_tests/blob/master/tests/conftest.py

Zsailer commented 4 years ago

December 5th, 2019

Attendees

Add your name to the table below:

Name	affiliation	username
Zach Sailer	Jupyter	@Zsailer
Kevin Bates	IBM	@kevin-bates
Luciano Resende	IBM	@lresende
Eric Charles	Datalayer	@echarles
JupyterLab dev-meeting attendees	*	*

Agenda + Minutes

[name=Zach] Server testing update - all tests converted to pytest, updating relative to 3.5 support - json encoding and pathlib issues being worked out, then ready for merge.
[name=Zach] Preparing for 0.2.0 release. Working on tests and docs with @echarles.
[name=Kevin] Kernel provider update - jupyter_kernel_mgmt release 0.5 was cut. Should try to add support for 3.5 (no known issues for that). Discovered that KernelApp had not been converted to the new framework.
[name=Steve] Briefly discussed how parameterized kernel launch would be helpful for creating/seeding environments.
[name=general] Briefly discussed content services acting on URIs and how it would be cool to convey the CS URI to kernels (local or remote) that can then gain access to content.

Zsailer commented 4 years ago

January 2nd, 2020

Attendees

Add your name to the table below:

Name	affiliation	username
Zach Sailer	Jupyter	@Zsailer
Eric Charles	Datalayer	@echarles
Kevin Bates	IBM	@kevin-bates

Agenda + Minutes

[ ] Jupyter Server 0.2.0 is released 🎉
[ ] NbClassic
- Config shim initial support is merged - This only address configs - We need to think about the extension json files: We should have a migration via a specific command to avoid users breaking their environment the first time they would start the server.
- [WIP] Fork notebook handlers instead, add tests from jupyter_server
- [DISCUSS] Pluggable user token creation/validation
[ ] Kernel Providers
- What do we need for Release jupyter_server 0.3.0 with kernel_mgmt 0.5.0 ?
- Status of Draft proposal for new kernel providers mechanism and associated changes ? Need vote quorum?
- Next Steps for Kernel Providers in Server?12 of 12 tasks complete
- @kevin-bates will rebase PR w/ master and remove [WIP] status
[ ] Example
- Simple Extension Example: @echarles will do a last pass before asking review.
[ ] JupyterLab
- Need to further work on JupyterLab as Server Extension and JupyterLab Server as Server Extension: @echarles to ensure unit tests pass...

Zsailer commented 4 years ago

January 9th, 2020

Attendees

Add your name to the table below:

Name	affiliation	username
Zach Sailer	Jupyter	@Zsailer
Eric Charles	Datalayer	@echarles
Kevin Bates	IBM	@kevin-bates

Agenda + Minutes

[x] JupyterLab to use Jupyter Server
- Unit tests to migrate.
- Status of jupyter_server pytest plugin?: Should we drop appveyor/travis and rely on github actions to avoid false negatives?
  - Zach is going to investigate the test failures further
  - Kevin brought up that conda envs might be the issue in appveyor.
[x] Authorization layer in Jupyter Server
- Short overview of design
- Demo from Zach
- Explore notion of "denial" from Microsoft.
- Discussion and review happening here.
[x] Styling/Formatting
- Zach [reverted styling]() until Kernel Providers are merged.
- We need to choose a styling tool... propose black?
- Add CI that lints formatting.
[ ] Overview of Branching
- Make sure we're on the same page with #163
- We'll have to backport bugfixes.
- Merge #163.
[ ] Review Jupyter Server 0.3.0 Roadmap
- Discuss tentative release date.
- Goals for 0.3.0
  - Kernel Providers.
  - Authorization (see below).
[ ] Proposal in nbclassic for Migration of notebook extension definitions to jupyter_server
- Feedback welcome before starting development.
[ ] Examples PR latest comment
- Current issues:
  - Configuration is not taken into account jupyter simple-ext1 --SimpleApp1.configA "ConfigA from command line" does not show up in the config.
  - ExtensionAppJinjaMixin does not call both _prepare_templates method with consequence that templates are not available in the settings - PR removes the Mixin, TBD maybe in a separated PR?
  - jupyter simple-ext11 --generate-config fails with "The ExtensionApp has not ServerApp ".
- Waiting a bit on @Zsailer feedback before opening separated issues for these.

Zsailer commented 4 years ago

January 16th, 2020

Attendees

Name	affiliation	username
Zach Sailer	Jupyter	@Zsailer
Eric Charles	Datalayer	@echarles
Kevin Bates	IBM	@kevin-bates

Agenda + Minutes

Zsailer commented 4 years ago

Hi everyone (specifically, @echarles and @kevin-bates)

I'm going to be unavailable for this week's meeting—I propose we cancel. Let's meet again next week, January 30th.

Thanks!

Zsailer commented 4 years ago

January 30th, 2020

Name	affiliation	username
Zach Sailer	Jupyter	@Zsailer
Kevin Bates	IBM	@kevin-bates
Luciano Resende	IBM	@lresende
Eric Charles	Datalayer	@echarles
Vidar T. Fauske	JPMorgan Chase	@vidartf

Agenda + Minutes

[name=Kevin] When to extend vs. subclass?
- E.g., a "hypothetical" Kernel Server doesn't want any of the content-related services exposed, how to disable via extension?
- Should we have "required services" (auth, api, config, security) and "optional services" (kernels, contents, edit, view, etc.) and remove assumption everything is present?
- Perhaps "extend" means just that - adding functionality. While "subclassing" transforms the existing functionality?
Outcome: Kevin will create an issue that enables discussion about how we might go about adding "optional" services, along with those that would be "required". However, the one requirement is that Jupyter Server include all of today's services by default since that's what users expect.
[name=Kevin] Discuss preventing merge commits?
- These don't appear to provide any meaninful value and make feature and change management difficult.
- Propose we only allow 'rebase merge' for single-commit PRs, and 'squash merge' for multi-commit PRs.
Outcome: There were good arguments for allowing merge commits, as well as rebase and squash. We decided to leave the merge mechanism to the discretion of the maintainer which will consider the "quality and context" of the commits.

Zsailer commented 4 years ago

February 6th, 2020

Name	affiliation	username
Zach Sailer	Jupyter	@Zsailer
Kevin Bates	IBM	@kevin-bates
Luciano Resende	IBM	@lresende
Afshin Darian	Two Sigma	@afshin

Agenda + Minutes

[name=Kevin] Service composition (continued)
- Implementations: Subclasses, Mixins, CLI Options
- Headless operations (KernelsAAS, ContentsAAS, etc)?
- Kevin's going to start a new branch trying out the Mixin approach.
[name=Kevin] Multi-user in Server?
- Jupyter Server should be a "user-quantity agnostic server"—this phrase sounds legit :laughing: @Zsailer.
- Propose to add a Session ID that services can use to identify the current "user".
  - session id is in every REST call.
  - @afshin:
    - Name a session cookie
    - First request gets/creates that session cookie.
    - All later requests expect that session cookie.
    - Give every service/handler the ability to read that named session cookie.
    - Pass through the auth headers in each request.
- Introduce "multitude-ness" (great word, created by @kevin-bates :sunglasses:) in Contents Managements?
  - Add the ability to start multiple different contents managers (each tied to specific session).
  - Later, add multiple contents "providers"—contents that are served from anywhere (local or remote).

Zsailer commented 4 years ago

February 13th, 2020

Attendees

Name	affiliation	username
Zach Sailer	Jupyter Cal Poly	@zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles
A. T. Darian	Two Sigma	@afshin
Luciano Resende	IBM	@lresende
Vidar T Fauske	J.P. Morgan Chase	@vidartf

Agenda + Minutes

[name=Eric] ExtensionHandler as Mixin
- https://github.com/jupyter/jupyter_server/pull/174
- Seems to be working for jupyterlab
[name=Zach] NBClassic needs attention.
- In my mind, nbclassic is a blocker for wide jupyter_server adoption.
- I'm planning to devote a week sprinting on this nbclassic (2/24-2/28).
- I will bring a "roadmap" for nbclass to next jupyter_server meeting.
Continued discussion on Multi-Contents Management / Providers
- Next step: identify who the stakeholders might be and start the discussion.
- Multiple stakeholders are definitely interested.
- There are multiple custom Contents Services in the wild:
  - nteract/bookstore—a custom "contents" API for notebooks stored in s3 buckets.
  - jupyter-drive: a custom mixed contents API for local contents and Google Drive contents.

Zsailer commented 4 years ago

Hi all, I apologize for the super late notice. I can't make it to today's meeting—I had to reschedule a student intern interview last minute during the Server meeting time. I propose we cancel today's meeting.

I will post my NBClassic "roadmap" (mentioned above) in a few hours. As I mentioned last week, my plan to sprint on NBClassic all next week. We can open discussion there if anyone is interested in participating in that sprint.

Thanks, all! Have a great weekend!

@kevin-bates, @echarles, @vidartf, @lresende, @afshin

Zsailer commented 4 years ago

February 27th, 2020

Attendees

Name	affiliation	username
Kevin Bates	IBM	@kevin-bates
A. T. Darian	Two Sigma	@afshin
Eric Charles	Datalayer	@echarles
Zach Sailer	Jupyter Cal Poly	@Zsailer
Max Klein	JP Morgan	@telamonian
Vidar T Fauske	JP Morgan	@vidartf

Agenda + Minutes

[name=eric]
- JupyterLab Server as Server Extension ready for review (depends on Make ExtensionHandler a Mixin )
- Should we remove Appveyor and Travis, see issues in this PR? Tracked in this PR.
- Will attempt a Dependency Injection approach based on injector (inspired by Google Guice, Java based).
- JupyterLab tags the repos with jupyterlab-extension. Which tag should we use? jupyter-server-extension, jupyterserver-extension...?
[name=Zach] NBClassic Progress
- Design for Traitlets Shim
- Current Logic in PR 7
- Current Question:
  - How do we handle traits with the same name in two extensions?
    - Previously, these trait values were inherited across multiple Traitlets objects
    - Steps to transitoin:
      1. Raise a warning for developers to make sure redundancy is on purpose. Add legacy-mode to "opt-in" to old behavior?
      2. Raise a warning for users that traits are no longer shared.
[name=Max]
- Multi contents manager :heart:
- Max is working on a Mult-contents manager and contributing it back to Jupyter Server
- Building off of https://github.com/timkpaine/multicontentsmanager

Zsailer commented 4 years ago

March 5th, 2020

Attendees

Name	affiliation	username
Zach Sailer	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Luciano Resende	IBM	@lresende
Eric Charles	Datalayer	@echarles
A. T. Darian	Two Sigma	@afshin
David Brochart	QuantStack	@davidbrochart

Agenda + Minutes

[name=Zach] Drop Travis and Appveyor
- Any objections?
- Issue: https://github.com/jupyter/jupyter_server/issues/181
- PR: https://github.com/jupyter/jupyter_server/pull/148
[name=Zach] Current status of nbclassic config shim
- Tests are finished
- Documentation needed.
- https://github.com/Zsailer/nbclassic/pull/7
- Shim class: https://github.com/Zsailer/nbclassic/blob/13e41f6a6fd17f8cc43d00b540e49e16cb956dd0/nbclassic/shim.py#L101
[name=Zach] Standardizing how we load server extensions
- https://github.com/jupyter/jupyter_server/issues/188
- Extension naming convention
- Important functions to know:
  - _jupyter_server_extension_path: point ntoebook
  - _load_jupyter_server_extension
[name=Luciano] Plans for nbclassic?
- When are we planning to migrate nbclassic changes to notebook repository?
- Zach and Luciano will discuss a possible proposal/plan to move nbclassic to a notebook 8.x "future" branch.

Zsailer commented 4 years ago

For those of you in the US, the meeting time is now an hour later (9am PST) due to daylight savings. We can talk about shifting the meeting time for future meetings if this proves to be inconvenient for too many people.

echarles commented 4 years ago

The README still mentions 8am PST. Should this be changed?

Zsailer commented 4 years ago

March 12th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles
David Brochart	QuantStack	@davidbrochart
Vidar T Fauske	JPMorgan Chase	@vidartf

Agenda + Minutes

[name=Zach]
- Discuss meeting time in light of Day light savings.
  - Revisit this in two weeks when Europe DST takes effect.
- Server extension loading mechanism.
  - https://github.com/jupyter/jupyter_server/pull/180
- Demo of the NBClassic config shim
  - https://github.com/Zsailer/nbclassic/pull/7
- Follow-up: What to do about notebook repo?
  - Write a document describing options (possibly an enhancement proposal)
- Next steps: documentation
  - Two types of docs: 1) developer docs and 2) user docs
[name=Zach and Eric] Current Status of JupyterLab Extension
- JupyterLab Server Tests are green!
- JupyterLab tests still need work to get them green.
- Zach is fixing examples.
Kernel Provider question
- Opening an issue to discuss how to proceed.
- https://github.com/jupyter/jupyter_server/issues/190

Zsailer commented 4 years ago

March 19th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Darian	Two Sigma	@afshin
Kevin	IBM	@kevin-bates
Luciano	IBM	@lresende
David	QuantStack	@davidbrochart
Eric	Datalayer	@echarles

Agenda + Minutes

[name=Zach] Notebook vs. NBclassic
- Zach is going to open an nbclassic branch in notebook
[name=kevin] Async kernel management (pre-providers)
- Thank you, David!
- Notebook Async kernel management PR 4479
  - We'd like to get this merged, then port to server.
  - Might require a release of Jupyter Client.
  - This should go in before jupyter_server 1.0 release.
[name=echarles] [DISCUSS] Release strategy in relation to Kernel Provider
- Cut a 1.0 release next Thursday.
- Documentation is needed before then.
  - Separate docs into roles.
  - Users and developers.
- Maybe create Github actions that auto-release moving forward.
- Final conclusion:
  - release 1.0
  - have a 1.x branch for bug fixes
  - master is the start of 2.x
  - merge Kernel Provides, Auth, etc.
    - Timeline? Still undecided.

Zsailer commented 4 years ago

March 26th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin	IBM	@kevin-bates
Vidar	JPMorgan Chase	@vidartf
David	QuantStack	@davidbrochart
Eric	Datalayer	@echarles

Agenda + Minutes

[name=Zach] Jupyter Server Documentation
- https://github.com/jupyter/jupyter_server/pull/196
- Broke the documentation into 4 roles/personas
- Switched to pydata_sphinx_theme
- Demo
[name=Zach] nbclassic branch on jupyter/notebook
- A nontrivial amount of work.
- nbclassic is a notebook fork. I'll need to revert some commits that previously removed javascript.
- Next step is to write up a post about this.

[name=Zach] Jupyter Server Gitter Chat

Seems like a good idea to me.

I tried creating a chat room, but gitter get this error:

You cannot create a room with a same name that as an already existing repo. You may need to grant public/private repo scope on the GitHub org in order for us to see and auto-associate it (the repo should appear in the room name typeahead).

Anyone else seen this?
Gitter has "write" access to Jupyter Org.

[name=Zach] Releasing 1.0 Checklist
- [ ] Merge new Jupyter Server documentation.
- [ ] Enable jupyter_client's AsyncKernelManager.
- [ ] Merge new mechanism for loading extensions.
- [ ] Release nbclassic 1.0

Zsailer commented 4 years ago

April 2nd, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Eric	Datalayer	@echarles
Kevin Bates	IBM	@kevin-bates
David	QuantStack	@davidbrochart

Agenda + Minutes

[name=Zach] Simplifying Server and Extension interaction
- https://github.com/jupyter/jupyter_server/pull/180
- Fixing tests and examples, then ready to merge.
Support for async Kernel Management in Notebook and Server
- Ready to merge jupyter/notebook#4479
- Nearly ready to merge jupyter/jupyter_server#191

Zsailer commented 4 years ago

Reminder that we moved this week's meeting up by 1 hour (8am Pacific).

Zsailer commented 4 years ago

April 9th, 2020

We had a shorter meeting this week.

Attendees

Name	affiliation	username
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles
A. T. Darian	Two Sigma	@afshin
Zach Sailer	Jupyter Cal Poly	@Zsailer

Agenda + Minutes

Zoom channel change. [name=Zach]
- Jupyter Cal Poly Channel is going away.
- Replacing with NumFOCUS channel
  - https://zoom.us/my/jovyan

Zsailer commented 4 years ago

April 16th, 2020

Attendees

Name	affiliation	username
Kevin Bates	IBM	@kevin-bates
Zach Sailer	Jupyter Cal Poly	@Zsailer
A. T. Darian	Two Sigma	@afshin

Agenda + Minutes

[name=Zach]
- PR jupyter-server/jupyter_server#180 is ready for review/merge.
- Documentation (#196) is nearly finished.
  - Let's merge (without much review) and iterate.
  - Adds the new structure for the docs.
  - We can correct and update regularly.
- 1.0 Release (see milestone board)
- Collaboration in Jupyter initiative.
  - Jupyter Server is a central piece of this initiative
  - Anyone interested in joining this group, add yourself to the HackMd.
  - https://hackmd.io/3wvMwR-1SYesRYsrJFwpMw

Zsailer commented 4 years ago

April 23rd, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Vidar	JP Morgan Chase	@vidartf
Darian	Two Sigma	@afshin
Jason	Bloomberg	@jasongrout

Agenda + Minutes

[name=Zach]
- New Jupyter Server docs went live this week. Check it out: https://jupyter-server.readthedocs.io/en/latest/
- v0.3.0 release out!
- Releasing plan discussion
  - Jason Grout asked if we're willing to release a few more 0.x branch to handle unforeseen transition painpoints/bugs.
  - Proposed plan:
    - Wait to release 1.0 this summer, in sync with JupyterLab 3.0.
    - JupyterLab should switch to Jupyter Server as soon as possible (use @echarles' branches).
    - We'll release minor versions as needed until the summer
    - Opt-in features, like Authorization, can land before 1.0 release.
    - Kernel Providers PR (#) is stalled until after 1.0 release, unfortunately.
    - Jupyter Lab will likely pin to Jupyter Server 1.0 for 1 year—two release cycles, i.e. JupyterLab 5.0
    - Jupyter Lab will use nbclassic to shim traits and provide the Classic Notebook next to JupyterLab.
- NBClassic and Notebook discussion
  - Conversation sparked by: https://github.com/jupyter/notebook/issues/5360
  - Darian is planning to write a JEP to "sunset" the Notebook.
  - Pending acceptance of this proposal, the notebook would go into a maintenance mode, LTS Period.
  - Need to decide how long LTS will be promised—is it 2 years, 5 years,... ?
  - In the meantime, Jupyter will promise to maintain Notebook (not accepting new features).
  - At the end of those 2 years, the Jupyter Team will no longer promise to maintain the Notebook.
  - Open question: do we switch Jupyter Notebook to run on Jupyter Server 1.0?
    - If yes:
      - Pros:
        
        One less backend branch we need to maintain.
        
        Jupyter Notebook and JupyterLab share the same server.
        
        Jupyter Notebook benefits from new features in Jupyter Server 1.0 (like Auth, telemetry, etc.)
      - Cons:
        
        Jupyter Notebook will likely pin to Jupyter Server 1.0. When JupyterLab switches to Jupyter Server 2.0, users will no longer be able to install both Jupyter Notebook and JupyterLab in the same environment due to conflicting Jupyter server dependency.
        
        Slightly disruptive to users; lots of shim + deprecation warnings.
    - If no:
      - Pros:
        
        Jupyter Notebook and JupyterLab will always be installable in the same environment because their server dependencies won't collide.
        
        No disruption for users. Jupyter Notebook works as usual until EOL.
      - Cons:
        
        We need to maintain an extra branch of the Jupyter backend services.
        
        Need a temporary, intermediate package—nbclassic—to allow other frontends to server Jupyter Notebook side-by-side

Zsailer commented 4 years ago

April 30th, 2020

Attendees

Name	affiliation	username
Kevin	IBM	@kevin-bates
Zach	Jupyter Cal Poly	@Zsailer
Eric	Datalayer	@echarles
Vidar	JP Morgan Chase	@vidartf

Agenda + Minutes

[name=Zach]
- Released NBClassic.
- Follow up on last week's conversation about Jupyter Server releases.
- Link to Zoom broken in README
[name=Kevin]
- Use AsyncMappingKernelManager as default MKM
[name=Eric]
- jupyterlab: linux+win32(py >= 3.5)
- jupyter_server: linux(py >= 3.5) win32(py >= 3.7)
- nbclassic: linux+win32(py >= 3.6)
- quid of win32 py3.8 for async kernel manager?

Zsailer commented 4 years ago

May 7th, 2020

Attendees

Name	affiliation	username
Kevin Bates	IBM	@kevin-bates
Vidar T Fauske	JP Morgan Chase	@vidartf
Zach Sailer	Jupyter Cal Poly	@Zsailer
A. T. Darian	Two Sigma	@afshin
Eric Charles	Datalayer	@echarles
Wei Ouyang	KTH Royal Institute of Technology	@oeway

Agenda + Minutes

[name=Zach]
- PR jupyter-server/jupyter_server#221: Fixed broken terminal test.
  - Virtual Notebook Hackathon next Friday.
- ExtensionApp name vs. extension_name Discussion.
  - Changes /static/{name} for current extensions.
  - There is some logic in jupyterlab to track sys-prefix/user
- Extensions configure ServerApp
  - Relevant issue: https://github.com/jupyter/jupyter_server/issues/207
    - Add a "required" field to extensions.
  - Applications in Jupyter-FS: https://github.com/jpmorganchase/jupyter-fs/issues/28
[name=Wei]
- ImJoy Demo https://imjoy.io/
- A demo gif https://twitter.com/weioyang/status/1257722468262871042

Zsailer commented 4 years ago

May 14th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles
A. T. Darian	Two Sigma	@afshin

Agenda + Minutes

[name=Zach]
- Notebook Hackathon Friday (tomorrow), May 15th, 9:30AM PST
  - Kevin put together a nice release plan
  - https://github.com/jupyter/notebook/issues/5423?
- Make load_other_extensions property in ExtensionApp configurable?
  - https://github.com/jupyter/jupyter_server
  - No immmediate objections.
  - Draft a PR and give it 24 hours. /issues/227
[name=Eric]
- How to move forward with the extension_name?
  - https://github.com/jupyter/jupyter_server/issues/224
  - https://github.com/jupyter/jupyter_server/issues/222
  - This brought up a deeper issue about how we discover extensions.
    - Currently, extensions are discovered by looking at the config.d, importing enabled extension packages, and looking for the _jupyter_server_extension_paths function.
    - Steve proposed that we switch to use entry-point mechanism in setup.py
      - The config.d still exists for enabling.
      - Zach will draft a PR to explore this approach

Zsailer commented 4 years ago

May 21st, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
A. T. Darian	Two Sigma	@afshin
Steven Silvester	AWS	@blink1073

Agenda + Minutes

Extensions: load different config from extension entrypoint vs. jupyter_server
- Brought up in Issue [#229(https://github.com/jupyter/jupyter_server/issues/229)
- Voila needs to prevent arbitrary code execution when launched from its entrypoint.
- Zach is drafting a PR to handle this issue.
  - Following ideas from this comment.
Extensions: discover from setuptools entrypoints or config.d
- Switching extension_name --> name in ExtensionApp doesn't cause any extra issues.
- Steve proposed switching to Python's native plugin system
  - Zach will draft a PR soon
JS Jupyter Enhancement Proposal
- Zach will update the Jupyter Server JEP
- remove the sys-prefix question section (see next item)
Sys-prefix question as a separate JEP
- Steve maybe collaborate with Sylvain?
Telemetry Draft opened on jupyter_server
- https://github.com/jupyter/jupyter_server/pull/233
- Replaces #231
Leaking file descriptor: https://github.com/jupyter/jupyter_server/issues/234
- No clear solution to this issue, but we'll look into this over the week.

Zsailer commented 4 years ago

May 28th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles
A. T. Darian	Two Sigma	@afshin
Steven Silvester	AWS	@blink1073

Agenda + Minutes

[name=Zach] I didn't have much time to work on Jupyter Server stuff this week.
- https://github.com/jupyter/jupyter-packaging/pull/35 makes it more tractable to use data_files for Jupyter and Jupyter-related packages
- To-do list:
  - [ ] Extensions: load different config from extension entrypoint vs. jupyter_server
    - Draft a PR from ideas in this comment.
  - [ ] Extensions: discover from setuptools entrypoints or config.d
    - ~~Draft a PR using Python's native plugin system.~~
    - Look at Jupyter Packaging for handling entrypoints.
  - [x] Merge extension_name --> name PR
  - [ ] Update Jupyter Server Jupyter Enhancement Proposal
[name=Steve] Jupyter Paths preferred/default ordering
- Another level of config for python environment?
  - We want there to be a clear hierarchy of defaults and overrides.
  - Use other standard utilities like npm as a guide
- Use JupyterLab application logic for "default" install targets for command line utilities
- Open an issue on jupyter_core and link to it from discourse
- Eventually migrate to a JEP
Leaking file descriptor update.
- Discussion happening in jupyter_client
- https://github.com/jupyter/jupyter_client/pull/548
[name=Eric] Master "half-broken" => HotFix (value from Bool trait?) or Rollback or wait extensions server traits whitelist
- See https://github.com/jupyter/jupyter_server/pull/217
- Eric will open a PR to make the field a static value (not a trait)
[name=Kevin] Thoughts on "partitioning" kernel management - I may be making false assumptions on intent
- See https://github.com/jupyter/jupyter_server/issues/235

Zsailer commented 4 years ago

June 4th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin	IBM	@kevin-bates
Eric	Datalayer	@echarles
Darian	Two Sigma	@afshin

Agenda + Minutes

[name=Zach]
- I'm going to be less available for the next two weeks.
- My goals during that time:
  - Merge Telemetry plumbing PR: https://github.com/jupyter/jupyter_server/pull/233
  - Draft PR to support all old ways of loading server extensions
[name=Eric]
- Add some test for the examples and run them in the GitHub Actions
- https://github.com/jupyter/jupyter_server/pull/232 (examples failing with jupyter-server/examples/simple/simple_ext1/application.py", line 48, in initialize_handlers (r'/{}/default'.format(self.extension_name), DefaultHandler),)

Zsailer commented 4 years ago

June 11th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Darian	Two Sigma	@afshin
Eric	Datalayer	@echarles
Vidar	JP Morgan Chase	@vidartf

Agenda + Minutes

Issue: Extension name and module name have to match
- This is a problem for JupyterLab, where name is lab and module name is jupyterlab
- We need a way to support this distinction.
- This should be solved by the extension metadata object.
Extension discovering, configing, and loading API.
- Zach—I'm working on a new module that provides utils finding extensions in multiple locations.

Zsailer commented 4 years ago

June 18th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles

Agenda + Minutes

[name=Zach]
- I've been working on a new ExtensionManager API.
- https://github.com/Zsailer/jupyter_server/blob/extension-loading/jupyter_server/extension/utils.py
[name=Eric]
- 2 needs for JupyterLab:
  - E xtension name should be lab => solved by https://github.com/Zsailer/jupyter_server/blob/extension-loading/jupyter_server/extension/utils.py ?
  - Jlab is asking for backward comptability of existing server extensions - https://github.com/jupyter/jupyter_server/issues/243
- Merge https://github.com/jupyter/jupyter_server/pull/242 (Add some test for the examples and run them in the GitHub Actions )?

Zsailer commented 4 years ago

June 25th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Steve Silvester	AWS	@blink1073
A. T. Darian	Two Sigma	@afshin
Eric Charles	Datalayer	@echarles

Agenda + Minutes

[name=Zach] New ExtensionManager API
- https://github.com/jupyter/jupyter_server/pull/248
- Once merged, let's make a release.
[name=Steve] Desk treadmill recommendation
Test Traitlets 5.0 against jupyter_server.
Potentially make jupyter_client depend on protocol and have jupyter_client be a kernel provider
Notebook Meeting
- Discourse over mailing list--> https://github.com/jupyter/enhancement-proposals/issues/59
- Security
  - https://github.com/jupyter/jupyter.github.io/blob/master/.well-known/security.txt
  - Steve is going to research security
  - Zach will write up the docs and issue template

Zsailer commented 4 years ago

July 2nd, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
A. T. Darian	Two Sigma	@afshin
Eric Charles	Datalayer	@echarles

Agenda + Minutes

[name=Zach] Classic server extensions and Jupyter Server
- Classic Jupyter Notebook Server extensions are not discovered by Jupyter Server (yet).
  - Specifically, Jupyter Server doesn't look at the jupyter_notebook_config.d directory (only the jupyter_server_config.d) for enabled extensions.
- Ideally, Nbclassic will handle this discovery.
  - Nbclassic can leverage the new approach ExtensionManager to configure the server—adding nbserver_extensions to jpserver_extensions—before the extensions are loaded.
  - This requires nbclassic to be installed to discover classic server extensions
- jupyter serverextension (from jupyter/notebook) versus jupyter server extension (from jupyter/jupyter_server)
  - This is confusing.
  - We may need to rename this subcommand in Jupyter Notebook.
    - Still an open question. Zach will open an issue on Github.

Zsailer commented 4 years ago

July 9th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles
Steven Silvester	AWS	@blink1073

Agenda + Minutes

[name=Zach]
- Progress in NBClassic—Notebook Server extensions in Jupyter Server
  - https://github.com/Zsailer/nbclassic/pull/12
- Extensions to try:
[name=Steven Silvester]
- Internationalization - in the server?
  - This exists in the classic notebook server, but was removed since we didn't offer a frontend.
  - It might make sense to include again in the future.
  - Testing in JupyterLab Server right now.
- Timeline for merging into JLab? API freeze is 31 July
  - Shooting to release Jupyter Server 1.0 and NBClassic 1.0
- Thoughts on JLab extensions behaving similar to server extensions
  - Zach: :+1:
Jupyter Archive: https://github.com/jupyter/jupyter_server/issues/252
- This is a gap in the Contents service. We serve files but not directories.
  - This is not really a new addition to the REST API, it's finishing a missing piece.
  - Zach: (Echoing other's opinions) I am in favor of reviewing+accepting this addition the Server. This not setting a precedence for any endpoint to be added. This is merely filling a gap.
- Discussion about what's a minimal Jupyter Server—keeps coming up.
- See discussion about proposal for composable Jupyter Servers.
  - Issue jupyter-server/jupyter_server#178
- A separate idea is to make the default services configurable.
  - We would need to the OpenAPI spec to build dynamically on server initialization.
  - Only the pieces of the OpenAPI spec that are used will be displayed.
  - Open question from Zach: is it unusual for a server-side library to allow users/operators to configure which default services are turned on?
Notebook discussion
- Issue template for notebook repo:
  - Need a place to send users who need help with installation issues
  - Should we advertise the discourse channel more (use JupyterCon)?

meeseeksmachine commented 4 years ago

This issue has been mentioned on Jupyter Community Forum. There might be relevant details there:

https://discourse.jupyter.org/t/jupyter-community-calendar/2485/12

Zsailer commented 4 years ago

July 16th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Steven Silvester	AWS	@blink1073

Agenda + Minutes

*

[name=Steve]
- Schedule for JuptyerLab 3.0
- Integrating with JupyterHub
  - https://github.com/jupyterhub/jupyterhub/issues/2984
  - https://github.com/jupyterhub/jupyterhub/pull/2601
[name=Zach]
- Priority setting (dates are subject to change)
  - Nbserver extensions (17th July)
    - Verified Steve as nbclassic maintainer (PyPI and Github)
  - Plan for JupyterHub integration (24th July)
  - JupyterLab integration (31st July)
  - Implement Jupyterhub integration (30th September)
- Scheduling for pair programming
  - Zach and Steve, 12:30pm July 16th
  - calpoly.zoom.us/my/zsailer
[name=Kevin]
- Administrative endpoints: https://github.com/jupyter/enterprise_gateway/issues/299#issuecomment-658889604
  - Goal: collect metrics on kernels in Jupyter Server
  - Zach: Can we merge this with the telemetry efforts?
  - There is a distinction between addings a new endpoint to Jupyter Server and adding features to Jupyter Server that affect the existing services.

Zsailer commented 4 years ago

July 23th, 2020

Attendees

Name	affiliation	username
Zach	Jupyter Cal Poly	@Zsailer
Kevin Bates	IBM	@kevin-bates
Eric Charles	Datalayer	@echarles
A. T. Darian	Two Sigma	@afshin
Steve Silvester	AWS	@blink1073
Vidar Fauske	JP Morgan Chase	@vidartf

Agenda + Minutes

[name=Zach]
- NBClassic now shims Notebook frontend extensions.
  - https://github.com/Zsailer/nbclassic/pull/12
- Roadmap from last week's meeting
  - Nbserver extensions (17th July)
  - Plan for JupyterHub integration (24th July)
  - JupyterLab integration (31st July)
  - Implement Jupyterhub integration (30th September)
- I will dive into the JupyterHub integration this week to evaluate the transition to Jupyter Server
- I will draft a report describing the "health" of JupyterLab, JupyterHub, and NBClassic on Jupyter Server.
[name=Eric]
- Kernel state is better maintained on Server, e.g.
  - https://github.com/jupyterlab/jupyterlab/issues/8632
  - https://github.com/jupyterlab/jupyterlab/pull/8562#issuecomment-646958719

jupyter-server / team-compass