#meeting:fedoraproject.org: commops

Meeting started by @jflory7:fedora.im at 14:00:41 UTC

Meeting summary

  1. TOPIC:Agenda (@jflory7:fedora.im, 14:01:01)
    1. INFO: Intros, welcomes, hellos (~5m) (@jflory7:fedora.im, 14:01:21)
    2. INFO: Team announcements & news (~5-10m) (@jflory7:fedora.im, 14:01:25)
    3. INFO: Ticket discussions (remaining time) (@jflory7:fedora.im, 14:01:29)
    4. INFO: Open floor (remaining 5-10 minutes) (@jflory7:fedora.im, 14:01:33)
  2. TOPIC:Intros, welcomes, hellos (@jflory7:fedora.im, 14:01:45)
  3. TOPIC:Team announcements & news (@jflory7:fedora.im, 14:06:19)
    1. INFO: === "End of OpenID authentication in Fedora Account System"=== (@jflory7:fedora.im, 14:06:33)
    2. LINK: https://communityblog.fedoraproject.org/end-of-openid-authentication-in-fedora-account-system/ (@jflory7:fedora.im, 14:06:42)
    3. INFO: "On the latest Fedora Infrastructure weekly meeting we decided on a date of OpenID authentication sunset. The date is 20th May 2025. The OpenID is being replaced by OpenIDConnect (OIDC) in most of the modern web and most of the Fedora infrastructure is already using OIDC as the default authentication method. OIDC offers us better security by handling both authentication and authorization. It also allows us to have more control over services that are using Fedora Account System (FAS) for authentication." (@jflory7:fedora.im, 14:06:50)
    4. INFO: === "Proposal to move Community Blog to Fedora Discussion" === (@jflory7:fedora.im, 14:07:13)
    5. LINK: https://communityblog.fedoraproject.org/proposal-to-move-community-blog-to-fedora-discussion/ (@jflory7:fedora.im, 14:07:19)
    6. INFO: See this proposal from March to migrate the Fedora Community Blog to Fedora Discussion. Although this proposal does not yet have an owner, we have not received strongly negative feedback on this proposal yet. In the coming quarter or two, this could be a good candidate project for CommOps if we find someone to be the project lead. (@jflory7:fedora.im, 14:07:25)
    7. INFO: === Flock is coming: 5-8 June 2025, Prague CZ === (@jflory7:fedora.im, 14:07:43)
    8. LINK: https://fedoraproject.org/flock/2025/ (@jflory7:fedora.im, 14:07:47)
    9. INFO: The annual Fedora contributor conference, Flock, is open for registration. The final event schedule is due very soon. We hope you could consider joining us in Prague this year if it is possible for you. If you need help with travel advice or getting to know more info about the event, join #flock:fedoraproject.org on Matrix. (@jflory7:fedora.im, 14:07:52)
    10. INFO: Present: @jflory7, @markrosenbaum, @neil, @davidct, @chris, @gonza-gertrude-agatha, @zlopez (@jflory7:fedora.im, 14:10:51)
  4. TOPIC:Ticket discussions (@jflory7:fedora.im, 14:11:14)
    1. LINK: https://gitlab.com/fedora/commops/home/-/issues/?label_name%5B%5D=meeting%20topic%20request (@jflory7:fedora.im, 14:11:22)
  5. TOPIC:#69: "Launch and maintain a new docs hub for project-wide contributor community best practices and norms" (@jflory7:fedora.im, 14:11:46)
    1. LINK: https://gitlab.com/fedora/commops/home/-/issues/69 (@jflory7:fedora.im, 14:11:50)
    2. LINK: https://gitlab.com/fedora/commops/home/-/work_items/71 (@jflory7:fedora.im, 14:25:55)
    3. INFO: +Present: @thisisyaash (@jflory7:fedora.im, 14:27:14)
    4. INFO: Created a new sub-task on issue #69 to brainstorm an implementation plan for UI/UX enhancements to the Fedora Docs Antora theme. (@jflory7:fedora.im, 14:27:52)
    5. ACTION: @chris Add a comment to task #71 with feedback on the proposed implementation plan (@jflory7:fedora.im, 14:28:09)
    6. ACTION: @chris Share task #71 with the Docs Team on Matrix in #docs:fedoraproject.org (@jflory7:fedora.im, 14:28:20)
    7. ACTION: @jflory7 Revise CommOps issue #69 into more clear asks about how to write and import other content into our docs site due:2025-04-15 (@jflory7:fedora.im, 14:33:07)
    8. ACTION: @aggraxis Comment on issue #69 about volunteering to help with content writing and editing on the knowledgebase project (@jflory7:fedora.im, 14:34:43)
  6. TOPIC:#70: "Fedora Matrix Moderation: Adding as a CommOps responsibility" (@jflory7:fedora.im, 14:35:39)
    1. LINK: https://gitlab.com/fedora/commops/home/-/issues/70 (@jflory7:fedora.im, 14:36:06)
    2. INFO: Emma [it/its] notes that the Synapse issue is impossible to address, and that the Element one is addressed by using draupnir bot in #fedora:fedoraproject.org (@jflory7:fedora.im, 14:42:26)
    3. INFO: Draupnir bot management is shared by multiple communities, so governance of this shared resource needs to be considered (@jflory7:fedora.im, 14:52:44)
  7. TOPIC:Open floor (@jflory7:fedora.im, 14:55:31)


Meeting ended at 15:01:45 UTC

Action items

  1. @chris Add a comment to task #71 with feedback on the proposed implementation plan
  2. @chris Share task #71 with the Docs Team on Matrix in #docs:fedoraproject.org
  3. @jflory7 Revise CommOps issue #69 into more clear asks about how to write and import other content into our docs site due:2025-04-15
  4. @aggraxis Comment on issue #69 about volunteering to help with content writing and editing on the knowledgebase project


People present (lines said)

  1. @jflory7:fedora.im (167)
  2. @emma:rory.gay (42)
  3. @zodbot:fedora.im (10)
  4. @davidct:fedora.im (8)
  5. @thisisyaash:fedora.im (8)
  6. @Zlopez:matrix.org (7)
  7. @aggraxis:fedora.im (6)
  8. @chris_idoko:matrix.org (5)
  9. @nhanlon:beeper.com (3)
  10. @meetbot:fedora.im (3)
  11. @myloothniel:matrix.org (2)
  12. @gonza_gertrude_agatha:matrix.org (1)
  13. @markrosenbaum:fedora.im (1)