Page History

...

1. Sign up for the upcoming Alignment Sprint
2. Review Ben Pennell's exposition of options for implementing mementos of binaries and their descriptions
3. Documentation mini sprint
   1. Who is interested? 
   2. Timeframe
   3. Objective
   4. Next steps
4. Review Ben Pennell's exposition of options for implementing mementos of binaries and their descriptions
5. Low hanging tickets that could be worked in a "pre-sprint" 
   1. ? 
   2. ?
6. Shall we consider using Duraspace checkstyle rules?
   
   1. Checkstyle Analysis
   2. Repo
   3. 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

...

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. Alignment with Specification - 2018 Spring Sprints

...

1. Issues: https://jira.duraspace.org/issues/?filter=14401
2. Danny: very productive sprint, lots of issues closed, major milestones
   1. memento functionality mostly 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

...

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

...

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

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

...

1. Danny: looks good to me — other folks can comment on the document

...

1. Actions

•  Yinlin Chen: Review and update ACL creation documentation: Quick Start with WebAC
•  Ben Pennell: Create a wiki page documenting options for mementos of binaries and their descriptions