Page History

...

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. Sprint Update
   1. Peter: summary of WebAC work, FCREPO-2760 unblocks many things
   2. Danny: we should create separate tickets for tests
   3. Danny: added support acl:Control to sprint scope

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

      : out of scope, potential impact on authN
      1. Jared: this is also not in the spec
   5. Mohamed: working on spring config, acl:append
      1. spring config will unblock manual testing
   6. External content handling
      1. Bethany: picked up Ben's work on external content, Jared continued on multiple huge changes
      2. Bethany: should have PR soon for external content, hopefully by EOD Friday
         1. should address all 3 access types (copy, proxy, and redirect)
   7. Randall's Java questions: got some advice before call, should be unstuck now
   8. Andrew is focussed on PR review (as well as gutting the codebase)
      1. Danny can support PR review by testing
      2. no open PRs on TCK
      3. 4 open sprint PRs on fcrepo4
      4. #1341 (single document ACL) has not been reviewed, Danny and Andrew will review
   9. Andrew: goal: align with spec, probably won't all happen in this sprint
      1. update delta document to reflect current state
      2. Danny: most red x's on delta document in WebAC, and versioning
      3. Peter: review delta document at sprint wrap-up meeting?
      4. Danny: will go though question mark items, then focus on red X's
   10. Ben: binary memento tests are mostly passing with new implementation of binaries, finishing up tests for description w/o binary
       1. PR today (hopefully)
2. Post Sprint Planning
   1. Much work done, but there is still work to bring 5.0.0 to release
      1. API alignment, bug fixes, documentation, compatibility test suite
   2. Randall: interested in getting back to compatibility test suite
   3. Peter: 5.x documentation for WebAC
      1. Andrew: a large amount of weeding that can be done on the wiki
   4. Kevin: what happened to breaking changes document?
      1. Danny: a question of focus, adopters guide could subsume the breaking changes document
      2. Kevin: breaking changes could be a list, adopter's guide can go into greater detail
      3. Danny: adopter's guide less urgent than 5.x documentation, 5.x is key
      4. Kevin: will look at adopter's guide, focus on uniform presentation
   5. Danny: contractor pausing on compatibility test suite while community looks at it?
      1. Andrew: yes, contractor is ready to go as soon as we give the okay, once WebAC and versioning drop in it would be good to give the green light
      2. contractors role to go line-by-line through spec and crank out tests
      3. Danny: how much value is there in us organizing that work?
         1. Andrew: high value in setting up a first test to give the contractors a starting point
         2. Danny: will stub out tests
         3. Randall: need a pattern to follow, so setup code and pseudocode will be very helpful
   6. Danny: will discuss plan for 5.0.0 release at sprint wrap-up meeting
3. Messaging Headers
   1. adoption of ActivityStreams
   2. JMS headers are still be emitted
   3. Peter: Camel might use them, needs review
   4. Andrew: need to review whether the camel toolbox works with the API sprint changes
   5. Kevin: removing headers would break their routes, possibly other people's
   6. Danny: review our header schemes, find out which routes depend on what headers
   7. Jared: fcrepo-camel is setup to turn an ActivityStream message to custom (non-JMS) headers
4. Inbound Links Question (Kevin)
   1. Kevin: issue is not critical and discussion can be delayed
      1. inbound reference list appears to get truncated
      2. feeling that it is a bug, but not sure
      3. RDF response is truncated
   2. Danny: try N-triples, see if it is serialization-dependent
   3. Andrew: please create a bug report so it doesn't get lost
   4. Kevin: will do
5. Checkstyle Rules
   1. Andrew: plan is to have a common set that could be suppressed on a rule-by-rule basis for other projects
   2. Danny: using Fedora as the basis for these common rules
6. 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.
7. 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.
8. 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. JiraserverDuraSpace JIRAcolumnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolutionserverIdc815ca92-fd23-34c2-8fe3-956808caf8c5keyFCREPO-2769

Actions