The 2i2c Team Compass

This Team Compass is a guide for team members of 2i2c to navigate our organization and community1. It is our team’s primary knowledge base.

The Team Compass is the Source of Truth!

If you see information that is out of date, propose an edit in the team compass repository. To propose an edit directly from the documentation, click -> .

Below we describe the major sections in the Team Compass.

Functional Areas

Information broken down by major functional areas of 2i2c.

Functional Areas

• Organization
  • Code of conduct
  • Mission, values, and stakeholders
  • Key Performance Indicators
  • Strategy and objectives
  • Organizational structure
  • Governance and decision making
  • Leadership workflow
• Team operations
  • Structure and responsibilities
  • Coordination strategy and goals
  • Where to look for information
  • Tips for distributed working
  • Onboard a team member
  • Communication channels
  • About the Team Compass
  • Team meetings
• People group
  • Expectations of team members
  • Compensation and Benefits
  • Hiring process and information
  • Job Titles
  • Taking time Off
  • References
• Engineering
  • Structure and responsibilities
  • Workflow
  • Accounts and cloud access
  • Secrets, credentials, and passwords
  • Merge and Code Review policy
  • GitHub repository conventions
  • Style guide for repositories
• Product
  • Structure and responsibilities
  • Workflow
• Community guidance
  • Structure and responsibilities
  • Workflow
• Partnerships and sustainability
  • Structure and responsibilities
  • Workflow
  • Communication channels
  • Leads and new partnerships process
• Communication and outreach
  • Communication strategy
  • Blog posts
  • Social media
  • Mailing list
  • Publishing and DOIs
  • Talks and conferences
• Finance and accounting
  • General information
  • Active grants and contracts
  • Budget projections
  • Accounting statements
  • Common questions and how to answer them
• Administration
  • Structure and responsibilities
  • CS&S Administration
  • Reimbursement and credit cards
  • Google workspace

Managed JupyterHubs Service

Currently 2i2c oversees a single major effort, which is building a sustainable service to make interactive computing with open source infrastructure more accessible and scalable. We act as a cross-functional team around this service, and share many responsibilities and duties. We document some major aspects of this service in the sections below.

Managed JupyterHub Service

• Overview
• Incident response
  • Roles and team structure
  • What counts as an incident?
  • Communication channels
  • Incident response process
  • Create an Incident Report
  • Handing off Incident Commander status
  • Key terms
• Sales and invoicing process
  • Location of sales assets and documents
  • Who participates in this process?
  • Tracking leads with AirTable
  • What we need in order to send an invoice
  • Steps in selling new services
  • Tips and FAQs
• Support process
  • Overview of the support process
  • Types of support requests
  • Roles and team structure
  • Communication channels
  • Process for support triage and resolution
  • Prioritizing non-incident support requests
• List of running hubs

Team Reference

Reference and archival information for our teams.

Reference Material

• Team Calendars
  • 2i2c Events
  • Team Roles Calendar
• List of team members
  • Team member locations and times
• Team meeting archive
  • 2022 Meeting Notes
  • 2021 Meeting Notes
  • 2020 Meeting Notes
• Important Terminology
• Inspiration for 2i2c’s practices
  • The Team Compass
  • Organizational influences
  • Documentation

---

1

For more about the Team Compass itself, see About the Team Compass.