...

• 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 

• A. Soroka
• Longshou Situ
• Yinlin Chen 
• Nick Ruest 
• Jared Whiklo 
• Danny BernsteinKatherine Lynch 
• Unknown User (acoburn)
• Bethany Seeger
• Andrew Woods
• David Wilcox
•  
• Daniel Lamb
• Esmé Cowles
• Michael Durbin
• Andy WagnerFrank Smutniak

Agenda

1. 4.7.0 release candidate - testing and migration
2. ...

3. Status of "in-flight" tickets

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13202 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

...

1. Please squash a bug!

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13122 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

2. Tickets resolved this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13111 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

3. Tickets created this week:

   Expand
   Jira server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery filter=13029 serverId c815ca92-fd23-34c2-8fe3-956808caf8c5

Minutes

1. 4.7.0 Release status – we need a PostgreSQL and Mysql test. Yinlin Chen has a question about Solr indexing, but it may be an artifact of how the tests are run. The Solr indexing issue does not appear to be a blocker but rather indicates a need for improvement of the testing mechanism. Jared Whiklo will conduct Islandora-based testing, and he will ask the Hydra community about testing.
2. Discussed

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-1868

    jcr.Session being replaced with a Fedora-specific interface. This will be a significant change to the code, potentially making alternate implementations considerably easier to write. Everyone is encouraged to review the current (in progress) pull request.
3. Discussed
4. Now that the release candidate is out,  let's focus on testing. 
   1. Yin will try vagrant today and verify whether or not it is broken.
      1. try "vagrant box update"
   2. Possible to tie vagrant to a specific version of the base box?  Since base boxes can shift under a fedora version and cause confusion...
      •  Nick Ruest will look into this.
   3.  Who will help with testing? 
      1. Danny
      2. Nick
      3. Aaron Birkland
   4. Some focus should be brought to migration of existing repositories
      1. Who might be willing to attempt such a migration test?
      • •  ? 
   5. Jared:  Please test something
5. LDP Test Suite:  We need to maintain this thing - at least insofar as the tool should still run:
   
   1. We should come to an agreement with Rob and others about the terms of maintenance.
   2. Do we fork this project ?
   3.  Project still runs, but will break.  Maintainers are not responding.
   4. Chris Beer has identified a problem with the Test Suite and has a pull request in.
    A. Soroka will open a JIRA to track this issue.  (

   Jira
   server DuraSpace JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-

   2249)
   •  Andrew Woods  will move this onto the agenda of LDP Next
6. HydraConnect:
   1. Anyone up for a meetup?  
   2. Who will be there: 
      1. Esme, Kate, Yinlin,  Ben, Andrew Woods, Bethany
   3. Any ideas of how to use this opportunity?
      1. Containerizing in Production Deployment
      2. Import/Export unconference session?  Yes - there is  interest there
   4. Informal get together?  Yes there is interest.
      1. Lunch Wednesday or Thursday?
         •  Bethany Seeger will organize.  
7. It is not always clear which versions of which pluggable components are compatible with which version of fcrepo4.
   1. Andrew Woods surfaced the need to maintain a compatibility matrix or at least capture this information somewhere in the documentation.
      
      1. Proposal:  When a component is released,  document which fcrepo4 version it will work against,  whether in a compatibility matrix or in the readme.
      2. General agreement: any release notes  should note which fcrepo4  the component was tested against.
      •  Andrew Woods : Add a note to EXTS policy docs indicating that people must document which version of fedora was used with integration tests (where applicable)
        • F4 GitHub Organizations
          
8. Next week Andrew Woods will be gone:  Any high priority work / blockers that should be raised?  No.
Comments on the API dependencies: Who will tackle each component: Resource CRUD:  
•  A. Soroka will reach out to Ben,  Tom Johnson, Danny Lamb

9. 1987

   Hash URIs on binaries. This issue gets deeply into the modeshape implementation – Danny Bernstein will reach out if he encounters challenges.
10. Discussed Linked Data Notifications (this will enter W3C recommendation review next week) and some proposed machinery for fcrepo-camel that would make it easier to build an asynchronous LDN toolchain for internal Fedora events. This feature intersects significantly with the current audit functionality but with (potentially) considerably more flexibility.