Issue #101. Re-arranged side menu; Updated help and join pages and added communications page #186
No reviewers
Labels
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
No milestone
No project
No assignees
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Council/council-docs#186
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue101-convert-help-wiki"
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?
Fix for Issue #101 - 1st Draft. nav.adoc, pages/help.adoc and pages/join.adoc all updated; pages/communications.adoc added.
rebased onto
93e4b9c620One sentence per line.
Also, maybe we should omit the context on why this decision was made for this page? I also see us pointing a lot of newcomers to this page, and I feel like it is is extraneous information for most people.
One sentence per line.
Also, I would prefer that we omit Telegram entirely. The bridges are in an unstable state and I would prefer to avoid emphasizing our bridged platforms in general. At some point in the long-term future, we may consider removing the bridges.
One sentence per line.
One sentence per line.
Also a minor typo:
s/announcments/announcements/I'm thinking that mailing lists should not be listed as a primary communication channel, but instead in the other channels section below. This primary section also omits any mention of Fedora Discussion other than the line about Fedora Ask. Ultimately, we really want to drive more people and traffic to Fedora Discussion as much as possible. This is the direction we want to move, also as part of our ongoing 5-year strategy to modernize our communication platforms.
@mattdm might also have thoughts about how exactly we word the mailing list piece? But at the very least, I'd prefer to not elevate the lists as a primary communication channel. We should mention something about Fedora Discussion here instead.
One sentence per line.
This is a tough one though. Should we mention Pagure here as a communication platform? Together with GitLab, these are common platforms for specific teams, working groups, and SIGs to discuss active work and tasks. But usually, this is for specific projects. I'm undecided on how we should explain Pagure and GitLab, and whether they should fit into this document at all. @bcotton @bookwar @sumantrom @dcantrell, any thoughts on this one?
Given the emergence of Ask Fedora, should we still list this community? It definitely seems active and people do go there to get questions answered. While I don't think they officially follow the Fedora Code of Conduct, they do have their own form of a code of conduct and forum etiquette, which seems sufficiently close to the Fedora CoC at a very cursory glance.
I'm not sure what is right to do here or not. I don't want to invalidate the heroic work of supporting people using Fedora and doing Q&A work. Maybe we could pad this text with more of an explanation, or add a disclaimer that the experience in this community is separate from the Fedora community? For example, if someone misbehaves there to a user or contributor and it is not handled by a platform moderator, realistically there isn't anything we could do about it.
Metadata Update from @jflory7:
Instead of listing Twitter, Reddit, and Discord here explicitly, I'd rather link to the Marketing social networks wiki page, which is more up-to-date on these kinds of things:
https://fedoraproject.org/wiki/Marketing_social_networks
One sentence per line.
Also, perhaps we should link directly to https://docs.fedoraproject.org/en-US/quick-docs/bugzilla/ ? If yes, let's use a
xrefhere. I think it would bexref:quick-docs::bugzilla/index.adoc[Fedora Quick Docs]This link is long. Any reason we cannot use https://fedoramagazine.org/how-to-contribute-to-fedora/ by itself? The extra
text=parameter has no effect for me in Firefox.@karl0sfandang0 Hey, a kudos for tackling #101! The wiki page you started with is an ancient page and there was so much information to crawl through and figure out if it was meaningful. I left some feedback inline above, but I want to add that your work is really appreciated and this is a page that we really need updated in Fedora. So, thank you for your work on this! 🙏
Hi @ankursinha, @alciregi, @t0xic0der, @bt0dotninja, @kevin, et al, if you have some free time, here is a Pull Request that we could really use your feedback on!
This will replace the Communicating and getting help wiki page once it goes live. Getting it right will be important so we can use this as a meaningful place to direct newcomers and old-timers alike about the best ways to get help and communicate with other Fedora folks across the community. Since you all are either Join SIG members or long-time Fedorans, you have a lot to offer here.
You can always pull down these changes locally and build the Fedora docs site locally, but an easier way to review this might be by using the Asciidoctor.js Live Preview for your browser and viewing each page from the browser (see add-on for Firefox, Chrome, Edge). Once you have the add-on installed, you can navigate to the specific pages:
I think that we should keep from using Pagure as a communication platform to better establish our move to GitLab for projects and Discussions for conversations.
It should be fine if we make it clear that this is an external support community.
I wonder if it begs us to ask the question or better define what an external support community is, their limits, etc.
+1 to this.
Pretty sure we would miss changing it everywhere consistently if a change were to happen so its just better to have it all in one designated place.
I agree with almost all @jflory7 's comments. ;)
I'd suggest for mailing lists we should just describe the current state (most dicussion is on discuss, but some communications still happen on lists), and then we can adjust it in another PR later when appropriate. I'd like to get this live instead of lingering on that. :)
Anyhow, many thanks for writing this up!!!
Agreed-ish. We should keep those announcement lists where they are, but focus on Discussion. Something like "We use Fedora Discussion for blah blah blah blah. Some teams and announcements still use mailing lists. A few key lists are:"
I'm okay with it in this context.
No.
Thank you for the input everyone. I will take it all into account in another pass at this as soon as possible.
OK. I've kept the Pagure bit in but moved it down, and I've removed the bit about Fedora Forums.
rebased onto
1a14eae9ceThis is in substantially good shape. We can make further edits afterward if needed. Thanks, @karl0sfandang0
Pull-Request has been merged by bcotton