===================================== # #meeting:fedoraproject.org: council ===================================== Meeting started by @jflory7:fedora.im at 2026-05-06 14:01:38 Meeting summary --------------- * TOPIC: Intros, welcomes, hellos (@jflory7:fedora.im, 14:02:25) * 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, 14:02:32) * INFO: Council members present: @jflory7, @dcantrell, @t0xic0der, @churchyard, @pbokoc, @jspaleta (@jflory7:fedora.im, 14:06:02) * TOPIC: Meeting Agenda (@jflory7:fedora.im, 14:06:09) * LINK: https://fedoraproject.org/wiki/Council_Meetings#Next_Meeting_Agenda (@jflory7:fedora.im, 14:06:13) * LINK: https://forge.fedoraproject.org/council/-/projects/2 (@jflory7:fedora.im, 14:06:22) * TOPIC: #565: F44 Council Interview Questions (due: 21 May 2026) (@jflory7:fedora.im, 14:07:55) * LINK: https://forge.fedoraproject.org/council/tickets/issues/565 (@jflory7:fedora.im, 14:08:00) * ACTION: @t0xic0der Create a Google Doc with the Council interview questions and share with all Council members for edits (@jflory7:fedora.im, 14:11:34) * ACTION: @t0xic0der Send a mail to council-private@lists.fp.o with the Google Docs link when ready, prompt Council members to weigh in and provide feedback (@jflory7:fedora.im, 14:11:57) * AGREED: Deadline for feedback is by 19 May 2026, preceding the next Council meeting. On the 20 May 2026 meeting, we take a formal ticket-driven vote. (@jflory7:fedora.im, 14:12:26) * IDEA: We have too many questions and they also feel too abstract/outdated. Suggested to narrow it down to three critical questions. (@jflory7:fedora.im, 14:12:42) * IDEA: @jspaleta suggests we all make votes for our top three questions and see what has the most appeal to the whole Council (@jflory7:fedora.im, 14:13:07) * INFO: We will table this topic until the next meeting but ask all Fedora Council members to provide async feedback on Ticket #565 (@jflory7:fedora.im, 14:13:34) * INFO: +Present: @pboy (@jflory7:fedora.im, 14:14:07) * TOPIC: #562: Community Initiative Proposal: Fedora AI Developer Desktop Initiative (@jflory7:fedora.im, 14:14:32) * LINK: https://forge.fedoraproject.org/council/tickets/issues/562 (@jflory7:fedora.im, 14:14:40) * IDEA: Address Justin Forbes' LTS kernel feedback specifically in the Fedora Wiki proposal for the Initiative (@jflory7:fedora.im, 14:30:45) * AGREED: `+6`/`0`/`-0` — The Fedora Council approves the AI Developer Desktop Initiative as a 12-month Initiative, led by @gordonmessmer and sponsored by @jspaleta. On the basis of our documented lazy consensus voting model, the decision will be ratified and final by Friday, 8 May in the ticket. (@jflory7:fedora.im, 14:40:59) * ACTION: Update Ticket #562 with the meeting discussion, change due date on issue to Friday, 8 May (@jflory7:fedora.im, 14:41:28) * ACTION: @jflory7 Update Ticket #562 with the meeting discussion, change due date on issue to Friday, 8 May (@jflory7:fedora.im, 14:41:44) * ACTION: @jflory7 If no -1 votes by Friday, onboard Gordon Messmer as a new Fedora Council member next week (@jflory7:fedora.im, 14:42:10) * ACTION: @gordonmessmer @jspaleta Create a recurring 1:1 meeting to discuss Initiative progress as Executive Sponsor/Initiative Lead (@jflory7:fedora.im, 14:42:40) * TOPIC: Ticket #564: Adopt Fedora Innovation Lifecycle as Council Policy (@jflory7:fedora.im, 14:43:59) * LINK: https://forge.fedoraproject.org/council/tickets/issues/564 (@jflory7:fedora.im, 14:44:07) * LINK: https://fedoraproject.org/wiki/User:Jspaleta/Drafts/FedoraInnovationLifecycle (@jflory7:fedora.im, 14:45:12) * INFO: For Entry phase: "Inclusion into the Sandbox stage explicitly confers a time-limited use of the Fedora trademarks during participation in sandbox and curation stages. On exit from the lifecycle via an alternative pathway, it is expected that the technology team will need to transition to standard Fedora Remix branding guidance, unless Council grants continued trademark use under its authority via a separate trademark usage proposal request." (@jflory7:fedora.im, 14:47:12) * HALP: Proposal appears to miss any gating/pre-reqs for how to request infrastructure, or who is on the hook for providing that infrastructure. (At least, in the Review phase, since it mentions Fedora Infrastructure being provided but not how someone gets it or what they are supposed to get) (@jflory7:fedora.im, 14:48:55) * INFO: @jspaleta is working on a public Fedora Project policy draft to share before Red Hat Summit next week. (@jflory7:fedora.im, 14:52:53) * INFO: Note that until the Policy Change Policy is initiated, this is only for discussion and nothing is being decided… yet. (@jflory7:fedora.im, 14:53:12) * ACTION: @jspaleta Share the Sandbox policy draft with Council on council-private@lists.fp.o for a round of Council early feedback/editing before moving ahead to the public Policy Change Policy process. (@jflory7:fedora.im, 14:53:42) * TOPIC: Ticket #563: public ticket with a summary of the provenpackager revocation discussion (@jflory7:fedora.im, 14:54:15) * LINK: https://forge.fedoraproject.org/council/tickets/issues/563 (@jflory7:fedora.im, 14:54:20) * LINK: https://forge.fedoraproject.org/council/tickets/issues/513 (@jflory7:fedora.im, 14:57:23) * INFO: The original request remains for a desire to know the FESCo voting record on the provenpackager incident. The Council needs to discuss further, but we ran out of time to discuss further today. (@jflory7:fedora.im, 15:03:19) * ACTION: @jflory7 Schedule an internal Council video call to discuss this sensitive ticket in high bandwidth, relay outcomes of that discussion into the public ticket (@jflory7:fedora.im, 15:03:44) * TOPIC: Open floor (@jflory7:fedora.im, 15:04:29) * INFO: Over time today! We must yield the meeting room. (@jflory7:fedora.im, 15:04:37) * ACTION: @jflory7 Post meeting summary on Fedora Discussion (@jflory7:fedora.im, 15:05:00) * ACTION: @jflory7 Update tickets with comments based on meeting discussion today (@jflory7:fedora.im, 15:05:12) Meeting ended at 2026-05-06 15:05:14 Action items ------------ * @t0xic0der Create a Google Doc with the Council interview questions and share with all Council members for edits * @t0xic0der Send a mail to council-private@lists.fp.o with the Google Docs link when ready, prompt Council members to weigh in and provide feedback * Update Ticket #562 with the meeting discussion, change due date on issue to Friday, 8 May * @jflory7 Update Ticket #562 with the meeting discussion, change due date on issue to Friday, 8 May * @jflory7 If no -1 votes by Friday, onboard Gordon Messmer as a new Fedora Council member next week * @gordonmessmer @jspaleta Create a recurring 1:1 meeting to discuss Initiative progress as Executive Sponsor/Initiative Lead * @jspaleta Share the Sandbox policy draft with Council on council-private@lists.fp.o for a round of Council early feedback/editing before moving ahead to the public Policy Change Policy process. * @jflory7 Schedule an internal Council video call to discuss this sensitive ticket in high bandwidth, relay outcomes of that discussion into the public ticket * @jflory7 Post meeting summary on Fedora Discussion * @jflory7 Update tickets with comments based on meeting discussion today People Present (lines said) --------------------------- * @jflory7:fedora.im (152) * @t0xic0der:fedora.im (24) * @jspaleta:fedora.im (18) * @churchyard:fedora.im (16) * @gordonmessmer:fedora.im (11) * @zodbot:fedora.im (8) * @dcantrell:fedora.im (4) * @meetbot:fedora.im (3) * @eseyman:fedora.im (3) * @pbokoc:fedora.im (2) * @pboy:fedora.im (2) * @decathorpe:fedora.im (1) * @mattdm:fedora.im (1)