#meeting:fedoraproject.org: docs

Meeting started by @jflory7:fedora.im at 13:01:37 UTC

Meeting summary

  1. TOPIC:Intros, welcomes, hellos (@jflory7:fedora.im, 13:02:19)
    1. INFO: Welcome to another Fedora Docs Team meeting! If you are present and intend to follow along with today's meeting, please identify yourself by typing `!hi` in the chat. (@jflory7:fedora.im, 13:02:34)
    2. INFO: Present: @jflory7, @pbokoc, @pboy, @nielsenb, @a-moor, @theprogram, @egret, @cstrauf (@jflory7:fedora.im, 13:05:27)
  2. TOPIC:Announcements & news (@jflory7:fedora.im, 13:06:24)
    1. INFO: Fedora Linux 44 released last Tuesday. The F43 release cycle is now concluding, and we are shifting to the F44 release cycle. This means time to focus on the next release and also participate in the next round of community elections. (@jflory7:fedora.im, 13:07:14)
    2. INFO: FYI: Nominations for Fedora Council, FESCo, Mindshare Committee, and EPEL Steering Committee all open this Wednesday, 7 May 2026. See the relevant wiki pages for opening nominations. (More to come on a Wednesday Community Blog article.) (@jflory7:fedora.im, 13:08:01)
    3. LINK: https://fedoramagazine.org/announcing-fedora-linux-44/ (@jflory7:fedora.im, 13:08:23)
    4. INFO: An official welcome to Jocelyn Gould (UTC-4) as our newest Fedora Docs Team member! 🎉 (@jflory7:fedora.im, 13:08:39)
    5. LINK: https://forge.fedoraproject.org/docs/tickets/issues/30 (@jflory7:fedora.im, 13:08:53)
    6. INFO: Meta: Sometime soon, the project board on the "Tickets" repo will be migrated to an organization-level project board in Forgejo. This means we can use the same project board across all of the Docs Team repos. (@jflory7:fedora.im, 13:10:27)
    7. LINK: https://forge.fedoraproject.org/docs/tickets/issues/33 (@jflory7:fedora.im, 13:10:27)
    8. INFO: Going forward, the correct way to triage tickets for meeting discussion will be to add an issue to the column for meeting triage. Please take note if you want to bring a topic up in one of our team meetings going forward! All Docs Team members are expected to have write access to the Project board. (@jflory7:fedora.im, 13:11:11)
  3. TOPIC:Ticket discussion (@jflory7:fedora.im, 13:15:00)
    1. LINK: https://forge.fedoraproject.org/docs/tickets/issues?labels=3655 (@jflory7:fedora.im, 13:15:35)
    2. INFO: Ticket #40: We need to put together a set of proper labels that would be applicable to every repo. What exactly do we want to track? (@jflory7:fedora.im, 13:16:31)
    3. LINK: https://forge.fedoraproject.org/docs/tickets/issues/40 (@jflory7:fedora.im, 13:16:34)
    4. INFO: Ticket #19: Outdated docsbuilder scripts (@jflory7:fedora.im, 13:16:37)
    5. LINK: https://forge.fedoraproject.org/docs/tickets/issues/19 (@jflory7:fedora.im, 13:16:40)
    6. INFO: Ticket #14: Local workflow authoring article. Ready for review/sign-off. (@jflory7:fedora.im, 13:19:23)
    7. LINK: https://forge.fedoraproject.org/docs/tickets/issues/14 (@jflory7:fedora.im, 13:19:25)
  4. TOPIC:Ticket #40: [Repo alignment] Fix labels (@jflory7:fedora.im, 13:20:12)
    1. LINK: https://forge.fedoraproject.org/docs/tickets/issues/40 (@jflory7:fedora.im, 13:20:17)
    2. LINK: https://forge.fedoraproject.org/org/docs/settings/labels (@jflory7:fedora.im, 13:22:42)
    3. AGREED: As a team, we should focus this conversation about _organization-wide issue labels_ since it impacts all repos and contributors working under the forge.fp.o/docs organization. We prefer to not get in the business of standardizing repo-level labels, as we believe individual maintainers can decide whether greater specificity is needed beyond the organization-wide labels. (@jflory7:fedora.im, 13:29:26)
    4. HALP: There is no documentation about our current label organization system. At the very least, if we do not approve new changes, we need to write up some docs for Docs Team members on how to use the org-level labels consistently. (@jflory7:fedora.im, 13:34:53)
    5. AGREED: We are putting a team vote requirement on this ticket. All team members are encouraged to share feedback in Ticket #40. On the next team meeting on 19 May 2026, we will record a final vote, ratify, and move on. Docs Team leads will also work on a clear proposal for voting on, and also writing meta docs on the proposed labeling system. (@jflory7:fedora.im, 13:40:54)
    6. ACTION: @pboy @pbokoc Write a clear proposal for issue labels and update Ticket #40 with the proposal, so it is clear to all Docs Team members what is being voted on. Do this at least 48 hours before the next Docs Team meeting on 19 May 2026. (@jflory7:fedora.im, 13:42:26)
    7. ACTION: @pbokoc Create a first-draft version of issue label howto for Fedora Docs team docs repo, prepare to share on 19 May 2026 team meeting (@jflory7:fedora.im, 13:42:56)
    8. INFO: +Present: @korora (@jflory7:fedora.im, 13:43:51)
    9. HALP: Instead of writing a new page, we have an existing page which likely could get a facelift. Yay for not duplicating ourselves! 😄 (@jflory7:fedora.im, 13:45:40)
    10. LINK: https://docs.fedoraproject.org/en-US/fedora-docs/organizational/workflow/ (@jflory7:fedora.im, 13:45:43)
  5. TOPIC:Ticket #19: Outdated docsbuilder.sh pulls Antora container w/ EOL nodejs (@jflory7:fedora.im, 13:46:51)
    1. LINK: https://forge.fedoraproject.org/docs/tickets/issues/19 (@jflory7:fedora.im, 13:46:56)
    2. LINK: https://forge.fedoraproject.org/docs/docs-template (@jflory7:fedora.im, 13:48:00)
    3. ACTION: Hristo Marinov Add a comment update on progress and next steps to Ticket #19 for updates to the Docs Template repo (@jflory7:fedora.im, 13:51:20)
  6. TOPIC:Ticket #14: Consolidate the Local Workflow Article (@jflory7:fedora.im, 13:53:24)
    1. LINK: https://forge.fedoraproject.org/docs/tickets/issues/14 (@jflory7:fedora.im, 13:53:27)
    2. LINK: https://forge.fedoraproject.org/egret/team-docs/src/commit/660af29c2442f1dced486d6d45912be54d5069d0/modules/ROOT/pages/contributing-docs/tools-edit-local-clone.adoc (@jflory7:fedora.im, 13:55:37)
    3. HALP: All Docs Team members are encouraged to review the local authoring guide that Eli Ridge and Jocelyn Gould (UTC-4) have been hard at work on. See ticket #14 for details and to find a place to share feedback. (@jflory7:fedora.im, 14:00:04)
    4. ACTION: @egret @korora Kick off a Matrix team room discussion about a deadline for Ticket #14 and what is sensible for your individual capacities (@jflory7:fedora.im, 14:02:26)
  7. TOPIC:Open floor (@jflory7:fedora.im, 14:02:34)
    1. INFO: No time today! We had a feature-packed meeting. (@jflory7:fedora.im, 14:02:42)
    2. ACTION: @jflory7 Post a meeting summary from today on Fedora Discussion (@jflory7:fedora.im, 14:03:06)


