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/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

Attendees 

1. Danny Bernstein
2. Jared Whiklo 
3. Ben Pennell 
4. Andrew Woods
5. Peter Winckles
6. David Wilcox 
7. Ben Cail 
8. Daniel Lamb

Agenda

1. Announcements
   1. ...
2. ISLE Fedora
   1. "Official" Base Docker Image (initially 5.x) now or later:  who has the credentials for https://hub.docker.com/u/fcrepo?
      1. Docker support ticket submitted (Docker Support Ticket 00118712 - Claiming 'fcrepo' Docker Hub organization ref:_00DG0ksDa._5006f1YIR1K:ref) Feb 3. Bumped Feb 13. Bumped again Mar 10.
   2. Does it make sense to create a ISLE Fedora docker first and then extract the base image later?
3. Road to Fedora 6
   1. Milestone list
      1. Validation of completion: compare HTTP responses with that of F5
   2. Please sign up for Apr, May, more... 2020 Sprints - Fedora 6
      1. April sprint focus: Containment & Messaging
      2. May sprint focus: ACLs
4. April Sprint Planning
   1. Tickets?
   2. Success of the sprint means...
5. Clarification on: FedoraResource and identifier translation
6. Priority tasks (Development Roadmap : 2020 Sprint Roadmap)
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
7. In-flight
   1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
8. To review:
   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.
9. Tickets resolved this week...

   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.

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. Announcements
   
   1. OCFL call - demo of Stanford validator. April will be a demo for work from Australian group.
2. ISLE Fedora
   1. effort to dockerize Islandora 8 - many containers
   2. official Fedora docker container
   3. can't get access to dockerHub fcrepo account yet - see if calling on the telephone helps; try community list also
   4. plans to move forward with ISLE docker image (in Islandora organization), and extract base Fedora image to be official Fedora image
3. Road to Fedora 6
   1. Milestones
      1. could compare responses between Fedora 6 and 5, and mark item as complete if responses are the same
      2. use Fedora API testsuite to see what's done and not?
   2. sign up for April/May sprints
4. April sprint planning
   1. tickets for containment/messaging?
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2. success of sprint looks like:
      1. containment basically working - storing containment in DB, checking index, provide containment triples when accessing resource, rebuilding containment relationships, reflect child deletions in triples
         1. simple searching - would that use the containment index? or would there be multiple indexes?
         2. inbound references
         3. UI - verify that containment works
      2. messaging
         1. select message bus, wire it in, make sure messages are posted/published for create/update/delete actions
         2. turn integration tests back on
         3. when to emit messages? When transactions are committed. How to handle messages that haven't been emitted yet? Persist them before emitting?
            1. ie. what if action completes, but message isn't emitted before Fedora dies?
5. FedoraResource and identifier translation
   1. pass through path string (acl, timemap requests) directly to kernel layer? Or strip them off?
   2. try not to duplicate string identifier parsing logic - could make the identifier an object that knows the different parts of the identifier
6. Review tickets

Actions

• Clarify in in documentation that multiple simultaneous writes to OCFL are not supported
• After team has a chance to comment, send Ghost Node idea to general community for feedback
• Call Docker about fcrepo account
• Email Community list about fcrepo DockerHub account