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. Ben Pennell
5. David Wilcox 
6. Peter Eichman 
7. Daniel Lamb 
8. Ben Cail 
9. Andrew Woods
10. Michael Ritter
11. Thomas Bernhart

Agenda

1. Announcements
   1.  Sprint will start on this Monday 
      1. 7 Participants
      2. 1 week + :  Jan 27- 31
   2. Fedora 6 documentation space: Fedora 6.x Documentation
      1. Updates/Corrections would be helpful... from top to bottom!
   3. Draft Fedora 6 test plan
      1. Feedback welcome!
2. Sprint Kickoff
   1. PRs to close today or Friday:
      1. Return Identifiers from Create:  https://github.com/fcrepo4/fcrepo4/pull/1607
      2. Stage object sessions in their own directories: https://github.com/fcrepo4/fcrepo4/pull/1606 
      3. Get Resource Service: https://github.com/fcrepo4/fcrepo4/pull/1608
   2. Housekeeping to be done right away:
      

      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. Cross cutting concerns
      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   4. CRUD Binary
      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   5. CRUD RDF
      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   6. Containment
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   7. Migration Utils
      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. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      6. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      7. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      8. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      9. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
      10. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
3. Decisions and Open Questions
   1. Where do we stand regarding Identifiers?
      1. Identifiers, RDF and Import Proposal
      2. Fcrepo6 Resource Identifiers
4. Import Export Bag Profile
   
   1. Beyond The Repository grant produced a new bag profile
   2. Adding support to export and import in said profile

1. Pair tree  testing partner
2. <Your topic here>

Tickets

Full list of Fedora 6.0.0 Unclosed

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