Page tree
Skip to end of metadata
Go to start of metadata

Time/Place

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

Attendees

Agenda

  1. Welcome to new Fedora Committer: Peter Eichman
  2. Sign up for Sprint Alignment
  3. Alignment Sprint Retrospective  https://jira.duraspace.org/issues/?filter=14401
    1. what worked
    2. what didn't 
    3. what was accomplished
    4. remaining tickets to be worked/wrapped before the beginning of the next sprint.
    5. major themes going into next sprint
  4. FCREPO-2709 - Getting issue details... STATUS
  5. Moving ACLs out of the modeshape layer.
    1. https://fcrepo.github.io/fcrepo-specification/#append-ldprs
    2. 5.7.3 LDP-NR - Patching Binaries (LDP-NR) - do we plan to support - if so what should it look like?
  6. Feedback on Peter Eichman's writeup on the use of userAgent and groupAgent base URI's and their relationship to WebAC in order to clarify whether or not what if anything needs improvement/clarification/alignment
  7. ?

Sprint tickets 

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh

Ticket Summaries

  1. Please squash a bug!

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  2. Tickets resolved this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

  3. Tickets created this week:

     Click here to expand...

    Key Summary T Created Updated Due Assignee Reporter P Status Resolution
    Loading...
    Refresh

Minutes

  1. Welcome to new Fedora Committer: Peter Eichman
  2. Sign up for Sprint Alignment
    1. 2018 Spring Sprints
  3. Alignment Sprint Retrospective
    1. Issues: https://jira.duraspace.org/issues/?filter=14401
    2. Danny: very productive sprint, lots of issues closed, major milestones
      1. memento functionality implemented
      2. team very engaged, plus lots of contribution from Jared Whiklo even though he wasn't offically on the sprint
    3. Yinlin: one suggestion: would appreciate documentation for command-line usage for creating ACLs
    4. Randall: early in the sprint, some PRs got merged while I was still testing them — maybe we should signal what we are reviewing/testing?
      1. Danny: you can specify the reviewer on the PR or JIRA ticket (including self-assigning), which might help make it clearer who's reviewing what
      2. Ben: we can have multiple reviewers on PRs
      3. Danny: if you're not comfortable merging a PR, you can review/test and request a second pair of eyes
      4. Joe: asking on Slack before merging is another good way to make sure we're all on the same page
    5. Ben: a documentation mini-sprint before the next sprint might be good
    6. Major features and themes for next sprint
      1. DateTime negotiation
      2. ACL append, including possibly moving ACL enforcement out of Modeshape
  4. Moving ACLs out of the modeshape layer.
    1. https://fcrepo.github.io/fcrepo-specification/#append-ldprs
    2. 5.7.3 LDP-NR - Patching Binaries (LDP-NR) - do we plan to support - if so what should it look like?
    3. Ben: seems worth investigating, since it would be a better long-term approach
    4. Danny: Exactly, would make it easier to switch to a non-Modeshape backend
    5. Aaron: There's a mismatch between Mode and WebAC permission modes
    6. Ben: hard to do on a sprint, since a major refactor like that would block other work
    7. Peter: fine with deferring append support to 5.1 release, but want to make sure nobody is waiting for it
    8. Danny: we could work on the other tickets without duplicating effort with ACL append implementation
  5. Binary description mementos
    1. FCREPO-2709 - Getting issue details... STATUS
    2. Ben: with binary mementos, you have both the binary and the description, which would require two updates to modify them
      1. But mementos are supposed to be immutable, so how would you create the binary and the description?
      2. Do we want to make the binary and description mementos separate from each other to avoid this?
    3. Esmé: Could we do a three-step process:
      1. create binary memento (auto-creating description memento)
      2. delete binary description memento
      3. create desired binary description memento
    4. Ben: what would the state be after you deleted the description memento? It could fall back to the current state of the description
      1. Seems like it could work, but also seems like more requests than needed
    5. Danny: This seems it is effectively allowing the binary description to be modified
    6. Jared: Almost any way you do this would allow inconsistent state, unless you separate them
    7. Ben: My PR separates the binary and description mementos, so I think that's feasible, it's really just a matter of deciding how we want them to behave
      1. It would be good to have a wiki page documenting how we want this to work
  6. Feedback on Peter Eichman's writeup on the use of userAgent and groupAgent base URI's and their relationship to WebAC in order to clarify whether or not what if anything needs improvement/clarification/alignment
    1. Danny: looks good to me — other folks can comment on the document
  7. James: Texas A&M has been looking at a lot of different platforms, including Hydra/Islandora, existing DSpace
    1. Generating IIIF manifests, Spotlight exhibits, going into production very soon


Actions

  • No labels