Team Compass for JupyterHub and Binder

This page contains links to the notes from team meetings with the JupyterHub community. For more some more technical information and links to various JupyterHub repositories, see the Team Compass README.

Site contents

• The JupyterHub Community
  • JupyterHub Team
  • Binder Team
  • Emoji keys
• Contributing to the JupyterHub Community
  • Do I really have something to contribute to JupyterHub?
  • Get connected
  • Contributing through GitHub
  • Find issues to work on
  • Help contributing to a specific repository
  • Thank you!
• Team meetings and meetings reports
  • Monthly Reports Archive
  • Weekly Reports Archive
  • Updating the team meeting agenda
• Milestones and roadmaps
  • jupyterhub
  • BinderHub
  • Zero to JupyterHub for Kubernetes
  • The Littlest JupyterHub
  • repo2docker
• Binder Project Governance
  • Project mission
  • Membership
  • Team privileges
  • Team responsibilities
  • Team roles
  • How decisions are made
  • Team size
  • Modus operandi
• Subdomains on mybinder.org
• JupyterHub Team Tools
  • Add a button to the built documentation in a Pull Request

Why have a Team Compass?

This repository helps the JupyterHub team and Binder team set a weekly course for project activity. Our overriding goal is continuous team and project improvement.

As projects and their growth evolve rapidly, the contents of this repo should aid us in setting project direction and adjusting the course as needed. The repo contains:

• team meeting agendas and archives
• direction and action plans
• communication and culture of respectful teamwork
• recognitions and team celebrations

We sail together

While we value each others individual strengths and contributions, we succeed or fail as a team. Whether taking corrective actions for a bug or being recognized for good work, the team, instead of an individual, shoulders the burden and success.

Code of Conduct

The JupyterHub community follows the broader Jupyter Community’s Code of Conduct.