Shared accounts and infrastructure#

There are a few services and infrastructure that the JupyterHub team has access to. Some of these are useful for our development workflows, while others are used as a part of services that we run.

GitHub#

We have a GitHub organization for hosting all of our code repositories. This organization is where we do most of the code-related work for the project, and where we have discussions and coordination.

PyPI#

We have a bot account named jupyterhub-bot on PyPI. This has historically been used to generate a token for use to publish new releases via our CI system. We are however transitioning away from this practice.

The current practice is to declare that PyPI project’s should allow a specific GitHub workflow (release.yaml) in the associated GitHub repository to be allowed to publish new releases. See our template GitHub workflow for more details.

There is a list of current team members with control of the account, ask if you need access or a change made related to the account.

Google Drive#

We have a JupyterHub Team Google Drive to store documents, presentations, images, etc that are useful to the team. You can put whatever you’d like here, just try to keep it organized :-)

Image registry on quay.io#

We have a quay.io organization for hosting Docker images. This is used for the repo2docker base image. If you do not have access to this organization and require it, ask a team member to add you.

Image registry on DockerHub#

We have a DockerHub organization for hosting Docker images. BinderHub and JupyterHub images are pushed to DockerHub as that still works, though we are considering publishing these images to use quay.io as well. If you do not have access to this organization and require it, ask a team member to add you.

Documentation and ReadTheDocs#

In general the JupyterHub team encourages the use of ReadTheDocs. This is a service that hosts documentation stored in online repositories.

For example, you can find the JupyterHub documentation at jupyterhub.readthedocs.io. And the JupyterHub ReadTheDocs dashboard is at readthedocs.org/projects/jupyterhub/.

To get access to a documentation page for a JupyterHub repository, you’ll need to be added by someone with the right privileges. New users may be added by an admin via the Admin -> Maintainers menu.

In addition, ReadTheDocs offers Pull Request previews for changes to documentation, which may be enabled via the instructions on this page.

Figma page for designing images and logos#

We have a JupyterHub Figma Project that can be used to quickly generate logos and images for use in our tools and documentation. This is available to anybody with the link to edit, and you can ask in the team compass if you’d like to be added as an administrator.

It contains a variety of design assets from many projects, here’s a preview below.

npm organization#

We have an npm organization at npmjs.com/org/jupyterhub. This can be used to publish packages relevant to JupyterHub on NPM.

If you’d like access or need to access a package, ask a Steering Council member.

mybinder.org infrastructure#

See mybinder.org infrastructure for more details.