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://duraspace.zoom.us/my/fedora 
  
  • Dial-in: 
    +1 408 638 0968
    +1 646 876 9923
    +1 669 900 6833
    Meeting ID:
    812 835 3771

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

Attendee

1. Danny Bernstein   
2. David Wilcox
3. Bethany Seeger 
4. Andrew Woods
5. Peter Winckles

Agenda

1. Announcements
2. Fedora 5.1.0  Release  RC 3  (July 26, 2019)
3. Import Export: 5.x roundtrip is complete
   
   1. Next steps
4. Update on Fedora 6 Pilots (NLM, Docuteam, UWM)
5. migration-utils work
   1. Configure "fedora4Client" to new implementation of the Fedora4Client.java interface
   2. Writing to OCFL instead of Fedora4/5/6 API
   3. Request: Fedora3 sample data
6. Fedora 6.0.0 Sprint Planning Page
   1.  Update on Remove all JCR dependent code
   2. 6.0 Architecture Review
7. Your topic here...

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.  Folks are largely out today :  just a skeleton crew.
2. Is it worth exposing an HTTP interface to the OCFL Go client? 
   1. Advantage:  decoupled service that can be used for a variety of purposes, not just Fedora
   2. Disadvantage:  performance could suffer, especially when thinking about supporting S3 (client → http → fedora → http → ocfl → http → S3  =  lots of hops)
3. migration-utils (f3 → ocfl)  work is moving forward:  Andrew is looking for internally consistent Fedora 3 data sets for testing :  will push something up once he's able to run a successful test.
4. There is agreement on the team to merge Danny's fcrepo4  PR  that removes modeshape.

Actions

• Danny Bernstein  will reach out to Greg about DRASTIC test results
  
• Ben Pennell will review import/export tasks