Time/Place

This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:

• Time: 11:00am Eastern Daylight Time US (UTC-4)
• Dial-in Number: (712) 775-7035
  • Participant Code: 479307#
  • International numbers: Conference Call Information
  • Web Access:  https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
• IRC:
  
  • Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
  • Or point your IRC client to #fcrepo on irc.freenode.net

Attendees

• Danny Bernstein
• Peter Eichman
• Andrew Woods
• David Wilcox
• Bethany Seeger
• Ben Pennell
• Jared Whiklo
• Doron Shalvi
• Yinlin Chen 
• Ben Cail 
• Kevin Ford
• ...

Agenda

1. 4.7.5 release testing - discussion of where things stand
   1. FCREPO-2666
   2. FCREPO-2665
2. Moving into alignment with the spec
   1. Sprint date options
3. Pairtree/Appletree options
   1. Where did we land here? 
   2. Volunteer to create a JIRA to specify the solution.
4. External Content: Redirect or Proxy? on fedora-tech
   
   1. Where is this landing?
5.  - Also move forward with creation-side resolution?
   
6. Compatibility Test Suite 
7. OCFL Update/Discussion
   1. Andrew Hankinson's paper
8. ...

Ticket Summaries

1. Please squash a bug!

   
   

2. Tickets resolved this week:

   
   

3. Tickets created this week:

   
   

Minutes

1. Current RC has issues with MySQL and Postgres, but need more tests to further confirm it.
https://jira.duraspace.org/browse/FCREPO-2665: not make it a blocker
https://jira.duraspace.org/browse/FCREPO-2666: not make it a blocker
Aaron will work on API-X.
There will be RC3 soon.

2. The Fedora API Alignment Sprint Date Options poll will close tomorrow.

3. Still needs further discussions and testing about Pairtree/Appletree options. Some discussions list below.
1. Need to do some furthers testing to help determine these options that indeed help the performance issues.
2. Option 4 is specifically intended to remove the ability to use pairtrees for partitioning membership from the client side.
3. Go with option 3 allow people to configure pairtrees if they want to do that, but stop hiding them if they exist.
4. Implement a workaround solution sounds not right.
5. Should not be a default configuration.
6. Need a document for these behaviors.
7. What is the default behaviors we want to bring into Fedora 5?
8. Some people favor option 3.

Other agenda items move to next meeting.