#meeting:fedoraproject.org: docs

Meeting started by @jflory7:fedora.im at 13:11:04 UTC

Meeting summary

  1. TOPIC:Roll Call & Welcome's (@jflory7:fedora.im, 13:11:18)
    1. INFO: Present: @jflory7, @korora, @cstrauf, @theprogram, @nielsenb, @pg-tips, @smoliicek, @pboy (@jflory7:fedora.im, 13:12:23)
  2. TOPIC:Announcements & community news (@jflory7:fedora.im, 13:12:43)
    1. INFO: === "Save the Date: Fedora Council Video Meeting on 2026 Strategy Summit" === (@jflory7:fedora.im, 13:13:11)
    2. LINK: https://fedoramagazine.org/fedora-council-meeting-2026-strategy-summit/ (@jflory7:fedora.im, 13:13:17)
    3. INFO: Join the Fedora Council video meeting on Feb 25, 2026 for 2026 Strategy Summit outcomes and strategic direction with Fedora leadership. (@jflory7:fedora.im, 13:13:33)
    4. INFO: Some migrations are underway for Forgejo, but some of the more complex repos (e.g. Antora theme, docs website) have some bigger challenges. Not enough details known to report on right now. (@jflory7:fedora.im, 13:17:31)
  3. TOPIC:Ad-hoc agenda triaging (@jflory7:fedora.im, 13:18:08)
    1. LINK: https://forge.fedoraproject.org/docs/tickets (@jflory7:fedora.im, 13:18:59)
    2. AGREED: Tickets to cover for today, as time allows: Ticket #1, Ticket #8, Ticket #6, Ticket #9 (@jflory7:fedora.im, 13:23:03)
  4. TOPIC:Ticket #1: Improvement of the instructions for the Fedora Local Authoring System (@jflory7:fedora.im, 13:23:15)
    1. LINK: https://forge.fedoraproject.org/docs/tickets/issues/1 (@jflory7:fedora.im, 13:23:21)
    2. INFO: Peter proposed the following packages of work to group the content. (@jflory7:fedora.im, 13:25:29)
    3. INFO: **Introductory page**: Update the tools section to focus on local authoring, leaving the other in the text, but marking as „not current“. Update explaining how to get a page from the icons on the documentation. (@jflory7:fedora.im, 13:25:34)
    4. INFO: **Article, "Create a new documentation module"**: Update focusing on Local authoring, leaving the other parts in place with a warning "outdated" (@jflory7:fedora.im, 13:25:40)
    5. INFO: **Contributing to Quick Docs**: Update with focus on Local authoring, Special Focus on Correct Meta Data (@jflory7:fedora.im, 13:25:46)
    6. INFO: **Article: How to Create and Use a Local Fedora Documentation Workflow**: Update to describe in a compact way the basic workflow, Integrate Article (How to run a local preview) (@jflory7:fedora.im, 13:25:52)
    7. INFO: **New: Article „Git for Writers“**: Starting with adjusting and improve „A Git cheat sheet For Server Documentation Authors“ (@jflory7:fedora.im, 13:25:57)
    8. LINK: https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/tools-local-authoring-env/ (@jflory7:fedora.im, 13:26:36)
    9. HALP: We need some help from the Docs Team to carry forward the local authoring content. Per the last discussion, we do not want to reinvent the wheel, but we can help guide new writers through our tools and help them understand our processes. Help wanted! 🙏 (@jflory7:fedora.im, 13:30:33)
    10. HALP: We need a default issue template for our Forgejo tickets repo (@jflory7:fedora.im, 13:33:43)
    11. ACTION: @jflory7 Post an update in Ticket #1, explaining the meeting discussion and the context of where the discussion has gone so far (@jflory7:fedora.im, 13:34:45)
    12. ACTION: @jflory7 Create five sub-issues from Ticket #1, following @pboy's five work packages defined in #1 (@jflory7:fedora.im, 13:35:05)
    13. HALP: Once the five sub-issues about the new author documentation for Fedora Docs are opened, share a callout post on Fedora Discussion to invite people to contribute and request mentoring on these tasks from experienced Fedora Docs Team members. (@jflory7:fedora.im, 13:36:52)
    14. HALP: Or a Magazine post, cross-posted to Fedora Discussion. (@jflory7:fedora.im, 13:37:03)
    15. IDEA: Better systems of organization and structure for issue tracking, revision management, etc. could be helpful (@jflory7:fedora.im, 13:42:37)
    16. IDEA: Structured mentoring as a better way of inviting new contributors (@jflory7:fedora.im, 13:42:46)
    17. ACTION: @cstrauf Follow-up on Ticket #1 to follow along with the sub-issue split into five new issues for this project (@jflory7:fedora.im, 13:44:19)
  5. TOPIC:Ticket #8: Creating a Beginner's Guide to Fedora (@jflory7:fedora.im, 13:45:15)
    1. LINK: https://forge.fedoraproject.org/docs/tickets/issues/8 (@jflory7:fedora.im, 13:45:17)
    2. ACTION: @theprogram Share a summary of meeting discussion in today's Docs Team meeting into Ticket #8 to help rally a path forward on publishing the beginner's guide (@jflory7:fedora.im, 13:59:34)
  6. TOPIC:Open floor (@jflory7:fedora.im, 13:59:40)
    1. INFO: We ran out of time to discuss Ticket #6 and Ticket #9. Docs Team members are encouraged to review these tickets asynchronously. (@jflory7:fedora.im, 14:00:08)
    2. ACTION: @jflory7 Publish a post-meeting summary on the #docs tag on Fedora Discussion after the meeting (@jflory7:fedora.im, 14:01:11)


Meeting ended at 14:01:23 UTC

Action items

  1. @jflory7 Post an update in Ticket #1, explaining the meeting discussion and the context of where the discussion has gone so far
  2. @jflory7 Create five sub-issues from Ticket #1, following @pboy's five work packages defined in #1
  3. @cstrauf Follow-up on Ticket #1 to follow along with the sub-issue split into five new issues for this project
  4. @theprogram Share a summary of meeting discussion in today's Docs Team meeting into Ticket #8 to help rally a path forward on publishing the beginner's guide
  5. @jflory7 Publish a post-meeting summary on the #docs tag on Fedora Discussion after the meeting


People present (lines said)

  1. @jflory7:fedora.im (121)
  2. @theprogram:fedora.im (33)
  3. @cstrauf:fedora.im (21)
  4. @zodbot:fedora.im (14)
  5. @pboy:fedora.im (14)
  6. @pg-tips:fedora.im (6)
  7. @nielsenb:fedora.im (6)
  8. @korora:fedora.im (6)
  9. @niknikovsky:fedora.im (4)
  10. @meetbot:fedora.im (3)
  11. @smoliicek:fedora.im (1)
  12. @hricky:fedora.im (1)