Time/Place
This meeting is a hybrid teleconference and IRC chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Dial-in Number: (712) 775-7035
- Participant Code: 479307#
- International numbers: Conference Call Information
- Web Access: https://www.freeconferencecallhd.com/wp-content/themes/responsive/flashphone/flash-phone.php
- IRC:
- Join the #fcrepo chat room via Freenode Web IRC (enter a unique nick)
- Or point your IRC client to #fcrepo on irc.freenode.net
- ? add slack channel info here?
Attendees
Agenda
- 4.7.5 Release
- bringing it over the finish line:
- Sign up for API Alignment sprints by adding your name
- Any remaining questions?
- Updates from spec editors on External Content: Redirect or Proxy?
- Compatibility Test Suite
- Results as of last night: LDP Test Suite Report.pdf
- Delta Document Progress Review
- <add your agenda item here>
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
- 4.7.5 Release
- Danny Bernstein had a question regarding 4.7.5 RC branch push to 4.7.5 maintenance. Have to open a PR from release branch to maintenance branch. As it's no longer an RC, we don't need that in the name. So 4.7.5_RC pushed to → 4.7.5 release pushed to → 4.7 maintenance.
- Bethany Seeger created PR this am. No remaining questions.
- Updates from spec editors on External Content: Redirect or Proxy?
- no spec editors here, so tabled til next week.
- Compatibility Test Suite
- Looked at LDP Test Suite Report.pdf
- Some of the things failing here are MAY or SHOULD, so does that count as a failure?
- Throwing of a 409 - is acceptable and expected in some case, but shows up as a 'fail'. The report could use another column that shows if the test is a MAY or SHOULD and whether or not a faillure is acceptable in certain cases (as in expected, in which case it wouldn't really be a failure).
- Jared Whiklo to make an issue on in the test repo for this.
- Delta Document Progress Review
- Jared Whiklo made a minus box for things that are not applicable. There are cases where you must be able to distinguish between something and that sounds more like a SHOULD then a MUST.
- Changing interaction model - Jared was able to add NonRDFSource to something that was an RDFSource - it worked but what does it mean? Not clear on how to change the RDF interaction model. Ie, how to go from an RDF Container to a RDF Direct container. Was it patch or link header? Jared will look into this more. Danny Bernstein thinks there might be a JIRA ticket for this.
- Danny Bernstein worked on the versioning part. He noted how the memento stuff is on a separate branch so he needed to test from there. When to merge? Probably only after we can create mementos, so not yet. Noted that there was a spec change in how versions are created. Most of the things in section 4.1 were not working yet. Many of the 'x's are due to not having finished the memento work yet.
- Should be able to get the LDPRv, but it won't have any mementos and will not accept Date-Time or do anything with that (since memento creation code is not complete yet)
- If folks work on the Resource Authorization section - put your name by the pieces you're working on so everyone knows someone is working on it.
- David Wilcox gave a brief update on the leadership meeting. Jared Whiklo has given them an update the state of Islandora CLAW.
Action Items
- Danny Bernstein to look for JIRA ticket around changing interaction model type.
- Danny Bernstein to touch base with Peter and Aaron regarding the Resource Authorization portion of the delta spec.
- Jared Whiklo to create issue for the pass/fail on the Compatibility Test Suite
