...

See Rotating Schedule here 

Notes

1. Announcements:
   1. Paid Slack is coming! (This will beat the August 26 deadline for retaining historical data).
   2. NLW and UNC need to register their instances on the Fedora website (Dan and Ben will investigate).
2. Pop-up/Other Topics:
   1. Slack issue - issues adjusting Content-Location for external binary
      1. Calvin is still working on this following Dan's comments; getting some weird responses from the API when updating external content (trying to set up redirect to external content in S3). "Invalid interaction model" errors in many cases. Sometimes the Content-Location data seems to disappear after updates. (This is happening in Fedora 6 with data migrated from Fedora 3). Dan and Calvin will continue to collaborate on this via Slack. Ben suggested testing whether this issue is isolated to S3 URLs or impacts all URLs; Calvin will try this next.
   2. Slack issue - issues adding custom ACLs to root, maybe caused by multiple acl:accessTo instances pointing at the same resource
      1. Status of issue is unclear; Arran will follow up to check on status.
   3. Slack issue from Islandora (from Rosie)
      
      1. Dan hasn't followed up yet, but this can be safely dropped from the agenda for next time.
   4. S3
      1. Question here: when is the next Fedora release, and what is in it? That should be a separate agenda item.
   5. Committing parallel transactions
      1. Thomas proposed scheduling a code review after he gets back from holiday in mid-to-late August (he'll add it to the agenda when ready). Demian is willing to facilitate.
3. Migration Updates:
   1. NLW migration is back underway; hoping to complete production migration by the 30th of September.
4. Updates on:
   1. Open tickets
      
      1. None this week
   2. In progress and older but still relevant open tickets
      1. FCREPO-3931
         1. No progress this week. Dan would appreciate assistance from others on this; may close this issue and open a separate one since the issue at hand is not directly related to the original issue.
   3. In review
      1. FCREPO-3950
         1. Already merged; Ben will close.
      2. FCREPO-3948
         1. Arran is willing to help with testing PRs like this one. (Running tests may be another way newer committers could contribute to reviews even if they're not yet comfortable with actually merging anything). Dan suggests that the nature of the testing may vary significantly from case to case, but having more testing doesn't hurt. Demian suggested that a triage approach could be taken – if more expert devs think testing would help but don't have time to work through it right away, they could assign PRs to others.
         2. This also led to some discussion about communication; would Slack notifications of updates/PRs/etc. be helpful? Are JIRA notifications failing to reach people who need them? (This ticket may be sitting idle because the creator hasn't checked back on it recently, which may in part be related to communication failures).
         3. Ben will review this later today and Arran will reach out to Tom for testing support.
      3. FCREPO-3939
         1. This is Jared's; he's out today.
      4. FCREPO-3935
         1. Next step: adding documentation about potential security/exposure risks.
         2. Emily should test to make sure it meets needs (Arran will facilitate if necessary).
         3. Ben will try to review today.
      5. FCREPO-3923
         1. Dan will work on this this week.
         2. Removal of one-click download link was already completed as part of the new website; no further action needed on that point.
      6. FCREPO-3919
         1. Dan has made some recent progress on this. Might be best to wait for Jared to return and confirm that his suggestions are fully incorporated.
      7. FCREPO-3917
         1. This belongs to Thomas, and he will be on holiday for the next couple of weeks. Dan has an open PR on this one with feedback from Jared. Dan will act on review as time permits.
      8. FCREPO-3912
         1. Dan has begun looking into this but had a question: fcrepo Docker repo has a GitHub action to deploy to DockerHub, but this same script is referenced in the main fcrepo action (yet the script doesn't exist in that repo). See reference to ./build-and-push-to-dockerhub.sh at end of https://github.com/fcrepo/fcrepo/blob/main/.github/workflows/build.yml for details. Here is the actual script: https://github.com/fcrepo-exts/fcrepo-docker/blob/main/build-and-push-to-dockerhub.sh, which is also being called from https://github.com/fcrepo-exts/fcrepo-docker/blob/main/.github/workflows/rebuild-latest-stable-image.yml. SOLUTION: Ben pointed out that the main GitHub Action is fetching the fcrepo-docker repository; this is how it is able to call the script.
5. Backlog Tickets to consider working:
   1. None this week.
6. Other:
   1. For week after next (since many people are out next week): talk about what goes into Fedora 6.5.1.
   Next Meeting Chair:  
7. Chair:
Note Taker: