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

Convert the Communicating and Getting Help Wiki page #101

New issue
Closed
opened 2021-01-06 15:40:09 +00:00 by pbokoc · 16 comments
pbokoc commented 2021-01-06 15:40:09 +00:00
Contributor
Copy link

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.

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.
mattdm commented 2021-01-06 15:48:41 +00:00
Contributor
Copy link

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

Oh yeah! I think that is exactly the page I had in mind in creating that placeholder. Thanks for the reminder!
bcotton commented 2021-01-06 15:53:46 +00:00
Contributor
Copy link

@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.

@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.
pbokoc commented 2021-01-06 18:28:38 +00:00
Author
Contributor
Copy link

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

@bcotton Generic. If you want to do it, be my guest :)
jflory7 commented 2021-02-10 20:38:50 +00:00
Contributor
Copy link

Metadata Update from @jflory7:

  • Issue priority set to: waiting on assignee
  • Issue tagged with: help wanted, type - new docs
**Metadata Update from @jflory7**: - Issue priority set to: waiting on assignee - Issue tagged with: help wanted, type - new docs
mattdm commented 2021-10-21 21:04:59 +00:00
Contributor
Copy link

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.)
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](https://matrix.to/#/#fedora:fedoraproject.org?web-instance%5Belement.io%5D=chat.fedoraproject.org) 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.)
karl0sfandang0 commented 2023-02-28 08:17:41 +00:00
Contributor
Copy link

I'm happy to take this one and start looking at it . @bcotton could you assign it to me?

I'm happy to take this one and start looking at it . @bcotton could you assign it to me?
bcotton commented 2023-02-28 14:02:20 +00:00
Contributor
Copy link

Metadata Update from @bcotton:

  • Issue assigned to karl0sfandang0
**Metadata Update from @bcotton**: - Issue assigned to karl0sfandang0
jflory7 commented 2023-02-28 17:51:08 +00:00
Contributor
Copy link

@karl0sfandang0++ Thanks for taking this one!

When the PR is ready, let's also bring in folks like @ankursinha, @t0xic0der, @alciregi, and perhaps others in the Join SIG to share feedback on the updated page. I know pages like this come up often in the Join SIG, so we should coordinate carefully with those folks before retiring any wiki pages like this one (there are a LOT of links to this specific page in our 10-15 year history of the Fedora Wiki).

Tagging them now so they have some advance notice on this, or if they have any additional feedback to add now before a draft is ready, they can do so.

@karl0sfandang0++ Thanks for taking this one! When the PR is ready, let's also bring in folks like @ankursinha, @t0xic0der, @alciregi, and perhaps others in the Join SIG to share feedback on the updated page. I know pages like this come up often in the Join SIG, so we should coordinate carefully with those folks before retiring any wiki pages like this one (there are a LOT of links to this specific page in our 10-15 year history of the Fedora Wiki). Tagging them now so they have some advance notice on this, or if they have any additional feedback to add now before a draft is ready, they can do so.
karl0sfandang0 commented 2023-03-01 17:34:16 +00:00
Contributor
Copy link

@jflory7 ACK. Thank you. I will do.

@jflory7 ACK. Thank you. I will do.
bcotton commented 2023-03-08 13:42:50 +00:00
Contributor
Copy link

@karl0sfandang0 a couple of more additions as I mentioned:

These probably fall into the 3rd item in Matthew's list

@karl0sfandang0 a couple of more additions as I mentioned: * Fedora Magazine (for user-facing announcements and cool stories about usage, features, etc etc): https://fedoramagazine.org * Fedora Community Blog (for contributor-facing announcements and updates): https://communityblog.fedoraproject.org * Friday's Fedora Facts (weekly posts with status updates, schedule info, etc. Also on the Community Blog but worth highlighting separately, imo): https://communityblog.fedoraproject.org/tag/fridays-fedora-facts/ These probably fall into the 3rd item in [Matthew's list](https://pagure.io/Fedora-Council/council-docs/issue/101#comment-758718)
pboy commented 2023-03-08 14:49:18 +00:00
Copy link

Just for the sake of completeness and as a reminder item: see #185 (closed as duplicate) The item Quick Doc must be replaced by User Docs (of which Quick Doc is a part).

Just for the sake of completeness and as a reminder item: see #185 (closed as duplicate) The item Quick Doc must be replaced by User Docs (of which Quick Doc is a part).
karl0sfandang0 commented 2023-03-08 15:32:41 +00:00
Contributor
Copy link

@pboy ACK. Thank you.

@pboy ACK. Thank you.
karl0sfandang0 commented 2023-03-08 15:46:21 +00:00
Contributor
Copy link

PR #186 Created

PR #186 Created
bcotton commented 2023-03-24 19:56:25 +00:00
Contributor
Copy link

Fixed in #186

Fixed in #186
bcotton commented 2023-03-24 19:56:25 +00:00
Contributor
Copy link

Metadata Update from @bcotton:

  • Issue close_status updated to: complete
  • Issue status updated to: Closed (was: Open)
**Metadata Update from @bcotton**: - Issue close_status updated to: complete - Issue status updated to: Closed (was: Open)
jflory7 commented 2023-03-25 14:17:10 +00:00
Contributor
Copy link

@karl0sfandang0 Thank you for your work on this!

I set a Fedora Docs redirect on the original wiki page to the new Fedora Docs page.

https://fedoraproject.org/wiki/Communicating_and_getting_help =>
https://docs.fedoraproject.org/en-US/project/communications/

@karl0sfandang0 Thank you for your work on this! I set a Fedora Docs redirect on the original wiki page to the new Fedora Docs page. https://fedoraproject.org/wiki/Communicating_and_getting_help `=>` https://docs.fedoraproject.org/en-US/project/communications/
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
6 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/council-docs#101
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?