There are lots of ways to contribute to the JupyterHub community.
Code, community interaction, documentation, bug testing, bug fixes, teaching,
proslytizing, etc…we recognize any and all contributions!
This page describes “self-described core” team members of the JupyterHub
community. These are people that spend a significant amount of their
time contributing to the projects and community under the JupyterHub umbrella.
Note that these teams are accompanied by a much larger group of contributors
to Binder, JupyterHub, and Project Jupyter as a whole.
If you’d like to be included in the teams below:
For JupyterHub, submit a pull request to add your name and information to
the JupyterHub team data
For Binder, check out the Membership section of the
Binder Project Governance document for information about how you can join the
Binder core team.
The JupyterHub team is roughly comprised of two different projects with heavily-
overlapping team membership. Both are part of Project Jupyter
and are developed by an open community of contributors.
The process and governance for both Binder and JupyterHub can be found in the
JupyterHub Project Governance and Binder Project Governance pages.
Here is the current JupyterHub team:
(listed alphabetically, with affiliation, and main areas of contribution)
Min Ragan-Kelley acts as the team lead for the JupyterHub organization.
The Alan Turing Institute
Wild Tree Tech
💼, code, fundingFinding, ideas, talk, infra
Open Microscopy Environment, University of Dundee
You may notice that some of the team-members have “emojis” to reflect their
contributions in JupyterHub. These are from the Kent Dodds “all contributors spec”.
Below is a short table to show what each emoji represents.
Answering Questions (in Issues, Stack Overflow, Gitter, Slack, etc.)
Ideas & Planning
Packaging/porting to support a new platform
Reviewed Pull Requests