*Note: This summary is AI-generated but has been validated by at least one of the attendants.*

### Key Discussion Points

*   **F44 Council Interview Questions (#565)**
    *   There is a consensus that the current interview questions are stale and too numerous.
    *   The Council agrees with FESCo's approach of using fewer (e.g., three) more critical questions.
    *   The plan is to collaborate asynchronously on a Google Doc to revise the questions, with a deadline of May 19th for feedback. A final vote will occur at the May 20th meeting.

*   **Fedora AI Developer Desktop Initiative (#562)**
    *   The initiative, led by Gordon Messmer, aims to create an atomic desktop system with out-of-the-box support for AI/ML applications.
    *   There was a brief discussion on naming ("AI" vs. "Machine Learning"), but it was decided not to let this block the proposal.
    *   Concerns about using an LTS kernel were noted, but alternative hardware enablement paths are also being explored.
    *   The Council voted `+6/0/-0` to approve the proposal as a 12-month Initiative, sponsored by Jef Spaleta.
    *   Due to the sensitive nature of the topic and absent members, the vote will be finalized on Friday, May 8th, based on lazy consensus (i.e., if no `-1` votes are received in the ticket by then).

*   **Fedora Innovation Lifecycle Policy (#564)**
    *   Jef Spaleta is preparing a formal policy draft based on the "Fedora Innovation Lifecycle" concept.
    *   A key aspect of the draft is that projects in the "Sandbox" stage would receive time-limited permission to use Fedora trademarks.
    *   Feedback was given that the draft needs more clarity on how infrastructure support is requested and provided for projects in this lifecycle.
    *   A public draft will be shared for community discussion before the formal two-week policy change process begins.

*   **Provenpackager Revocation Discussion Summary (#563)**
    *   A request was made to publish a summary of a past FESCo private discussion regarding a provenpackager revocation, including the individual voting records.
    *   The requester feels this is necessary for voters to make informed decisions in FESCo elections.
    *   Concerns were raised about reopening old wounds and the precedent of releasing private, people-related votes after the fact.
    *   The Council ran out of time and will hold a separate, high-bandwidth internal meeting to discuss the sensitive request before responding in the ticket.

### Action Items

*   **@t0xic0der**: Create a Google Doc with the Council interview questions and share with all Council members for edits.
*   **@t0xic0der**: Send an email to the `council-private` list with the Google Docs link, prompting Council members for feedback.
*   **@jflory7**: Update Ticket #562 with the meeting discussion and change the due date on the issue to Friday, May 8th.
*   **@jflory7**: If no -1 votes are cast 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 the Council on the `council-private` list for early feedback before moving ahead to the public Policy Change Policy process.
*   **@jflory7**: Schedule an internal Council video call to discuss the sensitive ticket (#563) in high bandwidth and relay the outcomes of that discussion into the public ticket.
*   **@jflory7**: Post the meeting summary on Fedora Discussion.
*   **@jflory7**: Update all relevant tickets with comments based on the meeting discussion.