*Note: This summary is AI-generated and has not been validated by the attendants, it may be incorrect.*

### Key Discussion Points

*   **Policy on `-epel` Suffix in Package Names (Issue #322):**
    *   The group discussed formalizing the policy for packages using the `-epel` suffix.
    *   The proposed policy is to reserve the `-epel` suffix for packages that ship subpackages missing from RHEL.
    *   Any other use of the suffix would require an exception approved by the EPEL Steering Committee (ESC).
*   **EPEL Issue Tracker Migration to Forgejo (Issue #355):**
    *   The transition from Pagure to the new Forgejo instance will happen after FOSDEM/Connect.
    *   The target timeline is the first week of February, with a follow-up at the February 4th meeting.
*   **Django Versions in EPEL:**
    *   A change proposal is pending to bring Django 6.x to EPEL 10.
    *   There is a future concern for EPEL 9, as it uses Django 4.2 (which powers Fedora's mailing list infrastructure) and its EOL is April 2026.
    *   Upgrading Django in EPEL 9 will likely require incompatible updates to its dependencies.
*   **Upcoming Meeting Cancellation:**
    *   The EPEL meeting on January 28th, 2026, will be canceled due to many members attending CentOS Connect/FOSDEM.

### Action Items

*   **`carlwgeorge`**: To create a pull request with a draft of the new policy regarding the `-epel` package name suffix. It will likely be added to the main EPEL policy page.
*   **`dherrera`**: To proceed with the migration of the EPEL issue tracker from Pagure to Forgejo after FOSDEM/Connect.
*   **`tdawson`**: To add the issue tracker migration as a topic to the agenda for the February 4th meeting to check on progress.
*   **`salimma`**: To create a COPR repository to investigate the dependencies and potential conflicts for a future Django upgrade in EPEL 9 and announce the contingency plan on the mailing list.