How we communicate

There are a few different communication channels with 2i2c, depending on your team and what kind of communication you’d like to have. See below for details.

Asynchronous communication

Most communication should be asynchronous - this means you communicate without the expectation that another person immediately responds. Asynchronous communication is more inclusive of team members that are spread across many time zones and with many responsibilities. By default, try to keep it async!

General discussion between the team

For those who are doing daily work with 2i2c, we use GitHub Discussions for our asynchronous conversation. There are a few different discussion forums depending on the kind of conversation you’d like to have:

To-do items and deliverables

For tracking actionable items and conversation around them, 2i2c uses GitHub issues and pull-requests. Check the repositories in the 2i2c-org GitHub org for where these conversations happen.

In addition, check the active projects page for a list of active projects and links to where communication is happening around them.

Team members are expected to monitor repositories that are important to the work that they are doing. Keep up-to-date with new issues and comments on pre-existing issues.

Daily workflow planning

See the team coordination page for information about how we communicate around our priorities and daily workflow.

Steering Council discussion

The Steering Council of 2i2c conducts asynchronous discussion via GitHub Issues in the meta/ repository. However, this may change in the future (see this issue for context).

Synchronous communication

Synchronous communication assumes that there are one or more people communicating directly with each other at the same time. This is usually for informal communication between team members (ie, information that does not need to be tracked over time).

Important

Any conversations that are important or that should be remembered outside of the immediate context should be encoded as Discussion threads, GitHub Issues, or otherwise put in a more asynchronous place so that others may discover it and participate.

Here are things that should not be conducted synchronously, but instead put in an issue or other “Source of Truth” location:

  • Important updates on the status of a project or issue

  • Decisions that were made from conversations in Slack

  • Important dates or deadlines announced on Slack

  • Major bugs or problems that were unconvered on Slack

  • New ideas that warrant follow-up

Team coordination

Team coordination generally happens via the 2i2c Slack channel (http://2i2c.slack.com/). In particular in the #team-updates channel as well as in the hub-specific channels (e.g., those beginning with #hub-). This is generally used for quick coordination, hand-offs, and requests for help or reviews. It is not used for official records or planning.

Informal communication

Informal communication happens in the 2i2c Slack channel (http://2i2c.slack.com/). This Slack has both 2i2c staff and Steering Conucil members, as well as several other interested parties.