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://duraspace.zoom.us/my/fedora
  

  • Dial-in:
    +1 408 638 0968
    +1 646 876 9923
    +1 669 900 6833
    Meeting ID:
    812 835 3771

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

Attendees

• Danny Bernstein
• Andrew Woods
  
• Bethany Seeger 
• Jared Whiklo 
• Peter Eichman   
• Doron Shalvi 
• Kevin Ford 
• Ben Pennell
• James Silas Creel
  
• David Wilcox
• Aaron Birkland
• Mohamed Abdul Rasheed
• Yinlin Chen
• Randall Floyd

Agenda

1. Sprint Update
   
   1. Board
   2. Backlog
   3. WebACL
   4. Versioning
   5. Compatibility Test Suite
2. Post Sprint Planning
   1. Who can commit to landing 5.0.0 for release
      1. Loose ends
         1. Completing the API alignment tasks
         2. Documentation 
            1. Adopters Guide
            2. FEDORA5x Review 
            3. Compatibility Test Suite
         3. Bug fixes

3. Messaging headers: should they stay or should they go? who is using them? Camel? 

4. Jira
   server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2604

   : 

   1. Are we comfortable with messages emitted?Shall we consider using Duraspace checkstyle rules?

5. Checkstyle Analysis

   1. Repo
   2. There are three rules in the fedora checkstyle rules that are not in the Duraspace checkstyle rules: 
      
      1. requiring @author in javadoc
      2. "final" required for parameter variables
      3. "final" required for local variables
6. Mailing list: Kevin Ford's inbound links question

Ticket Summaries

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. COAR some recommendations for behaviours or technologies for next generation repositories.
   1. A list of things that Fedora already does, but some to consider as an addition or plugin. Some may have been considered.
   2. Signposting - a set of HTTP Headers to allow machine readable data to be added as headers.
   3. Has there been any discussion or consideration of these technologies for use before David takes it to the leaders.
   4. Its likely we will see a push for some of this type of stuff from a strategic level, there was a meeting of this group at CNI. Some members of the group said they might be able to get some funding for this.
   5. Please review the list and have some idea of whether we think it is applicable at the Fedora level or API-X level.
   6. There has been previous discussion of Linked Data Notifications which could be one option.
   7. Activity Streams Paging model might be a way to deal with the many members problem.
2. Couple of documentation efforts that are underway. Not sure if we will get to them on the current sprint, but if you are not on the sprint and would like to help out with one of these efforts. Please reach out to Danny (email/slack) and he'll help you get started.
   1. Adopters guide is around the API transition from Fedora 4.7 to Fedora 5.0
   2. Breaking changes is around the Modeshape implementation.
3. Sprint is moving along and have closed quite a few issues.
   1. Any concerns about the process for the sprint?
   2. FCREPO-2753 decoupling WebAC from Modeshape and run into a circular dependency between http-api and auth-webac. How do we want to handle that? Because WebAC is the only one mentioned in the API spec should we move all the relevant auth-webac code to http-api and deprecate the old code. Or move it to a separate servlet filter. Or move it and use interfaces to keep them separate.
   3. There is one use case where you only allow an INSERT patch request if the user has acl:Append permission. There might be some room the SOLID spec to work around this issue.
   4. A separate servlet filter would make it easier for individuals to extend the WebAC implementation and swap it out for the default one without having to compile a custom Fedora.

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

      ACLs will have a standard location, do we have a location to put them? We could put them in a set a location and link the from each resource or hang them off the actual resource is an option. This would reduce the risk of ending up with orphan ACLs hanging around.
   6. Refactoring the binary implementation to separate the description of a binary to its own node. That arrangement was making it hard to resolve paths for versioning. Still in the initial stages of this work but it is looking promising.
   7. Deleting tombstone resources.

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

Actions