Delivering and logging Community Success Hours

Delivering and logging Community Success Hours#

2i2c team members deliver Community Success Hours (CSH) by:

  • Responding to complex support questions, which we track on GitHub.

  • Attending and supporting community planning meetings.

  • Offering ongoing Slack-based consultation.

  • Providing expert guidance on JupyterHub, image management, and open science workflows.

  • Supporting grant co-writing and open science governance structures.

Any team member can proactively recommend CSH to a community. Most commonly a community asks for help via a FreshDesk ticket or a question in a meeting.

How to log CSH activity#

Log CSH work in our activity log. When logging via GitHub, use the CSH label and include the community’s name and contact people in the issue.

How to deliver Community Success Hours#

  • Read the context about the community’s problem in the GitHub card.

  • Reach out to the community contact to offer your time - sending them your Cal.com link makes scheduling easy.

  • Listen to their problem and offer advice. That can include existing solutions or future ones on our public roadmap.

  • Add notes about outcomes and follow-up actions to the GitHub card.

  • When the work is done, log it (see How to log CSH activity).