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. Performance Testing Criteria
   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

1. Affirming the team's understanding of famous current issues/bugs: 
   1. bloated directory from migration utility update
      1. Peter has offered a potential solution to Calvin - just waiting to hear back
      2. Could also be due to incorrect size being reported from du command
   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
         1. Extract data stream from inline XML and calculate checksum based on that
      2. Expectations for the fcrepo-migration-validator
         1. Bad checksums in Fedora 3 will stay in Fedora 3 - validator will not carry this forward
      3. Danny will create JIRA tickets to track these issues
   3. The Daniel Lamb Bug
      1. Danny migrated a dataset with spaces in IDs
      2. Migration worked but updating a resource resulted in corrupted RDF with spaces in the IDs such that the object can no longer be read
      3. May be an issue with Millner
      4. Jared will help with debugging by trying to duplicate the issue
   4. The new Prefer Header recently accepted as part of the Fedora API  : https://github.com/fcrepo/fcrepo-specification/pull/412
      1. Core: http://fedora.info/definitions/fcrepo#ServerManaged is not currently recognized
         1. Danny will create a JIRA to update
         2. Do we deprecate or accept both?
            1. Add to list of breaking changes and deprecate
   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
      2. Currently, on start up, log messages indicate validation failures
      3. As a user, if you don't examine the logs, you won't notice the failures - need to document clearly
2. 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)
      3. Danny will merge these today
   2. Minimum container triples: https://github.com/fcrepo/fcrepo/pull/1851
      1. Andrew is reviewing this
3. Sprint planning:
   
   1. Testing
      1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Confirming rebuild is faster post-parallelization
      2. https://docs.google.com/document/d/1ihoAHlnl1X8yCLF9cXT-ZmZFkCX37nYzgqIc-U3J2YQ/edit
         1. Community-sourced performance criteria
         2. Need to review for anything that should be included in the beta
   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.
         1. Need to get a baseline as soon as possible
      2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Small task but should be included
      3. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Not critical for beta but needs to be in the release
      4. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Not a beta blocker - just need to default to n-triples if there is no mime type
      5. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
         1. Probably not a beta blocker but unsure how many people use ghost nodes
         2. Not affecting how anything is stored on disk in any case
      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.
         1. Not a beta blocker but relatively easy to implement
   3. Documentation
      1. Lots of things to work on
4. Release process
   1. With Andrew leaving it would be good to have others involved in the release process

Actions