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

### Key Discussion Points

*   **Fedora Forge Usage Policy (Ticket #558):**
    *   The Council discussed the draft policy for the new Fedora Forge and the process for its approval.
    *   It was decided to publish two separate articles:
        *   A **Fedora Magazine article** to announce the sunsetting of Pagure.io and reference the *draft* usage policy. This is aimed at a broad audience and is considered urgent.
        *   A **Fedora Community Blog article** to formally begin the two-week community feedback period required by the Council's policy change process.
    *   The Magazine article will be prioritized for review and publishing to communicate the migration timeline effectively.
    *   A potential issue was raised regarding the draft policy's handling of Personally Identifiable Information (PII) in contexts like reimbursement requests and Code of Conduct reports.

*   **EU Cyber Resilience Act (CRA) Stewardship (Ticket #559):**
    *   The Council found the proposal in the ticket to be a "theory of collaboration" rather than a concrete statement of work, leading to confusion about what is being asked of them.
    *   There was significant discussion on the distinction between the Fedora Project's responsibilities and Red Hat's legal obligations as an "Open Source Steward" under the CRA.
    *   It was acknowledged that while Fedora is a community project, its legal ties to Red Hat (trademarks, infrastructure) mean that Red Hat assumes the CRA-related legal obligations.
    *   The consensus is that a more detailed proposal is needed to understand the specific changes and actions required.
    *   The Council agreed to invite the people behind the proposal to a future video meeting for a more in-depth Q&A session.

### Action Items

*   **[@jspaleta](https://matrix.to/#/@jspaleta:fedora.im):** Work with @humaton to draft a Fedora Magazine article about the Pagure.io sunset by Friday, March 13, 2026, for publishing in the week of March 16th.
*   **[@jspaleta](https://matrix.to/#/@jspaleta:fedora.im):** During the week of March 16th, work on the Community Blog article draft to officially start the community discussion on the Fedora Forge usage policy.
*   **[@jflory7](https://matrix.to/#/@jflory7:fedora.im):** Comment on Ticket #559 to summarize the Council's initial feedback, questions, and request for a more concrete proposal regarding CRA compliance.
*   **[@jflory7](https://matrix.to/#/@jflory7:fedora.im):** Propose and schedule a Fedora Council Video Meeting in March to invite the CRA team to discuss the topic with the Council and the community.
*   **All Council Members:** Add any questions related to the EU CRA to Ticket #559.