JupyterHub and BinderHub Team Meeting

  • Date: Thursday 16th September 2021

  • Time: 5pm UTC

    • Your timezone: https://arewemeetingyet.com/UTC/2021-09-16/17:00/Hubs-Team-Meeting

  • GitHub issue: https://github.com/jupyterhub/team-compass/issues/442

  • Calendar for future meetings: https://jupyterhub-team-compass.readthedocs.io/en/latest/meetings.html

By participating in this meeting, you are agreeing to abide by and uphold the Code of Conduct. Please take a second to read through it! :pray:

Welcome to the Team Meeting

Hello!

If you are joining the team video meeting, sign in below so we know who was here. Roll call:

  • tim / Binder / @betatim

  • Min / Simula / @minrk

  • Sarah / 2i2c / @sgibson91

  • Simon / University of Dundee / @manics

  • Erik / Sundell Open Source / @consideRatio

  • Rollin / NERSC / @rcthomas

  • Isabela / Quansight Labs / @isabela-pf

  • Mridul / GESIS / @Mriduls

Quick updates

60 second updates on things you have been up to, questions you have, or developments you think people should know about. Please add yourself, and if you do not have an update to share, you can pass.

Reports and celebrations

This is a place to make announcements (without a need for discussion). This is also a great place to give shout-outs to contributors! We’ll read through these at the beginning of the meeting.

  • Isabela is here to give a heads-up that there will be a Jupyter accessibility workshop in the next month. Date and time to be announced soon.

Agenda items

Let’s collect all potential agenda items here before the start of the meeting. We will then attempt to create a coherent agenda that fits in the 60m meeting slot. If there are similar items try and group them together.

  • Simon (10m): Running BinderHub without Kubernetes

    • https://github.com/jupyterhub/binderhub/issues/1318

    • https://github.com/jupyterhub/binderhub/pull/1364

    • Katacoda example https://katacoda.com/manics/scenarios/binderhub-in-a-box

      • Collaborating with Yuvi for this work. Simon gives a demo showing how it runs and how to set it up.

      • This creates a single-server JupyterHub with minimal requirements in about five minutes.

      • Motivation: this could make it easier to test PRs

      • Question: where is repo2docker being run? It doesn’t really need to be run in a container, it’s run directly on the VM.

      • would be interesting to make a conda-forge package to make installing BinderHub easier (no compiler stuff needed)

      • Question: is this related to discussions about wanting to be able to build JupyterHub from images on the fly? That wasn’t the motivation, but it may make it more possible.

      • If we brought Binder as a a service to JupyterHub, what is the UI/UX a user would want?

        • figuring out this would be super useful, Tim thinks lots of people have lots of different ideas about this.

      • Question: where does the image end up? Locally on your docker.

      • Does this need support or review? It has already been reviewed, so it’s just implementing feedback.

  • Tim (10m): JupyterLab as default UI

    • old man Tim isn’t bothered by the switch but not so happy with how it turned out

    • is there a plan to update the documentation and examples?

    • should we show a link to a “how to update your repo” tutorial on the 404 page? Lots of people who do not pay attention to mybinder.org development will see a 404 now and (I guess) are kind of stranded.

    • A process question: why did the initial switch to lab not involve work to update the docs?

    • What is the strategy for dealing with the “dead” links that now exist around the internet?

      • some cases I’ve seen:

        • repo uses custom Dockerfile without lab -> now shows 404s

          • could argue that “custom Dockerfile means you are on your own”

        • teaching repo that links directly to notebooks with custom extensions -> now get “retro lab” but the extensions are gone/not there/UI looks different

        • Simon: filepath= with old version of JupyterLab which doesn’t support /doc

    • Question: Have these consequences been discussed somewhere? Have the people involved intentionally not made these changes? Min says it may have gotten overlooked because this documentation is not in the same repo as the PR that made this change.

    • Chris: in the future this might be better served as a Jupyter Enhancement Proposal to notify the wider community because this work probably has influenced even more than we are currently aware of.

    • docs PRs:

  • Simon (10m): General plan for using DockerHub vs quay.io

    • We moved repo2docker to quay.io due to limited number of API tokens in the jupyter (not jupyterhub) Docker Hub

    • What should we do in general?

    • https://github.com/jupyterhub/repo2docker/issues/1076#issuecomment-920642480

      • Current inclination: don’t break the existing docker-focused repos, but update the dev builds. Encourage switching but don’t force to move it at the moment.

      • Min: this does seem to be the popular process amongst projects right now.

      • Chris: notes lacking documentation of process related to credentials on docker hub / quay / etc.

      • Tim: what do we need to update in our docs once we use quay.io?

        • maybe look at the docs to find where we refer to Docker hub in the context of setting up a BinderHub

        • If we have docs recommending docker credentials to pull the images from docker hub to avoid rate limiting, that needs to be updated ([name=Min] I’m not sure we have this, but mybinder-sre or z2jh)

        • Erik: diataxis.fr for doc structure

  • Min (5m): JupyterHub 2.0 beta. Ready to publish after

  • General discussion: explore A/B demo of new features; bring back ‘beta.mybinder.org’? (open issue on mybinder)