...

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 Demian Katz 

See Rotating Schedule here 

Notes

1. Announcements
   1. Fedora 6.5.0 Release - went successfully, need to send announcement
   2. Fedora User Group Meeting - Still determining what the session will involve
2. Pop-up/Other Topics
   1. Outstanding Slack questions
      1. Issue with Fedora 3.4.2 - very old version, slow running query. Not sure what to tell them given how old it is.
      2. Fedora 4.7.5 - webapp+ authentication. We never did a 4.7.6 webapp+ release.
      3. Fedora 6 - corrupted objects in S3, says its missing header files. Some responses were left on the thread with ideas about things to check.
3. Migration Updates
   1. none
4. Updates on tickets
   
   1. fcrepo-3922 - Relates to tombstones, issue with the UI, nothing wrong with the data. Lower priority since we are going to replace the UI
   2. fcrepo-3921 - Issue with system wide java version installed, since its not running via terminal with env variables. Could we pack JVM in the jar? Do we still need to create the one-click or is the docker or jetty:run sufficient? jetty-console plugin is not maintained. Jared making a followup ticket
   3. fcrepo-3920 - Dan will take a look, readme update
   4. fcrepo-3918 - No updates. Will investigate soon. Maybe could check to see if commits are tagged, or could do daily builds. Complicated by needing both the fcrepo and fcrepo-docker repos to build.
   5. fcrepo-3917 - Dan will take this
   6. fcrepo-3910 - waiting on more info, likely april or may
   7. fcrepo-3827 - UI issue, should be very easy, but its low priority
   8. fcrepo-3912 - Thomas started, but needs to come back to it. Its a manual workflow at the moment. We will create a followup ticket for generating baseline releases automatically
   9. fcrepo-3871 - no updates
   10. fcrepo-3919 - PR posted, but initial user wasn't able to get it to work. Would be helpful to have others try it out.
   11. fcrepo-3913 - should be closed