Policies and standards

Governance and structure defines our decision-making policies, how we organize ourselves, and the practices that we commit to following.

Governance and structure

• Project Governance
  • JupyterHub Project mission
  • Binder Project mission
  • Membership
  • How decisions are made
  • Modus operandi
• Subdomains on mybinder.org
• Team structure and responsibilities
  • Expectations of all team members
  • Our teams
  • Offboarding team members
• Jupyter Code of Conduct

Team practices describe our operational policies and practices.

Team practices

• Team communication and user support
  • Types of discussions
  • How to get in touch with the JupyterHub Council
  • Chat
  • Support bot
• External communication
  • Expecations of team members
  • Blog posts
  • Talks and presentations
• Funding and reimbursements
  • Who can spend funds
  • Funds available to this project
  • How to get reimbursed from NumFocus
• Adding and onboarding new team members
  • What to consider when adding a team member
  • Process for adding team members
  • Onboarding a new team member
• Team check-ins
  • If a team member doesn’t respond to a check-in

Technical practices describe our standards and processes around technical infrastructure.

Technical practices

• Pull request workflow
  • Principles to follow
  • When to merge pull requests
  • What to look for when reviewing
• 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
• Making releases
  • Release ambitions
  • Release practices
    • Changelog updates with github-activity
      • Create PR list with github-activity
      • Create a changelog entry
    • Version updates with tbump
    • Publishing to PyPI
    • Publishing to conda-forge
• Readme Badges
  • About shields.io
  • Badges
    • Build
    • Package
    • Community