#meeting:fedoraproject.org: council

Meeting started by @jflory7:fedora.im at 15:01:41 UTC

Meeting summary

  1. TOPIC:Intros, welcomes, hellos (@jflory7:fedora.im, 15:02:08)
    1. INFO: Welcome to another Fedora Council meeting! If you are present and intend to follow along with today's meeting, please identify yourself by typing `!hi` in the chat. Council members in attendance will have their attendance noted before moving to the agenda. (@jflory7:fedora.im, 15:02:13)
    2. INFO: Council members present: @jflory7, @t0xic0der, @nimbinatus, @jonatoni, @dcantrell, @pboy, @churchyard, @jspaleta (@jflory7:fedora.im, 15:04:46)
  2. TOPIC:Meeting Agenda (@jflory7:fedora.im, 15:05:03)
    1. LINK: https://fedoraproject.org/wiki/Council_Meetings#Next_Meeting_Agenda (@jflory7:fedora.im, 15:05:07)
  3. TOPIC:#555: Council Strategy Summit 2026 – 2-6 February 2026 – Tirana, Albania (@jflory7:fedora.im, 15:05:43)
    1. LINK: https://pagure.io/Fedora-Council/tickets/issue/555 (@jflory7:fedora.im, 15:05:55)
    2. LINK: https://fedoraproject.org/wiki/Council/2026_Strategy_Summit#Schedule (@jflory7:fedora.im, 15:09:10)
    3. INFO: The hotel for the Council Strategy Summit is the Tirana Marriott. All Red Hat employees should have a booking made in Egencia for the days of travel. Non-Red Hatters must work with Justin on the hotel arrangements. (@jflory7:fedora.im, 15:13:47)
    4. INFO: Remote participation will be prioritized this year. Remote participants are encouraged to put their time zone availability on the Fedora Wiki page to prioritize remote engagement times. (@jflory7:fedora.im, 15:14:19)
    5. INFO: All airfare should be booked by now. Work with Justin if you have not yet booked roundtrip travel to Tirana. (@jflory7:fedora.im, 15:14:49)
    6. HALP: @dcantrell and @jspaleta to collaborate on the Flatpak/Flathub topic priorities for Council Strategy Summit (@jflory7:fedora.im, 15:16:01)
    7. HALP: @bookwar and @jspaleta to discuss more about Konflux and git forge integration for Council Strategy Summit (@jflory7:fedora.im, 15:16:18)
    8. ACTION: @jflory7 Work with @bookwar to confirm travel/airfare plans (@jflory7:fedora.im, 15:16:47)
  4. TOPIC:#452 Proposal: Mailing list retirement plan (@jflory7:fedora.im, 15:19:15)
    1. LINK: https://pagure.io/Fedora-Council/tickets/issue/452 (@jflory7:fedora.im, 15:19:25)
    2. LINK: https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-452-proposal-mailing-list-retirement-plan/82079/21 (@jflory7:fedora.im, 15:19:45)
    3. ACTION: @council Review Ticket #452 proposal and add comments/thoughts to help drive this ticket discussion to a close on mailing list retirement/archival (@jflory7:fedora.im, 15:22:01)
    4. LINK: https://fedoraproject.org/wiki/Council/2026_Strategy_Summit#2._Initiatives_&_Engagement_Metrics (@jflory7:fedora.im, 15:25:40)
    5. INFO: The topic of how to measure contributions and whether someone is a contributor came up, which is a much larger topic than just about archiving old mailing lists. We expect intense discussion around measuring engagement in a few weeks during the Fedora Council Strategy Summit! (@jflory7:fedora.im, 15:29:46)
    6. INFO: For now, the main priority for this ticket is identifying an Infrastructure SOP/policy that we can "handover" to the likes of Fedora Infrastructure & Red Hat Community Linux Engineering to implement. (@jflory7:fedora.im, 15:30:20)
  5. TOPIC:#557: Guidance necessary: Join SIG and temporary memberships for the sole purpose of voting in FESCo election (@jflory7:fedora.im, 15:30:41)
    1. LINK: https://pagure.io/Fedora-Council/tickets/issue/557 (@jflory7:fedora.im, 15:30:49)
    2. LINK: https://discussion.fedoraproject.org/t/fedora-council-tickets-ticket-557-guidance-necessary-join-sig-and-temporary-memberships-for-the-sole-purpose-of-voting-in-fesco-election/179126 (@jflory7:fedora.im, 15:30:58)
    3. ACTION: @bookwar Reply to Ticket #557 Fedora Discussion topic with feedback on formal rules for elections and the culture we promote through the Join SIG and other initiatives (@jflory7:fedora.im, 15:58:14)
    4. ACTION: @t0xic0der Reply to Ticket #557 Fedora Discussion topic with a perspective as Contributor Recognition lead from the Mindshare Committee (@jflory7:fedora.im, 15:58:34)
    5. ACTION: @jspaleta Reply to Ticket #557 Fedora Discussion topic with how participation is possible with old, dormant accounts and potential for election system abuse (@jflory7:fedora.im, 15:58:56)
    6. ACTION: @council Reply to Ticket #557 Fedora Discussion topic with other points of feedback and discussion (@jflory7:fedora.im, 15:59:12)
  6. TOPIC:Open floor (@jflory7:fedora.im, 15:59:27)
    1. INFO: Flock 2026 CfP open now until Feb 2nd 2026: "Apply now for the Flock to Fedora 2026 Call for Proposals (CfP) at cfp.fedoraproject.org. This year, the submission deadline for the Flock CfP is Monday, February 2nd, 2026." (@jflory7:fedora.im, 16:00:07)
    2. LINK: https://fedoramagazine.org/flock-2026-cfp-open-now-until-feb-2nd-2026/ (@jflory7:fedora.im, 16:00:09)
    3. ACTION: @t0xic0der Follow-up on progress on Ticket #550 and request for feedback to the Fedora Council on the existing draft (@jflory7:fedora.im, 16:01:02)


Meeting ended at 16:01:25 UTC

Action items

  1. @jflory7 Work with @bookwar to confirm travel/airfare plans
  2. @council Review Ticket #452 proposal and add comments/thoughts to help drive this ticket discussion to a close on mailing list retirement/archival
  3. @bookwar Reply to Ticket #557 Fedora Discussion topic with feedback on formal rules for elections and the culture we promote through the Join SIG and other initiatives
  4. @t0xic0der Reply to Ticket #557 Fedora Discussion topic with a perspective as Contributor Recognition lead from the Mindshare Committee
  5. @jspaleta Reply to Ticket #557 Fedora Discussion topic with how participation is possible with old, dormant accounts and potential for election system abuse
  6. @council Reply to Ticket #557 Fedora Discussion topic with other points of feedback and discussion
  7. @t0xic0der Follow-up on progress on Ticket #550 and request for feedback to the Fedora Council on the existing draft


People present (lines said)

  1. @jflory7:fedora.im (175)
  2. @nimbinatus:matrix.org (32)
  3. @t0xic0der:fedora.im (29)
  4. @bookwar:fedora.im (25)
  5. @jspaleta:fedora.im (19)
  6. @pboy:fedora.im (10)
  7. @churchyard:fedora.im (10)
  8. @dcantrell:fedora.im (10)
  9. @zodbot:fedora.im (9)
  10. @meetbot:fedora.im (3)
  11. @jonatoni:fedora.im (3)