Skip to article frontmatterSkip to article content

Communication within a community impacts the contributor experience, influences an individual’s sense of belonging, and provides a historical record of project decisions.

The choice of channels will depend on the specific requirements of your project, such as keeping the community informed of any known bugs or upcoming features, assessing current needs from the community members, inviting comments on the project’s management plans, facilitating the overall progress of the project, as well as having somewhere to field questions and receive/act on feedback.

When setting up your communication channels, there are some important things to consider, such as the following:

There are three commonly used channels: mailing lists (such as Topicbox or Google groups), community forums (such as Vanilla Forum or Discourse) and chats (such as Gitter or Slack). Besides these, many communities also use platforms for weekly or monthly newsletters, blogs, and social media on X (formerly Twitter) or Facebook.

In the table below, some properties of the first three communication platforms have been highlighted, which will allow open source project leaders to choose the most appropriate channels for their communities.

Features of Different Communication Channels

The table below compares features of mailing lists, forums and chats. Here are some of the questions one might wish to ask when thinking about each feature:

FeatureMailing ListsForumsChat
Media sharing✅ (cumbersome)
Archivable
Persistent
Noisy
Open
Consistent UX
Threading/Filtering of conversations
Social sharing
User profiles
“Friending”/“Ignoring” capabilities
Searchable by topic
Easily Exportable