#meeting:fedoraproject.org: docs

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

Meeting summary

  1. TOPIC:Roll Call (@jflory7:fedora.im, 13:04:47)
    1. INFO: Present: @jflory7, @pboy, @nielsenb, @pbokoc, @yukih (@jflory7:fedora.im, 13:10:45)
  2. TOPIC:Agenda (@jflory7:fedora.im, 13:10:52)
    1. LINK: https://discussion.fedoraproject.org/t/docs-team-2025-kick-off-meeting-part-two-agenda-proposal/179450 (@jflory7:fedora.im, 13:10:57)
    2. INFO: 1. Improving Contributor Guidance (@jflory7:fedora.im, 13:11:57)
    3. INFO: 2. Improvement of the current local authoring tool (@jflory7:fedora.im, 13:12:11)
    4. INFO: 3. Document analyses and improvement (@jflory7:fedora.im, 13:12:15)
    5. INFO: 4. Way of collaboration (@jflory7:fedora.im, 13:12:27)
  3. TOPIC:Action items from previous meeting (@jflory7:fedora.im, 13:12:47)
    1. LINK: https://discussion.fedoraproject.org/t/fedora-docs-team-meeting-2025-12-16-first-meeting-back-initiative-overview-and-next-steps/177331 (@jflory7:fedora.im, 13:13:06)
    2. INFO: An ongoing call for help: Meeting attendees last time were encouraged to reflect on areas of passion to volunteer for in the new year. (@jflory7:fedora.im, 13:14:18)
    3. INFO: +Present: @hricky (@jflory7:fedora.im, 13:15:03)
  4. TOPIC:Improving Contributor Guidance (@jflory7:fedora.im, 13:15:18)
    1. INFO: We will not discuss topic-by-topic, but instead, review all of the topics together, and go over prioritization and allow all present meeting members ask questions about the tasks to help get involved. (@jflory7:fedora.im, 13:18:01)
  5. TOPIC:Reviewing the 2026 Docs Team priorities, identifying task/topic leads, and team Q&A (@jflory7:fedora.im, 13:18:20)
    1. INFO: Meeting Goal: We are conducting our first round of work planning for the year. Our objective is to define our key work topics and, most importantly, assign a dedicated lead (someone to wear the "hat") for each initiative. We need individuals to commit to these specific areas to ensure progress. (@jflory7:fedora.im, 13:19:51)
    2. INFO: Contributor Guidance & Tooling: We are seeking a lead to document the Forgejo editing workflow and oversee improvements to the local authoring tool. This role includes managing technical tasks such as adding ARM support to the container and enabling on-demand document rebuilding to replace full site builds. (@jflory7:fedora.im, 13:22:05)
    3. INFO: Document Analysis & Maintenance: A lead is required to conduct a comprehensive audit of Quick Docs and Administration Guides to categorize content by age and accuracy. This individual will identify priority areas for updates, determine which guides should be archived, and coordinate with maintainers to verify technical details. (@jflory7:fedora.im, 13:22:21)
    4. INFO: Collaboration Workflow: We need a coordinator to finalize our collaboration standards, specifically regarding Git branching strategies and real-time editing platforms. This task involves evaluating the trade-offs between HackMD's discussion features and the requirement for native AsciiDoc support in alternative tools like Etherpad. (@jflory7:fedora.im, 13:22:42)
    5. ACTION: @jflory7 @pboy @pbokoc Migrate the Fedora Docs Team docs site from Pagure to Forgejo in January 2026 (ideally before FOSDEM) (@jflory7:fedora.im, 13:54:48)
    6. INFO: @yukih is interested in documenting the Fedora Docs tooling and working on the contributor guidance for authors. (@jflory7:fedora.im, 13:56:19)
    7. ACTION: @nielsenb Open a new ticket on Quick Docs repo with an initial analysis of content needs, challenges, and state of affairs so we can prioritize content updates and request help from authors later in 2026. due:2026-01-27 (next Fedora Docs Team meeting) (@jflory7:fedora.im, 14:01:38)


Meeting ended at 14:02:05 UTC

Action items

  1. @jflory7 @pboy @pbokoc Migrate the Fedora Docs Team docs site from Pagure to Forgejo in January 2026 (ideally before FOSDEM)
  2. @nielsenb Open a new ticket on Quick Docs repo with an initial analysis of content needs, challenges, and state of affairs so we can prioritize content updates and request help from authors later in 2026. due:2026-01-27 (next Fedora Docs Team meeting)


People present (lines said)

  1. @jflory7:fedora.im (125)
  2. @nielsenb:fedora.im (28)
  3. @yukih:fedora.im (22)
  4. @pboy:fedora.im (18)
  5. @zodbot:fedora.im (5)
  6. @meetbot:fedora.im (3)
  7. @hricky:fedora.im (3)
  8. @pbokoc:fedora.im (3)