Skip to content

Components: Update communication channels and community spaces pages #59

@duncandewhurst

Description

@duncandewhurst

Copying relevant comments from #58 (comment):

@kathryn-ods:

I'm wondering about the distinction between communications channels and community spaces - these could all potentially be under one heading

@duncandewhurst:

I'm wondering about the distinction between communications channels and community spaces - these could all potentially be under one heading

Good point. I'm definitely not a comms expert, but I think the difference is that communication channels are more about one-way/broadcast type communication, whilst community spaces are more about discussion amongst the community.

Based on that, maybe it was wrong to put email list under communication channels, as an email list as described on the page is mostly about discussion. However, most initiatives do have an email newsletter/mailing list (as distinct from a discusion group).

So maybe we need the following:

1. Communication channels


* Blog

* Social media

* Mailing list / newsletter


2. Community spaces


* Forum

* Chat channel

* Email list / discussion group (depending on the outcome of [Components - are public email lists still relevant? #59](https://github.com/OpenDataServices/os4d/issues/59))

What do you think?

@mollieodsc it would be good to get your take, too. We're discussing these two components:

* [Communication channels](https://os4d--58.org.readthedocs.build/components/communication_channels.html)

* [Community spaces](https://os4d--58.org.readthedocs.build/components/community_spaces.html)

@kathryn-ods:

Yeah, I think disambiguating the mailing list from the email discussion group is helpful here. Social media could potentially straddle both categories but I think it's fine putting it under communications channels


OS4D currently recommends an email list as a possible communication channel:

  • An email list is a widely-accessible and low-cost way for a group to hold discussions, and many email list providers offer a public archive service so that accountability is maintained. Standards often have a discussion list and a separate announcement list, so that members can choose how involved they want to be. The asynchronous nature of email lists allows users to be involved as regularly or infrequently as they prefer. However, some users are reticent to post to public email lists for fear of appearing foolish or having their words during their learning being recorded.

In #58 (comment), @kathryn-ods asked:

Are public email lists still common practice? This isn't something I have come across

Metadata

Metadata

Assignees

No one assigned

    Labels

    existing contentRelates to improving existing content

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions