Time/Place
This meeting is a hybrid teleconference and slack chat. Anyone is welcome to join...here's the info:
- Time: 11:00am Eastern Daylight Time US (UTC-4)
- Audio/Video Conference Link: https://duraspace.zoom.us/my/fedora
Dial-in:
+1 408 638 0968
+1 646 876 9923
+1 669 900 6833
Meeting ID:
812 835 3771
Join fedora-project.slack.com on the "tech" channel
Attendees
Agenda
Announcements
- 5.0.0 Release
- Release Post Mortem
- state of master and 5x-maintenance
- https://github.com/fcrepo4/fcrepo4/pull/1497 - pending PR for merging 5[.]x-maintenance into master
- Two PRs in master that will be in 5.0.1
- state of master and 5x-maintenance
- Remaining items - fcrepo-mint
- 5.0.1 Bugfix release
- Release Post Mortem
- Status of ecosystem tools:
- Java Client Release
- Camel Toolbox
- Docker
- Themes of first quarter 2018
- fcrepo-camel → Cameltoolbox -> vagrant
- 4→5 Migration (import export tool)
- 6.0.0:
- Modeshape replacement
- OCFL
- 5.1.0 - state tokens
<Your Discussion Point Here>
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
- Release announcement went out yesterday, release has been happening since last Friday. Lingering tasks around documentation and javadocs. CNI Fedora leaders meeting, consensus around moving off of Modeshape and bringing in OCFL in some sense. Read the minutes from the meeting. Bringing preservation into Fedora in some more concrete ways and OCFL seems like a place to start. Penn State and Emory are very interested and have funds to push this forward.
- Some issues related to updated plugins during the release process and some bugs have been found already that will need to be fixed.
- Master branch is now the 6.0.0-SNAPSHOT and the 5 maintenance branch is 5.1.0-SNAPSHOT to house any minor or bugfix releases.
- fcrepo-mint is in fcrepo4-exts and does not have a supporting institution (let alone 2), we need to find out if anyone is using and will help support it.
- fcrepo-audit is not performant and it is recommended to use the asynchronous auditing messages from the fcrepo-camel-toolbox. To make keep Fedora as "preservation", we should consider how we might adapt audit in the "after Modeshape" Fedora impl.
- UMD is storing checks and results for fixity checks inside Fedora, it would be good to capture this process in the community documentation.
- fcrepo-webapp-plus has no use in the 5.x branch
- fcrepo4-java-client can be released and should still work with the 4.7 branch.
- Should we be releasing fcrepo4-docker regularly sort of like the fcrepo4-vagrant?
- Should fcrepo-import-export be released with the other pieces to help people with migrate their repositories? Will not happen this time, but be good to consider going forward.
- Would be good to get fcrepo-camel-toolbox and fcrepo-vagrant updated and ready.
- fcrepo-camel-toolbox will need separate LDN processors for Fedora 4.x and 5.x, could release with 5.x compatibility and open some issues to add in 4.x compatibility too.
- Will return to this in the new year.
Actions
- Danny Bernstein to write short technical summary for the newsletter
- Danny Bernstein will rename the 5x-maintenance branch to 5.x-maintenance
- Danny Bernstein will reach out to Yinlin Chen to see about a fcrepo4-docker release with the 5.0 architecture.