#meeting:fedoraproject.org: docs

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

Meeting summary

  1. TOPIC:Roll Call & Hello's (@jflory7:fedora.im, 13:04:25)
    1. INFO: Present: @jflory7, @pg-tips, @pbokoc, @hricky, @cstrauf, @klavier, @theprogram (@jflory7:fedora.im, 13:07:56)
  2. TOPIC:Team news & announcements (@jflory7:fedora.im, 13:08:14)
    1. INFO: Early in March, @jflory7 attended SCaLE 23x in Pasadena, California. I presented about the Fedora Docs community and asked attendees to role-play different parts of the Fedora Docs community. I have notes and a write-up that I need to share more widely. (@jflory7:fedora.im, 13:10:30)
    2. INFO: The Beginner's Guide was created last week, after the work @cstrauf and @theprogram put in to assemble it. (@jflory7:fedora.im, 13:11:18)
    3. LINK: https://forge.fedoraproject.org/docs/docs-beginners (@jflory7:fedora.im, 13:11:24)
  3. TOPIC:Tickets & Main Work Discussion (@jflory7:fedora.im, 13:13:33)
    1. INFO: Topic 1: New member tickets (@jflory7:fedora.im, 13:14:03)
    2. INFO: Topic 2: Beginner's Guide (@jflory7:fedora.im, 13:14:07)
    3. INFO: Topic 3: Forgejo Migration Status: Let's touch base on the pages repo migration. (@jflory7:fedora.im, 13:14:09)
    4. INFO: Topic 4: Quick Docs? (@jflory7:fedora.im, 13:14:13)
    5. INFO: Topic 5: Open Floor: Anything else top of mind. (@jflory7:fedora.im, 13:14:16)
  4. TOPIC:New member tickets (@jflory7:fedora.im, 13:14:24)
    1. LINK: https://forge.fedoraproject.org/docs/tickets/issues/23 (@jflory7:fedora.im, 13:16:45)
    2. LINK: https://forge.fedoraproject.org/docs/tickets/issues/24 (@jflory7:fedora.im, 13:16:48)
    3. LINK: https://forge.fedoraproject.org/docs/tickets/issues/25 (@jflory7:fedora.im, 13:16:50)
    4. INFO: Per the agreed rules, after seven days, the tickets can be fully approved and new members added to the FAS group. (@jflory7:fedora.im, 13:18:35)
    5. INFO: The new member nomination form seems to be working well! If you are contributing to the Fedora Docs Team already but are not formally part of the group, please take a look at the form and consider nominating yourself. (@jflory7:fedora.im, 13:19:30)
    6. INFO: +Present: @venefilyn @jonashub @egret (@jflory7:fedora.im, 13:20:11)
  5. TOPIC:Beginner's Guide (@jflory7:fedora.im, 13:21:05)
    1. INFO: Currently, the Beginner's Guide is not yet published on docs.fedoraproject.org. It is pending a review from @pbokoc before it gets added to the Antora builder repo. (@jflory7:fedora.im, 13:30:23)
    2. INFO: +Present: @pboy (@jflory7:fedora.im, 13:30:59)
    3. INFO: Beginners Guide to Fedora is uploaded to Docs in the beginners-guide repo. (@theprogram:fedora.im, 13:34:06)
    4. INFO: @theprogram: We as Docs Team agree that the language used is suitable. We agree that the guide should be linked from the from page of Fedora Docs website in order to help more people install and learn about Fedora. (@jflory7:fedora.im, 13:36:13)
    5. INFO: @theprogram: @hricky will make some suggestions, RE: styling and formatting. (@jflory7:fedora.im, 13:36:18)
    6. INFO: We as Docs SIG agree that the language used in the beginners guide is suitable. We agree that the guide should be linked from the fron page of Fedora Docs website in order to help more people install and learn about Fedora. (@theprogram:fedora.im, 13:36:20)
    7. ACTION: @hricky Share comments on Beginner's Guide content with @cstrauf and @theprogram (@jflory7:fedora.im, 13:36:23)
    8. INFO: @theprogram: SIG members and others are welcome to indicate any factual errors or ommisions. Otherwise we are ready to go live after a review from Petr Bokoc (@jflory7:fedora.im, 13:36:26)
    9. INFO: Hristo will make some suggestions for the Fedora Beginners Guide re: styling and formatting. SIG members and others are welcome to indicate any factual errors or ommisions. Otherwise we are ready to go live after a review from Petr Bokoc. (@theprogram:fedora.im, 13:37:16)
    10. HALP: Blocked on editing the front page until the "pages" repository is moved from GitLab to Forgejo? (@jflory7:fedora.im, 13:37:29)
    11. LINK: https://forge.fedoraproject.org/docs/tickets/issues/8 (@jflory7:fedora.im, 13:39:35)
    12. ACTION: @docs Add any feedback on the Beginner's Guide in the pre-publishing stage on Ticket #8 for the Docs Team or in the Matrix room, #docs:fedoraproject.org. (@jflory7:fedora.im, 13:40:26)
    13. INFO: Once the Beginner's Guide is published, Docs Team Ticket #8 will be closed, and all future bugs/requests/feedback should be added as new issues directly on the Beginner's Guide repo on Forgejo. (@jflory7:fedora.im, 13:41:31)
  6. TOPIC:Forgejo Migration Status: Let's touch base on the pages repo migration. (@jflory7:fedora.im, 13:42:40)
    1. INFO: Forge migration status: Almost all Gitlab repos are migrated, 3 unpublished repos need to either just be deleted or have their contents archived, + the UI repo needs to move but we need a forgejo runner first. @pbokoc is on it. (@pbokoc:fedora.im, 13:46:05)
    2. INFO: 20 currently published repos on Pagure still need to be migrated. There are also some old repos in Pagure that aren't currently published but should be preserved. The plan is to migrate them and immediately archive them in Forge, and either we'll pick them up later or not. (@pbokoc:fedora.im, 13:47:42)
    3. INFO: Some detective work is needed to determine if the remaining 20 repositories on Pagure.io need to be migrated, or if they even still have a maintainer. @pbokoc will investigate further after the F44 release but before Flock. (@jflory7:fedora.im, 13:52:08)
    4. INFO: QUESTION: Do we migrate archived repos to Forgejo at all? Or do we have a Fedora Docs "graveyard" for archived, unpublished content? Where should this go? More discussion is needed. (@jflory7:fedora.im, 13:52:37)
    5. INFO: We likely need a clear proposal next on what to do with older content on Pagure.io and what our plan, as Docs Team, will be ahead of the Pagure.io sunset at Flock 2026. (@jflory7:fedora.im, 13:56:57)
  7. TOPIC:Open floor (@jflory7:fedora.im, 13:57:07)
    1. INFO: Not a full consensus, but some discussion that we likely only want active, maintained docs to migrate to the forge.fedoraproject.org/docs organization. Discoverability is very important and we don't want to direct users and contributors to dead content. (@jflory7:fedora.im, 14:01:00)


Meeting ended at 14:02:58 UTC

Action items

  1. @hricky Share comments on Beginner's Guide content with @cstrauf and @theprogram
  2. @docs Add any feedback on the Beginner's Guide in the pre-publishing stage on Ticket #8 for the Docs Team or in the Matrix room, #docs:fedoraproject.org.


People present (lines said)

  1. @jflory7:fedora.im (174)
  2. @cstrauf:fedora.im (26)
  3. @pbokoc:fedora.im (25)
  4. @theprogram:fedora.im (23)
  5. @klavier:fedora.im (16)
  6. @pboy:fedora.im (13)
  7. @zodbot:fedora.im (13)
  8. @pg-tips:fedora.im (6)
  9. @venefilyn:matrix.org (5)
  10. @hricky:fedora.im (4)
  11. @egret:fedora.im (3)
  12. @jonashub:fedora.im (3)
  13. @meetbot:fedora.im (3)
  14. @ahmedalmeleh:matrix.org (1)