Council/council-docs
1
0
Fork 0
Code Issues 8 Pull requests Projects Releases Packages Wiki Activity Actions

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

New issue
Open
opened 2024-03-14 10:17:01 +00:00 by ankursinha · 0 comments
ankursinha commented 2024-03-14 10:17:01 +00:00
Contributor
Copy link

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?
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
edition_policy_change
youtube_proposal
stg
No results found.
Labels
Clear labels   
blocked

Progress blocked by another task or issue

  
Closed As
complete
Closed with the reason of complete

  
Closed As
duplicate
Closed with the reason of duplicate

  
Closed As
insufficient data
Closed with the reason of insufficient data

  
Closed As
moved
Closed with the reason of moved

  
Closed As
not possible
Closed with the reason of not possible

  
Closed As
out of scope
Closed with the reason of out of scope

  
Closed As
stale
Closed with the reason of stale

  
good first issue

Good for newcomers (if you want to get involved, try working on one of these!)

  
help wanted

Anyone is welcome to help us with this!

  
needs changes

Needs changes or fixes before closing

  
needs feedback

Extra attention or feedback needed

  
needs testing

Needs testing or QA before closing

  
Priority
awaiting triage
Priority of awaiting triage

  
Priority
needs review
Priority of needs review

  
Priority
next meeting
Priority of next meeting

  
Priority
waiting on assignee
Priority of waiting on assignee

  
Priority
waiting on external
Priority of waiting on external

  
type - dev tools

Related to developer tooling or build scripts

  
type - existing docs

Improves or changes existing documentation

  
type - new docs

Adds or creates new documentation

No labels
blocked
Closed As
complete
Closed As
duplicate
Closed As
insufficient data
Closed As
moved
Closed As
not possible
Closed As
out of scope
Closed As
stale
good first issue
help wanted
needs changes
needs feedback
needs testing
Priority
awaiting triage
Priority
needs review
Priority
next meeting
Priority
waiting on assignee
Priority
waiting on external
type - dev tools
type - existing docs
type - new docs
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
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/council-docs#225
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?