Fedora Docs 2025 Initiative

Initiative Team Details

• Name: Peter Boy @pboy and Petr Bokoc @pbokoc
• Email: pboy at fedoraproject dot org, pbokoc at fedoraproject dot org
• Team space: #docs:fedoraproject.org on Matrix

Initiative Details

• Full Proposal: https://fedoraproject.org/wiki/Initiatives/Fedora_Docs_2025
• Summary Overview: One one hand, we have to take intensive onboarding and community building measures through intensive promotion and advocacy for Fedora Docs on all Fedora communication channels as well as to lessen the barriers to contribute to Doc by improving contributors documentation, add instruction videos, flatten the confusing, highly tangled storage locations (possibly into a single repository), and enhance the local authoring tools. On the other hand we have to establish a sound workflow, building interactions of devs and QA with writers for specific documentation topics, establish regular in-person hackfests either on their own or in conjunction with other Fedora events such as Flock, and offer high quality online instructional lessons and workshops.
• Target Release: F43, F44
• Link to Discussion post: https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-543-new-initiative-fedora-docs-2025/167686
• Dependencies:
  • Council executive sponsor Justin Wheeler
  • Aoife Moloney
  • Marketing team
  • Podcast team
  • Mindshare Committee
  • Design team
  • Join team
  • CommOps team
  • Budget Hackfest
  • Budgets for in-person meetings
  • Budgets for relevant events (Fosdem, Flock, DevConf, ...)
  • Interns/Outreachy mentored projects
• Requires Change Proposal(s): N

Benefit to Fedora

The exact scope of the output cannot be determined in detail at this point in time. Community building is a highly fluid process. It depends on how many team members can be attracted, how early they can be attracted, and what their skill profiles are. Instead of a fixed plan, communication must be continually ignited and emerging opportunities recognized and exploited. As little as details can be determined in advance, the more certain it is that such measures will lead to success. This is especially true in an environment such as the Fedora Project, where an organizational framework and a common interest already exist. The key is to steer the process from small, “unobtrusive” beginnings to establishing a regular topic of communication in the Fedora community.

Also, it is not possible to renew all documentation in a single year. However, the necessary structures, instructions, tools, and sample examples can be created. Which articles specifically receive an update depends on prioritization on the one hand and on opportunities that arise on the other.

Expected Outcomes

See Logic Model, Outcomes.

Success Criteria

See Logic Model, Outputs.