...

1. Danny Bernstein 
2. Jared Whiklo   
3. David Wilcox 
4. Andrew Woods 
5. Ben Pennell
6. Peter Eichman
7. Jon Roby
8. Bethany Seeger
9. Aaron Birkland
10. Yinlin Chen

Agenda

1. Announcements
   1. 2019-05 Fedora Camp Atlanta
   2. Fedora API Specification: Recommendation 1.0 release status
   3. Next week DuraSpacer's out of town
      1. Need a volunteer to lead the meeting
      OR
2. 5.0.3 and/or Fedora 5.1.0 ?
   
   1. Completed Bug fixesIn-Review:

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2991

      5.1.0 Complete

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-29352976

   2. 5.1.0 Closed

      1. 
         

         Expand
         Jira server DuraSpace JIRA jqlQuery filter=14901 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

         keyFCREPO-1889

         
         

   3. 5.1.0 Open (need to re-evaluate for inclusion in 5.1.0):
      To be done:
      

      1. Jira
         server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2976

      2. 
         

         Expand

      3. JiraserverDuraSpace JIRA

         Jira server DuraSpace JIRA

         serverIdc815ca92-fd23-34c2-8fe3-956808caf8c5keyFCREPO-2993

         jqlQuery filter=14902

         serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

         keyFCREPO-2994

         
         

      1. 5.x-maintenance branch does not currently have the above completed changes.
   4. Next Steps for Fedora 6 
      1. Java 11?
   5. Import  / Export
   6. <your discussion point here>

   Tickets

   1. In Review

      Expand
      Jira server DuraSpace JIRA jqlQuery filter=13100 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

   2. Please squash a bug!

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

   3. Tickets resolved this week:

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

   4. Tickets created this week:

      Expand
      Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

      
      

   Notes

   Announcements

   • Fedora Camp Atlanta
     
     • May 20-22 at Emory
     • Andrew, Danny, Jared as instructors
   • Open Repositories events
     • Fedora user group on Friday
     • Dinner earlier in the week
   • FMP Grant survey
     • Survey went out yesterday
     • Open to anyone to complete. About 10 minutes.

   Updates from Slack

   • #tech
     • Some questions about using JSON-LD
     • Questions around scale, ingest performance, etc.
   • #ocfl
     • Conversation around locking
       • Some suggestion that implementation notes should mention different approaches to contention in object updates, uncoordinated applications adding revisions to the same object. Maybe out of scope?
       • Some commenters thinking of scenarios analogous to those we will deal with in Fedora (e.g. many writers making simultaneous changes to an object).
       • How to build up and commit changes to an OCFL object safely. This could go in the implementation notes.
       • Dealing with locking: Fedora will need to answer this question. Less about OCFL and more about the applications built on top of OCFL. 
       • Fedora design includes caching changes until committing to an OCFL object. 
         • Changes are maintained in a deposit space until a version is explicitly created. 
       • OCFL in S3: filesystems can make certain guarantees that are impossible in S3. File paths are not really directories, no true renaming. S3 may only be safe if every client uses a single application that mediates access. 
       • Can locking be cast a a general HTTP issue rather than a Fedora-specific issue?
         • Stateless HTTP requests will need to be managed by a higher-level application
         • It would be useful to have concrete use cases
     • Oxford experimenting with Aaron Birkland's OCFL client
       • Created 250K objects and were pleased with performance

   Ready for Review

   • Jira
     server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2991

     • Most of the way through this issue
     • Test still failing in Travis but not locally
     • Null pointer exception, not clear where this is occurring
     • Andrew will try a couple builds and report back

   CNI / Leaders / Grant / ACRL Debrief

   ...

   API Spec, process

   1. Ready to release the Fedora API Specification as 1.0 Recommendation per the charter
      1. However, we want to get feedback from other implementations as well, one or more of:
         1. Derby
         2. DRASTIC
         3. Trilpy

   Next week's meeting

   1. Facilitator: Bethany

   5.0.3 and/or 5.1.0

   1. FCREPO-2991 - Cannot create resources with most identifiers containing :'s
      • Pending additional testing, Bess?
   2. FCREPO-2976 - Add Support for X-State-Token in GET and HEAD requests
      • Ready to merge
   3. Danny working on other X-State-Token tickets... today?
   4. Suggestion: release 5.1.0 once state-tokens are done
   5. 33 open tickets are targeting 5.1.0, need to review these for appropriateness
      • ACTION: Danny to take first pass to quickly remove/clean-up obvious tickets
      • Others to review as well, please complete this week
      • ACTION: Bethany to review fcrepo-2902
      • ACTION: Ben to review fcrepo-2789
      • Likely close fcrepo-2051
      • ACTION: Jared to fix Java 11 javadoc errors in a new ticket, link to fcrepo-2958
      • Where appropriate, close JIRAs and add as GitHub issues

   5.1.0 release

   1. Timeline: potentially have an RC as early as May
      • Pre-OR19

   5.x-maintenance

   1. ACTION: Danny to rename 5.x-maintenance to 5.0.x-maintenance
   2. Suggestion: release 5.1.0 off of master
      • Once released, create a 5.1.x-maintenance

   Import / Export

   1. Incremental progress on round-tripping F5
   2. Outstanding items
      • external content
      • ACLs
      • import

   ...

   • OCFL instead of ModeShape, implementing the Fedora API, adding a query API
   • Strong interest in not releasing Fedora 6.0 without migration support
   • Some interest in funding testing. 

   ...

   • Some people may not want OCFL, concerned with optimizing performance and assuming OCFL would have some negative impact

   ...

   Actions

   •  Peter Eichman  is planning to work on documenting UMD's fixity check system on the  Fedora in Production: Case Studies wiki page.
   •  Danny Bernstein will pull together some use cases for object locking in OCFL
   •  Danny Bernstein to take first pass to quickly remove/clean-up obvious tickets labeled with "fixed version" 5.1.0
   •  Bethany Seeger to review fcrepo-2902
   •  Ben Pennell  to review fcrepo-2789
   •  Jared Whiklo to fix Java 11 javadoc errors in a new ticket, link to fcrepo-2958
   •  Danny Bernstein to rename 5.x-maintenance to 5.0.x-maintenance