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
Attendees
- Jared Whiklo
- Nick Ruest
- Bethany Seeger
- Longshou Situ
- Unknown User (acoburn)
- A. Soroka
- Yinlin Chen
- Esmé Cowles
- Michael Durbin
- Kevin Ford
- Andrew Woods
- Peter Eichman
Agenda
LevelDB corruption issues - potential fix 4.1.1 (fcrepo-webapp-4.1.1-recovery.war)
Update on Versioning Spec - meeting notes
Fedora API GitHub repo(s)
- Which GitHub organization? fcrepo? duraspace?
- One or many repos?
- Are the constituent parts of the API versioned separately?
- Time to deprecate filesystem federation?
- Time to move fcrepo-message-consumer out of fcrepo4-exts?
- Review of: https://github.com/fcrepo4/ontology/pull/37
- ModeShape5 update
- Repository configuration (e.g. repository.json): should this be standardized in any way or do different Fedora implementations use whatever configuration style/content that makes sense for the implementation?
- Logging recommendations and style-guide
- ...
Status of "in-flight" tickets
Ticket Summaries
Please squash a bug!
Tickets resolved this week:
Tickets created this week:
Minutes
LevelDB corruption issues - potential fix 4.1.1 (fcrepo-webapp-4.1.1-recovery.war)
Discussion of a couple mailing list issues
- Consensus on Andrew Woods proposed resolution of
- using patch
- exporting content
- upgrating through fcrepo versions up to 4.5.1
- Consensus on Andrew Woods proposed resolution of
Get folks off LevelDB; Make a strong statement
Timing is problematic due to Modeshape 5
Update on Versioning Spec - meeting notes
- Waiting to get things into GitHub repo to proceed, and then into W3C spec format
- Waiting to get things into GitHub repo to proceed, and then into W3C spec format
Fedora API GitHub repo(s)
- Which GitHub organization? fcrepo? duraspace?
- fcrepo - https://github.com/fcrepo
- One or many repos?
- One standard with parts/chapters
- Are the constituent parts of the API versioned separately?
- Version as a unit
- Version as a unit
- Which GitHub organization? fcrepo? duraspace?
- Time to deprecate filesystem federation?
- Came from Esmé Cowles, out the D.C. Fedora Users group meeting
- Use webservers that perform better
- Discussion about moving it from core to fcrepo4-exts, or actually deprecating it
- Extract federation out of core base?
- Yes.
- Move it to labs
- Provide community notice, how to move from labs to exts
- If nobody picks it up after a period of time (to be determined), move it to archives/deprecated
- We need to make a deprecation warning, and a release before we do that
- "Super-double-down-deprecation-warning-with-blink-tags"
- "Super-double-down-deprecation-warning-with-blink-tags"
- Time to move fcrepo-message-consumer out of fcrepo4-exts?
- Move to labs
- Provide community notice, how to move from labs to exts
- If nobody picks it up after a period of time (to be determined), move it to archives/deprecated
- Review of: https://github.com/fcrepo4/ontology/pull/37
- This pull request brought up bigger issues about where this should live, and how things are organized
- Move to fcrepo4-exts
- Combine https://github.com/fcrepo4-exts/fcrepo-indexing-ontology & https://github.com/fcrepo4-exts/fcrepo-audit-ontology into a single fcrepo-exts ontology github repo, but still published as they are
- Discussion on how versioning will work if they are combined in one github repo
- Merge the pull request
- Needs some cleanup after move (A. Soroka will do it!)
- ModeShape5 update
- Carry to next meeting
- Carry to next meeting
- Repository configuration (e.g. repository.json): should this be standardized in any way or do different Fedora implementations use whatever configuration style/content that makes sense for the implementation?
- Carry to next meeting
- Carry to next meeting
- Logging recommendations and style-guide
- Carry to next meeting