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/88068382811
  
  • Meeting ID: 880 6838 2811
  • 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. Arran Griffith  
3. Jared Whiklo 
4. Peter Winckles 
5. Ben Pennell 
6. Calvin Xu  
7. Michael Ritter 
8. Demian Katz  (out)
9. Thomas Bernhart 

Agenda

1. Announcements
2. Open House Debrief
3. Open PRs
   1. https://github.com/fcrepo/fcrepo/pull/1975
   2. https://github.com/fcrepo/fcrepo/pull/1974
   3. https://github.com/fcrepo/fcrepo-storage-ocfl/pull/50
   4. https://github.com/fcrepo/fcrepo/pull/1968
4. Tickets
   1. FCREPO-3800 - Getting issue details... STATUS
   2. FCREPO-3806 - Getting issue details... STATUS
   3. FCREPO-3807 - Getting issue details... STATUS
   4. FCREPO-3808 - Getting issue details... STATUS
   5. FCREPO-3781 - Getting issue details... STATUS
5. Other topics?
   1. camel tool box 6.1 error on start up and null credential error 

Notes:

1. Fedora open house was a success
2. Open PRS
   1. 1975: the metadata version seems to be shared now, there should be an download button
   2. 1974: need to be merged and provide feedback
   3. storage-ocfl/pull/50 Mike will take a look
3. TIckets:
   1. FCREPO-3800: should be high priority, suggest different type of lock mechanism for adding concurrent child to single parent during separate transaction
   2. FCREPO-3806, FCREPO-3807,FCREPO-3808 are cameltool box related ticket for improvement on camel toolbox fixity timestamp, allow csv output for fixity result in camel toolbox so its more readable and not in log xml format; and allow push fixity result to S3
   3. FCREPO-3781: dropping custom service jars to extend Camel Toolbox, provide way to able to pull in packages, security concerns for integration testing?
      1. extension testing should not fall under responsibility of camel toolbox application itself
      2. provide recommended strategy 
4. other topics:
   1. camel toolbox 6.1 null credential error on reindex