Team Guides

Guides for JupyterHub teams

• JupyterHub and Binder team guide
  • What are the team resources?
    • General policy about communication channels
  • How can I help?
    • Are there any specific responsibilies?
  • When should I merge a pull request?
  • Periodic team check-ins
    • If a team member doesn’t respond to a check-in
• Skills and ways to contribute
  • Where to start?
  • A few general ways to help out
  • Things to know about JupyterHub
    • JupyterHub-specific knowledge
    • Server infrastructure
    • UI/UX
    • Deployment Infrastructure
    • Community infrastructure
  • A note on complexity of tasks
  • Links
  • Resources for Learning
• Repository Management and Code Standards
  • Preferred tools and pre-commit hooks
  • Applying to repos
  • Configuration of a tool
  • Proposing organization-wide use of a tool
• Adding and onboarding new team members
  • Adding a new team member
  • Onboarding a new team member
    • The onboarding checklist
    • An official onboarding message
• Shared accounts and infrastructure
  • GitHub
  • Image registry on quay.io
  • Image registry on DockerHub
  • Documentation and ReadTheDocs
  • mybinder.org infrastructure
    • Ownership of the mybinder.org domain
    • DNS entries for mybinder.org
    • Google Cloud Platform (GCP) Project
    • Other cloud deployments in the federation
• Resources for giving presentations and talks about the Projects
  • What to consider when speaking publicly about this community?
  • Resources for giving talks
  • Common questions and suggested answers

previous

JupyterHub HPC Meeting - November

next

JupyterHub and Binder team guide