This meta-repository is meant to help us organize ourselves across the many organizations, projects, and use-cases in the JupyterHub community. It's meant to make the project more welcoming, transparent, and inclusive. If you've got an idea for how this can be improved, please reach out!
Most of the Team Compass lives in this website:
Please familiarise yourself with the Code of Conduct.
Documentation status and codecov for several repositories
The JupyterHub community tries to keep its documentation strong and its code coverage for tests relatively high. A great way to contribute is to help improve either of these things. Below is a table of relevant information and links for each of these.
Name | Documentation | Code Coverage | Changelogs |
---|---|---|---|
JupyterHub | changelog | ||
KubeSpawner | changelog | ||
Z2JH | changelog | ||
TLJH | |||
BinderHub | changelog | ||
repo2docker | changelog | ||
binder docs | |||
team compass | |||
mybinder.org SRE |
Currently, the JupyterHub team is keeping track of the goings-on in the community via the following main channels:
- A monthly team meeting on the third Thursday of every month
- Issues / PRs in the JupyterHub repositories
- The JupyterHub / Binder Gitter channels
Note: any member of the community is welcome to participate in any of the process around discussion, archiving, and planning team meetings. Participate in whatever way works for you! Input is welcome!
The JupyterHub Team meetings occur on the 3rd Thursday of every month, alternating at UTC 07:00 (your timezone) and UTC 17:00 (your timezone). These are open to the community and we'd love for you to join!
Here are some useful links:
- Videoconference link provides access to the meeting.
- The monthly meeting archive has the contents / summary of each meeting.
- The monthly meeting agenda will be filled in during the meeting.
- The meeting agenda template is used to structure the conversation each month.
The list of "core" members of the JupyterHub and Binder projects can be found on the team-compass website.
🚨 The weekly team reports have been deprecated in favour of the monthly team meeting 🚨
The currently-active team report exists in a HackMD. Each week, team reports are archived in the weekly reports archive. Then, a new report is created with the team report template.