...

1. Danny Bernstein  
2. Arran Griffith   
3. Jared Whiklo  
4. Peter Winckles 
5. Ben Pennell 
6. Calvin Xu 
7. Michael Ritter 
8. ?Demian Katz 

Agenda

1. Announcements
2. NLM Migration Update
   

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

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

3. New Tickets:

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

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

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

4. 6.2.0 Release Update
   1. Stats PR: https://github.com/fcrepo/fcrepo/pull/1974
   2. https://github.com/fcrepo/fcrepo/pull/1969 : looks like a flyway issue
      1. If this one is included it is a breaking change
   3. Documentation? 
      1. Stats page
   4. Volunteer Release Manager?
5. Fedora S3 Video
6. Community Engagement Meeting Highlights
7. Jira, Slack, Github integrations

Notes:

1. Danny thinks he's moving on to....Palace
2. Document the number of inodes needed in Fedora 6, perhaps a comparison (ie. multiplication factor) against Fedora 3, 4 & 5. Mike Ritter was using BtreeFS, but you could try XFS.
3. Some new tickets to work on
4. 6.2.0 update
   1. Stats PR review has been updated. Some question about whether to include data that is already accessible from the simple search.
   2. If we need to have the repository reindexed due to internal changes is that a major change? It will require time without the repository being fully accessible.
   3. Jared volunteered to help Danny with the 6.2.0 release
5. New video of Fedora with S3
   1. Suggestions for community engagement videos, maybe stats, JMS configuration for message durability (ie. setting up an external broker and bridging Fedora to it).
6. Finding ways to meet potential users where they are