...

1. Danny Bernstein   
2. Andrew Woods  
3. Peter Winckles
4. Ben Cail 
5. Aaron Birkland
6. Ben Pennell
7. Bethany Seeger
8. Jared Whiklo

Agenda

1. Announcements
   1. #sprints channel 
   2. #github channel?
   3. kubernetes support in Deployment Tooling
   4. #general channel community issue
2. fcrepo-upgrade-utils
   1. Minimal 4 →5 migration needs testing  and code review:
      1. https://github.com/fcrepo4-exts/fcrepo-upgrade-utils/pull/17
3. Update on Fedora 6 Pilots (NLM, Docuteam, UWM)
   1. migration-utils PRs
4. Java 11:  When? 
5. Sprint Planning
   
   1. 6.0 Architecture Review
   2. Transaction Sidecar Spec Update
   3. OCFL community feedback on OCFL client with Database as authoritative metadata source
   4. https://github.com/pwinckles/ocfl-java-parent 
   5. Problems requiring design
      1. Tombstone Support in 6.0.0 
      2. Caching/indexing strategy 
         1. What caches and indexes do we need(ie in what layer(s)?)
            1. OCFL client 
            2. Persistence Implementation (OCFL) 
            3. Kernel Implementation
         2. Physical location of the cache (assuming we want to plan for horizontal scalability support)
            1. Cache per instance? 
               1. synchronizing changes across instance
            2. 1 Global cache/index?  
6. Your topic here...

...

1. Announcements
   
   1. sprints channel open & participants invited
   2. #github - Slack integration with github for PRs, ... - Jared will create the new #github channel.
      1. What should we do with GitHub issues?
   3. fcrepo4-docker - has kubernetes support now: Deployment Tooling
   4. #general channel - issue with simple file persistence error. Size is wrong.
      
      1. point Islandora to mysql or postgres for default configuration.
      2. look at updating documentation.
         1. The hyrax setup instructions (https://github.com/samvera/hyrax/wiki/Production-Installation-Overview)
            links to Deploying Fedora 4 Complete Guide
            which says to use https://github.com/fcrepo4/fcrepo4/blob/4.7-maintenance/fcrepo-configs/src/main/resources/config/file-simple/repository.json
            which uses the simple file system persistence approach
2. fcrepo-upgrade-utils
   1. should work for basic setups. People should try it out. Doesn't work with ACLs yet, but that's next.
3. Fedora 6 pilots
   1. OCFL client (https://github.com/pwinckles/ocfl-java-parent) - implements most of the spec.
      1. API - put/get at object level, read/update for individual files. Automatically commits (in single version) at the end of the object update changes.
      2. Doesn't handle multiple clients writing at the same time (& Go client doesn't currently support that, either).
         1. OCFL spec talks about deposit directory for staging content, but defines content at rest, not content in motion.
         2. Aaron suggested OCFL RFCs repo - implementation patterns, definitions, clarifications, ...
         3. What functionality should an OCFL client have? It should be written up.
4. Java 11
   1. Peter's code uses 11. Should make a decision at some point and switch everything.
   2. Ideal scenario:  all fedora eco-system tooling (fcrepo4, fcrepo-came-toolbox, fcrepo-import-export, fcrepo-upgrade-utils) will compile Java 11 source. 
      1. bytecode compatibility ?  Should that go to 11 as well? 
   3. Draft JVM policy re-wording https://docs.google.com/document/d/1ulXLOF2dL-vEUKhUFjkL8UG97wjXJ-9dbmytKVwzDMM/edit

   4. Current Oracle LTS is Java 11

   5. We should likely move to Java 11 this calendar year

   6. How hard is it for the community to move to Java 8

      1. Andrew to email to community list

      2. What is our plan?

         1. LTS releases: 4.7

         2. Fedora 6 to use openjdk-11

         3. needs Java 11 to run

5. Sprint planning
   1. OCFL implementations
      • OCFL Community meeting next week, Wednesday

   2. Conversation to continue on Slack

      • Request for Aaron B to document thoughts
        • Separation of concerns: what does Fedora need to know, what is internal to the OCFL client
      • Danny to update diagram (include 'deposit' space and 'versions')
   3. Transaction sidecar spec
      • https://github.com/fcrepo/fcrepo-specification-atomic-operations
      • Peter E is working on this
      • Interest in scoping transactions at the Archival-Group
   4. OCFL client with database as metadata store
      • https://wiki.duraspace.org/display/FF/Fedora+2019+Architectural+Diagrams#Fedora2019ArchitecturalDiagrams-OCFLClientwithpersistentdatabaseasauthoritativemetadatasource
        • Diagram needs to be re-worked
      • Fedora transactions will need support from underlying OCFL client
        • An OCFL client backed by a database may be able to support transactions that span multiple OCFL objects
      • Diagram details an OCFL interaction with transactions scoped to a single OCFL object
      • Todo: design how an OCFL client would support transactions over a single OCFL object
      • Todo: design how an OCFL client would support transactions over multiple OCFL objects

   5. Conversation to continue on Slack

      • Request for Aaron B to document thoughts
        • Separation of concerns: what does Fedora need to know, what is internal to the OCFL client
      • Danny to update diagram (include 'deposit' space and 'versions')

Actions

•  Danny Bernstein  will reach out to Greg about DRASTIC test results
•  Aaron Birkland  to work with Andrew Woods to get the Go client working on travis.
•  Aaron Birkland  to look explore notion of OCFL client with database as authoritative metadata source + asynchronous writing of the inventory.json file
•  Peter Eichman   and maybe Ben Pennell to make recommendations re transaction side car specification.
•   

...