Skip to main content
Ctrl+K

docs

  • Twitter
  • Mastodon
  • Contact
  • Blog
  • Twitter
  • Mastodon
  • Contact
  • Blog

Team Compass

Organization wide

  • Organization
    • Mission and values
    • Theory of Impact
    • Goals and strategy
    • Service model
    • Value proposition
    • Annual plan for 2026
    • Organizational structure
      • Executive Director
      • The steering council
    • Key Performance Indicators
  • People operations
    • Scope and responsibilities
    • KPIs for People
    • Expectations of team members
    • Hiring process and information
    • Compensation and Benefits
    • People Management
    • Planning for professional development
    • Personal and professional development: time and money
    • Job titles and levels
    • Taking time off
    • Cost reduction decision making framework
  • Open source strategy
    • Scope and responsibilities
    • Open source strategy and policies
    • Funding for open source
    • Intellectual property
    • Key open source communities
  • Finance and accounting
    • Scope and responsibilities
    • Financial strategy
    • Accounting data
      • Overview of accounting reports from SAGE Intacct
    • Contracts, grants, and invoices
    • Spending money
    • Fundraising and philanthropy pipeline
    • Budget projections
    • Monthly accounting and budget projection process
    • Payment accounts
    • Cloud costs
    • Ramp Cards Policy (for individual use)
  • Administration
    • Scope and responsibilities
    • Structure and roles
    • CS&S Administration
    • Reimbursements and Ramp
    • Set up a contractor with CS&S
    • Send invoices to CS&S
    • Google workspace
    • GitHub organization
    • AirTable accounts
    • Web domains and DNS
    • Authentication accounts for hubs
    • Shared bitwarden account
    • Zoom accounts
  • Team-wide practices
    • Workflow goals and strategy
    • Code of conduct
      • CoC Report Response Protocol
      • Social Rules
    • Workflow for planning and delivery
    • Team Practices
      • Guide for Open, Honest Conversations
      • Decision making guide
      • Expectations of all team members
      • Giving and receiving Effective Feedback
      • Responsibile and accountable roles
      • “Brown Bag” Tech Talks
    • Getting started and onboarding
    • Where to look for information
    • Meeting guidelines and policy
    • Communication channels
    • About the Team Compass
    • External documentation and their owners

Areas of work

  • Delivery Enablement
    • Delivery Enablement team overview
      • Chief of Staff Role
      • Delivery Manager Role
      • Operations Manager Role
      • People Lead Role
      • Executive Assistant
    • Delivery Enablement team KPIs
    • Creating alignment
    • Meetings in Delivery Enablement
      • Operations Planning (Review Operations Board)
      • Operations Sync (Operations Alignment and Sync)
      • Retrospective (Delivery Enablement/Operations Retro)
      • BD/P&S Engagement Review (Review Active Engagements in Asana)
    • General Processes
      • Process for managing Cloud Costs
      • Process for collecting MAU data
  • Business Development
    • Business Development Overview
    • Business development strategy
    • Pricing strategy
    • Key Performance Indicators for BD
    • Roles in Business Development
      • Business Development Lead (BD Lead)
      • Sales 1
    • Sales Operations Overview (2025)
    • HubSpot Usage (2026)
    • Engagement management
    • Creating alignment
    • Workflow for hub service leads
    • Grants and projects workflow
    • Engagement Workflow Overview
    • Strategic Contacts — HubSpot Guide
    • Using FreshDesk
    • Track Hub Usage with Grafana
    • Community Check-in
    • Meetings in Business Development
      • Horizon Scanning (P&S: Horizon Scanning)
      • Project Management alignment (P&S: Project Management)
      • Sales Sync (BizDev: Sales Sync)
      • Product Sync (BizDev - Product Sync)
  • Marketing and outreach
    • Marketing goals and strategy
    • Communications workflow
    • Our blog
    • Social media
    • Mailing list
    • Web analytics
    • Design, images, and videos
    • Publishing and DOIs
    • Talks, presentations, and conferences
    • Printing stickers
    • Business cards
  • Product and Services
    • Scope and responsibilities
    • Structure and roles
      • Head of Product and Services
      • Senior Product Manager, Open Science Enablement
      • Delivery Manager / Chief of Staff
      • Engineering Manager
      • Open Source Applications Engineer
      • Open Source Infrastructure Engineer
      • Technology Lead
    • Product delivery flow
    • Documentating product features
    • Using Productboard for prioritization
    • Community Relations
    • Services
    • Estimating costs of delivery
    • Key Performance Indicators
  • Engineering
    • Scope and responsibilities
    • Structure and roles
      • Delivery Manager / Chief of Staff
      • Engineering Manager
      • Open Source Applications Engineer
      • Open Source Infrastructure Engineer
      • Technology Lead
    • Workflow
      • 2-week iterations - Our default process
      • Hyper focus and learning workflow (1-week iterations)
      • Task Sizing
    • Engineering work definition of ready
    • Technical strategy
    • Accounts and cloud access
    • Secrets, credentials, and passwords
    • Merge and Code Review policy
    • GitHub repository conventions
    • Style guide for repositories
    • Team meeting archive
      • 2022 Meeting Notes
      • 2021 Meeting Notes
      • 2020 Meeting Notes

