#meeting:fedoraproject.org: docs

Meeting started by @pboy:fedora.im at 13:01:43 UTC

Meeting summary

  1. TOPIC:Agenda (@jflory7:fedora.im, 13:05:50)
    1. INFO: Follow-up actions & announcements (@jflory7:fedora.im, 13:05:57)
    2. INFO: Contributor documentation – how to proceed (@jflory7:fedora.im, 13:06:00)
    3. INFO: Quick Docs content structure – how to proceed (@jflory7:fedora.im, 13:06:04)
    4. INFO: Administrator Guide – Next steps (@jflory7:fedora.im, 13:06:08)
    5. INFO: Open Floor (@jflory7:fedora.im, 13:06:12)
  2. TOPIC:Follow-up actions & announcements (@jflory7:fedora.im, 13:07:48)
    1. INFO: The Fedora Council held its annual Strategy Summit (formerly known as Hackfest) last week in Tirana, Albania. One of the three days was dedicated to Fedora Community Initiatives. Co-leads @pboy and @pbokoc presented on the status of the Initiative, raised concerns and needs for resources, and participated in overall discussion about the next year in strategy for Fedora. Daily summaries of the Summit were shared on Fedora Discussion. Feedback and comments are welcome on Fedora Discussion about our topics, including but not limited to the Docs Initiative. (@jflory7:fedora.im, 13:10:23)
    2. LINK: https://discussion.fedoraproject.org/t/fedora-council-2026-strategy-summit-daily-briefings-summaries-tirana-albania/180535/5 (@jflory7:fedora.im, 13:10:25)
    3. LINK: https://fedoraproject.org/wiki/Council/2026_Strategy_Summit (@jflory7:fedora.im, 13:10:31)
    4. INFO: We held a workshop on Docs on CentOS connect. The most important outcome: We are launching a PoC to design Fedora Docs as upstream in specific areas. W'll start with a tutorial about "Setting up a full blown mail service" first for fedora an then for CentOS (which has some different/older versions of some parts). (@pboy:fedora.im, 13:11:22)
    5. INFO: Quick action item review from 27 January meeting (@jflory7:fedora.im, 13:14:03)
    6. LINK: https://meetbot.fedoraproject.org/meeting_matrix_fedoraproject-org/2026-01-27/docs.2026-01-27-13.06.html (@jflory7:fedora.im, 13:14:08)
    7. ACTION: @jflory7 Prepare a next meeting topic for opening up the contribution call for the Fedora Docs homepage project (@jflory7:fedora.im, 13:15:50)
    8. ACTION: @pbokoc Migrate the Fedora Docs "pages" repository from GitLab to Forgejo by the next team meeting on 24 February 2026 (@jflory7:fedora.im, 13:22:45)
    9. ACTION: @pboy Edit the Forgejo issue for the Docs homepage task to describe the "three phases" approach to this ticket. (@jflory7:fedora.im, 13:22:57)
    10. ACTION: @pboy Update Docs Team ticket about Quick Docs with today's discussion and next steps for the 24 February 2026 meeting (@jflory7:fedora.im, 13:23:13)
  3. TOPIC:Contributor documentation – how to proceed (@jflory7:fedora.im, 13:24:34)
    1. LINK: https://forge.fedoraproject.org/docs/tickets/issues/1 (@jflory7:fedora.im, 13:29:10)
    2. LINK: https://docs.fedoraproject.org/en-US/fedora-docs/contributing-docs/tools-local-authoring-env/ (@jflory7:fedora.im, 13:29:44)
    3. IDEA: @jflory7: Drop the GitLab and Pagure pages entirely. We might be stretching ourselves too thin by maintaining all of this docs. The local environment page is more helpful as a starting point. (@jflory7:fedora.im, 13:34:28)
    4. IDEA: The Fedora Join SIG has capacity and interest in helping newcomers with basic git skills. (@jflory7:fedora.im, 13:37:15)
    5. AGREED: The Fedora Docs Team agrees that providing starting points for new authors in Fedora Docs is useful. However, the Fedora Docs Team has limited capacity to maintain several different docs for several different writing workflows. The team needs to have strong opinions about what tools we recommend for working. Therefore, we will drop the GitLab and Pagure pages, refine the local authoring page to link out to other information, and later, create a new Forgejo page. (@jflory7:fedora.im, 13:48:15)
    6. INFO: @pboy will follow up with Eli to see if they want to work on Ticket #1, on improving the local authoring workflow for Fedora Docs. (@jflory7:fedora.im, 13:50:46)
    7. HALP: Interested in helping with Ticket #1, on improving the local authoring workflow for Fedora Docs? Please add a comment to the issue, and we will continue working asynchronously ahead of our next meeting. (@jflory7:fedora.im, 13:51:14)
  4. TOPIC:Quick Docs content structure – how to proceed (@jflory7:fedora.im, 13:52:00)
    1. LINK: https://pagure.io/fedora-docs/quick-docs/issue/923 (@jflory7:fedora.im, 13:52:52)
    2. LINK: https://fedoraproject.org/wiki/Initiatives/Fedora_Docs_2025#Expanded (@jflory7:fedora.im, 14:00:43)
    3. INFO: More discussion is needed about the bigger picture view for Quick Docs. There is some context in the Initiative proposal about organization, but it has not yet been moved into a ticket. (@jflory7:fedora.im, 14:02:10)
    4. ACTION: @nielsenb Add a new comment to Quick Docs #923 to audit what Quick Docs pages might fit into another Fedora Docs site or be owned by another team, and what pages still make sense to keep inside of Quick Docs. Also, consider if some pages should be retired altogether if they are no longer relevant. (@jflory7:fedora.im, 14:03:05)
  5. TOPIC:Open floor (@jflory7:fedora.im, 14:03:17)
    1. INFO: Our meeting was packed to the brim! We have no time for open floor and must yield the meeting room. (@jflory7:fedora.im, 14:03:35)
    2. ACTION: @jflory7 Post a meeting summary of today's meeting on Fedora Discussion (@jflory7:fedora.im, 14:04:14)


Meeting ended at 14:04:20 UTC

Action items

  1. @jflory7 Prepare a next meeting topic for opening up the contribution call for the Fedora Docs homepage project
  2. @pbokoc Migrate the Fedora Docs "pages" repository from GitLab to Forgejo by the next team meeting on 24 February 2026
  3. @pboy Edit the Forgejo issue for the Docs homepage task to describe the "three phases" approach to this ticket.
  4. @pboy Update Docs Team ticket about Quick Docs with today's discussion and next steps for the 24 February 2026 meeting
  5. @nielsenb Add a new comment to Quick Docs #923 to audit what Quick Docs pages might fit into another Fedora Docs site or be owned by another team, and what pages still make sense to keep inside of Quick Docs. Also, consider if some pages should be retired altogether if they are no longer relevant.
  6. @jflory7 Post a meeting summary of today's meeting on Fedora Discussion


People present (lines said)

  1. @jflory7:fedora.im (140)
  2. @pboy:fedora.im (68)
  3. @theprogram:fedora.im (17)
  4. @nielsenb:fedora.im (16)
  5. @shaunm:matrix.org (7)
  6. @zodbot:fedora.im (5)
  7. @hricky:fedora.im (4)
  8. @meetbot:fedora.im (2)
  9. @perpetrator1:matrix.org (1)