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. Daniel Lamb 
6. Calvin Xu
7. Ben Pennell 
8. Thomas Bernhart 

Agenda

1. Announcements
2. Sprint
   
   1. Review of the Board
3. Questions/discussions:
   1. is fcr:fixity still considered deprecated?
   2. Do we need F2 code in the migration utils?
   3. Removing fcrepo-config.xml
      1. https://github.com/pwinckles/fcrepo4/commit/16205c9e0386048e5138c2cd402d55066170ed23
4. Performance Testing
   
   1. Performance Testing Criteria
5. PRs
6. Your topic

Tickets

1. In Review

   
   

2. Please squash a bug!

   
   

3. Tickets resolved this week:

   
   

4. Tickets created this week:

   
   

Notes

1. Announcements
   1. David says that there's a lot of interest in Fedora 6.
   2. UC Davis is interested in F6
   3. Mike Ritter will be joining next week
2. Sprint
   
   1. Review of the Board
   2. Sprint going well
   3. What is the target for the final release? What tickets still need fixed? Where is the line?
3. Questions/discussions: 
   1. is fcr:fixity still considered deprecated?
      1. There are some users who expect this functionality to exist
      2. Leave it till there's a viable replacement
      3. Something needs to be added to the spec
   2. Do we need F2 code in the migration utils?
      1. Unsure if the F2 code works or if anyone still uses F2
      2. Seems like it's okay to remove
      3. Ben wants to migrate the entire FOXML without splitting it up as part of a PLAIN_OCFL migration
   3. Removing fcrepo-config.xml
      1. https://github.com/pwinckles/fcrepo4/commit/16205c9e0386048e5138c2cd402d55066170ed23
      2. Moving beans to Java Config and adding properties for configuring without touching spring
      3. Should be fine for most use cases. Unclear if people have custom auth configurations that may be more difficult for them to configure – still requires custom spring config
4. Performance Testing
   
   1. Performance Testing Criteria
5. PRs
6. Your topic

Actions