...

1. Announcements:
   1. Upcoming Conferences
      1. iPres - late Sept in Ghent, Belgium
      2. 2024 Virtual Fedora Showcase announcement - Oct 1-3, 2024 online
      3. Access 2024 - late October in Montreal, QC
2. Pop-up/Other Topics:
   1. ACL issues – any updates since last week?
   2. Slack Issue from Islandora - https://islandora.slack.com/archives/C019U12D44Q/p1720699950434699
      1. Any updates?

   3. https://groups.google.com/g/fedora-tech/c/TowKXMNdAkQ (S3) 

   4. https://groups.google.com/g/fedora-tech/c/3IXH5g0QtKU (committing parallel transaction) 

3. Migration Updates:
4. Updates on:

...

See Rotating Schedule here 

Notes

1. Announcements:
   1. 2024 Virtual Fedora Showcase - https://forms.gle/ahLv6bh3SJYorm1M8
   2. Governance nominations and voting is now open. There are not believed to be any community seats available at this time
2. Pop-up/Other Topics:
   1. ACL issues – Dan updated the meeting on the issue as seen by David Novak related to ACLs populating the membership/containment after reindexing
   2. Slack Issue from Islandora - https://islandora.slack.com/archives/C019U12D44Q/p1720699950434699
      1. Dan discussed this further with Rosie after last weeks meeting and was unable to replicate the issue on stock Fedora. She added that this was not a big issue for her. It appears to be an implementation issue rather than a bug but Dan will confirm

   3. https://groups.google.com/g/fedora-tech/c/TowKXMNdAkQ (S3)

      1. Thomas confirmed that their S3 testing has seen good performance improvements and is keen to hear from any other users

      2. Demian asked whether this will be in the next version and we discussed which tickets will form the next release. Demian suggested that we use the Kira release feature to take tickets for a particular release. Documentation is also   

   4. https://groups.google.com/g/fedora-tech/c/3IXH5g0QtKU (committing parallel transaction) 

      1. 1. No-one had a definite answer to Docuteams question on parallel transactions. Jared had stated in a previous meeting that additional logging would be useful to help learn more about what is happing internally. Peter Winkles may have more information on how this works? 
         2. Code review of unknown areas of 
3. Migration Updates:
4. Updates on:

REMINDER: Need to put tickets in meeting notes to ensure we don't lose information from dynamic filters.

1. 1. Open Tickets (but assigned in some cases): 
      
      
   2.  In Progress and older but still relevant open tickets:
       
   3. In Review:
      
      
   4. Recently closed tickets:  "closed" within "the last 2 weeks"

1. Backlog Tickets to consider working:
2. Next Meeting Chair:  
   1. Chair: Ben Pennell 
   2. Note Taker: Demian Katz