...
- Danny Bernstein
- Andrew Woods
- Bethany Seeger Jared Whiklo
- Peter Eichman Kevin Ford Ben Pennell
- Mohamed Abdul Rasheed
- Randall Floyd
- Carrick Rogers
- James Silas Creel
- Aaron Birkland
- David Wilcox
- Yinlin Chen
- Joe Harrington
Agenda
- Feedback on /fcr:fixity endpoint?
- Volunteers for running the weekly meeting:
- 5/17: Bethany Seeger
- 5/24: Jared Whiklo?
- 6/7: Cancelled
- Feedback on /fcr:fixity endpoint
- Getting to 5.0 Another sprint? Timeframe/Duration/Availability
- Review of work that happened this week:
- 6 PRs merged
- Documentation: Kudos Kevin Ford has kicked it off.
- External content (proxy, copy, and redirect)
- 5.x Documentation Effort
- 5.x Documentation Updates matrix
- Another sprint?
- Timeframe/Duration/Availability
- Ecosystem tools dependent on the release:
- java client import export tool
- camel tool kit
- fcrepo4-vagrant
- import export tooljava client
- api-x
- Review of work that happened this week:
:Jira server DuraSpace JIRA serverId c815ca92-fd23-34c2-8fe3-956808caf8c5 key FCREPO-2604 Are we comfortable with messages emitted??
Ticket Summaries
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 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 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
Facilitating upcoming meetings
- 5/17: Bethany
- 5/24: Jared? - Danny to reach out
- 6/7: cancelled
Feedback on /fcr:fixity endpoint
- Deprecate in 5.0
- Community has indicated interest in retaining the feature for now
Getting to a 5.0 release
- Great progress this week
External Content PR is in good shape for merge
- All flavors supported: redirect, proxy, copy
- One outstanding issue: one test is being @Ignored
- ACTION: Bethany to capture in a new ticket
Documentation
- Kevin Ford has been making good progress
- Adding sign-off of 5.0 wiki documentation to release process
- Yinlin interested in helping with documentation
- ACTION: Danny to update documentation table to align states with JIRA states
Sprint schedule
- Sprint A - summer
- Feature completion
- Documentation
- Compatibility Test Suite, contract work?
- We should create granular CTS tickets
- Valuable having "third-party" interprete spec and create unbiased tests
- Testing
- Sprint B - sept
- Bug resolution
- Critical backlog tickets?
- Ecosystem tools
- import/export
- camel-toolbox
- vagrant
- java-client
- api-x
- What is the target release date?
- Ideally 2018... mid-Oct
- ACTION: Danny to create a sprint date doodle
- Need to avoid scope-creep
- Identify other features that we would like sooner than later
- Danny: Sprint successful. Closed 30 issues. 11 Participants. Major work to handling of binaries and their descriptions (overhaul really) – to their structure to support binary mementos. Still some small issue around deleting of mementos nevertheless on the verge of declaring victory after some additional testing. Congrats to Ben Pennell. Major overhaul to WebAC. WebAC piece ended up being bigger than expected, but hats off to Mohamed Mohideen Abdul Rasheed and Peter Eichman for this effort. Updates on External Content
Bethany – Got tests passing and rebased. Working on getting binary memento tests to pass. Hope to have PR later today or tomorrow AM. Proxy and Copy should be covered. Versioning of external content: Has this scenario been addressed?
Jared noted that one might version the metadata related to the External Content, but there was a general consensus that versioning content, proxied or otherwise, outside the repository was beyond the scope.- Binary Versioning
Work merged into ‘master’. Worked out separation of binary and description. With one command you can create a binary version and that automatically creates a version of the description. And then you can independently version them. Work is in a good place.
CTS Danny – CTS is getting there. Should be in a good place by EOD to fix currently breaking tests, or to at least investigate the issues, and then it should be clear where to layer in the additional elements of the specification.
Randall noted that it was initially difficult to translate written spec to a test, but newer patterns in CTS provides clearer path forward.- There was a question surrounding this in Slack, presumably because the interaction for the digest feature in 5.0 is entirely Header-based and the 4.0 /fcr:fixity endpoint is superfluous. In the end, there is a notional consensus to remove the /fcr:fixity endpoint, but we should send note out to the list asking for feedback.
- Another sprint?
- Everyone commit to a ticket or two this week?
Danny - https://jira.duraspace.org/browse/FCREPO-2275?filter=14401 Grab a ticket and let’s see if we can get ‘er done.
If above tickets were closed, we'd be in alignment with spec.
BUT definitely more work to do on Documentation and CTS.
- 5.x Documentation Effort
- 5.x Documentation Updates matrix
Danny - Took every 5.x documentation page and set up a process around documentation review. Seemed straightforward and less arduous than using Jira for this. Put you name by a page and get crackin’.
Kevin – If those who worked on specific elements of the API – fixity or versioning for example – could initially review the carried-over documentation that would be really helpful as those individuals will be most familiar with the new interaction patterns and/or API differences.
Andrew – Perhaps if Peter and Mohammed could look at WebAC....
Ecosystem tools dependent on the release: - 5.x Documentation Updates matrix
- General agreement that a review of the existing ecosystem tools should be reviewed to determine whether there are any blockers or otherwise prioritize upgrading them.
- Noted that there are unlikely to be any 'blockers' but emphasized that the community might identify a number of very-nice-to-haves.
- Will take list to leadership group and community generally. List
- java client
- camel tool kit
- fcrepo4-vagrant
- import export tool
- api-x fcrepo4-exts
Are we comfortable with messages emitted?
TIME. Noted we need to talk about this but discussion postponed.
WebACPeter - Major refactoring into shiro and out of modeshape and fedora authorization delegates. Intend to get back to a few of the remaining issues or get the code pushed up for someone else to bring to completion. Given how modeshape works, we will still need some implementation of an authorization provider for modeshape to set up the security context for modeshape, despite the fact that we are not doing the authorization in modeshape, because modeshape still needs to know “who” did something. Mohamed has some work on this started.
The fate of /fcr:fixity endpoint: should we continue to support it in 5.0?
Getting to 5.0
Jira | ||||||
---|---|---|---|---|---|---|
|
Actions
- Danny Bernstein Create a ticket to check whether or not the fcrepo-camel-toolbox still works with 5.0. Part of that ticket is to evaluate whether or not there are dependencies on the jms.* headers included in the messages generated by Fedora
- Bethany Seeger Create tickets to test versioning and redirect/proxy.
- Kevin Ford Ask community about /fcr:fixity endpoint.
- Danny Bernstein Inquire with leadership group (and broader community?) about prioritizing ecosystem tools for alignment with 5.0.
- Bethany Seeger to create JIRA for @Ignored test in External Content PR
- Danny Bernstein to update documentation table to align states with JIRA states
- Danny Bernstein to create Sprint Doodle for immediate distribution