[main] communications.adoc: add some info explaining how to use the various communication channels? #225

Open
opened 2024-03-14 10:17:01 +00:00 by ankursinha · 2 comments
Contributor

A few newcomers in the Fedora Join matrix channel have noted that while we list the various channels, there isn't really a resource on how they are to be used. There's mailing list etiquette for example, but no real explanation on how to subscribe to a list and what to do to post. Similarly, even though Discourse and Matrix are quite intuitive perhaps short howtos with screenshots would be useful?

More thoughts:

  • should any pages related to guidelines/etiquette also be moved to docs, if yes, where?
A few newcomers in the Fedora Join matrix channel have noted that while we list the various channels, there isn't really a resource on how they are to be used. There's mailing list [etiquette](https://fedoraproject.org/wiki/Mailing_list_guidelines) for example, but no real explanation on how to subscribe to a list and what to do to post. Similarly, even though Discourse and Matrix are quite intuitive perhaps short howtos with screenshots would be useful? More thoughts: - should any pages related to guidelines/etiquette also be moved to docs, if yes, where?
Owner

Metadata Update from @jflory7:

  • Issue priority set to: waiting on assignee (was: awaiting triage)
  • Issue tagged with: help wanted, type - new docs
**Metadata Update from @jflory7**: - Issue priority set to: waiting on assignee (was: awaiting triage) - Issue tagged with: help wanted, type - new docs
Owner

I think the owners of each platform can help us with this. For Discourse, we can link to the newly-drafted moderation guidelines (related: Fedora Council Ticket 392). For Matrix, we could ask the Matrix WG for help with creating documentation like this.

I think the owners of each platform can help us with this. For Discourse, we can link to the newly-drafted moderation guidelines (related: [Fedora Council Ticket 392](https://forge.fedoraproject.org/council/tickets/issues/392)). For Matrix, we could ask the Matrix WG for help with creating documentation like this.
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
council/docs#225
No description provided.