eTime/Place

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

Attendees

  1. Danny Bernstein
  2. Peter Eichman
  3. Bethany Seeger
  4. Jared Whiklo
  5. David Wilcox
  6. Andrew Woods
  7. Kevin Ford
  8. Michael Durbin(star)
  9. Ben Pennell
  10. Aaron Birkland

Agenda

  1. Announcements

  2. Sprint progress/checkin

  3. Issues to discuss: 
    1. Unable to locate Jira server for this macro. It may be due to Application Link configuration.
    2. Unable to locate Jira server for this macro. It may be due to Application Link configuration.  :  Can we close it? 
    3. https://github.com/fcrepo4/fcrepo4/pull/1402
  4. Dependency Update Discussion
  5. <your agenda item here>
  6. Please squash a bug!

    key summary type created updated due assignee reporter priority status resolution

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

  7. Tickets resolved this week:

    key summary type created updated due assignee reporter priority status resolution

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

  8. Tickets created this week:

    key summary type created updated due assignee reporter priority status resolution

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

Minutes

  1. Announcements

    1. Peter Eichman will be out until Tuesday morning
    2. David Wilcox wondered if anyone wanted to help out at a workshop at Samvera Connect.  No one else on the call was going
  2. Sprint Progress
    1. no blockers, Andrew Woods wondered where remaining gaps may exist and where help is most needed (possibly reallocate efforts to ensure completion)
    2. closing in on the test suite as well (almost all but messaging is complete)
      1. Completing and passing the compatibility test suite should be prerequisite for a release
      2. Differing opinions about how close we are to having a shining example of a Fedora Spec implementation were expressed.
    3. WebAC is getting close as well 
  3. Issues to Discuss
    1. There are a few PRs in Compatibitliy Test Suite that should have straightforward reviews that should be reviewed and merged
    2. FCREPO-2854, FCREPO-2855:  Jared Whiklo doesn't see any purpose in accessToClass given that we don't have defaults and it only applies to a resource anyway.  Peter Eichman considers it useless but not harmful, and since maybe someone might find a reasonable way to use it in the future. 
      1. Peter Eichman suggested that some sort of best-practice-auditing tool might help (to warn people that they might be doing something that doesn't have any real effect in the repository and ensure they're not making a mistake), but didn't go as far to as to recommend anyone to write such a tool at this time.
    3. FCREPO-2852: are we satisfied that mementos should return original URIs and subjects?  (Indexing mementos in a simplistic way will result in historic triples included with the current ones)
      1. Kevin Ford suggested the extraordinarily clear documentation is likely the best approach now.
      2. Danny Bernstein said that technically it's be just reverting a commit to change this behavior
      3. Bethany Seeger suggested that it might be implied in the spec that the memento use original URIs
      4. Modeshape snapshots had references to the other elements in the snapshot.  Since some references point out from the snapshot to unsnapshotted resources, there wasn't any way to point to the memento because it doesn't exist.  They can only be original URIs.
      5. There were strong arguments for the current approach, but an acknowledged need to update the camel indexing routes to support better handling (probably dropping) of memento triples.
      6. Danny Bernstein will close the ticket, but create a new one about the documentation/camel toolbox
    4. FCREPO-1402: Aaron Birkland doesn't remember when/why we removed messages emitted during changes to linked resources.  Many current users might depend on it now.  While it's an easy change to make, do we have to, and who will it harm?
    5. Jared Whiklo has a workaround that morphs events into something else rather than throwing them away.
    6. No conclusion, will discuss further.


Future Agenda Topics: 

  • No labels