Communication


Meetings

The Core Program team on purpose do not currently have any sync meetings. All communication is done asynchronous within the Slack channel.

Async communication

There are several types of communication systems used by this team. All are expected to be async, even though some might not feel it. There should never be pressure to feel you have to respond right away.

  • Slack: The main form of communication is our Slack channel #core-program. All key topics are then reported here.
  • GitHub Discussions: We also use discussions for longer form topics, this is a way to share and collaborate on topics.

Always make a post

A principle of our communication within this is team is that no matter where it might begin or be discussed, should be surfaced back on this site as a post. This way, everyone gets the opportunity to participate.

Recommendations

Communication can be hard, here are a few suggestions to help empower.

  • If you are going to use a thread with Slack, use an emoji to indicate and also ask the question, give your reply in the thread to start it.
  • Do not treat Slack as sync communication where possible, be ok with longer reply times.
  • Use discussions for conversations and working through, issues for direct action on GitHub where possible. This of course doesn’t mean questions can’t be asked within issues, but there is a distinct difference between a discussion and a question.
  • Use pings lightly. You might think you know who should help you, but someone else might be able to. If you only ping one person others might think you are taken care of and not jump in to help.
  • Always communicate as you would like to be communicated with.

#core-program