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)
- U.S.A/Canada toll free: 866-740-1260, participant code: 2257295
- International toll free: http://www.readytalk.com/intl
- Use the above link and input 2257295 and the country you are calling from to get your country's toll-free dial-in number
- Once on the call, enter participant code 2257295
- 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
- A. Soroka
- Unknown User (acoburn)
- Unknown User (escowles@ucsd.edu)
- Bethany Seeger
- Nick Ruest
- Andrew Woods
- Jared Whiklo
- David Wilcox
- Osman Din
- Yinlin Chen
- Michael Durbin
- James R. Griffin III
- Aaron Birkland
- Stefano Cossu
- Kevin S. Clarke
Agenda
Retiring m2.duraspace.org
- Server-managed Premis predicates:
- ModeShape and many-child-nodes... almost perfect: https://github.com/ModeShape/modeshape/pull/1459
Bug Prioritization
- F4 GitHub Organizations - "Becoming an fcrepo4-exts project"
- WebAC update
- Hydra and Islandora involvement?
- Notice: API Extension Architecture call tomorrow (design)
...
Tickets resolved this week:
Tickets created this week:
Minutes
Retiring m2.duraspace.org
- Hosts a number of Maven artifacts that Fedora 3 needs
- We would like to retire it
- One approach: retire very soon and offer a script and JAR files to build the latest version of Fedora 3
- Another option: Continue maintaining the server (not very appealing)
- Someone else could stand up the server on their own infrastructure and redirect the DNS
- We could send a post to the mailing list asking if anyone wants to maintain the server
- There are probably very few people interested in building Fedora 3 vs. just using the installer
- For these people, will Andrew’s build script work as an option?
Server-managed PREMIS predicates
- There are some server-managed predicates in Fedora 4 now
- In some cases users want to manage their own PREMIS properties but they are currently immutable
- Should we stop using non-Fedora predicates for server-managed properties?
- We have to reserve some LDP properties, though many can be updated via SPARQL-Update
- In the case of PREMIS/fixity, should we (1) use a Fedora namespace, or (2) continue to use PREMIS but allow the properties to be mutable?
- Recommendation: Investigate allowing fixity-related properties to be user-modified
- Longer-term: Investigate using a server-managed Fedora namespace instead of PREMIS
ModeShape performance issue with many child nodes
- This issue has been addressed by the ModeShape community by creating a new node type
- The only issue is that this new node type won’t work with versioning
- Might be possible to have the root node be of this type and all other nodes be of the normal (versionable) type
- This mix of versionable and non-versionable containers might be cumbersome
- Need to add some concerns as comments on the PR
- We need to run new scalability tests with these updates
- The only issue is that this new node type won’t work with versioning
6 Comments
Michael Durbin
In response to the discussion about using a shell script script to include the jar files for the fedora 3 build that aren't in any maven repo, would it not be desirable instead to use a maven-install-plugin with an execution in the POM file to "install-file" for each of those libraries?
Andrew Woods
Possibly... although that would require another release, no?
Michael Durbin
Wasn't the scope the the issue people who wanted to build the software? Updating the source code so that the git HEAD can build would be enough, right? But I suppose if people want to build old releases a patch (even just in the form of a pom file and a few jars) is more trouble than a script.
Ralf Claussnitzer
For building the latest Fedora 3 code, one could change the POM to resolve certain artifacts from a local directory in the source tree (e.g. fcrepo/lib). This way, no maven-install-plugin execution is needed.
Andrew Woods
Ralf Claussnitzer, you are suggesting creating an "fcrepo/lib" directory with the artifacts, an updating the pom.xml. That would also require a release, no?
Is that simpler than the provided script?
https://github.com/fcrepo3/fcrepo/releases/download/v3.8.1/install-f3-deps.zip
Ralf Claussnitzer
Yes, you are right, doing it this way would require a release. Also, a new release is much more work than the provided script. This can all be avoided with the Patch-and-Install approach.
However, having a non-functional POM which requires an extra script from outside the source feels a bit "unclean". In the end there are Fedora 3 sources that cannot be build after pulling them from master. That's already a big step towards full deprecation.