...
Scheduling
Such a sprint would require a significant amount of community interestAt the earliest, this would likely be scheduled for some time during mid-August 2015
Possible The community itself will drive the direction of the sprint. Possible areas of focus include:
- Web ACL
- migration-utils?
At this point, there is little certainty; the community itself shall likely drive the direction of the sprint
Versioning/Upgrade Utility
Unknown User (escowles@ucsd.edu) was not present for the callNo other , and no other parties present appeared to be in the position to discuss this topic
Prioritized for later calls in which either Esme or Andrew Woods is present
API Extension Architecture
Aaron Birkland is aiming to next put out a call for interest from the community (in order to define the scope of the related tasks)
A. Birkland is just about to take his paternity will soon go on leave; Hencehence, this is to be delayed until his return during either early August or September
...
It is likely that this call for interest shall also involve the capturing of additional use cases
...
Structuring fcr:metadata resources as an LDP Container
Currently, non-RDF resources have the descriptive metadata structured using fcr:metadata
...
Without a clear sense for a time frame, this shall need to be discussed during the next call.
...
fcrepo-client and Issues Related to the Linking of fcr:metadata
James R. Griffin III seemed to be interested in undertaking this from the standpoint of becoming familiar with the code base
...
M. Durbin also advised that, if any such client is to be supported by other components of Fedora Commons 4.x, it would be best to have it covered within integration testing suites
LDPath Templating for HTML Views
...
James R. Griffin III showed some interest, but delayed commitment to the issue
Linking within the Splash Page
...
This would serve as a means by which to increase the degree of communication with the user base
Modeshape Integration and
...
OSGi Compliance
Currently, A. Coburn is working to decouple clean up the Modeshape package integration with fcrepo-kernel-impl (specifically, the parts of the fcrepo code that break into modeshape's internal classes)
By using the publicly-exposed Modeshape API, the best practices in compliance with complying with OSGI OSGi guidelines can be undertaken
...
Further, it appears to be the case that this was undertaken to access Infinispan cache stores more directly (and simply, as a consequence, broke through the Modeshape layer)
...
OSGi Cleaning
A. Birkland enquired as to whether or not A. Coburn still felt confident that complete OSGI OSGi support was possible for fcrepo-kernel
While this would be ideal, A. Coburn was uncertain as to whether or not this was possibleabout the degree to which the kernel can be completely modularized, but so far he is optimistic.
Issues in relation to the resolution of conflicts between Java servlet API's are far more trivial
...