Time/Place

This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Audio/Video Conference Link: https://lyrasis.zoom.us/j/396037251
  
  • Meeting ID: 396 037 251
  • Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia

  • Join fedora-project.slack.com on the "tech" channel

  • Self-register at: http://slack.fcrepo.org/

Attendees 

1. Danny Bernstein
2. David Wilcox 
3. Jared Whiklo 
4. Peter Winckles
5. Daniel Lamb 
6. Ben Pennell 
7. Thomas Bernhart 
8. Mike Ritter 

Agenda

1. Announcements
   1. Steering update
2. Camel toolbox sprint
   1. 2021-10 Camel Toolbox Sprint 
   2. Availability
   3. Design : Decoupling Camel ToolBox from Karaf
   4. Tasks
3. fcrepo-migration-validator update
   1. Fedora Migration Validation Tool Status page.
4. Pilots / Testing
   1. UTA
5. Pre release short list of bug fixes and improvements
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
6. Any new tickets/issues critical to the release
   1. Connection Pool move to Hikari
   2.   Unable to locate Jira server for this macro. It may be due to Application Link configuration.
7. Your topic

Tickets

1. In Review

   Click here to expand...

   type	key	summary	assignee	reporter	priority	status	resolution	created	updated	due
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

2. Please squash a bug!

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

3. Tickets resolved this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

4. Tickets created this week:

   Click here to expand...

   key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution
   Unable to locate Jira server for this macro. It may be due to Application Link configuration.

Notes

1. Steering call on Tues. Nothing to report.
2. Can Fedora store an arbitrarily large graph?
   1. In theory it should work. Need to test it
   2. Single-subject restriction is gone
3. Camel toolbox
   1. Get java client updated
   2. Pull out osgi related files
   3. First step getting it out of karaf and into spring and worry about configuration later
   4. The blueprints could be changed to spring java config
   5. For against Spring Boot?
      1. Boot provides a lot of integrations for free (health checks, monitoring, etc)
      2. How much stuff do we actually need? More simple without?
      3. Does it need an HTTP interface?
   6. Sprint scheduled for last week of April
4. Migration validator is alpha
5. No news from University of Texas - Austin
6. Danny working on updating search index
7. Should Fedora 3 objects always be migrated to archival groups?
   1. Archival groups do not model the on disk representation the same as Fedora 3.
   2. Archival groups do allow resources to be versioned together and for all of the resources to be grouped together on disk
      1. How much do people care about this?
   3. When a resource within an archival group is modified, it locks the entire AG to that transaction, which would not happen if the resources were not in an AG
   4. Archival groups will likely have more versions than an average resource because they are versioned every time any resource they contain is modified.

Actions