...

Agenda

1. Announcements:
   1. Fedora 6.5.0 Release
   2. Fedora User Group Meeting - Thurs. June 6th (1-5pm local time in Sweden)
      1. Taking place at OR venue
2. Pop-up/Other Topics:
   1. Outstanding Slack questions:
      1. https://fedora-project.slack.com/archives/C8B5TSR4J/p1709537943529519
      2. https://fedora-project.slack.com/archives/C8B5TSR4J/p1709234814995839
      3. https://fedora-project.slack.com/archives/C8B5TSR4J/p1709624865949649
3. Migration Updates:

4. Updates on:

   1. Open Tickets (but assigned in some cases): 
      

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3922

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3921

         - this is possibly a local machine issue and not something we can resolve, but maybe we need to add that to documentation somewhere...?

      3. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3920

      4. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3918

      5. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3917

      6. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3910

      7. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3897

         - adding this back as HTML UI facelift wasn't prioritized in the tech survey
   2.  In Progress and older but still relevant open tickets:

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3912

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3871

   3. In Review:

      1. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3919

      2. Jira
         server Fedora JIRA serverId 1fe6d535-c432-380f-b5c0-a7d3b2940ea4 key FCREPO-3913

5. New tickets:

   1. Not new tickets per se, but maybe there is an opportunity to start looking as a group into some of the performance testing work? I'll leave this up to Dan Field
6. Backlog Tickets to consider working:
7. Next Meeting Chair: (We've been off schedule, so we'll just try and reset here)
   1. Chair: Jared Whiklo
   2. Note Taker: Ben Pennell

...