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/j/396037251
  
  • Meeting ID: 396 037 251
  • Find your local number: https://lyrasis.zoom.us/u/ad6Xb7q3ia

  • Join fedora-project.slack.com on the "tech" channel

  • Self-register at: http://slack.fcrepo.org/

Attendees 

1. Danny Bernstein
2. David Wilcox  
3. Jared Whiklo 
4. Peter Winckles 
5. Ben Cail 
6. Daniel Lamb 
7. Calvin Xu
8. Rosie Le Faive

Agenda

1. Announcements
   1. Sprint:  Feb 8-19
2. Thoughts on the Leaders Committers call
3. Affirming the team's understanding of famous current issues/bugs: 
   1. bloated directory from migration utility update
   2. Fedora 3 "bad" checksum issue - for reference the MOTHER OF ALL THREADS on the subject (JIRA: Unable to locate Jira server for this macro. It may be due to Application Link configuration. )
      1. Changes to migration-utils
      2. Expectations for the fcrepo-migration-validator
   3. The Daniel Lamb Bug
   4. The new Prefer Header recently accepted as part of the Fedora API  : https://github.com/fcrepo/fcrepo-specification/pull/412
      1. Implications
         1. Core: http://fedora.info/definitions/fcrepo#ServerManaged is not currently recognized
         2. Test Suite
   5. The new  resource header  (json) field jira that will make the following PR's no longer need to be merged:
      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. Validation error reporting on start up and side-loading: What is going to work for the user? 
      1. For reference: https://github.com/fcrepo/fcrepo/pull/1852#pullrequestreview-577812174
4. PRs 
   1. object validation
      1. https://github.com/fcrepo/fcrepo/pull/1852 (wiring validation into fedora)
      2. https://github.com/fcrepo/fcrepo-storage-ocfl/pull/28 (validation logic)
   2. Minimum container triples: https://github.com/fcrepo/fcrepo/pull/1851
   3. ?
5. Sprint planning:
   
   1. Testing
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
   2.  Development: Are the following must haves for beta?
      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.
   3. Documentation

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