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. Peter Winckles 
3. Jared Whiklo 
4. Bethany Seeger  
5. Andrew Woods 
6. Ben Pennell 
7. Aaron Birkland
8. David Wilcox  (out)
9. Peter Eichman 
10. Daniel Lamb 
11. Ben Cail
12. Thomas Bernhart

Agenda

1. Announcements
   1. 2020 Q1 Sprint Doodle: https://doodle.com/poll/es7nwdppt94rv2pz
   2. CNI Update
2. State of the development
   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.
   3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. Containment Index
3. Fedora 6 Demo
   1. What
   2. When
4. Open Questions

   1. What to do with Pair Trees?

      from last week:
      * probably not a need for it; 
      * it was a performance hack with Fedora 6 that probably should go away
      * Aaron raises question about Fedora 4 to 6 migration of pair-trees
      * three options: collapse the pair-tree, retain pair-tree as containers, or retain Fedora 4 behavior
      * is there deployed Samvera behavior that depends on pair-tree nodes?

   2. Multi-tenancy question:  Would it be possible to think about a single fedora supporting multiple storage roots?  ie one storage root maps to each top level container?

5. <>

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

Actions

• Clarify in in documentation that multiple simultaneous writes to OCFL are not supported