Services

  • Services Overview
  • Dedicated Delivery Management
    • Ceremonies
    • Time Tracking
  • Interactive Computing
    • Hub Rollout Process
    • Sales Engineer Guide
    • Needs Assessment Guide
    • Validation Guide
    • Onboard a Community
    • Offboard a Community
    • Community Value
    • Communicating Changes
    • Making Changes to Multiple Hubs (network-wide updates)
    • Adding an Additional Hub to an Existing Community
    • Dedicated and Shared clusters for hubs
    • Budget alerts response
    • Showcase Hub
    • Incident Response
      • Things to know before an incident
      • Incident response process
      • After the incident
      • Paying out past Incident Report debt
  • Technical Support
    • Terminology
    • Roles and team structure
    • Support process
    • Add or update community representatives
    • Initial timeboxed (30m) ticket resolution checklist
    • Communication channels
    • Expected time off and downtime
    • Support Templates
  • Community Success Hours
    • Overview
    • Delivering and logging Community Success Hours
    • How to set up CSH in Asana
  • Open Source Development
  • Delivery
    • Engagement Management
    • Premier Membership Engagement
    • General Membership Engagement
    • Starter Service Engagement
  • List of running hubs

Reference Material

  • Calendars and meetings
  • List of team members
  • Guide to writing documentation
    • Edit the documentation
    • Write content with MyST markdown
    • Set up a local documentation environment
    • Secrets, passwords and access tokens
  • Important terminology
  • Inspiration for 2i2c’s practices
  • Repository
  • Suggest edit
  • .md

Technical Support

Technical Support#

Attention

Are you a community representative looking for Technical Support for your 2i2c hub? Please go our Support Page.

This section contains information that our team uses to triage, communicate, and resolve Support Requests that come from communities.

The Product and Services team is responsible for delivering our Technical Support and has the authority to design the system of roles and processes that defines “support at 2i2c”, and to advocate for the resources needed to fill those roles.

  • Terminology
  • Roles and team structure
  • Support process
    • Overview of the support process
    • Process for support triage and resolution
      • Triage process
      • Non-incident response process
      • Workshop Request
    • Prioritizing non-incident support requests
      • Associating Support Tickets with Communities
  • Add or update community representatives
  • Initial timeboxed (30m) ticket resolution checklist
    • Category 1: Something is not working
    • Category 2: New feature requested
    • Category 3: Technical advice
  • Communication channels
    • External communication
      • FreshDesk
    • Internal communication
  • Expected time off and downtime
    • Expected time off support policy
    • Support process during expected time off
    • Rotating team members during expected time off
  • Support Templates
    • Notifying a community champion of a budget alert trigger

previous

Paying out past Incident Report debt

next

Terminology

2i2c links

  • Twitter
  • Mastodon
  • Contact
  • Blog