#101 Convert the Communicating and Getting Help Wiki page
Opened 2 years ago by pbokoc. Modified a year ago

This Wiki page is now marked as old and slated for deletion: https://fedoraproject.org/wiki/Communicating_and_getting_help. It contains important information that we should review for accuracy and publish on the docs site. We even have a placeholder page for it (https://docs.fedoraproject.org/en-US/project/help/), so that's the obvious spot.

Later we'd like to link it from each page's header or footer through a change in the docs UI bundle; there's a separate issue for that (https://pagure.io/fedora-docs/fedora-docs-ui/issue/48), but we need to do the conversion first so we have somewhere to link to.


Oh yeah! I think that is exactly the page I had in mind in creating that placeholder. Thanks for the reminder!

@pbokoc does "we" mean "petr" or is it the generic "we"? I may end up working on it during meetings etc later this week, but if you're planning on tackling it, I'll stay out of your way.

@bcotton Generic. If you want to do it, be my guest :)

Metadata Update from @jflory7:
- Issue priority set to: waiting on assignee
- Issue tagged with: help wanted, type - new docs

2 years ago

Just to help move this along, let me move some things from my brain into this ticket.

I think this should be split into two pages, Getting Help and Project Communications.

Getting Help should focus on Docs, Ask Fedora, and on the #fedora channel via Matrix.

It could have some bits on how to get help in the OS itself, but I feel like maybe that gets too RTFMy. Likewise, maybe something about upstreams, but I'm not sure.

Project Communications should cover the whole glorious mess.

  1. It should start by mentioning Ask Fedora (and the Matrix channel again), and have a link to the Getting Help page.

  2. Next, it should talk about Fedora Chat / Matrix. Unlike the wiki page, this shouldn't attempt to list all of the channels. Instead, invite people to join the space to see. It should give a brief overview of what the server is, how we use it, and how to connect to the space from another client or homeserver.

  3. Then, it should cover Fedora Discussion and Hyperkitty. I think it should reference announce, devel, devel-announce, and perhaps test directly, but again shouldn't attempt to list them all.

  4. Finally, Other Communications Channels. Subsections in order:

  • Pagure tickets (like this one!)
  • Bugzilla (this should note that upstream bug trackers are also important)
  • IRC (quick pointer to libera.chat, mention the bridge; no list of channels)
  • External community channels (twitter, telegram, discord, fedora forum, reddit, etc.)

Login to comment on this ticket.

Metadata