#214 [main] Doc issue in file project/modules/ROOT/pages/communications.adoc - difficult to join Fedora space with a non-Fedora account
Opened by kparal. Modified

Today I finally found out how to join the Fedora space on Matrix, and it was far from trivial. The documentation needs improvements.

I already had a matrix.org account, so I didn't want to switch to a fedora.im account (i.e. go through https://chat.fedoraproject.org ). However, the Communication in Fedora doc only has information how to use chat.fp.o, and no other instructions. I can't even see the list of Fedora channels, because it's a link to https://chat.fedoraproject.org/#/room/#fedora-space:fedoraproject.org , which requires a fedora.im account.

After a lot of trials and errors (manually searching for Fedora spaces in Element, on fedoraproject.org and fedora.im domains), the solution for me was to manually create https://matrix.to/#/#fedora-space:fedoraproject.org link and open it, which allowed me to join the top-level Fedora space (which then shows all the sub-spaces and rooms) in Element.

Please adjust the documentation to also provide guidance for people with an existing non-fedora.im account. Something like this:

If you already have an existing (non-Fedora) Matrix account which you want to use, follow this invitation to join the Fedora space, or join #fedora-space:fedoraproject.org manually in your preferred client. This top-level Fedora space lists all sub-spaces and rooms available for you to join.

Thank you.

PS: This sentence should probably be removed, because the IRC bridge doesn't seem to be coming back:

Most of these channels are mirrored on IRC at Libera Chat.

CC @mattdm


I found out that the matrix.to link doesn't allow Fedora Chat users to join :-/ So ideally there should be both links provided - chat.fp.o (for Fedora Chat users) and matrix.to (for other clients).

Metadata Update from @jflory7:
- Issue priority set to: waiting on assignee (was: awaiting triage)
- Issue tagged with: good first issue, help wanted, type - existing docs

This could be a topic of interest for the Matrix Working Group to adopt this kind of guidance in the Community Ops team docs.

Metadata Update from @jflory7:
- Issue untagged with: type - existing docs
- Issue tagged with: type - new docs

I changed the label from existing docs to new docs because I think the purpose of the Communications page is to be brief and concise. We can link out to longer-form content elsewhere. Ultimately, this request will need to source the volunteer labor of documenting these things for the various folks helping run and maintain the Fedora Matrix presence.

Metadata