Call in details:

Attendees


Resources:

Discussion

  1.  Where do we stand
    1. Open issues
    2. CTS
  2. Open discussion
  3. Miscellaneous
    1. Status of https://github.com/whikloj/fedora4-tests - do we want to maintain these tests in the face of Integration tests + CTS? 



Notes: 


Goals

Logistics

  1. Post sprint stand-up notes by 10am ET https://wiki.duraspace.org/display/FF/2018+Fall+Sprints

Meeting schedule

  1. This Friday: Sept 14th @9:30am ET
  2. Last Friday of sprint: Sept 21st

Compatibility Test Suite

  1. Using GitHub Issues to track work
  2. Ensure that tests are written against the Specification, not the community impl
  3. Add lots of inline comments

Open Issues

  1. Kanban Query: API Alignment Epic

Who is doing what

  1. Peter / Mohamed
  2. Mohamed
  3. Ben
  4. Jared
  5. Mike


Minutes

  1. Surface any issues from the week that haven't been discussed or need to be discussed in preparation for next week.
  2. All CTS tests are written, one remaining PR then CTS is complete.
    1. Andrew Woods Will review the CTS to see if there are any missing tests
    2. Possibly PUT for creation tests. It is an optional behaviour and there are no relationships that can be assumed.
  3. Once there are more implementations of the Fedora API spec, we will need to review the CTS and see what biases exist that need to be removed.
  4. Jared Whiklo will take on FCREPO-2861
  5. Michael Durbin will have a look at Jared Whiklo's work on FCREPO-2730.
  6. SOLID spec has created some new WebAC terms (acl:groupListing), ours does not work if the acl:agentGroup URI contains a hash URI.
    1. The ability to use a hash URI as the object should be supported.
  7. 23 tickets for the API Alignment EPIC, 8 in-progress.
  8. FCREPO-2863 if acl:agent foaf:Agent then it should allow any users. But we can't test for a non-authenticated user as AuthN is handled by the container whereas Fedora only handles AuthZ.
    1. Two tests one for foaf:Agent and one for acl:authenticatedAgent
  9. fcrepo4-labs/fcrepo4-tests will be maintained for those things that are not covered by the CTS.
  10. Once the API Alignment EPIC is done, there is be all the other tickets available at
    type key summary assignee reporter priority status resolution created updated due

    Unable to locate Jira server for this macro. It may be due to Application Link configuration.

  • No labels