Meeting ended at 14:03:09 UTC

Action items

  1. @pboy @pbokoc Write a clear proposal for issue labels and update Ticket #40 with the proposal, so it is clear to all Docs Team members what is being voted on. Do this at least 48 hours before the next Docs Team meeting on 19 May 2026.
  2. @pbokoc Create a first-draft version of issue label howto for Fedora Docs team docs repo, prepare to share on 19 May 2026 team meeting
  3. Hristo Marinov Add a comment update on progress and next steps to Ticket #19 for updates to the Docs Template repo
  4. @egret @korora Kick off a Matrix team room discussion about a deadline for Ticket #14 and what is sensible for your individual capacities
  5. @jflory7 Post a meeting summary from today on Fedora Discussion


People present (lines said)

  1. @jflory7:fedora.im (161)
  2. @cstrauf:fedora.im (30)
  3. @egret:fedora.im (17)
  4. @pbokoc:fedora.im (16)
  5. @pboy:fedora.im (11)
  6. @zodbot:fedora.im (9)
  7. @hricky:fedora.im (5)
  8. @meetbot:fedora.im (3)
  9. @a-moor:fedora.im (3)
  10. @nielsenb:fedora.im (1)
  11. @korora:fedora.im (1)
  12. @theprogram:fedora.im (1)