What kind of things would you like to see in place of the change-style release notes we ship now? Do you think they could be beginner-friendly topics?
Would it help to do some strategic thinking and rework the nav structure? Is there anything more required than looking at
nav.adoc for this one?
These would be especially helpful for bringing in outsiders to contribute to our docs. It could be a good candidate agenda item for in-person collaboration?
The idea focuses on bridging active participants in user support communities to become Fedora Docs contributors. The benefit is raising the quality of official fedoraproject.org documentation and boost their visibility for those who help others fix problems or figure out new things on Fedora.
To me, online user support communities includes but is not limited to:
- Reddit: r/Fedora (16,000 subscribers)
- Telegram: @fedora (1,800+ members)
- Discord: discorg.gg/fedora (1,300+ people)
- And others
In all of these places, every day, people share (and re-share) links to solution pages or blogs on how to solve problems / learn new things. Different communities share different sets of resources. Our goal is to encourage top contributors to these user communities to consider contributing to official documentation based on the additions they want to see. This way, we involve them in the process of creating and maintaining the documentation. Evaluating consistency of frequently-linked URLs across groups is interesting after running a couple of these events.
I was thinking, this could be an equivalent to the QA team’s “Test Days” for specific-targeted goals. Instead, “Doc Days”, for specifically-targeted topics.
Does this better explain?